ABI Error Message

C18:	TARIFF NUMBER NOT ON FILE

THIS MESSAGE OCCURS IN THE NAFTA DUTY DEFERRAL MODULE WHEN THE TARIFF NUMBER SENT IN THE D12 RECORD, POSITIONS 6-15, DOES NOT EXIST IN THE TARIFF DATABASE.

LI7:	LIQ RESULTS IN RFND TO BE ISSUED

RELIQUIDATION RESULTS IN REFUND BEING ISSUED. PRESS PF8 TO COMPLETE.

VA6:	OGA OI REC MAY NOT BE BLANK

THE "OI" RECORD IS USED IN OTHER GOVERNMENT AGENCY ENTRIES. THE DESCRIPTION IS LOCATED IN THE CATAIR, PAGE OG-11. THIS RECORD IS SENT WHEN THERE IS DATA TO BE SENT (I.E. THE LINE IS NOT "DISCLAIMED"). IF SENT, THE RECORD MUST NOT BE BLANK. THERE MUST BE A COMMERCIAL DESCRIPTION SENT (POS 11-80). THE TARIFF DESCRIPTION IS NOT TO BE SENT.

RBL:	RECON EXISTS - REPLACE OR DELETE

THE RECON ALREADY EXISTS ON CUSTOMS FILE AND THE FILER HAS ATTEMPTED AN 'A' TRANSACTION. FILER MUST PERFORM AN 'R' IF THE RECON IS ALREADY IN CUSTOMS STATUS, OR IS IN REJECTED STATUS. IF THE RECON ENTRY IS STILL IN ABI STATUS, THE FILER MAY TRANSMIT A 'D' TO DELETE THE RECON. NOTE: IF THIS ERROR MESSAGE IS RECEIVED, OFTEN THE FILER WILL ALSO RECEIVE ERROR MESSAGE BRH 'OTHER RECON ALREADY ON FILE' FOR ALL THE ASSOCIATED IMPORT ENTRIES. CORRECTING ERROR RBL WILL ALSO CORRECT ERROR BRH.

834:	ADD INVALID - BROKER REF MISMATCH

IF AN ENTRY SUMMARY RECORD EXISTS AND AN ADD TRANSACTION IS SUBMITTED VIA BATCH ABI INPUT, THE BROKER REFERENCE NUMBER IN THE EXISTING RECORD MUST MATCH THE BROKER REFERENCE NUMBER IN THE '20' RECORD OF THE BATCH ADD TRANSACTION. FILERS MAY CHANGE THEIR FILER REFERENCE NUMBER IF THEY USE ACTION CODE OF "R" (REPLACE) OR "C" (CHANGE) IN LIEU OF "A" (ADD). THIS MESSAGE WILL ALSO RESULT IF THE CARGO DATA INPUT APPLICATION (HI) OR THE BORDER CARGO RELEASE APPLICATION (HN) IS USED AND THE "A" ACTION CODE IS TRANSMITTED WITH A DIFFERENT BROKER REFERENCE NUMBER THAN WAS USED ON THE INITIAL INPUT.

8WW:	MASTER BL/AWB NUMBER REQUIRED

THIS ERROR MESSAGE IS GENERATED IN RESPONSE TO A BILL OF LADING UPDATE TRANSACTION (APPLICATION LN). IF THE L3 RECORD IS TRANSMITTED, AT A MINIMUM, THE BILL OF LADING (OR AIR WAYBILL) NUMBER, THE MANIFESTED QUANTITY AND THE MANIFESTED UNIT OF MEASURE ARE REQUIRED. OTHER ELEMENTS ON THE L3 RECORD ARE OPTIONAL. IF ONE OR MORE OF THE REQUIRED ELEMENTS ARE NOT PRESENT IN THE L3 RECORD, THIS ERROR MESSAGE WILL BE GENERATED.

VOB:	EXISTING ENTRY NOT DRAWBACK CLAIM

THIS MESSAGE RESULTS WHEN THE FILER TRANSMITS AN ADDITION/DELETION CODE OF EITHER 'A' OR 'D' AND THE CLAIM NUMBER USED ALREADY EXISTS IS ACS AND IS NOT A DRAWBACK CLAIM. IF THE ENTRY NUMBER HAS ALREADY BEEN USED AND IS NOT A DRAWBACK CLAIM, THE CLAIM AND DISKETTE WILL BE RETURNED FOR CORRECTION. ABI WILL REJECT THE TRANSMISSION.

DKG:	CLAIM EXISTS - SUBMIT 'DELETE'

