ABI Error Message

VNL:	AUTOCERT INVALID - OGA LINE RLSE

THIS MESSAGE OCCURS IN AN ENTRY SUMMARY TRANSACTION WHEN THE FILER ATTEMPTS TO CERTIFY FOR CARGO SELECTIVITY FOR AN ENTRY NUMBER WHICH WAS RELEASED AS A FDA LINE RELEASE ENTRY. THE FILER MUST SEND THE EI TRANSACTION WITHOUT CARGO RELEASE CERTIFICATION AND SEND A '1' IN POSITION 80 OF THE EI 10 RECORD WHICH IDENTIFIES THE ENTRY AS A FDA LINE RELEASE ENTRY. NOTE: THE ABOVE MESAGE WILL ALSO BE GENERATED FOR AN ENTRY NUMBER THAT HAS NOT BEEN PROCESSED THROUGH LINE RELEASE IF THE SAME CONDITIONS AS OUTLINED ABOVE EXIST (CARGO CERT IN POS 38 OF THE 30 RECORD ACCOMPANIED BY A 1 IN POS 80 OF THE 10 REC). THUS, THIS MESSAGE WILL RESULT ON NON-LINE RELEASE ENTRIES IF THE AUTO CERTIFICATION INDICATOR IS "1" AND THE OGA INDICATOR IS ALSO TRANSMITTED. (IF A TRUE NON-LINE RELEASE ENTRY, THE CORRECTION IS TO REMOVE THE OGA INDICATOR IN THE 10 RECORD).

23H:	BOND SANCTION IN EFFECT

THIS MESSAGE INDICATES THAT A SANCTION HAS BEEN PLACED AGAINST THE INDIVIDUAL BOND TRANSMITTED BY THE FILER.

AH8:	43 RECORD IS BLANK / INVALID

THE 43 RECORD IS INVALID OR BLANK.

56F:	ISSUER CODE REQUIRED

CARGO RELEASE INPUT TRANSACTIONS (APPLICATION HI) WHICH REPORT MODE OF TRANSPORTATION 10 OR 11 MUST ALSO REPORT A STANDARD CARRIER ALPHA CODE (SCAC). THIS ELEMENT IS TRANSMITTED IN THE HA, POS 70-73. IF THE ISSUER CODE IS OMITTED (ALL BLANKS IN THE FIELD), THIS ERROR MESSAGE WILL RESULT. NOTE: IF THE ERROR DESCRIBED ABOVE IS CONTAINED WITHIN AN ENTRY SUMMARY TRANSACTION (APPLICATION EI), ERROR MESSAGE ADJ WILL BE GENERATED. AS OF MARCH 2000, THIS ERROR MESSAGE IS NOW SENT IN RESPONSE TO AN ENTRY SUMMARY INPUT THAT OMITS THE ISSUER CODE IN THE 22 REC, POS 70-73.

EJN:	ID NUMBER (B) REQUIRED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). THE C37 RECORD PROVIDES SPACE FOR TWO IDENTIFICATION NUMBERS. THE SECOND (IDENTIFIER B) IS REPORTED IN POS 45-79.IF ONE OF THE FOUR VALID ID NUMBER QUALIFIERS (SEE PAGE AII-34) IS REPORTED IN POS 42-44 OF THE C37 RECORD, THERE MUST BE DATA IN POS 45-79 (THE DATAMUST BE LEFT JUSTIFIED STARTING IN POSITION 45 BUT DOES NOT HAVE TO OCCUPY THE ENTIRE FIELD). IF THE FIELD IS LEFT BLANK, THIS ERROR MESSAGE WILL BE GENERATED. **NOTE** - AS OF APRIL 1998, ONLY THE ID NUMBER QUALIFIER "VIN" IN POS 42-44 WILL RESULT IN THIS MESSAGE IF THE ID NUMBER FIELD IS LEFT BLANK.

ASE:	ENTRY NUMBER REQUIRED

WHEN A P60 IS TRANSMITTED THE ENTRY NUMBER DATA FIELD CANNOT BE BLANK.

