353 Customs Events Advisory Details

Functional Group ID=SO

Introduction:

This X12 Transaction Set contains the format and establishes the data contents of the Customs Events Advisory Details Transaction Set (353) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by carriers to notify Customs of events concerning cargo moving in-bond, or of conveyance arrivals or departures. These events include the arrival of containers, or cargo covered by individual ocean bills of lading or in-bond numbers, which have moved in-bond to an inland destination or which have been exported. Carriers can also use this transaction set to notify Customs of the arrival or departure of a conveyance for which an electronic manifest has been filed and for the transfer of custodial liability when an in-bond movement involves multiple legs.

This Implementation Guideline uses the ASC 6050 Standards Version/release as its base

Notes:

SPECIAL MESSAGING CONSTRAINTS:
- Limit one Interchange (ISA-IEA) per message transmission is required
- Limit one message Group (GS-GE) per message transmission is required.
- Limit one transaction set (ST-SE) of the same Transaction Set (TS) Identifier Code (i.e., 353) are allowed per message transmission.
- Element delimiters used in this transaction must be ' * ' (asterisk). No blanks between delimiters if element is null.
- Segment delimiters used in this transaction must be one byte with a value of hex '15'.
- A segment delimiter must be the last byte of data in the message transmission data stream.
- Transmit ONLY displayable characters found on a standard American English keyboard.  Low-values, carriage return characters, or other non-standard characters must NOT be transmitted.
- 'Not Used' in the left column indicates that a data element will not be used by CBP. 
- 'Dep' in the left column indicates that CBP usage of a particular segment or element is Dependent (Conditional) within the CBP application.  
- Per the ASC X12 Standard, an 'M' indicates a Mandatory use, 'O' indicates Optional Use and an 'X' indicates a Conditional use.  
- CBP requirements may override ASC X12 Standard Mandatory or Conditional usages.
 - Maximum allowable message transmission size is 12 megabytes (12,582,912 bytes) of data.

(Last Update:  December 2014 ACE v 1.2  Ocean Export	

	Pos.	Seg.		Req.		Loop	
	No.	ID	Name	Des.	Max.Use	Repeat		
M	0050	ISA	Interchange Control Header	M	1									
M	0075	GS	Functional Group Header	M	1									
M	0100	ST	Transaction Set Header	M	1									
M	0200	M10	Manifest Identifying Information	M	1									
M	0300	P4	Port Information	M	1									
Not Used	0350	CM	Cargo Manifest	O	1									
			LOOP ID - M15			9999								
M	0400	M15	Customs Events Advisory Details	M	1									
	0410	M7A	Seal Number Replacement	O	22									
Not Used	0420	V1	Vessel Identification	O	1									
Not Used	0440	V2	Vessel Information	O	1									
Not Used	0445	MEA	Measurements	O	1									
Not Used	0450	K1	Remarks	O	4									
														
M	0500	SE	Transaction Set Trailer	M	1									
M	0550	GE	Functional Group Trailer	M	1									
M	0600	IEA	Interchange Control Trailer	M	1									

	Segment:	ISA Interchange Control Header
	Position:	0050
	Loop:
	Level:	
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To start and identify an interchange of zero or more functional groups and interchange-related control segments
	Syntax Notes:
	Semantic Notes:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
M	ISA01	I01	Authorization Information Qualifier	M	1 	ID 2/2	
	Code identifying the type of information in the Authorization Information	
	Always '00'	
 	00		No Authorization Information Present (No Meaningful Information in I02)	
M	ISA02	I02	Authorization Information	M	1 	AN 10/10	
	Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)	
	Always 10 spaces.	
M	ISA03	I03	Security Information Qualifier	M	1 	ID 2/2	
	Code identifying the type of information in the Security Information	
	Always '00'	
 	00		No Security Information Present (No Meaningful Information in I04)	
M	ISA04	I04	Security Information	M	1 	AN 10/10	
	This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)	
	Always 10 spaces.	
M	ISA05	I05	Interchange ID Qualifier	M	1 	ID 2/2	
	Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified	
	Always 'ZZ'	
 	ZZ		Mutually Defined	
