ABI Error Message

594:	INVALID DISTRICT /PORT OF UNLADING

THE PORT OF UNLADING (DIST/PORT CODE) MUST BE A VALID LOCATION AS SHOWN ON REGION/DISTRICT/PORT FILE (FOUR DIGIT DDPP). FILERS TRANSMIT THE PORT OF UNLADING FOR IMPORT SHIPMENTS IN THE ENTRY SUMMARY TRANSACTION (EI - 20 REC, POS 30-33) OR THE CARGO RELEASE TRANSACTION (HI - H1 REC, POS 65-68). IF THE PORT CODE TRANSMITTED DOES NOT EXIST ON THE DATABASE, THIS ERROR MESSAGE WILL RESULT. ***NOTE***- IN ADDITION TO THE ABOVE INFORMATION, A PORT THAT IS LISTED ON THE FILE MUST ALSO BE SET TO "Y" AS AN UNLADING PORT. IF THE PORT IS SET AS "N" FOR UNLADING PORT, THE ABOVE ERROR MESSAGE WILL BE GENERATED.

94M:	EXPECTED UNB SEGMENT NOT FND

EDIFACT SYNTAX ERROR. THE UNB (INTERCHANGE HEADER) SEGMENT IS MISSING.

1C6:	DUPLICATE ADD ERROR

THIS DRAWBACK MODULE MESSAGE MEANS THAT THE IMPORT ENTRY CITED ON THE DRAWBACK DISKETTE WAS SHOWN MORE THAN ONCE. SINCE THE DISKETTE AND ABI TRANSMISSION ARE CLAIM SUMMARIES, FILERS ARE INSTRUCTED TO ONLY SHOW AN IMPORT ENTRY ONE TIME AND SUMMARIZE THE TOTAL CLAIMED AMOUNT FOR THAT ENTRY. ON THE LEGAL PAPER CLAIM, A SINGLE IMPORT ENTRY MAY BE SHOWN MANY TIMES (FOR EXAMPLE, WHEN THEY BREAK A CLAIM DOWN BY PART NUMBER), BUT ON THE DISKETTE IT CAN ONLY APPEAR ONCE.

13M:	MANIFEST QTY MUST BE > ZERO

THE MANIFESTED QUANTITY IS REPORTED BY THE ENTRY FILER IN THE CARGO RELEASE APPLICATION (HI) IN THE HA REC, POS 51-58. IF THE FILER TRANSMITS ZERO AS THE MANIFESTED QUANTITY, THE ABOVE ERROR MESSAGE WILL BE GENERATED.

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.

AQ5:	INTERVENTION ALREADY FILED

AN INTERVENTION HAS ALREADY BEEN FILED AGAINST THE PROTEST. ONLY ONE INTERVENTION MAY BE FILED AGAINST ANY GIVEN 514 NAFTA PROTEST.

AFK:	CVD PYBL AMT INVALID; 35 REC

THE PAYABLE COUNTERVAILING DUTY AMOUNT TRANSMITTED IN REC 35, POS 38-48 DOES NOT EQUAL THE SUM OF THE COUNTERVAILING LINE ITEM AMOUNTS TRANSMITTED IN REC 60, POS 3-12.

VLY:	DRAWBACK ENTRY NOT FND FOR DELETE

THIS ERROR MESSAGE WILL APPEAR IF THE FILER USES THE ADDITION/DELETION CODE OF 'D' IN THE DRAWBACK 'CH' HEADER RECORD, BUT THE CLAIM RECORD DOES NOT EXIST IN ACS.

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.

94I:	SEARCH FAILURE IN UNH SEGMENT

THIS IS A UN/EDIFACT SYNTAX ERROR MESSAGE. IT INDICATES THAT A SUB-ELEMENT IS MISSING OR INVALID.

79L:	QUOTA-ENTRY SUMMARY REQUIRED

A MATCHING QUOTA RECORD EXISTS WITHOUT THE QM-TYPE = S

VHH:	DT HS7: INVALID ISO CODE

