ABI Error Message

180:	ENTRY NBR CHECK DIGIT MISMATCH

THE ENTRY NUMBER AND/OR ENTRY NUMBER CHECK DIGIT USED IN THE DRAWBACK DISKETTE MODULE IS INCORRECT BASED ON THE MATHEMATICAL CHECK-DIGIT COMPUTATION PERFORMED BY ACS.

825:	ULT CONS ON NAT'L SANCTION

THIS ENTRY SHOULD BE REJECTED TO THE FILER. A DUTY PAID, "LIVE" ENTRY IS REQUIRED. IF A FILER RECEIVES THIS MESSAGE THROUGH ABI THERE IS ADDITIONAL INFORMATION THAT CAN BE PROVIDED TO ASSIST THE FILER IN RESOLVING THE PROBLEM. CLIENT REPS CAN PROVIDE SANCTION INFORMATION, INCLUDING A CONTACT AT THE NATIONAL FINANCE CENTER, AND ANY BILL INFORMATION FOR OUTSTANDING BILLS THAT CAUSED THE SANCTION. NOTE: THIS MESSAGE IS NOT AN ABI REJECTION MESSAGE.

524:	TRANSACTION DATA REJECTED

USED BY ABI BATCH PROCESSING WHEN REJECTING A USER TRANSACTION. THIS MESSAGE IS ASSOCIATED WITH ALL CONDITIONS WHICH CONSTITUTE REJECTION OF THE TRANSACTION.

8WM:	VOYAGE/FLIGHT NUMBER INVALID

THIS MESSAGE IS GENERATED IN RESPONSE TO A BILL OF LADING UPDATE TRANSMISSION (APPLICATION LN). THE VOYAGE/FLIGHT NUMBER MUST BE A MINIMUM OF THREE CHARACTERS IN LENGTH. FOR OCEAN SHIPMENTS (MOT 10/11/12), ANY COMBINATION OF NUMBERS AND LETTERS IS PERMITTED FOR THE VOYAGE NUMBER. IF THE VOYAGE NUMBER HAS A LEADING SPACE AT THE BEGINNING OF THE ELEMENT IN THE L1 REC, POS 36-40, THIS MESSAGE WILL BE GENERATED EVEN IF THE REMAINING POSITIONS ARE FILLED WITH A MINIMUM OF THREE ALPHA-NUMERIC CHARACTERS. **NOTE** - FOR AIR SHIPMENTS, LEADING SPACES OR A FLIGHT NUMBER WITH FEWER THAN 3 NUMERIC CHARACTERS WILL GENERATE ERROR MESSAGE 10R "INVALID FLIGHT NUMBER FORMAT".

06F:	PC: VESSEL CODE & NAME SUBMITTED

THIS IS A "PAIRED" ENTRY. BOTH VESSEL CODE AND VESSEL NAME WERE SUBMITTED FOR EDIT. ONLY ONE OF THESE WILL BE CONSIDERED. PLEASE RE-ENTER ONE OR THE OTHER DATA ELEMENTS.

BRN:	RECON PORT/FILER NOT PERMITTED

FOR RECONCILIATION, THE FILER IA A LICENSED BROKER AND IS NOT PERMITTED IN LOCATION WHERE THE RECON IS BEING FILED.

SG3:	SUGAR CERT SENT FOR NON-CANADA

CANADIAN SUGAR CERTIFICATE DATA WAS PROVIDED ON-LINE AND EITHER/BOTH THE C/O AND/OR C/E IS NOT CANADA.

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.

4HI:	NO QUOTA FOR COUNTRY/CATEGORY

THIS MESSAGE IS GENERATED IN RESPONSE TO AN ABI QUOTA QUERY INPUT. IF THE CATEGORY AND COUNTRY IDENTIFIED BY THE TRANSMITTING FILER DO NOT RESULT IN A MATCH OF THE VARIOUS QUOTA FILES, THIS MESSAGE WILL BE SENT TO THE FILER AS A RESPONSE

AE7:	DATE INVALID/MISSING

