ABI Error Message

VAQ:	COMM. INVOICE DATA NOT ON FILE

FILERS WHO PARTICIPATE IN THE ELECTRONIC INVOICE PROGRAM (EIP) MUST TRANSMIT COMMERCIAL INVOICE DATA TO ABI PRIOR TO TRANSMITTING THEIR SUMMARY DATA IF THE SUMMARY CONTAINS AN "E" IN POS 56 OF THE 10 RECORD. IF THE FILER IS PARTICIPATING IN THE INVOICE BY REQUEST PROGRAM, THEN IT IS PERMISSABLE TO TRANSMIT THE 42 RECORD WITH THE INVOICE NUMBER AND THE 43 RECORD WITH THE "INVREQ" DATA WITHOUT FIRST TRANSMITTING THE COMMERCIAL INVOICE. HOWEVER, UNLESS ONE OF THE TWO CONDITIONS ABOVE IS MET, A TRANSMISSION OF THE SUMMARY AS AN ELECTRONIC SUMMARY (EIP) WILL BE REJECTED WITH THIS ERROR MESSAGE. **NOTE** IF THE FILER USES MORE THAN ONE 42 RECORD PER 40 RECORD, AND "INVREQ" PERTAINS TO THE 42 RECORD, EACH 42 RECORD MUST BE ACCOMPANIED BY A 43 RECORD. IF THIS PAIRING IS NOT FOLLOWED, THIS ERROR MESSAGE WILL RESULT.

11Q:	SPI OF 'H' OR 'S' CANNOT BE ABI

SPI OF "H' OR 'S' IS NOT ALLOWED FOR ABI ENTRIES.

AR7:	NOTIFY SUB. DATA REJECTED

NOTIFY SUBSTITUTE DATA REJECTED.

RB9:	RECON/IMPORT SURETY MISMATCH

THE SURETY CODE ON THE RECONCILIATION SUMMARY DOES NOT MATCH THE SURETY CODE ON ONE OR MORE OF THE ASSOCIATED IMPORT ENTRIES. ALL IMPORT ENTRIES AND THE RECON SUMMARY MUST HAVE THE SAME SURETY CODE. (IF THE IMPORTER NUMBER IDENTIFIED IN THE RECON AND IMPORT ENTRIES HAS CHANGED SURETY COMPANIES DURING THE PERIOD COVERED BY THE RECON ENTRY, IT WILL BE NECESSARY FOR THE FILER TO FILE AT LEAST TWO RECON ENTRIES. THIS IS THE ONLY WAY TO MAINTAIN THE CORRELATION BETWEEN THE SURETY SHOWN IN THE R10 REC, POS 32-34 AND THE SURETY IDENTIFED ON EACH IMPORT ENTRY).

" 1BI:

LINE ITEM NOT FOUND

THIS MESSAGE IS GENERATED IN RESPONSE TO A CARGO RELEASE DATA INPUT TRANSACTION (APPLICATION HI). IF THE FILER FAILS TO TRANSMIT AT LEAST ONE H5 RECORD, THIS MESSAGE WILL RESULT.

ADF:	ENTRY IS NOT A STATEMENT ENTRY

THIS MESSAGE IS GENERATED WHEN APPLICATION HP (STATEMENT ADD/DELETE) IS ATTEMPTED. THIS APPLICATION ALLOWS FILERS TO MOVE THE PAYMENT DUE DATE ON ENTRIES SCHEDULED FOR PAYMENT BY STATEMENT. IF THE FILER ATTEMPTS TO REMOVE AN ENTRY FROM A STATEMENT BUT THE ENTRY IN QUESTION IS NOT CURRENTLY SCHEDULED FOR PAYMENT BY STATEMENT, THIS MESSAGE WILL BE GENERATED.

FD2:	PRODUCT CODE INVALID

PRODUCT CODE INVALID: IT CAN ONLY CONTAIN NUMERIC, ALPHA, OR HYPHENS IN POSITIONS 4 & 5. SPACES ARE NOT ALLOWED IN ANY POSITIONS.

99A:	INVALID AG LICENSE FORMAT

