|
JAF: |
NO DATA FOUND FOR KEY |
THIS MESSAGE IS A REPLY TO ONE OR MORE ABI QUERIES THAT INDICATES THAT ABI COULD FIND NO RECORDS MATCHING THE FILER'S REQUEST. IT IS USED, AT A MINIMUM, AS A REPLY TO THE FDA PRODUCT CODE QUERY WHEN THE PRODUCT CODE TRANSMITTED BY THE FILER IS NOT FOUND ON THE FDPL DATABASE |
06J: |
UNLDNG PORT NOT = ENTRY PORT |
UNLADING PORT IS NOT EQUAL TO THE ENTRY PORT; YET THIS ENTRY HAS NOT BEEN FLAGGED AS PAIRED CITIES. |
27D: |
*CENSUS* OR-HI VAL/QTY (1)TARIFF1 |
THE UNIT PRICE (VALUE/PRIMARY QUANTITY) IS NOT WITHIN SPECIFIC LIMITS |
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. |
THE ONLY VALID INPUT FOR THIS FIELD IS 'Y'. OTHERWISE, THE FIELD SHOULD REMAIN BLANK. |
07H: |
EST ARRIVAL DATE NOT IN RANGE |
THE ESTIMATED ARRIVAL DATE ENTERED IS NOT WITHIN THE RANGE ALLOWED. VALID DATES INCLUDE: 1) TODAY'S DATE, 2) ANY DATE UP TO 30 DAYS IN THE PAST, 3) ANY DATE UP TO 5 DAYS IN THE FUTURE. |
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. |
THIS MESSAGE OCCURS WHEN A FILER SENDS ANTI-DUMPING (ADD) OR COUNTERVAILING (CVD) DATA IN ABI REC 60 (CATAIR, PAGE ENS-54) AND THE CASE NUMBER REPORTED (POS 13-22 OR 23-32) HAS BEEN REVOKED. IF THE CASE HAS BEEN REVOKED AND NEED NOT BE REPORTED. |
834: |
ADD INVALID - BROKER REF MISMATCH |
IF AN ENTRY SUMMARY RECORD EXISTS AND AN ADD TRANSACTION IS SUBMITTED VIA BATCH ABI INPUT, THE BROKER REFERENCE NUMBER IN THE EXISTING RECORD MUST MATCH THE BROKER REFERENCE NUMBER IN THE '20' RECORD OF THE BATCH ADD TRANSACTION. FILERS MAY CHANGE THEIR FILER REFERENCE NUMBER IF THEY USE ACTION CODE OF "R" (REPLACE) OR "C" (CHANGE) IN LIEU OF "A" (ADD). THIS MESSAGE WILL ALSO RESULT IF THE CARGO DATA INPUT APPLICATION (HI) OR THE BORDER CARGO RELEASE APPLICATION (HN) IS USED AND THE "A" ACTION CODE IS TRANSMITTED WITH A DIFFERENT BROKER REFERENCE NUMBER THAN WAS USED ON THE INITIAL INPUT. |
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. |
B24: |
LOWER CASE LETTERS FIRM/ADDR/CITY |
FIRM NAME FIELD, ADDRESS FIELD, OR CITY NAME FIELD CONTAINS LOWER CASE ETTERS. IN ABI TRANSACTIONS, FILERS SHOULD ALWAYS SUBMIT UPPER CASE ALPHA CHARACTERS. IF THEIR SYSTEM SENDS LOWER CASE LETTERS IN EITHER THE FIRM NAME OR CITY FIELDS, THIS MESSAGE WILL BE GENERATED. |
VOJ: |
NOT AUTHORIZED FOR REMOTE |
THE FILER'S ABE RECORD MUST BE SET TO 'Y' FOR RLF IN ORDER FOR A FILER TO PARTICIPATE IN REMOTE LOCATION FILING. TO BE SET TO 'Y' FOR RLF THERE MUST BE A RECORD ON FILE FOR THE DDPP/FILER AND OFFICE CODE (IF THERE IS AN OFFICE CODE). THERE MUST BE TWO PROFILE RECORDS SET TO 'Y' FOR REMOTE: THE DP-SITE AND EACH PREPARER PORT. |
4JB: |
QUANTITY MUST BE NUMERIC |
MUST BE EITHER NUMERIC OR BLANK. |
VKW: |
HLT: POS EXCEEDS TOTAL FLD LENGTH |
THE POSITION VALUE SPECIFIED IN THE OPTIONAL POSITION/LENGTH PARAMETER EXCEED THE TOTAL LENGTH OF THE FIELD. THE POSITION MUST BE WITHIN THE FIELD. |
14H: |
INVALID DUTY ENTERED |
DUTY ENTERED ON LINE ITEM IS NON-NUMERIC OR OTHERWISE INVALID. |
592: |
INVALID ENTRY DISTRICT /PORT |
DISTRICT/PORT NON-NUMERIC OR NON-EXISTENT FOR DRAWBACK ENTRY TYPES WHERE 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 |
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. |
4KP: |
VISA REQUIRES QUOTA ENTRY TYPE |
A STANDARDIZED VISA REQUIRES A QUOTA ENTRY TYPE. |
THE FTZ NO IN REC 20, POS 8-14 (EI APPLICATION) OR REC H2, POS 60-66 (HI APPLI- CATION) IS MANDATORY FOR ENTRY TYPE 06. IT MUST START WITH "FTZ" AND BE FOLLOWED BY FOUR NUMERICS. IF THE FTZ NO IS LESS THAN FOUR NUMERICS, THE NUMBER MUST BE PRECEDED BY ZEROS I.E. "FTZ0001". |
VAM: |
FILER MUST PAY BY ACH FOR QTA ENT |
IF THE FILER OF THE ENTRY IS NOT ACH OPERATIONAL AS OF THE DATE AND TIME OF THE TRANSMISSION OF THE ENTRY SUMMARY, ENTRY TYPE 02 CANNOT BE TRANSMITTED WITH A PAYMENT TYPE AND PAYMENT DUE DATE IN THE 30 REC (POS 53-59). THE ACH STATUS OF THE FILER WILL BE VERIFIED FROM THE FILER PROFILE RECORD IF THE FILER SENDS A LIVE ENTRY INDICATOR OF "1" IN POS 44 OF THE 10 RECORD. FURTHER, THE PRESENCE OF THE LIVE ENTRY INDICATOR WILL TRIGGER A SEARCH OF THE ACH UNIT PAYOR CROSS-REFERENCE FILE TO VERIFY THAT THE FILER, OR IMPORTER, HAS A VALID PAYER UNIT NUMBER RECORD. IF ANY OF THE HEADER DATA IS MISSING, THIS ERROR MESSAGE WILL RESULT. |
89F: |
FEE CODE REQUIRED BUT NOT ENTERED |
A FEE CODE OR AMOUNT WAS NOT ENTERED BUT IS REQUIRED BY TARIFF. |
8VB: |
COMPUTER SITE INVALID FOR BLOCK |
THIS MESSAGE IS GENERATED IN RESPONSE TO A TIB EXTENSION REQUEST (APPLICATION XN), ALTHOUGH IT MAY APPLY TO OTHER APPLICATIONS, AS WELL. IN THE INPUT RECORDS, THE XA RECORD CONTAINS A FIELD FOR THE DDPP OF THE SUMMARY FOR WHICH AN EXTENSION IS BEING REQUESTED. (POS 3-6). IF THAT FIELD IS LEFT BLANK, THIS MESSAGE IS GENERATED. NOTE: THIS MESSAGE WILL ALSO OCCUR IF THE PORT CODE FIELD IN THE XA RECORD IS NOT IDENTICAL TO THE PORT OF ENTRY FOR THE ENTRY BEING EXTENDED. |
ASU: |
MERCHANDISE DESC. REJECTED |
MERCHANDISE DESCRIPTION REJECTED. |
BE3: |
BLANK CANADIAN EXCISE NBR INVALID |
IF AN EI APPLICATION INCLUDES A '57' RECORD, THE CANADIAN EXCISE NUMBER ON MUST BE NON-BLANK. |
4BH: |
ENTRY TYPE CHANGE INVALID |
THIS MESSAGE INDICATES THAT THE ABI FILER IS ATTEMPTING TO TRANSMIT AN ENTRY SUMMARY WITH A DIFFERENT ENTRY TYPE THAN EXISTS ON THE ENTRY SUMMARY HEADER FILE FOR THE ENTRY NUMBER. IF THE ENTRY IS IN CUSTOMS STATUS, SUCH A CHANGE IS NOT PERMITTED. IF THE ENTRY IS STILL IN ABI STATUS, THIS CHANGE CAN USUALLY BE ACCOMPLISHED. THE MOST COMMON CHANGE IS FROM TYPE 11 TO TYPE 01 (OR VICE VERSA IN SOME CASES). FOR RECONCILIATION ON-LINE PROCESSING, THIS ERROR MEANS THAT YOU CANNOT CHANGE ANY PRE-EXISTING ENTRY THAT IS NOT RECONCILIATION TO A TYPE '09' RECONCILIATION ENTRY SUMMARY. |
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.
|
|