THIS ERROR MESSAGE OCCURS IN THE "REVISED FILER DATE" (DN) TRANSACTION WHEN A FILER TRANSMITS A REVISED ENTRY DATE IN THE DN01 RECORD, POSITIONS 19-24, THAT CONTAINS BLANKS, ZEROES OR IS AN INVALID DATE (E.G. 999999).

630:	INVALID MODE OF TRANSPORTATION

IN ORDER FOR CARGO CERTIFICATION TO BE PERFORMED, THE MODE OF TRANSPORTATION (MOT) FIELD MUST BE COMPLETED. INFORMAL ENTRY SUMMARY TRANSACTIONS (APPLICATION IDENTIFIER EI) WHICH REQUEST CARGO CERTIFICATION, BUT DO NOT PROVIDE THE MOT IN THE 20 REC, POS 28-29, WILL RECEIVE THIS ERROR MESSAGE. SIMILARLY, SEPARATE CARGO RELEASE INPUT TRANSACTIONS (APPLICATION IDENTIFIER HI) WHICH OMIT THE MOT (H1 REC, POS 32-33) WILL ALSO RECEIVE THIS ERROR MESSAGE, WHETHER OR NOT THE RELEASE CERTIFICATION CODE (H1 REC, POS 34) IS ALSO TRANSMITTED. (INFORMAL ENTRY SUMMARY INPUT WHICH DOES NOT REQUEST CARGO CERTIFICATION WILL BE ACCEPTED WITHOUT THE MOT).

834:	ADD INVALID - BROKER REF MISMATCH

IF AN ENTRY SUMMARY RECORD EXISTS AND AN ADD TRANSACTION IS SUBMITTED VIA BATCH ABI INPUT, THE BROKER REFERENCE NUMBER IN THE EXISTING RECORD MUST MATCH THE BROKER REFERENCE NUMBER IN THE '20' RECORD OF THE BATCH ADD TRANSACTION. FILERS MAY CHANGE THEIR FILER REFERENCE NUMBER IF THEY USE ACTION CODE OF "R" (REPLACE) OR "C" (CHANGE) IN LIEU OF "A" (ADD). THIS MESSAGE WILL ALSO RESULT IF THE CARGO DATA INPUT APPLICATION (HI) OR THE BORDER CARGO RELEASE APPLICATION (HN) IS USED AND THE "A" ACTION CODE IS TRANSMITTED WITH A DIFFERENT BROKER REFERENCE NUMBER THAN WAS USED ON THE INITIAL INPUT.

APN:	VOIDANCE REQST NOT VALID

A REQUEST FOR VOIDANCE OF DENIAL, INDICATED BY 'R', MAY BE SUBMITTED WITHIN 90 DAYS AFTER PROTEST HAS BEEN DENIED BY CUSTOMS. THE VOIDANCE REQUEST INDICATOR IS ALREADY SET AT 'R' (AFFIRMATIVE FOR REQUEST), OR THE PROTEST IS NOT IN DENIED STATUS.

0JN:	FIRMS CODE REQUIRED

ENTRIES WHICH REQUEST CARGO SELECTIVITY PROVISIONAL RESULTS MUST CONTAIN A FIRMS CODE WHICH IS "ACTIVE" AND WHICH REPRESENTS A VALID CARGO EXAMINATION SITE. (NOT A CUSTOMS ADMINISTRATIVE SITE). IF THE FIRMS CODE, FROM THE FIRMS FILE DATABASE, IS NOT ACTIVE, THE INPUT TRANSACTION WILL BE REJECTED WITH THIS ERROR MESSAGE.

VGU:	FDA 701:FDA NOTIFICATION NOT REQD

THIS ERROR MESSAGE RESULTS WHEN A FILER ATTEMPTS TO SEND FDA DATA FOR A TARIFF NUMBER THAT IS CODED IN THE HARMONIZED DATA BASE AS AN 'FD0" (FDA NOT REQUIRED). FDA DOES NOT WANT INFORMATION FOR THESE TARIFF NUMBERS.

8WY:	INVALID HOUSE BL/AWB NUMBER

