|
VC6: |
FW 3-177: VALUE MUST BE >0 |
IN THE FISH & WILDLIFE INTERFACE THE FWS VALUE (FW01 RECORD, POSITIONS 63-72) IS A MANDATORY RECORD. THIS ERROR MESSAGE WILL OCCUR IF THE DATA ELEMENT CONTAINS ALL ZEROES OR BLANKS. |
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). |
6GC: |
FDA CODE INVALID MUST BE '1' |
WHEN REPORTING FDA ON THE G01 RECORD, MUST BE '1' OR SPACES. |
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. |
2B1: |
MODE OF TRANSPORTATION REQUIRED |
THE MODE OF TRANSPORTATION (MOT) IS REQUIRED TO BE SHOWN IN ALL FORMAL ENTRY SUMMARY INPUT TRANSACTIONS. THE MOT IS SENT IN THE 20 REC, POS 28-29. IF THE MOT IS LEFT BLANK, THIS ERROR MESSAGE IS GENERATED. FOR INFORMAL ENTRIES AND FOR CARGO RELEASE INPUT TRANSACTIONS (APPLICATION IDENTIFIER HI), SEE ERROR MESSAGE 630. |
EI7: |
COMMERCIAL DESCRIPTION REQUIRED |
THIS MESSAGE IS GENERATED IN RESPONSE TO AN AUTOMATED INVOICE TRANSACTION (APPLICATION CI). THE COMMERCIAL DESCRIPTION OF THE INVOICED ARTICLES IS TRANSMITTED TO ABI IN THE C35 REC, POS 4-73. THIS FIELD MAY NOT BE BLANK. IF SO, THIS ERROR MESSAGE WILL BE GENERATED. |
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. |
46F: |
PAYMENT TYPE/DUE DATE CONFLICT |
WHEN CHANGING PAY BASIS INDICATOR FROM 2,3, OR 5 TO 1 (SINGLE PAYMENT) THE SCHEDULE PAY DATE MUST BE SPACES. NO OTHER DATES, ALPHA OR SPECIAL CHARACTERS CAN BE TRANSMITTED IN THIS FIELD WHEN THE PAYMENT TYPE IS 1. |
ENTRIES WHICH REQUEST CARGO SELECTIVITY PROVISIONAL RESULTS MUST CONTAIN A FIRMS CODE WHICH IS "ACTIVE" AND WHICH REPRESENTS A VALID CARGO EXAMINATION SITE. (NOT A CUSTOMS ADMINISTRATIVE SITE). IF THE FIRMS CODE, FROM THE FIRMS FILE DATABASE, IS NOT ACTIVE, THE INPUT TRANSACTION WILL BE REJECTED WITH THIS ERROR MESSAGE. |
AQW: |
FAX INDICATOR REQUIRED |
THE FAX INDICATOR CANNOT BE BLANK. |
AQ7: |
SAMPLE INDICATOR REQUIRED |
THIS DATA FIELD IS MANDATORY FOR THE PJ INITIAL FILING TRANSACTION. THE ACCEPTABLE INDICATORS ARE 'N' (NO SAMPLE) AND 'S' (SAMPLE SENT). THIS DATA FIELD IS CONDITIONAL FOR ANY SUBSEQUENT QJ AMENDMENT OR RJ ADDENDA TRANSACTION. IN A QJ OR RJ THE PROTEST RECORD CAN BE UPDATED TO CHANGE NO SAMPLE TO SAMPLE SENT BY TRANSMITTING 'S'. IF THE PJ OR PREVIOUS QJ OR RJ WAS TRANSMITTED TO UPDATE TO SAMPLE SENT, A SUBSEQUENT QJ OR RJ CANNOT BE USED TO CHANGE THE SAMPLE SENT BACK TO NO SAMPLE. INSTEAD THE FILER MUST CONTACT THE PROTEST PROCESSING TEAM AT THE PORT WHERE THE PROTEST WAS FILED AND REQUEST CUSTOMS MANUALLY UPDATE THE RECORD. |
AQN: |
FILING PERIOD BASE DATE INVALID |
THE BEGINNING OF THE FILING & AMENDMENT PERIOD FOR A PROTEST, CLAIM OR INTERVENTION CAN BE DETERMINED IN ANY ONE OF SEVERAL WAYS. WHEN PROTESTING DENIAL OF 520(C) OR 520(D) CLAIM IT IS THE DATE OF DENIAL. INTERVENTIONS MAY BE FILED ANYTIME BEGINNING WITH THE FILING OF PROTEST OF ADVERSE COUNTRY OF ORIGIN MARKING DECISION ENDING WITH USCS DECISION. FOR PROTESTS OR CLAIMS RELATED TO ENTRIES, LQUIDATION DATE CONSTITUTES THE START OF THE PERIOD. ANY OTHER CASE REQURES A FILING/AMENDMENT BASE DATE BE SUBMITTED BY THE FILER, TO BE VERIFIED BY USCS. THE VALUE SUBMITTED IN THE FILING PERIOD BASE DATE FIELD IS NOT A VALID DATE. |
216: |
INVALID TARIFF NUMBER |
TARIFF NUMBER BLANK OR NOT NUMERIC |
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. |
886: |
IT QUANTITY MUST BE NUMERIC |
THIS ERROR MESSAGE OCCURS IN THE ABI 'HI' CARGO SELECTIVITY TRANSACTION WHEN AN I.T. IS SENT IN POSITIONS 3-14 OF THE HA RECORD AND THE I.T. QUANTITY IN POSITIONS 51-58 ARE NOT ALL NUMERICS. |
RBV: |
WARNING - IMPTR ON REG'L SANCTION |
FOR RECONCILIATION, THIS MEANS THAT THE IMPORTER IS ON REGIONAL SANCTION. THIS IS ONLY A WARNING FOR RECONCILIATION. |
828: |
REFERENCE NUMBER VOIDED |
THIS ERROR MESSAGE OCCURS WHEN THE REFERENCE CF 4811# USED IN A DRAWBACK TRANSACTION IS VOIDED IN THE IMPORTER FILE. THIS MESSAGE ALSO OCCURS FOR RECONCILIATION WHEN THE REFERENCE CF 4811# IS VOIDED. |
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. |
VEK: |
FC 740:MODEL/TYPE NBR REQ |
A MODEL OR TYPE NUMBER CODE IS REQUIRED TO BE SENT IN THE FC01 RECORD, POSITIONS 58-74. |
VF3: |
OGA DISCLAIMER NOT ALLOWED |
OTHER GOVERNMENT AGENCY REQUIREMENTS ARE STIPULATED IN THE HARMONIZED TARIFF FILE. A DISCLAIMER IS ALLOWED ONLY ON THOSE TARIFF NUMBERS THAT ARE CODED WITH AN INDICATOR "MAY BE REQUIRED". AN EXAMPLE IS A TARIFF NUMBER CODED "FD1" OR "FW1". TARIFF NUMBERS CODED WITH AN INDICATOR "IS REQUIRED" (E.G. FD2, FW2) CANNOT BE DISCLAIMED. FILER SHOULD QUERY THE HARMONIZED NUMBER AND UPDATE THEIR DATABASE IF NECESSARY. |
12S: |
DB ERROR ON XRJ (FACILITY) FILE |
THE FIRMS CODE RECORD WHICH MATCHES THE TRANSMITTED FIRMS CODE CONTAINS A FACILITY TYPE CODE OF EITHER 07 OR 08, WHICH MEANS FIRMS CODE NOT VALID FOR ENTRY PURPOSES. |
VH2: |
DT HS7: VIN# ALREADY ON FILE |
THE VIN NUMBER TRANSMITTED IN POSITIONS 39-55 OF THE DT02 RECORD HAS ALREADY BEEN TRANSMITTED ON A PREVIOUS ENTRY. |
0II: |
IMP NO ENTRY SUMMARY MISMATCH |
IF AN IMPORTER OF RECORD HAS BEEN ESTABLISHED VIA AN ABI ENTRY SUMMARY TRANSMISSION, A FILER MAY NOT USE A DIFFERENT IMPORTER OF RECORD NUMBER ON A CARGO RELEASE INPUT TRANSACTION. IF THE ORIGINAL IMPORTER NUMBER IS INCORRECT, THE SUMMARY SHOULD BE DELETED AND THE CARGO RELEASE TRANSACTION SHOULD BE RESUBMITTED AFTER THE SUMMARY HAS BEEN REMOVED. |
Z29: |
HTS REQUIRES FORMAL ENTRY |
CERTAIN HTS NUMBERS WITH A VALUE GREATER THAN $250.00 REQUIRES A FORMAL ENTRY TYPE. APPENDIX K OF THE CATAIR (AS WELL AS PERIODIC ADMINISTRATIVE MESSAGES) LIST THE TARIFF NUMBERS THAT ARE SUBJECT TO THE $250 LIMITATION. ON THE TARIFF FILE, THESE TARIFF NUMBERS ARE CODED "MIS-REQ" WITH A VALUE OF "2". IF AN INFORMAL ENTRY SUMMARY IS TRANSMITTED TO ABI WITH A VALUE OVER $250 ON A LINE CONTAINING A TYPE "2" TARIFF NUMBER, THIS ERROR MESSAGE WILL BE GENERATED. NOTE: IF THE HSAS FILE SHOWS MIS-REQ WITH BOTH A "0" AND A "2", THE "0" CONDITION APPLIES AND ERROR MESSAGE 51D WILL BE GENERATED RATHER THAN THIS ERROR MESSAGE. IMPORT SPECIALIST NOTE: SEE ADMINISTRATIVE MESSAGE @ |
ARJ: |
PROTESTANT NBR NOT ON FILE |
A VALID IRS OR CUSTOMS ASSIGNED ID NUMBER PRESENT ON THE CUSTOMS IMPORTER DATABASE IS REQUIRED FOR ALL PROTESTANT TYPES EXCEPT F=FOREIGN AND O=OTHER. THE VALUE SUBMITTED IN THE PROTESTANT NUMBER FIELD DOES NOT EXIST ON THE CUSTOMS IMPORTER FILE. |
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.
|
|