THIS MESSAGE WILL APPEAR IF THE FILER HAS USED AN ADDITION/DELETION CODE OF 'A' ON THE 'CH' HEADER RECORD OF THE DRAWBACK DISKETTE (THE 'D10' RECORD FOR ABI) AND THE DRAWBACK CLAIM ALREADY EXISTS ON CUSTOMS FILE. A DELETE OF A CLAIM BY A FILER CAN ONLY BE HONORED IF THE CLAIM IS STILL IN ABI STATUS. ALL CLAIMS CREATED BY DISKETTE OR VIA ABI ARE PLACED IN ABI STATUS BY ACS WHEN FIRST ACCEPTED ERROR-FREE. THE SAME LOGIC APPLIES TO IMPORT ENTRIES FILED ELECTRONICALLY VIA ABI. ONCE IN CUSTOMS STATUS, THEY CANNOT BE DELETED BY THE FILER. IF NOT IN CUSTOMS STATUS, FILER MUST SUBMIT A 'D' ACTION CODE. NOTE: THE CLAIM CANNOT BE DELETED AT ALL IF ACCELERATED DRAWBACK HAS BEEN PAID. IF ACCELERATED HAS BEEN PAID AND THE FILER WISHES TO DELETE, THE CLAIM WILL HAVE TO BE LIQUIDATED "NO DRAWBACK" AND A BILL ISSUED FOR REPAYMENT OF THE ACCELERATED DRAWBACK. IF ACCELERATED HAS NOT BEEN PAID, BUT THE ENTRY IS IN A CUSTOMS STATUS, IT CAN BE CANCELLED, BUT NOT DELETED.

95T:	52 REC - 'CN' SWPM IND INVALID

THE REQUIRED SOLID WOOD PACKING MATERIAL INDICATOR MUST BE '1' OR '2'.

VH3:	FD 701 : ACTUAL SHPR ID REQUIRED

THERE ARE FIVE REQUIRED DATA ELEMENTS IN THE FDA INTERFACE. ONE IS THE FDA ACTUAL SHIPPER. IT IS REQUIRED TO BE SHOWN IN THE REC FD01, POS 63-77 (SEE CATAIR, PAGE OGA-28).THIS REJECT OCCURS WHEN NO MID IS TRANSMITTED.

VGN:	FD 701: UOM REQ IF QTY USED

IF A QUANTITY IS SENT IN THE FDA INTERFACE, REC FD02, POS 5-14, 19-28, 33-42, 47-56, 61-70 AND REC FD04, POS 5-14, A UNIT OF MEASURE (UOM) MUST BE TRANSMITTED. VALID FDA UNITS OF MEASURE ARE SHOWN ON PAGE OGA-31 OF THE CATAIR DOCUMENT. THESE UNITS ARE CONSIDERED TO BE "BASE UNITS" AND MUST BE EITHER THE LAST UNIT SENT (WHEN MORE THAN ONE QUANTITY/UOM PAIR IS ALSO TRANSMITTED) OR MUST BE THE UOM WHEN ONLY ONE QUANTITY IS SENT.

EIA:	INVALID INVOICE TYPE

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSACTION (APPLICATION CI). THE C01 REC, POS 43-44, PROVIDES A FIELD TO DESCRIBE WHICH ONE OF FIVE POSSIBLE TYPES OF INVOICE IS BEING REPORTED. THE TRANSMISSION OF EITHER A BLANK FIELD OR ANY OTHER INVOICE TYPE THAN IS SHOWN ON PAGE AII-6 OF THE CATAIR WILL RESULT IN THIS ERROR MESSAGE.

VEH:	FC 740 INV LINE #/SEQ

FCC DATA IS REPORTED IN THE FC01 AND FC02 RECORDS. THE FC01 RECORD MUST BE INCREMENTED FOR EACH SEPARATE MODEL/UNIT, ETC REPORTED IN THE SAME CUSTOMS LINE. IF THE FCC LINE NUMBER (FC01 REC, POS 8-10) IS NOT CORRECTLY INCREMENTED, THIS ERROR MESSAGE WILL RESULT.

8WM:	VOYAGE/FLIGHT NUMBER INVALID

THIS MESSAGE IS GENERATED IN RESPONSE TO A BILL OF LADING UPDATE TRANSMISSION (APPLICATION LN). THE VOYAGE/FLIGHT NUMBER MUST BE A MINIMUM OF THREE CHARACTERS IN LENGTH. FOR OCEAN SHIPMENTS (MOT 10/11/12), ANY COMBINATION OF NUMBERS AND LETTERS IS PERMITTED FOR THE VOYAGE NUMBER. IF THE VOYAGE NUMBER HAS A LEADING SPACE AT THE BEGINNING OF THE ELEMENT IN THE L1 REC, POS 36-40, THIS MESSAGE WILL BE GENERATED EVEN IF THE REMAINING POSITIONS ARE FILLED WITH A MINIMUM OF THREE ALPHA-NUMERIC CHARACTERS. **NOTE** - FOR AIR SHIPMENTS, LEADING SPACES OR A FLIGHT NUMBER WITH FEWER THAN 3 NUMERIC CHARACTERS WILL GENERATE ERROR MESSAGE 10R "INVALID FLIGHT NUMBER FORMAT".

BRZ:	POSSIBLE TAX MISMATCH

R20 ORIGINAL TAX DOES NOT MATCH PAID / LIQ TAX .

