856v4010Supplier Shipping Notice

Freightliner LLC Ship Notice/Manifest - 856 Ver ANSI ASC X12 4010

856v4010Supplier Shipping Notice.rtf 1

Freightliner LLC 856 Ship Notice / Manifest - AfterMarket, Manufacturing, Warranty

VERSION: ANSI ASC X12 4010 DRAFT

Created: February 25, 2002 02:44 PM Modified: May 28, 2002 09:55 AM



856 Ship Notice/Manifest

Functional Group=SH

This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

Heading: Pos Id Segment Name Req Max

Use Repeat Notes

010 ST Transaction Set Header M 1 020 BSN Beginning Segment for Ship Notice M 1 040 DTM Date/Time Reference M 10

Detail: Pos Id Segment Name Req Max

Use Repeat Notes

LOOP ID - HL 200000 010 HL Hierarchical Level SHIPMENT M 1 020 MEA Measurements M 1 030 TD1 Carrier Details (Quantity and Weight) M 2 040 TD5 Carrier Details (Routing Sequence/Transit Time) M 1 050 TD3 Carrier Details (Equipment) M 1 060 REF Reference Identification M 3

LOOP ID - N1 3 410 N1 Name M 1

LOOP ID - HL 200000 020 HL Hierarchical Level ITEM M 1 030 LIN Item Identification M 1 040 SN1 Item Detail (Shipment) M 1 050 SLN Subline Item Detail O 8 060 PRF Purchase Order Reference M 1 070 REF Reference Identification C 30

Summary: Pos Id Segment Name Req Max

Use Repeat Notes

040 CTT Transaction Totals M 1 N3/040 050 SE Transaction Set Trailer M 1

Note: The purpose of the Ship Notice/Manifest transaction, also known as the "Advanced Ship Notice (ASN)", is to convey the contents of and key reference numbers related to a shipment of material, e.g. Shipment Identification, Carrier PRO, Bill of Lading, Packing Slip, etc., placed in transit to a Freightliner facility. Ship quantities and due dates used in the 856 for parts shipped to manufacturing locations are



