ABI Error Message

66A:	IMPORTER IS INACTIVE

THIS MESSAGE IS GENERATED IN RESPONSE TO A CARGO RELEASE DATA INPUT TRANS- ACTION (APPLICATION HI). IF THE IMPORTER NUMBER (H1 REC, POS 20-31) IS IN 'INACTIVE' STATUS ON THE IMPORTER DATABASE, THIS ERROR MESSAGE WILL BE GENERATED. TO REACTIVATE, THE FILER MUST SEND AN "ADD CF5106" TRANSACTION WITH THE IMPORTER'S FULL NAME AND ADDRESS INFORMATION.

AE2:	PO BOX NOT ALLOWED IN 2ND ADDRESS

THIS MESSAGE IS GENERATED IN RESPONSE TO AN "ADD 5106" INPUT TRANSACTION, APPLICATION IDENTIFIER TI. FOR COMPANIES WITH FOREIGN ADDRESSES, ONLY ONE LINE OF ADDRESS DATA IS PERMITTED AND A POST OFFICE BOX IS NOT PERMITTED IN THE ADDRESS LINE. THIS MESSAGE WILL BE GENERATED IF THE T2 OR TB RECORD CONTAINS A POST OFFICE BOX.

AAR:	CASE REVOKED

THIS MESSAGE OCCURS WHEN A FILER SENDS ANTI-DUMPING (ADD) OR COUNTERVAILING (CVD) DATA IN ABI REC 60 (CATAIR, PAGE ENS-54) AND THE CASE NUMBER REPORTED (POS 13-22 OR 23-32) HAS BEEN REVOKED. IF THE CASE HAS BEEN REVOKED AND NEED NOT BE REPORTED.

VBA:	BRANCH CODE INVALID W/O STMT IND

REMOVE BRANCH CODE FOR 20REC WHEN PAYMENT INDICATOR IS NOT EQUAL TO 2, 3 OR 5 IN ADDITION, A VALID PAY DATE MUST BE TRANSMITTED IN THE 30 REC, POS 54-59, WHENEVER A PAYMENT TYPE INDICATOR IS TRANSMITTED IN POS 53. IF THE PAYMENT TYPE INDICATOR IS PRESENT, BUT THE PAYMENT DUE DATE IS BLANK OR ZEROES, AND A BRANCH CODE IS TRANSMITTED IN THE 20 REC, THIS ERROR MESSAGE WILL RESULT.

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

99K:	AG LIC REQUIRES FORMAL QUOTA ENT

AGRICULTURE LICENSE REQUIRED FORMAL QUOTA ENTRY TO BE FILED.

4KN:	TARIFF (1) INVALID FOR COUNTRY

ONE POSSIBLE REASON FOR THIS ERROR MESSAGE IS WHEN A NON-CBI COUNTRY IS USE THE COUNTRY OF ORIGIN (REC 50, POS 6-7) FOR HS NUMBER 9802008040 (REC 50,POS 4-13) SINCE THIS HS NUMBER IS RESTRICTED TO CBI COUNTRIES.

VNH:	FD 701: BASE UNIT MUST BE LAST

IN THE FDA INTERFACE, UP TO SIX QUANTITIES AND UNITS OF MEASURE (UOM) CAN BE TRANSMITTED. FIVE QUANTITIES/UOM CAN BE SENT IN REC FD02, POS 5-18, 19-32, 33-46, 47-60 AND 61-74 (CATAIR, PAGE OGA-30). THE SIXTH, IF APPLICABLE, IS SENT IN REC FD04, POS 5-18 (CATAIR, PAGE OGA-35). IF QUANTITIES/UOM'S ARE SENT THEN AT LEAST ONE OF THEM MUST BE A "BASE UNIT" AND IF MORE THAN ONE IS SENT THE BASE UNIT MUST BE IN THE LAST POSITION. IF, FOR EXAMPLE, THREE QUANTITIES/UOM'S ARE SENT THE BASE QUANTITY MUST BE IN THE "UNIT 3 QUANTITY AND MEASURE BLOCK (REC FD01, POS 33-46). IF ONLY ONE QUANTITY/UOM IS SENT IT MUST BE A BASE UNIT AND SENT IN THE UNIT 1 QUANTITY AND MEASURE BLOCK (REC FD01, POS 1-18). FDA BASE UNITS ARE SHOWN IN THE CATAIR, PAGES OGA-31.

AR5:	REFUND PARTY DATA REJECTED