EIE:	INVALID TYP SHIPPING/PACKING UNIT

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSACTION (APPLICATION CI). THE C05 REC, POS 19-23, PROVIDES SPACE TO REPORT A SHIPPING UNIT TYPE. VALID SHIPPING UNIT TYPES ARE LISTED IN APPENDIX B TO THE CATAIR, PAGES B-22 TO B-23. IF THE SHIPPING UNIT TYPE CODE TRANSMITTED IN THE C05 RECORD DOES NOT MATCH ONE OF THE SHIPPING UNIT TYPE CODES LISTED IN APPENDIX B, THIS ERROR MESSAGE WILL BE GENERATED.

89N:	MPF NOT REQUIRED

A MERCHANDISE PROCESSING FEE WAS ENTERED FOR THIS ENTRY BUT NOT REQUIRED. IN ADDITION, ABI WILL GENERATE THIS MESSAGE IN A VARIETY OF CONDITIONS WHEN MPF IS NOT APPROPRIATE. SOME OF THESE ARE: -- FILER SENDS A "CA" NAFTA CLAIM AND INCLUDES MPF. -- ENTRY IS FROM A CBI COUNTRY OF ORIGIN. -- AN INFORMAL ENTRY INCLUDES MPF ON THE LINE LEVEL (62 RECORD) -- THE CARGO IS AMERICAN GOODS RETURNED FROM HTS 9801. -- A TIB ENTRY IS TRANSMITTED (TYPE 23). -- CARGO IS FROM AN LDDC COUNTRY OF ORIGIN (COL 3). -- ISRAELI MERCHANDISE IS EXEMPTED (ADM 98-0772) -- FILER SENDS A "MX" NAFTA CLAIM AFTER 6/30/99 AND INCLUDES MPF.

23M:	SURETY SANCTION IN EFFECT

THIS MESSAGE INDICATES THAT THE SURETY COMPANY SENT BY THE FILER IS UNDER SANCTION.

94J:	EXPECTED UNH SEGMENT NOT FND

THIS IS A UN/EDIFACT SYNTAX ERROR MESSAGE. IT INDICATES THAT THE UNH MESSAGE HEADER IS MISSING.

VPD:	WHSE PROCESS TYPE INVALID

THIS MESSAGE OCCURS IN THE NAFTA DUTY DEFERRAL MODULE. THE WAREHOUSE ENTRY PROCESS TYPE MUST BE SENT IN THE D10 RECORD, POSITION 46 IF THE CLAIM TYPE INDICATOR IN THE D01 RECORD EQUALS 1. VALID WAREHOUSE PROCESSING TYPE CODES ARE: 1 EQUALS MANIPULATION, 2 = SMELTING OR MANUFACTURING.

94P:	UNABLE TO LOCATE BGM SEGMENT

EDIFACT SYNTAX ERROR. THE BGM (BEGINNING OF MESSAGE) SEGMENT IS MISSING.

VHE:	FC 740:INV PUBLIC W/HOLD IND

A CODE OF 'W' (WITHHOLD) IS SENT IN THE FC02 RECORD, POSITION 17, IF THE IMPORTER REQUESTS FCC 740 DATA BE WITHHELD FROM PUBLIC INSPECTION. ANY OTHER CODE WILL BE REJECTED.

8WR:	INVALID CONTROL ID / RECORD TYPE

THIS MESSAGE INDICATES A CONFLICT BETWEEN THE APPLICATION IDENTIFIER, WHICH IS TRANSMITTED IN THE "B" REC, POS 11-12 AND THE DETAIL RECORD IDENTIFIERS TRANSMITTED BETWEEN THE "B" AND "Y" RECORDS. EACH SEPARATE ABI APPLICATION HAS DESIGNATED RECORDS THAT CAN BE SENT IN THAT APPLICATION. IF ANY OTHER RECORDS ARE SENT WITH DIFFERENT RECORD IDENTIFIERS NOT ALLOWED BY THAT PARTICULAR APPLICATION, THIS MESSAGE WILL RESULT. AN EXAMPLE WOULD BE A TRANSMISSION OF THE TIB EXTENSION APPLICATION, WHICH WOULD HAVE "XN" IN THE "B" RECORD. THE INPUT RECORDS FOR THIS APPLICATION MUST ALL START WITH "XA". ANY OTHER RECORD IDENTIFIERS WILL BE REJECTED.

