DOC

In-bond & Vessel DepartureArrival Message - CBPgov

By Connie Hunt,2014-02-07 10:58
7 views 0
In-bond & Vessel DepartureArrival Message - CBPgovIn,in,&,&,Bond,bond

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1

    In-bond and Vessel

    Departure/Arrival Message

    Provides descriptions and format requirements for each data element contained

    within a transaction record input by a carrier, port authority, or service

    bureau to transmit in-bond or vessel departure/arrival to the

    U.S. Customs and Border Protection (CBP) Data Center.

TRANSACTION PROCESSING .. ............. ............ ............. .......................... ............. ............ .. ICM-3

INPUT RECORD USAGE MAP ... ............. ............ ............. .......................... ............. ............ .. ICM-4

    This section describes the Mandatory/Conditional/Optional designation for each record, relationships between records, and looping constraints.

OUTPUT RECORD USAGE MAP ............. ............ ............. .......................... ............. ............ .. ICM-5

    This section describes the Mandatory/Conditional designation for each output record, relationships between records, and looping constraints.

RECORD DESCRIPTIONS

    Record Identifier ACR . ............. ............. ............ ............. .......................... ............. ............ .. ICM-7

    The Transaction Control Header (ACR) Record provides data element descriptions and format

    requirements for the record beginning a transaction file.

    Record Identifier M01 .. ............. ............. ............ ............. .......................... ............. ............ .. ICM-8

    The Manifest Record provides data element descriptions and format requirements for transmitting manifest

    data.

    Record Identifier M02 ... ............. ............. ............ ............. .......................... ............. ............ ICM-10

    The Manifest Continuation Record provides data element descriptions and format requirements for

    transmitting the carrier-assigned batch number.

    Record Identifier P01..... ............. ............. ............ ............. .......................... ............. ............ ICM-11

    The Port Record provides data element descriptions and format requirements for transmitting port data.

    Record Identifier H01 ... ............. ............. ............ ............. .......................... ............. ............ ICM-12

    The In-bond and Vessel Departure/Arrival Record provides data element descriptions and format

    requirements for transmitting the arrival/export of an in-bond movement or vessel arrival.

    Record Identifier H02 ... ............. ............. ............ ............. .......................... ............. ............ ICM-17

    The In-bond and Vessel Departure/Arrival Record provides data element descriptions and format

    requirements for transmitting the foreign port of departure of the vessel and arrival/export of an in-bond

    movement at the container/equipment level. It also may be used to report the name of the vessel exporting

    the in-bond by water.

    Record Identifier W01 (Output Only) ....... ............ ............. .......................... ............. ............ ICM-19

    The Error Record provides data element descriptions and format requirements for transmitting error

    conditions for each data element in error.

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-1

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1

    Record Identifier W02 (Output Only) ....... ............ ............. .......................... ............. ............ ICM-20

    The Message Acceptance Record provides data element descriptions and format requirements for transmitting the cumulative result of an In-bond and Vessel Departure and Arrival transaction.

Record Identifier ZCR .. ............. ............. ............ ............. .......................... ............. ............ ICM-21

    The Transaction Control Trailer (ZCR) Record provides data element descriptions and format requirements for the record ending a transaction file.

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-2

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1

    TRANSACTION PROCESSING

    This function may be used to arrive or export in-bond movements in destination ports, depart vessels from a foreign port, arrive vessels in discharge ports, change the EDA for a vessel, and transfer in-bond liability.

    A vessel departure message (HI) must be sent for each foreign port where cargo (including FROB and IIT) is loaded on a vessel destined for the United States.

    Carriers, port authorities, and service bureaus authorized to participate in electronic vessel arrivals must arrive all vessels in a designated port by this method. When the vessel operator arrives a vessel, the arrival is cascaded to all related manifests by referencing the Unique Voyage Identifier (UVI).

    This transaction can also be used to replace the Unique Voyage Identifier for a vessel. When the vessel operator replaces the Unique Voyage Identifier, the update is cascaded to all related manifests. When a SLOT charter replaces the Unique Voyage Identifier, the update applies only to the individual manifest. The Unique Voyage Identifier cannot be changed after a vessel is

    arrived. The ability to replace the Unique Voyage Identifier is for FUTURE USE.

    When an in-bond movement arrives at the port of in-bond destination, participating carriers, NVOCC, port authorities, and service bureaus must transmit the arrival data. In-bond and Vessel Departure/Arrival Messages are reported using an Application Identifier (on ACR record) of “HI”. The corresponding outbound response Application Identifier (on ACR record) is “HR”.

    This chapter provides descriptions and format requirements for each data element contained within each In-bond and Vessel Departure/Arrival input or output response record. Format the accumulated data into the prescribed record formats as outlined in this chapter. Refer to the sections on Input Record Usage Map and Output Record Usage Map for a layout of mandatory, conditional, and optional records and looping structures.