IF THE FILER TRANSMITS DOT INFORMATION FOR BOX 05, 06, OR 12, THE ISO CODE OF THE COUNTRY OF ORIGIN IS REQUIRED. IF A CODE NOT FOUND ON THE COUNTRY CODE FILE IS TRANSMITTED IN POSITIONS 30-31 OF THE DT01 RECORD, THIS ERROR MESSAGE WILL BE GENERATED.

58G:	DIST.IN 10 REC NOT = TO B REC

THE FIRST TWO CHARACTERS OF THE DISTRICT/PORT OF ENTRY CODE (THE OLD DISTRICT CODE) IN THE "10" RECORD OF THE ENTRY SUMMARY (EI) MUST AGREE WITH THE FIRST TWO CHARACTERS OF THE PROCESSING DISTRICT/PORT CODE FOR THE "B" RECORD. THIS ALSO APPLIES FOR REMOTE LOCATION FILING ENTRIES. THE ONLY EXCEPTION IS THE CODES THAT APPLY TO THE NEW YORK AREA (10,46,47). FOR EXAMPLE, A "B" RECORD OF 4601 CAN BE TRANSMITTED WITH ENTRY SUMMARIES WITH A 10 RECORD PORT OF 4701, 1001, AS WELL AS 4601.

215:	INVALID TEAM NUMBER

REFERENCE APPLICATION JJ, REC D10, POS 40-42:  FOR DRAWBACK ENTRY TYPES WHERE THE 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

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.

ACP:	IMPORTER NUMBER IS INACTIVE

THIS MESSAGE CAN OCCUR AS A RESPONSE TO CARGO DATA INPUT TRANSACTION OR ENTRY SUMMARY TRANSACTION OR AS A RESPONSE TO A QUERY OF AN IMPORTER/BOND TRANSACTION (CATAIR, PAGE QIB-7). AN IMPORTER IS PUT INTO "INACTIVE" STATUS WHEN THERE HAVE BEEN NO CARGO SELECTIVITY, ENTRY SUMMARY OR ELECTRONIC INVOICE TRANSACTIONS DURING THE PRECEDING 18 MONTHS. TO REACTIVATE, FILER MUST SEND IN AN "ADD CF-5106" TRANSACTION WITH THE IMPORTER'S FULL NAME AND ADDRESS INFORMATION. IF THE IMPORTER NUMBER IS A CUSTOMS ASSIGNED NUMBER, FILER MUST TURN IN A CF 5106 TO CUSTOMS FOR REACTIVATION.  NOTE - THIS MESSAGE MAY NO LONGER BE GENERATED IN RESPONSE TO HI, CARGO RELEASE, INPUT TRANSACTIONS. SEE ERROR 66A.

69A:	ORIGIN COUNTRY/TARIFF NBR INVALID

THIS ERROR MESSAGE RESULTS WHEN A REQUIREMENT BETWEEN THE TARIFF NUMBER REPORTED IN THE 50 REC, POS 4-13, AND THE COUNTRY OF ORIGIN REPORTED IN THE 40 REC, POS 6-7, IS VIOLATED. THE MOST COMMON EXAMPLE OF THIS WOULD BE THE USE OF ANY COUNTRY OTHER THAN "US" WITH TARIFF NUMBERS IN THE 98010010NN RANGE. ALSO, CHAPTER 9999 NUMBERS MAY BE SPECIFICALLY LINKED TO EITHER CANADA OR MEXICO. IF THE COUNTRY OF ORIGIN IS NOT APPROPRIATE TO THE TARIFF NUMBER IN CHAPTER 99, THIS MESSAGE WILL ALSO RESULT. A LESS COMMON EXAMPLE WOULD THE ATTEMPTED USE OF CERTIFIED HAND-LOOM TEXTILE ARTICLES (AS FOLKLORE ARTICLES) WITH A COUNTRY OF ORIGIN THAT IS NOT ONE OF THE ACCEPTABLE COUNTRIES FOR CERTIFIED FOLKLORE ARTICLES. PAGE ENS-48 OF THE CATAIR LISTS THE CURRENTLY ACCEPTABLE COUNTRIES OF ORIGIN FOR SELECTED TARIFF NUMBERS (NOTE 2).