M	ISA06	I06	Interchange Sender ID	M	1 	AN 15/15	
	Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element	
	Sender Identifier.  Up to 4 alpha/numeric characters.  Value must contain the Standard Carrier Alpha Code (SCAC) or the identify of the Service Center. May be identical to that of GS02.	
M	ISA07	I05	Interchange ID Qualifier	M	1 	ID 2/2	
	Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified	
	Always 'ZZ'	
 	ZZ		Defined	
M	ISA08	I07	Interchange Receiver ID	M	1 	AN 15/15	
	Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them	
 	CUSTOMSTST		Testing	
 	CUSTOMS		Production	
M	ISA09	I08	Interchange Date	M	1 	DT 6/6	
	Date of the interchange	
	Date as YYMMDD where:	
 	YY		 Year	
 	MM		 Month of Year	
 	DD		 Day of Month	
M	ISA10	I09	Interchange Time	M	1 	TM 4/4	
	Time of the interchange	
	Time as HHMM where:	
 	HH		Hour	
 	MM		Minute	
M	ISA11	I65	Repetition Separator	M	1 	AN 1/1	
	Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator	
M	ISA12	I11	Interchange Control Version Number Code	M	1 	ID 5/5	
	Code specifying the version number of the interchange control segments	
	Always '00605'	
 	00605		Standards Approved for Publication by ASC X12 Procedures Review Board through October 2012	
M	ISA13	I12	Interchange Control Number	M	1 	N0 9/9	
	A control number assigned by the interchange sender	
M	ISA14	I13	Acknowledgment Requested Code	M	1 	ID 1/1	
	Code indicating sender's request for an interchange acknowledgment	
	Always '0'	
 	0		No Interchange Acknowledgment Requested	
M	ISA15	I14	Interchange Usage Indicator Code	M	1 	ID 1/1	
	Code indicating whether data enclosed by this interchange envelope is test, production or information	
	Preferred 'P'	
 	P		Production Data	
 	T		Test Data	
M	ISA16	I15	Component Element Separator	M	1 	AN 1/1	
	Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator	
	Preferred ' : ' (colon)	

	Segment:	GS Functional Group Header
	Position:	0075
	Loop:
	Level:	
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the beginning of a functional group and to provide control information
	Syntax Notes:
	Semantic Notes:	1	GS04 is the group date.
		2	GS05 is the group time.
		3	The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
M	GS01	479	Functional Identifier Code	M	1 	ID 2/2	
	Code identifying a group of application related transaction sets	
	Always 'SO'	
 	SO		Ocean Shipment Information	
M	GS02	142	Application Sender's Code	M	1 	AN 2/15	
	Code identifying party sending transmission; codes agreed to by trading partners	
	Sender identifier. Up to 4 alpha/numeric characters.  Value must contain the Standard Carrier Alpha Code or the identity of the Service Center if applicable.  May be identical to the ISA06.	
M	GS03	124	Application Receiver's Code	M	1 	AN 2/15	
	Code identifying party receiving transmission; codes agreed to by trading partners	
	Date as CCYYMMDD where:	
 	CUSTOMSTST		Testing	
 	CUSTOMS		Production	
M	GS04	373	Date	M	1 	DT 8/8	
	Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year	
	Date as CCYYMMDD where:	

M	

GS05	

337	CC  - Century
YY  - Year
MM – Month of Year
DD  - Day of Month
Time	

M	

1 	

TM 4/8	
	Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)	
	Use Eastern Standard/Daylight Time.
Time as HHMM where:	

M	

GS06	

28	HH  - Hour
MM - Minute
Group Control Number	

M	

1 	

N0 1/9	
	Assigned number originated and maintained by the sender	
M	GS07	455	Responsible Agency Code	M	1 	ID 1/2	
	Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480	
	Always 'X'	
 	X		Accredited Standards Committee X12	

M	
GS08	
480	
Version / Release / Industry Identifier Code	
M	
1 	
AN 1/12	
	Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed	
	Always '006050'	
 	006050		Standards Approved for Publication by ASC X12 Procedures Review Board through October 2013	

	Segment:	ST Transaction Set Header
	Position:	0100
	Loop:
	Level:	
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the start of a transaction set and to assign a control number
	Syntax Notes:
	Semantic Notes:	1	The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
		2	The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition.  When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
