856 EDI SPECIFICATIONS VERSION 4010

Transcription

1 856 EDI SPECIFICATIOS VERSIO /19/2007 Page 1 of 23 Revision 2

2 Transaction Set Header Segment: ST - Transaction Set Header Level: Heading Max. Use: 1 To indicate the start of the 856 transaction set and assign a transaction control number. The transaction set control number (data element ST02) in the header must match the transaction set control number in the trailer (data element SE02). ST*856*0001 ST Transaction Set Identifier Code ST Transaction Set Control umber M 3/3 856 M A 4/9 A unique number assigned to each transaction set within a functional group, starting with 0001 and incremented by 1 for each subsequent transaction set. 11/19/2007 Page 2 of 23 Revision 2

3 Beginning Segment for Ship otice Segment: BS - Beginning Segment for Ship otice Level: Heading Max. Use: 1 To transmit identifying numbers, dates and other basic data relating to the transaction set. BS*00*123456* *0810 BS BS Transaction Set Purpose Code Shipment Identification M 2/2 M A 2/30 00 = Original 05 = Replacement AS umber Unique supplier assigned number that is not repeated within a one year period. Infor Automotive recommends use of the shipment number (S). BS Date M DT 8/8 Date of AS Creation Format is YYYYMMDD BS Time M TM 4/4 Time of AS Creation Format is HHMM 11/19/2007 Page 3 of 23 Revision 2

4 Date/Time Reference Segment: Level: Max. Use: 2 Requirement: DTM - Date/Time Reference Heading DTM*011 Segment is Mandatory DTM*017 Segment is Optional To specify pertinent dates and times. DTM*011*880601*1115 or DTM*011*880601*1115*PT DTM*017*880607*0800 or DTM*017*880607*2300*PT DTM Date/Time Qualifier M 3/3 011 = Date and Time Shipment Leaves Supplier 017 = Estimated Date and Time of Arrival DTM Date M DT 8/8 If DTM01 is 011, this will be the shipment date. If DTM is 017, this will be the delivery date. Format is YYYYMMDD DTM Time C TM 4/4 If DTM01 = 011, this will be the shipment time. If DTM = 017, this will be the delivery time. Format is HHMM. DTM Time Code C A 2/2 Any valid time zone may be used (e.g., AT, ET, PT). This value can only be present if time value is present. 11/19/2007 Page 4 of 23 Revision 2

5 Hierarchal Level Segment: HL - Hierarchal Level Level: Detail - first segment in each HL loop Max. Use: 1 To identify dependencies among and the content of hierarchically related groups of data segments. The HL segment is used to identify levels of detail information using hierarchical structure, such as relating line item data to shipment data. Infor Automotive will only use the shipment and item levels. Cancellation ASs require only the shipment level. HL*1**S (shipment level) HL Hierarchical umber HL Hierarchical Parent umber HL Hierarchical Level Code HL Hierarchical Child Code M A 1/12 M A 1/12 M 1/2 1 for the first HL segment, incremented by 1 in each subsequent HL segment within the transaction set. ot Used S = Shipment 11/19/2007 Page 5 of 23 Revision 2

6 Measurement Segment: MEA - Measurements Level: Detail (Shipment Level) Max. Use: 2 (Both MEA Segments) To specify physical measurements, including dimensions, tolerances, weights and counts. At shipment hierarchical level: - gross weight of shipment- tare weight of shipment MEA*PD*G*1231*LB MEA*PD*T*323*LB MEA Measurement Reference Code M 2/2 PD for physical dimensions MEA Measurement Qualifier M 1/3 G = Gross Weight MEA Measurement Value M R 1/10 Weight T = Tare Weight MEA Unit of Measure Code M 2/2 Unit of Measure MEA Range Minimum MEA Range Maximum MEA Measurement Significance Code MEA Measurement Attribute Code MEA Surface/Layer/Position Code 11/19/2007 Page 6 of 23 Revision 2

7 Carrier Details (Quantity and Weight) Segment: TD1 - Carrier Details (Qty/Weight) Level: Detail (Shipment Hierarchical Level Only) Max. Use: 1 To specify the transportation details relative to commodity, weight and quantity. TD1*PLT71*2 TD Packaging Code M 5/5 Any defined code is acceptable, i.e., PLT71 for pallet; BOX34 for cardboard box; SKD90 for skid. TD Lading Quantity M 0 1/7 umber of packages of the type specified in TD101. TD Commodity Code Qualifier TD Commodity Code TD Lading Description TD Weight Qualifier TD Weight TD Unit of Measure Code 11/19/2007 Page 7 of 23 Revision 2

