Segment: ISA Interchange Control Header Level: N/A … _Generic.pdf · Implementation Guidelines for AIAG EDI Conventions TRANSACTION: 856 DATE: 10/29/05 VERSION: 004010 PAGE: 1 Segment:

Implementation Guidelines for

AIAG EDI Conventions

TRANSACTION: 856 DATE: 10/29/05 VERSION: 004010 PAGE: 1

Segment: ISA Interchange Control Header Level: N/A Loop: _______ Usage: Mandatory 1 per interchange Max Use: 1 Purpose: To start and identify an interchange of one or more functional groups and interchange- related control segments. Notes:

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS ISA01 I01 Authorization Information Qualifier M ID 2/2 Use "00" ISA02 I02 Authorization Information M AN 10/10 Use ten spaces ISA03 I03 Security Information Qualifier M ID 2/2 Use "00" for password ISA04 I04 Security Information M AD 10/10 Use ten spaces. ISA05 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes. ISA 06 I06 Interchange Sender ID M ID 15/15 ID Left justify, space fill. ISA07 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes. ISA08 I07 Interchange Receiver ID M ID 15/15 ID Left justify, space fill. ISA09 I08 Interchange Date M DT 6/6 Date of creation ISA10 I09 Interchange Time M TM 4/4 Time of creation ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Use "U" for U.S. ISA12 I11 Interchange Control Version Number M ID 5/5 Use "00400" ISA13 I12 Interchange Control Number M N0 9/9 A number that cannot be repeated within a 1-year period at a time. ISA14 I13 Acknowledgment Requested M ID 1/1 Use "0" for no Ack. Req., use "1" for Ack. Req.




Data Element Summary

REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS ISA15 I14 Test Indicator M ID 1/1 Use "T" for test data of "P" for production data. ISA16 I15 Subelement Separator M AN 1/1




Segment: GS Functional Group Header Level: N/A Loop: as required Usage: Mandatory 1 per functional group Max Use: 1 Purpose: To indicate the beginning of a functional group and to provide control information. Notes: See the ASC X12 segment directory for rules and notes. Strict compliance and agreement on content by trading partners is required.

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS GS01 479 Functional Identifier Code M ID 2/2 “SH” = Shipment Notice GS02 142 Application Sender’s Code M ID 2/15 Use Sender ID from ISA06. GS03 124 Application Receiver’s Code M ID 2/15 Use Receiver ID from ISA08. GS04 29 Data Interchange Date M DT 8/8 Date created GS05 30 Data Interchange Time M TM 4/4 Time created GS06 28 Data Interchange Control Number M N0 1/9 Start with 1 and increment by 1 for each subsequent GS segment. GS07 455 Responsible Agency Code M N0 1/2 Enter "X" for ASC X12 formats GS08 480 Version/Release/Industry ID Code M ID 1/12 Use "004010" for this version/release.




Segment: GE Functional Group Trailer Level: N/A Loop: _______ Usage: Mandatory 1 per functional group Max Use: 1 Purpose: To indicate the end of a functional group and to provide control information. Notes: 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 OUR DESC. ELEM NAME ATTRIBUTES COMMENTS GE01 97 Number of Transaction Sets Included M N0 1/6 Total number of ST segments in group GE02 28 Data Interchange Control Number M N0 1/9 Must be identical to the same data element in the associated group header (GS06)




Segment: IEA Interchange Control Trailer Level: N/A Loop: _______ Usage: Mandatory 1 per interchange Max Use: 1 Purpose: To define the end of an interchange of one or more functional groups and interchange-related control segments. Notes: The interchange control number IEA02 in this trailer must match the value in ISA13.

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS IEA01 I16 Number of Included Functional Groups M N0 1/5 Number of GS segments included between ISA and this IEA. IEA02 I12 Interchange Control Number M N0 9/9 Must match ISA13




ADVANCED SHIPMENT NOTICE TRANSACTION SET (856) Data Segment Sequence for the Heading Area Page Seq. Req. Des Max Loop Ref. ID Name AIAG US Use Repeat Table 1 8 ST Transaction Set Header M M 1 9 BSN Beginning Segment M M 1 10 DTM Date Time M M 1




