ABI Error Message

BR7:	DUPLICATE FEE CLASS CODE

AT LEAST ONE OF THE FEE CLASS CODES GIVEN ON THE 'R21' OR 'R89' RECORDS VIA THE ABI 'RA' TRANSACTION HAS BEEN DUPLICATED FOR THAT RECONCILIATION. FOR THE 'R21' RECORDS, NO FEE CLASS CODE CAN BE DUPLICATED WITHIN THE SAME 'R21' RECORD OR ADDITIONAL 'R21' RECORDS FOR THE SAME IMPORT ENTRY GIVEN IN THE 'R20' RECORD. FOR THE 'R89' RECORD, NO FEE CLASS CODE CAN BE DUPLICATED FOR THE SAME RECONCILIATION SUMMARY.

055:	INVALID BROKER CODE

NEW FILER CODES MUST BE 3 DIGIT ALPHA/NUMERIC. BROKER CODE IS REQUIRED INPUT FOR THIS TRANSACTION AND WAS OMITTED.

366:	ENTRY ALREADY CANCELLED

THIS MESSAGE OCCURS WHEN A FILER ATTEMPTS TO SEND A DELETE 'D' ACTION CODE IN AN ENTRY SUMMARY SEND FOR AN ENTRY SUMMARY THAT HAS BEEN CANCELLED BY CUSTOMS.

RB4:	EXCESS/INVALID FEE COUNT

FOR RECONCILIATION, THE 'R20' ABI INPUT RECORD FEE COUNT IS EITHER NOT NUMERIC (INVALID) OR > 10 (EXCESS). IN OTHER WORDS, POS 78-79 OF THE R20 RECORD MUST SHOW A NUMERIC FIGURE WHICH EQUALS THE NUMBER OF FOLLOWING R21 RECORDS. IF ONE R21 RECORD FOLLOWS THE R20 RECORD, POS 78-79 WOULD BE "01", E.G. IF THE FILER SPACE FILLS THIS ELEMENT BUT TRANSMITS AN R21 RECORD, THIS MESSAGE WILL RESULT (THE 'INVALID' PART OF THE NARRATIVE). IF THE FILER TRANSMITS A FIGURE GREATER THAN '10', THIS MESSAGE WILL ALSO RESULT (THE 'EXCESS' PART OF THE MESSAGE). NOTE: IF THE ENTRY IS AN AGGREGATE RECON, AND NO R21 RECORDS ARE TRANSMITTED, THE FILER MUST STILL SHOW '00' IN POS 78-79 OF EACH R20 RECORD.

8VB:	COMPUTER SITE INVALID FOR BLOCK

THIS MESSAGE IS GENERATED IN RESPONSE TO A TIB EXTENSION REQUEST (APPLICATION XN), ALTHOUGH IT MAY APPLY TO OTHER APPLICATIONS, AS WELL. IN THE INPUT RECORDS, THE XA RECORD CONTAINS A FIELD FOR THE DDPP OF THE SUMMARY FOR WHICH AN EXTENSION IS BEING REQUESTED. (POS 3-6). IF THAT FIELD IS LEFT BLANK, THIS MESSAGE IS GENERATED. NOTE: THIS MESSAGE WILL ALSO OCCUR IF THE PORT CODE FIELD IN THE XA RECORD IS NOT IDENTICAL TO THE PORT OF ENTRY FOR THE ENTRY BEING EXTENDED.

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.

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.

VAG:	DT HS7: INVALID BOX CERTIFICATIN

ONLY A "Y" IS PERMITTED TO TRANSMIT THE BOX CERTIFICATION REQUIREMENT (RECORD DT01, POS 10). ANY OTHER CHARACTER WILL GENERATE THIS MESSAGE.

EJZ:	REASON FOR DIFFERENCE REQUIRED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). IN THE C39 RECORD, POS 24-58 IS PROVIDED TO ENABLE THE FILER TO PROVIDE A FREE FORM DESCRIPTION OF THE REASON FOR THE DIFFERENCE IN THE QUANTITY OF CARGO SHIPPED BY THE INVOICING PARTY AND THE QUANTITY REPORTED ON THE C33 RECORD. THIS FIELD CANNOT BE BLANK OR THIS ERROR MESSAGE WILL BE GENERATED.

370:	ENTRY BELONGS TO ANOTHER DD/PP

THIS ERROR MESSAGE OCCURS WHEN A FILER SENDS AN ENTRY SUMMARY TRANSACTION FOR AN ENTRY THAT WAS RELEASED (OR AT LEAST ACCEPTED) AT ANOTHER PORT. THE SELECTIVITY RECORD WILL SHOW THE PORT CODE ESTABLISHED BY THE FILER'S FIRST SUCCESSFUL ABI TRANSMISSION. IF THE FILER'S SUMMARY INPUT PORT CODE (10 REC, POS 4-7) DOES NOT MATCH THE PORT CODE ON THE SELECTIVITY RECORD, THIS ERROR MESSAGE WILL RESULT. THIS ERROR WILL ALSO RESULT IF THE FILER TRANSMITS A CARGO RELEASE TRANSACTION THAT DOES NOT MATCH THE PORT CODE IN THE H1 REC, POS 4-7, TO THE PORT CODE SHOWN ON THE ENTRY MASTER FILE RECORD FROM THE FILER'S PRIOR TRANSMISSION. IF THE SELECTIVITY RECORD PORT CODE IS INCORRECT, THE FILER SHOULD FOLLOW LOCAL PROCEDURES IN ORDER TO BE ABLE TO RETRANSMIT THE SUMMARY WITH THE CORRECT PORT CODE ONCE THE SELECTIVITY RECORD HAS BEEN CHANGED. IF THERE IS AN ENTRY SUMMARY ON FILE, AND STILL IN ABI STATUS, THE FILER MAY DELETE THE SUMMARY AND RETRANSMIT IT WITH THE CORRECT PORT CODE.

8N6:	ALLOWABLE DUTY/TAX IS ZERO

THIS DRAWBACK MODULE ERROR MESSAGE MEANS THAT THE PAID OR LIQUIDATED AMOUNT FOR THE IMPORT ENTRY WAS ZERO AND THAT THE IMPORT IS NOT ELIGIBLE FOR THE DRAWBACK CLAIM.

AAM:	MFR/SHIPPER ID INVALID ISO PREFX

THIS ERROR MESSAGE WILL RESULT IF A SHIPMENT IDENTIFIES A MANUFACTURER IDENTIFICATION NUMBER (MID) INVOLVING A CANADIAN SHIPPER. VALID ISO PREFIXES FOR THESE SHIPMENTS ARE: XN (WHERE N= ONE OF THE 10 ALLOWABLE ALPHA CHARACTERS FOR THE 10 CANADIAN PROVINCES). IF THE SHIPMENT IN QUESTION DOES NOT INVOLVE CANADIAN GOODS, THE ISO COUNTRY PREFIX CODE MUST BE A VALID TWO-CHARACTER PREFIX FROM THE DATABASE. ERRORS IN THE CODE FOR NON-CANADIAN SHIPMENTS WILL GENERATE ERROR MESSAGE 0M9.

G9A:	REMOTE ENTRY/I.T. CONFLICT

IF THE B REC REMOTE ENTRY INDICATOR IS A '1', THE ENTRY DATA CANNOT CONTAIN I.T. NUMBER OF ANY OF THE POSSIBLE FORMATS IN ANY OF THE HA OR OM RECORDS.

VC9:	MPF SURCHARGE NOT REQUIRED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN ENTRY SUMMARY INPUT TRANSACTION (APPLICATION EI). FILERS WHO HAVE ABE RECORDS ANYWHERE IN THE UNITED STATES THAT INDICATE OPERATIONAL STATUS FOR CARGO RELEASE OR BORDER CARGO RELEASE ARE NOT REQUIRED TO DEPOSIT THE MANUAL MPF SURCHARGE. IF THE FILER TRANSMITS CLASS CODE 500 WITH $2.00 ON ANY ENTRY AFTER OBTAINING OPERATIONAL CARGO STATUS, THIS ERROR MESSAGE WILL RESULT.

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.

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.

DKN:	D50 RECORD MUST CONTAIN DATA

THIS ERROR MESSAGE COULD BE THE RESULT OF A DRAWBACK DISKETTE OR ABI DRAWBACK PROBLEM. IT IS SAYING THAT WHEN CUSTOMS FORMATTED THE RECORDS FROM THE DRAWBACK DISKETTE OR WHEN THE DATA WAS SENT VIA ABI, NO DATA WAS PRESENT IN THE GIVEN RECORD. IF THE DRAWBACK DISKETTE HAS NO DATA, THE PC PROGRAM SHOULD STOP IT BEFORE TRANSMISSION; HOWEVER, THERE MAY HAVE BEEN DATA THERE, BUT IT WAS BAD DATA.

