4.  Response and Notification Messages

***In this Chapter***

For this section... See page...

[4.1 Notification Messages 2](#notification-messages)

[4.2 Status Notifications 6](#status-notifications)

[4.3 Event Codes 8](#event-codes)

[4.4 Current Valid Disposition Codes
11](#current-valid-disposition-codes)

## Notification Messages

The structure of the Electronic Data Interchange system provides the
participant with multiple levels of control to ensure data integrity
within a given transmission, functional group, or transaction set. This
is accomplished through the use of header and trailer control segments
designed to uniquely identify the start and end of transmissions,
functional groups and transaction sets.

### Transaction set rejection

All EDI transaction sets associated with a transmission are validated
against the syntax rules associated with the particular EDIFACT or ANSI
X12 standard. The Functional Acknowledgment (FA) transaction set
provides a positive indication that all transactions transmitted were
received and, if errors exist, identifies the specific EDI segment
and/or elements in error along with the reason for error.

The FA message/transaction set in the UN/EDIFACT Standard is the CONTRL
message set. The FA message/transaction set used in the ANSI X12
Standard is the 997 transaction set.

Functional errors are reported in the FA message. Types of functional
errors detected are:

-   Incorrect data type

-   Incorrect field length

-   Missing information

-   Unrecognized code

-   Incorrect segment identifier

-   Special requirements not met

![](media/image1.png){width="6.198611111111111in" height="1.75in"}

Figure 4.1 -- ANSI X12 997 Functional Acknowledgement Implementation
Guide index.

The functional acknowledgement 997 transaction set is further defined in
detail in the Implementation Guides,
[http://www.cbp.gov/xp/cgov/toolbox/about/modernization/carrier_info/ace_edi_drafts/edi_messages/]{.underline}

### Error Reporting

The ANSI X.12 Transaction subset contains the format and establishes the
data contents of the transmission of a functional acknowledgment
transaction set (997) to the original sender to indicate the status of
the transmission with respect to adhering to standards.

The X12 997 FA transaction (below) is returned to the sender as a
receipt indicating the degree to which the message received by the
target EDI system complies with the message construct syntax rules as
defined by the particular standard. The FA message is generated by
translation software.

The Functional Acknowledgement does not imply acceptance of the contents
of the associated transaction sets.

### ANSI Translator error example

The ANSI 997 Transaction set identifies syntax compliance errors in the
particular transaction. The AK3 and AK4 segments in the 997 identify the
location and type of error encountered.

### ANSI Scenario

The following 309 transaction data set was sent to ACE.

![](media/image2.png){width="5.209722222222222in"
height="3.5180555555555557in"}

Figure 4.2 -- 309 Complete with **P401** port code missing

The functional acknowledgment details were displayed in the ACE system
below, note the AK3 and AK4 segments.

![](media/image3.png){width="6.084027777777778in"
height="2.0104166666666665in"}

Figure 4.3 ANSI Functional Acknowledgement details from Raw Data Edits
in ACE indicate that the P401 is missing data.

The following information for error detection was taken from the 997
functional acknowledgement details document located on the CBP website:

[http://www.cbp.gov/linkhandler/cgov/toolbox/about/modernization/carrier_info/ace_edi_drafts/edi_messages/ansi_message_sets/truck997.ctt/truck997.doc]{.underline}

For example AK3\*P4\*13\*2000

+-------------+---------------------------------------------------------+
| Segment     | Description                                             |
+-------------+---------------------------------------------------------+
| AK3         | Segment tag, use to report errors in a data segment     |
+-------------+---------------------------------------------------------+
| \*          | Data element separator                                  |
+-------------+---------------------------------------------------------+
| AK301       | Code defining the segment ID of the data segment in     |
|             | error = P4                                              |
+-------------+---------------------------------------------------------+
| \*          | Data element separator                                  |
+-------------+---------------------------------------------------------+
| AK302       | The numerical count position of this data segment from  |
|             | the start of the transaction set: the transaction set   |
|             | header is count position 1 = P4 segment is located on   |
|             | line 13.                                                |
+-------------+---------------------------------------------------------+
| \*          | Data element separator                                  |
+-------------+---------------------------------------------------------+
| AK303       | Loop Identifier Code =2000                              |
|             |                                                         |
|             | Code identifying a loop within the transaction set      |
|             | which is bounded by the related LS and LE segments      |
|             | (corresponding LS and LE segments must have the same    |
|             | value for loop identifier).                             |
+-------------+---------------------------------------------------------+

For example **AK4\*1\*\*1**

  ------------- ---------------------------------------------------------
  Segment       Description

  AK4           To report errors in a data element or composite data
                structure and to identify the Location of the data
                element.

  \*            Data element separator

  AK401         **Element Position in Segment.** This is used to indicate
                the relative position of the data element in error in
                this data segment, = P401

  \*            Data element separator

  \*            Data element separator

  \*            Data element separator

  AK403         **Data Element Syntax Error** Code indicating the error
                found after syntax edits of a data element. Code 1 =
                Mandatory Data element missing.
  ------------- ---------------------------------------------------------

For additional information on 997 Functional Acknowledgement
definitions, refer to the 997 Functional Acknowledgment Implementation
Guide.

### EDIFACT Translator error example

The EDIFACT CONTRL Message set identifies syntax compliance errors in
the particular transaction. The UCS segment in the CONTRL message
identifies the location and type of error encountered.

EDIFACT Scenario

The following CUSCAR transaction data set was sent to ACE. Note in line
21 -- the RFF segment is missing the Shipment Control Number.

![](media/image4.png){width="5.795833333333333in"
height="4.008333333333334in"}

Figure 4.4 The above CUSCAR example is missing an RFF segment after the
DOC segment.

For EDIFACT transaction sets, the functional acknowledgement details
were displayed in the ACE system below, note the UCS segments.

![](media/image5.png){width="4.813888888888889in"
height="3.097916666666667in"}

Figure 4.5 - Identifies an EDIFACT CONTRL message image that identifies
a segment is missing.

The following information for error reporting syntax was taken from the
CONTRL document located on the CBP website:
http://www.cbp.gov/linkhandler/cgov/toolbox/about/modernization/carrier_info/ace_edi_drafts/edi_messages/ctlset.ctt/ctlset.rtf

For example **UCS+16+15**

  ------------- ---------------------------------------------------------
  Segment       Description

  UCS           Segment Error Indication

  \+            Data element separator

  16            Segment position in Message -- the numerical count
                position of a specific segment

  \+            Data element separator

  15            Mandatory data segment missing, that is RFF segment
  ------------- ---------------------------------------------------------

The receiver of transaction sets which fail to pass the edit or audit
procedures may reject the entire transaction set, issuing the
appropriate in-formation in a functional acknowledgment transaction set.
(set 355) When a rejection occurs, manual or automatic means external to
the data interchange process are used by the sender for correction. The
entire transaction set may be retransmitted without any reference to the
previous error.

### Retransmission of rejected Transaction Sets

Transaction sets rejected previously must be retransmitted in full after
corrections are made by the sending system.

Accepted transaction sets are never retransmitted even when they are
within a functional group which may have contained one or more rejected
sets. There are significant operational exceptions to this statement. If
the multiple message group contains a 'delete Trip' followed by 'add
Trip' and the 'delete' fails for syntax reasons, the 'add would thereby
need retransmission.

## Status Notifications 

### For ANSI 

This X.12 Transaction set contains the format and establishes the data
contents of the Customs Status Information Transaction Set (350) for use
within the context of an Electronic Data Interchange (EDI) environment.
The transaction set can be used by the Customs Service (CS) to supply
carriers, terminal operators, port authorities, and service providers
with cargo release and cargo hold information for import shipments. It
can also be used by the CS to provide exporters or their agents,
carriers, and service providers with information pertaining to export
shipments.

If the consist (358) changes the port of arrival, USCS will send an
event advisory message to the brokers identified in the N1 segments of
the manifest, the carrier and secondary notify parties. A status
notification is sent to all parties associated with the manifest.

The trigger for the 350 release will be a conveyance arrival message
(AAD) when the truck crosses the border for immediate release, *see
Section 4.7 Event Codes.*

![](media/image6.png){width="6.997916666666667in"
height="1.4256944444444444in"}

Figure 4.6 - Identifies an ACE System Raw Data Edits 350 status
notification.

If the transmitted e-manifest has issues, then the customer will need to
work with U.S. Customs to resolve these issues. The customer is advised
via another 350 status notification of the HOLD's resolution. There are
three types of system generated HOLDs. They are:

-   Shipment related

-   Equipment related

-   Crew/Conveyance related

The M10 and P4 segments are required for import shipments for CBP.

For example: an A4 HOLD indicates:

  --------- ------------ ------------------------------------------------
  **A4**    **Entry not  Advisory Generated as a result of FDA/BTA
            on file**    processing: this notification Is sent on the
                         actual or estimated date of arrival, whichever
                         comes first to indicate the entry data is not
                         yet on file for a PAPS or BCS shipment

  --------- ------------ ------------------------------------------------

  -----------------------------------------------------------------------
  **NOTE:** Hold status information is displayed in the **X4** segment
  within the ANSI X12 350 transaction set. For shipments. Holds for
  people, conveyances, and equipment are in the V9

  -----------------------------------------------------------------------

![](media/image7.png){width="6.995138888888889in"
height="1.3868055555555556in"}

  -----------------------------------------------------------------------
  **NOTE** For a current list of Disposition Codes, *see section 4.4
  Current Valid Disposition Codes.*

  -----------------------------------------------------------------------

### For EDIFACT

This EDIFACT Transaction set contains the format and establishes the
data contents of the Customs Status Information Transaction Set (CUSRES)
for use within the context of an EDI environment. The transaction set
can be used by the CS (CS stands for ??) to supply carriers, terminal
operators, port authorities, and service providers with cargo release
and cargo hold information for import shipments. It can also be used by
the CS to provide exporters or their agents, carriers, and service
providers with information pertaining to export shipments.

A Customs Response Message (CUSRES) permits the transfer of data from a
customs administration:

-   to acknowledge the receipt of the message

-   to indicate whether the information received is correct or if there
    are errors (that is, accepted without errors, accepted with errors,
    rejected, etc.)

-   to inform the sender of the status of the customs declaration (that
    is, goods released, goods for examination, documents required, etc.)

-   to transmit additional information as agreed between parties (that
    is, tax information, quantity information, etc.)

-   to respond to batched messages (i.e. CUSCAR, CUSREP).

The trigger for the CUSRES release will be a conveyance arrival message
(AAH) when the truck crosses the border for immediate release, *see 4.7
Event Codes.*

Example: CUSRES status notification identifying a 'Hold".

The CUSRES transaction set will also identify errors from the original
transaction in the **ERP** (Error Point Detail) segment group. The FTX
segment in this group is used to transmit information in a free-form
format, if necessary, for comment or special instruction. The specific
error code or status codes are identified in the **ERC** (Application
Error Information) segment. Application error codes can be found in the
Implementation Guide for CUSRES status notification.

UNB+UNOA:4+CBP-ACE-TEST:ZZ+LOCK:02+20061109:1424+1781++ACETEST

UNG+CUSRES+CBP-ACE-TEST:ZZ+LOCK:ZZ+20061109:1424+1781+UN+D:03B

UNH+1781+CUSRES:D:03B:UN

BGM+34+LOCK080IITGK015

DTM+132:200609302359:203

DTM+163:200611091424:203

TDT+11++03+:::TR+LOCK+I++:172

TDT+11+++++++:146::16ABB43764376

TDT+11+++++++:274::11223344

LOC+24+0901:77

NAD+CA+1000000006:109

**ERP+1**

**ERC+SN030 = Trip arrived**

**FTX+AAH+++Trip Arrival**

UNT+13+1781

UNE+1+1781

UNZ+1+1781

The information described above indicates:

-   ERP+1 -- the "1" indicates the trip level

-   ERC+SN030 - indicates the trip has arrived. For a complete list of
    the application error codes, refer to the CUSRES status notification
    document located on the following website:
    http://www.cbp.gov/linkhandler/cgov/toolbox/about/modernization/carrier_info/ace_edi_drafts/edi_messages/unedifact_message_standard/status_notification.ctt/status_notification.doc

-   FTX+AAH -- Customs information message

## Event Codes

+--------+-------------------------------------------------------------+
| Code   | Definition                                                  |
+--------+-------------------------------------------------------------+
| AAD    | Actual Arrival of Conveyance at First US Port               |
+--------+-------------------------------------------------------------+
| COC    | Cancel Truck Arrival, **Future Use**                        |
+--------+-------------------------------------------------------------+
| HCR    | Crew/passengers Held                                        |
|        |                                                             |
|        | Used for CBP Truck Release when crew members or passengers  |
|        | are detained at the border.                                 |
+--------+-------------------------------------------------------------+
| HEQ    | Equipment Held                                              |
|        |                                                             |
|        | Used in Truck Release when equipment is detained at the     |
|        | border.                                                     |
+--------+-------------------------------------------------------------+
| HMI    | Hold Conveyance                                             |
|        |                                                             |
|        | Used for CBP truck Release when conveyance is detained at   |
|        | the border.                                                 |
+--------+-------------------------------------------------------------+
| HTR    | Trip Held                                                   |
|        |                                                             |
|        | Used in CBP Truck Release in lieu of HCR, HEQ,HMI and Cargo |
|        | held, when all components are held                          |
+--------+-------------------------------------------------------------+
| OCA    | Overdue Conveyance Arrival                                  |
|        |                                                             |
|        | Used when the truck has not been arrived at the first US    |
|        | Port within two days of consisting.                         |
+--------+-------------------------------------------------------------+
| RCR    | Crew/Passengers Released                                    |
|        |                                                             |
|        | Used for CBP Truck Release when Crew/Passengers are         |
|        | released completely at the border without detention, or     |
|        | when detention is completed.                                |
+--------+-------------------------------------------------------------+
| RCO    | Conveyance Released                                         |
|        |                                                             |
|        | Used for CBP Truck Release when Conveyance is released      |
|        | completely at the border without detention, or when         |
|        | detention is completed.                                     |
+--------+-------------------------------------------------------------+
| REQ    | Equipment Released                                          |
|        |                                                             |
|        | Used for CBP Truck Release when container/equipment is      |
|        | released completely at the border without detention, or     |
|        | when detention is completed.                                |
+--------+-------------------------------------------------------------+
| RTR    | Release Trip                                                |
|        |                                                             |
|        | Used for CBP Truck Release in lieu of RCE, RCO, REQ when    |
|        | the entire Trip is released at the border without           |
|        | detention, or when detention is completed. Future Use.      |
+--------+-------------------------------------------------------------+
| FCA    | Carrier does not possess valid U.S. operating authority     |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers. Pre-arrival of the truck at the first U.S. port:  |
|        |                                                             |
|        | The information contained in the information systems of     |
|        | FMCSA indicates that the carrier does not possess valid     |
|        | operating authority.                                        |
|        |                                                             |
|        | Arrival at the first U.S. port:                             |
|        |                                                             |
|        | If this carrier operates in the United States it will be    |
|        | subject to enforcement action because the carrier does not  |
|        | possess valid operating authority.                          |
+--------+-------------------------------------------------------------+
| FCB    | Carrier has an Out of Service order against it              |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers.                                                   |
|        |                                                             |
|        | Pre-arrival of the truck at the first U.S. port:            |
|        |                                                             |
|        | The information contained in the information systems of     |
|        | FMCSA indicates that this carrier has an out-of-service     |
|        | order against it.                                           |
|        |                                                             |
|        | Arrival at the first U.S. port:                             |
|        |                                                             |
|        | If this carrier operates in the United States it will be    |
|        | subject to enforcement action because the carrier has an    |
|        | out-of-service order against it.                            |
+--------+-------------------------------------------------------------+
| FCC    | Safety score indicates inspection is warranted              |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers.                                                   |
|        |                                                             |
|        | Pre-arrival of the truck at the first U.S. port:            |
|        |                                                             |
|        | Safety score indicates inspection warranted.                |
+--------+-------------------------------------------------------------+
| FCI    | Carrier's current insurance does not meet the minimum level |
|        | or better                                                   |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers. Pre-arrival of the truck at the first U.S. port:  |
|        |                                                             |
|        | The information contained in the information systems of     |
|        | FMCSA indicates that this carrier's current insurance level |
|        | does not meet the minimum requirements.                     |
|        |                                                             |
|        | Arrival at the first U.S. port:                             |
|        |                                                             |
|        | If this carrier operates in the United States it will be    |
|        | subject to enforcement action because the carrier's current |
|        | insurance level does not meet the minimum requirements.     |
+--------+-------------------------------------------------------------+
| FDL    | Driver does not have valid/current CDL or equivalent (MX or |
|        | CA)                                                         |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers.                                                   |
|        |                                                             |
|        | Pre-arrival of the truck at the first U.S. port:            |
|        |                                                             |
|        | The information contained in the information systems of     |
|        | FMCSA, Mexico, or Canada indicates that this driver does    |
|        | not have a valid/current CDL or equivalent (Mexico/Canada). |
|        |                                                             |
|        | Arrival at the first U.S. port:                             |
|        |                                                             |
|        | If this carrier operates in the United States the driver    |
|        | and the carrier will be subject to enforcement action       |
|        | because the driver does not have a valid/current CDL or     |
|        | equivalent (Mexico/Canada)                                  |
+--------+-------------------------------------------------------------+
| FDH    | Driver does not have proper CDL endorsements for HAZMAT     |
|        | cargo                                                       |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers.                                                   |
|        |                                                             |
|        | Pre-arrival of the truck at the first U.S. port:            |
|        |                                                             |
|        | The information contained in the information systems of     |
|        | FMCSA, or Mexico indicates that this driver does not have a |
|        | valid CDL with the proper HM endorsement or equivalent      |
|        | Mexican CDL with proper HM class of license. Canadian       |
|        | drivers must present HM training certificate on demand.     |
|        |                                                             |
|        | If this carrier operates in the United States the driver    |
|        | and the carrier will be subject to enforcement action       |
|        | because the driver does not have a CDL with the proper HM   |
|        | class of license. Canadian drivers must present HM training |
|        | Certificate on demand.                                      |
+--------+-------------------------------------------------------------+
| FVC    | No current CVSA decal on file. Please check visually        |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers prior to arrival of the truck a t the first U.S.   |
|        | port.                                                       |
|        |                                                             |
|        | Pre-arrival of the truck at the first U.S. port:            |
|        |                                                             |
|        | No current safety inspection decal on file for one or more  |
|        | commercial motor vehicles (Mexican long-haul carriers       |
|        | only).                                                      |
|        |                                                             |
|        | If this carrier operates in the United States beyond        |
|        | commercial zones with these vehicles it will be subject to  |
|        | enforcement action because one or more of the vehicles do   |
|        | not have current safety inspection decal.                   |
+--------+-------------------------------------------------------------+
| FCD    | Carrier check not performed, data not available at this     |
|        | time                                                        |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers prior to arrival of the truck at the first U.S.    |
|        | port.                                                       |
|        |                                                             |
|        | Carrier check not performed, data not available at this     |
|        | time                                                        |
+--------+-------------------------------------------------------------+
| FDD    | Driver check not performed, data not available at this time |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers prior to arrival of the truck at the first U.S.    |
|        | port.                                                       |
|        |                                                             |
|        | Driver check not performed, data not available at this time |
+--------+-------------------------------------------------------------+
| FVD    | Tractor check not performed, data not available at this     |
|        | time                                                        |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers prior to arrival of the truck at the first U.S.    |
|        | port.                                                       |
|        |                                                             |
|        | Trailer check not performed, data not available at this     |
|        | time.                                                       |
+--------+-------------------------------------------------------------+
| FED    | Trailer check not performed, data not available at this     |
|        | time                                                        |
|        |                                                             |
|        | Used for CBP Truck Release for FMCSA notifications to the   |
|        | carriers prior to arrival of the truck at the first U.S.    |
|        | port.                                                       |
|        |                                                             |
|        | Trailer check not performed, data not available at this     |
|        | time.                                                       |
+--------+-------------------------------------------------------------+
| FCS    | Carrier data not found in FMCSA systems                     |
|        |                                                             |
|        | Used for Truck Release for FMCSA notifications to the       |
|        | carriers prior to arrival of the truck at the first U.S.    |
|        | port.                                                       |
|        |                                                             |
|        | The information contained in the information systems of     |
|        | FMCSA indicates that this carrier is not registered with    |
|        | FMCSA.                                                      |
|        |                                                             |
|        | If this carrier operates in the United States it will be    |
|        | subject to enforcement action because the carrier is not    |
|        | registered with the FMCSA                                   |
+--------+-------------------------------------------------------------+

## Current Valid Disposition Codes 

  --------- --------------------- ------------------------------------------------
  CODE      DEFINITION            EXPLANATION

  1A        Entered: Intensive    Generated as a result of selectivity processing
            examination required  or Customs manual posting

  1B        Released: Intensive   Generated as a result of selectivity processing
            examination completed or Customs manual posting at the conclusion of
                                  an intensive examination

  1C        Entered and released: Generated as a result of selectivity processing
            general examination   or Customs manual posting: no further action
                                  required

  1F        Customs hold removed  Generated as a result of a Customs hold removal
            at port of in-bond    posting affecting the port of in-bond
            destination           destination: the bill returns to previous status
                                  from "HELD"

  1G        Customs hold placed   Generated as a result of a manually posted hold
            at port of in-bond    effective in the port of in-bond destination:
            destination           release is denied: the bill status changes to
                                  "HELD"

  1H        Customs hold placed   Generated as a result of a manually posted
            at port of discharge  Customs hold effective in the port of discharge
                                  (conveyance arrival): release is denied: bill
                                  status changes to "HELD"

  1I        Customs hold removed  Generated as a result of a manually posted
            at port of discharge  removal of a Customs hold effective in the port
                                  of discharge (conveyance arrival): bill status
                                  returns to previous status

  1J        In-bond Movement      Generated in response to IT, TE, and IE bill
            Authorized: bill of   data input by AMS (ACE) participants or Customs
            Lading open           

  1K        Bill of lading late   Advisory generated for IT, TE, and IE in-bond
            in 5 days             bills created by AMS (ACE) participants that
                                  have not been arrived at destination 5 days
                                  before expiration of the transit period

  1L        Bill of lading late   Advisory generated for IT, TE, and IE in-bonds
                                  bills created by AMS (ACE) participants that
                                  have not been arrived at destination by the
                                  expiration of the transit period

  1N        Overage               Advisory generated to the master or house bill
                                  transmitter when the quantity in the entry or
                                  associated entries filed is greater than the
                                  manifested quantity in the master or house bill.
                                  The status code should be generated once.

  1O        Shortage              Advisory generated to the master or house bill
                                  transmitter when the quantity in the entry filed
                                  is less than the manifested quantity in the
                                  master or house bill. The status code should be
                                  generated once.

  1R        Pending eligible      Advisory generated 2 days before the expiration
            general order         of lay order: indicates the released quantities
                                  on the bill are less than the original
                                  manifested or amended quantities

  1S        Ordered to general    Advisory generated at the expiration of the lay
            order                 order: indicates discrepancy in released
                                  quantities and the original manifested or
                                  amended quantities has not been resolved by the
                                  end of the lay order

  1T        Seized                Generated as a result of manual posting by
                                  Customs indicating that the manifest or partial
                                  quantity of the bill has been seized for
                                  violations: the seized quantity amount is
                                  written in the released quantity field

  1U        Sent to general order Generated as a result of manual posting by
                                  Customs indicating that the manifested or
                                  partial quantity of the bill has been removed to
                                  a general order facility: the quantity sent to
                                  GO is written in the REL quantity field

  2F        USDA Miscellaneous    Generated as a result of a USDA miscellaneous
            hold removed at port  hold removal posting affecting the port of
            of in-bond            in-bond destination: the bill returns to the
            destination           previous status from "HELD"

  2G        USDA miscellaneous    Generated as a result of a manually posted USDA
            hold placed at port   miscellaneous effective in the port of in-bond
            of in-bond            destination hold release is denied: bill status
            destination:          changes to "HELD"

  2H        USDA miscellaneous    Generated as a result of a manually posted USDA
            hold placed at port   miscellaneous hold effective in the port of
            of discharge          discharge (conveyance arrival): release is
                                  denied: bill status changes to "HELD"

  2I        USDA miscellaneous    Generated as a result of a manually posted
            hold removed at port  removal of a USDA miscellaneous hold effective
            of discharge          in the port of discharge (conveyance arrival):
                                  bill status changes to "HELD"

  3F        Other government      Generated as a result of a manually posted
            agency hold removed   removal of an other government agency hold
            at port of in-bond    effective in the port of in-bond destination:
            destination           bill status changes to previous status

  3G        Other government      Generated as a result of a manually posted other
            agency hold placed at government agency hold effective in the port of
            port of in-bond       in-bond destination: release is denied: bill
            destination           status changes to "HELD" status

  3H        Other government      Generated as a result of a manually posted other
            agency hold placed at government agency hold effective in the port of
            port of discharge     discharge (conveyance arrival): release is
                                  denied: bill status changes to "HELD" status

  3I        Other government      Generated as a result of a manually posted
            agency hold removed   removal of an other government agency hold
            at port of discharge  effective in the port of discharge (conveyance
                                  arrival): bill status changes to previous status

  11        Arrival of in-bond -  Advisory generated when an in-bond movement has
            complete movement     been arrived at destination as a complete
                                  movement (in-bond number) by the AMS (ACE)
                                  participant or by Customs

  12        Arrival of in-bond -  Advisory generated when an in-bond movement has
            bill of lading        been arrived at destination by the bill of
                                  lading by the AMS (ACE) participant or by
                                  Customs

  13        Arrival of in-bond -  Advisory generated when an in-bond movement has
            container             been arrived at the destination port by the
                                  container/equipment number by the AMS (ACE)
                                  participant or by Customs

  50        Export of in-bond -   Advisory generated when an in-bond movement has
            complete movement     been exported at the destination port as a
                                  complete movement (in-bond number) by the AMS
                                  (ACE) participant or by Customs

  51        Export of in-bond -   Advisory generated when an in-bond movement has
            bill of lading        been exported at the destination port as a
                                  complete movement (in-bond number) by the AMS
                                  (ACE) participant or by Customs

  52        Export of in-bond -   Advisory generated when an in-bond movement has
            container             been exported at the destination port by the
                                  container/equipment number by the AMS
                                  (ACE)participant or by Customs

  53        Overdue export        Advisory generated to AMS (ACE) participant when
                                  paperless or conventional TE or IE in-bond
                                  movement is not exported from the destination
                                  port within 30 days after the in-bond

  57        Change arrival of     Advisory generated when a paperless or
            in-bond -- complete   conventional in-bond is arrived in the system at
            movement              destination as a complete movement by the AMS
                                  (ACE) participant or by Customs subsequent to
                                  the original arrival at destination

  58        Change arrival of     Advisory generated when a paperless or
            in-bond -- bill of    conventional in-bond is arrived in the system at
            lading                destination by the bill of lading by the AMS
                                  (ACE)participant or by Customs subsequent to the
                                  original arrival at destination

  59        Change arrival of     Advisory generated when a paperless or
            in-bond -- container  conventional in-bond is arrived in the system at
                                  destination by the container/equipment number by
                                  the AMS (ACE)participant or by Customs
                                  subsequent to the original arrival at
                                  destination

  60        Change export of      Advisory generated when a paperless or
            in-bond -- complete   conventional in-bond is exported from the
            movement              destination port as a complete movement (in-bond
                                  number) by the AMS (ACE) participant or by
                                  Customs, subsequent to the original export: new
                                  export date written to all bills associated with
                                  the in-bond number

  61        Change export of      Advisory generated when a paperless or
            in-bond -- bill of    conventional in-bond is exported from the
            lading                destination port by a bill of lading number by
                                  the AMS (ACE) participant or by Customs,
                                  subsequent to the original export: new export
                                  date written to the bill. Does not affect other
                                  bills associated with the in-bond number.

  62        Change export of      Advisory generated when a paperless or
            in-bond -- container  conventional in-bond is exported from the
                                  destination port by a container/equipment number
                                  by the AMS (ACE) participant or by Customs,
                                  subsequent to the original export: new export
                                  date written to all the bills and in-bonds
                                  associated with the container/equipment.

  63        Delete arrival of     Advisory generated through Customs action: by
            in-bond by complete   complete movement
            movement              

  64        Delete arrival of     Advisory generated through Customs action by
            in-bond -- bill of    bill of lading number
            lading                

  65        Delete arrival of     Advisory generated through Customs action by
            in-bond -- container  container/equipment number

  66        Delete export of      Advisory generated through Customs action by
            in-bond -- complete   complete movement (in-bond number)

  67        Delete export of      Advisory generated through Customs action by
            in-bond -- bill of    bill of lading number.
            lading                

  68        Delete export of      Advisory generated through Customs action by
            in-bond -- container  container/equipment number.

  71        Intensive hold for    Generated as a result of a manually placed USDA
            USDA placed at port   intensive hold effective in the port of
            of discharge          discharge (conveyance arrival): release is
                                  denied: bill status changes to "HELD" .

  72        Inspection/document   Generated as a result of a manually placed USDA
            review for USDA       inspection/document review hold effective in the
            placed at the port of port of discharge (conveyance arrival): release
            discharge             is denied: bill status changes to "HELD"

  73        Fumigation hold for   Generated as a result of a manually placed USDA
            USDA placed at the    fumigation hold effective in the port of
            port of discharge     discharge (conveyance arrival): release is
                                  denied: bill status changes to "HELD"

  74        Intensive hold for    Generated as a result of a manually posted
            USDA removed at port  removal of USDA intensive hold effective in the
            of discharge          port of discharge (conveyance arrival): bill
                                  status returns to previous status.

  75        Inspection/document   Generated as a result of a manually placed USDA
            review for USDA       inspection/document review hold effective in the
            removed at the port   port of discharge (conveyance arrival): bill
            of discharge          status changes to previous status .

  76        Fumigation hold for   Generated as a result of a manually posted
            USDA removed at the   removal of a USDA fumigation hold effective in
            port of discharge     the port of discharge (conveyance arrival): bill
                                  status returns to previous status .

  77        Intensive hold for    Generated as a result of a manually placed USDA
            USDA placed at port   intensive hold effective in the port of in-bond
            of in-bond            destination: release is denied: bill status
            destination           changes to "HELD" .

  78        Inspection/document   Generated as a result of a manually placed USDA
            review for USDA       inspection/document review hold effective in the
            placed at the port of port of in-bond destination: release is denied:
            in-bond destination   bill status changes to "HELD" .

  79        Fumigation hold for   Generated as a result of a manually placed USDA
            USDA placed at the    fumigation hold effective in the port of in-bond
            port of in-bond       destination: release is denied: bill status
            destination           changes to "HELD" .

  80        Intensive hold for    Generated as a result of a manually posted
            USDA removed at port  removal of USDA intensive hold effective in the
            of in-bond            port of in-bond destination: bill status returns
            destination           to previous status.

  81        Inspection/document   Generated as a result of a manually placed USDA
            review for USDA       inspection/document review hold effective in the
            removed at the port   port of in-bond destination: bill status changes
            of in-bond            to "HELD" .
            destination           

  82        Fumigation hold for   Generated as a result of a manually posted
            USDA removed at the   removal of a USDA fumigation hold effective in
            port of in-bond       the port of in-bond destination: bill status
            Destination           returns to previous status .

  A1        PN on file            Advisory Generated as a result of FDA/BTA
                                  processing: this notification Is sent when the
                                  PN data is initially on file for a shipment,
                                  in-bond, or informal. For prefiled PAPS or BCS
                                  entries the notification will be based on the
                                  FDA status of the associated entry

  A4        Entry not on file     Advisory Generated as a result of FDA/BTA
                                  processing: this notification Is sent on the
                                  actual or estimated date of arrival, whichever
                                  comes first to indicate the entry data is not
                                  yet on file for a PAPS or BCS shipment

  A5        PN not on file        Advisory Generated as a result of FDA/BTA
                                  processing: this notification Is sent on the
                                  actual or estimated date of arrival, whichever
                                  comes first, to indicate that the PN data is not
                                  yet on file for a shipment, in-bond or informal
                                  which has FDA freight indicator = 'Y'

  02        Entry on file         Advisory generated to a participant when an
                                  entry has been filed in the port of discharge
                                  (conveyance arrival) against a bill on a
                                  conveyance that is still enroute: not a release.
  --------- --------------------- ------------------------------------------------

[]{.mark}