August 2008
Ship Notice / Manifest - 856
Orchard Supply Hardware
Ship Notice / Manifest
Ship Notice / Manifest X12 4010
Author:
Trading Partner:
Created:
Modified:
Notes:
ISA/GS Qualifier, Receiver ID
TEST
PRODUCTION
Orchard 856.2 Ver 4010.ecs
Orchard Supply Hardware
August 2008
ZZ, OSHTEST
ZZ, OSHPROD
1
August 2008
Ship Notice / Manifest - 856
REVISION (August 2011): ID change to ZZ, OSHTEST and ZZ, OSHPROD
REVISION (November 2004): Page 856.33, 856.41, 856.42, 856.43: Added UK qualifier to LIN segment to
enable specification of the case code for an item; revised examples.
REVISION (May 2001): Page 856.31: Enabled the use of MAN04 and MAN05 at the pack level to be able
to specify both an SSCC-18 number and a small package carrier tracking number. Revised notes in MAN
segment at Pack level. Page 856.41: Added tracking number to segment examples. Page 856.39:
Eliminated the use of TD505 in the item level. This is no longer required by industry standards.
INTRODUCTION
This document specifies Orchard Supply Hardware requirements for transmission of the 856 Ship
Notice/Manifest transaction set. The document includes the data requirements for reporting all shipments
made directly to Orchard retail customers from a supplier location and domestic shipments to all Orchard
stores, distribution centers, consolidation and cross-dock facilities.
The Orchard ship notice is structured hierarchically with 4 levels: shipment, order, tare (pallet) or pack
(carton), and item (SKU). One shipment level data area can be included per transaction set. One or more
orders with the same ship to unit number in the same bill of lading may be reported in a shipment. One or
more tares or packs may be reported for each order. Finally, one or more items may be reported for each
pack or tare. Pack or tare level data must be included to report the contents of each shipping container.
Two hierarchical data structures are supported when packaging levels are used: Pick and Pack and
Standard Carton Pack. Each structure contains the same 4 levels, i.e., Shipment, Order, Tare or Pack, and
Item and the usage of the segments within each level is basically the same. The only difference between the
two structures is the order in which the levels may appear within the transaction set and the use of the
Hierarchical Structure Code within the BSN segment. The use of this code in BSN05 informs Orchard of the
structure of the transaction set. The essential difference in the two is where the Item level is positioned in
relation to the Packaging level (Pack or Tare). Note: the two data structures cannot be mixed within the
same 856.
For the Pick and Pack Structure, the Item is subordinate to the Packaging level, i.e., the specification of the
SKU is always within the shipment container (packaging level). The order of the hierarchical levels is:
Shipment, Order, Packaging, and Item. The shipping container is specified, then all SKU's within the
shipping container are identified. This data structure should be used when different SKU's are packed within
the same shipping container and when the Tare level will be used.
For the Standard Carton Pack Structure, the Item is subordinate to the Order level and the Packaging level
is subordinate to the Item level; i.e., the specification of the shipping containers is always within the SKU
(Item level). The SKU is specified, then all the shipping containers for the SKU's are identified. The order or
sequence of the hierarchical levels are Shipment, Order, Item and Packaging (Tare or Pack). This data
structure may be used when identical SKU's are packed within the same shipping container.
You may choose to report one order per transaction (single-order processing) or many orders per transaction
(multi-order processing); either method is acceptable. If you are packing more than one order in the same
physical container, you must report all those orders in the same 856 transaction set (multi-order) and in the
same HL-Order level and you must reference the PO in the PRF segment at the Item level instead of the
PRF at the Order level. You may not mix merchandise for different departments in the same physical
shipping container. Orchard requires an accurate carton count and total weight for each Order level. This
additional information, reported in the TD1 segment, is critical to the receiving process.
Orchard 856.2 Ver 4010.ecs
2
August 2008
Ship Notice / Manifest - 856
Each 856 must be identified uniquely in the beginning segment; duplicates will be rejected. Per the VICS
Guidelines, the scope of the 856 shall not exceed the contents of the associated bill of lading. That is, there
can be more than one ship notice referencing the same bill of lading, but there never will be one ship notice
referencing multiple bills of lading.
Orchard will use the 856 data to monitor shipments and facilitate receiving. Orchard’s goal is to automate
the receiving process: unload, scan and put away. Therefore, the 856 Ship Notice must be received and
processed by Orchard before the physical shipment arrives at the Orchard location specified in the shipment
level data. The latest time the ship notice may be sent, then, is the time of shipment - when the doors are
closed on the truck; your processing of the 856 should be event-driven.
HIERARCHICAL STRUCTURE EXAMPLES
Following are examples of Pick and Pack and Standard Carton Pack hierarchical structures. Each box in the
diagram represents a detail loop (one HL segment followed by data segments) in an 856 transaction set.
Pick and Pack Structure Example
In this example, the shipment contains two orders. The first order has two cartons. The first carton contains
three items (SKUs) and the second carton contains one item (SKU). The second order has one carton which
contains six different items (SKUs). The data segments in a single pack level uniquely identify one physical
shipping container; the data segments in the associated item levels specify the SKU contents of the shipping
container. The hierarchical structure for this example is illustrated below.
SHIPMENT
ORDER
ORDER
PACK
PACK
PACK
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM
ITEM

Pick and Pack
The Item level is subordinate to the Pack level.
Orchard 856.2 Ver 4010.ecs
3
August 2008

Ship Notice / Manifest - 856
Only one carton serial number UCC/EAN-128 (SSCC-18) may
be specified in a single pack level.
Standard Carton Pack Structure Example
In this example the shipment contains two orders. The first order has three items. Each item has one pack
level with each carton containing the same quantity of the same SKU. The packaging levels are below the
item. In this example, a single packaging level may specify carton serial numbers for more than one physical
shipping container, each containing the same quantity of the same SKU. The hierarchical structure for this
example is illustrated below.
SHIPMENT
ORDER
ORDER


ITEM
ITEM
ITEM
ITEM
PACK
PACK
PACK
PACK
Standard Carton Pack
The Pack level is subordinate to the Item level.
More than one carton serial number may be specified within a single pack level.
Orchard 856.2 Ver 4010.ecs
4
August 2008
Ship Notice / Manifest - 856
Single Consumer Selling Unit Shipped in More than One Carton
The following example illustrates a shipment of three lamps for one order. The ordered unit is a lamp which
has been assigned an item number and a U.P.C. Each lamp is comprised of two components, the base and
the shade. Therefore, there are two pack levels subordinate to the item level. One pack level is sent for
each component of the item and one MAN segment is sent for each carton. The SLN segment in the pack
level is used to indicate the component and the quantity included in the item (consumer selling unit) of this
component. The PO4 segment at the pack level is used to specify the quantity of the component in one
carton. The MAN segments are used to specify all of the carton serial numbers (SSCC-18) for the four
cartons being shipped. The standard carton pack structure must be used.
Note: Identification of the components in the SLN segment has been omitted because neither the base nor
the shade has been assigned a U.P.C. However, the manufacturer may send their internal product code for
the components to assist in identification. (This is recommended, but not required.) The hierarchical
structure for this example is illustrated below. The EDI mapping for this example is on the following page.
Shipment
BSN05 = 0002
Order
Item - Consumer Unit
Lamps: LIN**IN*12345*UP*123456789123
3 sets: SN1**3*ST
Pack - Component A: Base
Qty. in set: SLN*1**I*1*EA
Qty. in carton: PO4*1
Pack - Component B: Shade
Qty. in set: SLN*2**I*1*EA
Qty. in carton: PO4*3
MAN
Bar code for first carton
MAN
Bar code for single carton
MAN
Bar code for second carton
MAN
Bar code for third carton
Single Consumer Selling Unit Shipped in More than One Carton
 The Pack level is subordinate to the Item level.
 Each Pack level identifies a component of the item.
 Component product identification at the Pack level is recommended, but not required.
