856 Advanced Shipping Notices (ASN)



Similar documents
ANSI X12 version Advance Ship Notice

Electronic Data Interchange

ANSI X12 ASN 856 Version

EDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)

Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS S

VDP Program Vendor Guidelines

Invoice. Transaction Set (810) (Outbound from TI)

Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

856 Ship Notice/Manifest - R US CANADA

214 Transportation Carrier Shipment Status Message - LTL

Staples Supplier Electronic Data Interchange Implementation Guide

X12 Implementation Guidelines For Outbound Receiving Advice v (861O)

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET

810 Invoice Revised 01/26/15

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

810 Invoice ANSI ASC X12 Version 4010

84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION August 21, 2007

ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message

ANSI X12 version Planning Schedule with Release Capability

EDI GUIDELINES INVOICE 810 VERSION 4010

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

MERITOR. EDI Business Process Guide

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

VERSION: ANSI X

EDI Specifications Advance Ship Notice (Supplier v4010)

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X Draft

Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)

810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:

EDI Services Guide December 2010

810 Invoice ANSI X.12 Version 5010

KANSAS CITY SOUTHERN EDI On-Boarding Guide

856 Advance Ship Notice Supplier Implementation Guide November 2015

214 Transportation Carrier Shipment Status Message

VOLVO Dealer Programs 810 Invoice EDI Guideline

Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS S Supplier

NEXCOM EDI 753 / 754 Supplier Shipping Instructions

Bill of Lading Number REF Reference Identification M AN 1/30 MustUse

Dart Container Corporation. EDI 810 Outbound Invoice Version 4010

Ford Customer Service Division SDS (Supplier Direct Ship) EDI Manual

BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010

Supply Chain Merchandise Logistics E-Commerce Purchase Order

EDI SPECIFICATIONS 4050VICS VERSION

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010

BORGWARNER IMPLEMENTATION GUIDELINE FOR V PLANNING SCHEDULE

Electronic Data Interchange

ASN. HDMA Electronic Data Interchange (EDI) Guidelines for the 856 Advance Ship Notice to Support Implementation of DSCSA

ANSI X12 version Text Message

3/31/08 ALTRA INDUSTRIAL MOTION Invoice Inbound 810 X Page 1 Created by Ralph Lenoir

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT IT1 Baseline Item Data M PID Product / Item Description M

Note: The following information is required on all Merchandise Invoices:

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS

Mazda North American Operations EDI Supplier Documentation October 20, 2015

The EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.

860 Purchase Order Change Request Buyer Initiated

824 Application Advice

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)

ADOBE ANSI X Version: 1.0

Customer EDI Guidelines United States 810 Invoice

RANDOM HOUSE. EDI Implementation Guide Invoice X12 Version 4010

322 TERMINAL OPERATIONS AND INTERMODAL RAMP ACTIVITY

ANSI X12 version Remittance Advice

EDI MAPPING SPECIFICATIONS 4010 VICS September 14, 2006 Revision

ANSI X Product Transfer and Resale Report

Electronic Document Interchange Standards Version 5050

CVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X

Bulk EDIFACT ASN MESSAGE FORMAT

RANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010

State of Tennessee Department of Revenue

Ultramar Ltd IMPLEMENTATION GUIDE

ZF Group North American Operations. EDI Implementation Guide

To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates. BIG^ ^12345^ ^ ^

ANSI ASC X12 SHIPMENT STATUS (214) VERSION

ORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version /2011 Page 1

999 Implementation Acknowledgment. Version: 1.0 Draft

Detail SE Transaction Set Trailer Summary GE Functional Group Trailer Summary IEA Interchange Control Trailer Summary. ISA Interchange Control Header

Purpose of the 270/271 Health Care Eligibility Benefit Inquiry and Response

As a service to Suppliers preferring to transact via EDI, Ariba SN accepts the ANSI X Ship Notice / Manifest document.

HIPAA EDI Companion Guide for 835 Electronic Remittance Advice

EDI. Overview. A Practical Guide to EDI and the TrueCommerce EDI Platform

PURCHASE ORDER RESPONSE

837 Professional Health Care Claim

BLUE CROSS AND BLUE SHIELD OF LOUISIANA DENTAL CLAIMS COMPANION GUIDE

DoD Transportation Electronic Data Interchange (EDI) Convention

Portland General Electric Implementation Standard

810 - Invoice. Set Number Set Name - Invoice Functional Group - IN

The information in this document will be common for all X12N implementation guides.

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

TABLE OF CONTENTS 1. INTRODUCTION TO EDI 2 2. PROGRAM OVERVIEW 4

Consignment No: Receiving Plant (Customer): example customer customer's street 57a City of customer GB

Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy

This document has been provided as a courtesy to anyone who wants to learn more about EDI and how it applies to their TrueCommerce solution.

State of Nebraska. Motor Fuels Division. EDI Implementation Guide. Revised May ANSI ASC X12 V.4030

DRS Defect Report Inbound 322. DRS Defect Report from Trading partner to Chassis.Com IB 322 Implementation Guide Prepared by Advent Inc for OCEMA

FEDERAL-MOGUL CORPORATION EDI SPECIFICATIONS 856 SHIP NOTICE ANSI X.12 VERSION

CSX EDI 824 Application Advice Version:

CREDIT CARD BULK PROVIDER REQUIREMENTS

Transcription:

NEXTEER Supplier Information Packet 856 Advanced Shipping Notices (ASN) Revised March, 2010

s GENERAL INFORMATION This packet is to provide information to Nexteer and SteeeringMex Direct Suppliers who are sending shipping notices to Nexteer. Programming should be FIXED BLOCK 80 Bytes. The purpose of an advanced shipping notice (856) is to electronically communicate details of a shipment to Nexteer via EDS*Elite (formerly GM-Net). The Nexteer Guidelines on the following pages, follow the GM Implementation Guidelines for version 002040GM. The Nexteer EDI Guideline details how Nexteer uses the ANSI X-12 transaction set within the Corporate Guidelines. It provides a standardized format for the data to be sent in a shipping schedule. The following section provides an interpretation of each segment of the 856 transaction set that will be received by Nexteer The EDS*Elit filename to be used is EDI856ASHP & destination code is SSG. The Guideline will detail three areas of the transmission: Heading Area, Detail Area, and Summary Area. Any exceptions for Nexteer will be noted where applicable. Please be sure to transmit an ASN within the first 15-30 minutes of the shipment leaving your Dock. The ASN must reach Nexteer before the shipment. 2/13/2013 2

s SEGMENT: ISA - Interchange Control Header (required) The ISA Segment is the Interchange Control Header used to start & identify an interchange of one or more functional groups & interchange related control segments. This is the only fixed length record in the ANSI X12 standard. 1 2 3 4 5 6 7 8 9 ISA*00* *01*SSG*01*123456789*01*005356878*970709 10 11 12 13 14 15 16 *2400*U*00204*000000001*0*P*?. Elem Elem Element Name & Definition ISA01 I01 1. Authorization Information Qualifier. Uses 00 (zeroes). * ISA02 I02 2. Authorization Information Segment. Uses 10 spaces. ** ISA03 I03 3. Security Information Qualifier. Uses 01. ISA04 I04 ISA05 I05 ISA06 I06 ISA07 I05 ISA08 I07 ISA09 I08 ISA10 I09 4. Security Information. Use EDS Elit (Van) destination code of SSG. 5. Interchange Id Qualifier. Use 01 indicating use of a Duns number. 6. Interchange Sender ID. The Supplier will use their Duns number. 7. Interchange ID Qualifier. Use 01 indicating use of a Duns number. 8. Interchange Receiver ID. The Supplier will use Nexteer Duns number. 9. Date of the transmission. The date will be in YYMMDD format. 10.Time of the transmission. The time is based on a 24 hour clock & is in HHMM format. 2/13/2013 3

s ISA11 I10 11. Interchange stands ID. Use U indicating USA. ISA12 I11 12. Interchange Version ID. Use 00204 or 00301. ISA13 I12 ISA14 I13 ISA15 I14 ISA16 I16 13. Interchange Control number. This is a sequential number starting with 1 & incrementing by 1 for each ISA between Sender & Receiver. 14. Acknowledge Requested Segment. Use 0 indicating that an acknowledgment is not required. 15. Test Indicator. A T will indicate test mode, & P will indicate production mode. 16. Sub-element separator. (Your choice) * Note if going through a VAN or FTP - need 03 in ISA01 **Note if going through a VAN or FTP - need EDI856ASHP in ISA02 2/13/2013 4

s SEGMENT: GS - Functional Group Header (required) The GS Segment indicates the beginning of a functional group & provides control information. 1 2 3 4 5 6 7 8 GS*SH*123456789*005356878*970709*2400*1*X*002040GM. Elem Elem Element Name & Definition GS01 479 GS02 142 GS03 124 GS04 29 GS05 30 GS06 28 1. Functional Identifier Code. Send SH indicating Ship Notice / Manifest. 2. Application Sender s Code. This is the Supplier s Duns Number. 3. Application Receiver s Code. This is Nexteer Duns Number 005356878. 4. Data Interchange Date. The format is YYMMDD. 5. Date Interchange Time. The format is HHMM based on a 2400 clock. 6. Date Interchange Control Number. GS07 455 7. Responsible Agency Code. X indicates ANSI ASC X12. GS08 480 8. Version/Release/Industry Identifier Code. Use 002040GM or 002040. 2/13/2013 5

s ISA**00* **01*SSG *01*123456789*01*005356878 *970722*2400*U*00204*000000001*0*P*. GS*SH*123456789*005356878*970722*2400*1*X*002040GM. HEADER DETAIL- SHIPMENT DETAIL- ORDER ST*856*0001 BSN*00*123456789*970709*2400 DTM*011*970709*2400 DTM*017*970805*2400 HL*1**S MEA*ST*G*39501*LB Cannot use Decimal Points TD1*PCS71*44 TD5*B*2*CETR*L TD3*TL*CETR*451030 REF*CN*PRO123456 (REQUIRED) REF*PK*123456 (REQUIRED) REF*BM*123456 REF*DK*07 Nexteer Specific (REQUIRED) N1*SU**1*123456789 N1*ST**1*005356878 N1*MI**1*005356878 N1*SF**1*123456789 HL*2*1*O LIN**BP*12345678 SN1**2500*LB*12345678 PRF*SAG1234567*123456**970709 DETAIL- HL*3*2*I ITEM SN1**25*BD Nexteer Specific CTT*1 SUMMARY SE*28*001 GE*1*1 IEA*1*000000001 * Note if going through a VAN or FTP - need 03 in ISA01 **Note if going through a VAN or FTP - need EDI856ASHP in ISA02 2/13/2013 6

s 856 TRANSACTION EXAMPLE WITH MULTIPLE ORDERS HEADER ST*856*0001 BSN*00*123456789*970709*2400 DTM*011*970709*2400 DTM*017*970805*2400 HL*1**S MEA*WT*G*39501*LB Cannot use Decimal Points MEA*WT*N*39501*LB Cannot use Decimal Points TD1*PCS71*44 TD5*B*2*CETR*L*CENTRAL TD3*TL*CETR*451030 REF*CN*PRO123456 (REQUIRED) DETAIL- REF*PK*123456 (REQUIRED) SHIPMENT REF*BM*123456 REF*DK*07 Nexteer Specific (REQUIRED) N1*SU**1*123456789 N1*ST**1*005356878 N1*MI**1*005356878 N1*SF**1*123456789 HL*2*1*O DETAIL- LIN**BP*12345678 CANNOT put same part # on ASN multiple times ORDER SN1**2500*LB*12345678 PRF*SAG1234567*123456**970709 HL*3*2*I DETAIL- SN1**25*BD Nexteer Specific ITEM DETAIL- ORDER MEA*PD*WT*2500*LB REF*HC*12345 REF*HC*23456 HL*4*1*O LIN**BP*01234567 SN1**2500*LB*12345678 PRF*SAG1234567*123456**970709 HL*5*4*I DETAIL- SN1**25*BD ITEM MEA*PD*WT*2500*LB Nexteer Specific REF*HC*12345 CTT*1 SE*28*001 GE*1*1 IEA*1*000000001 * Note if going through a VAN or FTP - need to have 03 in ISA01 **Note if going through a VAN or FTP - need to have EDI856ASHP in ISA02 2/13/2013 7

s SEGMENT SEQUENCE FOR THE HEADER AREA ST BSN DTM Transaction Set Header Beginning Segment (NO greater than 10 Characters) Date/Time Reference SEGMENT SEQUENCE FOR THE DETAIL AREA The Detail Area is comprised of three hierarchical levels - Detail Shipment, Detail Order & Detail Item. The Detail Shipment level contains data that applies to the whole shipment. This will include bill of lading numbers, quantities & supplier codes. MEA TD1 TD5 TD3 REF N1 Shipment Gross Weights Packaging - Quantity & Type Routing Information Equipment Description Shipment Level Reference Number Ship To/Ship From The Detail Order level contains data related to the order. This will include part numbers, number of units shipped & purchase order number. LIN SN1 PRF Customer s Part Number Quantity Shipped, Cumulative Quantity Shipped Customer s Order Number (PO#) The Detail Item level contains additional information related to the product being shipped. The Item Level will be required for all transmissions. SN1 MEA REF Number of Containers Shipped, Container Identification Shipment Net Weights Item Level Reference Numbers SEGMENT SEQUENCE FOR THE SUMMARY AREA CTT SE GE IEA Transaction Totals Transaction Set Trailer End of Functional Group Control Header 2/13/2013 8

SEGMENT: ST Segment Heading Level (Required) The ST Segment is the Transaction Set Header. 1 2 ST*856*0001 ST01 143 ST02 329 Transaction Set. The Supplier will send 856 to identify this transaction set as an Advanced Shipping Notice. Transaction Set Control Number. This will be a unique number that will not be repeated in the calendar year. 2/13/2013 9

SEGMENT: BSN Segment Heading Level (Required) The BSN Segment is the beginning segment of the transaction set 856. It indicates the beginning of a transaction set and is used to identify number and dates. 1 2 3 4 BSN*00*123456789*910111*2400 BSN01 353 BSN02 396 BSN03 373 BSN04 337 Transaction Set Purpose Code. It allows the supplier to communicate the ship notice information to the customer. Steering Solutions Services Corp will only accept code 00. 00 = Original - The first transmission of the transaction set for a shipment. Shipment ID Number (SID). This is a unique control number assigned by the original shipper to identify the shipment. This number must be referenced on both the packing list and the bill of lading as the SID. NO greater than 10 characters. Date transaction is generated. The date will be in the YYMMDD format. Time. This represents the time the transaction was created. The time will be in HHMM format based on a 24 hour clock. 2/13/2013 10

SEGMENT: DTM Segment Heading Level (Required) The DTM Segment is the Date/Time Reference segment. 1 2 3 DTM*011*910111*2400 (Required) DTM*017*910228*2400 (Optional) DTM01 374 Date/Time Qualifier. This qualifier specifies the type of date or time. 011 - Represents shipped on this date 017 - Represents estimated arrival date. DTM02 373 Ship Date/Estimated Arrival Date. The date will be in a YYMMDD format. DTM03 337 Ship Time/Estimated Arrival Time. The time will be HHMM format based on a 24 hour clock. 2/13/2013 11

SEGMENT: HL Segment Shipment Level (Required) The HL Segments are used to organize data in a format that contains the DETAIL-SHIPMENT, DETAIL-ORDER, and DETAIL-ITEM levels. 1 3 HL*1**S HL01 628 Hierarchical ID Number representing the first occurrence in the transaction set. Each subsequent HL segment will increment by 1. *** Please note that Hierarchical Parent ID is blank. HL03 735 Hierarchical Level Code. Valid codes for the HL segment are I, O, or S. Nexteer will accept S only to indicate shipment level. 2/13/2013 12

SEGMENT: MEA Segment Shipment Level (Required) The MEA Segment is used to specify physical measurements including dimensions, tolerances, weights and counts. 1 2 3 4 MEA*WT*G*39501*LB Cannot use Decimal Points MEA01 737 Measurement Reference ID Code. Nexteer will accept code WT weight. MEA02 738 Measurement Qualifier. Nexteer will accept the following codes: G - Gross Weight N - Net Weight MEA03 739 Value of the Measured Dimension - No decimals will be accepted. MEA04 355 Unit of Measure code. This field identifies the basic unit of measurement. Steering Solutions Services Corp will accept the following codes: LB - Pound TN - Net Ton 2/13/2013 13

SEGMENT: TD1 Segment Shipment Level (Required) The TD1 Segment specifies transportation details relative to commodity, weight, and quantity. 1 2 TD1*PCS71*44 TD101 103 Packaging Code. Nexteer will accept the following codes: Steel: Default: BDL52 - Bundle/Iron or Steel COL52 - Coil/Iron or Steel LIF52 - Lifts/Iron or Steel PCS71 - Pieces/Not otherwise specified TD102 80 Lading Quantity 2/13/2013 14

s SEGMENT: TD5 Segment Shipment Level (Required) The TD5 segment is used for routing sequence & carrier information. 1 2 3 4 TD5*B*2*CETR*L TD501 133 Routing Sequence Code. It specifies the carrier, routing & transit time. Nexteer will accept code B. TD502 66 ID Code Qualifier. Nexteer will accept code 2. TD503 67 TD504 91 This is the carrier SCAC code. On air shipments, an air bill number should be used. Transportation Mode. 2/13/2013 15

s SEGMENT: TD3 Segment Shipment Level (Optional) The TD3 Segment specifies transportation details relating to the equipment & numbers used by the carrier. 1 2 3 TD3*TL*CETR*451030 TD301 40 TD302 206 TD303 207 Equipment Description Code. Prefix or alpha part of an equipment unit s identifying number. A SCAC code may be used. Equipment Number Segment. A numeric form for the equipment number (trailer number). 2/13/2013 16

s SEGMENT: REF Segment Shipment Level (Required) The REF Segment is used to transmit identifying numbers associated with the named party. 1 2 REF*CN*PRO123456 (REQUIRED)* REF*PK*123456 (REQUIRED no greater than 10 characters) REF*BM*123456 REF*DK*07 (REQUIRED) REF01 128 This is the Reference Number Qualifier. Nexteer will accept the following codes: CN - Carrier s Reference Number (Pro #)* PK - Packing List Number BM - Bill of Lading Number DK - Dock Number REF02 127 This is the Reference Number. *Pro # can be any of the following: FEDX FEDX Tracking # LTL Carrier Pro # PNII ProTrans Pick Up # (needed by Nexteer Mex to track shipment) Dedicated or Milk Run Truck Routing # Carriers other than LTL ProTrans Pick Up # assigned 2/13/2013 17

s SEGMENT: N1 Segment Shipment Level (Required) code. The N1 Segment identifies the party by type of organization, name & A minimum of 3 iterations of the N1 are required. 1 3 4 N1*SU**1*123456789 N1*ST**1*005356878 N1*MI**1*005356878 N1*SF**1*123456789 N101 98 This is the Entity ID Code. This is a code identifying the type of party being defined. Mandatory codes are as follows: SU - Supplier ST - Ship To MI - Planning Schedule/Material Release Issuer *** Please note that if the supplier location & ship from location are not identical, a forth N1 segment is mandatory. Nexteer will accept code SF. SF - Ship From N103 66 This is the ID Code Qualifier. Nexteer will accept 1 to designate use of a DUN s number. N103 67 This is the ID Code. Nexteer will use DUN s Number 005356878 to identify the Ship To & Planning Schedule/Material Release Issuer. 2/13/2013 18

s SEGMENT: HL Segment Order level (Required) The HL Segment identifies dependencies among & content of related groups of data in segments. 1 2 3 HL*2*1*O HL01 628 HL02 734 HL03 735 This is the Hierarchical ID Number. This is the Hierarchical Level Parent ID Number. It is the ID number of the Next higher hierarchical data segment that the data segment being described is subordinated to. (Refers to shipment level - 1 being the parent ID). Code defining the characteristic of a level in the hierarchical structure. Valid codes for the HL segment are I, O, or S. Nexteer will accept O to indicate Order Level. 2/13/2013 19

SEGMENT: LIN Segment Order Level (Required) The LIN Segment specifies basic item identification data. 2 3 LIN**BP*12345678 LIN02 235 Product/Service ID Qualifier. Nexteer will accept code BP - Buyer s Part Number (eight digits). LIN03 234 Product/Service ID. This is the identifying number for the product. Number must be 8 digits. Same part # cannot be listed multiple times. Only once per ASN. Our system does not add. 2/13/2013 20

SEGMENT: SN1 Segment Order Level (Required) The SN1 Segment represents the quantity shipped and the cumulative quantity shipped. 2 3 4 SN1**2500*LB*50000 SN102 350 Number of Units Shipped. SN103 355 Unit of Measure Code. SN104 646 Quantity Shipped to Date. (Cumulative) 2/13/2013 21

SEGMENT: PRF Segment Order Level (Required) The PRF Segment provides reference to a specific purchase order. 1 2 4 PRF*SAG90I4567*123456**910111 PRF01 324 Purchase Order Number. This is the number on the shipment authorization document. Prefix SAG will only be accepted or can use just the PO. PRF02 328 Release Number. This is the number on the shipment authorization document. (optional) PRF04 323 Purchase Order Date. This is the date the purchase order originated. (optional) 2/13/2013 22

SEGMENT: HL Segment Item Level (Required) The HL Segment identifies dependencies among and content of related groups of data segments. 1 2 3 HL*3*2*I HL01 628 HL02 734 Hierarchical ID Number. Hierarchical Parent ID Number. HL03 735 Hierarchical Level Code. Valid codes for the HL Segment are S, O, or I. Nexteer will accept I at the Item Level. 2/13/2013 23

SEGMENT: SN1 Segment Item Level (Required) The SN1 Segment specifies line item detail relative to the shipment. 2 3 SN1**25*BD SN102 382 Number of Containers Used to Ship this Part. This is not a count of pieces shipped. SN103 355 Unit of Measure Code. This is a container identification code. If unsure speak with your plant contact for expected code. 2/13/2013 24

SEGMENT: MEA Segment Item Level (Optional, Unless Steel) The MEA Segment is used to specify physical measurements including dimensions, tolerances, weights, and counts. 1 2 3 4 MEA*PD*WT*2500*LB Cannot use Decimal Points MEA01 737 Measurement Reference ID Code. Nexteer will accept code PD - Physical Dimensions. MEA02 738 Measurement Qualifier. Nexteer will accept code WT - Weight. MEA03 739 Value of the Measured Dimension. This is the Net Weight. No decimals will be accepted. MEA04 355 Unit of Measurement Code. This field identifies the basic unit of measurement. Nexteer will accept the following codes: LB - Pound TN - Net Ton 2/13/2013 25

SEGMENT: REF Segment Item Level (Optional, Unless Steel) The REF Segment specifies identifying numbers. 1 2 REF*HC*12345 REF*HC*67890 REF01 128 Reference Number Qualifier. Nexteer will accept code HC - Heat Code. REF02 127 Reference Number 2/13/2013 26

SEGMENT: CTT Segment Summary (Required) The CTT Segment summarizes the transaction totals. 1 CTT*1 CTT01 354 Number of Line Items. This segment specifies the total number of line items in a transaction. 2/13/2013 27

SEGMENT: SE Segment Summary (Required) The SE Segment is a transaction set trailer. It indicates the end of the transaction set and provides a count of transmitted segments including the beginning and the ending segments. 1 2 SE*28*000000001 SE01 96 Number of Included Segments. SE02 329 Transaction Set Control Number. The number value in this trailer must match the same element value in the transaction set header (ST Segment). 2/13/2013 28

SEGMENT: GE Segment Summery (Required) The GE Segment specifies the end of a functional group of related transaction sets. 1 2 GE*1*000000001 GE01 97 Number of Included Transaction Sets. GE02 28 Data Interchange Control Number. This number must be identical to the same data element in the functional group header (GS Segment). 2/13/2013 29

SEGMENT: IEA Segment Summary (Required) The IEA Segment is the interchange control trailer. The purpose is to define the end segment of the envelope. 1 2 IEA*1*000000001 IEA01 IEA02 405 Number of Included Groups Segment. This is the number of GS segments included between the ISA and IEA segments. 709 Interchange Control Number. The control number must match the interchange control number of the ISA segment. 2/13/2013 30