ABI Error Message

125:	HIGH NUMBER NOT GREATER THAN LOW

DOCUMENT NUMBER: -THE HIGH DOCUMENT NUMBER MUST BE GREATER THAN THE LOW DOCUMENT NUMBER IN A RANGE. IT IS PERMISSIBLE FOR THE HIGH DOCUMENT NUMBER AND THE LOW DOCUMENT NUMBER TO BE THE SAME WHERE A SINGLE DOCUMENT NUMBER IS BEING ADJUSTED.

636:	ENTRY NUMBER-FISCAL YEAR ERROR

FISCAL YEAR PORTION OF THE ENTRY NUMBER DOES NOT MEET EDIT TESTS AGAINST THE ENTRY DATE

BRD:	IMPORT ENTRY NOT SUBJECT TO RECON

THE IMPORT ENTRY GIVEN IN THE R20 RECORD IS NOT FLAGGED FOR RECONCILIATION, THEREFORE CANNOT HAVE A RECONCILIATION FILED AGAINST IT.

40J:	SPI CLAIM INVALID FOR TARIFF

MOST TARIFF NUMBERS ARE ELIGIBLE FOR ONE OR MORE SPECIAL PROGRAMS THAT REDUCE OR ELIMINATE THE DUTY REQUIRED. THESE ARE CODED AS "SPI" FOR THOSE PROGRAMS THAT THE INDIVIDUAL TARIFF NUMBER HAS BEEN FLAGGED FOR. IF AN ABI FILERS TRANSMITS AN SPI (SUMMARY TRANSACTION 50 REC, POS 3, OR POS 78-79; 70/80/81 REC, POS 13 OR POS 79-80) THAT IS NOT LISTED ON THE TARIFF FILE FOR THAT TARIFF NUMBER, THIS ERROR MESSAGE WILL RESULT. FILERS SHOULD VERIFY THE SPI FROM THEIR HARMONIZED QUERY OUTPUT (V3 REC, POS 53-72) TO ASCERTAIN THAT THE SELECTED SPI APPLIES TO THE TARIFF NUMBER. NOTE: AS STATED IN ERROR MESSAGE 40L, IF THE TRANSMITTED SPI (50 RECORD OR 70 RECORD) IS ON THE TARIFF FILE FOR THE TARIFF NUMBER, IT MUST NONETHELESS AGREE WITH THE C/O CODE (EITHER "MX" OR "CA"). IF THE C/O IS "CA", AN SPI OF "MX" WILL GENERATE THIS ERROR MESSAGE.

371:	IR TAX REQUIRED

IF TARIFF FLAG = '1', AN INTERNAL REVENUE TAX APPLIES AND MUST BE INPUT ON THE LINE ITEM ENTRY . IF THE TARIFF FILE INDICATES THAT THE TARIFF NUMBER IS SUBJECT TO IRS EXCISE TAXES, THIS MESSAGE WILL BE GENERATED IF NO TAX AMOUNT IS TRANSMITTED IN THE 60 RECORD, POS 59-68. NOTE THAT IN THOSE INSTANCES WHERE THE FILER IS AUTHORIZED TO PAY LESS TAX (OR INADVERTENTLY TRANSMITS INCORRECT TAX), THAN THE STATUTORY TAX RATE WOULD INDICATE, ERROR MESSAGE 42N - "WARNING - EST TAX < COMPUTED TAX" WILL RESULT.

40O:	FAS SPI ORIG CTRY NOT = EXP CNTRY

IF AN ENTRY CLAIMS A FREELY ASSOCIATED STATES SPI (Z), THE COUNTRY OF ORIGIN AND THE COUNTRY OF EXPORT MUST BE THE SAME.

VBQ:	FW 3-177: NO MID NAME/ADDRESS

IF A SUMMARY IS TRANSMITTED WITH FISH AND WILDLIFE DATA AND THE MANUFACTURER ID IN THE FW03 RECORD IS LISTED ON THE MID FILE IN "PENDING" STATUS, THIS ERROR MESSAGE WILL RESULT. THAT FILE IS NOT CURRENTLY BEING EXPANDED WHEN FILERS TRANSMIT MID'S WITHOUT CORRESPONDING NAME AND ADDRESS DATA, SO THIS ERROR MESSAGE SHOULD NOT OCCUR OFTEN, IF AT ALL.

VQP:	MISSING FTZ NUMBER

THIS ERROR MESSAGE OCCURS IN THE NAFTA DUTY DEFERRAL MODULE. IF THE CLAIM TYPE INDICATOR IN THE D01 RECORD, POSITION 4 IS A '2' (FTZ) THEN THE IMPORT FTZ NUMBER IN THE D10 RECORD, POSITIONS 28-34 CANNOT BE SPACES.