BRG:	INVALID OTHER ISSUE

FILER HAS ATTEMPTED TO FILE A RECON FOR AN 'OTHER' ISSUE AGAINST AN IMPORT ENTRY THAT IS NOT FLAGGED FOR AN 'OTHER' NAFTA ISSUE, OR THE FILER HAS ATTEMPTED TO FILE A RECON FOR AN 'OTHER' ISSUE FOR AN IMPORT THAT HAS BEEN FLAGGED FOR A DIFFERENT 'OTHER' ISSUE. EG. - FILER ATTEMPTS RECON FOR 'CL' ISSUE AND IMPORT FLAGGED FOR 'VL' . ALSO, IF AN IMPORT ENTRY WAS FLAGGED AT SOME POINT IN THE PAST, BUT IS NOT FLAGGED AT THE TIME THAT THE RECON ENTRY IS TRANSMITTED TO ABI, THIS MESSAGE WILL BE GENERATED, INSTEAD OF 'ENTRY NOT SUBJECT TO RECON'.

4A0:	INVALID ACTION CODE

THIS MESSAGE IS GENERATED IN RESPONSE TO A CARGO RELEASE DATA INPUT TRANSACTION (APPLICATION HI). THE H1 RECORD, POS 3 MUST REFLECT ONE OF THREE ACTION CODES: A (ADD) D (DELETE) OR R (REPLACE). IF ANY OTHER CHARACTER, OR A BLANK, IS TRANSMITTED IN THIS FIELD, THIS ERROR MESSAGE WILL BE GENERATED.

29H:	INVALID DIST/PORT/BROKER

THIS MESSAGE OCCURS WHEN A FILER SENDS A DISTRICT/PORT/FILER COMBINATION IN THE 10 RECORD OF AN ENTRY SUMMARY EI TRANSACTION, AN H1 RECORD FOR AN HI TRANSACTION OR AN 01 RECORD OF A HN TRANSACTION THAT DOES NOT EXIST IN THE FILER PROFILE DATABASE.

79H:	TARIFF FORMAT/CONTEXT ERROR

FORMAT OR CONTEXT ERROR

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.

VL9:	DRAWBACK CLAIMANTID INVALID

THIS ERROR MESSAGE INDICATES THAT THE FORMAT OF THE DRAWBACK CLAIMANT ID IS NOT A VALID IRS/SS/CUSTOMS ASSIGNED NUMBER FORMAT. VALID IRS FORMAT IS NN-NNNNNNNXX (WHERE 'XX'=SUFFIX); SS IS NNN-NN-NNNN; CUSTOMS ASSIGNED NUMBER IS YYDDPP-NNNNN.

VEN:	FDA LINE ALREADY REJECTED

THIS ERROR MESSAGE HAPPENS ONLY BETWEEN CUSTOMS ACS AND FDA'S SYSTEM. FDA SENDS INFORMATION VIA CUSTOMS TO THE FILER BY THE "LP" TRANSACTION. THIS ERROR OCCURS WHEN FDA HAS SENT AN "LP" INDICATING THAT THE ENTRY SHOULD BE REJECTED FOR FDA PURPOSES AND THE LINE IN QUESTION IS ALREADY IN FDA REJECT STATUS.

DKK:	NAFTA CLAIM - CANADIAN DATA REQD

THIS IS A DRAWBACK MODULE MESSAGE. FOR DRAWBACK DISKETTE, THE NAFTA INDICATOR WAS SET TO 'Y' IN THE 'CH' HEADER RECORD, OR FOR ABI, IT WAS SET TO '1'. EITHER WOULD INDICATE THAT THIS CLAIM IS A NAFTA CLAIM SUBJECT TO THE "LESSER OF" RULE. ACCORDINGLY, WE MUST HAVE THE NAFTA CNTRY IMPORT ENTRY DATA IN THE 'CI' (DISKETTE) OR 'D50' (ABI) RECORD(S) IF THE CLAIM TYPE IS '41' OR '44'. IF THE CLAIM TYPE IS '42' OR '45', THE NAFTA CTRY IMPORT ENTRY DATA WILL BE CONSIDERED OPTIONAL BY ACS, BUT THAT DOES NOT RELIEVE THE FILER OF THE STATUTORY REPORTING REQUIREMENT IF NAFTA IS APPLICABLE.

 Next 10 >>Showing results 1 to 25 of 1405