SBO:	MUST BE A "Y" OR "N"

THIS ERROR MESSAGE WILL RESULT IF AN ABI TRANSACTION IS SENT WITH A FIELD THAT REQUIRES A YES (Y) OR NO (N) INDICATOR FOR THE AFFECTED FIELD. AN EXAMPLE IS A RECONCILIATION ENTRY (TYPE 09) FOR WHICH THE FILER MUST INDICATE IF THE ENTRY IS AN AGGREGATE ENTRY (AGGREGATE INDICATOR = Y) OR AN ENTRY BY ENTRY RECONCILIATION (AGGREGATE INDICATOR =N). IF ANY OTHER CHARACTER IS USED IN SUCH A FIELD, THIS ERROR MESSAGE WILL RESULT

VN4:	D41 RECORD MUST CONTAIN DATA

THIS ERROR MESSAGE COULD BE THE RESULT OF A DRAWBACK OR ABI DRAWBACK PROBLEM. IT IS SAYING THEN WHEN CUSTOMS FORMATTED THE RECORDS FROM THE DISKETTE OR WHEN THE DATA WAS SENT VIA ABI, NO DATA WAS PRESENT IN THE GIVEN RECORD. IF THE DRAWBACK DISKETTE HAS NO DATA, THE PC PROGRAM SHOULD STOP IT BEFORE TRANSMISSION; HOWEVER, THERE MAY HAVE BEEN DATA THERE, BUT IT WAS BAD DATA.

2BU:	INVALID STATE CODE

ACS REQUIRES THE ABI FILER TO REPORT THE STATE OF ULTIMATE DESTINATION FOR THE IMPORTED CARGO. THIS CODE IS TRANSMITTED IN THE 10 REC, POS 78-79. ONLY THE TWO CHARACTER POSTAL ABBREVIATION FOR ONE OF THE 50 STATES WILL BE ACCEPTED IN THIS ELEMENT. IF ANY OTHER CODE IS TRANSMITTED, THIS ERROR MESSAGE WILL BE GENERATED. IF THE ADD 5106 APPLICATION (CODE TI) IS USED, THIS ERROR MESSAGE WILL BE GENERATED IF THE STATE CODE IS NOT ONE OF THOSE APPROVED BY THE UNITED STATES POSTAL SERVICE. NOTE THAT ERROR MESSAGE 2B8 IS IDENTICAL TO THIS ERROR MESSAGE AND MAY BE THE ONE BEING CALLED FOR 5106 INPUT ERRORS. THAT APPLICATIION IS NOT RETURNING ERROR CODES AS OF MAY 1998.

2AL:	SURETY CODE INVALID

IF THE FILER TRANSMITS BOND CODE 8 (CONTINUOUS BOND) IN THE SUMMARY INPUT (REC 10, POS 49), THE SURETY CODE IN REC 10, POS 73-75 MUST BE LISTED ON THE BOND DATABASE FILE AND MUST BE IN ACTIVE STATUS. IN ADDITION, THE SURETY CODE CITED IN THE 10 RECORD MUST MATCH THE SURETY CODE IN THE BOND DATABASE FILE FOR THE IMPORTER NUMBER TRANSMITTED IN REC 10, POS 8-19. (THE SURETY CODE FIELD CANNOT BE BLANK, EITHER). IF CASH IS USED IN LIEU OF A BOND, THE BOND TYPE MUST BE A "9" AND SURETY CODE "998" MUST BE USED. IF BOND TYPE "0" IS SENT, AND NO SURETY CODE IS SENT, AS WELL, THIS MESSAGES RESULTS. THIS MESSAGE WILL ALSO APPEAR IF THE IMPORTER HAS TWO ACTIVE CONTINUOUS BONDS IN EFFECT AT THE SAME TIME. THE SURETY CODE FOR THE BOND THAT WENT INTO EFFECT FIRST MUST BE USED ON SUMMARY INPUT TRANSACTIONS. SURETY CODES ARE VALIDATED BASED ON DATE OF RELEASE, SO A SUMMARY TRANSMITTED WITH A SURETY CODE BASED ON ESTIMATED ENTRY DATE WILL ALSO REJECT IF A DIFFERENT SURETY CODE WAS IN EFFECT AT THE TIME OF RELEASE. FOR RECONCILIATION, THE SURETY CODE GIVEN MUST BE VALID ON CUSTOMS FILE.

