|
|
|
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. |
|
VG8: |
FEI # INVALID,2 LEADING 0'S REQD |
| THIS ERROR MESSAGE OCCURS IN THE FEI (FDA ESTABLISHMENT IDENTIFIER) QUERY, SPECIFICALLY WHEN A QUERY (Q) IS SENT IN POSITION 5 OF THE FDPP 10 RECORD AND THE FEI NUMBER BEING QUERIED IN POSITIONS 6-17 DOES NOT START WITH A MINIMUM OF TWO LEADING ZEROES. |
|
2CI: |
INBOND - INVALID CHECK DIGIT |
| ENTRY SUMMARY OR CARGO RELEASE INPUT TRANSACTIONS THAT REPORT PAPERLESS MASTER INBOND NUMBERS (THOSE STARTING WITH "V") MUST TRANSMIT A VALID MIB NUMBER, INCLUDING THE LAST DIGIT (CHECK DIGIT). IF THE LAST DIGIT IS NOT CORRECT, PRESUMING THAT THE FIRST 10 DIGITS ARE CORRECT, THIS ERROR MESSAGE WILL RESULT. THE FILER SHOULD RECONFIRM THE ENTIRE PAPERLESS MIB NUMBER WITH THE ISSUING CARRIER. NOTE: ERRORS IN THE CHECK DIGIT FOR AIR WAYBILLS USED AS INBOND NUMBERS OR FOR CONVENTIONAL (9 DIGIT ALL NUMERIC) INBOND NUMBERS WILL GENERATE ERROR MESSAGE 361. |
|
506: |
CALC. DUTY DOES NOT MATCH EST. |
| THE TOTAL DUTY CALCULATED FROM THE ENTRY LINE ITEMS DOES NOT MATCH THE ESTIMATED DUTY FOR THE ENTRY. EACH LINE ON A MULTI-LINE SUMMARY SHOULD REFLECT THE EXACT DUTY AMOUNT DUE, BASED ON THE DUTY RATES APPLICABLE TO THE TARIFF NUMBER. HOWEVER, ABI WILL ALLOW A DIFFERENCE, PER LINE, OF UP TO $2.99 (PLUS OR MINUS) BETWEEN THE ACTUAL CALCULATED DUTY AMOUNT AND THE AMOUNT TRANSMITTED BY THE ABI FILER. THIS $2.99 DIFFERENCE ALSO APPLIES TO THE ENTRY, AS A WHOLE. THUS, WHILE INDIVIDUAL LINES MAY BE ALLOWED WITH THE DUTY DISCREPANCY CITED ABOVE, THE ENTRY MAY STILL BE REJECTED IF THE TOTAL DUTY AMOUNT TRANSMITTED (90 REC, POS 3-13) IS MORE THAN $2.99 ABOVE OR BELOW THE AMOUNT CALCULATED BY ABI AS BEING THE ACTUAL DUTY FOR ALL LINES ON THE SUMMARY. |
|
0IJ: |
ULT CON ENTRY SUMMARY MISMATCH |
| THE ENTRY ULTIMATE CONSIGNEE DOES NOT MATCH THE SELECTIVITY RECORD. PLEASE CORRECT THE SELECTIVITY RECORD IF IT IS INCORRECT. |
|
DLD: |
WARNING-NO ACCEL APPV'D-CHK PRIVS |
| THIS MESSAGE OCCURS IN THE AUTOMATED DRAWBACK MODULE. IT IS A 'WARNING', NOT A FATAL ERROR, THAT APPEARS IF THE CLAIMANT HAS APPLIED FOR THE ACCELERATED PRIVILEGE, BUT HAS NOT YET BEEN APPROVED. MESSAGE DLD WILL CONTINUE TO BE A WARNING ONLY AFTER 4/6/1999. |
|
FD3: |
AFFIRMATION COMPLI TYPE INVALID |
| COMPLIANCE TYPE HAS TO BE ALPHANUMERIC WITH NO SPACES. |
|
4NN: |
LINE ITEM VALUE ERROR |
| IF A FILER TRANSMITS A CARGO RELEASE DATA TRANSACTION (APPLICATION HI), AND ALSO ELECTS TO REPORT VALUES AT THE LINE ITEM LEVEL (H5 REC, POS 45-54), THE TOTAL OF ALL VALUES IN THE H5 RECORD MUST EQUAL THE AMOUNT SHOWN AS THE TOTAL ENTRY VALUE (H2 REC, POS 29-38). THE TOTAL DOES NOT AGREE, THIS ERROR MESSAGE WILL BE GENERATED. |
|
VMM: |
INVALID WHSE ENTRY SUMMARY |
| THE WHSE SUMMARY CITED ON THE 30 REC EITHER 1) DOES NOT EXIST, 2) IS NOT A TYPE 21 OR 22 OR 3) IS LIQUIDATED, RELIQUIDATED, OR CANCELLED. |
| "
4GE: |
NO QUOTA RECORD FOR THIS TARIFF |
| THE TARIFF, AS INPUT, HAS NO QUOTA RECORD ON THE QUOTA FILE. |
|
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. |
|
17I: |
UNKNOWN APPLICATION CODE |
| THE ABI APPLICATION CODE ENTERED ON THE 'B' RECORD WAS NOT FOUND IN THE APPLICATION CODE FILE. ACTION: CORRECT THE CODE ENTERED ON THE 'B' RECORD AND RESTART THE APPLICATION. |
|
2DG: |
ENTRY SUMMARY IN ABI STATUS |
| AN ERROR CONDITION WAS RETURNED BY THE DATE SUBROUTINE (SPX152) WHEN THE ENTRY/COLLECTION DATE WAS BLANK OR INVALID. THIS CONDITION OCCURS WHEN THE SUMMARY IS ON FILE IN ABI STATUS. |
|
AR9: |
PROTESTANT ADDRESS INVALID |
| PROTESTANT TYPE "F" (FOREIGN) REQUIRES FOREIGN ADDRESS; PROTESTANT TYPE "O" (OTHER) REQUIRES DOMESTIC ADDRESS. DOMESTIC AND CANADIAN ADDRESSES AND ZIP CODES ARE VALIDATED AGAINST "CODE-1", ANY INVALID ADDRESSES OR ZIP CODES ARE REJECTED. U.S. ADDRESSES REQUIRE ABBREVIATED POSTAL CODE FOR STATE AND THE ISO CODE "US". CANADIAN ADDRESSES REQUIRE CANADIAN PROVINCE CODE AND THE ISO CODE "CA". THE CANADIAN POSTAL ZIP CODE IS ALSO REQUIRED. MEXICAN ADDRESSES REQUIRED THE CODE "FN" (FOREIGN) IN PLACE OF A STATE CODE AND THE IOS CODE "MX". POSTAL ZIP CODES ARE NOT USED FOR MEXICAN ADDRESSES. |
|
RBU: |
RECON FILER NOT ON FILE |
| THIS MESSAGE MEANS THAT THE FILER CODE GIVEN ON THE RECONCILIATION DOES NOT EXIST IN ACS. |
|
VKH: |
HLT: DESCRIPTION REQUIRED |
| DESCRIPTION IS REQUIRED TO CREATE A TABLE LOCATE/INQUIRY DEFINITION. |
|
ARG: |
PROTESTANT TYPE REQUIRED |
| A VALID VALUE IS REQUIRED IN THE PROTESTANT TYPE FIELD VALID VALUES ARE: D - DRAWBACK CLAIMANT F - FOREIGN MAUFACTURER/PRODUCER/EXPORTER I - IMPORTER/CONSIGNEE M - MASTER OF VESSEL S - SURETY V - VESSEL OPERATOR O - OTHER |
|
VKN: |
HLT:O INVALID W/ OVERRIDE CRIT.N |
| SUBSEQUENT SORT ORDER O=OVERRIDE IS INVALID WHEN OVERRIDE CRITERIA N=NO. |
|
VKV: |
HLR: MAX 15 RETURN FLDS EXCEEDED |
| A MAXIMUM OF FIFTEEN FIELDS MAY BE SELECTED TO RETURN VALUES TO THE INVOKING SCREEN. THE FIELD(S) IN ERROR EXCEED THIS LIMIT. |
|
DK0: |
SCHED B NUMBER NOT ON FILE |
| THIS MESSAGE OCCURS IN THE AUTOMATED DRAWBACK MODULE. THE MESSAGE SIMPLY MEANS THAT THE SCHEDULE B NUMBER, AT THE 6, 8, OR 10 DIGIT LEVEL DOES NOT EXIST IN THE FILE. NORMALLY, THIS OCCURS WHEN THE FILER HAS GIVEN 10 DIGIT ON OLDER RECORDS. FOR OLDER RECORDS, IF THE FILER USES 6 DIGITS (OR 8 IF PETROLEUM) THE PROBLEM IS MINIMIZED. |
|
BE1: |
C/O CANADA REQ'D FOR EXCISE NBR |
| A BEER EXCISE # WAS ENTERED FOR A LINE THAT WAS A COUNTRY OF ORIGIN OF OTHER THAN 'CA' (CANADA). |
|
VHC: |
FD 701:PHONE NBR MUST BE NUMERIC |
| THIS ERROR MESSAGE OCCURS WHEN NON-NUMERIC CHARACTERS ARE INPUT INTO THE "CONTACT PHONE NUMBER" FIELD, REC FD04, POS 29-38. THIS IS AN OPTIONAL FIELD. A COMMON PROBLEM IS THAT THE USER WILL SEND A "CONTACT NAME" (REC FD04 POS 19-28) THAT IS LONGER THAN 10 CHARACTERS AND THE FILER'S PROGRAM ALLOWS THE EXTRA CHARACTERS TO SPILL OVER INTO THE PHONE NUMBER FIELD. ALSO, PHONE NUMBERS MUST INCLUDE THE AREA CODE. IF THIS PART OF THE PHONE NUMBER ELEMENT IS LEFT BLANK, ERROR VHC ALSO RESULTS. |
|
AP3: |
HEADER/DETAIL DATA REJECTED |
| THIS IS A SUMMARY TYPE MESSAGE. IT SIMPLY POINTS TO ERRORS MADE IN OTHER RECORDS CAUSING THE TRANSACTION TO BE REJECTED. |
|
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. |
|
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. |
Next 10 >>Showing results 1 to 25 of 1405
If you find this information helpful, please leave a donation to support Informed Trade International's ongoing mission to help importers improve their understanding of international trade.
|
|