IF A REFUND C/O PARTY WAS NOT NAMED AT THE TIME OF INITIAL FILING, AN AMEND- MENT QJ OR ADDENDA RJ TRANSACTION CAN BE SUBMITTED TO ADD THE REFUND C/O PARTY TO THE PROTEST RECORD. WHEN A REFUND C/O PARTY IS ALREADY LISTED ON THE PROTEST RECORD, THE FILER CAN CHANGE IT USING THE AMEND OR ADDENDA TRANSACTION. IT IS MANDATORY THAT THE FILER INDICATE THE TYPE OF ACTION HE INTENDS TO PERFORM, 'A' = ADD REFUND C/O WHEREAS 'R' = REPLACE. THIS IS A 'HIGH LEVEL' ERROR MESSAGE RELATING TO SPECIFIC ERRORS IN THE P40 RECORD WHICH SHOULD ALSO BE INDICATED BY THE PRESENCE OF ONE OR MORE ERROR MESSAGES. A COMMON EXAMPLE WOULD BE "ARW: REFUND PARTY NBR NOT ON FILE," WHICH COULD RESULT FROM THE USE OF IMPROPER FORMAT OF THE IRS, SOC, OR USCS NUMBER.

4K7:	CERTIFICATE NUMBER INVALID

THIS MESSAGE OCCURS WHEN A COTTON CERTIFICATE NUMBER IS SENT IN POSITIONS 48-56 OF THE 51 RECORD AND THERE IS NO COTTON FEE CODE (056) INDICATOR IN THE HARMONIZED RECORD. IT WILL ALSO OCCUR WHEN THERE IS A DUAL TARIFF NUMBER (E.G. CHAPTER 99) AND THE TARIFF NUMBER IN THE 70 RECORD DOES NOT HAVE A COTTON FEE CODE. SENDING A COTTON CERTIFICATE NUMBER WITH A NON-NUMERIC OR ONE THAT IS LESS THAN THAN NINE NUMERICS ALSO GENERATES THIS MESSAGE.

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.

1I6:	DUTY COMP DATE > SCH PAY DATE

THIS ERROR MESSAGE WILL RESULT IF THE DATE TRANSMITTED BY THE ABI FILER IN SUMMARY INPUT IS GREATER (LATER) THAN THE DATE REPRESENTING THE SCHEDULED PAYMENT DUE DATE. THE MOST COMMON EXAMPLE OF THIS CONDITION IS WHEN A FILER TRANSMITS AN "ESTIMATED ENTRY  DATE" (10 REC, POS 50-55) THAT IS LATER THAN THE PAYMENT DUE DATE (30 REC, POS 54-59).

