ABI Error Message

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.

2B1:	MODE OF TRANSPORTATION REQUIRED

THE MODE OF TRANSPORTATION (MOT) IS REQUIRED TO BE SHOWN IN ALL FORMAL ENTRY SUMMARY INPUT TRANSACTIONS. THE MOT IS SENT IN THE 20 REC, POS 28-29. IF THE MOT IS LEFT BLANK, THIS ERROR MESSAGE IS GENERATED. FOR INFORMAL ENTRIES AND FOR CARGO RELEASE INPUT TRANSACTIONS (APPLICATION IDENTIFIER HI), SEE ERROR MESSAGE 630.

36P:	INVALID CHECK DIGIT FACTOR

WITH THE NEW CHECK DIGIT FIELD ON THE NATIONAL FILER DATABASE RECORD YOU MAY ONLY HAVE A VALUE 1 (ONE) OR 0 (ZERO).

AR7:	NOTIFY SUB. DATA REJECTED

NOTIFY SUBSTITUTE DATA REJECTED.

070:	INVALID OBJECT CLASS

1 TO 3 DIGIT CODE IS NOT FOUND WHEN VALIDATED AGAINST THE CAMIS OBJECT CLASS CODE FILE. OBJECT CLASS CODE IS NOT NUMERIC. EXCEPTION: MAY BE NON-NUMERIC FOR CLASS CODES 060,061,062,063,069 OR 071. LEFT-JUSTIFIED ZEROS ARE NOT REQUIRED INPUT.

AP4:	AFR REQUEST DATA INCOMPLETE

WHEN FURTHER REVIEW IS APPLIED FOR AT TIME OF INITIAL FILING, THREE CRITERIA QUESTIONS MUST BE ANSWERED IN THE P16 RECORD. WHEN FURTHER REVIEW IS APPLIED FOR AT TIME OF INITIAL FILING OR BY AMENDMENT, THE THREE CRITERIA QUESTIONS MUST BE ANSWERED, AND ADDITIONAL NARRATIVE MUST BE SENT JUSTIFYING FURTHER REVIEW ACCORDING TO CFR 174.25(B)(3).

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.

12P:	FIRMS CODE NOT ON FILE

FIRMS CODE TRANSMITTED NOT FOUND ON DATABASE.

183:	INVALID REGION/DISTRICT/PORT

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

4BH:	ENTRY TYPE CHANGE INVALID

THIS MESSAGE INDICATES THAT THE ABI FILER IS ATTEMPTING TO TRANSMIT AN ENTRY SUMMARY WITH A DIFFERENT ENTRY TYPE THAN EXISTS ON THE ENTRY SUMMARY HEADER FILE FOR THE ENTRY NUMBER. IF THE ENTRY IS IN CUSTOMS STATUS, SUCH A CHANGE IS NOT PERMITTED. IF THE ENTRY IS STILL IN ABI STATUS, THIS CHANGE CAN USUALLY BE ACCOMPLISHED. THE MOST COMMON CHANGE IS FROM TYPE 11 TO TYPE 01 (OR VICE VERSA IN SOME CASES). FOR RECONCILIATION ON-LINE PROCESSING, THIS ERROR MEANS THAT YOU CANNOT CHANGE ANY PRE-EXISTING ENTRY THAT IS NOT RECONCILIATION TO A TYPE '09' RECONCILIATION ENTRY SUMMARY.

DKZ:	TARIFF NOT ONFILE

THIS MESSAGE OCCURS IN THE AUTOMATED DRAWBACK MODULE. THE MESSAGE SIMPLY MEANS THAT THE NUMBER, AT THE 6, 8, OR 10 DIGIT LEVEL DOES NOT EXIST ON THE TARIFF FILE. NORMALLY, THIS OCCURS WHEN THE FILER HAS GIVEN 10 DIGITS ON OLDER RECORDS. FOR OLDER RECORDS, IF THE FILER USES 6 DIGITS (OR 8 IF PETROLEUM) THE PROBLEM IS MINIMIZED.

VGW:	FD 701: ACTUAL MFG REQUIRED

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

BRS:	R10 FIELDS MUST MATCH FILED ENTRY

THIS MESSAGE CAN OCCUR IF THE RECONCILIATION SUMMARY IS ALREADY FILED AND THE FILER IS DOING A REPLACEMENT OR CORRECTION. VIRTUALLY ALL FIELDS IN THE NEW 'R10' MUST MATCH WHAT IS ALREADY ON FILE. THE MAIN REASON FOR THIS REJECT IS THE ABSENCE OF A '00' SUFFIX IN THE IMPORTER OF RECORD NUMBER IN THE R10 REC, POS 20-31. EVEN IF THE ORIGINAL TRANSMISSION DID NOT CONTAIN THE SUFFIX, ONCE IT HAS BEEN ACCEPTED ERROR-FREE, THE ENAI RECORD SUPPLIES THE ZEROS AND MAKES THEM MANDATORY WHEN A RETRANSMISSION IS DONE. NOTE THAT THE R10 RECORD LISTS TWO FIELDS WHERE THIS ERROR CAN OCCUR: THE IMPORTER ID MENTIONED ABOVE IN POS 20-31 AND THE 4811 REFERENCE NUMBER IN POS 60-71. BOTH FIELDS MUST HAVE A SUFFIX IN ORDER TO PROCESS THE RECON ENTRY. A SECOND REASON FOR THIS REJECTION MESSAGE RELATES TO THE RECON TEAM, IN POS 41-43 OF THE R10. IF THE PORT HAS CHANGED THE ASSIGNED TEAM ON THE ENAI RECORD FOR THE PREVIOUSLY TRANSMITTED 09 ENTRY, IT MUST BE CHANGED BACK TO THE APPROPRIATE RECON TEAM NUMBER BEFORE THE FILER CAN RETRANSMIT THE ENTRY.

