ABI Error Message

EJS:	SUPPLIER CODE DOES NOT MATCH C01

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSACTION (APPLICATION CI). THE C08 RECORD CONTAINS SPACE TO REPORT ONE OF ELEVEN PARTY QUALIFIER CODES (SEE CATAIR PAGE AII-17 FOR A LIST OF THE VALID CODES). IF THE CODE SELECTED IS "SU", IT MUST BE AN EXACT MATCH, IN MID FORMAT, TO THE SUPPLIER CODE TRANSMITTED IN THE C01 RECORD, POS 5-19. IF THE CODE DOES NOT AGREE, THIS ERROR MESSAGE WILL BE GENERATED.

2AI:	INVALID BOND TYPE

A SHORT LISTING OF CURRENT BOND TYPES AND THEIR CORRESPONDING ACTIVITY CODES CAN BE FOUND IN THE CATAIR ON PAGE QIB-8. NOTE: ABI FILERS WHO DO BOND QUERIES WILL RECEIVE A SINGLE ALPHA CHARACTER CODE DESIGNATING WHICH TYPE OF BOND IS ON FILE, IF ANY, FOR THE IMPORTER BEING QUERIED. THE FILER'S SOFTWARE SHOULD TRANSLATE THE CODE INTO THE APPROPRIATE BOND TYPE AND DESCRIPTION.

Q17:	DSI FILE MISSING STATEMENT IMPORTER

THE STATEMENT NUMBER IN THE 'QT' RECORD IS IDENTIFIED AS AN IMPORTER STATEMENT WITH A SPECIFIC IMPORTER NUMBER; THE PAYOR UNIT NUMBER PROVIDED IN THE 'QT' RECORD IS NOT ASSIGNED TO THAT IMPORTER ON THE DATA FILE.

VL3:	DRAWBACK DDPP INVALID

IN THE DRAWBACK MODULE THIS MESSAGE MEANS THAT THE FILER HAS GIVEN US A CLAIM THAT DOES NOT USE ONE OF THE EIGHT CORRECT PORT CODES BY FILING LOCATION:  0401, 1001, 2002, 3901, 5201, 5301, 2704, 2809

FD3:	AFFIRMATION COMPLI TYPE INVALID

COMPLIANCE TYPE HAS TO BE ALPHANUMERIC WITH NO SPACES.

AQ9:	PROTESTANT DATA NOT APPLICABLE

PROTESTANT NAME AND ADDRESS INFORMATION IS REQUIRED ONLY WHEN THE PROTESTANT TYPE IS "O" (OTHER) AND "F" (FOREIGN). PROTESTANT IDENTIFICATION INFORMATION IS NOT ACCEPTED UNDER ANY OTHER CIRCUMSTANCES.

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.

07I:	VESSEL CODE & NAME SUBMITTED

THIS MESSAGE IS GENERATED IN RESPONSE TO A CARGO RELEASE DATA INPUT TRANSACTION (APPLICATION HI). ABI WILL ACCEPT THE VESSEL NAME, BUT NOT THE VESSEL CODE. IF BOTH ARE TRANSMITTED, THIS ERROR MESSAGE WILL BE ISSUED. (NOTE - 5-CHARACTER VESSEL CODES ARE NO LONGER USED).

293:	INVALID TARIFF FORMAT

TARIFF IN REFERENCE BOUND IS IN INVALID FORMAT .

VLJ:	DUP MFGR # ENCOUNTERED/CERT MFGR