General Rules for Input Transmissions and Responses from CBP:

; Spaces are transmitted in all data elements marked „filler‟.

    ; Transmit ONLY uppercase ENGLISH alphabetic data.

    ; Transmit ONLY displayable characters found on a standard keyboard. Low-values, carriage

    return characters, or other non-standard characters must NOT be transmitted.

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-3

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1

    INPUT RECORD USAGE MAP

    The following table illustrates how the automated interface expects repeating groups to be structured within an In-bond and Vessel Departure/Arrival Message. Additional notes are provided for clarification on looping structures.

In-bond and Vessel Departure/Arrival (HI) Record Usage Map:

Record Req. Max Loop

    ID Name Des. Use Repeat Notes

    Block Control Grouping M 1

    Transaction Control Header M 1 ACR

     Manifest Grouping M 99

    Manifest M 1 1 M01

    Manifest Continuation Record C 1 M02

     Port Grouping M 20

    Port M 1 1 P01

     Arrival Grouping M 9999

    In-bond and Vessel Arrival M 1 2 H01

    Arrival/Export Reference Information C 1 3 H02

     Transaction Control Trailer M 1 ZCR

    Designation: M = Reporting Mandatory; C = Reporting Conditional; O = Reporting Optional

Note 1:

    Under certain conditions AMS will not edit all of the typically required fields for the header records (M01 and P01) in In-bond and Vessel Departure/Arrival Messages at the container/equipment level. The conditions for when specific fields are required are included in the detailed record descriptions.

Note 2:

    The In-bond and Vessel Departure/Arrival Record (H01) is transmitted to notify CBP of an arrival, or export for in-bond movement, vessel departure/arrival, or a transfer of in-bond liability.

Note 3:

    The In-bond and Vessel Departure/Arrive Record (H02) is transmitted to notify CBP of an in-bond arrival, export, and transfer of liability at the container/ equipment level. It is a conditional record that accompanies an H01. It may also be used to identify the foreign port of lading. Lastly, it contains the exporting vessel name and method of transportation for in-bonds exported by water. This record may be used instead of the I02 Record, Export vessel information in the MI application, when it was not known at the time of bill creation.

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-4

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1

    OUTPUT RECORD USAGE MAP

    The M01, M02, and P01 are always returned in the response from CBP. Additionally the H01 record will be conditionally returned in the response message when one or more errors are determined for the H01/H02 grouping. When one or more error(s) are determined as a result of processing a given transaction, each record in-error is returned in the response message and is immediately followed by one or more Error records (W01) describing the nature of the error. The Message Acceptance/Rejection record (W02) provides summary information on the number of In-bond and Vessel Events accepted/rejected, and is included at the end of a response transaction prior to the ZCR record.

    Conditional output records and fields will be populated only if the corresponding records and fields were included in the inbound In-bond and Vessel Departure and Arrival transmission.

    The following table illustrates how the automated interface expects repeating groups to be structured within an In-bond and Vessel Departure and Arrival Response (HR). Additional notes are provided for clarification on looping structures.

    Outbound Response for In-bond and Vessel Departure and Arrival (HR) Record Usage Map:

Record Req. Max Loop

    ID Name Des. Use Repeat Notes

    Block Control Grouping M 1

    Transaction Control Header M 1 ACR

     Manifest Grouping M 99 1

    Manifest M 1 2 M01

    Error Record C 10 W01

    Manifest Continuation Record C 1 2 M02

    Error Record C 10 W01

     Port Grouping M 20

    Port M 1 2, 3 P01

    Error Record C 10 3 W01

     Event Grouping C 9999 4

    In-bond and Vessel Event M 1 5 H01

    Error Record C 10 W01

    Reference Information C 1 H02

    Error Record C 10 W01

     Error Record C 10 7 W01

    Message Acceptance/Rejection M 1 6 W02

    Transaction Control Trailer M 1 ZCR

Designation: M = Reporting Mandatory; C = Reporting Conditional

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-5

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1

    Note 1:

    When In-bond and Vessel Departure and Arrival (HI) messages are received with multiple Manifest groupings in a single input message, a separate outbound response is generated for each separate Manifest grouping (M01 through H02 records), each with its own Transaction Control Header and Trailer records.

Note 2:

    The Manifest records (M01) and Port record (P01) are always returned in the response. If the M02 record is provided on the inbound message, it will be returned in the response.

Note 3:

    For an error at the Manifest level (M01 or M02), all In-bond and Vessel events will be rejected.

Note 4:

    For an error on a specific Event grouping (records H01 and H02), only the affected Event grouping is rejected, and processing continues to the next Event grouping.

Note 5:

    For error(s) on any H02 record in a given Event grouping, the H01 record for that Event will be returned in the response message prior to the record(s) in error.

    For error(s) on the H01 record, the H01 record will be returned in the response message, immediately followed by 1 or more W01 records describing the specific error condition(s); if present, the H02 record within that group will still be validated and if in error, returned in the response, immediately followed by 1 or more W01 records as appropriate.

Note 6:

    The Message Acceptance/Rejection record (W02) is always included immediately prior to the Transaction Control Trailer record (ZCR) and provides summary information including number of In-bond and Vessel Events accepted and rejected.

    A successful (error-free) input transaction will result in a response consisting only of the records: ACR, M01, M02 (optional), P01, W02, and ZCR.

Note 7:

    This occurrence of the W01 Record is used to report errors at the ACR or ZCR level.

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-6

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1 Record Identifier ACR

    Transaction Control Header Record

    This record signals the beginning of a transaction file.

Record Identifier ACR

    Data Element Length/Position Status Description Note

    Class

    Control Identifier 3A 1-3 M Must always equal ACR.

    AMS User Code 4AN 4-7 M A code representing the carrier, CBP-

    assigned port authority, or service bureau.

    Filler 6AN 8-13 M Space fill.

    Application 2A 14-15 M A code representing the type of application

    Identifier detail data contained within the block. For

    In-bond and Vessel Departure and Arrival

    input transactions, set to HI. In the

    outbound response messages, Application

    Identifier is HR.

    Date 6N 16-21 C A date in YYMMDD (year, month, day) 1

    format representing the date of processing.

    Time 6N 22-27 C A time in HHMMSS (hours, minutes, 1

    seconds) format representing the time of

    processing. Eastern Standard/Daylight

    Time should be reported.

    Batch Number 5N 28-32 C A CBP-generated 5-position numeric code 1

    from 00001 to 99999. The batch number is

    used in conjunction with the date of

    transmission to uniquely identify a user

    transmission.

    Filler 48AN 33-80 M Space fill.

Note 1:

This data is not transmitted by the participant in input transaction control records. It is returned

    to the participant in output transaction control records. Do not use this field on input.

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-7

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1

    Record Identifier M01

    Manifest Record

    This is a mandatory record used to transmit vessel information and specific manifest data. Once the original manifest (ACR record positions 14-15 code „MI‟) has been transmitted and accepted,

    the M01 record becomes „frozen‟. In any subsequent amendments or actions (ACR record positions 14-15 code „AI‟,‟HI‟, “II‟, „TI‟) the mandatory and required elements in the M01 record in the original manifest must be submitted. This means if the vessel name (positions 12-34) were submitted in the original manifest it is required in any subsequent amendments or actions. If the IMO Lloyds vessel code (positions 35-39) were submitted in the original manifest it is required in any subsequent amendments or actions. If both a vessel name (positions 12-34) and the IMO Lloyds vessel code (positions 52-58) were submitted in the original manifest, they are required in any subsequent amendments or actions