THIS MESSAGE IS GENERATED IN RESPONSE TO A BILL OF LADING UPDATE TRANSACTION (APPLICATION LN). THE HOUSE BILL NUMBER IS TRANSMITTED IN THE L3 REC, POS 36-47. IF THE NUMBER REPORTED IN THIS FIELD IS FEWER THAN 12 CHARACTERS LONG, THE NUMBER SHOULD BE LEFT JUSTIFIED. IF ANY LEADING SPACES ARE INCLUDED IN THE HOUSE BILL NUMBER, THIS ERROR MESSAGE WILL BE GENERATED.

40O:	FAS SPI ORIG CTRY NOT = EXP CNTRY

IF AN ENTRY CLAIMS A FREELY ASSOCIATED STATES SPI (Z), THE COUNTRY OF ORIGIN AND THE COUNTRY OF EXPORT MUST BE THE SAME.

EIN:	INVALID TERMS OF DELIVERY CODE

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). TERMS OF DELIVERY ARE TRANSMITTED IN THE C13 REC, POS 4-6.VALID TERMS OF DELIVERY CODES ARE LISTED ON PAGE AII-23 OF THE CATAIR. THE USE OF ANY OTHER CODE, OR A BLANK FIELD, IN THIS DATA ELEMENT WILL GENERATE THIS ERROR MESSAGE. ND ADDRESS ARE ALSO REQUIRED TO BE TRANSMITTED IN THE C09-C11 RECORDS. IF THE NAME ELEMENT IN THE C09 REC, POS 4-38, IS LEFT BLANK, THIS ERROR MESSAGE WILL BE GENERATED.

RB5:	R89, R21 FEE CLASSES INCONSISTENT

THIS MESSAGE MEANS THAT AT LEAST ONE OF THE FEE CLASS CODES GIVEN IN THE 'R89' RECORD(S) OF THE 'RA' RECON TRANSACTION DOES NOT EXIST ON ANY OF THE GIVEN 'R21' RECORDS VIA ABI.

VK5:	HLS:HEX CONSTANT FORMAT INVALID

A HEXADECIMAL CONSTANT VALUE MUST BE EXPRESSED AS X'....' EVEN NUMBERS OF HEXADECIMAL DIGITS 0 THRU 9 A A THRU F ARE REQUIRED.

2C0:	BOND NOT IN EFFECT

A VALID BOND IS ON FILE, BUT IS NOT EFFECTIVE ON THE DATE OF THE QUOTA ENTRY. OR, IF NOT ABI, CHECK BOND TYPE ON ENTRY HEADER MASTER RECORD. IF (9), MUST "X" 'S.E.B.' ACS WILL NOT CHECK CONTINUOUS (301) BOND FILE.

AGU:	RELEASD-CANT UPDATE INVOICE

IF SSA01-RELEASE IS NOT SPACES, AN ASSOCIATED INVOICE CANNOT BE UPDATED. THE ABOVE COMMENT MEANS THAT AN INVOICE INPUT (APPLICATION CI) CANNOT BE TRANSMITTED IF THERE IS A RELEASE DATE ALREADY POSTED TO ANY ENTRY NUMBER ASSOCIATED WITH THE INVOICE.

AE3:	SECONDARY ADDRESS REQUIRED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN 'ADD 5106' TRANSACTION, APPLICATION IDENTIFIER TI. IF A POST OFFICE BOX IS TRANSMITTED IN THE T1 RECORD, POS 48-79, A SECONDARY ADDRESS IS REQUIRED TO BE SENT IN THE TB/TC RECORDS.

ARH:	PROTESTANT TYPE INVALID

A VALID VALUE IS REQUIRED IN THE PROTESTANT TYPE FIELD. VALID VALUES ARE: D - DRAWBACK CLAIMANT F - FOREIGN MANUFACTURER/PRODUCER/EXPORTER I - IMPORTER/CONSIGNEE M - MASTER OF VESSEL S - SURETY V - VESSEL OPERATOR O - OTHER THE VALUE SUBMITTED IN THE PROTESTANT TYPE FIELD IS NOT A VALID VALUE.

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.

 Next 10 >>Showing results 1 to 25 of 1405