660:	IMPORTER ON NAT'L SANCTION LIST

THIS ENTRY SHOULD BE REJECTED TO THE FILER. A DUTY PAID, "LIVE" ENTRY IS REQUIRED. IF A FILER RECEIVES THIS MESSAGE THROUGH ABI THERE IS ADDITIONAL INFORMATION THAT CAN BE PROVIDED TO ASSIST THE FILER IN RESOLVING THE PROBLEM. CLIENT REPS CAN CHECK THE ACS SYSTEM FOR SANCTION INFORMATION, INCLUDING A CONTACT AT THE NATIONAL FINANCE CENTER, AND BILL INFORMATION FOR ANY OUTSTANDING BILLS.

AD8:	INVOICE LINES NOT NUMERIC

THIS MESSAGE OCCURS WHEN AN EI 42 RECORD IS SENT WITH INVOICE LINES THAT ARE NOT ALL NUMERIC (E.G. A001).

176:	INVALID FILER CODE

THE THREE CHARACTER FILER CODE MUST BE ALPHA-NUMERIC. NO SPECIAL CHARACTERS AND MUST NOT BE LEFT BLANK.  FILER MUST BE INCLUDED IN THE APPROPRIATE ACS FILE AS A NATIONAL FILER, AND IN THE DISTRICT FILE AS ALLOWED TO FILE ENTRIES IN YOUR DISTRICT. ( ENTRIES FILED AFTER OCTOBER 1, 1986).

20A:	INVALID CARRIER CODE

THIS ERROR MESSAGE IS GENERATED IN RESPONSE TO ENTRY SUMMARY INPUT TRANSACTIONS. IF THE CARRIER CODE REPORTED IN THE 30 REC, POS 73-76, IS NOT ON THE CARRIER LIST FILE . THIS MESSAGE WILL BE GENERATED. IT DOES NOT MATTER IF THE SUMMARY CONTAINS A CARGO CERTIFICATION REQUEST. THE CARRIER CODE FIELD MUST BE FOUR CHARACTERS. OCEAN SHIPMENTS MUST HAVE A FOUR CHARACTER STANDARD ALPHA CARRIER CODE (SCAC) IN THIS FIELD. AIR SHIPMENTS MUST HAVE A TWO CHARACTER IATA CODE (ALSO FOUND ON THE CARRIER CODE FILE) IN THE POS 73-74 OF THE 30 RECORD. NOTE: IF THE CARRIER CODE IS OMITTED ENTIRELY, ERROR MSG 2DF WILL BE GENERATED. NOTE - THIS MESSAGE WILL ALSO GENERATE IF THE ENTRY USES AN AIR CARRIER CODE AND AN OCEAN PORT OF UNLADING CODE OR VICE VERSA.

381:	ORIGIN COUNTRY INVALID - UNKNOWN

INVALID COUNTRY OF ORIGIN - NOT ON FILE. FOR THE EI APPLICATION, REC 40,POS 6-7 IS BLANK OR CONTAINS A TWO CHARACTER ISO CODE THAT IS NOT PRESENT IN THE ACS COUNTRY CODE FILE, THIS MESSAGE WILL RESULT.

VNM:	WAIVER INVALID FOR BOND OR CLAIM

IN THE DRAWBACK MODULE THE WAIVER INDICATOR MAY ONLY BE 'Y' ('1' IF ABI) IF THE BOND TYPE CODE IS NOT '0' (WOULD BE EITHER '8' OR '9'), AND THE CLAIM TYPE IS NOT '41' OR '44 (MANUFACTURING DRAWBACK). IF 'Y' ('1' IF ABI) IS USED AND THE CONDITION IS NOT CORRECT THIS MESSAGE IS GENERATED. ALSO, WAIVER OF PRIOR NOTICE IS NOT VALID FOR TYPE '43' DRAWBACK CLAIMS.

AP3:	HEADER/DETAIL DATA REJECTED

THIS IS A SUMMARY TYPE MESSAGE. IT SIMPLY POINTS TO ERRORS MADE IN OTHER RECORDS CAUSING THE TRANSACTION TO BE REJECTED.

VP5:	ENTRY SUMM ALREADY ON FILE

THIS MESSAGE OCCURS IN THE NAFTA DUTY DEFERRAL MODULE WHEN THE NAFTA CLAIM ENTRY SUMMARY NUMBER SENT IN POSITIONS 11-21 OF THE D01 RECORD ALREADY EXISTS AS A CLAIM.

690:	I.T. DATE WITH NO I.T. NUMBER