ADVANCED SHIPMENT NOTICE TRANSACTION SET (856) Data Segment Sequence for the Detail Area Page Seq. Req. Des Max Loop Ref. ID Name AIAG US Use Repeat Table 2 LOOP ID – HL – (Shipment) 10000 11 HL Hierarchical Level – (Shipment) M M 1 12 MEA Measurements M M 1 13 TD1 Carrier Details M M 1 14 TD5 Carrier Details O O 1 15 TD3 Carrier Details O O 20 16 REF Reference O M 260 LOOP ID – HL/N1 3 17 N1 Name O M 1 LOOP ID – HL – (Order) 10000 18 HL Hierarchical Level – (Order) M M 1 19 LIN Item Identifier M M 1 20 SN1 Item Detail M M 1 LOOP ID – HL – (Item) 10000 21 HL Hierarchical Level – (Item) O O 1 22 REF Reference O O 1 23 CLD Load Detail O O 1 24 REF Reference O O 1 Data Segment Sequence for the Summary Area Page Seq. Req. Des Max Loop Ref. ID Name AIAG US Use Repeat Table 3 25 CTT Transaction Totals M M 1 26 SE Transaction Set Trailer M M 1




Segment: ST Transaction Set Header Level: Header Loop: _____ Usage: Mandatory Max Usage: 1 Purpose: To indicate the start of a transaction set and to assign a control number. General Info: The transaction set control number (ST02) in the header must match the transaction set control number (SE02) in the transaction set trailer (SE). Example: ST*856*0001 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS ST01 143 Transaction Set ID Code M ID 03/03 Use "856" ST02 329 Transaction Set Control Number M AN 04/09 A unique control number assigned to each transaction set within a functional group starting with 0001 and incrementing by 1 for each subsequent transaction set.




Segment: BSN Beginning Segment for Ship Notice Level: Header Loop: _____ Usage: Mandatory Max Use: 1 Purpose: To transmit identifying numbers, date and other basic data relating to the transaction set. General Info: The intent of this segment is to provide information for the entire transaction. Some of this information may be overridden by subsequent segments in the transaction. To change a previous ASN you must first cancel the previous one. Examples: BSN*00*123456*20020920*1300 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS BSN01 353 Transaction Set Purpose Code M ID 02/02 "00" = Original “01” = Cancellation BSN02 396 Shipment Identification M AN 01/30 Unique supplier-assigned number that is not repeated within a one year period. BSN03 373 Date M DT 08/08 Date created (CCYYMMDD) BSN04 337 Time M ID 04/08 Time created expressed in 24-hour clock as HHMM.




Segment: DTM Date/Time Reference Level: Header Loop: _____ Usage: Mandatory Max Use: 10 Purpose: To specify pertinent dates and times. General Info: At least one DTM segment is required. Examples: DTM*011*20020920*1300 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS DTM01 374 Date/Time Qualifier M AN 03/03 “011” = Shipped DTM02 373 Date M DT 08/08 Date created (CCYYMMDD) DTM03 337 Time M ID 04/08 Time created expressed in 24-hour clock as HHMM.




Segment: HL Hierarchical Level Level: Detail - Shipment Loop: HL Repeat: 200000 Usage: Mandatory Max Use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments. General Info: HL at the shipment level must only occur once and must be the first HL. Examples: HL*1**S N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS HL01 628 Hierarchical ID Number M AN 01/12 Use “1” for this occurrence of the HL at the shipment level HL02 734 Hierarchical Parent ID Number O AN 01/12 Not used for this occurrence of the HL HL03 735 Hierarchical Level Code M ID 01/02 Use “S” for shipment level HL04 736 Hierarchical Child Code O ID 01/01 Code indicating whether there are child data segments subordinate to the level being described




Segment: MEA Measurements Level: Detail - Shipment Loop: HL Usage: Mandatory Max Use: 2 Purpose: To specify physical measurements or counts. General Info: Only gross weight is required and net weight may be sent if desired. Examples: MEA*PD*G*5000*LB N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS MEA01 737 Measurement Reference ID Code M ID 02/02 “PD” = Physical Dimensions MEA02 738 Measurement Qualifier M ID 01/03 “G” = Gross Weight “N” = Net Weight MEA03 739 Measurement Value M R 01/20 Weight in Pounds MEA04 355 Unit or Basis for Measurement Code M ID 01/01 “LB” = Pounds