M	ST01	143	Transaction Set Identifier Code	M	1 	ID 3/3	
	Code identifying a Transaction Set	
	Always '353'	
 	353		Customs Events Advisory Details	
M	ST02	329	Transaction Set Control Number	M	1 	AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set	
Not Used	ST03	1705	Implementation Convention Reference	O	1 	AN 1/35	

	Segment:	M10 Manifest Identifying Information
	Position:	0200
	Loop:
	Level:	
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To transmit manifest identifying information
	Syntax Notes:	1	If either M1004 or M1010 is present, then the other is required.
		2	If either M1015 or M1016 is present, then the other is required.
	Semantic Notes:	1	M1004 is the International Maritime Organization (IMO) Vessel Code maintained in Lloyd's Register of Shipping.
		2	M1007 is used for the six-digit Numeric Manifest Sequence Number.
		3	M1011 indicates if the transmission involves an in-bond participant. A "Y" indicates it does; an "N" indicates it does not.
		4	M1012 is a unique identification number for the manifest assigned by the originator of the manifest with a maximum length of 15.
		5	M1017 is the type of initial manifest being amended by this transmission.
               Notes:    Once the original manifest (M1009 code ‘W’) has been submitted and accepted, the M10
                         Segment becomes ‘frozen’.  In any subsequent amendments or actions (sets 309 M1009                           Code ‘Y’, 353) the mandatory and required elements in the M10 segment from the	       
         Original manifest must be submitted.  This means if a vessel name were submitted
         In the original manifest, it is required in any subsequent amendments or actions.  If both
         The vessel name and IMO Lloyds vessel code (M1004/M1010) were submitted in the  
         Original manifest they are required in any subsequent amendments and actions.     

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
	M1001	140	Standard Carrier Alpha Code	O	1 	ID 2/4	
	Code identifying the Standard Carrier Alpha Code	
	A code representing the automated Carrier reporting  the TS353	
	M1002	91	Transportation Method/Type Code	O	1 	ID 1/2	
	Code specifying the method or type of transportation for the shipment	
	Always 'O'	
 	O		Containerized Ocean	
	M1003	26	Country Code	O	1 	ID 2/3	
	Code identifying the country	
	ISO 2 alpha Country Code.  Refer to CAMIR Appendix G for valid codes
	
Not Used	M1004	597	Vessel Code	X	1 	ID 1/8	

M	

M1005	

182	Code identifying vessel
International Maritime Organization (IMO) Code issued by Lloyds.  Either M1004 or M1005 is required.  Required if M1010 is submitted.

This field is required for Conveyance Arrival, conveyance export and Update Vessel Date of Arrival; not validated for all other message codes.  Only provide if this data element was previously reported in the TS309.

CBP will accept only 7 numeric characters in this element  
Vessel Name	

O	

1 	

AN 2/28	
	Name of ship as documented in "Lloyd's Register of Ships"	
	Either M1004 or M1005 is required.  If both are provided, data is validated and both must match entries in the vessel code table.

This field is required for conveyance arrival,  Conveyance Export; not validated for all other message codes.

- CBP accepts up to 23 alpha/numeric characters in this element.	
	M1006	55	Flight/Voyage Number	O	1 	AN 2/30	
	Identifying designator for the particular flight or voyage on which the cargo travels	
	This field is required for conveyance arrival,  Conveyance Export; not validated for all other message codes.

- CBP accepts 5 alpha/numeric characters in this element.	
	M1007	127	Reference Identification	O	1 	AN 1/80	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Unique carrier number which will be returned from CBP in the response.  IF
Not provided CBP will return '000001' in the response message.

Important to note: When this data element is provided to all subsequent 
Transmissions relative to this manifest (i.e., TS309, TS359, TS353) must
Must include this exact sequence number.

- CBP accepts up to 6 numeric characters  in this element.	
Not Used	M1008	380	Quantity	O	1 	R 1/15	
	M1009	256	Manifest Type Code	O	1 	ID 1/1	
	Code identifying the type of manifest transmitted	
	Always 'H'.	
 	H		Arrival Notification from Carrier to CBP	
	M1010	897	Vessel Code Qualifier	X	1 	ID 1/1	

