ABI Error Message

VOR:	REMOTE ENTRY/SUMM CERT MISSING

THIS MESSAGE RESULTS WHEN A FILER, WHO IS SET TO OPERATIONAL FOR REMOTE LOCATION FILING (AND THEREFORE BY DEFINITION FOR AII), SENDS AN 'E' IN POSITION 56 OF THE 10 RECORD BUT DOES NOT SEND A '1' IN POSITION 37 OF THE 30 RECORD WHICH IS A CERTIFICATION OF THE ENTRY SUMMARY, AN ELECTRONIC SIGNATURE.

VH5:	DT HS7: DUPLICATE VIN ENCOUNTERED

IF TWO SETS OF DOT DATA ARE TRANSMITTED FOR THE SAME CUSTOMS LINE ON AN ENTRY, THE VIN NUMBERS TRANSMITTED IN THE DT02 RECORD CANNOT BE THE SAME. IF THEY ARE, THIS ERROR MESSAGE WILL RESULT. (NOTE: IF THE FILER NEEDS TO REPORT MORE THAN ONE VIN NUMBER FOR MULTIPLE IMPORTS ON THE SAME CUSTOMS LINE, A SEPARATE SET OF DT01/DT02 RECORDS IS REQUIRED FOR EACH VIN. THE DT03, ORIGINALLY DESIGNED TO PROVIDE SPACE TO REPORT MULTIPLE VINS, WILL NOT BE ACCEPTED BY ABI IF A DT02 IS ALSO TRANSMITTED. FOR BOX 2A ONLY, A DT03 CAN BE TRANSMITTED WITH VIN DATA IN LIEU OF A DT02. ALL OTHER BOX NUMBERS REQUIRE A DT02 TO REPORT VEHICLE DATA.)

APB:	USCS PROTEST NUMBER REQUIRED

THE CUSTOMS ASSIGNED PROTEST NUMBER ASSIGNED AT INITIAL PROTEST FILING IS REQUIRED FOR ALL SUBSEQUENT (AMENDMENT, ADDENDA & SERVICE) FILINGS FOR THAT PROTEST.

VNJ:	DCMCI IMPORTER/FILER INVALID

DCMCI ENTRIES FOR EMERGENCY WAR MATERIAL MAY BE ENTERED BY ANY FILER WHO USES ENTRY TYPE 01. IF ENTRY TYPE 51 IS USED, HOWEVER, THE ONLY ACCEPTABLE FILER CODE AND IMPORTER NUMBER MUST BELONG TO DCMCI. THE CURRENT VALID FILER CODE IS P99. IF A DIFFERENT FILER CODE IS USED, THIS ERROR MESSAGE WILL RESULT.

DKQ:	TOTAL CANADA TRAILER COUNT WRONG

THIS DRAWBACK MODULE ERROR MESSAGE MEANS THAT THE SUM OF ALL THE DISKETTE 'IT' IMPORT TRAILER, 'CN' CONTRACT TRAILER, 'CM' IMPORT TRAILER, OR 'CI' NAFTA IMPORT TRAILER RECORDS OR ABI 'D12', '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 ABI CANNOT KNOW WHETHER THE TOTAL COUNT IS SIMPLY WRONG, OR THE TOTAL COUNT IS RIGHT AND THERE ARE MISSING RECORDS.

8XU:	ENTRY MUST BE IN CUSTOMS STATUS

THIS MESSAGE APPLIES, AT A MINIMUM, TO THE TIB EXTENSION PROCEDURES (APPLICATION XN). IF A FILER ATTEMPTS TO EXTEND A TIB ENTRY, THAT ENTRY MUST FIRST BE IN CUSTOMS-ACCEPTED STATUS. IF THE ENTRY NUMBER IS ONLY IN 'ABI' STATUS, THIS MESSAGE WILL BE GENERATED IN RESPONSE TO THE FILER'S XN INPUT.