Segment: TD1 Carrier Details (Quantity and Weight) Level: Detail - Shipment Loop: HL Usage: Optional Max Use: 20 Purpose: To specify the transportation details relative to commodity, weight and quantity. General Info: Examples: TD1*CTN90*5 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS TD101 103 Packaging Code M AN 03/05 Code identifying type of packaging. Part 1 - Packaging form (CTN). Part 2 - Packaging Material (90) TD102 80 Lading Quantity M N0 01/07 Number of packages specified in TD101




Segment: TD5 Carrier Details (Routing Sequence/Transit Time) Level: Detail - Shipment Loop: HL Usage: Optional Max Use: 12 Purpose: To specify the carrier, sequence of routing and to provide transit time information. General Info: Examples: TD5*B*2*RITE*M N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS TD501 133 Routing Sequence Code M ID 01/02 “B” – Origin/Delivery Carrier Any Mode TD502 66 Identification Code Qualifier M ID 01/02 “2” - SCAC TD503 67 Identification Code M AN 02/20 Use Carriers SCAC Code TD504 91 Transportation Method/Type Code M ID 01/02 Any AIAG Valid Code




Segment: TD3 Carrier Details (Equipment) Level: Detail - Shipment Loop: HL Usage: Optional Max Use: 12 Purpose: To specify the transportation details relating to the equipment used by the carrier. General Info: Examples: TD3*TL**TRUCKNUM N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS TD301 40 Equipment Description Code M ID 02/02 “TL” – Trailer TD302 206 Equipment Initial O AN 01/04 Carrier’s SCAC code TD303 207 Equipment Number M AN 01/10 Carrier’s Trailer Number




Segment: REF Reference Numbers Level: Detail - Shipment Loop: HL Usage: Optional Max Use: 200 Purpose: To specify identifying numbers General Info: At least 2 iterations are required. Examples: REF*PK*12345 N/L REF*BM*98765 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS REF01 128 Reference Number Qualifier M ID 2/2 “PK” – Packing List Number “BM” – Bill of Lading Number Any Valid AIAG Code REF02 127 Reference Number M AN 1/30 Reference Number as qualified by REF01




Segment: N1 Name Level: Detail Shipment Loop: HL/N1 Repeat: 200 Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name and code. General Info: This N1 loop in the header area can be used to identify the supplier, ship to and material issuer locations. All three codes are required. Examples: N1*SU**01*123456789 N/L N1*ST**92*9999 N/L N1*MI**92*9999 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS N101 98 Entity Identifier Code M ID 02/02 "ST" = Ship to location "SU" = Supplier "MI" = Material Issuer N102 93 Name O AN 01/35 Not used N103 66 ID Code Qualifier M ID 01/02 "01" = DUNS Number “92” = Assigned by Buyer “ZZ” = Mutually Defined N104 67 ID Code M ID 02/20 Assigned ID Code




Segment: HL Hierarchical Level Level: Detail - Order Loop: HL Repeat: 200000 Usage: Mandatory Max Use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments. General Info: HL at the shipment level must only occur once and must be the first HL. Examples: HL*2*1*O N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS HL01 628 Hierarchical ID Number M AN 01/12 Increment by 1 for each subsequent HL segment HL02 734 Hierarchical Parent ID Number M AN 01/12 Identification number of the next higher data segment that the data segment being described is subordinate to HL03 735 Hierarchical Level Code M ID 01/02 Use “O” for order level HL04 736 Hierarchical Child Code O ID 01/01 Code indicating whether there are child data segments subordinate to the level being described




Segment: LIN Item Identification Level: Detail - Order Loop: HL Usage: Mandatory Max Use: 1 Purpose: To specify basic item identification data. General Info: Used to identify part, purchase order and release number information. The part number and purchase order number are required. Examples: LIN**BP*425966C1*PO*P123456*RE*0001 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS LIN01 350 Assigned Identification O AN 01/06 Not used LIN02 235 Product/Services ID Qualifier M ID 02/02 The first pair of Product/Service ID Qualifier and Product Service ID (data elements 235 and 234) is used to indicate the Part Number. LIN03 234 Product/Service ID M AN 01/30 Identifying number for product or service NOTE: LIN04 thru LIN31 provide 14 additional pairs of Product/Service ID Qualifier (235) Product/Service ID (234). The following codes for element #235 are acceptable: BP = Buyer's Part Number PO = Purchase Order Number RE = Release Number