8 Carrier Details (Routing / Transit) Segment: TD5 - Carrier Detail (Routing Sequence / Transit Time) Level: Detail (Shipment Hierarchical Level Only) Max. Use: 1 To specify the carrier, routing sequence, and provide transit time information. One TD5 is required for each shipment. Do not use more than one TD5. TD5*B*2*CTR*M TD5*B*92*CTR*A***OR*GRR TD Routing Sequence Code M 1/2 B = Carrier is Origin/Delivery Carrier TD Identification Code Qualifier M 1/2 2 SCAC Code 92 Assigned by Buyer TD Identification Code M A 2/17 Carrier's SCAC code TD Transportation Method/Type Code TD Routing TD Ship/Order Status Code M 1/2 M = Motor, A = Air, etc. Valid Codes are listed below OLY Use Codes Included in the Table Below TD Location Qualifier C OR for Origin required if TD504 = A or AE TD Location Identifier C Airport Code (e.g., GRR) TD Transit Direction Code TD Transit Time Direction Qualifier TD Transit Time 11/19/2007 Page 8 of 23 Revision 2

9 Transportation Method Mode The following are valid codes for segment TD5, element TD504: Transportation Method Mode: A - AIR AE - AIR EXPRESS C - COSOLATIO LT - LTL TRUCKLOAD M - MOTOR (COMMO CARRIER) Please note these are the only valid codes accepted by our ERP system. Using any other code will cause the data upload to fail. 11/19/2007 Page 9 of 23 Revision 2

10 Carrier Details (Equipment) Segment: TD3 - Carrier Details (Equipment) Level: Detail (Shipment Hierarchal Level Only) Max. Use: 1 To specify transportation details relating to the equipment used by the carrier. Only one TD3 segment is used per shipment to identify the conveyance number. TD3*TL**5 TD Equipment Description Code TD Equipment Initial TD Equipment umber TD Weight Qualifier TD Weight TD Unit of Measure Code TD Ownership Code M 2/2 M A 1/10 TL = Trailer AF = Air Freight Conveyance umber (i.e., trailer number or air bill number) 11/19/2007 Page 10 of 23 Revision 2

11 Reference umber Segment: Level: Max. Use: 3 Requirement: REF - Reference umbers Detail (Shipment Level) Mandatory (REF*SI Iteration Mandatory) (REF*SI Iteration Mandatory when Sending Serial umbers.) (Mandatory CLD and REF*SE Segments Required in Item Loop since Serial umbers are Sent.) (If sending MULTIPLE Shipper umbers per Master Bill of Lading the REF*SI segment MUST be included in EACH Item Loop (HL***I - Item Level) preceding the first CLD segment and OT in the Shipping Loop (HL***S). REF*BM Mandatory in the Shipping Loop) To specify identifying numbers. Used in the shipment level for: Air bill number - required if air shipment, Bill of Lading number - required if ground shipment. REF*SI* required if air shipment REF*BM* required if ground shipment REF*DK*DK1 REF Reference Identification Qualifier M 2/2 BM = Bill of Lading SI = Shipper umber* REF Reference Identification M A 1/10 REF Description DK = Dock Code 11/19/2007 Page 11 of 23 Revision 2

12 ame Segment: 1 - ame Level: Detail (Shipment Hierarchical Level) Max. Use: 2 (Both ST and SF Segments) To identify a party by type of organization, name and code. The SF Ship From and ST Ship To segments 1*ST**01* *SF**92* Entity Identifier Code M ame Identification Code Qualifier M 2/2 M 1/2 ST = Ship To SF = Ship From For Ship From (SF) Qualifier 92 and 5 Digit Vendor Code Preferred 01 = DUS umber ZZ = User-assigned 92 = Buyer-assigned umber Identification Code M A 2/17 Identifying umber from /19/2007 Page 12 of 23 Revision 2