Record Identifier M01

    Data Element Length/Position Status Description Note

    Class

    Control Identifier 3AN 1-3 M Must always equal M01.

    Carrier Code 4AN 4-7 M A Standard Carrier Alpha Code (SCAC) 1

    representing the automated carrier/NVOCC

    reporting the In-bond and Vessel

    Departure/Arrival Message.

    Mode of 2N 8-9 M A code indicating the Mode of Transport of 2

    Transportation Code the Carrier in the Carrier Code data

    element. Valid codes are:

    10 = Vessel, non-container, or unable to

    determine if container (Including

    Lightered, Land Bridge and LASH)

    11 = Vessel Containerized (Container)

    Vessel Country 2A 10-11 M An International Organization for 2

    Code Standardization (ISO) country code

    representing the flag country of the vessel.

    Refer to CAMIR Appendix G for valid

    codes.

    Vessel Name 23AN 12-34 C A valid vessel name entered using no 2

    slashes. The vessel name will always be

    populated in the response transmission from

    CBP when either the Vessel Name or

    Vessel Code is provided in the input

    transaction.

    Voyage Number 5AN 35-39 M The voyage number entered using no 2

    slashes.

    Filler 5AN 40-44 M Space fill.

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-8

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1

    Record Identifier M01

    Data Element Length/Position Status Description Note

    Class

    Manifest Sequence 6N 45-50 C The manifest sequence number. This 2

    Number number is a carrier-assigned sequence

    number. The system-generated default is

    one (000001). It may be a date. Once

    transmitted, it cannot be changed. All

    subsequent transmissions for the manifest

    must use the original manifest sequence

    number.

    Filler 1AN 51 M Space fill.

    Vessel Code 7AN 52-58 C International Maritime Organization (IMO) 2

    Code issued by Lloyds representing the

    importing vessel.

    Filler 22AN 59-80 M Space fill.

Note 1:

    The Standard Carrier Alpha Code (SCAC) is issued by the National Motor Freight Traffic Association, Inc. located at 1001 North Fairfax Street, Suite 600, Alexandria, VA 22314. The Internet URL is: www.NMFTA.org. In the case of water carriers who own their containers, the SCAC is issued by the Intermodal Association of North America located at 6410 Kenilworth Ave., Suite 108, Riverdale, MD 20737.

Note 2:

    The M01 record must be provided for all actions performed. The specific field requirements are described below for vessel arrival (H01 Message Code = 4), vessel foreign port departure (H01 Message Code = 9), replace Unique Voyage Identifier (H01 Message Code = U-Future Use), and change in Estimated Date of Arrival (H01 Message Code = Y):

    ; Mode of Transportation, Vessel Country Code and Voyage number are required fields ; The Vessel Name, the Vessel Code, or both must be provided on the M01 record. ; The Manifest Sequence Number field is required if it was provided in the original manifest.

    These fields are only validated for message codes 4, 9, U (Future Use), and Y.

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-9

    Customs Ocean Automated Manifest Interface Requirements Ocean ACE M1 Record Identifier M02

    Manifest Continuation Record

This is a conditional record used to transmit the carrier-assigned batch number.

Record Identifier M02

    Data Element Length/Position Status Description Note

    Class

    Control Identifier 3AN 1-3 M Must always equal M02.

    Carrier-Assigned 30AN 4-33 M The carrier-assigned batch number. The

    Batch Number participants may use this field for internal

    tracking purposes.

    Filler 47AN 34-80 M Space fill.

     CAMIR V1.5 2012 In-bond and Vessel Departure/Arrival Message ICM-10

Report this document

For any questions or suggestions please email
cust-service@docsford.com