FD3:	AFFIRMATION COMPLI TYPE INVALID

COMPLIANCE TYPE HAS TO BE ALPHANUMERIC WITH NO SPACES.

ED0:	SYSTEM PROBLEM - CALL CLIENT REP

THIS "GENERIC" MESSAGE WILL SHOW UP PERIODICALLY, USUALLY WITH DATABASE ERRORS. AS OF JULY 1999, THIS MESSAGE IS BEING ASSIGNED TO ENTRIES IN WHICH THE FILER IS ATTEMPTING TO USE SPI "E" WITH HTS 9802008015 (WHICH IS ELIGIBLE FOR CARIBBEAN BASIN INITIATIVE FILING UNDER SPI "E") WITH A SECOND TARIFF NUMBER THAT IS NOT CBI ELIGIBLE. IN THIS CASE, THE FILER MAY NOT CLAIM "E" FOR THE CUSTOMS LINE IN QUESTION. AS STATED ABOVE, THIS ERROR MESSAGE CAN CHANGE MEANINGS AS DATABASE PROBLEMS WARRANT.

SUS:	WARNING - SURETY SANCTIONED

FOR RECONCILIATION, THE SURETY ORIGINALLY GIVEN ON THE IMPORT ENTRIES IS NOW SANCTIONED.

4BB:	SELECTIVITY ALREADY PERFORMED

SELECTIVITY IS PROCESSED IN ABI PRIOR TO ONLINE PROCESSING IF THE ARRIVAL DATE OF THE ENTRY IS LESS THAN 6 DAYS IN THE FUTURE. ONCE SELECTIVITY HAS BEEN PERFORMED, EVEN THOUGH THE ENTRY MAY BE IN ABI STATUS, A REPLACEMENT OF THE ENTRY BY THE BROKER THROUGH ABI IS NOT ALLOWED.

2C1:	BOND EXPIRED

A VALID BOND WAS ON FILE FOR IMPORTER, BUT IT HAS EXPIRED. NOTE: THIS MESSAGE WILL ALSO OCCUR IF THE FILER USES A VALID BOND THAT IS NOT A TYPE 1 OR 1A1 (THE ONLY VALID BOND TYPES FOR IMPORTATIONS BY IMPORTERS). CLIENT REPS CAN CHECK THE BOND FILE TO DETERMINE WHAT TYPE BOND IS ON FILE FOR THE IMPORTER OF RECORD NUMBER. NOTE: IF THE PORT PROCESSING THE BOND DOES NOT COMPLETE THE UPDATE ACTION, AN ABI FILER TRANSMITTING AN ENTRY SUMMARY THAT REFERENCES AN 'INCOMPLETE' BOND WILL RECEIVE THIS ERROR MESSAGE AS WELL.

VNO:	EXPORT SUM INVALID FOR BOND TYPE

IN THE DRAWBACK MODULE THE EXPORT SUMMARY INDICATOR MAY ONLY BE A 'Y' (OR '1' IF ABI) IF THE BOND TYPE CODE IS NOT '0' (WOULD BE EITHER '8' OR '9'), UNLESS THE GOVERNMENT CLAIM INDICATOR IS ALSO 'Y' (OR '1' IF ABI). IF 'Y' (OR '1' IF ABI) IS USED AND THE CONDITION IS NOT CORRECT, MESSAGE VNO APPEARS.

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.

EID:	PAYMENT TERMS REQUIRED

THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSMISSION (APPLICATION CI). PAYMENT TERMS ARE TRANSMITTED IN THE C02 REC, POS 6-75. THIS FIELD MAY NOT BE BLANK OR THIS ERROR MESSAGE WILL BE GENERATED.

 Next 10 >>Showing results 1 to 25 of 1405