THIS DRAWBACK MODULE ERROR MESSAGE MEANS THAT THE FILER HAS GIVEN US THE SAME CM NUMBER (CERT MFGR #) MORE THAN ONCE ON THE CLAIM. JUST AS WITH IMPORT ENTRIES CLAIMED ON THE DISKETTE OR VIA ABI, THE CM NUMBER SHOULD ONLY APPEAR ONCE WITH THE TOTAL DRAWBACK CLAIMED FOR THAT CM.

BRM:	POSSIBLE FEE MISMATCH

THE ORIGINAL FEE AMOUNT FOR A GIVEN FEE CLASS CODE IN THE RECON'S 'R21' RECORD DOES NOT AGREE WITH WHAT USCS SHOWS AS BEING THE FEE AMOUNT FOR THAT CLASS CODE ON THE ORIGINAL IMPORT ENTRY. THIS MESSAGE USUALLY RESULTS WHEN ABI ATTEMPTS TO VERIFY THAT THE INDIVIDUAL FEE CLASS AMOUNTS ON THE IMPORT ENTRY AGREE WITH THE AMOUNTS REPORTED IN THE RECON ENTRY (R21 RECORD). IF THE IMPORT ENTRY HAS BEEN RED-LINED DURING THE LIQUIDATION PROCESS, THE USFI RECORD (WHERE FEES ARE DISPLAYED BY CLASS CODE AND AMOUNT) WILL BE BLANK AND THE LNLI RECORDS (ENTRY LINE DATA FOR THE IMPORT ENTRY) IS ALSO LIKELY TO BE BLANK. THUS ABI HAS NO FILE TO SEARCH TO VERIFY THE HMF OR MPF AMOUNT CLAIMED BY THE RECON FILER IN ITS R21 RECORD. THIS MESSAGE IS A WARNING, HOWEVER, AND WILL NOT, IN AND OF ITSELF, CAUSE A RECON ENTRY TO BE REJECTED.

VP4:	DEFER. DUTY CLAIM ALREADY ON FILE

THIS MESSAGE OCCURS IN THE NAFTA DUTY DEFERRAL MODULE. IF AN AUTOMATED CLAIM IS ALREADY ON FILE THIS ERROR MESSAGE WILL OCCUR.

4GH:	INVALID CNTRY CODE

COUNTRY CODE MUST BE VALID TWO CHARACTER ALPHABETIC ISO CODE. TO VIEW VALID COUNTRY CODES DO RFJL 2/AA. IN VVCU FUNCTION, VALID CNTRY CODE = ISO-CODE WITH ACTIVE RECORD ON VVCR

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.

VGA:	FD701: INV LINE#/SEQ

THIS ERROR MESSAGE RESULTS WHEN A FILER SENDS AN FDA CORRECTION (CP TRANSACTION) TO RESPOND TO AN FDA DT REJECT MESSAGE AND THE CUSTOMS LINES THAT THEY ARE SENDING IN THE FDA CORRECTION DO NOT MATCH THE EXACT SEQUENCE OF LINES IN THE SELECTIVITY RECORD. WHEN A CORRECTION IS DONE, THE FILER MUST SEND THE CUSTOMS LINES (WITH THE CORRESPONDING FDA DATA OR DISCLAIM AS APPLICABLE) IN THE EXACT ORDER AS IT APPEARS ON THE SELECTIVITY LINE ITEM SCREEN. THE FILER MUST ALSO SEND ALL CUSTOMS LINES WHETHER OR NOT THEY ARE FDA REGULATED. CHECK THE ORDER OF THE TARIFF NUMBERS IN THE CP SEND AGAINST THE SELECTIVITY LINE ITEM SCREEN. THEY MUST MATCH EXACTLY. THIS MESSAGE ALSO RESULTS WHEN A FILER ATTEMPS TO START A FDA LINE NUMBER WITHIN A CUSTOMS LINE WITH A NUMBER OTHER THAN 001. THE MOST COMMON OCCURANCE IS WHEN CUSTOMS LINE 001 IS SENT AND, FOR EXAMPLE FDA LINES 001 AND 002 ARE SENT WITH IT. THEN THE FILER SENDS CUSTOMS LINE 002 AND STARTS THE FDA LINE NUMBERING WITH 003. THIS REJECT WILL ALSO OCCUR IF THE FILER SENDS BOTH AN FD0 (DISCLAIM) AND FDA DATA FOR THE SAME CUSTOMS LINE ON AN ENTRY SUMMARY INPUT TRANSACTION.

125:	HIGH NUMBER NOT GREATER THAN LOW

DOCUMENT NUMBER: -THE HIGH DOCUMENT NUMBER MUST BE GREATER THAN THE LOW DOCUMENT NUMBER IN A RANGE. IT IS PERMISSIBLE FOR THE HIGH DOCUMENT NUMBER AND THE LOW DOCUMENT NUMBER TO BE THE SAME WHERE A SINGLE DOCUMENT NUMBER IS BEING ADJUSTED.

42D:	EST TAX NO MATCH TO COMPUTED TAX

IR TAX ENTERED IS NOT WITHIN $3.00 OF COMPUTED IR TAX.

AEP:	ERROR IN A32 REC; RLSE 3

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

AEY:	42 SENT; NOT REQUIRED

IN THE AUTOMATED INVOICE INTERFACE PROGRAM THIS ERROR MESSAGE WILL OCCUR IF AUTOMATED FILER SENDS A 42 INVOICE RECORD WITHOUT AN "E" (ELECTRONIC INVOICE INDICATOR) IN POSITION 56 OF THE 10 RECORD. IF THE FILER SENDS THE "E" THEY MUST SEND THE 42 RECORD.

DKU:	APPV'D RULING REQD FOR DBK PAYMT

THIS "WARNING" MESSAGE (NOT A FATAL ERROR) OCCURS IN THE AUTOMATED DRAWBACK MODULE AND WILL APPEAR IF THE DRAWBACK CLAIM TYPE IS '41' OR '44' AND NO VALID RULING (CONTRACT) NUMBER IS GIVEN VIA ABI.

VKB:	HLT: SEARCH NUMBER REQUIRED

TABLE NAME AND SEARCH NUMBER ARE BOTH REQUIRED TO CONSTRUCT A VALID TABLE LOCATE/INQUIRY DEFINITION.

VHQ:	DT HS7: MAKE REQUIRED

THIS ERROR MESSAGE OCCURS IN THE DOT INTERFACE. THE MAKE (NAME OF COMPANY THAT MANUFACTURED VEHICLE) SENT IN POSITIONS 5-19 OF THE DT02 RECORD IS MANDATORY IF BOXES 03, 05 OR

VLM:	DRAWBACK DELETE CODE INVALID

THIS MESSAGE WILL APPEAR IF THE FILER HAS USED AN ADDITION/DELETION CODE OF 'D' ON THE 'CH' HEADER RECORD OF THE DRAWBACK DISKETTE (THE D10 ABI RECORD) AND THE CLAIM IS ALREADY IN A CUSTOMS STATUS. A DELETE OF A CLAIM BY A FILER CAN ONLY BE HONORED IF THE CLAIM IS STILL IN 'ABI' STATUS. ALL CLAIMS CREATED BY DISKETTE OR VIA ABI ARE PLACED IN ABI STATUS BY ACS WHEN FIRST ACCEPTED ERROR-FREE. THE SAME LOGIC APPLIES TO IMPORT ENTRIES FILED ELECTRONICALLY VIA ABI. ONCE IN CUSTOMS STATUS, THEY CANNOT BE DELETED BY THE FILER. NOTE: THE CLAIM CANNOT BE DELETED AT ALL IF ACCELERATED DRAWBACK HAS BEEN PAID. IF ACCELERATED DRAWBACK HAS BEEN PAID AND THE FILER WISHES TO DELETE, THE CLAIM WILL HAVE TO BE LIQUIDATED "NO DRAWBACK" AND A BILL ISSUED FOR REPAYMENT OF THE ACCELERATED DRAWBACK. IF ACCELERATED HAS NOT BEEN PAID, BUT THE ENTRY IS IN A CUSTOMS STATUS, IT CAN BE CANCELLED, BUT NOT DELETED.

4BL:	ENTRY WAS NOT ORIGINALLY ABI

ALTHOUGH THE DISKETTE PROGRAM IS NOT ABI AND THE CLAIMS ARE NOT ABI, WE USE SIMILIAR PROGRAMMING AS THE SOURCE OF CLAIM CREATION. IF THE CLAIM HAS BEEN COMPLETELY INPUT MANUALLY AND RECORDS EXIST AT THE TIME THE ABI OR DISKETTE JOBS ARE RUN, THE DISKETTE AND ABI WILL NOT PERMIT THE OVERLAY OF DATA.

183:	INVALID REGION/DISTRICT/PORT

REGION/DISTRICT/PORT IS NOT VALID ON THE REGION DISTRICT PORT FILE.

 Next 10 >>Showing results 1 to 25 of 1405