THE ENTERED AGRICULTURE LICENSE MUST BE IN ONE OF THE FOLLOWING FORMATS: 'N-AA-NNN-N' OR'N-A -NNN-N' WHERE 'N' =NUMERIC, 'A'=ALPHA, AND ' '=SPACE.  1. OR SUNDAY.

VKE:	HLT:DBID REQUIRED

DBID IS REQUIRED TO CREATE A TABLE/LOCATE INQUIRY DEFINITION.

386:	GSP COUNTRY EXP/ORIG CONFLICT

THE COUNTRY OF ORIGIN (40 RECORD, POS 6-7) AND THE EXPORT COUNTRY (50 REC, POS 69-70) MUST BE THE SAME AND MUST BOTH BE GSP ELIGIBLE TO CLAIM A DUTY EXEMPTION UNDER SPI "A" (REC 50, POS 3). IF THE COUNTRY OF EXPORT IS A MEMBER OF AN ASSOCIATION OF COUNTRIES (ASEAN, FOR EXAMPLE), THE COUNTRY OF EXPORT MAY DIFFER FROM THE COUNTRY OF ORIGIN WITHOUT VIOLATING THE GSP PROVISIONS.

VL7:	DRAWBACK DDPP NOT FOUND

THIS MESSAGE MEANS THAT THE FILER HAS USED AN IMPOSSIBLE DDPP IN THE DRAWBACK MODULE.

33C:	DATE OVER 90 DAYS INTO FUTURE

THE END DATE CANNOT BE OVER 90 DAYS UNLESS IT IS INDEFINITE. IN ADDITION TO THE ABOVE DEFINITION, IF ABI FILERS TRANSMIT ENTRY SUMMARY DATA WITH A PAYMENT DUE DATE MORE THAN 90 DAYS IN THE FUTURE, AS COMPARED TO THE TRANSMISSION DATE, THIS ERROR MESSAGE WILL BE GENERATED.

15F:	TARIFF NBR NOT LOGICALLY RELATED

THE TARIFF NUMBER IDENTIFIED IS NOT LOGICALLY RELATED TO ANOTHER TARIFF NUMBER ON THE LINE IN THE SUMMARY TRANSMISSION. THE MOST COMMON EXAMPLE IS THE ATTEMPT TO REPORT A NUMBER FROM CHAPTERS 1-97 WITH TARIFF NUMBER 98010010NN. THIS IS A TARIFF NUMBER FOR REPORTING THE RETURN OF A PRODUCT MANUFACTURED OR PRODUCED IN THE UNITED STATES. A SECOND TARIFF NUMBER IS NOT PERMITTED WHEN REPORTING U.S. GOODS RETURNED. OTHER EXAMPLES INCLUDE REPORTING WATCH/CLOCK COMPONENTS NOT RELATED TO ONE ANOTHER AND REPORTING CERTAIN WEARING APPAREL ARTICLES AS PART OF AN ENSEMBLE WHEN THE DATABASE DOES NOT RECOGNIZE THE COMPONENT AS BELONGING TO THE ENSEMBLE.

ACY:	IMPORTER NUMBER ALREADY ON FILE

THIS MESSAGE IS GENERATED IN RESPONSE TO AN ABI 5106 INPUT TRANSACTION (APPLICATION TI). IF THE IDENTIFICATION NUMBER (EIN, SSN, OR USCS ASSIGNED NUMBER) IS ALREADY ON FILE IN THE 5106 DATABASE, THIS MESSAGE WILL BE GENERATED TO THE FILER. NOTE: AS OF MAY 1998, THE ERROR MESSAGE NARRATIVE IS NOT BEING ACCOMPANIED BY THE IDENTIFICATION NUMBER "ACY".

AQ5:	INTERVENTION ALREADY FILED

AN INTERVENTION HAS ALREADY BEEN FILED AGAINST THE PROTEST. ONLY ONE INTERVENTION MAY BE FILED AGAINST ANY GIVEN 514 NAFTA PROTEST.

VA1:	INV DECLARATION IN 'OA' REC

THIS ERROR MESSAGE WILL BE GENERATED IF THE OA RECORD IS TRANSMITTED BLANK.

RBK:	RECON IMPT ENT CANNOT = RECON SUM