13 Hierarchal Level Segment: HL - Hierarchal Level Level: Detail - first segment in each HL loop (Item Level) Max. Use: 1 To identify dependencies among and the content of hierarchically related groups of data segments. The HL segment is used to identify levels of detail information using hierarchical structure, such as relating line item data to shipment data. Infor Automotive will only use the shipment and item levels. Cancellation ASs require only the shipment level. HL*2*1*I (item level) HL Hierarchical umber HL Hierarchical Parent umber HL Hierarchical Level Code HL Hierarchical Child Code M A 1/12 M A 1/12 M 1/2 1 for the first HL segment, incremented by 1 in each subsequent HL segment within the transaction set. The number of the parent HL segment. Required for all HL segments at the item level. I = Item 11/19/2007 Page 13 of 23 Revision 2

14 Item Identification Segment: LI - Item Identification Level: Detail (Item Hierarchical Level) Max. Use: 1 To specify basic item identification data. LI**BP*ABC LI**BP* LI Assigned Identification LI Product/Service Qualifier M 2/2 BP = Buyer's Part umber LI Product/Service M A 1/20 Part numbers are up to 20 characters in length only 11/19/2007 Page 14 of 23 Revision 2

15 Item Detail (Shipment) Segment: S1 - Item Detail (shipment) Level: Detail (Item Hierarchal Level) Max. Use: 1 To specify line item detail relative to shipment. Used to show the quantity being shipped, the unit of measure, and cumulative year to date shipments. S1**123*EA*1055 S Assigned Identification S umber of Units Shipped M R 1/10 S Unit of Measure Code M 2/2 Must use the unit of measure received on the material release 830. S Quantity Shipped to Date S Quantity Ordered S Unit of Measure Code S Returnable Container Load Make-Up Code S Line Item Status Code O R 1/9 Cumulative quantity shipped for this model year, including this AS. 11/19/2007 Page 15 of 23 Revision 2

16 Purchase Order Reference Segment: PRF - Purchase Order Reference Level: Detail (Item Hierarchical Level) Max. Use: 1 To provide reference to a specific purchase order. PRF*PO123*** PRF Purchase Order umber M A 1/22 PRF Release umber PRF Change Order Sequence umber PRF Purchase Order Date O DT 8/8 Format is YYYYMMDD PRF Assigned Identification PRF Contract umber 11/19/2007 Page 16 of 23 Revision 2

17 Load Detail Segment: CLD - Load Detail Level: Detail (Item Hierarchical Level) Max. Use: 200 To specify the number of material loads shipped. A CLD segment is required. Serial umbers are to be sent. CLD*123*12***EA CLD umber of Containers CLD umber of Units Shipped CLD Packaging Code CLD Size CLD Unit of Measurement Code M O 1/5 M R 1/10 O 2/2 umber of Containers Shipped Quantity Shipped per Container Must be the unit of measure code received on the /19/2007 Page 17 of 23 Revision 2

18 Reference umbers Segment: REF - Reference umbers Level: Detail (Item Hierarchical Level) Max. Use: 200 To specify identifying numbers. The REF segments are required. Serial umbers are to be sent. REF*SE* REF Reference Identification Qualifier M 2/2 REF Reference Identification M A 1/9 REF Description SE = Serial or Lot umber Identifier LS ot Accepted 11/19/2007 Page 18 of 23 Revision 2

19 Transaction Totals Segment: Level: Requirement: Max. Use: CTT - Transaction Totals Summary Mandatory 1 To transmit a hash total for a specific element in the transaction set. This segment is intended to provide hash totals to validate transaction completeness and correctness. CTT*2*100 CTT umber of Line Items M 0 1/6 Total umber of HL Segments CTT Hash Total M R 1/10 Required hash total of quantity shipped from all S102 segments. CTT Weight CTT Unit of Measure Code CTT Volume CTT Unit of Measure Code CTT Description 11/19/2007 Page 19 of 23 Revision 2

20 Transaction Set Trailer Segment: Level: Requirement: Max. Use: SE - Transaction Set Trailer Summary Mandatory 1 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*25*00001 SE umber of Included Segments M 0 1/6 SE Transaction Set Control umber M A 4/9 Matches ST02 Character Represented As Data Segment Terminating Character (Preference 7E) Tilde ( ~ ) Data Element Separating Character (Preference 2A) Asterisk ( * ) Data Sub-Element Separating Character (Preference 3C) Less Than ( < ) The actual characters will be defined in the ISA segment. These characters are being used for display purposes only. Any valid ASI X.12 defined <control_char> will be used for the data segment terminator (i.e., hex 1C). Do ot Use (Hex 2E (Period.)) as a Data or Hex Character. This will cause adverse effects on the processing of your AS. Any valid ASI X.12 defined <control_char>, <special_char>, or <other_special_char> will be used for the data element and subelement separator (i.e., * and \). 11/19/2007 Page 20 of 23 Revision 2

