ABI Error Message

DKI:	NOT NAFTA CLAIM - D50 NOT ALLOWED

IN THE DRAWBACK MODULE FOR THE DISKETTE, THE NAFTA INDICATOR WAS SET TO 'N' IN THE 'CH' HEADER RECORD, OR FOR ABI IT WAS SET TO SPACE FILL IN THE 'D50' RECORD. EITHER WOULD INDICATE THAT THIS CLAIM IS NOT A NAFTA CLAIM SUBJECT TO THE "LESSER OF" RULE. ACCORDINGLY, WE DO NOT WANT THE CANADIAN IMPORT ENTRY DATA.

Q05:	'QT' AMOUNT PAID INVALID

THE 'QT' RECORD HAS SPACES, OR OTHER NON-NUMERIC DATA IN THE PAYMENT AMOUNT FIELD POSITIONS 25-34. ZERO DOLLARS IS A VALID AMOUNT THAT MAY BE PAID VIA ACH. (THE TRANSMITTING OF ZERO DOLLARS IS AN INDICATOR BY THE FILER THAT THE STATEMENT IS CORRECT IN THAT ALL ENTRIES HAVE NO MONEY DUE. THE TRANSMISSION IS NECESSARY, HOWEVER, IN ORDER TO "PROCESS/PAY" THE STATEMENT AND ALLOW THE GENERATION OF THE FINAL STATEMENT).

" 4GE:

NO QUOTA RECORD FOR THIS TARIFF

THE TARIFF, AS INPUT, HAS NO QUOTA RECORD ON THE QUOTA FILE.

AE4:	WARNING! ENTRY DATE < EXPORT DATE

THIS WARNING MESSAGE OCCURS IN THE "REVISED FILER DATE" (DN) TRANSACTION WHEN A FILER TRANSMITS AN ENTRY DATE THAT IS EARLIER THAN THE EXPORT DATE THAT RESIDES IN THE LINE ITEM FILE OF THE ENTRY SUMMARY RECORD.

BRB:	INTERES AMOUNT MISMATCH (R17:R91)

THE PAYABLE INTEREST AMOUNT IN THE R17 RECORD MUST = THE INTEREST AMOUNT IN THE R91 RECORD. IF NO INTEREST IS PAYABLE, BOTH THE R17 AND R91 RECORDS MUST INDICATE ZEROES FOR THE INTEREST AMOUNT.

VGX:	INVALID FORMAT

THIS ERROR MESSAGE OCCURS IN THE FDA INTERFACE WHEN A FILER ATTEMPTS TO SEND A QUERY OR AN ADD REQUEST FOR AN FDA ESTABLISHMENT NUMBER (FEI) IN THE PP TRANSACTION AND THE FORMAT OF THEIR QUERY IS INCORRECT. THIS CAN TAKE MANY FORMS BUT USUALLY INVOLVES TRYING TO FIT A FOREIGN ADDRESS INTO FIELDS THAT ONLY ACCEPT A US ADDRESS. IN MOST CASES, IT INVOLVES A PROGRAMMING PROBLEM IN THE FILERS SOFTWARE. PROPER FORMAT FOR THE PP TRANSACTION IS SHOWN ON PAGES OGQ 14-20 OF THE CATAIR.

170:	INVALID MANUFACTURER NUMBER

MINIMUM CONSTRAINTS FOR VALID MANUFACTURER NUMBER INCLUDE: 1) ENTIRE NUMBER INCLUDING ISO CODE MUST BE AT LEAST 7 ALPHA OR NUMERIC CHARACTERS LONG AND IT MUST BE LEFT JUSTIFIED. 2) IF THE MID INCLUDES PIECE FOUR (LARGEST NUMBER IN STREET ADDRESS), NUMERIC CHARACTERS CANNOT BE PRECEDED BY MORE THAN 8 ALPHA CHARACTERS. NOTE: AS OF JUNE 27, 2000, WHEN THIS MESSAGE IS GENERATED, ABI IS NOT INDICATING WHICH LINE OF THE SUMMARY IS INVALID.

