| Title: | FDA/BTA CHANGES FOR 'WP' APPLICATION |
|---|---|
| Date: | 2003-11-05 |
| To: | abi |
| Links: | previous, next |
SEE ALSO ADMIN MESSAGES 03-2619, DATED NOVEMBER 4, 2003 AND 03-2540,
DATED OCTOBER 24, 2003. MESSAGE 03-2540 PROVIDED INFOMATION ON THE
HARMONIZED TARIFF CHANGES FOR FDA/BTA. MESSAGE 03-2619 PROVIDED THE
FDA/BTA MODIFICATIONS TO THE 'EI', 'HI', AND 'HN' ABI ENTRY APPLICATION
RECORDS.
THE CURRENT 'WP' IN-BOND UPDATE APPLICATION HAS BEEN MODIFIED TO ACCEPT
FDA/BTA DATA. THIS MODIFICATION WILL PERMIT FDA/BTA PRIOR NOTICE DATA
TO BE PROVIDED FOR IN-BONDS, FTZ ADMISSIONS, AND OTHER TRANSACTIONS NOT
INVOLVING AN ENTRY. ADDITIONALLY, THE REVISED 'WP' MAY BE USED TO SEND
FDA PRIOR NOTICE DATA FOR AN ENTRY INDEPENDENTLY OF THE 'EI', 'HI', AND
'HN' ENTRY TRANSACTIONS.
THIS CAPABILITY WILL ENABLE CURRENT 'QP' AND CAFES USERS AND OTHER NON
LICENSED ENTITIES TO SUBMIT DATA INDEPENDENTLY RATHER THAN AS PART OF
ENTRY PROCESSING. THE 'WP' APPLICATION CAN ONLY BE USED FOR FILING BTA
PRIOR NOTICE DATA. THE CURRENT FDA 801(A) DATA MUST STILL BE SUBMITTED
VIA THE VARIOUS ENTRY PROCESSES. PLEASE NOTE THAT NOTHING PRECLUDES A
LICENSED BROKER, OR IMPORTER FILING VIA ABI ON THEIR OWN ACCOUNT, FROM
USING THE REVISED 'WP' APPLICATION TO SEND FDA/BTA PRIOR NOTICE DATA
FOR AN ENTRY IN ADVANCE OF ACTUALLY FILING THE ENTRY VIA ABI.
IN ORDER TO MINIMIZE THE IMPACT ON FILERS, THE CURRENT OGA RECORD
FORMATS WILL BE UTILIZED. FOR FDA-SPECIFIC DATA, THE CURRENT 'OI'
AND 'FD01' THROUGH 'FD05' RECORDS WILL BE USED. FDA/BTA PRIOR NOTICE
DATA WILL BE SUBMITTED AS REQUIRED UTILIZING NEW AFFIRMATIONS OF
COMPLIANCE AND ASSOCIATED AFFIRMATION OF COMPLIANCE QUALIFIERS IN THESE
RECORDS. THE CURRENT 'OI' AND 'FD01 THRU 'FD05' RECORD LAYOUTS APPEAR
IN THE CATAIR IN THE "OTHER GOVERNMENT AGENCIES" SECTION.
FOR 'WP' FOR PRIOR NOTICE, THE CURRENT 'W10' INPUT RECORD WILL BE USED.
TWO NEW ACTION CODES HAVE BEEN IDENTIFIED FOR THE EXCLUSIVE PURPOSE OF
SEND BTA PRIOR NOTICE DATA:
ACTION CODE '8' WILL BE USED TO INDICATE THAT THE 'WP' IS BEING
USED TO TRANSMIT PRIOR NOTICE DATA FOR AN IN-BOND TRANSACTION.
ACTION CODE '9' WILL BE USED TO INDICATE THAT THE 'WP' IS BEING USED
TO TRANSMIT PRIOR NOTICE DATA FOR OTHER THAN AN IN-BOND
TRANSACTION (I.E. - AN FTZ ADMISSION, ENTRY, ETC.)
THE 'W10' RECORD WILL BE SENT WITH A CODE OF '8' OR '9', AS APPROPRIATE,
IN POSITION 3. THE BALANCE OF THE 'W10' RECORD WILL BE SPACE-FILLED.
IMMEDIATELY FOLLOWING THE 'W10' WILL BE THE FIRST 'OI' RECORD FOLLOWED
BY THE 'FD01' THRU 'FD05' RECORDS FOR THE FIRST FDA BTA ITEM. THE LAST
'FD05' FOR THAT ITEM SHOULD BE FOLLOWED BY THE NEXT 'OI' AND 'FD01' THRU
'FD05' FOR THE NEXT ITEM, ETC.
A PARTIAL LIST OF THE AFFIRMATIONS OF COMPLIANCE ASSOCIATED TO BTA
CAN BE FOUND IN ADMIN 03-2619. THOSE AFFIRMATONS APPLY TO BOTH BTA
DATA SUBMITTED FOR ENTRIES AND FOR BTA DATA SUBMITTED FOR IN-BONDS AND
OTHER TRANSACTIONS. MANDATORY, CONDITIONAL AND OPTIONAL DATA
REQUIREMENTS FOR THOSE AFFIRMATIONS IN MESSAGE 03-2619 ALSO APPLY TO
PRIOR NOTICE DATA SENT VIA 'WP'.
THE FOLLOWING ADDITIONAL AFFIRMATION OF COMPLIANCE CODES APPLY
EXCLUSIVELY TO TRANSACTIONS SENT VIA THE 'WP' APPLICATION:
AFFIRMATION CODE QUALIFIER
EFC ENTRY FILER CODE. THIS IS CONDITIONAL AND
WILL BE PROVIDED IF BTA DATA FOR AN ENTRY
IS BEING PROVIDED INDEPENDENTLY VIA THE
'WP' APPLICATION.
ENT ENTRY SEQUENCE NUMBER. THIS IS THE
8-DIGIT ENTRY NUMBER. THIS IS CONDITIONAL
AND WILL BE PROVIDED IF BTA DATA FOR AN
ENTRY IS BEING PROVIDED INDEPENDENTLY VIA
THE 'WP' APPLICATION.
ETP THIS IS THE 2-DIGIT ENTRY TYPE. THIS IS
CONDTIONAL AND WILL BE PROVIDED IF BTA
DATA FOR AN ENTRY IS BEING PROVIDED
INDEPENDENTLY VIA THE 'WP' APPLICATION.
INB IN-BOND NUMBER. THIS IS CONDITIONAL AND
WILL BE PROVIDED IF BTA DATA IS BEING SENT
VIA 'WP' FOR AN IN-BOND TRANSACTION.(SEE
ACTION CODE '8' DESCRIPTION, ABOVE.)
INT IN-BOND TYPE. MUST BE 61 OR 62. THIS IS
CONDITIONAL AND WILL BE SENT IF BTA DATA
IS BEING SENT VIA 'WP' FOR AN IN-BOND
TRANSACTION.
MOT MODE OF TRANSPORT. THIS IS MANDATORY FOR
BTA DATA BEING SENT VIA 'WP'
FIR LOCATION OF GOODS (FIRMS CODE).
FTZ FTZ ADMISSION NUMBER. THIS IS CONDITIONAL
AND MUST BE PROVIDED IF THE BTA DATA BEING
SENT IS FOR AN FTZ ADMISSION.
SCA IMPORTING CARRIER CODE. CONDITIONAL AND
MUST BE PROVIDED IF TRANSPORT VIA COMMON
CARRIER. VALID SCAC OR IATA CODE.
HTS HARMONIZED TARIFF NUMBER. OPTIONAL DATA.
SHOULD BE PROVIDED IF AVAILABLE AND MAY BE
PROVIDED AT THE 6, 8 OR 10 DIGIT LEVEL.
VALID HARMONIZED TARIFF NUMBER.
IMM IMPORTER LAST NAME. THIS IS CONDITIONAL
FOR BTA DATA BEING SENT VIA 'WP'. MAY BE
DIFFERENT FROM CONTACT NAME IN 'FD04'
RECORD. THIS SHOULD BE PROVIDED IF
IMPORTER IS AN INDIVIDUAL.
IMF IMPORTER FIRST NAME. THIS IS CONDITIONAL
FOR BTA DATA BEING SENT VIA 'WP'. MAY BE
DIFFERENT FROM CONTACT NAME IN 'FD04'
RECORD. THIS SHOULD BE PROVIDED IF
IMPORTER IS AN INDIVIDUAL.
IMP IMPORTER PHONE NUMBER. THIS IS MANDATORY
FOR BTA DATA BEING SENT VIA 'WP'. MAY BE
DIFFERENT FROM CONTACT PHONE NUMBER IN
'FD04' RECORD.
IMX IMPORTER FAX NUMBER. THIS IS MANDATORY
FOR BTA DATA BEING SENT VIA 'WP'. IF
NONE, ZERO FILL.
IME IMPORTER EMAIL. THIS IS MANDATORY FOR
BTA DATA BEING SENT VIA 'WP'. IF NONE,
ENTER 'NONE'.
IMC IMPORTER FIRM NAME. THIS IS CONDITIONAL
FOR BTA DATA BEING SENT VIA 'WP'. THIS
SHOULD BE PROVIDED IF IMPORTER IS OTHER
THAN AN INDIVIDUAL.
IM1 LINE 1 OF IMPORTER ADDRESS. THIS IS
MANDATORY FOR BTA DATA SENT VIA 'WP'.
IM2 LINE 2 OF IMPORTER ADDRESS. OPTIONAL.
USE AS NEEDED.
IMU IMPORTER ADDRESS CITY. THIS IS MANDATORY
FOR BTA DATA SENT VIA 'WP'.
IMS IMPORTER STATE CODE OR CANADIAN PROVINCE.
IF A COUNTRY OTHER THAN U.S. OR CANADA,
USE 'FN'. THIS IS MANDATORY FOR BTA DATA
SENT VIA 'WP'.
IMZ IMPORTER ZIP OR MAIL CODE. THIS IS
MANDATORY FOR BTA DATA SENT VIA 'WP'.
IMA IMPORTER COUNTRY CODE (ISO CODE). THIS
IS MANDATORY FOR BTA DATA SENT VIA 'WP'.
COM CONSIGNEE LAST NAME. THIS IS CONDITIONAL
FOR BTA DATA BEING SENT VIA 'WP'. MAY BE
DIFFERENT FROM CONTACT NAME IN 'FD04'
RECORD. THIS SHOULD BE PROVIDED IF THE
CONSIGNEE IS AN INDIVIDUAL.
COF CONSIGNEE FIRST NAME. THIS IS CONDITIONAL
FOR BTA DATA BEING SENT VIA 'WP'. MAY BE
DIFFERENT FROM CONTACT NAME IN 'FD04'
RECORD. THIS SHOULD BE PROVIDED IF THE
CONSIGNEE IS AN INDIVIDUAL.
COP CONSIGNEE PHONE NUMBER. THIS IS MANDATORY
FOR BTA DATA BEING SENT VIA 'WP'. MAY BE
DIFFERENT FROM CONTACT PHONE NUMBER IN
'FD04' RECORD.
COX CONSIGNEE FAX NUMBER. THIS IS MANDATORY
FOR BTA DATA BEING SENT VIA 'WP'. IF
NONE, ZERO FILL.
COE CONSIGNEE EMAIL. THIS IS MANDATORY FOR
BTA DATA BEING SENT VIA 'WP'. IF NONE,
ENTER 'NONE'.
COC CONSIGNEE FIRM NAME. THIS IS CONDITIONAL
FOR BTA DATA BEING SENT VIA 'WP'. THIS
SHOULD BE PROVIDED IF THE CONSIGNEE IS
OTHER THAN AN INDIVIDUAL.
CO1 LINE 1 OF CONSIGNEE ADDRESS. THIS IS
MANDATORY FOR BTA DATA SENT VIA 'WP'.
CO2 LINE 2 OF CONSIGNEE ADDRESS. OPTIONAL.
USE AS NEEDED.
COU CONSIGNEE ADDRESS CITY. THIS IS MANDATORY
FOR BTA DATA SENT VIA 'WP'.
COV CONSIGNEE STATE CODE OR CANADIAN PROVINCE.
IF A COUNTRY OTHER THAN U.S. OR CANADA,
USE 'FN'. THIS IS MANDATORY FOR BTA DATA
SENT VIA 'WP'.
COZ CONSIGNEE ZIP OR MAIL CODE. THIS IS
MANDATORY FOR BTA DATA SENT VIA 'WP'.
COA CONSIGNEE COUNTRY CODE (ISO CODE). THIS
IS MANDATORY FOR BTA DATA SENT VIA 'WP'.
AGAIN, THE ABOVE AFFIRMATIONS OF COMPLIANCE ARE ADDITIONAL AND APPLY
ONLY TO PRIOR NOTICE TRANSACTIONS SENT VIA 'WP'. THEY ARE IN ADDITION
TO THOSE CODES PREVIOUSLY PROVIDED IN ADMIN MESSAGE 03-2619. SO, FOR
ANY PRIOR NOTICE SENT VIA 'WP', BOTH SETS OF CODES APPLY. THOSE THAT
ARE LISTED AS MANDATORY IN THE PREVIOUS MESSAGE ARE ALSO MANDATORY FOR
'WP'.
IN ADDITION TO THE ABOVE AFFIRMATIONS OF COMPLIANCE, THE FOLLOWING
DATA ELEMENTS IN THE FD01 THROUGH FD05 RECORDS WILL BE MANDATORY FOR
ITEMS SUBJECT TO PRIOR NOTICE AND SENT VIA THE REVISED 'WP' TRANSACTION:
FD02 RECORD UNIT 1 - QUANTITY (POSITIONS 5-14)
FD02 RECORD UNIT 1 - UNIT OF MEASURE (POSITIONS 15-18)
FD04 RECORD CONTACT NAME (POSITIONS 19-28)
FD04 RECORD CONTACT TELEPHONE NBR (POSITIONS 29-38)
PRIOR NOTICE DATA PRESENTED VIA AFFIRMATIONS OF COMPLIANCE WILL BE
SUBJECTED TO BASIC EDITS SUCH AS VALID DATE FORMATS, VALID COUNTRY
CODES, VALID DDPP, ETC. ANY DATA NOT PASSING THESE WILL BE REJECTED
WITH THE APPROPRIATE ERROR CODE.
THE 'WP' ACCEPTANCE OR CBP DATA REJECTION WILL BE RETURNED VIA THE
EXISTING 'WT' TRANSACTION IN THE WT95 OUTPUT RECORD.
THE EXISTING FORMATS FOR THE 'WP' WP10 INPUT RECORD AND THE 'WT' WT95
RECORD MAY BE FOUND IN THE CATAIR IN THE "IN-BOND" SECTION.
THE NEW ABI 'BN' APPLICATION AS DESCRIBED IN ADMIN MESSAGE 03-2619 WILL
ALSO BE USED TO PROVIDE PRIOR NOTICE-SPECIFIC LINE ITEM PROCESSING
RESULTS FOR THE 'WP' TRANSACTION AT THE ITEM LEVEL TO THE TRADE.
THE NEW 'BN' APPLIACTIONS CONSIST OF TWO OUTPUT RECORD TYPES, BN01'
AND 'BN02'. THE BN01 RECORD WILL BE RETURNED ONCE AT THE HEADER LEVEL
(I.E. - THE IN-BOND NUMBER, ENTRY NUMBER, ETC) AND THERE WILL BE AS
MANY BN02 RECORDS AS THERE ARE PRIOR NOTICE FDA ITEMS. 'BN' IS OUTPUT
ONLY.
FOLLOWING ARE THE RECORD LAYOUT REQUIREMENTS FOR THE 'BN' APPLICATION:
RECORD IDENTIFIER BN01 (OUTPUT) - ONE RECORD PER FDA PRIOR NOTICE HEADER
DATA ELEMENT LENGTH/CLASS POSITION STATUS DESCRIPTION
CONTROL ID 4AN 1-4 M MUST ALWAYS = BN01'
HEADER ID 1AN 5 M MUST ALWAYS =
'A' - AIR WAYBILL (+
HOUSE AIR WAYBILL
IF USED)
'E' - ENTRY NUMBER
'I' - INBOND NUMBER
'B' - BILL OF LADING NBR
'F' - FTZ ADMISSION NBR
HEADER KEY 25AN 6-30 M MUST BE THE VALUE FOR
THE HEADER IDENTIFIER,
AS APPROPRIATE. (E.G. -
THE ACTUAL IN-BOND NBR,
ENTRY NBR, ETC.). USE
THE ACTUAL NUMBER WITH
NO DASHES, SLASHES, OR
OTHER SPECIAL CHARACTERS
FILLER 50X 31-80 M SPACE FILL
RECORD IDENTIFIER BN02 (OUTPUT) - REPEATABLE AS NEEDED. ONE BN02 RECORD
FOR EACH FDA PRIOR NOTICE ITEM.
DATA ELEMENT LENGTH/CLASS POSITION STATUS DESCRIPTION
CONTROL ID 4AN 1-4 M MUST ALWAYS = BN02'
CBP ENTRY LINE 3AN 5-7 C THE CBP LINE NUMBER WHEN
THE HEADER IDENTIFIER IN
THE BN01 RECORD = 'E'.
THIS WILL ONLY APPLY TO
ENTRIES SENT VIA 'EI',
'HI', OR 'HN'. OTHERWISE
SPACE FILL.
FDA LINE 4AN 8-11 M THE FDA LINE NUMBER
APPLICABLE TO THE
REQUIREMENT.
PRIOR NOTICE
CONFIRMATION NBR 12AN 12-23 C THE CONFIRMATION NUMBER
RECEIVED FROM FDA WHEN
PRIOR NOTICE RCEIVED
MESSAGE IS GENERATED BY
FDA (SEE NOTE 1)
PRIOR NOTICE
LINE MESSAGE 26AN 24-49 M PRIOR NOTICE LINE LEVEL
MESSAGE SUCH AS "PRIOR
NOTICE RECEIVED" OR
"PRIOR NOTICE
SATISFIED". FREE FORM.
PRIOR NOTICE
RECEIPT DATE 8AN 50-57 C RECEIVED FROM FDA WHEN
PRIOR NOTICE RECEIVED
MESSAGE IS GENERATED.
THIS FIELD WILL BE
BLANK WHEN PRIOR NOTICE
SATISFIED MESSAGE IS
RECEIVED. MMDDYYYY
FORMAT. (SEE NOTE 2)
PRIOR NOTICE
RECEIPT TIME 6AN 58-63 C RECEIVED FROM FDA WHEN
PRIOR NOTICE RECEIVED
MESSAGE IS GENERATED.
THIS FIELD WILL BE
BLANK WHEN PRIOR NOTICE
SATISFIED MESSAGE IS
RECEIVED. HHMMSS
FORMAT. (SEE NOTE 2)
PRIOR NOTICE
LINE REJECT
CODES 16AN 64-79 C CODES IDENTIFYING
REJECT REASONS WHEN
PRIOR NOTICE IS
REJECTED.(SEE NOTE 3)
FILLER 1X 80 M SPACE FILL
NOTES:
1. THE PRIOR NOTICE CONFIRMATION NUMBER IS THE VALIDATION AND
CERTFICATION FROM FDA THAT THE PRIOR NOTICE DATA WAS RECEIVED FOR
THE MERCHANDISE. THEI SHOULD BE RETAINED BY THE FILER. THERE WILL BE
A SEPARATE CONFIRMATION NUMBER FOR EACH FDA LINE ITEM.
2. THE PRIOR NOTICE RECEIPT DATE AND TIME ARE RETURNED WHEN FDA
GENERATES A PRIOR NOTICE RECEIVED MESSAGE TO THE FILER FOR THE
MERCAHNDISE. THIS INFORMATION SHOULD BE RETAINED WITH THE
CONFIRMATION NUMBER.
3. FOLLOWING ARE THE VALID LINE REJECT REASON CODES. THESE CODES ARE
POSITIONAL ALLOWING EACH LINE TO HAVE MULTIPLE CODES UP TO 16. WHILE
SOME CODES MAY BE REPEATED, THEIR MEANING IS SPECIFIC RELATIVE TO
THE FIELD IN THE RECORD IN WHICH THEY MAY APPEAR. THUS, FOR EXAMPLE,
AN 'S' IN POSITION 5 INDICATES "INVALID MID FOR SHIPPER" WHILE AN
'S' IN POSITION 10 INDICATES "INVALID COUNTRY OF SHIPPING".
THESE CODES REPRESENT FDA REJECT REASONS. QUESTIONS REGARDING THESE
CODES SHOULD BE DIRECTED TO FDA.
POSITION VALUE REASON
1 'F' FOREIGN CONSIGNEE
2 'R' INVALID REGISTRATION
3 'Q' INVALID QUANTITY
4 'M' INVALID MID FOR MANUFACTURER
5 'S' INVALID MID FOR SHIPPER
6 'I' INVALID IMPORTER
7 'C' INVALID CONSIGNEE
8 'Z' INVALID STATE/ZIP FOR U.S. MANUFACTURER
9 'O' INVALID COUNTRY OF ORIGIN
10 'S' INVALID COUNTRY OF SHIPPING
11 'N' OTHER REJECT REASON, CALL FDA
12 FUTURE USE
13 FUTURE USE
14 FUTURE USE
15 FUTURE USE
16 FUTURE USE
THE COMPLETE CATAIR RECORD LAYOUTS FOR THE REVISED 'WP' APPLICATION
WILL BE AVAILABLE ON THE CBP WEB SITE AS SOON AS POSSIBLE. WE WILL
ADVISE YOU WHEN THEY ARE AVAILABLE.
QUESTIONS MAY BE DIRECTED TO YOUR CLIENT REPRESENTATIVE.