ABI Error Message

AI3:	INVALID CASE NUMBER ENTERED

ADA/CVD BROKER QUERY INPUT RECORD CONTAINED AN INVALID CASE NUMBER .

546:	EXISTING ENTRY IN CUSTOMS STATUS

THIS MESSAGE OCCURS WHEN A FILER ATTEMPTS TO TRANSMIT AN ENTRY SUMMARY TRANSACTION FOR AN ENTRY NUMBER THAT IS IN CUSTOMS STATUS. CUSTOMS STATUS MEANS THAT CUSTOMS HAS "PROCESSED" THE ENTRY. THE MOST COMMON SITUATION FOR THIS ERROR IS WHEN A PAYMENT HAS BEEN COLLECTED (BY CHECK, STATEMENT PROCESSING OR ACH) AND THE FILER ATTEMPTS TO RETRANSMIT THE SUMMARY DATA. ANOTHER COMMON CAUSE FOR THIS ERROR IS WHEN THE ENTRY NUMBER APPEARS ON A PRELIMINARY STATEMENT AND THE FILER ATTEMPTS TO CORRECT THE SUMMARY DATA WITHOUT FIRST REMOVING THE ENTRY FROM STATEMENT STATUS. IF THE ENAI SCREEN SHOWS "ENT ACP NOT LIQ", THE FILER MAY NOT RETRANSMIT THE SUMMARY UNTIL THE SUMMARY IS PUT INTO A REJECTED STATUS. IF THE ENTRY NUMBER IS A DRAWBACK CLAIM THAT IS IN CUSTOMS STATUS AND THE FILER IS ATTEMPTING TO CHANGE THE DATA, THE DISKETTE WILL BE REJECTED AND CUSTOMS WILL MANUALLY PROCESS ANY CHANGES AS INDICATED ON THE PAPER CLAIM. IF THE ENTRY NUMBER IS NOT A DRAWBACK CLAIM, BOTH THE CLAIM AND DISKETTE WILL BE RETURNED. ACCELERATED DRAWBACK WILL BE PAID UPON CORRECTION (IF NOT PREVIOUSLY PAID). ABI WILL REJECT THE TRANSMISSION.