7BB:	DUPLICATE ENTRY & LINE-ITEM SEQ

THIS MESSAGE OCCURS IN THE ULTIMATE CONSIGNEE NAME AND ADDRESS (IJ) TRANSACTION WHEN THE FILER SENDS MULTIPLE I7 RECORDS WITH DIFFERENT LINE NUMBERS AND THE SAME ULTIMATE CONSIGNEE INFORMATION APPLIES TO ALL LINES. IF THE NAME AND ADDRESS INFORMATION APPLIES TO ALL LINES THE FILER SHOULD SEND JUST ONE I7 RECORD. IN 0400 AN ENTRY WAS FOUND WITH THIS ERROR WHERE AN IJ WAS ATTEMPTED SIX WEEKS AFTER THE SELECTIVITY ENTRY WAS CLOSED.

097:	ENTRY NBR ON HISTORY FILE

THE ENTRY NUMBER INPUT IS IN THE HISTORY FILE IN ABBREVIATED FORMAT.

ARV:	REFUND PARTY ID NBR REQUIRED

A VALID IRS OR USCS ASSIGNED ID NUMBER PRESENT ON THE USCS IMPORTER DATABASIS REQUIRED FOR ALL REFUND C/O PARTY TYPES.

B24:	LOWER CASE LETTERS FIRM/ADDR/CITY

FIRM NAME FIELD, ADDRESS FIELD, OR CITY NAME FIELD CONTAINS LOWER CASE ETTERS. IN ABI TRANSACTIONS, FILERS SHOULD ALWAYS SUBMIT UPPER CASE ALPHA CHARACTERS. IF THEIR SYSTEM SENDS LOWER CASE LETTERS IN EITHER THE FIRM NAME OR CITY FIELDS, THIS MESSAGE WILL BE GENERATED.

99E:	INVALID ENTRY TYPE / AG LICENSE

THE ENTRY TYPE MUST BE '02', '07', '21', '22'. '26', '30', '31', '32', '34', '35', '37', OR '38' FOR AN AGRICULTURE LICENSE TO BE ENTERED.

07H:	EST ARRIVAL DATE NOT IN RANGE

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, 3) ANY DATE UP TO 5 DAYS IN THE FUTURE.

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.

79S:	MID NOT ON FILE-LINE ITEM >?<

THIS MESSAGE IS GENERATED IN RESPONSE TO AN ENTRY SUMMARY INPUT TRANSACTION (APPLICATION EI). IF ONE OR MORE CUSTOMS LINES (40 RECORD) HAVE AN ASSOCIATED MID (60 REC, POS 43-57) THAT IS NOT REFLECTED ON THE SELECTIVITY FILE, THAT LINE(S) WILL BE IDENTIFIED IN THIS OUTPUT MESSAGE. THIS IS NOT A REJECT CONDITION BUT WILL PRECLUDE A PAPERLESS CARGO RELEASE FOR THE ENTRY.

AP9:	VOID. REQ. DATA REJECTED

VOIDANCE REQUEST DATA REJECTED. THE REQUEST TO VOID DENIAL OF THE PROTEST CAN ONLY BE SUBMITTED ONE TIME. REQUEST CANNOT BE MADE IF THE STATUS OF THE PROTEST IS OTHER THAN DENIED, PARTLY DENIED, NOT PROTESTABLE, OR UNTIMELY FILED-DENIED. THIS MESSAGE MAY ALSO BE RETURNED ALONG WITH THE AP8 WHEN VOID REQUEST DATA IS MISSING.

929:	DUTY DOES NOT MATCH

THE DUTY AMOUNT INPUT DOES NOT MATCH THE TOTAL OF ALL PAID DUTY AMOUNTS FOR THIS ENTRY.

AE4:	WARNING! ENTRY DATE < EXPORT DATE

