ABI Error Message

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.

VN2:	CERT MFGR NBR NOT ON FILE

THIS DRAWBACK MODULE ERROR MESSAGE MEANS THAT THE CM (CERT MFGR) NUMBER FORMAT IS VALID, BUT THE CM NUMBER DOES NOT EXIST IN ACS.

AER:	ERROR IN A 32 REC; RLSE 5

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 FIFTH RELEASE IN THE 32 RECORD.

17K:	INVALID APPLICATION CODE

THE APPLICATION CODE FOUND ON THE 'B' RECORD WAS LOCATED IN THE APPLICATION CODE FILE, HOWEVER, THE CODE IS NUMERIC AND RESERVED FOR SPECIAL USE.

VBE:	FW 3-177: INVLD SPECIE NAME GENUS

IF XXXX IS USED FOR THE SPECIES CODE IN REC FW01, POS 5 - 8, THE SCIENTIFIC NAME GENUS (REC FW01, POS 9-26) IS MANDATORY. IF THE SPECIES CODE IS OTHER THAN XXXX, THE FIELD FOR THE SCIENTIFIC NAME GENUS MUST BE BLANK. THE LANGUAGE IN THE ERROR MESSAGE VBE IS INACCURATE. IT SHOULD READ "INVLD SCIENT NAME GENUS". (NOTE: WHEN XXXX IS USED FOR THE SPECIES CODE, THE COMMON NAME SPECIFIC (RECORD FW02, POS 5-22) AND THE COMMON NAME GENERAL (RECORD FW02, POS 23-40) ARE ALSO MANDATORY.

VHA:	FD 701:AFFRM/COMPLNCE REQ ON FD05

IF THE FILER REPORTS FDA AFFIRMATION OF COMPLIANCE DATA IN THE FD01 RECORD (POS 20-22), AND THERE IS AT LEAST ONE MORE AFFIRMATION OF COMPLIANCE CODE TO REPORT, THE FD05 RECORD MUST BE TRANSMITTED. HOWEVER, THIS RECORD CANNOT BE BLANK. IF THE SECOND OR SUCCEEDING AFFIRMATION OF COMPLIANCE CODES/QUALIFIERS ARE NOT INCLUDED IN THE FD05 RECORD, THIS ERROR MESSAGE WILL BE GENERATED.

WT1:	R89 RECS NOT PROPERLY UTILIZED

EACH R89 RECORD CAN ACCOMMODATE 3 FEE CLASS CODES. THIS IS AN ACS PERFORMANCE REQUIREMENT, I.E. SPACE ALLOCATION MUST BE OPTIMIZED. EXAMPLE WT1 ERROR: IF 2 R89 RECORDS ARE SUBMITTED AND THE FIRST CONTAINS TWO FEE CLASS CODES AND THE SECOND R89 CONTAINS 1 FEE CLASS CODE, ALL OF THE FEE CLASS CODES SHOULD HAVE BEEN SUBMITTED ON ONE R89 RECORD.

05D:	INDICATE PAIRED CITIES WITH 'X'

A CHARACTER WAS ENTERED IN THE PAIRED CITIES INDICATOR BUT IT WAS NOT AN 'X'. X' IS THE ONLY VALID CHARACTER FOR INDICATING PAIRED CITIES. IF THIS IS NOT A PAIRED CITIES ENTRY, THE PAIRED INDICATOR SHOULD REMAIN A SPACE.

VEP:	ENTRY HAS NO FDA DATA

THIS MESSAGE OCCURS WHEN FDA ATTEMPTS TO SEND PROCESSING RESULTS ON AN ENTRY THAT HAS BEEN DELETED FROM SELECTIVITY BY CUSTOMS AFTER THE INFORMATION HAD BEEN TRANSMITTED TO FDA VIA THE KI TRANSACTION BUT BEFORE THE DELETE STATUS WAS SENT TO FDA.

4LV:	CN SILK - VISA NBR NOT ALLOWED

SILK ARTICLES EXPORTED FROM CHINA (CN) DO NOT REQUIRE A VISAED DOCUMENT SINCE 1993. IF AN ABI TRANSACTION W/ HARMONIZED TARIFF NUMBERS FOR SILK ARTICLES IN CATEGORY 733 - 759 IS TRANSMITTED, THE ENTRY WILL BE REJECTED WITH ERROR MSG NBR 4LV. *SILK FROM CHINA HAS NOT REQUIRED A VISAED DOCUMENT (VISA) SINCE 1993. **THIS EDITING WILL PREVENT THE USE OF DUMMY VISA NBRS ABOVE DATA ADDED BY HQ QUOTA. ENTRIES USING THESE CATEGORIES MAY BE FILED USING ENTRY TYPE 01, AS WELL AS 02.

Q41:	STMT PAID, TO DELETE, NEGATE COLL

THIS MESSAGE OCCURS WHEN AN ABI FILER ATTEMPTS TO REMOVE AN ENTRY FROM STATEMENT (APPLICATION HP) AND THE STATEMENT HAS ALREADY HAD AN ACH AUTHORIZATION TRANSMITTED TO ABI (APPLICATION QN). THE SOLUTION IS FOR THE FILER TO CONTACT A CLIENT  REP WHO CAN PERFORM THE PAYMENT AUTHORIZATION DELETE FUNCTION, IF THE PAYMENT AUTHORIZATION WAS TRANSMITTED ON THE SAME DAY AS THE REQUEST IS MADE.

EJI:	NO. OF SHIPPING/PACKING UNITS REQ

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). THE NUMBER OF EXTERIOR SHIPPING UNITS MUST BE REPORTED (FOR CONTAINERIZED CARGO) IN THE C5 REC, POS 4-18.IF THIS FIELD IS BLANK OR REFLECTS A ZERO QUANTITY, THIS ERROR MESSAGE WILL BE GENERATED. THIS MESSAGE ALSO APPLIES TO THE C47 RECORD.