RB7:	R89 AND R21 ORIG AMTS DIFFER

TTHIS MEANS THAT THE ORIGINAL FEE AMOUNTS GIVEN FOR AN ENTRY-BY-ENTRY RECON IN THE 'R21' RECORDS FOR A GIVEN CLASS CODE DO NOT AGREE WITH THE 'R89' TOTAL ORIGINAL FEE AMOUNT FOR THAT CLASS CODE GIVEN IN THE 'R89' RECORD(S).

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.

2GC:	DATA ADDED AS REQUESTED

THIS IS A NORMAL RESPONSE MESSAGE TO A CARGO RELEASE DATA INPUT TRANSACTION (APPLICATION HI) WHEN THE FILER USES ACTION CODE "A" TO ADD DATA. UNLESS THE INPUT CONTAINS A CERTIFICATION CODE OF "1" IN POSITION 41 OF THE H1 RECORD, ABI WILL NOT GENERATE PROVISIONAL SELECTIVITY RESULTS TO THIS INPUT.

AGB:	SUMMARY NOT CERTIFIED

THIS MESSAGE OCCURS WHEN A FILER, WHO IS SET TO OPERATIONAL STATUS 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 (ELECTRONIC SIGNATURE). THIS MESSAGE WAS CORRECT WHEN WRITTEN, BUT IT NOW (APR 2000) MEANS THAT THE CARGO CERTIFICATION (30 REC, POS 38) WAS OMITTED.

2C3:	INVALID BOND

CONVERTED BOND TYPE 2: * MAY BE ON FILE BUT NOT FOR THE PORT OF ENTRY AND NOT ON FILE AT A CROSS DDPP OF THE PORT OF ENTRY FOR THE IMPORTER OR ITS PARENT (IF APPLICABLE), * IS ON THE FILE BUT DOESN'T COVER THE DATE OF THE ENTRY DOESN'T AGREE WITH THE BOND TYPE THAT IS ON FILE. CONVERTED BOND TYPE 5: * IS NOT ON FILE FOR THE IMPORTER OR ITS PARENT COMPANY * IS ON THE FILE BUT DOESN'T COVER THE DATE OF THE ENTRY BOND TYPE 8: * THE BOND THAT IS ON FILE IS NOT A VALID CONTINUOUSBOND THAT IS APPROPRIATE FOR THE ENTRY TYPE. FOR BOND TYPE 8, IF THE BOND IS NOT ON FILE ON THE DATE USED FOR BOND VALIDATION (CARGO REL DATE, PAY DUE DATE, ETC) IN THE SUMMARY INPUT, THIS ERROR MESSAGE WILL RESULT. THIS WILL ALSO APPLY TO ENTRIES WITH A BOND THAT IS NOT EITHER A 1 OR 1A1 TYPE BOND IN THE BNDL FILE.

VHD:	FDA701:AFRM/CMPLNCE NOT ALLOWED

THIS MESSAGE OCCURS WHEN A FILER ATTEMPTS TO SEND A FDA AFFIRMATION OF COMPLIANCE CODE IN THE FD05 RECORD, POSITIONS 5-7 WHEN THE AFFIRMATION OF COMPLIANCE CODE IN THE FD01 RECORD, POSITIONS 20-22 IS BLANK. IF THERE IS ONLY ONE AFFIRMATION OF COMPLIANCE CODE IT MUST BE SENT IN THE FD01 RECORD. ANY ADDITIONAL (UP TO FOUR) CODES ARE SENT IN THE FD05 RECORD AND THEY CANNOT BE DUPLICATES OF THE CODE IN THE FD01 RECORD.

SUS:	WARNING - SURETY SANCTIONED

FOR RECONCILIATION, THE SURETY ORIGINALLY GIVEN ON THE IMPORT ENTRIES IS NOW SANCTIONED.

AD9:	OVERLAPPING INVOICE LINE RANGE

THIS MESSAGE OCCURS WHEN AN EI 42 RECORD IS SENT WITH OVERLAPPING INVOICE LINE RANGES. FOR EXAMPLE, IF INVOICE A IS SENT WITH A BEGINNING AND ENDING RANGE 0001-0004 AND INVOICE B HAS A BEGINNING AND ENDING RANGE OF 0004-0008, THIS MESSAGE WILL OCCUR BECAUSE '0004' OVERLAP.

ARD:	SURETY CERTIFICATION N/A

EITHER THE PROTESTANT IS NOT A SURETY, THE INDICATOR TRANSMITTED WAS A LETTER OR CHARACTER OTHER THAN "Y", OR THE SURETY CERTIFICATION WAS INCORRECTLY USED AS PART OF AN AMENDMENT, ADDENDA, OR SERVICE REQUEST TRANSMISSION.

AR4:	REFUND PARTY DATA INCOMPLETE

EITHER THE ID NUMBER OR THE PARTY TYPE INDICATOR IS MISSING, OR A BLANK RECORD WAS RECEIVED.

 Next 10 >>Showing results 1 to 25 of 1405