ABI Error Message

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.

14K:	ENTRY DATE RESTRICTION

THE ENTERED DATE IS NOT WITHIN THE BEGINNING AND ENDING DATE BOUNDS AS SHOWN IN THE TARIFF FILE.

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.

AAY:	WARNING - CASES NOT RELATED

THIS MESSAGE IS GENERATED AS A RESULT OF AN ENTRY SUMMARY TRANSACTION. IF THE FILER REPORTS BOTH ANTI-DUMPING AND COUNTERVAILING DUTY CASE NUMBER IN THE 60 RECORD, THESE MUST BE RELATED. IF EITHER CASE DOES NOT POINT TO THE OTHER CASE, THIS MESSAGE WILL RESULT.

VBJ:	FW 3-177: QUANTITY MUST BE > 0

THE FISH AND WILDLIFE QUANTITY (REC FW03, POS 5-16) IS MANDATORY EVEN IF IDENTICAL TO THE QUANTITY ASSOCIATED WITH THE TARIFF NUMBER. THIS FIELD CANNOT BE SPACE FILLED OR ZERO FILLED.

0DJ:	PRESENT DATE < ARRIVAL DATE

THIS MESSAGE IS GENERATED IN RESPONSE TO A CARGO RELEASE DATA INPUT TRANSACTION (APPLICATION HI). IF THE DATE OF PRESENTATION IS ELECTED AS THE ENTRY DATE, A "P" IS TRANSMITTED IN POS 23 OF THE H2 RECORD. SIMULTANEOUSLY, THE FILER MUST SEND A "PRESENTATION DATE" IN POS 50-55 OF THE H1 RECORD. THIS DATE CANNOT BE PRIOR TO THE ESTIMATED ARRIVAL DATE, TRANSMITTED IN POS 34-39 OF THE H1 RECORD. IF IT IS, THIS ERROR WILL BE GENERATED.

VNP:	D11 RECORD MUST CONTAIN DATA

THIS ERROR MESSAGE COULD BE THE RESULT OF A DRAWBACK DISKETTE OR ABI PROBLEM. 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 DISKETTE HAS NO DATA, THE PC PROGRAM SHOULD STOP IT BEFORE TRANSMISSION; HOWEVER, THERE MAY HAVE BEEN DATA THERE, BUT IT WAS BAD DATA.

AE5:	ENTRY DATE EXCEEDS CURRENT DATE

THIS ERROR MESSAGE OCCURS IN THE ENTRY DATE UPDATE 'DN' TRANSACTION WHEN THE REVISED ENTRY DATE SENT IN POSITIONS 19-24 OF THE DN01 RECORD EXCEEDS THE CURRENT DATE (PAGE ENU-2, CATAIR).

EJ7:	CNTRY INCONSISTENT W MANUF/SUB CD

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). THE ISO COUNTRY CODE FOR THE PARTY IDENTIFIED IN THE C08 RECORD IS TRANSMITTED IN THE C11 REC, POS 57-58. IF THE ISO CODE IS "CA", AND THE PARTY TYPE CODE TRANSMITTED IN THE C08 RECORD IS EITHER "SU", "II", OR "MF", A VALID MID MUST BE TRANSMITTED (STARTING WITH ONE OF THE 10 VALID PROVINCE CODES FOR CANADIAN ORIGIN CARGO). CONVERSELY, IF THE PARTY CODE IS "SU", "II", OR "MF", AND THE MID STARTS WITH "XN" (WHERE "N" EQUALS ONE OF THE TEN PROVINCE CODE IDENTIFIERS), THE ISO COUNTRY CODE TRANSMITTED IN THE C11 RECORD MUST BE "CA".

"27B:

CENSUS QTY1/QTY2 (TARIFF 1)