API:	AFR REQUEST IND. INVALID

AN APPLICATION FOR FURTHER REVIEW, INDICATED BY 'R', APPLIES ONLY TO TYPE 514 PROTESTS, AND MUST BE REQUESTED DURING FILING AND AMENDMENT PERIOD, EITHER INITIAL FILING OR BY AN AMENDMENT FILING. THE VALUE SUBMITTED IN THE AFR REQUEST FIELD IS NOT 'R'.

BRX:	EARLIEST IMPRT DATE MUST = SPACES

RECONCILIATION: WHEN THE R10 ISSUE CODE IS NOT = 'NF', THE R10 EARLIEST IMP DATE MUST = SPACES.

EI2:	QUANTITY REQUIRED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSACTION (APPLICATION CI). QUANTITY DATA IS REPORTED IN THE C33 REC (POS 4-18) OR THE C34 REC (POS 4-18 AND 22-36). IF THE ARTICLE DESCRIBED IN THE INVOICE HAS ONE OR MORE QUANTITIES (BASED ON THE TARIFF NUMBER WHICH DESCRIBES THE ARTICLE), THE C33 AND C34 RECORDS PROVIDE THE MEANS TO REPORT THE REQUIRED QUANTITIES. AT A MINIMUM, THE C33 RECORD MUST CONTAIN A NUMBER GREATER THAN ZERO. IF THE C34 RECORD IS USED TO DESCRIBE ADDITIONAL QUANTITES FOR THE ARTICLE, THE QUANTITY FIELDS IN THAT RECORD MUST BE GREATER THAN ZERO, DEPENDING ON WHETHER THE ARTICLE DESCRIBED HAS TWO REPORTABLE QUANTITIES (WHICH WOULD REQUIRE THE C33 RECORD AND THE "QUANTTIY 2 FIELD IN THE C34 REC) OR THREE REPORTABLE QUANTITES (WHICH WOULD REQUIRE THE C33 REC, AND THE QUANTITY 2 AND QUANTITY 3 FIELDS IN THE C34 REC).

LI7:	LIQ RESULTS IN RFND TO BE ISSUED

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

AQ0:	NO FILING PERIOD BASE DATE

WHEN A FILING/AMENDMENT BASIS INDICATOR IS USED, A FILING PERIOD BASE DATE REQUIRED. THE FILING PERIOD BASE DATE IS BLANK.

4L0:	TARIFF (2) INVALID

TARIFF NUMBER TWO IS INVALID

355:	ENTRY NOT FOUND

THIS MESSAGE OCCURS WHEN A FILER ATTEMPTS TO USE THE 'HP' STATEMENT ADD/DELETE TRANSACTION FOR AN ENTRY THAT IS NOT FOUND ELIGIBLE FOR AN 'HP'. AN EXAMPLE WOULD BE AN ENTRY THAT HAS BEEN ARCHIVED (ACS HISTORY FILE).

4NN:	LINE ITEM VALUE ERROR

IF A FILER TRANSMITS A CARGO RELEASE DATA TRANSACTION (APPLICATION HI), AND ALSO ELECTS TO REPORT VALUES AT THE LINE ITEM LEVEL (H5 REC, POS 45-54), THE TOTAL OF ALL VALUES IN THE H5 RECORD MUST EQUAL THE AMOUNT SHOWN AS THE TOTAL ENTRY VALUE (H2 REC, POS 29-38). THE TOTAL DOES NOT AGREE, THIS ERROR MESSAGE WILL BE GENERATED.

HL7:	ENTRY NOT QUAL. FOR HLD STATUS

THE ENTRY DOES NOT QUALIFY FOR HOLDING CODE STATUS AT THIS TIME.

17I:	UNKNOWN APPLICATION CODE

THE ABI APPLICATION CODE ENTERED ON THE 'B' RECORD WAS NOT FOUND IN THE APPLICATION CODE FILE. ACTION: CORRECT THE CODE ENTERED ON THE 'B' RECORD AND RESTART THE APPLICATION.

VKZ:	HLT: LEN REQUIRED W/ OPTIONAL POS

A LENGTH VALUED MUST BE SPECIFIED FOR THE OPTIMAL POSITION/LENGTH PARAMETER WHEN A POSITION IS SPECIFIED.

14G:	THIS TARIFF NBR ALREADY ENTERED

THIS ERROR MESSAGE OCCURS IN A SET PROVISION SITUATION WHEN THE TARIFF NUMBER SENT IN THE 70 RECORD IS THE SAME AS THE SET PROVISION TARIFF NUMBER SENT IN THE 50 RECORD. THE TARIFF NUMBER IN THE 70 RECORD MUST BE DIFFERENT AND MUST BE THE NUMBER THAT ESTABLISHES THE CORRECT RATE OF DUTY FOR THE SET. THIS ERROR MESSAGE CAN ALSO OCCUR IN NON SET PROVISION LINES IF THE FILER USES THE SAME TARIFF NUMBER IN THE 50 AND 70 RECORDS OR IN THE 70 AND 80 RECORDS.

 Next 10 >>Showing results 1 to 25 of 1405