ABI Error Message

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.

DK8:	TOT SCHEDB TRAILER COUNT INVALID

THIS MESSAGE OCCURS IN THE AUTOMATED DRAWBACK MODULE. THE SUM OF THE ABI 'D12', 'D20', 'D25', 'D30', 'D40', OR 'D50' RECORDS DOES NOT ADD UP TO WHAT THE COUNT IS IN THE 'CT CLAIM TRAILER' RECORD, OR ABI 'D90' RECORD. BECAUSE IT DOES NOT ADD UP, WE CANNOT KNOW WHETHER THE TOTAL COUNT IS SIMPLY WRONG, OR THE TOTAL COUNT IS RIGHT AND WE ARE MISSING RECORDS.

79H:	TARIFF FORMAT/CONTEXT ERROR

FORMAT OR CONTEXT ERROR

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.

183:	INVALID REGION/DISTRICT/PORT

REGION/DISTRICT/PORT IS NOT VALID ON THE REGION DISTRICT PORT FILE.

8WK:	EST ARRIVAL DT > SELECTIVITY DT

THIS MESSAGE OCCURS IN A BILL OF LADING UPDATE TRANSACTION (LN) FOR AN AIR ENTRY WHEN A FILER SENDS A NEW ESTIMATED DATE OF ARRIVAL THAT EXCEEDS THE DATE OF PROVISIONAL SELECTIVITY PROCESSING.

EJA:	QUANTITY DISPATCHED REQUIRED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). THE C39 RECORD IS USED TO REPORT VARIATIONS FROM THE QUANTITIES REPORTED IN THE C33 RECORD. IF THE "QUANTITY DISPATCHED" BY THE INVOICING PARTY DIFFERS FROM THE QUANTITY REPORTED IN THE C33 RECORD, THAT DIFFERENCE IS REPORTED ON THIS RECORD. THE "QUANTITY DISPATCHED" FIELD IN POS 4-18 MUST CONTAIN A NUMBER GREATER THAN ZERO, OR THIS ERROR MESSAGE WILL BE GENERATED.

DKN:	D50 RECORD MUST CONTAIN DATA

THIS ERROR MESSAGE COULD BE THE RESULT OF A DRAWBACK DISKETTE OR ABI DRAWBACK PROBLEM. IT IS SAYING THAT WHEN CUSTOMS FORMATTED THE RECORDS FROM THE DRAWBACK 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.

VKA:	HLT: TABLE NAME REQUIRED

TABLE NAME AND SEARCH NUMBER ARE BOTH REQUIRED TO CONSTRUCT A VALID TABLE LOCATE/INQUIRY DEFINITION.

EJQ:	ENTRY ALREADY HAS ABI STATEMENT

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). IF ANY ENTRY ASSOCIATED WITH THE INVOICE IN THE INSTANT TRANSMISSION HAS ALREADY APPEARED ON A PRELIMINARY STATEMENT, CHANGES TO THE INVOICE ARE NOT PERMITTED. UPDATES TO INVOICE DATA ARE ONLY PERMITTED IF THE ASSOCIATED ENTRIES HAVE NOT YET APPEARED ON A STATEMENT.

Q01:	INPUT RECORD TYPE MUST BE "QT"

POSITIONS 1&2 ON EACH INPUT RECORD WITHIN THE "QN" APPLICATION MUST BE "QT" .

99P:	ADDITIONAL WARNING ON ERRORS

NUMBER OF MESSAGES PASSED BACK TO PROGRAM CALLING ABIGI1 EXCEEDS 10.

23H:	BOND SANCTION IN EFFECT

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

60M:	COUNTRY CODE(S) MUST BE PRESENT

COUNTRY CODE(S) MUST BE PRESENT WHEN COUNTRY RESPONSIBILITY CODE = 1 OR 2.  COUNTRY RESPONSIBILITY CODE 1 = INDIVIDUAL COUNTRIES; 2 = COUNTRY RANGE

Q03:	'QT' FILER INVALID

QT INPUT RECORD HAS SPACES OR ALL ZEROS IN POS 11-13.

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.

2AI:	INVALID BOND TYPE

