LVS/ET Division ASN Advance Ship Notice

Transcription

1 LVS/ET Division ASN Advance Ship Notice ANSI X12 Version lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 1 of 28

2 856 Advance Ship Notice Transaction Layout: Segments: Arm Req Pos No Seg ID Name Req Des Max Use Loop Repeat Notes and Examples Required 001 ISA Interchange Control Header M 1 Required 002 GS Functional Group Header M 1 Heading: Arm Req Pos No Seg ID Name Req Des Max Use Loop Repeat Notes and Examples Required 010 ST Transaction Set Header M 1 Required 020 BSN Beginning Segment for Ship M 1 Notice Required 040 DTM Date/Time Release O 10 Detail: Arm Req Pos No Seg ID Name Req Des Max Use Loop Repeat Notes and Examples LOOP ID HL Required Required Required Required Required Required HL MEA TD1 TD5 TD3 REF Hierarchical Level Measurements Carrier Details (Quantity & Weights) Carrier Details (Routing Sequence /Transit Time Carrier Details (Equipment) Reference Identification M O O O O O >1 LOOP ID N1 200 Required 220 N1 Name O 1 LOOP ID SAC >1 Optional 320 SAC Service Promotion, Allowance, or Charge Information O 1 lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 2 of 28

3 LOOP ID HL Required 010 HL Hierarchical Level M 1 Required 020 LIN Item Identification O 1 Required 030 SN1 Item Detail (Shipment) O 1 LOOP ID CLD 200 Optional 170 CLD Load Detail O 1 Optional 180 REF Reference Identification O 200 Summary: Arm Req Pos No Seg ID Name Req Des Max Use Loop Repeat Notes and Examples Required 010 CTT Transaction Totals O 1 Required 020 SE Transaction Set Trailer M 1 Segments: Arm Req Pos No Seg ID Name Req Des Max Use Loop Repeat Notes and Examples Required 00Y GE Functional Group Trailer M 1 Required 00Z IEA Interchange Control Trailer M 1 lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 3 of 28

4 Segment: ISA Interchange Control Header Position: 001 Loop: Level: Heading Usage: Mandatory Purpose: To start and identify an interchange of zero or more functional groups and interchangerelated control segments ISA~00~ ~00~ ~ZZ~ ~ZZ~ LVS ~070226~1413~U~00401~ ~0~P~~` Required ISA01 I01 Authorization Information Qualifier M ID 2/2 Code to identify the information in Authorization information 00 No authorization information present Required ISA02 I02 Authorization Information Description M 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 blank Required ISA03 I03 Security Information Qualifier M ID 2/2 Code to identify the type of information in the Security Information. All valid standard codes are used 00 No security information present Required ISA04 I04 Security Information M 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 blank Required ISA05 I05 Interchange ID Qualifier M ID 2/2 Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified. All valid standard codes are used 01 Duns (Dun & Bradstreet) 12 Phone (Telephone companies) ZZ Mutually Defined Required ISA06 I06 Interchange Sender ID M AN 15/15 Code 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 Required ISA07 I05 Interchange ID Qualifier M ID 2/2 Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified. All valid standard codes are used 01 Duns (Dun & Bradstreet) 12 Phone (Telephone companies) ZZ Mutually Defined Required ISA08 I07 Interchange Receiver ID M AN 15/15 Identification code published by the receiver of thedata. 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 Required ISA09 I08 Interchange Date M DT 6/6 Date of the interchange lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 4 of 28

5 Required ISA10 I09 Interchange Time M TM 4/4 Time of the interchange Required ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer Required ISA12 I11 Interchange Control Version Number M ID 5/5 This version number covers the interchange control segments Draft standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997 Required ISA13 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender Required ISA14 I13 Acknowledgment Requested M ID 1/1 Code sent by the sender to request an interchange acknowledgment 0 No Acknowledgement Required Required ISA15 I14 Usage Indicator M ID 1/1 Code to indicate whether data enclosed by this interchange envelope is test, production or information P Production Date T Test Data Required ISA16 I15 Component Element Separator M 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 lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 5 of 28

6 Segment: GS Functional Group Header Position: 002 Loop: Level: Heading Usage: Mandatory Purpose: To indicate the beginning of a functional group and to provide control information GS~SH~ ~ ~ ~1413~999~X~004010` Required GS Functional Identifier Code M ID 2/2 Code identifying a group of application related transaction sets. All valid standard codes are used. Required GS Application Sender s Code M AN 2/15 Code identifying party sending transmission. Codes agreed to by Trading Partners. Required GS Application Receiver s Code M AN 2/15 Code identifying party receiving transmission. Codes agreed to by Trading Partners. Required GS Date M DT 8/8 Date expressed as CCYYMMDD Required GS Time M TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H=hours (0-23), M=minutes (00-59), S=integer segments (00-59), and DD=decimal seconds; decimal seconds are expressed as follows: D=tenths (0-9) and DD=hundreths (00-99) Required GS06 28 Group Control Number M N0 1/9 Assigned number originated and maintained by the Sender Required GS Responsible Agency Code M ID 1/2 Code used in conjunction with Data Element 480 to identify the issuer of the standard. X Accredited Standards Committee X12 Required GS Version / Release / Industry Identifier Code M AN 1/12 Code indicating the version, release, sub-release, 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 release and sub-release, 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 4010 Draft Standards Approved for Publications by ASC X12 Procedures Review Board through October 1997 lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 6 of 28

7 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Purpose: To indicate the start of a transaction set and to assign a control number Semantic Notes: The transaction set identifier (ST01) is used by the translation routines of the Interchange partners to select the appropriate transaction set. ST~856~30001` Required ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set Required ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 7 of 28

8 Segment: BSN Beginning Segment for Ship Notice Position: 020 Loop: Level: Heading Usage: Mandatory Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set Semantic Notes: 1 BSN03 is the date the shipment transaction set is created. 2 BSN04 is the time the shipment transaction set is created. BSN~00~ ~ ~1410` Required BSN Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set Required BSN Shipment Identification M AN 2/30 A unique control number assigned by the original shipper to identify a specific shipment Unique supplier assigned Shipment ID Number (SID) that is not repeated Within a one-year period. This number will be the key identifying number for reconciliation of payments Required BSN Date M DT 8/8 Date expressed as CCYYMMDD Local ASN creation date Required BSN Time M TM 4/8 Time expressed in 24-hour clock time as follows: HHMM Local ASN creation time lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 8 of 28

9 Segment: DTM Date/Time Reference Position: 040 Loop: Level: Heading 0 Purpose: To specify pertinent dates and times Semantic Notes: If DTM04 is present, then DTM03 is required. DTM~011~ ~1410~ET` Required DTM Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 011 Shipped Required DTM Date C DT 8/8 Date expressed as CCYYMMDD The local shipment date Required DTM Time C TM 4/8 Time expressed in 24-hour clock time as follows: HHMM The local shipment time Required DTM Time Code O ID 2/2 Code identifying the time. Use an appropriate code. Some typical codes from ASC X12 Data Element Dictionary are: CD Central Daylight Time CS Central Standard Time CT Central Time ED Eastern Daylight Time ES Eastern Standard Time ET Eastern Time GM Greenwich Mean Time MD Mountain Daylight Time MS Mountain Standard Time MT Mountain Time PD Pacific Daylight Time PS Pacific Standard Time PT Pacific Time lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 9 of 28

10 Segment: HL Hierarchical Level Position: 010 Loop: HL Mandatory Level: Detail Usage: Mandatory Purpose: To identify dependencies among and the content of hierarchically related groups of data Segments Semantic Notes: 1 The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to lineitem data. The HL segment defines a top-down/left-right ordered structure 2 HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction. 3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate 4 HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information. HL~1~~S` Required HL Hierarchical ID Number M AN 1/12 A unique number assigned by the sender to identify a particular data segment in a hierarchical structure "1" in the initial HL segment, incrementing by 1 each subsequent HL segment within the transaction. HL Hierarchical Parent ID Number O AN 1/12 Identification number of the next higher hierarchical data segment that the data Segment being described is subordinate to Required except for Shipment level Required HL Hierarchical Level Code M ID 1/2 Code defining the characteristic of a level in a hierarchical structure S Shipment lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 10 of 28

11 Segment: MEA Measurements Position: 080 Loop: HL Mandatory Level: Detail Max Use: 40 Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights Semantic Notes: MEA04 defines the unit of measure for MEA03. MEA~PD~G~15000~LB` MEA~PD~N~14000~LB` Required MEA Measurement Reference ID Code O ID 2/2 Code identifying the broad category to which a measurement applies PD Physical Dimensions Required MEA Measurement Qualifier O ID 1/3 Code identifying a specific product or process characteristic to which a measurement applies G Gross Weight N Actual Net Weight Required MEA Measurement Value C R 1/20 The value of the measurement MEA04 C001 Composite Unit of Measure C 0/1 To identify a composite unit of measure Required C Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken LB Pound lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 11 of 28

12 Segment: TD1 Carrier Details (Quantity and Weight) Position: 110 Loop: HL Mandatory Level: Detail Max Use: 20 Purpose: To specify the transportation details relative to commodity, weight, and quantity Semantic Notes: IF TD101 is present, then TD102 is required. Notes: TD1~CTN25~12` Required by ArvinMeritor at the Shipment level to indicate the total number of higher level packages (pallets, skids, etc.) on the shipment. Required TD Packaging Code O AN 3/5 Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required Use an appropriate code. Some typical codes from ASC X12 Data Element Dictionary are: BOX25 Cardboard Box COL52 Steel Coil CTN25 Carboard Carton MIX90 Mixed Container Types PLT71 Pallet Required TD Lading Quantity C N0 1/7 Number of units (pieces) of the lading commodity lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 12 of 28

13 Segment: TD5 Carrier Details (Routing Sequence/Transit Time) Position: 120 Loop: HL Mandatory Level: Detail 2 Purpose: To specify the carrier and sequence of routing and provide transit time information Semantic Notes: 1 If TD502 is present, then TD503 is required. 2 If TD507 is present, then TD508 is required.. TD5~B~2~ZIXP~LT` Required TD Routing Sequence Code O ID 1/2 Code describing the relationship of a carrier to a specific shipment movement B Origin/Delivery Carrier (Any Mode) Required TD Identification Code Qualifier C ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 2 Standard Carrier Alpha Code (SCAC) Required TD Identification Code C AN 2/80 Code identifying a party or other code Valid, mutually agreed SCAC Code Required TD Transportation Method/Type Code C ID 1/2 Code specifying the method or type of transportation for the shipment. Some typical codes from ASC X12 Data Element Dictionary are: A Air AE Air Express D Parcel Post E Expedited Truck LT Less Than Trailer Load (LTL) M Motor (Common Carrier) O Containerized Ocean R Rail TD Routing C AN 1/35 Free-form description of the routing or requested routing for shipment, or the Originating carrier's identity Carrier Text Name TD Location Qualifier O ID 1/2 Code identifying type of location OR Origin (Shipping Point) PE Port of Entry (Port where customs is declared) PP Pool Point TD Location Identifier X AN 1/30 Code which identifies a specific location If TD507 = "PP" use pool point shown on Supplier Routing Instructions. If TD507 = "OR" use originating airport code from airbill lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 13 of 28

14 Segment: TD3 Carrier Details (Equipment) Position: 130 Loop: HL Mandatory Level: Detail 2 Purpose: To specify transportation details relating to the equipment used by the carrier Semantic Notes: If TD302 is present, then TD303 is required.. TD3~TL~~211` Required TD Equipment Description Code C ID 2/2 Code identifying type of equipment used for shipment Use any valid code from the ANSI X12 v4010 dictionary. TD Equipment Initial O AN 1/4 Prefix or alphabetic part of an equipment unit's identifying number Use alpha portion of the Equipment ID Required TD Equipment Number C AN 1/10 Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred) Trailer number, Flight number, or Railcar number lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 14 of 28

15 Segment: REF Reference Identification Position: 150 Loop: HL Mandatory Level: Detail Max Use: >1 Purpose: To specify identifying information Notes: REF~PK~ ` REF~BM~ ` At least one REF segment with a "PK" qualifier (Packing Slip Number) is required at this level. Required REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification. Use an appropriate code. Some typical codes from ASC X12 Data Element Dictionary are: AW Air Waybill Number BM Bill of Lading Number CN Carrier's Reference Number (PRO/Invoice) FR Freight Bill Number KB Beginning Kanban Serial Number KE Ending Kanban Serial Number MB Master Bill of Lading PK Packing List Number SI Shipper s Identifying Number for Shipment (SID) Required REF Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 15 of 28

16 Segment: N1 Name Position: 220 Loop: N1 Optional Level: Detail Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required 2 If either N103 or N104 is present, then the other is required Semantic Notes: This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. N1~ST~~92~0999` N1~SF~~92~ ` N1~SU~~92~ ` Required N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an Individual SF Ship From ST Ship To SU Supplier/Manufacturer shipment N Name C AN 1/60 Free-form name Required N Identification Code Qualifier C ID 1/2 Code designating the system/method of code structure used for Identification 1 D-U-N-S Number, Dun & Bradstreet 12 Telephone Number (Phone) 92 Assigned by Buyer or Buyer's Agent ZZ Mutually Defined Required N Identification Code C AN 2/80 Code identifying a party or other code lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 16 of 28

17 Segment: SAC Service, Promotion, Allowance, or Charge Information Position: 320 Loop: SAC Optional Level: Detail Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge SAC~C~D240~~~10217~~~~~~~06` Required SAC Allowance or Charge Indicator M ID 1/1 Code which indicates an allowance or charge for the service specified A Allowance C Charge Q Charge Request S Service Required SAC Service, Promotion, Allowance, or Charge Code C ID 4/4 Code identifying the service, promotion, allowance, or charge D240 Freight H550 Surcharge I260 Transportation Direct Billing I500 Vendor Freight Required SAC Amount O N2 1/15 Monetary amount Required SAC Allowance or Charge Method of Handling Code O AN 2/2 Code indicating method of handling for an allowance or charge. Use appropriate code. 05 Charge to be paid by Vendor 06 Charge to be paid by Customer ZZ Mutually Defined lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 17 of 28

18 Segment: HL Hierarchical Level Position: 010 Loop: HL Mandatory Level: Detail Usage: Mandatory Purpose: To identify dependencies among and the content of hierarchically related groups of data Segments Semantic Notes: 1 The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to lineitem data. The HL segment defines a top-down/left-right ordered structure 2 HL01 shall contain a unique alphanumeric number for each ocurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction. 3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate 4 HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information. HL~2~1~I` Required HL Hierarchical ID Number M AN 1/12 A unique number assigned by the sender to identify a particular data segment in a hierarchical structure "1" in the initial HL segment, incrementing by 1 each subsequent HL segment within the transaction Required HL Hierarchical Parent ID Number O AN 1/12 Identification number of the next higher hierarchical data segment that the data Segment being described is subordinate to Required HL Hierarchical Level Code M ID 1/2 Code defining the characteristic of a level in a hierarchical structure I Item lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 18 of 28

19 Segment: LIN Item Identification Position: 020 Loop: HL Mandatory Level: Detail Purpose: To specify basic item identification data Syntax Notes: 1 If either LIN04 or LIN05 is present, then the other is required 2 If either LIN06 or LIN07 is present, then the other is required LIN~~BP~ ` Required LIN Product/Service ID Qualifier M ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number Required LIN Product/Service ID M AN 1/48 Identifying number for a product or service ArvinMeritor part number LIN Product/Service ID Qualifier C ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) EC Engineering Change Level RC Returnable Container Number VP Vendor's (Seller's) Part Number LIN Product/Service ID C AN 1/48 Identifying number for a product or service If LIN04 = "VP", then this is the Vendor part number. If LIN04 = "EC", then this is the engineering change level. If LIN04 = "RC", then this is the Returnable Container LIN Product/Service ID Qualifier C ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) LIN Product/Service ID C AN 1/48 Identifying number for a product or service If LIN06 = "VP", then this is the Vendor part number. If LIN06 = "EC", then this is the engineering change level. If LIN06 = "RC", then this is the Returnable Container Code. LIN Product/Service ID Qualifier C ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) LIN Product/Service ID C AN 1/48 Identifying number for a product or service If LIN08 = "VP", then this is the Vendor part number. If LIN08 = "EC", then this is the engineering change level. If LIN08 = "RC", then this is the Returnable Container Code lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 19 of 28

20 Segment: SN1 Item Detail (Shipment) Position: 030 Loop: HL Mandatory Level: Detail Purpose: To specify line-item detail relative to shipment SN1~~1758~PC~86223` Required SN Number of Units Shipped M R 1/10 Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set Number of parts (quantity shipped) for the Buyer's Part indicated in the LIN segment Required SN Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Refer to the part unit of measure on your ArvinMeritor Purchase Order SN Shipped to Date O R 1/15 Number of units shipped to date YTD cumulative for current model year. lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 20 of 28

21 Segment: PRF Purchase Order Reference Position: 050 Loop: HL Mandatory Level: Detail Purpose: To provide reference to a specific purchase order Semantic Notes: PRF04 is the date assigned by the purchaser to purchase order. PRF~123456` Required PRF Purchase Order Number M AN 1/22 Identifying number for Purchase Order assigned by the orderer/purchaser ArvinMeritor PO number including amendments PRF Date O DT 8/8 Date expressed as CCYYMMDD ArvinMeritor PO Date. PRF Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set PO Line Number lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 21 of 28

22 Segment: CLD Load Detail Position: 170 Loop: HL Mandatory Level: Detail Purpose: To specify the number of material loads shipped CLD~6~293~CTN71` Required CLD Number of Loads M N0 1/5 Number of customer-defined loads shipped by the supplier Number of Containers Required CLD Number of Units Shipped M R 1/10 Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set. Total number of units in container Required CLD Packaging Code O AN 3/5 Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required. Use an appropriate code. Some typical codes from ASC X12 Data Element Dictionary are: BOX25 Cardboard Box COL52 Steel Coil CTN25 Carboard Carton MIX90 Mixed Container Types PLT71 Pallet Required CLD Size C R 1/8 Size of supplier units in pack Subpack quantity Required CLD Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken UOM for subpack quantity. lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 22 of 28

23 Segment: REF Reference Identification Position: 180 Loop: CLD Optional Level: Detail Max Use: 200 Purpose: To specify identifying information REF*DK*A` Required REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification. DK Dock Number Required REF Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 23 of 28

24 Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Purpose: To transmit a hash total for a specific element in the transaction set Semantic Notes: This segment is intended to provide hash totals to validate transaction completeness and correctness. CTT~2~500` Required CTT Number of Line Items M N0 1/6 Total number of line items in the transaction set Total number of HL loops in transaction CTT Hash Total O R 1/10 Total number of parts in ASN lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 24 of 28

25 Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary 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) SE~21~30001` Required SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments Required SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 25 of 28

26 Segment: GE Functional Group Trailer Position: 00Y Loop: Level: Summary Usage: Mandatory Purpose: To indicate the end of a functional group and to provide control information Semantic Notes: Comments: The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06. The use of identical interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header. GE~1~999` Required GE01 97 Number of Transaction Sets Included M N0 1/6 Total number of transaction sets included in the functional group of interchange (transmission) group terminated by the trailer containing this data element Required GE02 28 Group Control Number M N0 1/9 Assigned number originated and maintained by the Sender lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 26 of 28

