ABI Error Message

Q09:	STATEMENT NOT ELIGIBLE FOR ACH

IF THE PROFILE RECORD FOR THE FILER OF THE QT RECORD IS NOT SET TO "Y" FOR THE ACH ELEMENT, THIS MESSAGE WILL RESULT. THE ABE RECORD FOR THE FILER SHOULD BE CORRECTED. NOTE: EVEN AFTER THE CORRECTION HAS BEEN DONE, THE REJECTED QT CANNOT BE REPROCESSED FOR PAYMENT VIA ACH UNLESS POSITION 555 ON THE STATEMENT FILE IS RESET TO A "1" OR THE FILER CAN PAY BY CHECK OR THE FILER CAN MOVE THE ENTRIES TO A NEW (FUTURE) PAYMENT DUE DATE. NOTE: IF THE STATEMENT IS ELIGIBLE FOR CHECK PAYMENT AND A COLLECTION HAS BEEN STARTED, BUT NOT COMPLETED, THIS ERROR MESSAGE WILL ALSO RESULT.

8VZ:	BILL DATA UPDATED AS REQUESTED

THIS MESSAGE IS AN "ERROR FREE" NOTIFICATION TO THE FILER THAT A BILL OF LADING UPDATE 'LN' TRANSACTION WAS SUCCESSFUL. A SUCCESSFUL BOL UPDATE MEANS THAT THE UPDATE INFORMATION HAS BEEN PASSED TO THE AMS CARRIER AND THAT THE SELECTIVITY FILE HAS BEEN UPDATED.

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.

G9C:	REMOTE ENTRY/ENTRY TYPE CONFLICT

IF THE B RECORD REMOTE ENTRY INDICATOR IS A '1',THE ENTRY TYPE CODE MUST BE EITHER 01 OR 11.

42B:	LINE RELEASE ENTRY ON FILE

THIS ERROR MESSAGE OCCURS IN THE "REVISED FILER DATE" (DN) TRANSACTION WHEN A FILER TRANSMITS A REVISED ENTRY DATE IN THE DN01 RECORD, POSITIONS 19-24,WHEN THE ENTRY HAS BEEN RELEASED VIA LINE RELEASE. LINE RELEASE SETS THE ENTRY DATE AND CANNOT BE REVISED.

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.

VAF:	DT HS7: BOX CERTIFICATION REQ'D

IF POSITION 10 OF THE DT01 RECORD IS LEFT BLANK, THIS MESSAGE WILL RESULT.

VGB:	FD 701: PRODUCT CODE NOT ON FILE

THIS ERROR OCCURS WHEN A FILER ATTEMPTS TO USE AN FDA PRODUCT CODE THAT IS NOT ON FILE IN ACS. FDA MAINTAINS THE FILE. THE FILER SHOULD BE INSTRUCTED TO CONTACT THEIR FDA CONTACT TO CHECK THE PRODUCT CODE. THERE ARE APPROXIMATELY 580,000 PRODUCT CODES.

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.

04U:	INVALID DDPP UNLADING FOR CENSUS

ERROR OCCURS IN CARGO SELECTIVITY PROCESSING WHEN DDPP OF UNLADING ON SELECTIVITY HAS A CORRESPONDING 'DISTRICT-PORT' RECORD IN WHICH THE FLAG FOR "UNLADING (Y/N)" IS SET TO 'N'.

DK0:	SCHED B NUMBER NOT ON FILE

THIS MESSAGE OCCURS IN THE AUTOMATED DRAWBACK MODULE. THE MESSAGE SIMPLY MEANS THAT THE SCHEDULE B NUMBER, AT THE 6, 8, OR 10 DIGIT LEVEL DOES NOT EXIST IN THE FILE. NORMALLY, THIS OCCURS WHEN THE FILER HAS GIVEN 10 DIGIT ON OLDER RECORDS. FOR OLDER RECORDS, IF THE FILER USES 6 DIGITS (OR 8 IF PETROLEUM) THE PROBLEM IS MINIMIZED.

DKD:	D12 RECORD MUST CONTAIN DATA

THIS ERROR MESSAGE COULD BE THE RESULT OF A DRAWBACK DISKETTE OR ABI DRAWBACK PROBLEM. IT IS SAYING THAT WHEN CUSTOMS FORMATTED THE RECORDS FROM THE DRAWBACK DISKETTE OR WHEN THE DATA WAS SENT VIA ABI, NO DATA WAS PRESENT IN THE GIVEN RECORD. IF THE DISKETTE HAS NO DATA, THE PC PROGRAM SHOULD STOP IT BEFORE TRANSMISSION; HOWEVER, THERE MAY HAVE BEEN DATA THERE, BUT IT WAS BAD DATA.

322:	INVALID BROKER MODE

MUST BE NUMERIC; 0,1,2, OR 3.

28N:	*CENSUS* IMPROBABLE MFR/SHPER ID

AN ENTRY WITH A COUNTRY OF ORIGIN OR COUNTRY OF EXPORT OF 'CA' IS ENTERED AND THE FIRST TWO BYTES OF THE MANUFACTURER IS OTHER THAN 'XA" 'XC' 'XM' 'XB' 'XW' 'XN' 'XO' 'XP' 'XQ' 'XS'.

