|
|
| THIS MESSAGE OCCURS WHEN A FILER ATTEMPTS TO USE THE 'HP' STATEMENT ADD/DELETE TRANSACTION FOR AN ENTRY THAT IS NOT FOUND ELIGIBLE FOR AN 'HP'. AN EXAMPLE WOULD BE AN ENTRY THAT HAS BEEN ARCHIVED (ACS HISTORY FILE). |
| THE TAX AMOUNT TRANSMITTED IN THE 60 REC, POS 59-68 IS NOT AN EXACT MATCH TO THE TOTAL TAX TRANSMITTED IN THE 90 REC, POS 14-24.THIS MESSAGE APPLIES TO AN ENTRY SUMMARY TRANSACTION (APPLICATION EI), BUT THIS ERROR WILL NORMALLY BE FOUND IN THE EY OUTPUT RECORD AND THE ERROR MESSAGE NUMBER DOES NOT DISPLAY. |
|
VER: |
***ISIS TABLE OVERFLOW - ERROR*** |
| THIS MESSAGE IS INTERNAL TO FDA'S ISIS PROCESSING SYSTEM. IT WILL OCCUR IN SEVERAL APPLICATIONS UNDER FILER CODE 9900/I99. |
|
27D: |
*CENSUS* OR-HI VAL/QTY (1)TARIFF1 |
| THE UNIT PRICE (VALUE/PRIMARY QUANTITY) IS NOT WITHIN SPECIFIC LIMITS |
|
1I6: |
DUTY COMP DATE > SCH PAY DATE |
| THIS ERROR MESSAGE WILL RESULT IF THE DATE TRANSMITTED BY THE ABI FILER IN SUMMARY INPUT IS GREATER (LATER) THAN THE DATE REPRESENTING THE SCHEDULED PAYMENT DUE DATE. THE MOST COMMON EXAMPLE OF THIS CONDITION IS WHEN A FILER TRANSMITS AN "ESTIMATED ENTRY DATE" (10 REC, POS 50-55) THAT IS LATER THAN THE PAYMENT DUE DATE (30 REC, POS 54-59). |
|
299: |
INVALID INFORMAL ENTRY NUMBER |
| INVALID EIGHT DIGIT ENTRY NUMBER FOR INFORMAL COLLECTION. |
|
4CU: |
VISA # INVALID FOR FASHION SAMPLE |
| SPI "M" IS USED TO REPORT IMPORTATIONS OF FASHION SAMPLES OR CERTAIN CARPETS FROM CHINA. (SEE ADMIN MSG 97-0482, 97-0952, AND 97-0990). ONE OF THE REQUIREMENTS OF THIS PROGRAM IS THAT IF "M" IS USED, THE VISA NUMBER FOR THE ITEM IN QUESTION MAY NOT BE TRANSMITTED TO ABI. IF THE VISA NUMBER IS SENT, THIS ERROR MESSAGE WILL BE GENERATED. |
|
AE4: |
WARNING! ENTRY DATE < EXPORT DATE |
| THIS WARNING MESSAGE OCCURS IN THE "REVISED FILER DATE" (DN) TRANSACTION WHEN A FILER TRANSMITS AN ENTRY DATE THAT IS EARLIER THAN THE EXPORT DATE THAT RESIDES IN THE LINE ITEM FILE OF THE ENTRY SUMMARY RECORD. |
|
VKO: |
HLT: INQUIRY DISPLAY MUST BE Y/N |
| THE INQUIRY DISPLAY SWITCH MUST BE Y=YES N=NO. |
|
ASM: |
ARGUMENT/JUSTIFICATION REQ'D |
| A STATEMENT OF THE NATURE OF, AND JUSTIFICATION FOR THE PROTEST, PETITION, INTERVENTION MUST BE INCLUDED AT THE TIME OF INITIAL FILING. THE P90 RECORD IS MISSING OR BLANK. |
|
VHU: |
DT HS7: INVALID YEAR |
| THE DT02 REC, POS 35-38 MUST REFLECT THE FOUR-DIGIT YEAR. ANY YEAR NOT IN THE RANGE FROM 1901 THROUGH 2099, INCLUSIVE, WILL GENERATE THIS ERROR MESSAGE. |
|
109: |
INVALID SPECIAL PROGRAMS INDICATOR |
| ABI ENTRY SUMMARY TRANSMISSIONS MAY INCLUDE A SPECIAL PROGRAM INDICATOR CODE ("SPI"). THE VALID CODES ARE LISTED ON PAGES ENS-48 THROUGH ENS-50 OF THE CATAIR (CUSTOMS AND TRADE AUTOMATED INTERFACE REQUIREMENTS DOCUMENT). IF A FILER'S TRANSMISSION CONTAINS A CODE NOT CURRENTLY AUTHORIZED AS A SPECIAL PROGRAM INDICATOR, THIS ERROR MESSAGE WILL RESULT. |
|
AFV: |
PIRP NUMBER CANNOT FOLLOW DESC |
| IF FILERS USE THE 43 RECORD TO TRANSMIT "INVREQ", NO COMMERCIAL DESCRIPTION DATA IS PERMITTED IN POS 11-80 OF THE 43 REC. ANY DATA IN THIS FIELD WILL GENERATE THIS ERROR MESSAGE. |
|
40J: |
SPI CLAIM INVALID FOR TARIFF |
| MOST TARIFF NUMBERS ARE ELIGIBLE FOR ONE OR MORE SPECIAL PROGRAMS THAT REDUCE OR ELIMINATE THE DUTY REQUIRED. THESE ARE CODED AS "SPI" FOR THOSE PROGRAMS THAT THE INDIVIDUAL TARIFF NUMBER HAS BEEN FLAGGED FOR. IF AN ABI FILERS TRANSMITS AN SPI (SUMMARY TRANSACTION 50 REC, POS 3, OR POS 78-79; 70/80/81 REC, POS 13 OR POS 79-80) THAT IS NOT LISTED ON THE TARIFF FILE FOR THAT TARIFF NUMBER, THIS ERROR MESSAGE WILL RESULT. FILERS SHOULD VERIFY THE SPI FROM THEIR HARMONIZED QUERY OUTPUT (V3 REC, POS 53-72) TO ASCERTAIN THAT THE SELECTED SPI APPLIES TO THE TARIFF NUMBER. NOTE: AS STATED IN ERROR MESSAGE 40L, IF THE TRANSMITTED SPI (50 RECORD OR 70 RECORD) IS ON THE TARIFF FILE FOR THE TARIFF NUMBER, IT MUST NONETHELESS AGREE WITH THE C/O CODE (EITHER "MX" OR "CA"). IF THE C/O IS "CA", AN SPI OF "MX" WILL GENERATE THIS ERROR MESSAGE. |
|
52Y: |
MAXIMUM I7 RECORDS EXCEEDED |
| REFER TO ADMINISTRATIVE MESSAGE 98-0236, DATED 032098. IN SOME CASES THE ULTIMATE CONSIGNEE NAME AND ADDRESS APPLICATION (IJ) WAS CAUSING DATA BASE ERRORS WHEN THE NUMBER OF I7 ENTRY NUMBER/LINE ITEM SEQUENCE RECORDS EXCEEDED THE LIMIT SET BY THE PROGRAM FOR A PARTICULAR NAME AND ADDRESS I3 AND I4 RECORD SET. ALSO, IN SOME REJECT SITUATIONS THE ERROR MESSAGE "524 TRANSACTION DATA REJECTED" WAS DISPLAYING ERRONEOUSLY IN THE IB OUTPUT MESSAGES WHEN THE ENTIRE IJ APPLICATION WAS NOT REJECTED. TO ELIMINATE THE ABOVE SITUATIONS AND TO PROVIDE MORE ACCURATE INFORMATION WHEN ERRORS ARE DETECTED IN THE ULTIMATE CONSIGNEE NAME AND ADDRESS APPLICATION (IJ) TRANSMISSIONS, THIS ERROR MESSAGE AND 52Z "ENTRY/LINE SEQUENCE REJECTED" ARE GENERATED. BOTH THE 52Y AND 52Z MESSAGES WILL APPEAR AS IB OUTPUT RECORDS WHEN CUSTOMS DETERMINES THAT THE INFORMATION TRANSMITTED CANNOT BE ADDED TO THE DATABASE AS REQUESTED BY AN ABI FILER. |
|
VOH: |
PREPARER/REMOTE IND CONLICT |
| THE REMOTE PROCESSING DISTRICT PORT IS SENT IN THE 'B' RECORD, POSITIONS 47-50. THE REMOTE PREPARER FILER IS SENT IN THE 'B' RECORD, POSITIONS 51-53. IF THE REMOTE PREPARER INDICATOR IN POSITION 56 OF THE 'B' RECORD IS SET TO '1' (YES) THEN THE DDPP/FILER MUST BE SET UP IN THE ABI BROKER REMOTE FILING LOCATIONS FILE. |
|
2J0: |
SURETY INVALID OR NOT ON FILE |
| THIS REJECT MESSAGE REFERS TO THE SURETY REPORTED, IF ANY, FOR ANTIDUMPING OR COUNTERVAILING DUTY TRANSACTIONS. (MESSAGE 2AL IS THE EQUIVALENT ERROR MESSAGE FOR INVALID SURETY CODES REPORTED IN THE 10 RECORD). ADA OR CVD SURETY CODES ARE TRANSMITTED IN THE 35 REC, POS 49-51. SURETY CODES ARE REQUIRED ONLY WHEN THE BONDED INDICATOR FOR THE CASE NUMBER BEING REPORTED IS "1" (REPORTED IN POS 14 OF THE 35 REC). FOR ENTRIES WITH MULTIPLE ADD/CVD LINES, IF AT LEAST ONE LINE IS A BONDED CASE, THE SURETY CODE IN THE 35 RECORD IS REQUIRED. "000" IS THE MOST FREQUENTLY REPORTED INCORRECT SURETY CODE AND WILL CAUSE THIS MESSAGE TO BE ISSUED BY ACS. IF BLANKS ARE TRANSMITTED FOR THIS ELEMENT, MESSAGE 2AL WILL BE ISSUED. |
|
486: |
INVALID CONSIGNEE NUMBER FORMAT |
| CONSIGNEE NUMBERS TRANSMITTED TO ABI MUST BE IN ONE OF THE FOLLOWING FORMATS: IRS OR EIN NUMBER: NN-NNNNNNNXX SSN: NNN-NN-NNNN CUSTOMS ASSIGNED NUMBER: YYDDPP-NNNNN N = NUMERIC CHARACTER; X = ALPHANUMERIC CHARACTER (EXCEPT FOR THE LETTERS "O", "I", "Z"); YY= LAST TWO DIGITS OF THE CALENDAR YEAR IN WHICH THE NUMBER WAS ASSIGNED. ANY OTHER FORMAT THAN ONE OF THE ABOVE WILL BE REJECTED WITH THIS MESSAGE. |
|
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. |
|
VBW: |
DT HS7: WARN - TIRE BRAND MISSING |
| IF A FILER TRANSMITS A 'T' IN THE DOT DT01 RECORD, POSITION 37 AND THE TIRE MANUFACTURER ID CODE IN POSITIONS 38-40, THE TIRE MANUFACTURER BRAND NAME SHOULD BE SENT IN POSITIONS 41-60. |
|
ADF: |
ENTRY IS NOT A STATEMENT ENTRY |
| THIS MESSAGE IS GENERATED WHEN APPLICATION HP (STATEMENT ADD/DELETE) IS ATTEMPTED. THIS APPLICATION ALLOWS FILERS TO MOVE THE PAYMENT DUE DATE ON ENTRIES SCHEDULED FOR PAYMENT BY STATEMENT. IF THE FILER ATTEMPTS TO REMOVE AN ENTRY FROM A STATEMENT BUT THE ENTRY IN QUESTION IS NOT CURRENTLY SCHEDULED FOR PAYMENT BY STATEMENT, THIS MESSAGE WILL BE GENERATED. |
|
07A: |
INVALID CROSS DIST PRCSSING PORT |
| THIS MESSAGE OCCURS IN AN 'HN' BORDER CARGO RELEASE TRANSACTION WHEN THE DISTRICT/PORT OF ENTRY SENT IN THE 01 RECORD, POSITIONS 4-7 IS DIFFERENT FROM THE PROCESSING DISTRICT/PORT SENT THE THE 'B' APPLICATION CONTROL RECORD, POSITIONS 4-7. THIS DESPITE THE WORDING IN THE DESCRIPTION BLOCK FOR THE DISTRICT/PORT OF ENTRY IN RECORD IDENTIFIER 01, PAGE BCR-4 OF THE CATAIR WHICH STATES "GENERALLY, THE DISTRICT CODE IS THE SAME AS THE DISTRICT CODE CONTAINED IN THE BLOCK CONTROL HEADER RECORD (RECORD IDENTIFIER B); HOWEVER, THE PORT CODE CAN BE DIFFERENT" THIS DOES NOT APPEAR TO BE TRUE. THE DDPP'S MUST BE THE SAME OR THIS REJECT OCCURS. |
|
05C: |
ENTRY TYPE INVALID FOR SELECT |
| ENTRY TYPE IS VALID BUT NOT FOR SELECTIVITY. VALID ENTRY TYPES FOR SELECTIVITY ARE 01-03, 06, 07, 11, 12, 21, 23, 51-53. FLAG FOR "UNLADING (Y/N)" IS SET TO 'N'. |
|
VK2: |
HLS: OP TYPE MUST BE 'C' OR 'M' |
| THE OPERAND TYPE CODE MUST BE 'C' FOR CONSTANT OF 'M' FOR MAP. WHEN 'C' THE OPERAND MUST BE A DISPLAY CONSTANT IN SINGLE QUOTES OR A HEX CONSTANT IN THE FORM X ,....' WHEN 'M' THE OPERAND MUST BE A BMS MAP FIELD NAME. |
|
17K: |
INVALID APPLICATION CODE |
| THE APPLICATION CODE FOUND ON THE 'B' RECORD WAS LOCATED IN THE APPLICATION CODE FILE, HOWEVER, THE CODE IS NUMERIC AND RESERVED FOR SPECIAL USE. |
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.
|
|