A SHORT LISTING OF CURRENT BOND TYPES AND THEIR CORRESPONDING ACTIVITY CODES CAN BE FOUND IN THE CATAIR ON PAGE QIB-8. NOTE: ABI FILERS WHO DO BOND QUERIES WILL RECEIVE A SINGLE ALPHA CHARACTER CODE DESIGNATING WHICH TYPE OF BOND IS ON FILE, IF ANY, FOR THE IMPORTER BEING QUERIED. THE FILER'S SOFTWARE SHOULD TRANSLATE THE CODE INTO THE APPROPRIATE BOND TYPE AND DESCRIPTION.

12O:	INVALID FIRMS CODE

THE FIRMS CODE MUST BE 4 ALPHA NUMERIC CHARACTERS IN LENGTH.

VMK:	INVALID DIST/PORT ON WHSE ENTRY

THE DISTRICT PORT ON 30 RECORD OF EI APPLICATION DID NOT MATCH THE DISTRICT/PORT OF THE WITHDRAWAL SUMMARY.

ABX:	BROKER NOT AUTHORIZED FOR REQUEST

A BROKER HAS REQUESTED INFORMATION THAT MAY BE ON FILE, BUT IS NOT ASSIGNED ITS FILER CODE. FOR RECONCILIATION ENTRIES, THIS MESSAGE INDICATES THAT THE FILER IS NOT A STATEMENT FILER IN THE PORT OF PROCESS. RECONCILIATION ENTRIES MUST BE PAID VIA STATEMENT PROCESSING, THUS THE FILER WILL GET THIS REJECT MESSAGE UNTIL HIS PROFILE RECORD REFLECTS OPERATIONAL STATUS FOR STATEMENT PROCESSING.

05F:	PC:EST ARR DATE NOT IN RANGE

PAIRED CITIES ENTRY. THE ESTIMATED ARRIVAL DATE ENTERED IS NOT WITHIN THE RANGE ALLOWED. VALID DATES INCLUDE:  1) TODAY'S DATE; 2) ANY DATE UP TO 30 DAYS IN THE PAST; AND 3) ANY DATE UP TO 5 DAYS IN THE FUTURE

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.

2A7:	CARGO RELEASE DATA NOT ON FILE

THIS MESSAGE GENERALLY INDICATES A PROBLEM IN THE CREATION OF CARGO SELECTIVITY RECORDS FROM FILER'S INPUT. EXAMPLE: A FILER SENT IN SEVERAL ENTRIES USING BORDER CARGO RELEASE (APPLICATION HN). BEFORE ABI COULD COMPLETE THE PROCESSING OF THE ENTRIES, THE FILER'S SYSTEM SENT THE SAME ENTRIES AGAIN (WITHIN 12 SECONDS OF THE FIRST TRANSMISSION). THIS DUPLICATION CAUSED DATABASE (DB) ERRORS ON THOSE ENTRIES THAT WERE BEING PROCESSED AT THE INSTANT THE SECOND ITERATION OF THE SAME ENTRY NUMBER REACHED THE MAINFRAME. THE SECOND SET OF ENTRIES HAD PROCESSING DONE, BUT NO ON-LINE RECORDS WERE CREATED. THE ERROR MESSAGE ABOVE WAS CREATED AND ATTACHED TO THE SECOND SET OF ENTRY NUMBERS. THE SOLUTION, IN ALMOST ALL CASES, IS FOR THE FILER TO TRANSMIT ONLY ONCE AND TO WAIT FOR RESULTS BEFORE RE-SUBMITTING DATA FOR THE SAME ENTRY NUMBER.

27E:	*CENSUS* OR-HI VAL/QTY (1)TARIFF2

THE UNIT PRICE (VALUE/PRIMARY QUANTITY) IS NOT WITHIN SPECIFIC LIMITS

41D:	WARNING TSUSA EFFECT. W/IN 3 WKS.

THIS MESSAGE IS A WARNING MESSAGE, NOT A REJECTION. IT USUALLY REFERS TO THE FACT THAT THE ENTRY SUMMARY CONTAINS A NEWLY CREATED TARIFF NUMBER THAT HAS GONE INTO EFFECT WITHIN  THE LAST THREE CALENDAR WEEKS. IT HAS NO BEARING ON THE PROCESSING OF THE CARGO RELEASE TRANSACTION.

 Next 10 >>Showing results 1 to 25 of 1405