34D:	CANT DELETE WHILE ENTRIES PRESENT

THIS MESSAGE MAY APPLY TO SEVERAL APPLICATIONS IN ABI. FOR PROTESTS, THIS MESSAGE ADVISES THE FILER THAT A PROTEST MAY NOT BE DELETED WHILE ONE OR MORE ENTRIES ARE STILL ON FILE FOR THE PROTEST NUMBER IN QUESTION. FOR AUTOMATED INVOICE TRANSMISSIONS, THIS MESSAGE INDICATES THAT INDIVIDUAL INVOICES MAY NOT BE DELETED ONCE AN ENTRY IS ON FILE IN ACS FOR THAT INVOICE NUMBER.

VDH:	INCORRECTLY ESTIMATED MPF MINIMUM

CLASS CODE 499 SHOULD INDICATE THE TOTAL MERCHANDISE PROCESSING FEES (MPF) FROM ALL LINE-ITEM "62" RECORDS. IF THE ACTUAL TOTAL IS LESS THAN $25.00, USE $25.00 IN THE "89" RECORD. IF THE ENTRY IN QUESTION INVOLES NAFTA, THE MINIMUM MPF IS $21.00 UNLESS ONE OR MORE LINES DO NOT CLAIM NAFTA. IF THE FILER DOES NOT TRANSMIT THE APPROPRIATE MINIMUM MPF FOR A NAFTA ENTRY, THIS ERROR MESSAGE WILL ALSO BE GENERATED.

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

ADR:	ENTRY TYPE MUST BE 01 OR 11

A CONSOLIDATED ENTRY SUMMARY IS ONLY VALID FOR ENTRY TYPE 01 OR 11.IF A FILER TRANSMITS THE CONSOLIDATED SUMMARY FLAG "C" IN REC 30, POS 39 (EI APPLICATION INPUT), WITH ANY ENTRY TYPE OTHER THAN 01 OR 11, THIS ERROR MESSAGE WILL RESULT.

VOS:	REMOTE ENTRY/RLSE CERT MISSING

THIS MESSAGE OCCURS WHEN A FILER, SET TO OPERATIONAL STATUS FOR REMOTE LOCATION FILING, DOES NOT SEND A '1' SIGNIFYING CERTIFICATION FOR CARGO RELEASE, IN POSITION 38 OF THE 30 RECORD. THIS IS A REQUIREMENT FOR REMOTE LOCATION FILING.

EI9:	ID NUMBER (A) REQUIRED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). THE C37 RECORD PROVIDES FOR THE REPORTING OF IDENTIFICATION NUMBERS (OTHER THAN THE ITEM NUMBER REPORTED IN THE C33 RECORD). EACH IDENTIFICATION NUMBER MAY BE ASSOCIATED WITH AN ID QUALIFIER, TRANSMITTED IN POS 4-6 (FOR IDENTIFICATION NUMBER "A"). IF POS 4-6 IS POPULATED WITH ONE OF THE FOUR VALID QUALIFIERS, POS 7-41 MUST CONTAIN DATA. IF POS 7-41 IS LEFT BLANK, THIS ERROR MESSAGE WILL BE GENERATED. **NOTE** - AT THE CURRENT TIME (APRIL 1998), IF POS 4-6 IS BLANK AND POS 7-41 IS ALSO BLANK, THIS ERROR MESSAGE WILL ALSO GENERATE.

VAU:	ULT CONSIGNEE IN ENTRY HEADER

WHEN AN ULTIMATE CONSIGNEE NUMBER IS TRANSMITTED IN THE HI APPLICATION, REC H2, POS 11-22 (INDICATING ONE ULTIMATE CONSIGNEE FOR THE SHIPMENT), POS 33-44 IN REC H5 MUST BE SPACE FILLED.

DLE:	WARNING - ACCEL REVOKED, CHK PRIV