Not Used	

M1011	

1073	Code specifying the vessel code source
Required is M1004 is used
  L                  IMO code issued by Lloyds        
Yes/No Condition or Response Code	

O	

1 	

ID 1/1	
	M1012	127	Reference Identification	O	1 	AN 1/80	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Carrier assigned reference number that will be returned in the response
Message

- CBP accepts up to 30 alpha/numeric characters in this element.	
Not Used	M1013	353	Transaction Set Purpose Code	O	1 	ID 2/2	
Not Used	M1014	346	Application Type Code	O	1 	ID 2/2	

Not Used	

M1015	

580	Code identifying an operation
Values accepted by CBP:
   22                  Ocean Export Manifest
Amendment Type Code	

X	

1 	

ID 1/1	
Not Used	M1016	393	Amendment Code	X	1 	ID 2/2	
Not Used	M1017	256	Manifest Type Code	O	1 	ID 1/1	

	Segment:	P4 Port Information
	Position:	0300
	Loop:
	Level:	
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To transmit identifying information for a port
	Syntax Notes:
	Semantic Notes:	1	P401 is used for customs district and port code (census schedule D).
		2	P402 is the estimated date of arrival.
		3	P403 is used for number of bills of lading.
		4	P404 is the Facilities Information and Resources Management System (FIRMS) Code.
		5	P405 is the estimated time of arrival for P402.
		6	P406 is the date conveyance departed prior port.
		7	P407 is the time conveyance departed prior port.
Notes:		Port of export information. CBP only accepts one P4 segment per transaction for OCEAN applications.	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
M	P401	310	Location Identifier	M	1 	AN 1/30	
	Code which identifies a specific location	
	Each U.S Export port of load.  
Refer to Census Schedule D in the CAMIR Appendix E for valid codes.	
M	P402	373	Date	M	1 	DT 8/8	
	Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year	
	Estimated Date of departure from last U.S. Port indicated in P401
Date as CCYYMMDD where:	

Not Used	

P403	

380	CC  - Century
YY  - Year
MM – Month of Year
DD  - Day of Month  
Quantity	

O	

1 	

R 1/15	
Not Used	P404	310	Location Identifier	O	1 	AN 1/30	
Not Used	P405	337	Time	O	1 	TM 4/8	
Not Used	P406	373	Date	O	1 	DT 8/8	
Not Used	P407	337	Time	O	1 	TM 4/8	

	Segment:	M15 Customs Events Advisory Details
	Position:	0400
	Loop:	M15        Mandatory
	Level:	
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To notify Customs of in-bond cargo movement or of a conveyance arrival or departure, or of transfer of custodial liability when an in-bond movement involves multiple legs
	Syntax Notes:	1	At least one of M1504 or M1510 is required.
		2	If M1511 is present, then M1510 is required.
		3	If either M1513 or M1514 is present, then the other is required.
		4	If M1515 is present, then M1516 is required.
		5	If either M1518 or M1519 is present, then the other is required.
	Semantic Notes:	1	M1503 is the start date of the event.
		2	M1504 is the Schedule D code for place of cargo movement, transfer of liability or conveyance arrival or departure.
		3	M1505 is the unique bill of lading issuer code, required when M1501 is "2", "6", or "B".
		4	M1506 is the start time of the event.
		5	M1508 is the Internal Revenue Service identification number of the next in-bond carrier.
		6	M1509 is the Standard Carrier Alpha Code (SCAC) of the next in-bond carrier.
		7	M1510 is the city in which a transfer of custodial liability occurs.
		8	M1511 is the state or province code for the city named in M1510.
		9	If M1512 is "Y", then M1504 is an intermediate port.  If "N", then M1504 is the port of final destination.
		10	M1515 is the name of the exporting vessel.
		11	M1517 is the last foreign port prior to sailing for the United States.
		12	M1518 is the end date of the event.
		13	M1519 is the end time of the event.