27 Segment: IEA Interchange Control Trailer Position: 00Z Loop: Level: Summary Usage: Mandatory Purpose: To define the end of an interchange of zero or more functional groups and interchangerelated control segments IEA~1~ ` Required IEA Number of Included Groups M N0 1/5 A count of the number of functional groups included in an interchange Required IEA Interchange Control Number M N0 9/9 lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 27 of 28

28 856 (ASN) Advance Ship Notice v4010 Example: ISA~00~ ~00~ ~ZZ~ ~ZZ~ LVS ~070226~1413~U~00401~ ~0~P~~` GS~SH~ ~ ~ ~1413~999~X~004010` ST~856~30001` BSN~00~ ~ ~1410` DTM~011~ ~1410~ET` HL~1~~S` MEA~PD~G~15000~LB` MEA~PD~N~14000~LB` TD1~CTN25~12` TD5~B~2~ZIXP~LT` TD3~TL~~211` REF~PK~ ` REF~BM~ ` N1~ST~~92~0999` N1~SF~~92~ ` N1~SU~~92~ ` HL~2~1~I` LIN~~BP~ ` SN1~~1758~PC~86223` PRF~123456` CLD~6~293~CTN71` CTT~2~500` SE~21~30001` GE~1~999` IEA~1~ ` 856v4010 Revised 5/24/2007 Page 28 of 28