THIS MESSAGE OCCURS IN THE AUTOMATED DRAWBACK MODULE. IT IS A 'WARNING' THAT APPEARS IF THE CLAIMANT IS CURRENTLY IN THE PRIVILEGE FILE SHOWING THAT ACCELERATED DRAWBACK IS REVOKED. CLAIMANTS HAVE UNTIL 4/6/1999 TO RE-APPLY FOR PRIVILEGES. MESSAGE DLE WILL BECOME A FATAL ERROR ON OR AFTER 4/6/1999.

RB6:	R21, R89 FEE CLASSES INCONSISTENT

ESSENTIALLY THE REVERSE OF MESSAGE 'RB5', THIS MEANS THAT ON THE 'RA' RECON SUMMARY TRANSACTION, THERE IS AT LEAST ONE 'R21' RECORD WITH A FEE CLASS CODE THAT DOES NOT EXIST ON ANY 'R89' RECORD.

2A3:	ENTRY CANNOT BE CERTIFIED

THIS MESSAGE IS GENERATED WHEN A CERTIFICATION (USUALLY FROM THE ENTRY SUMMARY DATA) IS ATTEMPTED AND, FOR ONE OF SEVERAL REASONS, CANNOT BE PERFORMED. THIS MESSAGE WILL BE ACCOMPANIED BY AT LEAST ONE MORE MESSAGE DESCRIBING THE REASON WHY CARGO CERTIFICATION FAILED.

2GB:	DATA REPLACED AS REQUESTED

THIS IS A NORMAL PROCESSING RESPONSE TO A CARGO RELEASE DATA INPUT TRANSACTION (APPLICATION HI) WHEN THE FILER IS USING ACTION CODE "R" TO REPLACE PREVIOUSLY TRANSMITTED, BUT NOT CERTIFIED, DATA.

2C3:	INVALID BOND

CONVERTED BOND TYPE 2: * MAY BE ON FILE BUT NOT FOR THE PORT OF ENTRY AND NOT ON FILE AT A CROSS DDPP OF THE PORT OF ENTRY FOR THE IMPORTER OR ITS PARENT (IF APPLICABLE), * IS ON THE FILE BUT DOESN'T COVER THE DATE OF THE ENTRY DOESN'T AGREE WITH THE BOND TYPE THAT IS ON FILE. CONVERTED BOND TYPE 5: * IS NOT ON FILE FOR THE IMPORTER OR ITS PARENT COMPANY * IS ON THE FILE BUT DOESN'T COVER THE DATE OF THE ENTRY BOND TYPE 8: * THE BOND THAT IS ON FILE IS NOT A VALID CONTINUOUSBOND THAT IS APPROPRIATE FOR THE ENTRY TYPE. FOR BOND TYPE 8, IF THE BOND IS NOT ON FILE ON THE DATE USED FOR BOND VALIDATION (CARGO REL DATE, PAY DUE DATE, ETC) IN THE SUMMARY INPUT, THIS ERROR MESSAGE WILL RESULT. THIS WILL ALSO APPLY TO ENTRIES WITH A BOND THAT IS NOT EITHER A 1 OR 1A1 TYPE BOND IN THE BNDL FILE.

591:	LINE ITEMS INVALID FOR ENTRY TYPE

THIS MESSAGE WILL RARELY BE OBSERVED ON ABI TRANSMISSIONS UNLESS THE FILER MANAGES TO TRANSMIT AN ENTRY TYPE IN THE EI APPLICATION (10 REC, POS 71-72) THAT DOES NOT PERMIT THE REPORTING OF LINE ITEM DETAILS (40-62 RECORDS). USUALLY, THE ENTRY TYPE WILL BE THE ERROR (SUCH AS REPORTING A NON-EXISTENT ENTRY TYPE). MOST AUTOMATED SYSTEMS WILL NOT ALLOW FILERS TO USE ENTRY TYPES THAT ARE NOT CURRENTLY USED FOR IMPORT TRANSACTIONS. THUS, THIS MESSAGE WILL RARELY SURFACE.

VBF:	FW 3-177: INVLD COMN NAME SPECIFC

