ECTF EDIPro Standard
EDI 856 Ship Notice/Manifest (ASC X12 Version 4 Release 1)
This document contains an outline of common business issues for consideration when implementing the EDI 856 Ship Notice/Manifest for ASC X12 Version 4010. It is the intent of this document to act as an addendum to the ASC X12 EDI Standards documentation.
856 Ship Notice/Manifest
Included in this document:
Page
Section 1: Business Issues......................................................... 2...........................................................................................................
Section 2: Segment Notes...................................................... 5
Section 3: Example Notes..................................................... 33
Section 1
856 Ship Notice/Manifest
Business Issues
This section contains business discussions about the use of the 856 Ship Notice/Manifest. These discussions will assist in determining application changes and business process changes that may be necessary within a company.
Page
Hierarchical Level....................................................................... 3
Use of Shipping Container Code (SCC-14) and Quantity Unit of Measure.................................................................................................................................................. 3
Use of Text Fields......................................................................... 3
Special Carrier/Shipments....................................................... 3
Identification of Business Location........................................ 4
Business Issues
The following business issues should be considered when implementing the 856 Ship Notice/Manifest:
Hierarchical structures define the placement of levels within a transaction set. Each structure sets parameters on the parent/child relationship of the hierarchical levels. The Ship Notice/Manifest supports many different hierarchical levels of detail including shipment, tare, pack, order, and item data. The required level of detail should be discussed and agreed to by both trading partners. The subsequent paragraphs outline the general information provided at each hierarchical level of the Ship Notice/Manifest.
Shipment
The information contained in this level of the Ship Notice/Manifest pertains to the entire shipment. This level will always occur as the first hierarchical level.
Tare (SSCC-18)
This hierarchical level is used to identify a transport package, which may be a pallet, master container, or other physical unit of load. The SSCC-18 (commonly referred to as the license plate) is the method of identification for a transport package.
The master container is used for overpack situations when several smaller items are combined into one master container and will be labeled with an SSCC-18. It is possible for one or more master containers to be packaged within one transport package (multiple boxes on one pallet).
Pack (SCC-14)
This hierarchical level is used to identify the pack level for an item. As defined by ASC X12, pack levels imply that items in the carton are the same U.P.C. number. The SCC-14 is used to identify these cartons.
Order
This hierarchical level identifies data related to the original purchase order.
Item (U.P.C.-12 or SCC-14)
The U.P.C.-12 or SCC-14 identifying the product and quantity shipped is included at this hierarchical level.
Detailed diagrams and examples showing the different hierarchical looping structures are provided in Section 3: Example Transactions of this document.
This SCC-14 format includes the designation of a specific package level which is associated with a discrete quantity. The quantity unit of measure (SN103 data element) should not be used to calculate the net quantity shipped of an item when the item is identified by a SCC-14. It is recommended that a value of “EA” be used as the quantity unit of measure for items identified with a SCC-14.
The PID segment promotes the inclusion of text data. When using this segment it is recommended that they be restricted to free form text and that any other use for specific data which could be mapped, be discouraged.
It should be noted that the use of text data in EDI transactions should be limited to those specific agreements between trading partners. Anytime text data is passed within a transaction, the receiving partner may have to queue the transaction into an exception process for review. In this case the transaction cannot be automatically processed.
To permit the seller to communicate special shipping conditions such as Same Day, Air Freight, etc., or to allow the specification of a specific carrier, the use of the TD5 segment is recommended.
When specifying a specific carrier it is further recommended that the Standard Carrier Alpha Code (SCAC) be used if one has been assigned to the carrier. See the TD5 segment for further discussion
It should be noted that the TD5 segment may be included at the header portion of the transaction, thereby applying to the entire order, or at the line item level of the order, applying only to the specified line.
DUNS + 4 should be used as the primary and preferred method of identifying business locations. Organizations not using the “+ 4” suffix of the DUNS number should insert four zeros in its place.
Section 2
856 Ship Notice/Manifest
Segment Details
This section contains business discussions about the segments used in the 856 Ship Notice/Manifest. These discussions will assist in determining application changes and business process changes that may be necessary within a company.
856.................................................................................................. 6
ST..................................................................................................... 7
BSN................................................................................................. 8
HL.................................................................................................... 9
LIN................................................................................................ 10
SN1............................................................................................... 12
SLN................................................................................................ 13
PRF................................................................................................ 16
PO4.............................................................................................. 17
PID................................................................................................ 18
TD1............................................................................................... 19
TD5............................................................................................... 20
TD3............................................................................................... 22
REF................................................................................................ 23
MAN............................................................................................ 24
DTM.............................................................................................. 25
FOB............................................................................................... 26
PAL............................................................................................... 27
N1................................................................................................. 28
N3................................................................................................. 29
N4................................................................................................. 30
CTT............................................................................................... 31
SE.................................................................................................. 32
|
||
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.
|
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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - HL |
|
|
200000 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
010 |
HL |
Hierarchical Level |
M |
1 |
|
C2/010 |
|
|
|
|
|
|
|
|
|
|
|
|
020 |
LIN |
Item Identification |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
030 |
SN1 |
Item Detail (Shipment) |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
040 |
SLN |
Subline Item Detail |
O |
1000 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
050 |
PRF |
Purchase Order Reference |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
060 |
PO4 |
Item Physical Details |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
070 |
PID |
Product/Item Description |
O |
200 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
110 |
TD1 |
Carrier Details (Quantity and Weight) |
O |
20 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
120 |
TD5 |
Carrier Details (Routing Sequence/Transit Time) |
O |
12 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
130 |
TD3 |
Carrier Details (Equipment) |
O |
12 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
150 |
REF |
Reference Identification |
O |
>1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
190 |
MAN |
Marks and Numbers |
O |
>1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
200 |
DTM |
Date/Time Reference |
O |
10 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
210 |
FOB |
F.O.B. Related Instructions |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
215 |
PAL |
Pallet Information |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - N1 |
|
|
200 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
220 |
N1 |
Name |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
240 |
N3 |
Address Information |
O |
2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
250 |
N4 |
Geographic Location |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
010 |
CTT |
Transaction Totals |
O |
1 |
|
N3/010 |
|
|
|
|
|
|
|
|
|
|
|
|
020 |
SE |
Transaction Set Trailer |
M |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
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
Example:
ST*856*0001^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
ST01 |
143 |
Transaction Set Identifier Code Description: Code uniquely identifying a Transaction Set 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 |
|
|
Beginning Segment for Ship Notice |
Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 5 |
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Example:
BSN*00*01234678*20010731*1450*0002^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
BSN01 |
353 |
Transaction Set Purpose Code Description: Code identifying purpose of transaction set Code NAME
_ 00 Original |
M |
ID |
2/2 |
|
|
|
BSN02 |
396 |
Shipment Identification Description: A unique control number assigned by the
original shipper to identify a specific shipment |
M |
AN |
2/30 |
|
|
|
BSN03 |
373 |
Date Description: Date expressed as CCYYMMDD |
M |
DT |
8/8 |
|
|
|
BSN04 |
337 |
Time Description: Time expressed in 24-hour clock time as follows:
HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M =
minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds;
decimal seconds are expressed as follows: D = tenths (0-9) and DD =
hundredths (00-99) |
M |
TM |
4/8 |
|
|
|
BSN05 |
1005 |
Hierarchical Structure Code Description: Code indicating the hierarchical application
structure of a transaction set that utilizes the HL segment to define the
structure of the transaction set Code NAME _ 0001 Shipment,Packaging, Item 0002 Shipment,Item, Packaging 0003 Shipment,Order, Item 0004 Shipment,Item |
O |
ID |
4/4 |
|
|
Hierarchical Level |
Pos: 010 Max: 1 Detail - Mandatory Loop: HL Elements: 3 |
To identify dependencies among and the content of hierarchically related groups of data segments
Example:
HL*1**S^
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 |
M |
AN |
1/12 |
|
|
|
HL02 |
734 |
Hierarchical Parent ID Number Description: Identification number of the next higher
hierarchical data segment that the data segment being described is
subordinate to ECTF Notes:
The HL02 is not required within the first occurance of the HL segment. |
O |
AN |
1/12 |
|
|
|
HL03 |
735 |
Hierarchical Level Code Description: Code defining the characteristic of a level in
a hierarchical structure Code NAME
_ I Item O Order P Pack S Shipment T Shipping Tare |
M |
ID |
1/2 |
|
|
Item Identification |
Pos: 020 Max: 1 Detail - Optional Loop: HL Elements: 13 |
To specify basic item identification data
ECTF Notes:
LIN02 through LIN13 provide for multiple product/service IDs for each item. If only one product/service ID is provided, LIN02 and LIN03 are used. LIN04 and LIN05 would be used for a second product/service ID, etc. Multiple product/service ID's can be presented in any sequence.
Example:
LIN*1*VC*P-8750*UP*09999982011*BP*CC-14*RK*BZ0R6A12*CH*USA^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
LIN01 |
350 |
Assigned Identification Description: Alphanumeric characters assigned for
differentiation within a transaction set |
O |
AN |
1/20 |
|
|
|
LIN02 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) Code NAME
_ BP Buyer's Part Number CB Buyer's Catalog Number CH Country of Origin Code EN European Article Number (EAN) (2-5-5-1) HD International Harmonized Commodity Code LT Lot Number RK Rack Number SN Serial Number U2 U.P.C. Shipping Container Code (1-2-5-5) UD U.P.C./EAN Consumer Package Code (2-5-5) UP U.P.C. Consumer
Package Code (1-5-5-1) UI U.P.C. Consumer Package Code (1-5-5) UK U.P.C./EAN Shipping Container Code
(1-2-5-5-1) VC Vendor's (Seller's) Catalog Number VP Vendor's (Seller's) Part Number |
M |
ID |
2/2 |
|
|
|
LIN03 |
234 |
Product/Service ID Description: Identifying number for a product or service |
M |
AN |
1/48 |
|
|
|
LIN04 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
LIN05 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
LIN06 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
LIN07 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
LIN08 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
LIN09 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
LIN10 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
LIN11 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
LIN12 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
LIN13 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
Item Detail (Shipment) |
Pos: 030 Max: 1 Detail - Optional Loop: HL Elements: 2 |
To specify line-item detail relative to shipment
ECTF Notes:
This segment is used to specify item quantity information.
Example:
SN1*0001*10000*PC^
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 |
M |
R |
1/10 |
|
|
|
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 ECTF Notes:
It is recommended that a value of "EA" be used as the
quantity unit of measure for items identified with a SCC-14. Code NAME _ BG Bag BK Book CA Case CG Card CT Carton CX Coil EA Each FT Foot HU Hundred KG Kilogram KT Kit LB Pound MR Meter PC Piece PK Package PL Pallet/Unit Load RD Rod (length) - 5.5 Yards RE Reel RL Roll SH Sheet SO Spool TH Thousand |
M |
ID |
2/2 |
|
|
Subline Item Detail |
Pos: 040 Max: 1000 Detail - Optional Loop: HL Elements: 16 |
To specify product subline detail item data
ECTF Notes:
Segment SLN is to be used if the item is shipped in sub assemblies to identify the sub assemblies to the customer. SLN09 through SLN20 provide for multiple product/service IDs for each item. If only one product/service ID is provided, SLN09 and SLN10 are used. SLN11 and SLN12 would be used for a second product/service ID, etc. Multiple product/service ID's can be presented in any sequence.
Example:
SLN*1.1**I*10000*PC****VC*P-875OS*UP*099999820011^
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 |
1/20 |
|
|
|
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 |
C |
R |
1/15 |
|
|
|
SLN05 |
C001 |
Composite Unit of Measure Description: To identify a composite unit of measure(See
Figures Appendix for examples of use) |
C |
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
_ BG Bag BK Book CA Case CG Card CT Carton CX Coil EA Each FT Foot HU Hundred KG Kilogram KT Kit LB Pound MR Meter PC Piece PK Package PL Pallet/Unit Load RE Reel RL Roll SH Sheet SO Spool TH Thousand |
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
_ BP Buyer's Part Number CB Buyer's Catalog Number CH Country of Origin Code EN European Article Number (EAN) (2-5-5-1) HD International Harmonized Commodity Code LT Lot Number RK Rack Number SN Serial Number U2 U.P.C. Shipping Container Code (1-2-5-5) UD U.P.C./EAN Consumer Package Code (2-5-5) UI U.P.C. Consumer Package Code (1-5-5) UP U.P.C. Consumer
Package Code (1-5-5-1) UK U.P.C./EAN Shipping Container Code
(1-2-5-5-1) VC Vendor's (Seller's) Catalog Number VP Vendor's (Seller's) Part Number |
C |
ID |
2/2 |
|
|
|
SLN10 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
SLN11 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
SLN12 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
SLN13 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
SLN14 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
SLN15 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
SLN16 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
SLN17 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
SLN18 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
|
SLN19 |
235 |
Product/Service ID Qualifier Description: Code identifying the type/source of the
descriptive number used in Product/Service ID (234) |
C |
ID |
2/2 |
|
|
|
SLN20 |
234 |
Product/Service ID Description: Identifying number for a product or service |
C |
AN |
1/48 |
|
|
Purchase Order Reference |
Pos: 050 Max: 1 Detail - Optional Loop: HL Elements: 3 |
To provide reference to a specific purchase order
Example:
PRF*092123456***20010814^
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 |
M |
AN |
1/22 |
|
|
|
PRF02 |
328 |
Release Number Description: Number identifying a release against a Purchase
Order previously placed by the parties involved in the transaction |
O |
AN |
1/30 |
|
|
|
PRF04 |
373 |
Date Description: Date expressed as CCYYMMDD |
O |
DT |
8/8 |
|
|
Item Physical Details |
Pos: 060 Max: 1 Detail - Optional Loop: HL Elements: 4 |
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Example:
PO4*1*1*PC^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
PO401 |
356 |
Pack Description: The number of inner containers, or number of
eaches if there are no inner containers, per outer container |
O |
N0 |
1/6 |
|
|
|
PO402 |
357 |
Size Description: Size of supplier units in pack |
C |
R |
1/8 |
|
|
|
PO403 |
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
_ BG Bag BK Book CA Case CG Card CT Carton CX Coil EA Each FT Foot HU Hundred KG Kilogram KT Kit LB Pound MR Meter PC Piece PK Package PL Pallet/Unit Load RE Reel RL Roll SH Sheet SO Spool TH Thousand |
C |
ID |
2/2 |
|
|
|
PO414 |
810 |
Inner Pack Description: The number of eaches per inner container |
O |
N0 |
1/6 |
|
|
Product/Item Description |
Pos: 070 Max: 200 Detail - Optional Loop: HL Elements: 2 |
To describe a product or process in coded or free-form format
Example:
PID*F****Product Description^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
PID01 |
349 |
Item Description Type Description: Code indicating the format of a description Code NAME
_ F Free-form |
M |
ID |
1/1 |
|
|
|
PID05 |
352 |
Description Description: A free-form description to clarify the related
data elements and their content |
C |
AN |
1/80 |
|
|
Carrier Details (Quantity and Weight) |
Pos: 110 Max: 20 Detail - Optional Loop: HL Elements: 5 |
To specify the transportation details relative to commodity, weight, and quantity
Example:
TD1*CNT90*6****G*50*LB^
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 Code NAME
_ BDL Bundle BOX Box CNT Container PLT Pallet 90 Standard |
O |
AN |
3/5 |
|
|
|
TD102 |
80 |
Lading Quantity Description: Number of units (pieces) of the lading
commodity |
C |
N0 |
1/7 |
|
|
|
TD106 |
187 |
Weight Qualifier Description: Code defining the type of weight Code NAME _ G Gross Weight |
O |
ID |
1/2 |
|
|
|
TD107 |
81 |
Weight Description: Numeric value of weight |
C |
R |
1/10 |
|
|
|
TD108 |
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
_ KG Kilogram LB Pound |
C |
ID |
2/2 |
|
|
Carrier Details (Routing Sequence/Transit Time) |
Pos: 120 Max: 12 Detail - Optional Loop: HL Elements: 5 |
To specify the carrier and sequence of routing and provide transit time information
ECTF Notes:
Preferred Carrier
To specify the carrier, a TD502 element should be included having a qualifier of "2", followed by a TD503 element containing a valid Standard Carrier Alpha Code (SCAC) describing the carrier. The SCAC table is a certified list of four character codes associated with specific carriers. This list is published by the National Motor Freight Traffic Association. Examples of SCAC codes are listed below.
Code Description
CFWY Consolidated Freightways (Type - LTL)
FEPL Federal Express (Type - Air)
OVNT Overnight (Type - LTL)
Note: ID qualifiers 91 and 92 require prior trading partner agreement and should be avoided.
Shipment Method
A TD504 element should be included having a valid qualifier describing the method of shipment.
Service Level
TD512 element should be included having a valid qualifier describing the service level.
Example:
TD5**2*AAAA*M*AAA FREIGHT CO.*******09^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
TD502 |
66 |
Identification Code Qualifier Description: Code designating the system/method of code
structure used for Identification Code (67) Code NAME
_ 2 Standard Carrier Alpha Code (SCAC) 91 Assigned by Seller or Seller's Agent 92 Assigned by Buyer or Buyer's Agent |
C |
ID |
1/2 |
|
|
|
TD503 |
67 |
Identification Code Description: Code identifying a party or other code |
C |
AN |
2/80 |
|
|
|
TD504 |
91 |
Transportation Method/Type Code Description: Code specifying the method or type of transportation
for the shipment Code NAME
_ A Air C Consolidation D Parcel Post H Customer Pickup L Contract Carrier M Motor (Common Carrier) R Rail T Best Way (Shippers Option) U Private Parcel Service AE Air Express BU Bus LT Less Than Trailer Load (LTL) SR Supplier Truck |
C |
ID |
1/2 |
|
|
|
TD505 |
387 |
Routing Description: Free-form description of the routing or
requested routing for shipment, or the originating carrier's identity |
C |
AN |
1/35 |
|
|
|
TD512 |
284 |
Service Level Code Description: Code indicating the level of transportation
service or the billing service offered by the transportation carrier Code NAME _ 09 Premium Surface CX Express Service ND Next Day Air ON Overnight PA Primary Service Area - Next Day by 10:30
A.M. PR Primary Service Area - Next Day by 5:00
P.M. PS Primary Service Area - Second Day by
Noon SC Second Day Air SD Saturday SE Second Day SG Standard Ground |
C |
ID |
2/2 |
|
|
Carrier Details (Equipment) |
Pos: 130 Max: 12 Detail - Optional Loop: HL Elements: 4 |
To specify transportation details relating to the equipment used by the carrier
Example:
TD3*TL*CFWY*123456^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
TD301 |
40 |
Equipment Description Code Description: Code identifying type of equipment used for
shipment Code NAME
_ AC Closed Container CN Container FT Flat Bed Trailer LU Load/unload Device on Equipment RR Rail Car TL Trailer (not otherwise specified) |
C |
ID |
2/2 |
|
|
|
TD302 |
206 |
Equipment Initial Description: Prefix or alphabetic part of an equipment
unit's identifying number |
O |
AN |
1/4 |
|
|
|
TD303 |
207 |
Equipment Number Description: Sequencing or serial part of an equipment
unit's identifying number (pure numeric form for equipment number is
preferred) |
C |
AN |
1/10 |
|
|
|
TD309 |
225 |
Seal Number Description: Unique number on seal used to close a shipment |
O |
AN |
2/15 |
|
|
Reference Identification |
Pos: 150 Max: >1 Detail - Optional Loop: HL Elements: 2 |
To specify identifying information
Example:
REF*BM*C000006304^
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 BT Batch Number CN Carrier's Reference Number (PRO/Invoice) DT Downstream Shipper Contract Number MB Master Bill of Lading PK Packing List Number R1 Current Revision Number SI Shipper's Identifying Number for
Shipment (SID) |
M |
ID |
2/3 |
|
|
|
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 |
|
|
Marks and Numbers |
Pos: 190 Max: >1 Detail - Optional Loop: HL Elements: 2 |
To indicate identifying marks and numbers for shipping containers
ECTF Notes:
This segment is commonly included when information is to be passed that is displayed on shipping papers or package labels. Use of this segment to pass other data is discouraged.
The UCC/EAN-128 Serial Shipping Container Code (SSCC-18) uniquely identifies the shipping container and its contents. It is sometimes generically called a shipping container license plate.
Example:
MAN*GM*00006328106201689152^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
MAN01 |
88 |
Marks and Numbers Qualifier Description: Code specifying the application or source of
Marks and Numbers (87) Code NAME _ W Pallet Number GM SSCC-18 and Application Identifier MC Master Carton Number |
M |
ID |
1/2 |
|
|
|
MAN02 |
87 |
Marks and Numbers Description: Marks and numbers used to identify a shipment
or parts of a shipment |
M |
AN |
1/48 |
|
|
Date/Time Reference |
Pos: 200 Max: 10 Detail - Optional Loop: HL Elements: 2 |
To specify pertinent dates and times
Example:
DTM*011*20000122^
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 Code NAME _ 011 Shipped |
M |
ID |
3/3 |
|
|
|
DTM02 |
373 |
Date Description: Date expressed as CCYYMMDD |
C |
DT |
8/8 |
|
|
F.O.B. Related Instructions |
Pos: 210 Max: 1 Detail - Optional Loop: HL Elements: 1 |
To specify transportation instructions relating to shipment
Example:
FOB*PC^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
FOB01 |
146 |
Shipment Method of Payment Description: Code identifying payment terms for
transportation charges Code NAME
_ CC Collect PC Prepaid but Charged to Customer PP Prepaid (by Seller) PU Pickup |
M |
ID |
2/2 |
|
|
Pallet Information |
Pos: 215 Max: 1 Detail - Optional Loop: HL Elements: 6 |
To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet
Example:
PAL*4***50***6*5*6*FT^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
PAL01 |
883 |
Pallet Type Code Description: Code indicating the type of pallet Code NAME _ 4 Standard |
O |
ID |
1/2 |
|
|
|
PAL04 |
356 |
Pack Description: The number of inner containers, or number of
eaches if there are no inner containers, per outer container |
O |
N0 |
1/6 |
|
|
|
PAL07 |
82 |
Length Description: Largest horizontal dimension of an object
measured when the object is in the upright position |
C |
R |
1/8 |
|
|
|
PAL08 |
189 |
Width Description: Shorter measurement of the two horizontal
dimensions measured with the object in the upright position |
C |
R |
1/8 |
|
|
|
PAL09 |
65 |
Height Description: Vertical dimension of an object measured when
the object is in the upright position |
C |
R |
1/8 |
|
|
|
PAL10 |
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
_ FT Foot MR Meter |
C |
ID |
2/2 |
|
|
Name |
Pos: 220 Max: 1 Detail - Optional Loop: N1 Elements: 4 |
To identify a party by type of organization, name, and code
ECTF Notes:
DUNS+4 should be considered the primary and preferred method of identifying a location. ID qualifiers 91 and 92 require prior trading partner agreement and should be avoided.
Example:
N1*ST**1*056201585^
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
_ BS Bill and Ship To BT Bill-to-Party BY Buying Party (Purchaser) EN End User SE Selling Party SF Ship From ST Ship To |
M |
ID |
2/3 |
|
|
|
N102 |
93 |
Name Description: Free-form name |
C |
AN |
1/60 |
|
|
|
N103 |
66 |
Identification Code Qualifier Description: Code designating the system/method of code
structure used for Identification Code (67) Code NAME
_ 1 D-U-N-S Number,Dun & Bradstreet 9 D-U-N-S+4, D-U-N-S Number with Four
Character Suffix 91 Assigned by Seller or Seller's Agent 92 Assigned by Buyer or Buyer's Agent |
C |
ID |
1/2 |
|
|
|
N104 |
67 |
Identification Code Description: Code identifying a party or other code |
C |
AN |
2/80 |
|
|
Address Information |
Pos: 240 Max: 2 Detail - Optional Loop: N1 Elements: 2 |
To specify the location of the named party
Example:
N3*620 Peachtree Street^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
N301 |
166 |
Address Information Description: Address information |
M |
AN |
1/55 |
|
|
|
N302 |
166 |
Address Information Description: Address information |
O |
AN |
1/55 |
|
|
Geographic Location |
Pos: 250 Max: 1 Detail - Optional Loop: N1 Elements: 4 |
To specify the geographic place of the named party
Example:
N4*Atlanta*GA*30084*USA^
Element Summary:
|
Ref _ |
Id _ |
Element Name _ |
Req |
Type |
Min/Max |
|
|
|
N401 |
19 |
City Name Description: Free-form text for city name |
O |
AN |
2/30 |
|
|
|
N402 |
156 |
State or Province Code Description: Code (Standard State/Province) as defined by
appropriate government agency |
O |
ID |
2/2 |
|
|
|
N403 |
116 |
Postal Code Description: Code defining international postal zone code
excluding punctuation and blanks (zip code for United States) |
O |
ID |
3/15 |
|
|
|
N404 |
26 |
Country Code Description: Code identifying the country Code NAME
_ CAN Canada MEX Mexico USA United States |
O |
ID |
2/3 |
|
|
Transaction Totals |
Pos: 010 Max: 1 Summary - Optional Loop: N/A Elements: 2 |
To transmit a hash total for a specific element in the transaction set
Example:
CTT*5^
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 |
M |
N0 |
1/6 |
|
|
|
CTT02 |
347 |
Hash Total Description: Sum of values of the SN102 data element. |
O |
R |
1/10 |
|
|
Transaction Set Trailer |
Pos: 020 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)
Example:
SE*36*0001^
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 |
|
|
Section 3
856 Ship
Notice/Manifest
Example
Transaction
This section contains an example transaction showing the use of the segments within the 856 Ship Notice/Manifest. Note: The example may not show all segments or qualifier combinations.
Page
Example Diagram.................................................................... 34
Example EDI 856 Ship Notice/Manifest #1 S-O-I............ 35
Example EDI 856 Ship Notice/Manifest #2 S-O-T-P-I...... 36
Example EDI 856 Ship Notice/Manifest #3 S-O-I-T-P...... 38
Example EDI 856 Ship Notice/Manifest #4 S-T-P-O-I...... 40
This
diagram is used to illustrate a typical shipment. Data from this illustration is used as a basis for building the
examples. This shipment shows multiple
orders, multiple items on an order, and multiple orders within a master
container.
Example EDI 856 Ship Notice/Manifest #1 S-O-I |
|
ST*856*0001^ |
|
BSN*00*01234678*20010731*1450*0004^ |
|
This starts the shipment level hierarchical loop |
|
HL*1**S^ |
|
TD1*CNT90*6****G*50*LB^ |
|
TD5**2*AAA*M*AAA FREIGHT CO.*******09^ |
|
TD3*TL*CFWY*123456^ |
|
REF*BM*C000006304^ |
|
DTM*011*20010122^ |
|
FOB*PC^ |
|
N1*ST**9*1231239870000^ |
|
N3*620 Peachtree Street^ |
|
N4*Atlanta*GA*30084*USA^ |
|
N1*SF**1*555823456^ |
|
This starts the purchase order level hierarchical loop for the first
purchase order of the shipment |
|
HL*2*1*O^ |
|
PRF*092123456***20000814^ |
|
This starts the item level hierarchical loop for the first item on
the first purchase order of the shipment |
|
HL*3*2*I^ |
|
LIN*1*VC*AAA001*UP*099999982011*BP*CC-14^ |
|
SN1*0001*3*EA^ |
|
This starts the purchase order level hierarchical loop for the second
purchase order of the shipment |
|
HL*4*1*O^ |
|
PRF*095987654**20000820^ |
|
This starts the item level hierarchical loop for the first item on
the second purchase order of the shipment |
|
HL*5*4*I^ |
|
LIN*1*VC*BBB001*UP*099999940011*BP*DD-14^ |
|
SN1*0001*3*EA^ |
|
This starts the purchase order level hierarchical loop for the third
purchase order of the shipment |
|
HL*6*1*O^ |
|
PRF*092555321**20000830^ |
|
This starts the item level hierarchical loop for the first item on
the third purchase order of the shipment |
|
HL*7*6*I^ |
|
LIN*1*VC*CCC001*UP*099999976011*BP*EE-14^ |
|
SN1*0001*1*EA^ |
|
This starts the purchase order level hierarchical loop for the fourth
purchase order of the shipment |
|
HL*8*1*O^ |
|
PRF*092444777**20000914^ |
|
This starts the item level hierarchical loop for the first item on
the fourth purchase order of the shipment |
|
HL*9*8*I^ |
|
LIN*1*VC*DDD001*UP*099999332011*BP*FF-14^ |
|
SN1*0001*1*EA^ |
|
This starts the item level hierarchical loop for the second item on
the fourth purchase order of the shipment |
|
HL*10*8*I^ |
|
LIN*1*VC*EEE001*UP*099999892011*BP*GG-14^ |
|
SN1*0001*1*EA^ |
|
|
|
CTT*9^ |
|
SE*39*0001^ |
|
Example EDI 856 Ship Notice/Manifest #2 S-O-T-P-I |
|
ST*856*0001^ |
|
BSN*00*01234678*20010731*1450*0001^ |
|
This starts the shipment level hierarchical loop |
|
HL*1**S^ |
|
TD1*CNT90*6****G*50*LB^ |
|
TD5**2*AAA*M*AAA FREIGHT CO.*******09^ |
|
TD3*TL*CFWY*123456^ |
|
REF*BM*C000006304^ |
|
DTM*011*20010122^ |
|
FOB*PC^ |
|
N1*ST**9*1231239870000^ |
|
N3*620 Peachtree Street^ |
|
N4*Atlanta*GA*30084*USA^ |
|
N1*SF**1*555823456^ |
|
This starts the purchase order level hierarchical loop for the first
purchase order of the shipment |
|
HL*2*1*O^ |
|
PRF*092123456***20000814^ |
|
This starts the pallet level hierarchical loop for the first purchase
order of the shipment |
|
HL*3*2*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the item level hierarchical loop for the first item on the
first purchase order of the shipment |
|
HL*4*3*I^ |
|
LIN*1*VC*AAA001*UP*099999982011*BP*CC-14^ |
|
SN1*0001*3*EA^ |
|
This starts the purchase order level hierarchical loop for the second
purchase order of the shipment |
|
HL*5*1*O^ |
|
PRF*095987654**20000820^ |
|
This starts the pallet level hierarchical loop for the second
purchase order of the shipment |
|
HL*6*5*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the item level hierarchical loop for the first item on
the second purchase order of the shipment |
|
HL*7*6*I^ |
|
LIN*1*VC*BBB001*UP*099999940011*BP*DD-14^ |
|
SN1*0001*3*EA^ |
|
This starts the purchase order level hierarchical loop for the third
purchase order of the shipment |
|
HL*8*1*O^ |
|
PRF*092555321**20000830^ |
|
This starts the pallet level hierarchical loop for the third purchase
order of the shipment |
|
HL*9*8*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the pack level hierarchical loop for the third purchase
order of the shipment |
|
HL*10*9*P^ |
|
MAN*GM*00001453789645478532^ |
|
This starts the item level hierarchical loop for the first item on
the third purchase order of the shipment |
|
HL*11*10*I^ |
|
LIN*1*VC*CCC001*UP*09999997601*BP*EE-14^ |
|
SN1*0001*1*EA^ |
|
This starts the purchase order level hierarchical loop for the fourth
purchase order of the shipment |
|
HL*12*1*O^ |
|
PRF*092444777**20000914^ |
|
This starts the pallet level hierarchical loop for the fourth
purchase order of the shipment |
|
HL*13*12*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the pack level hierarchical loop for the fourth purchase
order of the shipment |
|
HL*14*13*P^ |
|
MAN*GM*00001453789645478532^ |
|
This starts the item level hierarchical loop for the first item on
the fourth purchase order of the shipment |
|
HL*15*14*I^ |
|
LIN*1*VC*DDD001*UP*099999332011*BP*FF-14^ |
|
SN1*0001*1*EA^ |
|
This starts the item level hierarchical loop for the second item on
the fourth purchase order of the shipment |
|
HL*16*14*I^ |
|
LIN*1*VC*EEE001*UP*099999892011*BP*GG-14^ |
|
SN1*0001*1*EA^ |
|
|
|
CTT*16^ |
|
SE*50*0001^ |
|
Example EDI 856 Ship Notice/Manifest #3 S-O-I-T-P |
|
ST*856*0001^ |
|
BSN*00*01234678*20010731*1450*0002^ |
|
This starts the shipment level hierarchical loop |
|
HL*1**S^ |
|
TD1*CNT90*6****G*50*LB^ |
|
TD5**2*AAA*M*AAA FREIGHT CO.*******09^ |
|
TD3*TL*CFWY*123456^ |
|
REF*BM*C000006304^ |
|
DTM*011*20010122^ |
|
FOB*PC^ |
|
N1*ST**9*1231239870000^ |
|
N3*620 Peachtree Street^ |
|
N4*Atlanta*GA*30084*USA^ |
|
N1*SF**1*555823456^ |
|
This starts the purchase order level hierarchical loop for the first
purchase order of the shipment |
|
HL*2*1*O^ |
|
PRF*092123456***20000814^ |
|
This starts the item level hierarchical loop for the first item on the
first purchase order of the shipment |
|
HL*3*2*I^ |
|
LIN*1*VC*AAA001*UP*099999982011*BP*CC-14^ |
|
SN1*0001*3*EA^ |
|
This starts the pallet level hierarchical loop for the first item of
the first purchase order of the shipment |
|
HL*4*3*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the purchase order level hierarchical loop for the second
purchase order of the shipment |
|
HL*5*1*O^ |
|
PRF*095987654**20000820^ |
|
This starts the item level hierarchical loop for the first item on
the second purchase order of the shipment |
|
HL*6*5*I^ |
|
LIN*1*VC*BBB001*UP*099999940011*BP*DD-14^ |
|
SN1*0001*3*EA^ |
|
This starts the pallet level hierarchical loop for the first item of
the second purchase order of the shipment |
|
HL*7*6*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the purchase order level hierarchical loop for the third purchase
order of the shipment |
|
HL*8*1*O^ |
|
PRF*092555321**20000830^ |
|
This starts the item level hierarchical loop for the first item on
the third purchase order of the shipment |
|
HL*9*8*I^ |
|
LIN*1*VC*CCC001*UP*099999976011*BP*EE-14^ |
|
SN1*0001*1*EA^ |
|
This starts the pallet level hierarchical loop for the first item of
the third purchase order of the shipment |
|
HL*10*9*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the pack level hierarchical loop for the first item of the
third purchase order of the shipment |
|
HL*11*10*P^ |
|
MAN*GM*00001453789645478532^ |
|
This starts the purchase order level hierarchical loop for the fourth
purchase order of the shipment |
|
HL*12*1*O^ |
|
PRF*092444777**20000914^ |
|
This starts the item level hierarchical loop for the first item on
the fourth purchase order of the shipment |
|
HL*13*12*I^ |
|
LIN*1*VC*DDD001*UP*099999332011*BP*FF-14^ |
|
SN1*0001*1*EA^ |
|
This starts the pallet level hierarchical loop for the first item of
the fourth purchase order of the shipment |
|
HL*14*13*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the pack level hierarchical loop for the first item of the
fourth purchase order of the shipment |
|
HL*15*14*P^ |
|
MAN*GM*00001453789645478532^ |
|
This starts the item level hierarchical loop for the second item on
the fourth purchase order of the shipment |
|
HL*16*12*I^ |
|
LIN*1*VC*EEE001*UP*099999892011*BP*GG-14^ |
|
SN1*0001*1*EA^ |
|
This starts the pallet level hierarchical loop for the second item of
the fourth purchase order of the shipment |
|
HL*17*16*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the pack level hierarchical loop for the second item of
the fourth purchase order of the shipment |
|
HL*18*17*P^ |
|
MAN*GM*00001453789645478532^ |
|
|
|
CTT*18^ |
|
SE*54*0001^ |
|
Example EDI 856 Ship Notice/Manifest #4 S-T-P-O-I |
|
ST*856*0001^ |
|
BSN*00*01234678*20010731*1450*0003^ |
|
This starts the shipment level hierarchical loop |
|
HL*1**S^ |
|
TD1*CNT90*6****G*50*LB^ |
|
TD5**2*AAA*M*AAA FREIGHT CO.*******09^ |
|
TD3*TL*CFWY*123456^ |
|
REF*BM*C000006304^ |
|
DTM*011*20010122^ |
|
FOB*PC^ |
|
N1*ST**9*1231239870000^ |
|
N3*620 Peachtree Street^ |
|
N4*Atlanta*GA*30084*USA^ |
|
N1*SF**1*555823456^ |
|
This starts the pallet level hierarchical loop for the shipment |
|
HL*2*1*T^ |
|
MAN*GM*00006328196201689152^ |
|
This starts the purchase order level hierarchical loop for the first
purchase order of the shipment |
|
HL*3*2*O^ |
|
PRF*092123456***20000814^ |
|
This starts the item level hierarchical loop for the first item on
the first purchase order of the shipment |
|
HL*4*3*I^ |
|
LIN*1*VC*AAA001*UP*099999982011*BP*CC-14^ |
|
SN1*0001*3*EA^ |
|
This starts the purchase order level hierarchical loop for the second
purchase order of the shipment |
|
HL*5*2*O^ |
Second Purchase Order |
PRF*095987654**20000820^ |
|
This starts the item level hierarchical loop for the first item on the
second purchase order of the shipment |
|
HL*6*5*I^ |
|
LIN*1*VC*BBB001*UP*099999940011*BP*DD-14^ |
|
SN1*0001*3*EA^ |
|
This starts the pack level hierarchical loop for the shipment |
|
HL*7*2*P^ |
|
MAN*GM*00001453789645478532^ |
|
This starts the purchase order level hierarchical loop for the third
purchase order of the shipment |
|
HL*8*7*O^ |
|
PRF*092555321**20000830^ |
|
This starts the item level hierarchical loop for the first item on the
third purchase order of the shipment |
|
HL*9*8*I^ |
|
LIN*1*VC*CCC001*UP*099999976011*BP*EE-14^ |
|
SN1*0001*1*EA^ |
|
This starts the purchase order level hierarchical loop for the fourth
purchase order of the shipment |
|
HL*10*7*O^ |
|
PRF*092444777**20000914^ |
|
This starts the item level hierarchical loop for the first item on
the fourth purchase order of the shipment |
|
HL*11*10*I^ |
Item One on fourth purchase order |
LIN*1*VC*DDD001*UP*099999332011*BP*FF-14^ |
|
SN1*0001*1*EA^ |
|
This starts the item level hierarchical loop for the second item on
the fourth purchase order of the shipment |
|
HL*12*10*I^ |
Item Two on fourth purchase order |
LIN*1*VC*EEE001*UP*099999892011*BP*GG-14^ |
|
SN1*0001*1*EA^ |
|
CTT*12^ |
|
SE*42*0001^ |
|