EI1:	ARTICLE A NEEDED FOR ARTICLE B

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). THE C31 RECORD ENABLES FILERS TO REPORT SPECIFIC DATA ON ITEM NUMBERS FOR AN INVOICE LINE. POS 8-42 ARE USED TO PROVIDE AN IDENTIFICATION NUMBER FOR THE ITEM ON THE INVOICE LINE (PART NUMBER, CATALOG NUMBER, ETC). A FURTHER DEFINITION (BUYER'S PART NUMBER, ETC) IS PERMITTED IN POS 43-77. THESE TWO FIELDS ARE IDENTIFED AS "ITEM A" AND "ITEM B". IF DATA APPEARS IN THE "ITEM B" FIELD, DATA MUST ALSO APPEAR IN THE "ITEM A" FIELD. IF NOT, THIS ERROR MESSAGE WILL BE GENERATE.

8WP:	INTENSIVE EXAM DATE EXCEEDED

THIS MESSAGE WILL USUALLY BE GENERATED IN RESPONSE TO A BILL OF LADING UPDATE TRANSACTION (APPLICATION LN). FILERS ARE PERMITTED, WITHIN SET LIMITS, TO CHANGE THE ESTIMATED ARRIVAL DATE CREATED BY THEIR INITIAL CARGO RELEASE INPUT. (SEE ERROR MESSAGE 8WQ, 8WK, AND 8WO). ANOTHER RESTRICTION IS THAT THE ESTIMATED ARRIVAL DATE CANNOT EXCEED THE DATE OF ANY INTENSIVE EXAMINATION DATE THAT HAS BEEN ENTERED ON THE SSAI RECORD. IF THE FILER'S LN INPUT CONTAINS SUCH A DATE, THIS ERROR MESSAGE WILL BE GENERATED.

8VB:	COMPUTER SITE INVALID FOR BLOCK

THIS MESSAGE IS GENERATED IN RESPONSE TO A TIB EXTENSION REQUEST (APPLICATION XN), ALTHOUGH IT MAY APPLY TO OTHER APPLICATIONS, AS WELL. IN THE INPUT RECORDS, THE XA RECORD CONTAINS A FIELD FOR THE DDPP OF THE SUMMARY FOR WHICH AN EXTENSION IS BEING REQUESTED. (POS 3-6). IF THAT FIELD IS LEFT BLANK, THIS MESSAGE IS GENERATED. NOTE: THIS MESSAGE WILL ALSO OCCUR IF THE PORT CODE FIELD IN THE XA RECORD IS NOT IDENTICAL TO THE PORT OF ENTRY FOR THE ENTRY BEING EXTENDED.

8VZ:	BILL DATA UPDATED AS REQUESTED

THIS MESSAGE IS AN "ERROR FREE" NOTIFICATION TO THE FILER THAT A BILL OF LADING UPDATE 'LN' TRANSACTION WAS SUCCESSFUL. A SUCCESSFUL BOL UPDATE MEANS THAT THE UPDATE INFORMATION HAS BEEN PASSED TO THE AMS CARRIER AND THAT THE SELECTIVITY FILE HAS BEEN UPDATED.

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.

RBZ:	INVALID RECONCILIATION ISSUE CODE

EITHER THE FILER HAS NOT PROVIDED AN ISSUE CODE IN THE R10 RECORD FOR A RECONCILIATION SUMMARY, OR THE ISSUE CODE GIVEN IS INVALID / DOES NOT EXIST.

FDL:	NO FDA RECORD ON FILE FOR ENTRY

THIS MESSAGE OCCURS IN A FDA INTERFACE SITUATION WHEN A FILER ATTEMPTS TO SEND AN OTHER GOVERNMENT AGENCY CORRECTION ('CP') TRANSACTION FOR AN ENTRY THAT WAS NOT ORIGINALLY A FDA INTERFACE ENTRY. TYPICALLY IT INVOLVES A FILER SENDING AN ENTRY WITH NO REGULATED FDA TARIFF NUMBERS ON IT THEN ATTEMPTING TO SEND A 'CP' WITH THE FDA REGULATED TARIFF NUMBER(S). THE ONLY SOLUTION IS FOR CUSTOMS TO DO A PEN AND INK CHANGE TO THE ENTRY OR TO HAVE CUSTOMS DELETE THE ENTRY AND THE FILER THEN RESENDS THE CORRECT INFORMATION.

VBN:	FW 3-177: INVLD WILDLIFE DSCRIPTN

THE WILDLIFE DESCRIPTION (REC FW03, POS 24-27) MUST CONSIST OF FOUR ALPHA CHARACTERS AND MUST MATCH ONE OF THE WILDLIFE DESCRIPTION CODES LISTED IN THE CATAIR ON PAGE OGA-21.

AS5:	WRN: ENTRY PORT NOT IN DISTRICT

THE FIRST TWO DIGITS OF THE DISTRICT PORT CODE OF THE ENTRY MUST MATCH THE FIRST TWO DIGITS OF THE DISTRICT PORT CODE OF THE PROTEST FILING LOCATION. WITH FEW EXCEPTIONS, THE PROTEST OR PETITION MUST BE FILED WITHIN THE BOUNDOF THE OLD DISTRICTS. ENTRIES FOR CHICAGO (3901) CANNOT BE PROTESTED IN LOS ANGELES (2704), BUT DENVER ENTRIES CAN BE PROTESTED IN SAN FRANCISCO. THE OPERATIONAL RULES FOR ENTRIES PROCESSED UNDER TARIFF SHARING DO NOT ABIDE BY THIS AND THIS WARNING CONDITION SHOULD BE IGNORED.

915:	IT DATE/DATE OF IMP INCONSISTENT

THE DATE TRANSMITTED FOR THE OPENING OF THE IN-TRANSIT (I.T.) ACTION (WHICH MOVES THE FREIGHT FROM THE PORT OF ARRIVAL TO A SECOND U.S. PORT WHERE THE SHIPMENT WILL BE ENTERED) MUST BE ON OR AFTER THE DATE OF IMPORT OF THE FREIGHT INTO THE UNITED STATES. COMPARE THE I.T. DATE FROM THE SUMMARY TRANSMISSION, REC 22, POS 64-69, TO THE IMPORT DATE IN REC 20, POS 34-39.

BR9:	PAY AMOUNTS MISMATCH (R17:R90)

THE PAYMENT AMOUNTS OF DUTY, TAX, OR FEES MUST EQUAL THE TOTAL RECON DUTY, OR FEES FROM THE 'R90' MINUS THE ORIGINAL DUTY, TAX, FEES, RESPECTIVELY, FOR THE 'R90' RECORD. IF THE CALCULATION YIELDS ZERO OR A NEGATIVE, THE CORRESPONDING 'R17' AMOUNT SHOULD BE ZERO.

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.

AEO:	ERROR IN A32 REC; RLSE 2

THIS MESSAGE FOLLOWS A MORE SPECIFIC ERROR MESSAGE (I.E. 1F5 RELEASE NOT ON FILE) IN A CONSOLIDATED ENTRY SUMMARY TRANSACTION. IT NOTIFIES THE FILER THAT THE ERROR IS IN THE SECOND RELEASE IN THE 32 RECORD.

 Next 10 >>Showing results 1 to 25 of 1405