Notes:		1.  Only one Conveyance Arrival notification may be reported per TS353 message sent to CBP.	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
M	M1501	1497	Notification Entity Qualifier	M	1 	AN 1/2	
	Code indicating type of notifications	
	Values accepted by CBP	
 	1
2                       
3                    
                  	   	Arrive inbond by inbond number
Arrive inbond by bill of lading number at destination port
Arrive inbond by container/equipment at destination port	
 	5		Export inbond by inbond number	

M	

M1502	

27	  6                  Export inbond by bill of lading
  7                  Export inbond by container/equipment 
  8                  Departure of conveyance for foreign 
                      Note: code 8 applies for conveyance   
                      Departure in set 353 version 
                      6050.  If set 353 set version 4010 is 
                      used code 9 for foreign departure 
                      applies.          
  F                  Cancel inbond arrival by inbond 
                      Number
  G                  Cancel inbond arrival by bill of lading 
  H                  Cancel inbond arrival by 
                      Container/equipment  
  I                   Cancel inbond export by inbond 
                      number    
  J                   Cancel inbond export by bill of 
                      lading 
  K                  Cancel inbond export by 
                      Container/equipment    
Reference Identification	

M	

1 	

AN 1/80	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	If M1501=1, 5, F, I,  the M1502 will be the In-bond Number.

If M1501=2, 6, G, J  the M1502 will be the Bill Issuer Sequence Number of the Bill of Lading.  The Bill Issuer SCAC is reported in the M1505.
If M1501=3, 7, H, K, the M1502 will be the Equipment Initial and Equipment Number (cannot arrive non-containerized (NC) cargo). 

If M1501 = 4 then the conveyance is arrived: at the last U.S. port prior to departure from the U.S.

If M1501 = 8 then M1014 in the original export 309 data was '22' .  The conveyance that has arrived at the port of export has departed the country.
 
- CBP will accept up to 14 alpha/numeric characters in this element.	
M	M1503	373	Date	M	1 	DT 8/8	
	Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year	
	Date as CCYYMMDD where:	

M1504	

310	
CC  - Century
YY  - Year
MM – Month of Year
DD  - Day of Month
Location Identifier	

X	

1 	

AN 1/30	
	Code which identifies a specific location	
	This element is required when M1501= 8. For all other M1501 message codes only ANSI X.12 syntax validations will be performed on M1504.  
When M1501=8, this element represents the last U.S. Port of exportation and may or may not equal the value in the P401,.

Refer to Schedule D in CAMIR Appendix E for valid codes.	
Not Used	M1505	140	Standard Carrier Alpha Code	O	1 	ID 2/4	
M	M1506	337	Time	M	1 	TM 4/8	
	Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)	
	Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99).