SG2:	INVALID CANADA SUGAR CERT FORMAT`

A CORRECT CERTIFICATE MUST BE 7 ALPHA-NUMERIC CHARACTERS WITH NO SPECIAL CHARACTERS. EITHER THE GIVEN DATA CONTAINS SPECIAL CHARACTERS OR IS NOT A TOTAL OF 7 CHARACTERS IN LENGTH.

40K:	SPI INVALID FOR EXP COUNTRY

SPECIAL PROGRAM INDICATORS, LISTED IN THE CATAIR ON PAGES ENS-48 AND 49 MAY NOT BE VALID FOR ALL PROGRAMS FOR ALL COUNTRIES. FOR EXAMPLE, ECUADOR IS ELIGIBLE FOR THE ANDEAN PREFERENCE PROGRAM (SPI "J"), BUT IS NOT ELIGIBLE FOR THE CARRIBEAN PREFERENCE PROGRAM (SPI "E"). THEREFORE, AN ENTRY SUMMARY INPUT TRANSACTION THAT USED CODE "E" WITH ISO CODE "EC" AS THE COUNTRY OF EXPORT WOULD RECEIVE THIS ERROR MESSAGE.

VNT:	DBK IMPORT ENTRY NOT ON FILE

THIS DRAWBACK MODULE ERROR MESSAGE MEANS THAT THE DESIGNATED IMPORT ENTRY DOES NOT EXIST AS GIVEN. ACS DOES A MATCH ON THE IMPORT ENTRY NUMBER AND THE PORT OF ENTRY GIVEN ON THE DISKETTE BY THE FILER. IF THE FILER USES AN IMPORT ENTRY/PORT COMBINATION THAT IS NOT VALID IN ACS, THIS MESSAGE WILL BE GENERATED. THEREFORE, EITHER THE ENTRY DOES NOT EXIST AT ALL, OR IT DOES NOT EXIST FOR THE PORT INDICATED. NOTE: THERE ARE INSTANCES WHERE VALID ENTRIES ARE NOT IN ACS (E.G. INFORMALS THAT WERE JUST DONE ON CASH RECEIPTS). FOR THESE, A SPECIAL CM NUMBER HAS BEEN ESTABLISHED IN ACS. IF THE FILER INDICATES THAT THIS IS THE CASE, THE FILER MAY DESIGNATE THE MONIES FROM CM888888/9900. THIS CM HAS BEEN ESTABLISHED JUST FOR THIS CASE WHERE EITHER AN INFORMAL OR MAIL ENTRY WAS DONE ON A CASH RECEIPT WITH NO ACS ENTRY RECORD CREATED.

VIA:	DT HS7: VIN LIST DUP POSITION: 3

THIS MESSAGE IS GENERATED WHEN FILERS TRANSMIT DOT INFORMATION IN THE DT03 RECORD. THIS RECORD PROVIDES FOR UP TO FOUR INSTANCES OF THE VIN (VEHICLE IDENTIFICATION NUMBER). IF FEWER THAN FOUR RECORDS ARE TRANSMITTED, THE RECORDS MUST BE COMPLETED USING THE FIRST FIELD (POS 5-21), THEN THE SECOND (POS 22-38), ETC. IF POSITION 3 IS LEFT BLANK, BUT A VIN IS TRANSMITTED IN POSITION 4, THIS ERROR MESSAGE WILL RESULT. NOTE: THIS MESSAGE IS ONLY APPLICABLE WHEN THE DOT DATA IS TRANSMITTED AS PART OF AN ENTRY SUMMARY BEING CERTIFIED FOR CARGO RELEASE (APPLICATION ID IS EI). IF EITHER HN (BORDER CARGO RELEASE) OR HI (CARGO RELEASE) IS USED TO REPORT DOT DATA, ERROR MESSAGE VH6 WILL BE GENERATED.

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.

458:	IMPORT DATE INVALID/CONFLICTING

THE IMPORT DATE MUST BE IN THE MMDDYY FORMAT, 20 REC, POS 34-39. IF THE DATE TRANSMITTED IS NOT A VALID DATE ON THE CALENDAR (I.E., 013298), THIS ERROR MESSAGE WILL BE GENERATED. THE IMPORT DATE MUST ALSO BE IN PROPER CHRONOLOGICAL SEQUENCE WITH THE REPORTED DATE OF EXPORT (50 REC, POS 71-76) AND THE I.T. DATE (IF AN I.T. IS REPORTED) IN THE 22 REC, POS 64-69. HOWEVER, IF THE DATE SEQUENCE IS INCORRECT, EITHER ERROR MESSAGE NUMBER 915 (IT DATE/DATE OF IMP INCONSISTENT) OR ERROR MESSAGE NUMBER 384 (EXPORT DATE INVALID/CONFLICTING) WILL BE GENERATED. ALSO, IF THE IMPORT DATE IS CORRECT, BUT THE ESTIMATED DATE OF ARRIVAL IN THE 20 REC, POS 66-71, IS BLANK, THIS MESSAGE WILL ALSO RESULT. **NOTE** - IF ALL THE DATES ON THE EI TRANSACTION APPEAR TO BE CORRECT, VERIFY IF THE SUMMARY HAS HAD AN ENTRY DATE ASSIGNED THAT IS PRIOR TO THE IMPORT DATE. IF SO, THE ENTRY MASTER FILE RECORD WILL NEED TO BE CORRECTED.

VPR:	CLAIM LINE# OUT OF SEQUENCE

THIS ERROR MESSAGE OCCURS IN THE NAFTA DUTY DEFERRAL MODULE. A CLAIM LINE NUMBER IS SENT IN THE D10 RECORD, POSITIONS 4-6. THIS RECORD CAN BE REPEATED UP TO 99 TIMES BUT THE SEQUENCING MUST BE IN ORDER. IF THERE ARE THREE LINES AND THE LINE NUMBERS ARE SENT 001, 003, 002, THIS REJECT WILL BE GENERATED.

VDT:	INVALID FTZ ZONE STATUS

THE FOREIGN TRADE ZONE STATUS (REC 40, POS 63) IS MANDATORY WHEN THE ENTRY TYPE IS 06. THE ONLY ACCEPTABLE CODES ARE P, D, N, OR Z. THIS MESSAGE ALSO OCCURS WHEN ONE OF THE ACCEPTABLE CODES IS SENT,BUT ON A NON-FTZ (TYPE 06) ENTRY.

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.

B05:	INVALID RECORD TYPE CODE

INPUT RECORD TYPE CODE FIELD CONTAINS A CHARACTER OTHER THAN '1', '2', '3', '4'. IN THE AUTOMATED DRAWBACK MODULE THIS MESSAGE INDICATES THE USE OF A CLAIM TYPE (OR AN ENTRY TYPE) OF OTHER THAN '41', '42', '43', '44', '45' OR '46'.

40J:	SPI CLAIM INVALID FOR TARIFF

MOST TARIFF NUMBERS ARE ELIGIBLE FOR ONE OR MORE SPECIAL PROGRAMS THAT REDUCE OR ELIMINATE THE DUTY REQUIRED. THESE ARE CODED AS "SPI" FOR THOSE PROGRAMS THAT THE INDIVIDUAL TARIFF NUMBER HAS BEEN FLAGGED FOR. IF AN ABI FILERS TRANSMITS AN SPI (SUMMARY TRANSACTION 50 REC, POS 3, OR POS 78-79; 70/80/81 REC, POS 13 OR POS 79-80) THAT IS NOT LISTED ON THE TARIFF FILE FOR THAT TARIFF NUMBER, THIS ERROR MESSAGE WILL RESULT. FILERS SHOULD VERIFY THE SPI FROM THEIR HARMONIZED QUERY OUTPUT (V3 REC, POS 53-72) TO ASCERTAIN THAT THE SELECTED SPI APPLIES TO THE TARIFF NUMBER. NOTE: AS STATED IN ERROR MESSAGE 40L, IF THE TRANSMITTED SPI (50 RECORD OR 70 RECORD) IS ON THE TARIFF FILE FOR THE TARIFF NUMBER, IT MUST NONETHELESS AGREE WITH THE C/O CODE (EITHER "MX" OR "CA"). IF THE C/O IS "CA", AN SPI OF "MX" WILL GENERATE THIS ERROR MESSAGE.

592:	INVALID ENTRY DISTRICT /PORT

DISTRICT/PORT NON-NUMERIC OR NON-EXISTENT FOR DRAWBACK ENTRY TYPES WHERE DATE OF ENTRY IS = OR > 10/01/94 ONLY, THE FOLLOWING DISTRICT/PORT/TEAM COMBINATIONS WILL BE VALID: DDPP / TEAM DDPP / TEAM 0401 1DA 2002 5LB 1001 2DB 5301 6D0 3901 3DR 2704 7D0 5201 4LA 2809 7D7

28O:	*CENSUS* MFR/SHP NO NAME/ADDRESS

MANUFACTURER/SHIPPER'S NAME AND/OR ADDRESS IS NOT ON FILE

10V:	SURETY CODE NOT FOUND

THIS MESSAGE APPLIES TO CARGO RELEASE TRANSACTIONS (HI) ONLY. A FILER MUST TRANSMIT BOND INFORMATION (AN "8" FOR A CONTINUOUS BOND OR A "9" FOR A SINGLE TRANSACTION BOND) IN THE H1 REC, POS 40. IF BOND TYPE "9" IS ELECTED, A SURETY CODE IS MANDATORY IN THE H1 REC, POS 71-73. IF THE SURETY CODE TRANSMITTED IS NOT FOUND LISTED ON THE SURETY DATABASE, THIS MESSAGE WILL RESULT. NOTE: IF THE SURETY CODE IS PRESENT ON THE DATABASE, BUT IS IN REVOKED STATUS, ERROR MESSAGE 10U WILL BE GENERATED.

AH8:	43 RECORD IS BLANK / INVALID

THE 43 RECORD IS INVALID OR BLANK.

1GL:	MAIL FEE REQUIRED

FOR DUTIABLE MAIL ENTRIES (MOT 50), A 34 RECORD WITH CLASS CODE 496 AND AN AMOUNT OF $5.00 MUST BE TRANSMITTED ON THE SUMMARY INPUT. IF THE 34 RECORD IS OMITTED, THIS ERROR MESSAGE WILL RESULT.

AEQ:	ERROR IN A32 REC;RLSE 4

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

04F:	PC: ENTER VESSEL NAME

ENTRY IS PAIRED CITIES. VESSEL NAME IS BLANK. VESSEL NAME IS REQUIRED.

3A5:	SELECTIVITY ALREADY PERFORMED

THIS MESSAGE OCCURS WHEN A FILER ATTEMPTS TO SEND SELECTIVITY DATA FOR AN ENTRY NUMBER WHERE SELECTIVITY HAS ALREADY BEEN PERFORMED, EITHER ELECTRONICALLY OR BY MANUAL PROCESSING. THIS MESSAGE DOES NOT OCCUR IF THE FILER SENDS SELECTIVITY DATA FOR AN ENTRY THAT RECEIVED AN INITIAL SELECTIVITY RESPONSE OF "PAPERLESS". IN THIS CASE THE FILER WILL RECEIVE MESSAGE 681 "CUSTOMS REL VIA EREL ON FILE". NOTE: IN SOME CASES, THIS MESSAGE WILL ACCOMPANY THE MESSAGE "OGA DATA IGNORED" AND IF THE INPUT APPLICATION WAS FROM AN ENTRY SUMMARY, THESE TWO MESSAGES WILL NOT CAUSE A REJECTION.

VNR:	CLAIM DTE OVER 30 DAYS IN FUTURE

IN THE DRAWBACK MODULE THIS MESSAGE INDIACTES THAT THE DATE IS IN A VALID FORMAT, BUT IS GREATER THAN 30 DAYS IN THE FUTURE. FUTURE DATES ARE NOT ACCEPTED FOR THE DISKETTE PROGRAM. DATES UP TO 30 DAYS IN ADVANCE ARE ACCEPTED VIA ABI. FOR ABI TRANSMISSIONS, MESSAGE VLZ WILL BE USED IF OVER 30 DAYS IN ADVANCE.EN A SUCCESSFUL ACKNOWLEDGEMENT IS RECEIVED FROM ABI SHOULD THE ACH PAYMENT BE TRANSMITTED.

ASJ:	PROTESTED ISSUE NOT APPLICABLE

THE P70 CANNOT BE REPEATED OR TRANSMITTED AS PART OF AN AMENDMENT, ADDENDA, SERVICE REQUEST.

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

BR5:	RECON FEES MISMATCH (R89:R90)

THE TOTAL RECONCILED FEES FROM ALL 'R89' RECORDS DO NOT MATCH THE TOTAL RECONCILED FEES REFLECTED BY THE FILER IN THE RECON'S 'R90' RECORD.

 Next 10 >>Showing results 1 to 25 of 1405