THIS WARNING MESSAGE OCCURS IN THE "REVISED FILER DATE" (DN) TRANSACTION WHEN A FILER TRANSMITS AN ENTRY DATE THAT IS EARLIER THAN THE EXPORT DATE THAT RESIDES IN THE LINE ITEM FILE OF THE ENTRY SUMMARY RECORD.

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).

AQZ:	TEST CASE NUMBER NOT ON FILE

A MATCH FOR THE NUMBER ENTERED IN THE TEST SUMMONS NUMBER FIELD MUST BE FOUND IN THE USCS COURT SUMMONS FILE. A MATCH WAS NOT FOUND. ONLY SUMMONSES FILED AGAINST THE UNITED STATES CUSTOMS SERVICE ARE RECORDED IN ACS. SUMMONSES SERVED AGAINST OTHER AGENCIES, SUCH AS THE DEPARTMENT OF COMMERCE, CANNOT BE USED AS TEST CASE NUMBERS.

8WL:	INVALID CARRIER CODE

THIS ERROR MESSAGE OCCURS IN THE BILL OF LADING UPDATE (LN) TRANSACTION WHEN A FILER SENDS AN INVALID CARRIER CODE IN THE L1 RECORD, POSITIONS 32-35.

365:	IR TAX NOT APPLICABLE

IF THE TARIFF TAX CODE = '0', THE LINE ITEM INTERNAL REVENUE FIELD MUST BE BLANK . IF THE TARIFF FILE FOR THE REJECTED TARIFF NUMBER DOES NOT INDICATE THAT IRS EXCISE TAXES ARE APPLICABLE, THIS MESSAGE WILL RESULT IF AN ABI FILER TRANSITS IR TAX DATA IN REC 60, POS 59-68.

693:	INVALID MISSING DOCUMENT CODE

MISSING DOCUMENTS, SUCH AS COMMERCIAL INVOICES, DUTY-FREE CERTIFICATES, AND PACKING LISTS, MAY BE REPORTED AS "MISSING" ON THE SUMMARY INPUT. REC 10, POS 45-48 IS RESERVED FOR REPORTING ONE OR MORE MISSING DOCUMENTS. DATA FOR THIS FIELD MUST BE LISTED AS A VALID MISSING DOCUMENT CODE, WHICH CAN BE FOUND IN APPENDIX B OF THE CATAIR, PAGE B-13. ANY CODE NOT SPECIFIED ON THE LIST WILL BE REJECTED WITH THIS ERROR MESSAGE. 01 COMMERCIAL INVOICE 17 OGA FORMS 24-25 RESERVED 02-09 RESERVED 18 DUTY FREE ENT CERT 26 PACKING LIST 10 CF 5523 HSUS 9808.00.30009 27-97 RESERVED 11 CF 3291 19 SCALE WT. 98 NOT SPECIFIED ABOVE 12-13 RESERVED 20 END USE CERT 99 IF (3) OR MORE DOCS 14 LEASE STATEMENT 21 FORM 'O' (COFFEE) ARE MISSING USE CORR 15 RE-MELTING CERT 22 CHEMICAL ANALYSIS CODE FOR 1ST & '99' 16 CORR COMM INV 23 OUTTURN RPT FOR ANY ADDITIONAL

EJ5:	UNIT PRC/PYMNT TERMS INCONSISTENT

CONCERNING ABI CI, IF THE PAYMENT TERMS TYPE ON THE C02 RECORD IS '15' (NO CHARGE), THE UNIT PRICE ON THE C33 RECORD MUST BE ZERO. IF OTHER PAYMENT TERMS ARE USED ON THE C02 RECORD, THE UNIT PRICE MUST BE GREATER THAN ZERO. THIS MESSAGE IS ALMOST ALWAYS ACCOMPANIED BY ERROR MESSAGE EJ4.

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.

RBH:	RECONCILIATION DATE INVALID

THE RECON DATE PROVIDED IS INVALID OR IN INVALID FORMAT (MMDDYY).

 Next 10 >>Showing results 1 to 25 of 1405