IF XXXX IS USED FOR THE SPECIES CODE (FW01 REC POS 5-8), THE COMMON NAME SPECIFIC (REC FW02, POS 5-22) IS MANDATORY. NOTE: WHEN XXXX IS USED AS THE SPECIES CODE, THE SCIENTIFIC NAME GENUS (REC FW01, POS 9-26) AND THE COMMON NAME GENERAL (REC FW02, POS 23-40) ARE ALSO MANDATORY.

327:	INVALID DP-SITE DISTRICT/PORT

THIS MESSAGE RESULTS WHEN A FILER SENDS AN 'A' RECORD DISTRICT/PORT/FILER SITE THAT DOES NOT EXIST IN THE BROKER PROFILE IN ACS. A BROKER PROFILE RECORD MUST EXIST FOR THE TRANSMITTED DP-SITE DISTRICT/PORT. IN ADDITION TO THE ABOVE, FOR FILERS WHO HAVE OFFICE CODES IN THEIR BROKER PROFILE RECORDS, THIS MESSAGE WILL BE GENERATED IF THE PORT CODE IN THE 10 RECORD OF THE EI APPLICATION DOES NOT AGREE EXACTLY WITH THE PORT CODE IN THE "B" RECORD. (NOTE 1 ON PAGE APL-6 OF THE CATAIR INDICATES THAT AGREEMENT BETWEEN APPLICATION DETAIL RECORDS AND THE "B" RECORD MUST BE AT THE DISTRICT CODE LEVEL. THIS IS TRUE EXCEPT FOR OFFICE CODE SITUATIONS, WHICH REQUIRES AGREEMENT AT THE FOUR-DIGIT DDPP LEVEL).

VPJ:	CANADIAN TARIFF NBR INVALID

THIS MESSAGE OCCURS IN THE NAFTA DUTY DEFERRAL MODULE. THE NAFTA CTRY TARIFF NUMBER IS SENT IN POSITIONS 24-33 OF THE D20 RECORD AND MUST BE A VALID NUMBER.

08D:	NEW ENT-NBR INVLD BEFORE 10-01-86

THE ENTRY NUMBER SUBMITTED IS IN THE NEW ENTRY NUMBER FORMAT. THE ESTIMATED DATE OF ARRIVAL IS PRIOR TO 10-01-86. NEW ENTRY NUMBER FORMAT IS VALID ONLY FOR ENTRIES WITH ESTIMATED DATES OF ARRIVAL ON OR AFTER 10-01-86.

52Z:	ENTRY/LINE SEQUENCE REJECTED

REFER TO ADMINISTRATIVE MESSAGE 98-0236, DATED 032098. IN SOME CASES THE ULTIMATE CONSIGNEE NAME AND ADDRESS APPLICATION (IJ) WAS CAUSING DATA BASE ERRORS WHEN THE NUMBER OF (I7) ENTRY NUMBER/LINE ITEM SEQUENCE RECORDS EXCEEDED THE LIMIT SET BY THE PROGRAM FOR A PARTICULAR NAME & ADDRESS I3 AND I4 RECORD SET. ALSO, IN SOME REJECT SITUATIONS THE ERROR MESSAGE "524 TRANSACTION DATA REJECTED" WAS DISPLAYING ERRONEOUSLY IN THE IB OUTPUT MESSAGES WHEN THE ENTIRE (IJ) APPLICATION WAS NOT REJECTED. TO ELIMINATE THE ABOVE SITUATIONS AND TO PROVIDE MORE ACCURATE INFORMATION WHEN ERRORS ARE DETECTED IN THE ULTIMATE CONSIGNEE NAME AND ADDRESS APPLICATION (IJ) TRANSMISSIONS, THIS ERROR MESSAGE AND 52Y "MAXIMUM (I7) RECORDS EXCEEDED" ARE GENERATED. BOTH THE 52Y AND 52Z MESSAGES WILL APPEAR AS (IB) OUTPUT RECORDS WHEN CUSTOMS DETERMINES THAT THE INFORMATION TRANSMITTED CANNOT BE ADDED TO THE DATABASE AS REQUESTED BY AN ABI FILER.

 Next 10 >>Showing results 1 to 25 of 1405