856 Ship Notice and Manifest Transaction Set
Follow the guidelines in this article to use the Ship Notice and Manifest Transaction Set (856) in an EDI environment.
Note: You can also view this information in Word format: Walmart.com Drop Ship Vendor_856_4010_EDI.docx
Functional Group SH
This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use in an Electronic Data Interchange (EDI) environment. The transaction set can list the contents of a shipment of goods and 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 transaction's sender 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 interested in the contents of a shipment or information about the contents of a shipment.
Heading
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
---|---|---|---|---|---|---|---|
010 | ST | Transaction Set Header | M | 1 | Must use | ||
020 | BSN | Beginning Segment for Ship notice | M | 1 | Must use | ||
040 | DTM | Date/Time Reference | M | 10 | Must use |
Detail
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
---|---|---|---|---|---|---|---|
LOOP ID – HL | 200000 | ||||||
010 | HL | Hierarchical Level | M | 1 | LOOP ID – HL, C2/010 | Must Use | |
020 | LIN | Item Identification | M | 1 | LOOP ID – HL | Must Use | |
030 | SN1 | Item Detail (Shipment) | M | 1 | LOOP ID – HL | Must Use | |
050 | PRF | Purchase Order Reference | M | 1 | LOOP ID – HL | Must Use | |
110 | TD1 | Carrier Details (Quantity and Weight) | M | 20 | LOOP ID – HL | Must Use | |
120 | TD5 | Carrier Details (Routing Sequence/Transit Time) | M | 12 | LOOP ID – HL | Must Use | |
190 | MAN | Marks and Numbers | M | >1 | LOOP ID – HL | Dependent | |
LOOP ID – SAC | >1 | ||||||
320 | SAC | Service, Promotion, Allowance, or Charge Information | M | 1 | LOOP ID – SAC | Must use |
Summary
Pos | Id | Segment Name | Req | Max Use | Repeat | Notes | Usage |
---|---|---|---|---|---|---|---|
010 | CTT | Transaction Totals | O | 1 | N3/010 | Must use | |
020 | SE | Transaction Set Trailer | M | 1 | Must use |
Notes
- N3/010: The number of line items (CTT01) is the accumulation of the number of HL segments.
Sample Spec 856 Files
S2HS2SS2HS2S
ISA*00* *00* *12*8478505336 *01*12571829*070424*0757*U*00401*000000008*0*P*>
GS*SH*8478505336*12571829*20070424*0757*8*X*004010
ST*856*0001
BSN*00*1584552300*20070424*0755
DTM*011*20070312*1521*ET
HL*1*0*O
PRF*12635837******DS
HL*2*1*P
TD1******G*1.5*LB
TD5*O*94*02
MAN*CP*1ZR580970342882215
MAN*SM*8890500613298
SAC*N*G821******0****06
HL*3*2*I
LIN*1*PL*1
SN1*1*1*EA
CTT*3
SE*16*0001
GE*1*8
IEA*1*000000008
ST Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Usage Option: Must use
- Pos: 010
- Max: 1
- Heading – Mandatory
- Loop: N/A
- Elements: 2
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
ST01 | 143 | Transaction Set Identifier Code | M | ID | 3/3 | 856 | Ship Notice/Manifest |
ST02 | 329 | Transaction Set Control Number | M | AN | 4/9 |
BSN Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set.
- Pos: 020
- Max: 1
- Heading – Mandatory
- Loop: N/A
- Elements: 4
- Usage Option: Must use
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
BSN01 | 353 | Transaction Set Purpose Code | M | ID | 2/2 | 00 | Original |
BSN02 | 396 | Shipment Identification | M | AN | 2/30 | see notes | |
BSN03 | 373 | Date | M | DT | 8/8 | ||
BSN04 | 337 | Time | M | TM | 4/8 |
Segment Notes
- BSN02: Unique numeric identifier for this shipment, assigned by the supplier
- BSN03: Date the Transaction Set was created
- BSN04: Time the Transaction Set was created
DTM Date/Time Reference
To specify pertinent dates and times
Usage Option: Must use
- Pos: 040
- Max: 10
- Heading – Optional
- Loop: N/A
- Elements: 4
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
DTM01 | 374 | Date/Time Qualifier | M | ID | 3/3 | 011 | shipped |
DTM02 | 373 | Date | M | DT | 8/8 | ||
DTM03 | 337 | Time | M | TM | 4/8 | ||
DTM04 | 623 | Time Zone Qualifier | M | ID | 2/2 | see notes |
Segment Notes
Time Zone Values (North America/Europe):
- ET: Eastern Time
- CT: Central Time
- MT: Mountain Time
- PT: Pacific Time
- ED: Eastern Daylight Time
- CD: Central Daylight Time
- MD: Mountain Daylight Time
- PD: Pacific Daylight Time
- GM: Greenwich Mean Time (GMT England)
Example: DTM*011*20080708*1150*PT~
HL Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
Usage Option: Must use
- Pos: 010
- Max: 1
- Detail – Mandatory
- Loop: HL
- Elements: 3
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
HL01 | 628 | Hierarchical ID Number | M | AN | 1/12 | see notes | |
HL02 | 734 | Hierarchical Parent ID Number | M | AN | 1/12 | see notes | |
HL03 | 735 | Hierarchical Level Code | M | ID | 1/2 | see notes |
Segment Notes
- HL01: Numeric sequence number to uniquely identify this HL segment within the transaction set
- HL02:
- If HL03 = “O”, this value is “0” (zero)
- If HL03 = “P”, this value is the ID Number (HL01) from the associated order HL
- If HL03 = “I”, this value is the ID Number (HL01) from the associated package HL
- HL03:
- I: Item
- O: Order
- P: Pack
LIN Item Identification
To specify basic item identification data
Usage Option: Must use
- Pos: 020
- Max: 1
- Detail – Optional
- Loop: HL
- Elements: 5
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
LIN01 | 350 | Assigned Identification | M | AN | 1/20 | see notes | |
LIN02 | 235 | Product/Service ID Qualifier | M | ID | 2/2 | PL | Purchaser’s Order Line Number |
LIN03 | 234 | Product/Service ID | M | AN | 1/48 | see notes | |
LIN04 | N/A | Product/Service ID | O | ID | 2/2 | see notes | |
LIN05 | N/A | Product/Service ID | O | AN | 1/48 | see notes |
Segment Notes
Contains the purchase order line number, only used in the line hierarchical level (HL03 = “I”).
Can (optional) contain the store number ID and store number only in the line hierarchical level (HL03 = “I”).
- LIN01: Numeric sequence number to uniquely identify this LIN segment within the transaction set
- LIN03: Purchase Order Line Number (PO101) from the original 850 PO
- LIN04: Is used to indicate Store Number Identifier “SN”
- LIN05: Is used to indicate the actual Store Number
SN1 Item Detail (Shipment)
To specify line-item detail relative to shipment
Usage Option: Must use
- Pos: 030
- Max: 1
- Detail – Optional
- Loop: HL
- Elements: 3
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
SN101 | 350 | Assigned Identification | M | AN | 1/20 | see notes | |
SN102 | 382 | Number of Units Shipped | M | R | 1/10 | ||
SN103 | 355 | Unit or Basis for Measure Code | M | ID | 2/2 | EA | Each |
Segment Notes
Contains the number of units shipped, only used in the line hierarchical level (HL03 = “I”).
- SN101: Numeric sequence number to uniquely identify this SN1 segment within the transaction set. Can be the same as the LIN01 ID Number within this HL loop.
PRF Purchase Order Reference
To provide reference to a specific purchase order Usage Option: Must use
- Pos: 050
- Max: 1
- Detail – Optional
- Loop: HL
- Elements: 2
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
PRF01 | 324 | Purchase Order Number | M | AN | 1/22 | see notes | |
PRF07 | 92 | Purchase Order Type Code | M | ID | 2/2 | DS | Dropship |
Segment Notes
Contains a reference to the purchase order number, only used in the order hierarchical level (HL03 = “O”).
- PRF01: Purchase Order Number (BEG03) from the original 850 PO
TD1 Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity Usage Option: Must use
- Pos: 110
- Max: 20
- Detail – Optional
- Loop: HL
- Elements: 3
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
TD106 | 187 | Weight Qualifier | M | ID | 1/2 | G | Gross Weight |
TD107 | 81 | Weight | M | R | 1/10 | ||
TD108 | 355 | Unit or Basis for Measurement Code | M | ID | 2/2 | LB | Pound |
Segment Notes
Contains the package weight, which must be used in the package hierarchical level (HL03 = “P”).
TD5 Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information.
Usage Option: Must use
- Pos: 120
- Max: 12
- Detail – Optional
- Loop: HL
- Elements: 3
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
TD501 | 133 | Routing Sequence Code | M | ID | 1/2 | O | Origin Carrier (Air, Motor, or Ocean) |
TD502 | 66 | Identification Code Qualifier | M | ID | 1/2 | 94 | see notes |
TD503 | 67 | Identification Code | M | AN | 2/80 | see notes |
Segment Notes
Contains the package shipping method, which must be used in the package hierarchical level (HL03 = “P”).
-
TD502: Code assigned by the organization that is the ultimate destination of the transaction set
-
TD503 can use one of the following codes:
CMID XML Carrier Method Name CARRIER 9 9 UPS Second Day Air UPS 17 17 Common Carrier Common Carrier 18 18 FedEx Freight FedEx 19 19 FedEx Express Saver (3-Day Service) FedEx 20 20 FedEx Ground FedEx 21 21 FedEx Priority Overnight FedEx 22 22 FedEx 2-Day FedEx 24 24 FedEx Standard Overnight (PM Delivery) FedEx 31 31 USPS Priority Mail USPS 43 43 Pilot Freight Basic Delivery Pilot 65 65 FedEx Smartpost Over 1lb Smartpost 66 66 FedEx Smartpost Under 1lb Smartpost 67 67 FedEx Home Delivery FedEx 68 20 FedEx Ground FedEx 79 79 FedEx Ground – S2S FedEx 80 80 UPS Ground – S2S UPS 82 82 Seko Worldwide Seko 90 90 Yellow Freight System – S2S YRC 97 97 UPS Second Day Air – S2S UPS 98 98 Downloads In-Store Pickup 143 43 Pilot Freight Room of Choice Delivery Pilot 155 55 Estes Forwarding Worldwide Basic Delivery Estes 223 22 FedEx 2-Day FedEx 243 43 Pilot Freight White-Glove Pilot 255 55 Estes Forwarding Worldwide Basic Delivery Estes 267 67 FedEx Home Delivery FedEx 355 55 Estes Forwarding Worldwide Room of Choice Delivery Estes 443 43 Pilot Freight Unattended Delivery Pilot 501 2 UPS Ground UPS 545 146 NSD for DSV Non-Stop Delivery 6761 20 FedEx Ground Cold Split FedEx 6762 67 FedEx Home Delivery Cold Split FedEx 6763 20 FedEx Ground Cold Split FedEx 6764 67 FedEx Home Delivery Cold Split FedEx 6766 801 FedEx Ground Hot Split FedEx 6767 802 FedEx Home Delivery Hot Split FedEx 6768 801 FedEx Ground Hot Split FedEx 6769 802 FedEx Home Delivery Hot Split FedEx
MAN Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Must use for MAN*CP and MAN*SM
- Pos: 190
- Max: >1
- Detail – Optional
- Loop: HL
- Elements: 2
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
MAN01 | 88 | Marks and Numbers Qualifier | M | ID | 1/2 | see notes | |
TD503 | 67 | Identification Code | M | AN | 2/80 | see notes |
Segment Notes
Contains the package identification numbers, only used in the package hierarchical level (HL03 = “P”).
- MAN01 can accept several codes:
- CP: Carrier-Assigned Package ID Number
- SM: Shipper Assigned
- GM: SSCC-18 Bar code
- MAN02:
- If MAN01 = “CP, then this is the tracking number assigned by the carrier. Required for all packages, both Site to Home and Site to Store.
- If MAN01 = “SM”, then this is a unique package ID assigned by the supplier. Required for all packages, both Site to Home and Site to Store. Can be the same value as in MAN-02 when MAN-01=”CP”.
- If MAN01 = “GM”, then this is a vendor-assigned 20-digit SSCC-18 bar code number. Must for only Site to Store packages. Do not send this for Site to Home packages.
SAC Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge Usage Option: Must use
- Pos: 320
- Max: 1
- Detail – Optional
- Loop: SAC
- Elements: 5
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
SAC01 | 248 | Allowance or Charge Indicator | M | ID | 1/1 | N | No Allowance or Charge |
SAC02 | 1300 | Service, Promotion, Allowance, or Charge Code | X | ID | 4/4 | see notes | |
SAC08 | 118 | Rate | M | R | 1/9 | Can be defaulted to zero | |
SAC12 | 331 | Allowance or Charge Method of Handling Code | M | ID | 2/2 | see notes | |
SAC15 | 352 | Description | X | AN | 1/80 | see notes |
Segment Notes
Contains the information about related costs.
Shipping costs (SAC02 = “G821”) are mandatory and are reported on the package hierarchical level (HL03 = “P”).
Handling and special service costs (SAC02 = “D500” and “H151”) are optional and are reported on the item hierarchical level (HL03 = “I”).
- SAC02 codes:
- D500: Handling
- G821: Shipping (Must Use)
- H151: Special Services
- SAC02 codes:
- If SAC02 = “G821”, then the shipping cost can be paid by Walmart.com to the vendor (SAC12 = “06”) or directly to the carrier (SAC12 = “15”). Otherwise, the costs are paid to the vendor (SAC12 = “06”).
- 06: Charge to be Paid by Customer
- 15: Information Only
- SAC15 codes:
- If SAC02 = “H151”, then this field contains the VAS code associated with the special service. Otherwise, this element is not used.
- VGM: Gift Message (Up to 4 Lines)
- VGT: Gift Tag (To/From)
- VGW: Gift Wrapping
CTT Transaction Totals
To transmit a hash total for a specific element in the transaction set
Usage Option: Must Use
- Pos: 010
- Max: 1
- Summary – Optional
- Loop: N/A
- Elements: 1
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
CTT01 | 354 | Count of the Number of HL levels | M | N0 | 1/6 |
SE Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Usage Option: Must Use
- Pos: 030
- Max: 1
- Summary – Mandatory
- Loop: N/A
- Elements: 2
Element Summary
Ref | Id | Element Name | Req | Type | Min/Max | Code | Name |
---|---|---|---|---|---|---|---|
SE01 | 96 | Number of Included Segments | M | N0 | 1/10 | ||
SE02 | 329 | Transaction Set Control Number | M | AN | 4/9 |
Updated about 2 months ago