THIS MESSAGE IS AN ABI REPLY TO AN ENTRY SUMMARY INPUT TRANSACTION. IT INDICATES THAT THE RATIO OF THE FIRST QUANTITY TO THE SECOND QUANTITY FOR THE LINE IN QUESTION, FOR THE FIRST TARIFF REPORTED (OR THE ONLY ONE IF THE LINE ONLY CALLS FOR ONE TARIFF NUMBER) IS OUTSIDE THE LIMITS THAT HAVE BEEN RECORDED BY CENSUS FROM PREVIOUS IMPORTATIONS. IF THE FILER REVIEWS ITS DATA AND FINDS THAT BOTH QUANTITIES ARE CORRECT AS REPORTED, THE FILER DOES NOT NEED TO MAKE ANY ABI CHANGES, BUT SHOULD ALERT THE ENTRY TEAM THAT THE DATA IS CORRECT.

VNW:	IMPORT MUST BE IN CUSTOMS STATUS

THIS DRAWBACK MODULE ERROR MESSAGE MEANS THAT THE IMPORT ENTRY IS STILL IN ABI STATUS AND HAS NOT BEEN PROCESSED BY CUSTOMS.

2A7:	CARGO RELEASE DATA NOT ON FILE

THIS MESSAGE GENERALLY INDICATES A PROBLEM IN THE CREATION OF CARGO SELECTIVITY RECORDS FROM FILER'S INPUT. EXAMPLE: A FILER SENT IN SEVERAL ENTRIES USING BORDER CARGO RELEASE (APPLICATION HN). BEFORE ABI COULD COMPLETE THE PROCESSING OF THE ENTRIES, THE FILER'S SYSTEM SENT THE SAME ENTRIES AGAIN (WITHIN 12 SECONDS OF THE FIRST TRANSMISSION). THIS DUPLICATION CAUSED DATABASE (DB) ERRORS ON THOSE ENTRIES THAT WERE BEING PROCESSED AT THE INSTANT THE SECOND ITERATION OF THE SAME ENTRY NUMBER REACHED THE MAINFRAME. THE SECOND SET OF ENTRIES HAD PROCESSING DONE, BUT NO ON-LINE RECORDS WERE CREATED. THE ERROR MESSAGE ABOVE WAS CREATED AND ATTACHED TO THE SECOND SET OF ENTRY NUMBERS. THE SOLUTION, IN ALMOST ALL CASES, IS FOR THE FILER TO TRANSMIT ONLY ONCE AND TO WAIT FOR RESULTS BEFORE RE-SUBMITTING DATA FOR THE SAME ENTRY NUMBER.

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.

VGS:	FD 701: DMNS INV;PREV DMNS=0'S

THIS ERROR MESSAGE OCCURS WHEN A FILER HAS TRANSMITTED A CONTAINER DIMENSION IN THE "CONTAINER DIMENSION #2" FIELD (REC FD03, POS 69-72) OR "CONTAINER DIMENSION #3" FIELD (REC FD03, POS 73-76) AND THE PREVIOUS CONTAINER DIMENSION FIELD WAS ZERO FILLED. FOR EXAMPLE, IF 0511 WAS TRANSMITTED IN THE "CONTAINER DIMENSION #2" FIELD AND 0000 IN THE "CONTAINER DIMENSION #1" FIELD, THIS REJECT WOULD RESULT.

58H:	QUOTA NOT PERMITTED ON STATEMENTS

OT PERMITTED ON STATEMENTS

4DA:	IMPORTER NOT ON FILE

THE IMPORTER NUMBER IS IN CORRECT FORMAT, BUT THE NUMBER IS NOT IN THE IMPORTER FILE.

8WA:	NO ENTRY EXISTS OR ENTRY CLOSED

THIS MESSAGE IS GENERATED IN RESPONSE TO A BILL OF LADING UPDATE TRASNMISSION. IF THE FILER ATTEMPTS TO SEND APPLICATION LN AGAINST AN ENTRY NUMBER FOR WHICH NO PROVISIONAL SELECTIVITY STATUS HAS BEEN ISSUED BY ABI, THIS ERROR MESSAGE WILL BE GENERATED. MOST OF THE TIME, ERROR MESSAGE 8WB, ENTRY BELONGS TO ANOTHER DD/PP, WILL ALSO BE GENERATED. **NOTE** - THIS MESSAGE CAN ALSO APPLY TO OTHER APPLICATIONS WHICH INVOLVE AN ENTRY NUMBER THAT IS NOT RESIDENT ON THE ENTRY OR SELECTIVITY DATABASES. **NOTE** THIS ERROR MESSAGE ALSO APPLIES TO A FILER'S ATTEMPT TO SEND A TIB EXTENSION REQUEST AFTER THE DATE THAT THE TIB ENTRY SHOWS AS 'CLOSED' PER THE ENTRY RECORD.

B15:	INSUFFICIENT DATA IN FIRM OR CITY

INPUT FIRM NAME OR CITY NAME FIELD DOES NOT CONTAIN ENOUGH CHARACTERS TO CREATE A MANUFACTURER ID. IN ABI, THIS MESSAGE CAN OCCUR IF THE FILER TRANSMITS LOWER CASE LETTERS IN THE FIRM NAME OR CITY NAME FIELD, BUT THE FIRST LETTER OF THE FIRM NAME AND CITY NAME IS A CAPITAL LETTER.

P11:	FIELD MUST BE NUMERIC

THIS MESSAGE MEANS THAT A NON-NUMERIC CHARACTER WAS PLACED IN A FIELD THAT IS DEFINED AS NUMERIC. THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED DRAWBACK INPUT.

95D:	21 REC SENT; NOT ALLOWED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN ENTRY SUMMARY INPUT TRANSACTION (APPLICATION EI). THE 21 RECORD TO REPORT THE BOND AMOUNT AND THE PRODUCER IDENTIFICATION NUMBER IS ONLY PERMITTED WHEN A SINGLE TRANSACTION BOND (BOND TYPE 9) IS TRANSMITTED. IF ANY OTHER TYPE OF BOND INDICATOR IS SENT IN THE 10 REC, POS 49, THIS ERROR MESSAGE WILL RESULT.

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.

VOU:	REMOTE INDICATOR INVALID

THIS MESSAGE OCCURS WHEN A REMOTE INDICATOR OF OTHER THAN '1' OR 'BLANK' IS SENT IN THE 'B' RECORD, POSITION 56.

ADO:	RELEASE ALREADY CONSOLIDATED

THIS MESSAGE OCCURS IN A CONSOLIDATED ENTRY SUMMARY TRANSACTION WHEN A RELEASE ENTRY NUMBER TRANSMITTED IN THE A32 RECORD IS AN ENTRY THAT HAS BEEN CONSOLIDATED ON ANOTHER ENTRY SUMMARY NUMBER. THIS MESSAGE WILL ALSO OCCUR ON A NON-CONSOLIDATED SUMMARY TRANSMISSION IF THE ENTRY NUMBER HAS BEEN LISTED IN A 32 RECORD AS PART OF A CONSOLIDATED SUMMARY TRANSMISSION PREVIOUSLY SENT BY THE FILER.

364:	CHECK DIGIT INVALID OR MISSING

ENTRY NUMBER ASSIGNMENT: YOU MAY NOT UPDATE THE ENTRY NUMBER ASSIGNMENT FILE FOR THIS DISTRICT. THIS DISTRICT IS NOT ONE OF YOUR ASSIGNED LOCATIONS. CHECK THE CHECK DIGIT IN THE TSUS/HSUS NUMBER

RBK:	RECON IMPT ENT CANNOT = RECON SUM

THE FILER HAS ATTEMPTED TO GIVE AN IMPORT ENTRY WITH THE SAME ENTRY NUMBER AS THEY ARE USING FOR THE RECONCILIATION SUMMARY.

 Next 10 >>Showing results 1 to 25 of 1405