21 Sample 856 With Serial umbers ISA*00* *00* *ZZ*XXXYYYYY *01* *070321*0933*U*00401* *0*P*<~ GS*SH* * * *0933*202*X*004010~ ST*856* ~ BS*00*976174* *0933~ DTM*011* *0930~ DTM*017* *0930~ HL*1**S~ MEA*PD*G*8120*LB~ MEA*PD*T*4494*LB~ TD1*PLT90*7~ TD5*B*2*MISC*M~ TD3*TL**730035~ REF*SI*976174~ 1*ST**01* ~ 1*SF**01*YYYYY~ HL*2*1*I~ LI**BP*1BM91PR4AC~ S1**160*EA*6797~ PRF*R000084*** ~ CLD*4*40***EA~ REF*SE* ~ REF*SE* ~ REF*SE* ~ REF*SE* ~ HL*3*1*I~ LI**BP*1BM91DX8AC~ S1**120*EA*14200~ PRF*R000084*** ~ CLD*3*40***EA~ REF*SE* ~ REF*SE* ~ REF*SE* ~ CTT*3*280~ SE*32* ~ GE*1*202~ IEA*1* ~ 11/19/2007 Page 21 of 23 Revision 2

22 Sample 856 Master Bill of Lading Individual Shipment umbers with Serial umbers ISA*00* *00* *ZZ*XXXYYYYY *01* *070321*0933*U*00401* *0*P*<~ GS*SH* * * *0933*202*X*004010~ ST*856* ~ BS*00*976174* *0933~ DTM*011* *0930~ DTM*017* *0930~ HL*1**S~ MEA*PD*G*8120*LB~ MEA*PD*T*4494*LB~ TD1*PLT90*7~ TD5*B*2*MISC*M~ TD3*TL**730035~ REF*BM*976174~ 1*ST**01* ~ 1*SF**01*YYYYY~ HL*2*1*I~ LI**BP*1BM91PR4AC~ S1**160*EA*6797~ PRF*R000084*** ~ REF*SI*976174~ CLD*4*40***EA~ REF*SE* ~ REF*SE* ~ REF*SE* ~ REF*SE* ~ HL*3*1*I~ LI**BP*1BM91DX8AC~ S1**120*EA*14200~ PRF*R000084*** ~ REF*SI*976175~ CLD*3*40***EA~ REF*SE* ~ REF*SE* ~ REF*SE* ~ CTT*3*280~ SE*34* ~ GE*1*202~ IEA*1* ~ 11/19/2007 Page 22 of 23 Revision 2

23 Sample 856 Master Bill of Lading Individual Shipment umbers with Serial umbers Different Pack Quantities ISA*00* *00* *ZZ*XXXYYYYY *01* *070321*0933*U*00401* *0*P*<~ GS*SH* * * *0933*202*X*004010~ ST*856* ~ BS*00*976174* *0933~ DTM*011* *0930~ DTM*017* *0930~ HL*1**S~ MEA*PD*G*8120*LB~ MEA*PD*T*4494*LB~ TD1*PLT90*7~ TD5*B*2*MISC*M~ TD3*TL**730035~ REF*BM*976174~ 1*ST**01* ~ 1*SF**01*YYYYY~ HL*2*1*I~ LI**BP*1BM91PR4AC~ S1**160*EA*6797~ PRF*R000084*** ~ REF*SI*976174~ CLD*2*40***EA~ REF*SE* ~ REF*SE* ~ CLD*2*20***EA~ REF*SE* ~ REF*SE* ~ HL*3*1*I~ LI**BP*1BM91DX8AC~ S1**120*EA*14200~ PRF*R000084*** ~ REF*SI*976175~ CLD*2*40***EA~ REF*SE* ~ REF*SE* ~ CLD*1*20***EA~ REF*SE* ~ CTT*3*280~ SE*36* ~ GE*1*202~ IEA*1* ~ 11/19/2007 Page 23 of 23 Revision 2