Required by CBP when time of Conveyance Arrival (M1501=4, Conveyance Export (M1501=8).

Use Eastern Standard/Daylight Time.
Time as HHMM where:	
Not Used	M1507	225	Seal Number	O	1 	AN 2/15	
Not Used	M1508	127	Reference Identification	O	1 	AN 1/80	
Not Used	M1509	140	Standard Carrier Alpha Code	O	1 	ID 2/4	
Not Used	M1510	19	City Name	X	1 	AN 2/30	
Not Used	M1511	156	State or Province Code	O	1 	ID 2/2	
Not Used	M1512	1073	Yes/No Condition or Response Code	O	1 	ID 1/1	
Not Used	M1513	128	Reference Identification Qualifier	X	1 	ID 2/3	

Not Used	

M1514	

127	

Reference Identification	

X	

1 	

AN 1/80	
Not Used	M1515	182	Vessel Name	O	1 	AN 2/28	
Not Used	M1516	91	Transportation Method/Type Code	X	1 	ID 1/2	
	M1517	310	Location Identifier	O	1 	AN 1/30	
	Code which identifies a specific location	
	For M1501 message code of  '8', report Facilities Information and Resource Management Systems (FIRMS) Code when available.  The FIRMS location must be on file and match the Port of Departure given in M1504.	
Not Used	M1518	373	Date	X	1 	DT 8/8	
Not Used	M1519	337	Time	X	1 	TM 4/8	

	Segment:	M7A Seal Number Replacement
	Position:	0410
	Loop:	M15        Mandatory
	Level:	
	Usage:	Optional
	Max Use:	22
	Purpose:	To provide an audit trail of seal number changes
	Syntax Notes:	1	If either M7A04 or M7A05 is present, then the other is required.
	Semantic Notes:	1	M7A01 is the original seal number.
		2	M7A02 is the replacement seal number.
		3	M7A03 is the date the new seal was installed.
		4	M7A04 and M7A05 indicate the party responsible for the seal replacement.
		5	M7A06 is a description of why the seal was replaced.
		6	M7A07 is the location of the replaced seal on the equipment.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
M	M7A01	225	Seal Number	M	1 	AN 2/15	
	Unique number on seal used to close a shipment	
	A valid exporter/carrier seal number associated with this shipment.
If it is a seal number it must be provided.  It cannot include special
Characters ('.', '-', '/', etc).

This is the seal that is being replaced.	
M	M7A02	225	Seal Number	M	1 	AN 2/15	
	Unique number on seal used to close a shipment	
	A valid exporter/carrier seal number associated with this shipment.
If it is a seal number it must be provided.  It cannot include special
Characters ('.', '-', '/', etc).

This is the seal replacing the seal listed in M7A01.	
	M7A03	373	Date	O	1 	DT 8/8	
	Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year	
	The date the change of seal occurred
Date as CCYYMMDD where:	
Not Used	M7A04	98	Entity Identifier Code	X	1 	ID 2/3	
	M7A05	93	Name	X	1 	AN 1/60	
	Free-form name	
	M7A06	352	Description	O	1 	AN 1/80	
	A free-form description to clarify the related data elements and their content	
	Reason for the change of seal.	
	M7A07	302	Location on Equipment Code	O	1 	ID 1/3	
	Code indicating a location on a piece of equipment, as observed from the rear-end.  The rear-end of the equipment is based on the equipment type (i.e. container door, chassis wheels, brakes.)	
	Codes accepted by CBP:	
 	C		Complete Equipment, Right and Left	
 	F		Front	
 	I		Interior	
 	LF		Left Front	
 	LIC		Left Inner Center	
 	LIF		Left Inside Front	
 	LIR		Left Inside Rear	
 	LOC		Left Outer Center	
 	LOF		Left Outside Front	
 	LOR		Left Outside Rear	
 	LR		Left Rear	
 	LS		Left Side	
 	R		Rear	
 	R0F		Right Outside Front	
 	RF		Right Front	
 	RIC		Right Inner Center	
 	RIF		Right Inside Front	
 	ROC		Right Outer Center	
 	ROR		Right Outside Rear	
 	RR		Right Rear	
 	RS		Right Side	
 	RSC		Right Side Center	
 	RSF		Right Side Front	
 	RSR		Right Side Rear	
 	T		Top	
 	TC		Top Center	
 	TF		Top Front	
 	TR		Top Rear	
 	U		Under	

	Segment:	SE Transaction Set Trailer
	Position:	0500
	Loop:
	Level:	
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
	Syntax Notes:
	Semantic Notes:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
M	SE01	96	Number of Included Segments	M	1 	N0 1/10	
	Total number of segments included in a transaction set including ST and SE segments	
M	SE02	329	Transaction Set Control Number	M	1 	AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set	

	Segment:	GE Functional Group Trailer
	Position:	0550
	Loop:
	Level:	
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the end of a functional group and to provide control information
	Syntax Notes:
	Semantic Notes:	1	The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
M	GE01	97	Number of Transaction Sets Included	M	1 	N0 1/6	
	Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element	
M	GE02	28	Group Control Number	M	1 	N0 1/9	
	Assigned number originated and maintained by the sender	

	Segment:	IEA Interchange Control Trailer
	Position:	0600
	Loop:
	Level:	
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To define the end of an interchange of zero or more functional groups and interchange-related control segments
	Syntax Notes:
	Semantic Notes:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	    Attributes    
M	IEA01	I16	Number of Included Functional Groups	M	1 	N0 1/5	
	A count of the number of functional groups included in an interchange	
M	IEA02	I12	Interchange Control Number	M	1 	N0 9/9	
	A control number assigned by the interchange sender