I.T. DATA IS REPORTED IN THE SUMMARY TRANSACTION IN THE 22 RECORD. THE I.T. NUMBER IS REPORTED IN POS 3-14.  IF AN I.T. NUMBER IS REPORTED, AN I.T. DATE IS REQUIRED IN POS 64-69. LIKEWISE, IF AN I.T. DATE IS REPORTED, THERE MUST BE AN I.T. NUMBER. IF ONLY THE DATE IS REPORTED, THIS ERROR MESSAGE WILL BE GENERATED.

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.

VNF:	FD 701: NO BASE UNIT REPORTED

IF A FILER SENDS QUANTITY/UOM (UNIT OF MEASURE) INFORMATION (REC FD02) FOR AN FDA LINE, THE UOM MUST BE ONE OF THE FDA BASE UNITS LISTED ON PAGE OG-31 OF THE CATAIR IF ONLY ONE QUANTITY/UOM IS SENT. IF MORE THAN ONE QUANTITY/UOM IS SENT, THE LAST ONE MUST BE A BASE UNIT AND MUST BE A VALID ONE.

07S:	I.T.//NON I.T. CONFLICT

THIS MESSAGE RESULTS FROM A CARGO RELEASE INPUT TRANSACTION (APPLICATION HI). IF MULTIPLE BILLS OF LADING OR AIR WAYBILLS ARE REPORTED, ALL MUST BE EITHER RELATED TO AN INBOND NUMBER OR NONE CAN BE. IF THE FILER REPORTS ONE BILL WITH AN ASSOCIATED INBOND NUMBER AND DOES NOT INCLUDE INBOND DATA FOR ANY OTHER BILLS REPORTED, THIS MESSAGE WILL RESULT.

552:	ENTRY DELETE NOT ALLOWED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN ENTRY SUMMARY DELETE INPUT TRANSACTION (APPLICATION EI). IF THE FILER HAS PREVIOUSLY TRANSMITTED AN ENTRY SUMMARY THAT WAS REJECTED, AND THE SUMMARY IN QUESTION HAS NOT BEEN PAID IN OR OTHERWISE FILED WITH A LOCAL CUSTOMS OFFICE, THE ABI REJECT WILL ERASE PREVIOUSLY TRANSMITTED ABI ENTRY SUMMARY DATA. IN SUCH A CASE, THE TRANSMISSION OF AN ENTRY SUMMARY DELETE TRANSACTION (ACTION CODE "D" IN POS 3 OF THE 10 REC) WILL GENERATE THIS ERROR MESSAGE.

G9B:	REMOTE ENTRY/BOND TYPE CONFLICT

IF THE B RECORD REMOTE ENTRY INDICATOR IS A '1', THE BOND TYPE CODE IN THE ENTRY DATA MUST BE 8.

AQL:	ASSOC. PROT. NBR NOT APPLIC

WHEN FILING AN INTERVENTION IN A PROTEST OF AN ADVERSE COUNTRY OF ORIGIN MARKING DECISION UNDER NAFTA, THE USCS ASSIGNED PROTEST NUMBER UPON WHICH IS BEING INTERVENED IS REQUIRED. THE INTERVENTION MAY BE FILED AT ANY TIME AFTER PRO- TEST UNTIL USCS DECISION. THIS FIELD DOES NOT APPLY WHEN FILING TYPE 514 PROTESTS OR TYPE 520(C) OR 520(D) CLAIMS.

VHR:	DT HS7: INVALID MAKE

THIS ERROR RESULTS IF THE MAKE OF THE VEHICLE IN THE DT02 RECORD, POS 5-19 HAS FEWER THAN 3 CHARACTERS.

07A:	INVALID CROSS DIST PRCSSING PORT

THIS MESSAGE OCCURS IN AN 'HN' BORDER CARGO RELEASE TRANSACTION WHEN THE DISTRICT/PORT OF ENTRY SENT IN THE 01 RECORD, POSITIONS 4-7 IS DIFFERENT FROM THE PROCESSING DISTRICT/PORT SENT THE THE 'B' APPLICATION CONTROL RECORD, POSITIONS 4-7. THIS DESPITE THE WORDING IN THE DESCRIPTION BLOCK FOR THE DISTRICT/PORT OF ENTRY IN RECORD IDENTIFIER 01, PAGE BCR-4 OF THE CATAIR WHICH STATES "GENERALLY, THE DISTRICT CODE IS THE SAME AS THE DISTRICT CODE CONTAINED IN THE BLOCK CONTROL HEADER RECORD (RECORD IDENTIFIER B); HOWEVER, THE PORT CODE CAN BE DIFFERENT" THIS DOES NOT APPEAR TO BE TRUE. THE DDPP'S MUST BE THE SAME OR THIS REJECT OCCURS.

 Next 10 >>Showing results 1 to 25 of 1405