dictated by the EDI 866 (Production Sequence) or 862 (Shipping Schedule) transaction received from Freightliner or as authorized by an 830 transaction (Planning Schedule with Release Capability) if the former two transactions have not been implemented with the supplier. An EDI 850 (Purchase Order) transaction received from Freightliner will initiate a shipment of goods to a parts distribution center (PDC) or an authorized Freightliner, Sterling or Western Star Dealer location. The data transmitted in the 856 is used by Freightliner to facilitate the on-line computer receipt of material, shipment tracking, and payment of supplier invoices. The Shipment Identification Number (SID) is the primary reference used by Freightliner in all of these processes. In addition to ship quantities and due dates, other data elements to be included in the 856, e.g. Purchase Order Number, Item Number, Ship-to Location Code/Dealer Code, etc. are conveyed to the supplier via the EDI 866, 862, 830, or 850 transaction as applicable; the 856 should echo back these elements when material is shipped, ideally from an integrated system which precludes the need for data entry. This requires that the data received from Freightliner be stored in the supplier's system and retrieved when the 856 is generated. Freightliner has a fully integrated EDI system. An integrated supplier system ensures that the 856 data transmitted is valid and accurate. If one of the following carriers are not used to ship the goods a trailer number is required in the 856 transaction. BAX GLOBAL, CF AIR FREIGHT, DANZAS, DHL, EMERY WORLDWIDE, FEDEX, FEDEX GROUND, LOOMIS AIR, LOOMIS GROUND, PUROLATOR, SAME DAY RIGHT O'WAY, or UPS GROUND. Contents/Organization An EDI 856 transmission (ISA through IEA segment) can consist of multiple transaction sets, one transaction set (ST through SE segment) per shipment. Each 856 transaction set will consist of three levels (shipment, item, and summary.) Segments in the shipment level convey reference numbers, etc. which pertain to the shipment as a whole while segments at the item level describe a single part number within the shipment. Summary level segments are used to validate the transaction (see CTT and SE segments). Generally, the order in which they are presented within each level is not significant provided that all segments required by Freightliner are included; similarly, Freightliner does not desire the inclusion of segments not required per this section of the EDI User's Manual, i.e. send only the segments, elements, and values requested. The appropriate EDI Coordinator must be advised if one or more segments required by Freightliner cannot be included in the transaction and/or segment(s) not required cannot be excluded; all discrepancies will be addressed on a case by case basis and must be authorized prior to implementation of the transaction. The 856 transaction may be requested of a supplier by two separate EDI implementation groups at Freightliner: Manufacturing and Aftermarket. The Manufacturing EDI Coordinator will test and implement the 856 transaction as it pertains to shipments made from the supplier to Freightliner manufacturing locations, e.g. Portland Truck Plant, Cleveland Truck Plant, etc. The Aftermarket EDI Coordinator will test and implement the 856 transaction as it pertains to shipments made from the supplier to Freightliner parts distribution centers (PDC's), e.g. Chicago Distribution Center, Atlanta Distribution Center, etc, or to a Dealer location. While the contents and organization of these 856 transactions will be very similar, there are some differences which the supplier must be aware of. All requirement variances, i.e. unique segments, data elements, and/or values, between the two versions are presented in the following segment descriptions as they apply. Shipment Identification Number These requirements apply to the Manufacturing and Aftermarket transactions. Adherence to the following numbered items must be demonstrated by providing test data and matching printed documents (fax acceptable) to Freightliner upon request prior to implementation of the transaction set into the production environment. All deviations from these requirements will be subject to a rigorous review and approval process involving all applicable Freightliner manufacturing facilities and corporate departments impacted. 1. The SID used in an EDI 856 transaction (element BSN02) must appear on the corresponding printed Packing Slip (or similar) documents which travel with the physical shipment, preferably in the upper right hand corner of the header portion of the document. The number must be machine printed (handwritten is not acceptable) and appear exactly as it does in the EDI data, i.e. it should not include any extraneous characters, leading zeros, etc. and MUST CONSIST OF NINE OR FEWER ALPHANUMERIC CHARACTERS IN LENGTH. Furthermore, the SID must be a unique number which references an entire physical shipment and MUST NOT BE REUSED WITHIN A ONE YEAR PERIOD. NOTE: If the shipping document contains multiple pages, the SID must appear on each page. For example. if multiple packing slips are generated for a shipment, i.e. one packing slip per part per shipment, the same SID must be machine printed on each one. 2. The SID on the printed shipping document must be preceded by a literal, e.g. "SID:". The literal must also be machine printed. Alternate placement of the literal will be acceptable provided it is intuitively obvious to which number the literal is referring (subject to Freightliner's approval.) 3. The above requirements must also be applied to the corresponding printed invoice document for the shipment (if applicable). If the EDI 810 (Invoice) transaction has been implemented with the supplier, the matching SID must appear in the REF*SI segment (see 810 transaction). In summary, the SID used for a shipment must be consistent in usage and appearance across all corresponding EDI transaction(s) and printed documentation. 4. The SID AND ANY OTHER TRACKING NUMBERS MUST BE PASSED TO THE CARRIER. Transmission Frequency



Generally, a supplier should generate and transmit an 856 transaction to Freightliner as soon as a shipment of material has been placed in transit, or within the hour.. Error Handling Each 856 transaction received by Freightliner will be edited for conformance to requirements as described in this section of the manual. Errors will result and are reported to the Freightliner material planner if segments/elements required are missing or element values are invalid. Here are some common errors found in a Manufacturing/Aftermarket 856: 1. Invalid Item Number. The Item Number in the LIN segment was not found on Freightliner's database; this is a hard error which prevents an in transit record from being created for the item on Freightliner's Purchasing System. 2. Invalid Purchase Order/Line Number. The Purchase Order (P.O.) and/or Line Number in the PRF segment was not found on Freightliner's database or was found but not associated with the supplier, item number in corresponding LIN segment, and/or ship-to location; this is a hard error which prevents an in transit record from being created for the item. NOTE: A unique manufacturing blanket P.O. number is established for each 856 supplier with unique line numbers (within the blanket P.O.) assigned to each sourced item. Each P.O. line can then be opened for one or more manufacturing ship-to locations. 3. Invalid Ship-to Location Code. The Ship-to Location Code in the N1*ST segment is not valid; this is a hard error which prevents an in transit record from being created for all item(s) in the transaction. 4. Duplicate Transmission. A duplicate transmission was received (match is on elements ISA06 (Sender ID) + ISA09 (Transmit Date) + ISA10 (Transmit Time) + ISA13 (Control Number) + BSN02 (SID Number from last transaction in transmission) + CTT01 + CTT02 (CTT01 and CTT02 are hash totals and are summed across all transaction(s) in transmission for this edit); this is a hard error which prevents in transit record(s) from being created for the entire transmission. 5. Duplicate SID/Item. A duplicate item number was received against SID Number in BSN segment (match is on elements BSN02 (SID Number) + REF02 (Bill of Lading Number) + REF02 (Packing Slip Number) + SN102 (Ship Quantity)); this is a hard error which prevents an in-transit record from being created for the item. This error can result within a single 856 (duplicate LIN loops) or across multiple transactions (perhaps a duplicate transmission was sent but new ISA envelope was used causing edit #4 above to pass). MFG NOTE ONLY: A shipped item number must be specified in one LIN loop only within an 856 unless it is packaged in such a way that dictates multiple packing slip numbers and/or quantities be specified. For example, if item A is shipped for quantity = 10 and there is one packing slip number associated with the item (or entire shipment), then specify one LIN loop in the 856 where element SN102 (Ship Quantity) = 10; if two LIN loops are specified where SN102 = 5 in each, then Freightliner's system will reject the second occurrence as a duplicate. 6. SID/Item Already Received. A truck plant/ Parts Distribution Center (PDC)/Dealer receipt record was found for an item number specified in the 856 against SID specified; this is a hard error which prevents an in transit record from being created for the item. This error can result if the 856 is sent too late (truck plant / PDC/Dealer has already received the material and entered computer receipt transactions from the shipment paperwork, i.e. packing list). If one or more of the above errors (among others) are detected in an 856 by Freightliner's system, the supplier will be notified via the use of the 824 transaction which will be sent on the half hour. The supplier will then be advised of the error condition(s) with an expectation that they will not be repeated in subsequent transmissions; corrective action may be requested as well, e.g. retransmit the 856 with corrected values. NOTE: Suppliers must not retransmit 856 transactions which will result (or have resulted) in error(s) without prior authorization from Freightliner; a retransmit will most likely result in duplicate error(s), further compounding the problem.

Example: DS Example ST*856*0220. BSN*00*215413*19990727*0755. DTM*011*19990726*1630. HL*1**S. MEA*PD*G*1*LB. TD1*CTN*1. TD5*B*2*CFWY*M.



TD3*TL**9340. REF*BM*215413. N1*SU*Supplier Name*92*SUN . N1*ST**92*FFYFD. HL*2*1*I. LIN*1*BP*102715. SN1**1*EA. PRF*83271****001. CTT*1*1. SE*17*0220. PDC Example ST`856`0037. BSN`00`864198`19990803`1854. DTM`011`19990803`1850. HL`1``S. MEA`PD`G`5016`LB. TD1`CNT `128. TD1`CTN90`176. TD5`B`2`SWFT`M. TD3`TL``59340. REF`BM`864198. REF`PK`864198. REF`CN`0803991. N1`ST`FREIGHTLINER - ALLIANCE PDC`92`19A. N1`SU`Supplier Name`92`SUPN. HL`2`1Ì. LIN`001`BP`21-20113-000. SN1``80ÈA. PRF`Z695 K462CK````009. HL`3`1Ì. LIN`002`BP`21-20112-001. SN1``128ÈA. PRF`Z695 K462CK````001. HL`4`1Ì. LIN`003`BP`21-20113-000. SN1``48ÈA. PRF`Z695 K462CK````010. HL`5`1Ì. LIN`004`BP`21-20112-002. SN1``48ÈA. PRF`Z695 K462CK````016. CTT`5`304. SE`32`0037. MFG Example ST+856+0020. BSN+00+5253+19990727+2155. DTM+011+19990727+2155. HL+1++S. MEA+PD+G+10800+LB. TD1+RCK58+8. TD5+B+2+PRO +M+++PP+00190. TD3+TL++409. REF+BM+5253. REF+PK+5253. REF+CN+PDX-075374-9. N1+ST+TMP+92+001. N1+SU+MFG Company+92+MFG. HL+2+1+I. LIN+001+BP+A18-29879-004. SN1++8+EA. PRF+A02121++++026. REF+PK+5253. CTT+2+8.



SE+20+0020.



ST Transaction Set Header Pos: 010 Max: 1

Heading - Mandatory Loop: N/A Elements: 2

To indicate the start of a transaction set and to assign a control number

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a Transaction Set

Note: Will always be '856'. Code Name _ 856 Ship Notice/Manifest

M ID 3/3

ST02 329 Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

M AN 4/9



BSN Beginning Segment for Ship Notice Pos: 020 Max: 1


To transmit identifying numbers, dates, and other basic data relating to the transaction set

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max BSN01 353 Transaction Set Purpose Code

Description: Code identifying purpose of transaction set

Note: Will always be '00'. Code Name _ 00 Original

Note:

M ID 2/2

BSN02 396 Shipment Identification Description: A unique control number assigned by the original shipper to identify a specific shipment

Note: Unique supplier-assigned number (SID)THAT IS NOT REPEATED WITHIN A ONE YEAR PERIOD.

M AN 1/10

BSN03 373 Date Description: Date expressed as CCYYMMDD

M DT 8/8

BSN04 337 Time Description: HHMM

M TM 4/4



DTM Date/Time Reference Pos: 040 Max: 10


To specify pertinent dates and times

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max DTM01 374 Date/Time Qualifier

Description: Code specifying type of date or time, or both date and time

Note: DTM01 will always be '011'. Code Name _ 011 Shipped

M ID 3/3

DTM02 373 Date Description: Date expressed as CCYYMMDD

M DT 8/8

DTM03 337 Time Description: HHMM

M TM 4/4



HL Hierarchical Level SHIPMENT Pos: 010 Max: 1

Detail - Mandatory Loop: HL Elements: 2

To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max HL01 628 Hierarchical ID Number

Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

Note: HL01 will always be '1'.

M AN 1/1

HL03 735 Hierarchical Level Code Description: Code defining the characteristic of a level in a hierarchical structure Code Name _ S Shipment

M ID 1/1



MEA Measurements Pos: 020 Max: 1


To specify physical measurements or counts, including dimensions, tolerances, variances, and weights(See Figures Appendix for example of use of C001)

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max MEA01 737 Measurement Reference ID Code

Description: Code identifying the broad category to which a measurement applies

Note: MEA01 will always be 'PD'. Code Name _ PD Physical Dimensions

M ID 2/2

MEA02 738 Measurement Qualifier Description: Code identifying a specific product or process characteristic to which a measurement applies

Note: MEA02 will always be 'G'. Code Name _ G Gross Weight

M ID 1/1

MEA03 739 Measurement Value Description: The value of the measurement

M R 1/6

MEA04 C001 Composite Unit of Measure Description: To identify a composite unit of measure

Note: MEA04 will always be 'LB'.

M Comp

355 Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Code Name _ LB Pound

M ID 2/2

Note: Shipment Level



TD1 Carrier Details (Quantity and Weight) Pos: 030 Max: 2


To specify the transportation details relative to commodity, weight, and quantity

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max TD101 103 Packaging Code

Description: 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

Note: Use Packaging Code of the shipping unit (e.g. ten boxes on one pallet is

specified as one pallet).

All valid X12 codes are used.

Some typical codes from ANSI ASC X12 Data Element Dictionary are:

"BAG13" = Bag;

"BBL52" = Barrel;

"BIN51" = Wire Mesh Bin;

"BIN52" = Steel Bin;

"BOX25" = Cardboard Box;

"COL52" = Steel Coil;

"CRT71" = Crate;

"CTN25" = Cardboard Carton;

"LSE71" = Loose;

"MIX90" = Mixed;

"PLT71" = Pallet;

"RCK58" = Rack;

"SKD71" = Skid;

M AN 3/5

TD102 80 Lading Quantity Description: Number of units (pieces) of the lading commodity

M N0 1/7




TD5 Carrier Details (Routing Sequence/Transit Time)

Pos: 040 Max: 1


To specify the carrier and sequence of routing and provide transit time information

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max TD501 133 Routing Sequence Code

Description: Code describing the relationship of a carrier to a specific shipment movement

Note: TD501 will always be 'B'. Code Name _ B Origin/Delivery Carrier (Any Mode)

M ID 1/1

TD502 66 Identification Code Qualifier Description: Code designating the system/method of code structure used for Identification Code (67)

Note: TD502 will always be '2'. Code Name _ 2 Standard Carrier Alpha Code (SCAC)

M ID 1/1

TD503 67 Identification Code Description: Code identifying a party or other code

M AN 4/4

TD504 91 Transportation Method/Type Code Description: Code specifying the method or type of transportation for the shipment Code Name _ A Air M Motor (Common Carrier) Q Conventional Ocean R Rail

M ID 1/1




TD3 Carrier Details (Equipment) Pos: 050 Max: 1


To specify transportation details relating to the equipment used by the carrier

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max TD301 40 Equipment Description Code

Description: Code identifying type of equipment used for shipment

Note: TD301 will always be 'TL'. Code Name _ TL Trailer (not otherwise specified)

M ID 2/2

TD303 207 Equipment Number Description: Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

M AN 1/10




REF Reference Identification Pos: 060 Max: 3


To specify identifying information

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference Identification Code Name _ BM Bill of Lading Number CN Carrier's Reference Number (PRO/Invoice) D9 Claim Number PK Packing List Number

M ID 2/2

REF02 127 Reference Identification Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

C AN 1/30

Note: 1. Bill of Lading #, max. size: 16 2. Carrier's PRO #, max. size:30 3. Packing List #, max. size: 10 4. Claim No. , required when parts are being returned for Warranty inspection, max. size: 7



N1 Name Pos: 410 Max: 1

Detail - Mandatory Loop: N1 Elements: 4

To identify a party by type of organization, name, and code

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max N101 98 Entity Identifier Code

Description: Code identifying an organizational entity, a physical location, property or an individual Code Name _ ST Ship To SU Supplier/Manufacturer

M ID 2/2

N102 93 Name Description: Free-form name

C AN 1/35

N103 66 Identification Code Qualifier Description: Code designating the system/method of code structure used for Identification Code (67) Code Name _ 92 Assigned by Buyer or Buyer's Agent

M ID 2/2

N104 67 Identification Code Description: Code identifying a party or other code

Note: When N101 = 'SU' then N104 must contain Freightliner's assigned vendor code for the supplier.

When N101 = 'ST' then N104 must contain Freightliner's assigned Ship To code (See Appendix "C"). When N104 is a dealer code it will be a minimum of 5 characters and a maximum of 5 characters.

When N101 = 'SF' then N104 must contain the Sales Outlet code of the customer returning parts claimed for Warranty.

M AN 2/5




HL Hierarchical Level ITEM Pos: 020 Max: 1


To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max HL01 628 Hierarchical ID Number

Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

Note: HL01 must start with 1 and increment by 1 for each subsequent HL loop.

M AN 1/3

HL03 735 Hierarchical Level Code Description: Code defining the characteristic of a level in a hierarchical structure Code Name _ I Item

M ID 1/1



LIN Item Identification Pos: 030 Max: 1


To specify basic item identification data

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max LIN01 350 Assigned Identification

Description: Alphanumeric characters assigned for differentiation within a transaction set

Note: Values must start with 1 and increment by 1 for each subsequent LIN segment.

M AN 1/3

LIN02 235 Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Note: LIN02 will always be 'BP'. Code Name _ BP Buyer's Part Number

M ID 2/2

LIN03 234 Product/Service ID Description: Identifying number for a product or service

M AN 1/25



SN1 Item Detail (Shipment) Pos: 040 Max: 1


To specify line-item detail relative to shipment

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max SN102 382 Number of Units Shipped

Description: Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

Note: use whole numbers

M R 1/7

SN103 355 Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

Note: This should be the same Unit of Measure provided on the corresponding releasing document (830, 850, 862, 866).

See Appendix E for valid codes

M ID 2/2



SLN Subline Item Detail Pos: 050 Max: 8

Detail - Optional Loop: HL Elements: 6

To specify product subline detail item data

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max SLN01 350 Assigned Identification

Description: Alphanumeric characters assigned for differentiation within a transaction set

M AN 3/3

SLN03 662 Relationship Code Description: Code indicating the relationship between entities Code Name _ I Included

M ID 1/1

SLN04 380 Quantity Description: Numeric value of quantity

M R 1/7

SLN05 C001 Composite Unit of Measure Description: To identify a composite unit of measure

M Comp

355 Unit or Basis for Measurement Code Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Code Name _ EA Each

M ID 2/2

SLN09 235 Product/Service ID Qualifier Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) Code Name _ SN Serial Number

M ID 2/2

SLN10 234 Product/Service ID Description: Identifying number for a product or service

M AN 1/25

Note: THIS SEGMENT USED BY PDC ONLY, FOR SERIALIZED CORES ONLY. LIN11 - LIN28 USED FOR ADDITIONAL SERIALIZED CORES.



PRF Purchase Order Reference Pos: 060 Max: 1


To provide reference to a specific purchase order

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max PRF01 324 Purchase Order Number

Description: Identifying number for Purchase Order assigned by the orderer/purchaser

Note: Use PO number provided in releasing documents (e.g., 830, 850, 862, 866). MAFG has a min/max of 6. PDC has a min/max of 11.

M AN 6/20

PRF05 350 PO Line number Description: Alphanumeric characters assigned for differentiation within a transaction set

Note: MAFG uses this element for

PO LINE #

M AN 3/3



REF Reference Identification Pos: 070 Max: 30

Detail - Conditional Loop: HL Elements: 2

To specify identifying information

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference Identification Code Name _ LS Bar-Coded Serial Number PK Packing List Number SE Serial Number VT Motor Vehicle ID Number

M ID 2/2

REF02 127 Reference Identification Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

C AN 1/15

Note: 1. One REF*SE segment must be included for each major component part shipped, e.g. engine, transmission, etc.; for example, if SN102 (Ship Quantity) = 10, then there should be ten REF*SE segments included within the same LIN loop, each specifying a unique serial number. 2. One or more REF*VT segments must be included which indicate all vehicle serial number(s) for which the part specified in the previous LIN segment is to be assembled onto/within (typically one REF*VT per occurrence of the part). The serial numbers to use should come directly from the 866 transaction data received from Freightliner which initiated the shipment. The REF*VT segment is used to flag the part as shipped in Freightliner's Line Sequence System for the vehicle serial identified, therefore causing 866 data to not be sent again to the supplier for the vehicle/part number, even in the event of a scheduling change (vehicle's build date is moved out into the future after shipment of material pegged to the vehicle has been made). 3. REF*PK is used at this level only if multiple PK slips are sent with shipment. 4. This segment is only used if the trading partner receives an 866, an 830 for a major component, or has multiple packing slip numbers..



CTT Transaction Totals Pos: 040 Max: 1

Summary - Mandatory Loop: N/A Elements: 2

To transmit a hash total for a specific element in the transaction set

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max CTT01 354 Number of Line Items

Description: Total number of line items in the transaction set

Note: Total number of HL segments

M N0 1/6

CTT02 347 Hash Total

Note: Hash total of quantity shipped (SN102)

M R 1/10



SE Transaction Set Trailer Pos: 050 Max: 1

Summary - Mandatory Loop: N/A Elements: 2

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max SE01 96 Number of Included Segments

Description: Total number of segments included in a transaction set including ST and SE segments

M N0 1/10

SE02 329 Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

M AN 4/9

Documents

856v4010Supplier Shipping Notice