Segment: SN1 Item Detail (Shipment) Level: Detail - Order Loop: HL Usage: Mandatory Max Use: 1 Purpose: To specify line item detail relative to the shipment. General Info: Used to show the net quantity shipped, unit of measure and cumulative year-to-date shipments if applicable. Examples: SN1**5000*LB*50000 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS SN101 350 Assigned Identification O AN 01/11 Not used SN102 382 Number of units shipped M R 01/10 Total quantity shipped SN103 355 Unit or Basis for Measurement Code M ID 01/02 Must be same unit of measure provided on 830 or 862 document. SN104 646 Quantity Shipped to Date O R 01/09 Total quantity shipped to date including this shipment




Segment: HL Hierarchical Level Level: Detail - Item Loop: HL Repeat: 200000 Usage: Mandatory Max Use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments. General Info: HL at the shipment level must only occur once and must be the first HL. Examples: HL*3*2*I N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS HL01 628 Hierarchical ID Number M AN 01/12 Increment by 1 for each subsequent HL segment HL02 734 Hierarchical Parent ID Number M AN 01/12 Identification number of the next higher data segment that the data segment being described is subordinate to HL03 735 Hierarchical Level Code M ID 01/02 Use “I” for item level HL04 736 Hierarchical Child Code O ID 01/01 Code indicating whether there are child data segments subordinate to the level being described




Segment: REF Reference Numbers Level: Detail - Item Loop: HL Usage: Optional Max Use: 200 Purpose: To specify identifying numbers General Info: Examples: REF*DK*DOCK N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS REF01 128 Reference Number Qualifier M ID 02/02 “DK” – Dock Number REF02 127 Reference Number M AN 01/30 Reference Number as qualified by REF01 REF03 352 Description O AN 01/80 Not used




Segment: CLD Load Detail Level: Detail - Item Loop: HL/CLD Repeat: 200 Usage: Optional Max Use: 1 Purpose: To specify the number of material loads shipped General Info: Used to inform us about the number of loads shipped and the quantity per load Examples: REF*5*1000*CTN90 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS CLD01 622 Number of Loads M N0 01/05 Number of customer defined loads Shipped by the supplier CLD02 382 Number of Units Shipped M R 01/10 Total quantity per container CLD03 103 Packaging Code O AN 03/05 Code identifying type of packaging. Part 1 - Packaging form (CTN). Part 2 - Packaging Material (90)




Segment: REF Reference Numbers Level: Detail - Item Loop: HL/CLD Usage: Optional Max Use: 200 Purpose: To specify identifying numbers General Info: Used to specify bar-coded serial numbers relative to the load (CLD) described above. Examples: REF*LS*S123456789 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS REF01 128 Reference Number Qualifier M ID 02/02 “LS” – Bar-coded serial number REF02 127 Reference Number M AN 01/30 Bar-coded serial number with prefix REF03 352 Description O AN 01/80 Not used




Segment: CTT Transaction Totals Level: Summary Loop: ________ Usage: Mandatory Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set. Example: CTT*4 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS CTT01 354 Number of Line Items M NO 01/06 Total number of HL segments




Segment: SE Transaction Set Trailer Level: Summary Loop: _________ 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). General Info: The transaction set control number value in this trailer (SE02) must match the Same element value in the transaction set header (ST02). Example: SE*18*0001 N/L

Data Element Summary REF. DATA OUR DESC. ELEM NAME ATTRIBUTES COMMENTS SE01 96 Number of Included Segments M NO 01/06 Number of included segments SE02 239 Transaction Set Control Number M AN 04/09 Same as ST02

Documents

Segment: ISA Interchange Control Header Level: N/A … _Generic.pdf · Implementation Guidelines for AIAG EDI Conventions TRANSACTION: 856 DATE: 10/29/05 VERSION: 004010 PAGE: 1 Segment: