ABI Error Message

33C:	DATE OVER 90 DAYS INTO FUTURE

THE END DATE CANNOT BE OVER 90 DAYS UNLESS IT IS INDEFINITE. IN ADDITION TO THE ABOVE DEFINITION, IF ABI FILERS TRANSMIT ENTRY SUMMARY DATA WITH A PAYMENT DUE DATE MORE THAN 90 DAYS IN THE FUTURE, AS COMPARED TO THE TRANSMISSION DATE, THIS ERROR MESSAGE WILL BE GENERATED.

070:	INVALID OBJECT CLASS

1 TO 3 DIGIT CODE IS NOT FOUND WHEN VALIDATED AGAINST THE CAMIS OBJECT CLASS CODE FILE. OBJECT CLASS CODE IS NOT NUMERIC. EXCEPTION: MAY BE NON-NUMERIC FOR CLASS CODES 060,061,062,063,069 OR 071. LEFT-JUSTIFIED ZEROS ARE NOT REQUIRED INPUT.

VL5:	DRAWBACK TEAM INVALID FOR DDPP

IN THE DRAWBACK MODULE THIS MESSAGE MEANS THAT THE DDPP/TEAM COMBINATION IS NOT CORRECT. THIS WILL MOST OFTEN APPEAR IN COMBINATION WITH ERROR MESSAGE VL4.THERE IS A DIRECT CODED  LINK BETWEEN THE VALID FILING DDPP CODES AND THE VALID TEAM CODES.

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.

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.

34D:	CANT DELETE WHILE ENTRIES PRESENT

THIS MESSAGE MAY APPLY TO SEVERAL APPLICATIONS IN ABI. FOR PROTESTS, THIS MESSAGE ADVISES THE FILER THAT A PROTEST MAY NOT BE DELETED WHILE ONE OR MORE ENTRIES ARE STILL ON FILE FOR THE PROTEST NUMBER IN QUESTION. FOR AUTOMATED INVOICE TRANSMISSIONS, THIS MESSAGE INDICATES THAT INDIVIDUAL INVOICES MAY NOT BE DELETED ONCE AN ENTRY IS ON FILE IN ACS FOR THAT INVOICE NUMBER.

13M:	MANIFEST QTY MUST BE > ZERO

THE MANIFESTED QUANTITY IS REPORTED BY THE ENTRY FILER IN THE CARGO RELEASE APPLICATION (HI) IN THE HA REC, POS 51-58. IF THE FILER TRANSMITS ZERO AS THE MANIFESTED QUANTITY, THE ABOVE ERROR MESSAGE WILL BE GENERATED.

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.

94N:	EXPECTED UNG/UNH SEGMENT NOT FND

EDIFACT SYNTAX ERROR. THE UNG/UNH (MESSAGE HEADER) SEGMENTS ARE MISSING.

ASB:	SEQUENCE NUMBER REQUIRED

SEQUENCE NUMBER REQUIRED. THE FILER MAY LIST UP TO 9999 ENTRIES AND TRANSMIT UP TO 9999 LINES OF NARRATIVE. EACH ENTRY AND EACH LINE OF NARRATIVE MUST BE PRECEDED BY 4 CHARACTERS REPRESENTING THE ORDER IN WHICH IT APPEARS, THE FIRST PROTESTED ENTRY WOULD BE 0001.

ST2:	NO PEVIOUS SET HEADER PROCESSED

A SET ITEM (SECONDARY SPI OF 'V') WAS ENTERED WITHOUT A SET HEADER (SECONDARY SPI OF 'X') LINE IMMEDIATELY PRECEDING THIS LINE.

VOW:	NON-REMOTE ENTRY ALREADY ON FILE

THIS MESSAGE IS GENERATED IN RESPONSE TO AN ENTRY SUMMARY INPUT TRANSMISSION. IF A FILER HAS ALREADY ESTABLISHED SELECTIVITY RECORDS IN ACS, VIA THE HI (CARGO RELEASE DATA INPUT) TRANSACTION, THE FILER MAY NOT TRANSMIT AN RLF SUMMARY FILE FOR THE SAME ENTRY NUMBER. IF THE FILER WISHES TO CREATE AN RLF ENTRY FOR THE NUMBER IN QUESTION, THE ORIGINAL SELECTIVITY RECORDS FROM THE HI TRANSACTION WILL HAVE TO BE REMOVED BY PORT PERSONNEL.

8WI:	TRANSACTION DATA REJECTED

THIS IS THE STANDARD REJECTION MESSAGE THAT WILL BE GENERATED WHEN A BILL OF LADING UPDATE TRANSMISSION INPUT HAS FATAL ERRORS.

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.

VOE:	D10 FIELDS MUST MATCH FILED ENTRY

THIS DRAWBACK MODULE ERROR MESSAGE CAN OCCUR IF THE DRAWBACK CLAIM WAS MANUALLY INPUT PRIOR TO THE DISKETTE OR ABI INFORMATION BEING TRANSMITTED. THIS INDICATES THAT THERE ARE MEANINGFUL DIFFERENCES BETWEEN WHAT WAS KEYED IN FROM THE CLAIM AND WHAT WAS ON THE DISKETTE OR IN ABI. FOR 'D10', VIRTUALLY ALL FIELDS MUST MATCH WHAT WAS INPUT EXCEPT FOR DATES AND MONEY AMOUNTS.

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.

66A:	IMPORTER IS INACTIVE

THIS MESSAGE IS GENERATED IN RESPONSE TO A CARGO RELEASE DATA INPUT TRANS- ACTION (APPLICATION HI). IF THE IMPORTER NUMBER (H1 REC, POS 20-31) IS IN 'INACTIVE' STATUS ON THE IMPORTER DATABASE, THIS ERROR MESSAGE WILL BE GENERATED. TO REACTIVATE, THE FILER MUST SEND AN "ADD CF5106" TRANSACTION WITH THE IMPORTER'S FULL NAME AND ADDRESS INFORMATION.

RBT:	RECON DATE OVER 90 DAYS IN FUTURE

FOR RECONCILIATION, THIS MESSAGE INDICATES THAT THE DATE IS IN A VALID FORMAT, BUT IS GREATER THAN 90 DAYS IN THE FUTURE. DATES UP TO 90 DAYS IN IN ADVANCE ARE ACCEPTED VIA  ABI FOR RECONCILIATION.

VOS:	REMOTE ENTRY/RLSE CERT MISSING

THIS MESSAGE OCCURS WHEN A FILER, SET TO OPERATIONAL STATUS FOR REMOTE LOCATION FILING, DOES NOT SEND A '1' SIGNIFYING CERTIFICATION FOR CARGO RELEASE, IN POSITION 38 OF THE 30 RECORD. THIS IS A REQUIREMENT FOR REMOTE LOCATION FILING.

02J:	PC: NONNUMERIC EST ARRIVAL DATE

ESTIMATED ARRIVAL DATE ENTERED IS NON-NUMERIC. THIS ENTRY HAS BEEN FLAGGED AS A PAIRED CITIES ENTRY. A VALID ESTIMATED ARRIVAL DATE IS REQUIRED.

BRB:	INTERES AMOUNT MISMATCH (R17:R91)

THE PAYABLE INTEREST AMOUNT IN THE R17 RECORD MUST = THE INTEREST AMOUNT IN THE R91 RECORD. IF NO INTEREST IS PAYABLE, BOTH THE R17 AND R91 RECORDS MUST INDICATE ZEROES FOR THE INTEREST AMOUNT.

1L5:	WARNING-NO BOND FOR IMPORTER

THIS MESSAGE IS GENERATED IN RESPONSE TO LINE RELEASE OUTPUT RECORD CREATION. IT IS USUALLY ACCOMPANIED BY ERROR 628 (MISSING/INVALID IMPORTER NUMBER). IF THE BOND IS ASSOCIATED WITH A PROPERLY FORMATTED IMPORTER NUMBER (IN EIN, SSN, OR USCS ASSIGNED NUMBER FORMAT), AND THE IMPORTER NUMBER FORMAT IS NOT IN THE CORRECT FORMAT, THE BOND WILL CONSEQUENTLY BE NOT ON FILE. CORRECTION OF THE IMPORTER NUMBER ERROR WILL USUALLY RESOLVE THE NO BOND ERROR, PROVIDED AN ACTUAL CONTINUOUS BOND EXISTS.

VEM:	FC 740:QTY EXCEEDS 03 ALLOWANCE

THE QUANTITY FOR AN 03 IMPORT CONDITION NUMBER CANNOT EXCEED 200 UNITS WITHOUT PRIOR APPROVAL. IF QUANTITY EXCEEDS 200, REPORT PRIOR APPROVAL BY SENDING A "Y" IN POSITION 7 OF THE FC01 RECORD, DATA ELEMENT "03 IMPORT CONDITION NUMBER QUANTITY APPROVAL".

1ED:	EST'D ARRIVAL DATE: NOT NUMERIC

THIS MESSAGE OCCURS WHEN A FILER CERTIFIES AN ENTRY SUMMARY FOR CARGO RELEASE BY SENDING A '1' IN POSITION 38 OF THE EI 30 RECORD BUT SENDS BLANKS FOR THE ESTIMATED ARRIVAL DATE IN POSITION  66-71 OF THE EI 20 RECORD. THIS MESSAGE WILL ALSO BE GENERATED IF THE ESTIMATED ARRIVAL DATE IS INCORRECT IN THE L1 RECORD OF THE BILL OF LADING UPDATE FEATURE.

VPX:	CANADIAN DISCLAIMER INVALID

THIS ERROR MESSAGE OCCURS IN THE NAFTA DUTY DEFERRAL MODULE. THE COMPLETE DESCRIPTION OF THIS DATA ELEMENT IS "NAFTA CTRY ENTRY LIST DISCLAIMER". IT IS SENT IN THE D30 MANDATORY RECORD, POSITION 68 AND IS A CODE WHICH INDICATES THAT THE NAFTA COUNTRY ENTRY DATA ASSOCIATED WITH THE CLAIM WILL OR WILL NOT BE PROVIDED. THE ONLY ALLOWED INDICATORS ARE 'SPACE FILL' WHICH INDICATES THAT THE INFORMATION WILL BE PROVIDED AND '1' WHICH INDICATES THAT THE INFORMATION WILL NOT BE PROVIDED. THE MOST COMMON ERROR IS SENDING A '0' FOR 'SPACE FILL'

 Next 10 >>Showing results 1 to 25 of 1405