BE3:	BLANK CANADIAN EXCISE NBR INVALID

IF AN EI APPLICATION INCLUDES A '57' RECORD, THE CANADIAN EXCISE NUMBER ON MUST BE NON-BLANK.

AFZ:	HOUSE/SUBHOUSE REQUIRES MASTER

A HOUSE BILL OF LADING OR HOUSE/SUBHOUSE BILL OF LADING CANNOT BE SENT WITHOUT A MASTER BILL OF LADING IN AN ENTRY SUMMARY TRANSACTION (APPLICATION EI).

17J:	MORE THAN ONE APPLICATION CODE

MORE THAN ONE APPLICATION (B TO Y) TYPE WAS SUBMITTED WITHIN THE Z SET.

APJ:	AFR QUES MISSING/INCOMPLETE

AN APPLICATION FOR FURTHER REVIEW, INDICATED BY 'R', APPLIES ONLY TO 514 PROTESTS, AND MUST BE REQUESTED DURING THE FILING AND AMENDMENT PERIOD, EITHER AT INITIAL FILING OR BY AN AMENDMENT FILING. EITHER THE FILING IS NOT 514 PROTEST, OR THE FILING AND AMENDMENT PERIOD HAS EXPIRED.

95I:	RECON REQUIRES CONTINUOUS BOND

RECONCILIATION ENTRIES REQUIRE THAT A CONTINUOUS BOND BE ON FILE FOR THE IMPORTER IDENTIFIER IN THE R10 REC, POS 20-31. NOTE: IF THIS MESSAGE OCCURS IN CONJUNCTION WITH ERROR 8PN, IT MAY NOT BE CORRECT IN RELATION TO THE ENTRY IN QUESTION. SEE ERRS 8PN FOR MORE INFORMATION. NOTE: THIS MESSAGE, AS WELL AS ERROR BRIM, WILL ALSO OCCUR IF ERROR 0AA (ENTRY IN R20 RECORD NOT IN ACS) IS GENERATED.

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.

LU4:	INVALID LUMBER PERMIT NUMBER

IF THE ABI FILER REPORTS A LUMBER PERMIT TYPE (40 REC, POS 70-72), A NINE- POSITION NUMERIC LUMBER PERMIT NUMBER IS REQUIRED IN THE 51 REC, POS 57-65. IF THE PERMIT NUMBER IS OMITTED, THIS ERROR MESSAGE WILL BE GENERATED.

96B:	STMT/RECON CALENDAR ERROR

INVALID RDP CALENDAR. A SYSTEM CALENDAR DOES NOT EXIST FOR THE ENTRY DATE, SCHEDULED PAY DATE, DATE OF EXPORT, CALCULATION OF A FUTURE RECON DATE, ETC. IF THIS MESSAGE IS GENERATED FOR AN IMPORT ENTRY BEING FLAGGED FOR RECON, IT INDICATES THAT THE CALENDAR FOR THE YEAR IN WHICH THE RECON ENTRY WOULD BE DUE HAS NOT YET BEEN ENTERED INTO ACS (FOR A NON-NAFTA RECON FLAGGED IMPORT ENTRY FILED IN OCTOBER 2000, THE RECON ENTRY ITSELF WOULD BE DUE IN THE YEAR 2002. IF THE 2002 CALENDAR IS NOT LOADED INTO ACS WHEN THE IMPORT ENTRY IS TRANSMITTED TO ABI, THIS MESSAGE WOULD BE GENERATED.)

8VE:	DATA CONTAINED IN FUTURE FIELD

THIS ERROR MESSAGE IS GENERATED IN RESPONSE TO A BILL OF LADING UPDATE TRANSMISSION (APPLICATION LN). THE FILER HAS ENTERED DATA IN ONE OF THE TWO FIELDS RESERVED FOR THE SCAC (STANDARD CARRIER ALPHA CODE) OF THE ISSUER OF THE HOUSE BILL NUMBER (L3 REC, POS 32-35) OR THE SUBHOUSE BILL NUMBER (L3 REC, POS 48-51). THESE ARE FUTURE USE FIELDS.

14I:	QUANTITY/UNIT OF MEASURE MISMATCH

MISMATCH CONDITION BETWEEN ENTERED QUANTITY AND ENTERED UNIT OF MEASURE HAS BEEN DISCOVERED.

VN5:	DESCRIPTION MUST BE > 1 CHARACTER

WHILE DESCRIPTION FIELD ARE CURRENTLY OPTIONAL DATA IN THE DRAWBACK MODULE, IF A FILER DOES INPUT DESCRIPTIONS, THEY MUST BE MORE THAN A SINGLE CHARACTER.

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.

VKA:	HLT: TABLE NAME REQUIRED

TABLE NAME AND SEARCH NUMBER ARE BOTH REQUIRED TO CONSTRUCT A VALID TABLE LOCATE/INQUIRY DEFINITION.

 Next 10 >>Showing results 1 to 25 of 1405