THE FILER HAS ATTEMPTED TO GIVE AN IMPORT ENTRY WITH THE SAME ENTRY NUMBER AS THEY ARE USING FOR THE RECONCILIATION SUMMARY.

EJ4:	DUTIABLE ADJ REQUIRED FOR NO CHG

FOR ABI CI TRANSMISSION, IF C02 OR C42 PAYMENT TERMS IS NO CHARGE ('15'), A DUTIABLE ADJUSTMENT (CODE "D") MUST BE PROVIDED IN THE C17 OR C53 RECORD. THIS MESSAGE WILL ALMOST ALWAYS BE ACCOMPANIED BY ERROR MESSAGE EJ5.

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

AFV:	PIRP NUMBER CANNOT FOLLOW DESC

IF FILERS USE THE 43 RECORD TO TRANSMIT "INVREQ", NO COMMERCIAL DESCRIPTION DATA IS PERMITTED IN POS 11-80 OF THE 43 REC. ANY DATA IN THIS FIELD WILL GENERATE THIS ERROR MESSAGE.

1M9:	IT DATE MORE THAN 2 YEARS OLD

MORE THAN 2 YEARS OLD

AQR:	BASE DATE QUALIFIER N/A

WHEN A FILING/AMENDMENT PERIOD BASE DATE IS SUBMITTED, FILER MUST DECLARE THE LIFECYCLE EVENT ASSOCIATED TO THE DATE. NO FILING/AMENDMENT PERIOD BASE DATE HAS BEEN SUBMITTED, OR IT HAS BEEN SUBMITTED IN ERROR.

8WO:	ACTUAL DATE OF ARRIVAL ON FILE

THIS MESSAGE OCCURS IN THE THE BILL OF LADING UPDATE FUNCTION (LN). THE FILER HAS ATTEMPTED TO SEND A NEW ESTIMATED ARRIVAL DATE IN POSITIONS 41-46 OF THE L1 RECORD WHEN THERE IS AN ACTUAL DATE OF ARRIVAL POSTED TO THE ENTRY FIL . PAGE BOL-3 OF THE CATAIR STATES "THE ESTIMATED DATE OF ARRIVAL CANNOT BE UPDATED IF THE AMS MODULE HAS ALREADY POSTED AN ACTUAL DATE OF ARRIVAL TO THE ENTRY."

2CI:	INBOND - INVALID CHECK DIGIT

ENTRY SUMMARY OR CARGO RELEASE INPUT TRANSACTIONS THAT REPORT PAPERLESS MASTER INBOND NUMBERS (THOSE STARTING WITH "V") MUST TRANSMIT A VALID MIB NUMBER, INCLUDING THE LAST DIGIT (CHECK DIGIT). IF THE LAST DIGIT IS NOT CORRECT, PRESUMING THAT THE FIRST 10 DIGITS ARE CORRECT, THIS ERROR MESSAGE WILL RESULT. THE FILER SHOULD RECONFIRM THE ENTIRE PAPERLESS MIB NUMBER WITH THE ISSUING CARRIER. NOTE: ERRORS IN THE CHECK DIGIT FOR AIR WAYBILLS USED AS INBOND NUMBERS OR FOR CONVENTIONAL (9 DIGIT ALL NUMERIC) INBOND NUMBERS WILL GENERATE ERROR MESSAGE 361.

10V:	SURETY CODE NOT FOUND

THIS MESSAGE APPLIES TO CARGO RELEASE TRANSACTIONS (HI) ONLY. A FILER MUST TRANSMIT BOND INFORMATION (AN "8" FOR A CONTINUOUS BOND OR A "9" FOR A SINGLE TRANSACTION BOND) IN THE H1 REC, POS 40. IF BOND TYPE "9" IS ELECTED, A SURETY CODE IS MANDATORY IN THE H1 REC, POS 71-73. IF THE SURETY CODE TRANSMITTED IS NOT FOUND LISTED ON THE SURETY DATABASE, THIS MESSAGE WILL RESULT. NOTE: IF THE SURETY CODE IS PRESENT ON THE DATABASE, BUT IS IN REVOKED STATUS, ERROR MESSAGE 10U WILL BE GENERATED.

 Next 10 >>Showing results 1 to 25 of 1405