APN:	VOIDANCE REQST NOT VALID

A REQUEST FOR VOIDANCE OF DENIAL, INDICATED BY 'R', MAY BE SUBMITTED WITHIN 90 DAYS AFTER PROTEST HAS BEEN DENIED BY CUSTOMS. THE VOIDANCE REQUEST INDICATOR IS ALREADY SET AT 'R' (AFFIRMATIVE FOR REQUEST), OR THE PROTEST IS NOT IN DENIED STATUS.

AAP:	INVALID ADD/CVD CASE NUMBER

THIS MESSAGE OCCURS WHEN AN ABI FILER SENDS AN ANTIDUMPING OR COUNTERVAILING CASE NUMBER THAT IS INVALID. CASE NUMBERS ARE FORMATTTED AS FOLLOWS: A = ANTIDUMPING (OR C FOR COUNTERVAILING) CCC = CCC = FIRST THREE DIGITS OF THE COUNTRY CODE (FROM THE RFJ FILE). NNN = A SPECIFIC MANUFUCTURER WITHING THE CASE (OR 000 IF NOT SPECIFIC). IF, FOR EXAMPLE, A 'B' WAS SENT IN THE FIRST POSITION OR '###' WAS SENT IN THE NNN POSITIONS, THIS ERROR MESSAGE WOULD BE GENERATED.

95E:	ENTRY NOT ELIGIBLE FOR RECONCILE

THIS MESSAGE IS GENERATED IN RESPONSE TO AN ENTRY SUMMARY INPUT TRANSACTION (APPLICATION EI). ONLY THREE ENTRY TYPES ARE ELIGIBLE FOR THE RECONCILIATION PROTOTYPE AS OF OCT 1998. THE THREE TYPES ARE "01", "02", AND "06". IF ANY OTHER ENTRY TYPE IS TRANSMITTED IN THE 10 REC, POS 71-72, THIS ERROR MESSAGE WILL RESULT.

BRX:	EARLIEST IMPRT DATE MUST = SPACES

RECONCILIATION: WHEN THE R10 ISSUE CODE IS NOT = 'NF', THE R10 EARLIEST IMP DATE MUST = SPACES.

VPN:	D02 RECORD MUST CONTAIN DATA

THIS ERROR MESSAGE OCCURS IN THE NAFTA DUTY DERERRAL MODULE WHEN A D02 RECORD, OPTIONAL RECORD THAT CONTAINS THE CF4811 DATA AND BROKER REFERENCE NUMBER, IS SENT BUT CONTAINS NO DATA.

DDB:	OTHER RECONCILIATION NOT FILED

A DRAWBACK CLAIM CANNOT BE FILED AGAINST AN IMPORT ENTRY THAT HAS BEEN FLAGGED FOR RECONCILIATION UNTIL SUCH TIME AS THE RECONCILIATION SUMMARY HAS BEEN FILED AND PAID. AT THE TIME OF LIQUIDATION, THIS MESSAGE IS ALSO USED TO ALERT THE USER THAT A NAFTA RECONCILIATION IS DUE ON A TYPE '01', '02', OR '06' ENTRY, BUT HAS NOT YET BEEN FILED. THIS MESSAGE IS OVERRIDEABLE AT LIQUIDATION.

VAK:	FW 3-177: SPECIES NOT ON FILE

THE SPECIES CODE TRANSMITTED IN THE FW01 RECORD, POSITIONS 5-8 MUST BE RESIDENT IN THE FWS FILE.

 Next 10 >>Showing results 1 to 25 of 1405