549:	INVALID COLLECTION. MODE/PAY TYPE/DATE

THIS MESSAGE ARISES FROM AN ATTEMPT BY A NON-AUTHORIZED FILER TO SCHEDULE AN ENTRY SUMMARY FOR PAYMENT VIA STATEMENT PROCESSING. IF THE FILER IS IN TEST STATUS (OR IN OPERATIONAL SUMMARY STATUS, BUT NOT YET IN OPERATIONAL OR TEST STATUS FOR STATEMENT PROCESSING), AND SENDS AN EI APPLICATION TO ABI WITH THE PAYMENT TYPE (30 REC, POS 53) AND PAYMENT DUE DATE (EI REC, POS 54-59) COMPLETED, THIS ERROR WILL RESULT.

AHZ:	DEMO FILER MUST BE IN RDP 8888

THE 'B' RECORD DDPP MUST BE '8888' FOR AN "X" FILER CODE.

VH9:	DT HS7: VIN LIST DUP POSITION: 2

IF THE FILER REPORTS DOT INFORMATION VIA THE DT03 RECORD AND THE DATA IS INCLUDED IN AN ENTRY SUMMARY INPUT TRANSACTION, THERE ARE FOUR POSITIONS AVAILABLE IN THE DT03 RECORD TO REPORT UP TO FOUR VEHICLE IDENTIFICATION NUMBERS (VIN). IF THE VIN REPORTED IN POSITIONS 5-21 (FIRST VIN FIELD) IS DUPLICATED IN POSITIONS 22-38, THIS ERROR MESSAGE WILL BE GENERATED.

8WS:	INVALID CHG: AMS TO NON AMS CAR

THIS MESSAGE IS USUALLY GENERATED IN RESPONSE TO A BILL OF LADING UPDATE TRANSACTION (APPLICATION LN). IF THE ENTRY IN QUESTION REFLECTS AN AMS CARRIER CODE, A CHANGE TO A NON-AMS CARRIER IS NOT PERMITTED. THE CARRIER CODE (SCAC) IN THE L1 RECORD MUST BE FOUND ON THE DATABASE FOR THE PORT OF ARRIVAL ON THE ENTRY RECORD. IF THE DATABASE FILE DOES NOT SHOW THE SCAC FOR THE ARRIVAL PORT, THIS ERROR MESSAGE IS GENERATED, EVEN IF THE INTENDED NEW CARRIER CODE IS AN AMS CODE IN OTHER PORTS.

AFU:	PIRP NUMBER INVALID FOR 'D' TYPE

THIS MESSAGE IS GENERATED WHEN A PIRP NUMBER IS SENT IN THE EI 43 RECORD, POSITIONS 3-8 AND A 'D' FOR COMMERCIAL DESCRIPTION IS SENT IN POSITION 9. AS OF 7/98 THERE ARE NO 'D' TYPE PIRPS.

8WB:	ENTRY BELONGS TO ANOTHER DD/PP

THIS MESSAGE IS USALLY FOUND IN CONJUNCTION WITH MESSAGE 8WA (NO EXISTING ENTRY FOUND). IT ONLY APPLIES TO THE BILL OF LADING UPDATE TRANSACTION (APPLICATION LN). WHEN A FILER ATTEMPTS TO TRANSMIT A BILL OF LADING UPDATE ACTION AGAINST AN ENTRY FOR WHICH NO PROVISIONAL SELECTIVITY MESSAGE HAS BEEN ISSUED VIA ABI, MESSAGE 8WA WILL BE ISSUED, AS WILL THIS MESSAGE.

LU1:	LUMBER PERMIT/ORIG CNTRY INVALID

LUMBER PERMIT CANNOT BE ENTERED FOR COUNTRY OF ORIGIN OF 'CA' .

591:	LINE ITEMS INVALID FOR ENTRY TYPE

THIS MESSAGE WILL RARELY BE OBSERVED ON ABI TRANSMISSIONS UNLESS THE FILER MANAGES TO TRANSMIT AN ENTRY TYPE IN THE EI APPLICATION (10 REC, POS 71-72) THAT DOES NOT PERMIT THE REPORTING OF LINE ITEM DETAILS (40-62 RECORDS). USUALLY, THE ENTRY TYPE WILL BE THE ERROR (SUCH AS REPORTING A NON-EXISTENT ENTRY TYPE). MOST AUTOMATED SYSTEMS WILL NOT ALLOW FILERS TO USE ENTRY TYPES THAT ARE NOT CURRENTLY USED FOR IMPORT TRANSACTIONS. THUS, THIS MESSAGE WILL RARELY SURFACE.

BRJ:	AGGREGATE: ALL AMTS MUST BE ZERO

IF THE RECON IS AN AGGREGATE, ALL MONETARY AMOUNTS ON THE 'R20' IMPORT ENTRY ASSOCIATION RECORDS MUST BE ZERO.

215:	INVALID TEAM NUMBER

REFERENCE APPLICATION JJ, REC D10, POS 40-42:  FOR DRAWBACK ENTRY TYPES WHERE THE 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

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.

 Next 10 >>Showing results 1 to 25 of 1405