Orchard 856.2 Ver 4010.ecs
5
August 2008
Ship Notice / Manifest - 856
Business Example
Single Consumer Selling Unit Shipped in More than One Carton
ST*856*1234
BSN*00*449187654*19991203*1210*0002
[Unique shipment ID, Standard Carton Pack]
HL*1**S
TD1**4****G*10*LB
TD5**2*ABCD
REF*BM*C000006304
DTM*011*19991203
N1*ST**92*1570
[Begin Shipment level details]
[Lading quantity and gross weight per B/L]
[Carrier SCAC required]
[B/L number required]
[Actual ship date]
[Ship to unit number from PO - per B/L]
HL*2*1*O
PRF*1570-40-3023-00***19991008
PID*S**VI*FL
TD1**4****G*10*LB
REF*IA*65432
N1*BY**92*1570
[Begin Order level details]
[PO reference]
[FLSA compliance indicator]
[Carton count and weight for this order level]
[Internal supplier number from PO]
[Bill to unit number from PO]
HL*3*2*I
[Begin Item level details]
LIN*001*IN*2212345*UP*123456789123*VN*123456
[Item reference for product shipped]
SN1**3*ST
[Quantity of sets shipped for this order]
HL*4*3*P
SLN*1**I*1*EA
PO4*1
MAN*GM*00006328106201689152
[Begin 1st pack level details]
[Segment ID number, Included, quantity shipped of this
component in the set]
[Qty of this component in each carton]
[Carton serial number; segment repeats for each
carton]
MAN*GM*00006328106201689473
MAN*GM*00006328106201689497
HL*5*3*P
SLN*2**I*1*EA
PO4*3
MAN*GM*00006328106201689624
[Begin 2nd pack level details]
[Segment ID number, Included, quantity shipped of this
component in the set]
[Qty of this component in each carton]
[Carton serial number; one segment for one carton]
SE*Count of segments*Control number from ST
Orchard 856.2 Ver 4010.ecs
6
August 2008
Ship Notice / Manifest - 856
SH
Functional Group ID=
Transaction Set Table
Header
Seg.
ID
ST
BSN
Name
Transaction Set Header
Beginning Segment for Ship Notice
Req.
Des.
M
M
Max.Use
1
1
Req.
Des.
Max.Use
Loop
Repeat
Detail - Shipment level
Seg.
ID
HL
TD1
TD5
TD3
REF
DTM
N1
N3
N4
Name
LOOP ID - HL
Hierarchical Level
Carrier Details (Quantity and Weight)
Carrier Details (Routing Sequence/Transit
Time)
Carrier Details (Equipment)
Reference Identification
Date/Time Reference
LOOP ID - N1
Name
Address Information
Geographic Location
M
O
O
1
20
12
O
O
O
12
>1
10
O
O
O
1
2
1
Loop
Repeat
200000
200
Detail - Order level
Seg.
ID
HL
PRF
PID
TD1
REF
N1
Orchard 856.2 Ver 4010.ecs
Name
LOOP ID - HL
Hierarchical Level
Purchase Order Reference
Product/Item Description
Carrier Details (Quantity and Weight)
Reference Identification
LOOP ID - N1
Name
Req.
Des.
Max.Use
M
O
O
O
O
1
1
200
20
>1
O
1
Loop
Repeat
200000
200
7
August 2008
Ship Notice / Manifest - 856
Detail - Tare level
Seg.
ID
HL
MAN
Name
LOOP ID - HL
Hierarchical Level
Marks and Numbers
Req.
Des.
Max.Use
M
O
1
>1
Req.
Des.
Max.Use
Loop
Repeat
200000
Detail - Pack level
Seg.
ID
HL
SLN
PO4
MAN
Name
LOOP ID - HL
Hierarchical Level
Subline Item Detail
Item Physical Details
Marks and Numbers
M
O
O
O
Loop
Repeat
200000
1
1000
1
>1
Detail - Item level
Seg.
ID
HL
LIN
SN1
SLN
PRF
TD5
Name
LOOP ID - HL
Hierarchical Level
Item Identification
Item Detail (Shipment)
Subline Item Detail
Purchase Order Reference
Carrier Details (Routing Sequence/Transit
Time)
Req.
Des.
M
O
O
O
O
O
Max.Use
Loop
Repeat
200000
1
1
1
1000
1
12
Summary
Seg.
ID
SE
Orchard 856.2 Ver 4010.ecs
Req.
Des.
M
Name
Transaction Set Trailer
8
Max.Use
1
Loop
Repeat
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Ref.
Des.
ST01
ST02
Orchard 856.2 Ver 4010.ecs
ST Transaction Set Header
Header
Mandatory
1
Data Element Summary
Data
Element Name
143
Transaction Set Identifier Code
856
Ship Notice/Manifest
329
Transaction Set Control Number
9
Attributes
M ID 3/3
M
AN 4/9
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
BSN Beginning Segment for Ship Notice
Header
Mandatory
1
1.
2.
3.
4.
Ref.
Des.
BSN01
BSN02
BSN03
BSN04
BSN05
N/U
N/U
BSN06
BSN07
Orchard 856.2 Ver 4010.ecs
BSN05 indicates the structure of the 856 and tells Orchard how to process the
document.
Only one data structure may be used within a single transaction set. That is, if
packaging levels are used, they may appear below or above the item level, but their
placement must be consistent within the same transaction set. The code in BSN05
will indicate the order in which the levels are used.
The shipment identification number in BSN02 must be a unique number and must
remain unique for 30 days. Orchard will check for duplicates using the reference
number in BSN02. If a duplicate is encountered, the transaction set will be rejected.
Time created (BSN04) is required on all Orchard ship notices. This data element is
used in the duplicate checking process. A 24 hour clock is used.
Data Element Summary
Data
Element Name
353
Transaction Set Purpose Code
00
Original
396
Shipment Identification
373
Date
Date Created
337
Time
4-6
Time Created (HHMMSS)
1005
Hierarchical Structure Code
0001
Shipment, Order, Packaging, Item
Pick and Pack Structure
0002
Shipment, Order, Item, Packaging
Standard Carton Pack Structure
0004
Shipment, Order, Item
No packaging levels are sent
640
Transaction Type Code
641
Status Reason Code
10
Attributes
M ID 2/2
M
M
AN 2/30
DT 8/8
M
TM 4/8
O
ID 4/4
X
O
ID 2/2
ID 3/3
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
HL Hierarchical Level
HL
Detail - Shipment
Mandatory
1
1.
2.
3.
Ref.
Des.
HL01
N/U
HL02
HL03
N/U
HL04
Orchard 856.2 Ver 4010.ecs
This HL segment marks the beginning of the shipment loop. The shipment level is
mandatory and may occur only once per transaction set.
The value in HL01 will always be 1 for the first occurrence of the HL segment in
the transaction set and will be incremented by 1 for each additional occurrence of
the HL segment present within the transaction set.
The shipment level specifies the details relative to the entire physical shipment and
associated bill of lading.
Data Element Summary
Data
Element Name
628
Hierarchical ID Number
The value for this level (shipment) is 1.
734
Hierarchical Parent ID Number
735
Hierarchical Level Code
S
Shipment
736
Hierarchical Child Code
11
Attributes
M AN 1/12
O
M
AN 1/12
ID 1/2
O
ID 1/1
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
N/U
N/U
N/U
N/U
Ref.
Des.
TD101
TD102
TD103
TD104
TD105
TD106
TD107
TD108
N/U
N/U
TD109
TD110
Orchard 856.2 Ver 4010.ecs
TD1 Carrier Details (Quantity and Weight)
HL
Detail - Shipment
Required by Orchard
20
1.
2.
This segment is required on all Orchard ship notices.
The lading quantity reflects the total number of cartons, or containers in the
shipment as consigned to the carrier. The gross weight reflects the total weight in
pounds of the shipment as stated on the bill of lading and as consigned to the
carrier.
Data Element Summary
Data
Element Name
103
Packaging Code
80
Lading Quantity
The number of packages in the shipment
23
Commodity Code Qualifier
22
Commodity Code
79
Lading Description
187
Weight Qualifier
G
Gross Weight
81
Weight
355
Unit or Basis for Measurement Code
LB
Pound
183
Volume
355
Unit or Basis for Measurement Code
12
Attributes
O AN 3/5
X N0 1/7
O
X
O
O
ID 1/1
AN 1/30
AN 1/50
ID 1/2
X
X
R 1/10
ID 2/2
X
X
R 1/8
ID 2/2
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
TD5 Carrier Details (Routing Sequence/Transit Time)
HL
Detail - Shipment
Required by Orchard
12
1.
2.
This segment is required on all ship notices to specify the SCAC.
The Standard Carrier Alpha Code (SCAC) lists and codes transportation carriers
operating in North America. Each carrier is assigned a unique 2 - 4 letter code for
use as an abbreviation or to identify a particular carrier for transportation data
processing purposes. The SCAC directory contains 2 sections. Section 1 is an
alphabetical listing of carrier names. Section 2 is an alphabetical listing of carrier
codes.
A computer tape file, the Continental Directory NMF101 of Standard Carrier Alpha
Codes and Standard Tariff Agent's Codes may be purchased from the American
Trucking Association, 2200 Mill Road, Alexandria, VA 22314.
N/U
Ref.
Des.
TD501
TD502
TD503
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
TD504
TD505
TD506
TD507
TD508
TD509
TD510
TD511
TD512
TD513
TD514
TD515
Orchard 856.2 Ver 4010.ecs
Data Element Summary
Data
Element Name
Attributes
133
Routing Sequence Code
O ID 1/2
66
Identification Code Qualifier
X ID 1/2
2
Standard Carrier Alpha Code (SCAC)
67
Identification Code
X AN 2/80
2-4
SCAC code
91
Transportation Method/Type Code
X ID 1/2
387
Routing
X AN 1/35
368
Shipment/Order Status Code
X ID 2/2
309
Location Qualifier
O ID 1/2
310
Location Identifier
X AN 1/30
731
Transit Direction Code
O ID 2/2
732
Transit Time Direction Qualifier
O ID 2/2
733
Transit Time
X R 1/4
284
Service Level Code
X ID 2/2
284
Service Level Code
X ID 2/2
284
Service Level Code
O ID 2/2
26
Country Code
O ID 2/3
13
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
Ref.
Des.
TD301
TD302
TD303
N/U
N/U
N/U
N/U
N/U
N/U
N/U
TD304
TD305
TD306
TD307
TD308
TD309
TD310
Orchard 856.2 Ver 4010.ecs
TD3 Carrier Details (Equipment)
HL
Detail - Shipment
Conditional for Orchard
12
1.
This segment is required on all ship notices to specify the trailer number for
truckload shipments. This segment is not used for LTL shipments.
Data Element Summary
Data
Element Name
40
Equipment Description Code
TL
Trailer (not otherwise specified)
206
Equipment Initial
2-4
SCAC code (trailer prefix)
207
Equipment Number
1 - 10 Trailer number
187
Weight Qualifier
81
Weight
355
Unit or Basis for Measurement Code
102
Ownership Code
407
Seal Status Code
225
Seal Number
24
Equipment Type
14
Attributes
X ID 2/2
O
AN 1/4
X
AN 1/10
O
X
X
O
O
O
X
ID 1/2
R 1/10
ID 2/2
ID 1/1
ID 2/2
AN 2/15
ID 4/4
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
Ref.
Des.
REF01
REF02
N/U
N/U
REF03
REF04
Orchard 856.2 Ver 4010.ecs
REF Reference Identification
HL
Detail - Shipment
Required by Orchard
1
1.
2.
Orchard requires the bill of lading number for all truckload and LTL shipments.
The PRO number is required when the shipment has been prepaid by the shipper.
Data Element Summary
Data
Element Name
Attributes
128
Reference Identification Qualifier
M ID 2/3
BM
Bill of Lading Number
BN
Booking Number
CN
Carrier's Reference Number (PRO/Invoice)
SN
Seal Number
127
Reference Identification
X AN 1/30
2 - 12 Bill of Lading Number
2 - 12 Booking Number
2 - 13 Carrier's Reference Number (PRO/Invoice)
2 - 12 Seal Number
352
Description
X AN 1/80
C040
Reference Identifier
O
15
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
DTM Date/Time Reference
HL
Detail - Shipment
Required by Orchard
10
1.
2.
Ref.
Des.
DTM01
N/U
N/U
N/U
N/U
DTM02
DTM03
DTM04
DTM05
DTM06
Orchard 856.2 Ver 4010.ecs
This segment is required on all ship notices to specify the actual ship date
(DTM*011).
If the shipment is not picked up on time and the actual ship date does not match the
scheduled ship date, 2 iterations of the DTM segment must be sent to specify the 2
dates (DTM*011 and DTM*068).
Data Element Summary
Data
Element Name
374
Date/Time Qualifier
011
Shipped
068
Current Schedule Ship
373
Date
337
Time
623
Time Code
1250
Date Time Period Format Qualifier
1251
Date Time Period
16
Attributes
M ID 3/3
X
X
O
X
X
DT 8/8
TM 4/8
ID 2/2
ID 2/3
AN 1/35
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
N1 Name
N1
Detail - Shipment
Conditional for Orchard
1
1.
2.
Ref.
Des.
N101
N102
N103
N104
N/U
N/U
N105
N106
Orchard 856.2 Ver 4010.ecs
The N1 segment at the shipment level identifies the shipper and the ship to location
for the physical shipment - the same details as entered on the associated bill of
lading.
The N1*ST segment is required on all ship notices. This may be a store,
distribution center or cross-dock facility or consolidation point for the order.
Data Element Summary
Data
Element Name
Attributes
98
Entity Identifier Code
M ID 2/3
SF
Ship From
ST
Ship To
93
Name
X AN 1/60
Shipper name - use only when N101 contains code value SF
66
Identification Code Qualifier
X ID 1/2
92
Assigned by Buyer or Buyer's Agent
67
Identification Code
X AN 2/80
4 - 4 Ship To; use only when N101 contains code value ST
706
Entity Relationship Code
O ID 2/2
98
Entity Identifier Code
O ID 2/3
17
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
N3 Hierarchical Level
N1
Detail - Shipment
Conditional for Orchard
2
Data Element Summary
Ref.
Des.
N301
N302
Orchard 856.2 Ver 4010.ecs
Data
Element
166
166
Name
Address Information
Address Information
18
Attributes
M
O
AN 1/55
AN 1/55
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
N4 Geographic Location
N1
Detail - Shipment
Conditional for Orchard
1
1.
Country code is specified only if it is outside of the United States.
Data Element Summary
Ref.
Des.
N/U
N/U
Data
Element
N401
19
N402
N403
156
116
N404
26
N405
N406
309
310
Orchard 856.2 Ver 4010.ecs
Name
Attributes
City Name
2 - 19 City name
State or Province Code
Postal Code
5-9
Zip code
Country Code
Optional - use only if outside of US
Location Qualifier
Location Identifier
19
O
AN 2/30
O
O
ID 2/2
ID 3/15
O
ID 2/3
X
O
ID 1/2
AN 1/30
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
Ref.
Des.
HL01
HL02
HL03
N/U
HL04
Orchard 856.2 Ver 4010.ecs
HL Hierarchical Level
HL
Detail - Order
Mandatory
1
1.
The order level is always subordinate to the shipment level. Therefore the parent
HL parent number for the HL-O will always be 1.
Data Element Summary
Data
Element Name
628
Hierarchical ID Number
734
Hierarchical Parent ID Number
1
The parent ID number for the order level will
always be ‘1’
735
Hierarchical Level Code
O
Order
736
Hierarchical Child Code
20
Attributes
M AN 1/12
O AN 1/12
M
ID 1/2
O
ID 1/1
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
Ref.
Des.
PRF01
N/U
N/U
PRF02
PRF03
PRF04
N/U
N/U
N/U
PRF05
PRF06
PRF07
Orchard 856.2 Ver 4010.ecs
PRF Purchase Order Reference
HL
Detail - Order
Required by Orchard
1
1.
2.
Orchard requires the PO date from the original purchase order in PRF04.
Specify the Orchard PO number in this segment at the order level unless you pack
more than one PO in the same physical shipping container. If you pack multiple
PO’s in the same container, you must use the pick and pack data structure and
reference the PO number and date in the PRF segment at the item level. The PRF at
the order level and the PRF at the item level are mutually exclusive.
Data Element Summary
Data
Element Name
324
Purchase Order Number
15 - 15 PO number
328
Release Number
327
Change Order Sequence Number
373
Date
PO date
350
Assigned Identification
367
Contract Number
92
Purchase Order Type Code
21
Attributes
M AN 1/22
O
O
O
AN 1/30
AN 1/8
DT 8/8
O
O
O
AN 1/20
AN 1/30
ID 2/2
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
Ref.
Des.
PID01
N/U
PID02
PID03
PID04
N/U
N/U
N/U
N/U
N/U
PID05
PID06
PID07
PID08
PID09
Orchard 856.2 Ver 4010.ecs
PID Product/Item Description
HL
Detail - Order
Required by Orchard
200
1.
One occurrence of this segment is required on every ship notice to Orchard to
indicate compliance with the Fair Labor Standards Act.
Data Element Summary
Data
Element Name
Attributes
349
Item Description Type
M ID 1/1
S
Structured (From Industry Code List)
The description will be found in PID03 and PID04.
750
Product/Process Characteristic Code
O ID 2/3
559
Agency Qualifier Code
X ID 2/2
VI
Voluntary Inter-Industry Commerce Standard (VICS)
EDI
751
Product Description Code
X AN 1/12
FL
Compliant with Fair Labor Standards Act
352
Description
X AN 1/80
752
Surface/Layer/Position Code
O ID 2/2
822
Source Subqualifier
O AN 1/15
1073
Yes/No Condition or Response Code
O ID 1/1
819
Language Code
O ID 2/3
22
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
N/U
N/U
N/U
N/U
Ref.
Des.
TD101
TD102
TD103
TD104
TD105
TD106
TD107
TD108
N/U
N/U
TD109
TD110
Orchard 856.2 Ver 4010.ecs
TD1 Carrier Details (Quantity and Weight)
HL
Detail - Order
Required by Orchard
20
1.
The carton count and weight of each HL-Order level are required on all ship
notices. The data reported in this TD1 applies only to this order level.
Data Element Summary
Data
Element Name
103
Packaging Code
80
Lading Quantity
23
Commodity Code Qualifier
22
Commodity Code
79
Lading Description
187
Weight Qualifier
G
Gross Weight
81
Weight
355
Unit or Basis for Measurement Code
LB
Pound
183
Volume
355
Unit or Basis for Measurement Code
23
Attributes
O AN 3/5
X N0 1/7
O ID 1/1
X AN 1/30
O AN 1/50
O ID 1/2
X
X
R 1/10
ID 2/2
X
X
R 1/8
ID 2/2
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
Ref.
Des.
REF01
REF02
N/U
N/U
REF03
REF04
Orchard 856.2 Ver 4010.ecs
REF Reference Identification
HL
Detail - Order
Required by Orchard
1
1.
The internal vendor number is present on the purchase order and is required to be
returned on the ship notice. The value of REF*IA on the ship notice will be the
same as the value of REF*IA on the purchase order.
Data Element Summary
Data
Element Name
128
Reference Identification Qualifier
IA
Internal Vendor Number
127
Reference Identification
5-5
Internal vendor number
352
Description
C040
Reference Identifier
24
Attributes
M ID 2/3
X
AN 1/30
X
O
AN 1/80
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
N1 Name
N1
Detail - Order
Required by Orchard
1
1.
2.
Ref.
Des.
N101
N/U
N102
N103
N104
N/U
N/U
N105
N106
Orchard 856.2 Ver 4010.ecs
The N1*BY segment is required on every ship notice. Orchard cannot process your
ship notice without this segment. The N104 data is the Orchard-assigned unit
number which will be billed for the merchandise. The value entered in N104 will
always be the same as the N1*BY from the purchase order.
If present on the purchase order, the N1*Z7 segment must be returned on the ship
notice. This is the "Mark for" unit or final destination for the order. The mark for
condition will be encountered on orders that will be packed for a store but crossdocked through a distribution facility.
Data Element Summary
Data
Element Name
Attributes
98
Entity Identifier Code
M ID 2/3
BY
Buying Party (Purchaser)
Z7
Mark-for Party
This is the final destination for the order.
93
Name
X AN 1/60
66
Identification Code Qualifier
X ID 1/2
92
Assigned by Buyer or Buyer's Agent
67
Identification Code
X AN 2/80
4-4
Orchard unit number
706
Entity Relationship Code
O ID 2/2
98
Entity Identifier Code
O ID 2/3
25
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
HL Hierarchical Level
HL
Detail - Tare
Conditional for Orchard
1
1.
2.
3.
Ref.
Des.
HL01
HL02
HL03
N/U
HL04
Orchard 856.2 Ver 4010.ecs
The tare level should be used only to identify pallets. If there are no identifiable
pallets (with bar coded shipping container label affixed), then the tare level should
be omitted.
This level is not used when BSN05 contains code value 0002 (Standard Carton Pack
data structure).
For Pick and Pack shipments (BSN05 contains code value 0001), the tare level is
always subordinate to the order level. Therefore the value in HL02 will be the value
sent in HL01 for the associated order level.
Data Element Summary
Data
Element Name
628
Hierarchical ID Number
734
Hierarchical Parent ID Number
735
Hierarchical Level Code
T
Shipping Tare
736
Hierarchical Child Code
26
Attributes
M AN 1/12
O AN 1/12
M ID 1/2
O
ID 1/1
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
MAN Marks and Numbers
HL
Detail - Tare
Conditional for Orchard
1
1.
2.
Ref.
Des.
MAN01
MAN02
N/U
N/U
N/U
N/U
MAN03
MAN04
MAN05
MAN06
Orchard 856.2 Ver 4010.ecs
This segment, at the tare level, is used to specify the identification numbers for a
pallet. This segment is required when the Tare level is used.
The Tare level may be used only in a Pick and Pack data structure. Only one MAN
segment will be present in each HL-Tare loop. Use code AA or GM in MAN01 to
specify the SSCC-18 serial shipping container code.
Data Element Summary
Data
Element Name
Attributes
88
Marks and Numbers Qualifier
M ID 1/2
AA
SSCC-18
This is an eighteen-character UCC/EAN-128 Serial
Shipping Container Code (SSCC-18) that does not
include the two digit application identifier, the
symbology code, or the modulo 103 check character.
CP
Carrier-Assigned Package ID Number
This is the tracking number for small package
shipments, e.g., UPS.
GM
SSCC-18 and Application Identifier
This is a twenty-character UCC/EAN-128 Serial
Shipping Container Code (SSCC-18) that includes
the two digit application identifier. The symbology
code and the modulo 103 check digit are not
included.
87
Marks and Numbers
M AN 1/48
18 - 18 SSCC-18
1 - 48 Carrier-Assigned Package ID number
20 - 20 SSCC-18 and Application Identifier
87
Marks and Numbers
O AN 1/48
88
Marks and Numbers Qualifier
X ID 1/2
87
Marks and Numbers
X AN 1/48
87
Marks and Numbers
O AN 1/48
27
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
HL Hierarchical Level
HL
Detail - Pack
Conditional for Orchard
1
1.
2.
3.
Ref.
Des.
HL01
HL02
HL03
N/U
HL04
Orchard 856.2 Ver 4010.ecs
The pack level is used to identify carton numbers on packs. If there are no
identifiable packs (with bar coded shipping container label affixed), then the pack
level is omitted. If the pack level is sent, then the tare level should be omitted.
For Pick and Pack shipments (BSN05 contains code value 0001), the pack level is
subordinate to the order level. Therefore, the value in HL02 will be the value sent
in HL01 for the associated order level.
For Standard Carton Pack shipments (BSN05 contains code value 0002), the pack
level is subordinate to the item level. Therefore, the value sent in HL02 will be the
value sent in HL01 for the associated item level.
Data Element Summary
Data
Element Name
628
Hierarchical ID Number
734
Hierarchical Parent ID Number
735
Hierarchical Level Code
P
Pack
736
Hierarchical Child Code
28
Attributes
M AN 1/12
O AN 1/12
M ID 1/2
O
ID 1/1
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
N/U
N/U
N/U
SLN Subline Item Detail
HL
Detail - Pack
Conditional for Orchard
1000
1.
This segment, when used in a Standard Carton Pack structure at the pack level, may
be used only to specify an individual component of the item identified in the LIN
segment in the previous/associated item level. The quantity specified in SN102, at
the item level, represents the number of sets, and SN103 will contain code ST, to
identify it as a set. Each subsequent MAN segment, within this pack level, identifies
the carton ID for each component identified in the SLN segment. Additional pack
level SLN segments and MAN segments are used to represent each different
component of the set.
Data Element Summary
Data
Element Name
Attributes
350
Assigned Identification
M AN 1/20
350
Assigned Identification
O AN 1/20
662
Relationship Code
M ID 1/1
I
Included
SLN04
380
Quantity
X R 1/15
SLN05
C001
Composite Unit of Measure
X
-C00101
355
Unit or Basis for Measurement Code
M ID 2/2
ST
Set
-C00102 - C00115
SLN09
235
Product/Service ID Qualifier
X ID 2/2
IN
Supplier’s Item Number (Orchard item number)
UP
U.P.C. Consumer Package Code (1-5-5-1)
VN
Supplier’s (Seller's) Item Number
SLN10
234
Product/Service ID
X AN 1/48
7-7
Orchard item number
12 - 12 U.P.C. number
1 - 15 Supplier’s item number
SLN11
235
Product/Service ID Qualifier
X ID 2/2
See SLN09
SLN12
234
Product/Service ID
X AN 1/48
See SLN10
SLN13
235
Product/Service ID Qualifier
X ID 2/2
See SLN09
SLN14
234
Product/Service ID
X AN 1/48
See SLN10
SLN15
235
Product/Service ID Qualifier
X ID 2/2
Ref.
Des.
SLN01
SLN02
SLN03
Orchard 856.2 Ver 4010.ecs
29
August 2008
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
Ship Notice / Manifest - 856
Ref.
Des.
SLN16
SLN17
SLN18
SLN19
SLN20
SLN21
SLN22
SLN23
SLN24
SLN25
SLN26
SLN27
SLN28
Orchard 856.2 Ver 4010.ecs
Data
Element
234
235
234
235
234
235
234
235
234
235
234
235
234
Name
Product/Service ID
Product/Service ID Qualifier
Product/Service ID
Product/Service ID Qualifier
Product/Service ID
Product/Service ID Qualifier
Product/Service ID
Product/Service ID Qualifier
Product/Service ID
Product/Service ID Qualifier
Product/Service ID
Product/Service ID Qualifier
Product/Service ID
30
Attributes
X AN 1/48
X ID 2/2
X AN 1/48
X ID 2/2
X AN 1/48
X ID 2/2
X AN 1/48
X ID 2/2
X AN 1/48
X ID 2/2
X AN 1/48
X ID 2/2
X AN 1/48
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
PO4 Item Physical Details
HL
Detail - Pack
Conditional for Orchard
1
1.
2.
3.
Ref.
Des.
PO401
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
PO402
PO403
PO404
PO405
PO406
PO407
PO408
PO409
PO410
PO411
PO412
PO413
PO414
N/U
N/U
N/U
N/U
PO415
PO416
PO417
PO418
Orchard 856.2 Ver 4010.ecs
When using the Standard Carton Pack structure, the PO4 segment at the Pack level
is required to specify the quantity packed in each shipping container. The SN1 will
report the total quantity shipped for the item (in all cartons).
If inner packs are used, the quantity of units in each shipping container is calculated
by multiplying the number of inner packs (PO401) by the number of eaches per
pack (PO414). This result, multiplied by the number of MAN segments is the
receipt quantity and must equal the quantity sent in the SN1 segment for the
associated item.
If inner packs are not used, then PO401 must specify the quantity of units in each
shipping container. This quantity, multiplied by the number of MAN segments is
the receipt quantity and must equal the quantity sent in the SN1 segment for the
associated item.
Data Element Summary
Data
Element Name
Attributes
356
Pack
O N0 1/6
The number of inner containers or number of eaches if there are no inner
containers.
357
Size
X R 1/8
355
Unit or Basis for Measurement Code
X ID 2/2
103
Packaging Code
X AN 3/5
187
Weight Qualifier
O ID 1/2
384
Gross Weight per Pack
X R 1/9
355
Unit or Basis for Measurement Code
X ID 2/2
385
Gross Volume per Pack
X R 1/9
355
Unit or Basis for Measurement Code
X ID 2/2
82
Length
X R 1/8
189
Width
X R 1/8
65
Height
X R 1/8
355
Unit or Basis for Measurement Code
X ID 2/2
810
Inner Pack
O N0 1/6
Number of eaches per inner container
752
Surface/Layer/Position Code
O ID 2/2
350
Assigned Identification
X AN 1/20
350
Assigned Identification
O AN 1/20
1470
Number
O N0 1/9
31
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
MAN Marks and Numbers
HL
Detail - Pack
Conditional for Orchard
1
1.
2.
3.
Ref.
Des.
MAN01
MAN02
N/U
MAN03
MAN04
MAN05
N/U
MAN06
Orchard 856.2 Ver 4010.ecs
For Pick and Pack shipments, send only one MAN segment in each HL-Pack loop.
Use code AA or GM in MAN01 to specify the SSCC-18 (UCC/EAN-128) serial
shipping container code.
For Standard Carton Pack shipments, send one MAN segment for each shipping
container for the item. Use code AA or GM in MAN01 to specify the SSCC-18
(UCC/EAN-128) serial shipping container code.
For shipments that are sent toan Orchard facility via a small package carrier,
MAN01 must contain code AA or GM, and MAN04 will contain code CP. MAN02
will contain the SSCC-18, and MAN04 will contain the small package carrier’s
tracking number.
Data Element Summary
Data
Element Name
Attributes
88
Marks and Numbers Qualifier
M ID 1/2
AA
SSCC-18
This is an eighteen-character UCC/EAN-128 Serial
Shipping Container Code (SSCC-18) that does not
include the two digit application identifier, ‘00’.
CP
Carrier-Assigned Package ID Number
This is the tracking number for a small package
shipment, e.g., UPS.
GM
SSCC-18 and Application Identifier
This is the full twenty-character UCC/EAN-128
Serial Shipping Container Code (SSCC-18) that
includes the two digit application identifier, ‘00’.
87
Marks and Numbers
M AN 1/48
18 - 18 SSCC-18
1 - 48 Carrier-Assigned Package ID number
20 - 20 SSCC-18 and Application Identifier
87
Marks and Numbers
O AN 1/48
88
Marks and Numbers Qualifier
M ID 1/2
CP
Carrier-Assigned Package ID Number
This is the tracking number for a small package
shipment, e.g., UPS.
87
Marks and Numbers
X AN 1/48
1 - 48 Carrier-Assigned Package ID number
87
Marks and Numbers
O AN 1/48
32
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
Ref.
Des.
HL01
HL02
HL03
N/U
HL04
Orchard 856.2 Ver 4010.ecs
HL Hierarchical Level
HL
Detail - Item
Mandatory
1
1.
2.
At least one iteration of this loop is required for every parent order loop.
The item level may be subordinate to the pack, tare or order levels. Therefore the
value in HL02 will be the value sent in the HL01 element for the parent pack, tare
or order level.
Data Element Summary
Data
Element Name
628
Hierarchical ID Number
734
Hierarchical Parent ID Number
735
Hierarchical Level Code
I
Item
736
Hierarchical Child Code
33
Attributes
M AN 1/12
O AN 1/12
M ID 1/2
O
ID 1/1
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
LIN Item Identification
HL
Detail - Item
Required by Orchard
1
1.
2.
3.
4.
5.
Ref.
Des.
LIN01
LIN02
LIN03
LIN04
LIN05
Orchard 856.2 Ver 4010.ecs
Each LIN segment represents a single line item.
Orchard item identifiers must be returned on the ship notice as sent on the original
purchase order. The U.P.C. number may be sent in addition to the Orchard item
number.
The PO line number (LIN01) is a sequential control number assigned to each line
item on the order and helps distinguish between like items on the order. If sent on
the purchase order, it must be referenced on the ship notice. This is a requirement
for Orchard.
If a substitution has been authorized by the Orchard buyer, the LIN segment will
specify the substitute product shipped and the SLN segment will report the
originally ordered item and quantity.
When LIN02, LIN04 or LIN06 contain code UK, the number in the corresponding
Product Service ID element is the EAN/UCC number assigned to the case level of
the product, it is not for the consumer unit.
Data Element Summary
Data
Element Name
Attributes
350
Assigned Identification
O AN 1/20
235
Product/Service ID Qualifier
M ID 2/2
IN
Supplier’s Item Number
UK
U.P.C./EAN Shipping Container Code (1-2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
VN
Supplier’s (Seller's) Item Number
234
Product/Service ID
M AN 1/48
7-7
Orchard-assigned item number
12 - 12 U.P.C. number
1 - 15 Supplier’s Item Number
235
Product/Service ID Qualifier
X ID 2/2
See LIN02
234
Product/Service ID
X AN 1/48
See LIN03
34
August 2008
Ship Notice / Manifest - 856
Ref.
Des.
LIN06
LIN07
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
LIN08
LIN09
LIN10
LIN11
LIN12
LIN13
LIN14
LIN15
LIN16
LIN17
LIN18
LIN19
LIN20
LIN21
LIN22
LIN23
LIN24
LIN25
LIN26
LIN27
LIN28
LIN29
LIN30
LIN31
Orchard 856.2 Ver 4010.ecs
Data
Element Name
235
Product/Service ID Qualifier
See LIN02
234
Product/Service ID
See LIN03
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
235
Product/Service ID Qualifier
234
Product/Service ID
35
Attributes
X ID 2/2
X
AN 1/48
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
ID 2/2
AN 1/48
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
SN1 Item Detail (Shipment)
HL
Detail - Item
Required by Orchard
1
1.
2.
3.
4.
N/U
Ref.
Des.
SN101
SN102
SN103
N/U
N/U
N/U
N/U
N/U
SN104
SN105
SN106
SN107
SN108
Orchard 856.2 Ver 4010.ecs
This segment is used to specify the actual quantity shipped for the item/SKU
identified in the associated LIN segment. The value sent in SN103 should be the
same value sent on the PO.
SN103 will contain code ‘ST’ when you are reporting quantity shipped for a single
consumer unit packed in more than one physical shipping container.
If a substitution has been authorized by the Orchard buyer, the LIN segment will
specify the substituted item/SKU, the SN1 segment will report a quantity shipped
and the SLN segment(s) following will report the originally ordered item/SKU and
quantity.
To cancel the balance for an item, the SN1 segment shall report the quantity shipped
for the item and the TD5 segment may then be used to indicate that the balance
should be canceled.
Data Element Summary
Data
Element Name
Attributes
350
Assigned Identification
O AN 1/20
382
Number of Units Shipped
M R 1/10
355
Unit or Basis for Measurement Code
M ID 2/2
Value from PO103 from 850
ST
Set (when reporting items packed in more than one
Shipping container)
646
Quantity Shipped to Date
O R 1/15
330
Quantity Ordered
X R 1/15
355
Unit or Basis for Measurement Code
X ID 2/2
728
Returnable Container Load Make-Up Code
O ID 1/2
668
Line Item Status Code
O ID 2/2
36
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
SLN Subline Item Detail
HL
Detail - Item
Conditional for Orchard
1000
1.
2.
3.
The SLN segment should be used only to report authorized substitutions.
For Orchard Authorized Substitutions, the SLN should specify the originally
ordered product ID and quantity. The value in SLN03 must be 'S'. The LIN and
SN1 segments should report the product ID and quantity shipped of the substituted
product.
The value of SLN01 should be a sequential number, beginning with one and
incrementing by one for each occurrence of the SLN segment within each HL-I
loop.
Data Element Summary
Data
Element Name
Attributes
350
Assigned Identification
M AN 1/20
1-3
Sequence number
SLN02
350
Assigned Identification
O AN 1/20
SLN03
662
Relationship Code
M ID 1/1
I
Included
S
Substituted
SLN04
380
Quantity
X R 1/15
Quantity shipped for the SKU referenced in this SLN segment
SLN05
C001
Composite Unit of Measure
X
-C00101
355
Unit or Basis for Measurement Code
M ID 2/2
Any value in the VICS Guidelines
-C00102 - C00115
SLN06
212
Unit Price
X R 1/17
SLN07
639
Basis of Unit Price Code
O ID 2/2
SLN08
662
Relationship Code
O ID 1/1
Ref.
Des.
SLN01
N/U
N/U
N/U
N/U
N/U
Orchard 856.2 Ver 4010.ecs
37
August 2008
Ship Notice / Manifest - 856
Ref.
Des.
SLN09
SLN10
SLN11
SLN12
SLN13
SLN14
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
SLN15
SLN16
SLN17
SLN18
SLN19
SLN20
SLN21
SLN22
SLN23
SLN24
SLN25
SLN26
SLN27
SLN28
Orchard 856.2 Ver 4010.ecs
Data
Element Name
Attributes
235
Product/Service ID Qualifier
X ID 2/2
IN
Supplier’s Item Number
UP
U.P.C. Consumer Package Code (1-5-5-1)
VN
Supplier’s (Seller's) Item Number
234
Product/Service ID
X AN 1/48
7–7
Orchard item number
12 - 12 U.P.C. number
1 - 15 Supplier’s item number
235
Product/Service ID Qualifier
X ID 2/2
See SLN09
234
Product/Service ID
X AN 1/48
See SLN10
235
Product/Service ID Qualifier
X ID 2/2
See SLN09
234
Product/Service ID
X AN 1/48
See SLN10
235
Product/Service ID Qualifier
X ID 2/2
234
Product/Service ID
X AN 1/48
235
Product/Service ID Qualifier
X ID 2/2
234
Product/Service ID
X AN 1/48
235
Product/Service ID Qualifier
X ID 2/2
234
Product/Service ID
X AN 1/48
235
Product/Service ID Qualifier
X ID 2/2
234
Product/Service ID
X AN 1/48
235
Product/Service ID Qualifier
X ID 2/2
234
Product/Service ID
X AN 1/48
235
Product/Service ID Qualifier
X ID 2/2
234
Product/Service ID
X AN 1/48
235
Product/Service ID Qualifier
X ID 2/2
234
Product/Service ID
X AN 1/48
38
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
Ref.
Des.
PRF01
N/U
N/U
PRF02
PRF03
PRF04
N/U
N/U
N/U
PRF05
PRF06
PRF07
Orchard 856.2 Ver 4010.ecs
PRF Purchase Order Reference
HL
Detail - Item
Conditional for Orchard
1
1.
For Orchard retail shipments (Pick and Pack structure only), the PRF at the item
level should be used only to reference the original purchase order for the product
specified in the associated LIN segment when multiple Orchard purchase orders are
packed in the same shipping container. In this case, each HL-I loop must contain a
PRF segment to report the Orchard PO and the PRF at the order level shall not be
used. The PRF at the item level and the PRF at the order level are mutually
exclusive. All merchandise packed in the same physical shipping container must be
marked for the same store and department.
Data Element Summary
Data
Element Name
324
Purchase Order Number
15 - 15 PO number
328
Release Number
327
Change Order Sequence Number
373
Date
Purchase order date
350
Assigned Identification
367
Contract Number
92
Purchase Order Type Code
39
Attributes
M AN 1/22
O
O
O
AN 1/30
AN 1/8
DT 8/8
O
O
O
AN 1/20
AN 1/30
ID 2/2
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
N/U
Ref.
Des.
TD501
TD502
TD503
TD504
TD505
TD506
TD507
TD508
TD509
TD510
TD511
TD512
TD513
TD514
TD515
Orchard 856.2 Ver 4010.ecs
TD5 Carrier Details (Routing Sequence/Transit Time)
HL
Detail - Item
Optional for Orchard
12
1.
For Orchard, this segment can be used to cancel the balance of an ordered quantity.
The LIN segment will specify the item/SKU shipped, SN1 will report the quantity
shipped and TD505 will be sent to cancel the balance of the ordered item.
Data Element Summary
Data
Element Name
Attributes
133
Routing Sequence Code
O ID 1/2
66
Identification Code Qualifier
X ID 1/2
67
Identification Code
X AN 2/80
91
Transportation Method/Type Code
X ID 1/2
387
Routing
X AN 1/35
368
Shipment/Order Status Code
X ID 2/2
CP
Partial Shipment, Considered No Backorder
309
Location Qualifier
O ID 1/2
310
Location Identifier
X AN 1/30
731
Transit Direction Code
O ID 2/2
732
Transit Time Direction Qualifier
O ID 2/2
733
Transit Time
X R 1/4
284
Service Level Code
X ID 2/2
284
Service Level Code
X ID 2/2
284
Service Level Code
O ID 2/2
26
Country Code
O ID 2/3
40
August 2008
Ship Notice / Manifest - 856
Segment:
Loop:
Level:
Usage:
Max Use:
Notes:
SE Transaction Set Trailer
Summary
Mandatory
1
1.
2.
Ref.
Des.
SE01
SE02
Orchard 856.2 Ver 4010.ecs
SE01 is a count of the total number of segments present in the transaction, including
the control segments.
SE02 must match the number in ST02.
Data Element Summary
Data
Element Name
96
Number of Included Segments
329
Transaction Set Control Number
41
Attributes
M N0 1/10
M AN 4/9
August 2008
Ship Notice / Manifest - 856
Segment Usage Examples
Orchard X-dock Shipments - Pick and Pack Structure
ST*856*Control number
BSN*00*Shipment ID number*Date*Time*0001
[Unique shipment ID, date and time of creation,
Pick and Pack structure]
HL*1**S
TD1**Lading quantity****G*Weight*LB
TD5**2*SCAC code
TD3*TL*Trailer prefix*Trailer number
REF*BM*B/L number
DTM*068*Scheduled ship date
DTM*011*Date shipped
N1*ST**92*Ship to unit number
N1*SF*Shipper name
[Begin Shipment level details]
[Lading quantity and gross weight per B/L]
[Carrier SCAC required]
[Trailer prefix and trailer number for TL shipments only]
[B/L number required]
[Scheduled ship date, if different from Actual ship date]
[Actual ship date]
[Ship to unit number from PO per B/L]
[Shipper name]
HL*HL ID number*1*O
PRF*PO number***PO date
PID*S**VI*FL
TD1**Total cartons****G*Weight*LB
REF*IA*Internal vendor number
N1*BY**92*Buying party
N1*Z7**92*Mark for unit
[Begin Order level details]
[PO reference if one PO per shipping container]
[FLSA compliance indicator]
[Carton count and weight for this order level]
[Internal vendor number from PO]
[Bill to unit number from PO]
[Mark for unit number from PO]
HL*HL ID number*Parent ID number*T
[Begin Tare level details]
MAN*GM*UCC-128 serial shipping container code [Pallet serial number]
HL*HL ID number*Parent ID number*P
[Begin Pack level details]
MAN*GM*UCC-128 serial shipping container code**CP*Tracking number
[Carton serial number (required) and tracking number (if
shipped via small package carrier)]
HL*HL ID number*Parent ID number*I
[Begin Item level details]
LIN**IN*Orchard item number*UP*U.P.C. number*VN*Vendor's item number*UK*Case code
[Item reference for product shipped]
SN1**Quantity shipped*Unit of measure
[Actual quantity shipped within pack]
SLN*SLN sequence number**Rel. code*Quantity*EA*Selling price*RE**IN*Orchard Item number
*UP*U.P.C. number
[Report substitutions]
PRF*PO number***PO date
[PO reference if more than one PO in shipping
container]
TD5***** *CP
[Report partial shipment, balance cancel]
SE*Count of segments*Control number
Orchard 856.2 Ver 4010.ecs
42
August 2008
Ship Notice / Manifest - 856
Segment Usage Examples
Orchard X-dock Shipments - Standard Carton Pack Structure (single SKU in a carton)
ST*856*Control number
BSN*00*Shipment ID number*Date*Time*0002
[Unique shipment ID, date and time of creation,
Standard Carton Pack structure]
HL*1**S
TD1**Lading quantity****G*Weight*LB
TD5**2*SCAC code
TD3*TL*Trailer prefix*Trailer number
REF*BM*Bill of lading number
DTM*068*Scheduled ship date
DTM*011*Date shipped
N1*ST**92*Ship to unit number
N1*SF*Shipper name
[Begin Shipment level details]
[Lading quantity and gross weight per B/L]
[Carrier SCAC required]
[Trailer prefix and trailer number for TL shipments only]
[B/L number required]
[Scheduled ship date, if different from Actual ship date]
[Actual ship date]
[Ship to unit number from PO - per B/L]
[Shipper name]
HL*HL ID number*1*O
PRF*PO number***PO date
PID*S**VI*FL
TD1**Total cartons****G*Weight*LB
REF*IA*Internal vendor number
N1*BY**92*Buying party
N1*Z7**92*Mark for unit
[Begin Order level details]
[PO reference]
[FLSA compliance indicator]
[Carton count and weight for this order level]
[Internal vendor number from PO]
[Bill to unit number from PO]
[Mark for unit number from PO]
HL*HL ID number*Parent ID number*I
[Begin Item level details]
LIN**IN*Orchard item number*UP *U.P.C. number*VN*Vendor's item number*UK*case code
[Item reference for product shipped]
SN1**Quantity shipped*Unit of measure
[Actual quantity shipped for all packs for this order]
SLN*SLN ID no.**Rel. code*Quantity*EA*Selling price*RE**IN*Orchard item number*UP*U.P.C. number
[Report substitutions]
TD5******CP
[Report partial shipment, balance cancel]
HL*HL ID number*Parent ID number*P
[Begin Pack level details]
PO4*Inner packs or eaches*************Number of eaches per inner pack
[Number of inner packs per carton or eaches if no inner
packs are used, Quantity of items per inner pack if
inner packs are used]
MAN*GM*UCC-128 serial shipping container code**CP*Tracking number
[Carton serial number (required) and tracking number (if
shipped via small package carrier)]
SE*Count of segments*Control number from ST
Orchard 856.2 Ver 4010.ecs
43
August 2008
Ship Notice / Manifest - 856
Segment Usage Examples
Orchard - No Pack Level
ST*856*Control number
BSN*00*Shipment ID number*Date*Time*0004
[Unique shipment ID, date and time of creation, No Pack
level structure code]
HL*1**S
TD1**Lading quantity****G*Weight*LB
TD5**2*SCAC code
TD3*TL*Trailer prefix*Trailer number
REF*BM*B/L number
DTM*068*Scheduled ship date
DTM*011*Date shipped
N1*ST**92*Ship to unit number
N1*SF*Shipper name
[Begin Shipment level details]
[Lading quantity and gross weight per B/L]
[Carrier SCAC required]
[Trailer number for truckload shipments only]
[B/L number required]
[Scheduled ship date, if different from Actual ship date]
[Actual ship date]
[Ship to unit number from Shipping Schedule - per B/L]
[Shipper name]
HL*HL ID number*1*O
PRF*PO number***PO date
PID*S**VI*FL
TD1**Total cartons****G*Weight*LB
REF*IA*Internal vendor number
N1*BY**92*Buying party
[Begin Order level details]
[PO reference]
[FLSA compliance indicator]
[Carton count and weight for this order level]
[Internal vendor number from Shipping Schedule]
[Bill to unit number from Shipping Schedule]
HL*HL ID number*Parent ID number*I
[Begin Item level details. Loop repeats once for each
Item/quantity shipped]
LIN**IN*Orchard item number*UP*U.P.C. number*VN*Vendor's item number*UK*Case code
[Item reference for product shipped]
SN1**Quantity shipped*Unit of measure
[Actual quantity shipped for all packs for this order]
SE*Count of segments*Control number from ST
Orchard 856.2 Ver 4010.ecs
44