|
AR8: |
PROTESTANT ID FORMAT INVALID |
VALID FORMATS FOR THE PROTESTANT IDENTIFICATION NUMBER ARE: NNN CUSTOMS ASSIGNED SURETY CODE NN-NNNNNNNXX EMPLOYER IDENTIFICATION NUMBER (EIN) OR INTERNAL REVENUE SERVICE NUMBER (IRS) NNN-NN-NNNN SOCIAL SECURITY NUMBER YYDDPP-NNNNN CUSTOMS ASSIGNED NUMBER (NEW FORMAT ONLY) AAANNNNNN CANADIAN EMPLOYER NUMBER AAANNNNNN CANADIAN IMPORTER/EXPORTER NUMBER AAAAYYMMDDXXX MEXICAN FEDERAL TAX REGISTRY NUMBER (INDIVIDUAL) AAAYYMMDDXXX MEXICAN FEDERAL TAX REGISTRY NUMBER (CORPORATE) |
THIS MESSAGE OCCURS IN THE AII MODULE. THE ENTRY FILER IS NOT AUTHORIZED IN THE DISTRICT/PORT FOR THE TRANSACTION. |
VN3: |
CERT MFGR UOM INVALID |
IN THE DRAWBACK MODULE IF A UNIT OF MEASURE IS GIVEN ON THE CM (CERT MFGR), MUST BE A VALID 3 ALPHA-NUMERIC CHARACTER CODE (E.G. BBL, CWT, PCS). ALSO, IT MEANS THAT IF A QUANTITY IS GIVEN, A UNIT OF MEASURE MUST BE REPORTED. |
8VP: |
MULTIPLE TRANS FOR SAME BILL NBR |
THIS MESSAGE OCCURS IN THE BILL OF LADING UPDATE (LN) FUNCTION. MULTIPLE L3 RECORDS CAN BE SENT BUT THE BILL OF LADING INFORMATION CANNOT BE IDENTICAL OR THIS MESSAGE WILL RESULT. THE BILL OF LADING INFORMATION MUST BE DIFFERENTIATED BY USE OF DIFFERENT MASTER BILL NUMBERS OR, THE MASTER BILLS CAN BE THE SAME IF THE HOUSE BILLS ARE DIFFERENT (AIRWAY BILLS AND HOUSE AIRWAY BILLS IN THE AIR AMS ENVIRONMENT). |
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. |
AR7: |
NOTIFY SUB. DATA REJECTED |
NOTIFY SUBSTITUTE DATA REJECTED. |
AQS: |
AFR QUESTIONS RESPONSE REQ'D |
WHEN APPLYING FOR FURTHER REVIEW, THE FILER MUST RESPOND TO 3 FURTHER REVIEW CRITERIA QUESTIONS. VALID RESPONSES ARE 'Y' OR 'N'. THE ANSWERS TO THOSE QUESTIONS ARE MISSING. |
EJ9: |
INVALID INVOICE NUMBER FORMAT |
INVOICE NUMBERS CAN CONSIST ONLY OF LETTERS, NUMBERS, SLASHES, OR DASHES. TRAILING SPACES ARE ALLOWED, IMBEDDED SPACES ARE NOT. LETTERS MUST BE IN UPPER CASE. NOTE: AS OF MAY 1995, THE SLASH (/) IS NO LONGER PERMITTED AS A VALID CHARACTER IN THE INVOICE NUMBER. THE INVOICE NUMBER IS TRANSMITTED IN THE C01 REC, POS 20-36. |
AF0: |
CITY HAS LEAD SPACE OR SPEC CHAR |
FILERS CAN ADD ADDRESS INFORMATION IN SEVERAL APPLICATIONS. IF THE CITY PORTION OF THE ADDRESS IS SENT WITH A SPACE IN THE FIRST POSITION, THIS ERROR MESSAGE WILL RESULT. |
VBY: |
HS7:CODE/MFR MUST BE ALPHANUMERIC |
THE FIELD FOR THE TIRE MANUFACTURER CODE (RECORD DT01, POS 38-40) OR THE TIRE MANUFACTURER BRAND NAME (RECORD DT01, POS 41-60) WILL ACCEPT ONLY LETTERS AND NUMBERS. IF ANY OTHER CHARACTER IS TRANSMITTED IN EITHER FIELD, THIS MESSAGE WILL RESULT. SLASHES, DASHES, PERIODS, ETC. WILL NOT BE ALLOWED IN THESE ELEMENTS. |
461: |
PAY DUE DATE INVALID/CONFLICTING |
THIS MESSAGE WILL RESULT IF THE FILER TRANSMITS A PAYMENT DUE DATE THAT IS AT LEAST ONE WORKING DAY IN THE FUTURE WHEN COMPARED TO THE ABI TRANSMISSION DATE. THE PAYMENT DUE DATE IS TRANSMITTED IN THE 30 RECORD, POS 54-59. |
VDV: |
FTZ PRVLGED/TARIFF EDIT SUSPENDED |
THIS ERROR MESSAGE IS A WARNING THAT OCCURS WHEN AN FTZ PRIVILEGED ENTRY IS SUBMITTED WITH A TARIFF NUMBER THAT IS NOT ON FILE USING THE PRIVILEGE DATE. THE FILER WILL ALSO RECEIVE "DUTY COMPUTATION NOT PERFORMED" AND "ENTRY ACCEPTED WITH WARNINGS". |
ASW: |
JUSTIFICATION/ARGS REJECTED |
JUSTIFICATION/ARGUMENTS REJECTED. THIS MESSAGE WILL USUALLY BE ACCOMPANIED BY ANOTHER MESSAGE THAT INDICATES WHY THE JUSTIFICATION IS NOT APPROPRIATE EXAMPLE, IF ADDITIONAL ARGUMENTS ARE SUBMITTED VIA APPLICATION SJ (SERVICEREQUEST), NO ADDITIONAL ARGUMENTS WILL BE PERMITTED IF THE PROTEST IN QUESTION HAS BEEN REFERRED FOR FURTHER REVIEW. ERROR MESSAGE "ASN" WILL MOST LIKELY ACCOMPANY THIS ERROR MESSAGE IN SUCH A CASE. |
VOK: |
INVALID REMOTE PROC DDPP |
IN A REMOTE ENTRY TRANSACTION, THE PROCESSING DDPP SENT IN THE 'B' RECORD, POSITIONS 4-7, MUST BE A VALID DDPP IN THE DISTRICT/PORT FILE. |
AEW: |
PAPERLESS ENVIRONMENT REQUIRES 42 |
THIS MESSAGE OCCURS IN THE ABI AUTOMATED INVOICE SCENARIO. THE FILER HAS SENT AN "E" IN POSITION 56 OF THE ENTRY SUMMARY TRANSACTION IDENTIFYING THE TRANSACTION AS AN AII ENTRY BUT THEY DID NOT SEND THE REQUISITE '42' RECORD CONTAINING THE INVOICE INFORMATION. |
API: |
AFR REQUEST IND. INVALID |
AN APPLICATION FOR FURTHER REVIEW, INDICATED BY 'R', APPLIES ONLY TO TYPE 514 PROTESTS, AND MUST BE REQUESTED DURING FILING AND AMENDMENT PERIOD, EITHER INITIAL FILING OR BY AN AMENDMENT FILING. THE VALUE SUBMITTED IN THE AFR REQUEST FIELD IS NOT 'R'. |
29F: |
"Y" RECORD MISSING OR INVALID |
THIS MESSAGE INDICATES THAT THE "Y" RECORD IS MISSING FROM THE INPUT TRANSACTION. THE ERROR MESSAGE DOES NOT USUALLY DISPLAY WHEN THIS ERROR OCCURS. |
VMC: |
HLO: SORT ORDER MUST BE A/D |
THE SORT ORDER CODE IS REQUIRED AND MUST BE A=ASCENDING D=DESCENDING. |
ADS: |
RLSE ON FILE-CONSL NOT ALLOWED |
AN ENTRY SUMMARY INPUT TRANSACTION (APPLICATION EI) CANNOT USE AN ENTRY NUMBER THAT WAS PREVIOUSLY USED IN A RELEASE TRANSACTION. IF EITHER THE SELECTIVITY FILE OR THE ENTRY HEADER FILE SHOWS A RELEASE ON THE ENTRY NUMBER IN QUESTION, THAT NUMBER CANNOT BE USED IN THE SUMMARY INPUT, 10 REC, POS 59-70. THIS MESSAGE WILL BE GENERATED IF THE ENTRY NUMBER HAS ALREADY BEEN USED FOR A RELEASE TRANSACTION. |
1G4: |
INVALID USER FEE CLASS CODE |
USER FEE CLASS CODES ARE TRANSMITTED IN THE SUMMARY INPUT RECORDS. RECORD 34, 62, AND 89 HAVE FIELDS DEDICATED TO THESE CLASS CODES. THE CLASS CODES USED IN THESE FIELDS MUST RESIDE ON THE CLASS CODE DATABASE. IF THE CLASS CODE FIELD IS BLANK, OR CONTAINS A CODE NOT LISTED ON THE DATABASE THIS ERROR MESSAGE WILL RESULT. ALSO, THE CLASS CODES REPORTED IN THE 62 AND 89 RECORDS, OR IN THE 34 AND 89 RECORDS, MUST AGREE WITH EACH OTHER. THAT IS, IF THE 62 RECORD REPORTING MPF (CLASS CODE 499) OMITS THE CLASS CODE, BOTH THE 62 RECORD AND THE 89 RECORD WHICH CORRECTLY TRANSMITS 499 WILL RECEIVE THIS REJECTION MESSAGE. |
AR2: |
NOTIFY SUB DATA NOT APPLICABLE |
NOTIFY SUBSTITUTE TYPE NOT APPLICABLE. |
THE 'QT' RECORD HAS BEEN ACCEPTED ERROR FREE. THE STATEMENT WILL BE MARKED AS "PAID", POSTINGS TO THE INDIVIDUAL ENTRIES WILL OCCUR, A FINAL STATEMENT WILL BE GENERATED, AND AN ELECTRONIC ACH DEBIT WILL OCCUR TO THE PAYOR'S BANK ACCOUNT DENOTED BY THE 'QT' TRANSACTION PAYOR'S UNIT NUMBER. |
56G: |
ISSUER CODE/MOT CONFLICT |
IN THE CARGO RELEASE DATA INPUT TRANSACTION, APPLICATION HI, THE MODE OF TRANSPORTATION (H1 REC, POS 32-33) MUST AGREE WITH THE CODE REPRESENTING THE IMPORTING CARRIER. (H1 REC, POS 70-73). FOR AIR SHIPMENTS USING MOT 40, THE ISSUER CODE IS NOT USED AND MUST BE BLANK. IF THE ISSUER CODE FIELD IS NOT BLANK, THIS ERROR MESSAGE WILL RESULT. FOR MOT 20 OR 30, THE ISSUER CODE FIELD IS IGNORED. |
0GI: |
VESSEL CODE NOT PERMITTED FOR MOT |
THIS MESSAGE WILL GENERATE, IF A VESSEL CODE (REC. 20, POS. 3-7) IS TRANSMITTED IN THE ENTRY SUMMARY INPUT TRANSACTION WITH A MODE OF TRANSPORTATION CODE OTHER THAN OCEAN (MOT = 10, 11). |
Q01: |
INPUT RECORD TYPE MUST BE "QT" |
POSITIONS 1&2 ON EACH INPUT RECORD WITHIN THE "QN" APPLICATION MUST BE "QT" . |
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.
|
|