856 Ship Notice/Manifest: Version: 1.3 Final

856 Ship Notice/Manifest
X12/V4010/856 : 856 Ship Notice/Manifest
Version: 1.3 Final
Publication: 2/29/2016
Notes:
2/10/2016 Ship Notice/Manifest - 856
Table of Contents
856 Ship Notice/Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 1
ISA Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 3
GS Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 6
ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . . 8
BSN Beginning Segment for Ship Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . . 9
DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 11
HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 12
MEA Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 13
TD1 Carrier Details (Quantity and Weight) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 15
TD3 Carrier Details (Equipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 22
REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 23
N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 24
N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 25
SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 26
HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 28
LIN Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 29
SN1 Item Detail (Shipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 31
SLN Subline Item Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 32
PRF Purchase Order Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 34
REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 35
CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 36
SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 37
GE Functional Group Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 38
IEA Interchange Control Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 39
MIG_856_4010.ecs i For internal use only


Functional Group= SH
Purpose: 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.
Not Defined:
Pos Id Segment Name Req Max Use Repeat Notes Usage
ISA Interchange Control Header M 1 Must use
GS Functional Group Header M 1 Must use
Heading:
010 ST Transaction Set Header M 1 Must use
020 BSN Beginning Segment for Ship M 1 Must use
Notice
040 DTM Date/Time Reference O 10 Used
Detail:
LOOP ID - HL 200000 CN2/010L
010 HL Hierarchical Level M 1 C2/010 Must use
080 MEA Measurements O 40 Used
110 TD1 Carrier Details (Quantity O 20 Used
and Weight)
130 TD3 Carrier Details (Equipment) O 12 Used
150 REF Reference Identification O >1 Used
LOOP ID - N1 200
220 N1 Name O 1 Used
LOOP ID - N1 200
220 N1 Name O 1 Used
LOOP ID - SAC >1

320 SAC Service, Promotion, O 1 Used
Allowance, or Charge
Information
LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level M 1 C2/010 Must use
020 LIN Item Identification O 1 Used
030 SN1 Item Detail (Shipment) O 1 Used
040 SLN Subline Item Detail O 1000 Used
MIG_856_4010.ecs 1 For internal use only


050 PRF Purchase Order Reference O 1 Used
150 REF Reference Identification O >1 Used
Summary:
010 CTT Transaction Totals O 1 N3/010 Used
020 SE Transaction Set Trailer M 1 Must use
Not Defined:
GE Functional Group Trailer M 1 Must use
IEA Interchange Control Trailer M 1 Must use
Notes:
2/010L Shipment Level
3/010 Number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total
(CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Comments:
2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no
meaning.
2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no
meaning.
2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no
meaning.
2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no
meaning.

Pos: Max: 1
ISA Interchange Control Header Not Defined - Mandatory
Loop: N/A Elements: 16
User Option (Usage): Must use

Purpose: To start and identify an interchange of zero or more functional groups and interchange-related control
segments
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
ISA01 I01 Authorization Information Qualifier M ID 2/2 Must use
Description: Code to identify the type of

information in the Authorization
Information
CodeList Summary (Total Codes: 7, Included: 1)

Code Name
00 No Authorization Information Present (No Meaningful Information in I02)
ISA02 I02 Authorization Information M AN 10/10 Must use
Description: Information used for

additional identification or authorization of
the interchange sender or the data in the
interchange; the type of information is set
by the Authorization Information Qualifier
(I01)
ISA03 I03 Security Information Qualifier M ID 2/2 Must use
Description: Code to identify the type of

information in the Security Information
ISA04 I04 Security Information M AN 10/10 Must use
Description: This is used for identifying

the security information about the
interchange sender or the data in the
interchange; the type of information is set
by the Security Information Qualifier (I03)
ISA05 I05 Interchange ID Qualifier M ID 2/2 Must use
Description: Qualifier to designate the

system/method of code structure used to
designate the sender or receiver ID
element being qualified
ISA06 I06 Interchange Sender ID M AN 15/15 Must use
Description: Identification code

published by the sender for other parties
to use as the receiver ID to route data to
them; the sender always codes this value
in the sender ID element
ISA07 I05 Interchange ID Qualifier M ID 2/2 Must use
Description: Qualifier to designate the

system/method of code structure used to


designate the sender or receiver ID
element being qualified
ISA08 I07 Interchange Receiver ID M AN 15/15 Must use
Description: Identification code

published by the receiver of the data;
When sending, it is used by the sender as
their sending ID, thus other parties
sending to them will use this as a
receiving ID to route data to them
ISA09 I08 Interchange Date M DT 6/6 Must use
Description: Date of the interchange
ISA10 I09 Interchange Time M TM 4/4 Must use
Description: Time of the interchange
ISA11 I10 Interchange Control Standards M ID 1/1 Must use

Identifier
Description: Code to identify the agency

responsible for the control standard used
by the message that is enclosed by the
interchange header and trailer
All valid standard codes are used.
(Total Codes: 1)
ISA12 I11 Interchange Control Version Number M ID 5/5 Must use
Description: Code specifying the version

number of the interchange control
segments
ISA13 I12 Interchange Control Number M N0 9/9 Must use
Description: A control number assigned

by the interchange sender
ISA14 I13 Acknowledgment Requested M ID 1/1 Must use
Description: Code sent by the sender to

request an interchange acknowledgment
(TA1)
ISA15 I14 Usage Indicator M ID 1/1 Must use
Description: Code to indicate whether

data enclosed by this interchange
envelope is test, production or information
ISA16 I15 Component Element Separator M 1/1 Must use
Description: Type is not applicable; the

component element separator is a
delimiter and not a data element; this field
provides the delimiter used to separate
component data elements within a
composite data structure; this value must
be different than the data element
separator and the segment terminator

Example:
Enveloping Segment, No information needed by user

Pos: Max: 1
GS Functional Group Header Not Defined - Mandatory

Purpose: To indicate the beginning of a functional group and to provide control information
Element Summary:
GS01 479 Functional Identifier Code M ID 2/2 Must use
Description: Code identifying a group of

application related transaction sets

Code Name
SH Ship Notice/Manifest (856)
GS02 142 Application Sender's Code M AN 2/15 Must use
Description: Code identifying party

sending transmission; codes agreed to by
trading partners
GS03 124 Application Receiver's Code M AN 2/15 Must use
Description: Code identifying party

receiving transmission; codes agreed to
by trading partners
GS04 373 Date M DT 8/8 Must use
Description: Date expressed as

CCYYMMDD
GS05 337 Time M TM 4/8 Must use
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)
GS06 28 Group Control Number M N0 1/9 Must use
Description: Assigned number originated

and maintained by the sender
GS07 455 Responsible Agency Code M ID 1/2 Must use
Description: Code identifying the issuer

of the standard; this code is used in
conjunction with Data Element 480
All valid standard codes are used.
(Total Codes: 2)


GS08 480 Version / Release / Industry Identifier M AN 1/12 Must use
Code
Description: Code indicating the version,

release, subrelease, and industry
identifier of the EDI standard being used,
including the GS and GE segments; if
code in DE455 in GS segment is X, then
in DE 480 positions 1-3 are the version
number; positions 4-6 are the release and
subrelease, level of the version; and
positions 7-12 are the industry or trade
association identifiers (optionally assigned
by user); if code in DE455 in GS segment
is T, then other formats are allowed

Code Name
004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board
through October 1997
Semantics:
1. GS04 is the group date.
2. GS05 is the group time.
3. The data interchange control number GS06 in this header must be identical to the same data element in the
associated functional group trailer, GE02.
Comments:
1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of
similar transaction sets enclosed by a functional group header and a functional group trailer.
Example:

Pos: 010 Max: 1

ST Transaction Set Header Heading - Mandatory

Purpose: To indicate the start of a transaction set and to assign a control number
Element Summary:
ST01 143 Transaction Set Identifier Code M ID 3/3 Must use
Description: Code uniquely identifying a

Transaction Set

Code Name
ST02 329 Transaction Set Control Number M AN 4/9 Must use
Description: Identifying control number

that must be unique within the transaction
set functional group assigned by the
originator for a transaction set
Semantics:
1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the
appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
Example:

Pos: 020 Max: 1

BSN Beginning Segment for Ship Heading - Mandatory
Notice Loop: N/A Elements: 4

Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set
Element Summary:
BSN01 353 Transaction Set Purpose Code M ID 2/2 Must use
Description: Code identifying purpose of

transaction set

Code Name
00 Original
BSN02 396 Shipment Identification M AN 2/30 Must use
Description: A unique control number

assigned by the original shipper to identify
a specific shipment
BSN03 373 Date M DT 8/8 Must use

CCYYMMDD
Note: Transaction Date
BSN04 337 Time M TM 4/8 Must use

hundredths (00-99)
Note: Transaction Time
Syntax Rules:
1. C0706 - If BSN07 is present, then BSN06 is required.
Semantics:
1. BSN03 is the date the shipment transaction set is created.
2. BSN04 is the time the shipment transaction set is created.
3. BSN06 is limited to shipment related codes.
Comments:
1. BSN06 and BSN07 differentiate the functionality of use for the transaction set.
Example:

BSN*00*A0139*20150223*1331

Pos: 040 Max: 10

DTM Date/Time Reference Heading - Optional
User Option (Usage): Used

Purpose: To specify pertinent dates and times
Element Summary:
DTM01 374 Date/Time Qualifier M ID 3/3 Must use
Description: Code specifying type of date

or time, or both date and time

Code Name
011 Shipped
DTM02 373 Date X DT 8/8 Used

CCYYMMDD
Note: Shipped Date
DTM03 337 Time X TM 4/8 Used

hundredths (00-99)
Note: Shipped Time
Syntax Rules:
1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.
2. C0403 - If DTM04 is present, then DTM03 is required.
3. P0506 - If either DTM05 or DTM06 is present, then the other is required.
Example:
DTM*011*20150219*1731

Pos: 010 Max: 1

HL Hierarchical Level Detail - Mandatory
Loop: HL Elements: 2

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments
Element Summary:
HL01 628 Hierarchical ID Number M AN 1/12 Must use
Description: A unique number assigned

by the sender to identify a particular data
segment in a hierarchical structure
HL03 735 Hierarchical Level Code M ID 1/2 Must use
Description: Code defining the

characteristic of a level in a hierarchical
structure

Code Name
S Shipment
Comments:
1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating
line-item data to shipment data, and packaging data to line-item data.
2. The HL segment defines a top-down/left-right ordered structure.
3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction
set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which
case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each
subsequent HL segment within the transaction.
4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
5. HL03 indicates the context of the series of segments following the current HL segment up to the next
occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent
segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL
segment.
Example:
HL*1**S

Pos: 080 Max: 40

MEA Measurements Detail - Optional

Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and
weights(See Figures Appendix for example of use of C001)
Element Summary:
MEA01 737 Measurement Reference ID Code O ID 2/2 Used
Description: Code identifying the broad

category to which a measurement applies

Code Name
PD Physical Dimensions
MEA02 738 Measurement Qualifier O ID 1/3 Used
Description: Code identifying a specific

product or process characteristic to which
a measurement applies

Code Name
G Gross Weight
MEA03 739 Measurement Value X R 1/20 Used
Description: The value of the

measurement
Note: Container Weight
Nissan Usage: Mandatory Field for
Nissan ASN
MEA04 C001 Composite Unit of Measure X Comp Used
Description: To identify a composite unit

of measure(See Figures Appendix for
examples of use)
MEA04-01 355 Unit or Basis for Measurement Code M ID 2/2 Must use
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
Syntax Rules:
1. R03050608 - At least one of MEA03, MEA05, MEA06 or MEA08 is required.

2. C0504 - If MEA05 is present, then MEA04 is required.

3. C0604 - If MEA06 is present, then MEA04 is required.
4. L07030506 - If MEA07 is present, then at least one of MEA03, MEA05 or MEA06 is required.
5. E0803 - Only one of MEA08 or MEA03 may be present.
Semantics:
1. MEA04 defines the unit of measure for MEA03, MEA05, and MEA06.
Comments:
1. When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a
positive (+) value cannot be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+)
value.
Example:
MEA*PD*G*2739*KG

Pos: 110 Max: 20

TD1 Carrier Details (Quantity and Detail - Optional
Weight) Loop: HL Elements: 2

Purpose: To specify the transportation details relative to commodity, weight, and quantity
Element Summary:
TD101 103 Packaging Code O AN 3/5 Used
Description: Code identifying the type of

packaging; Part 1: Packaging Form, Part
2: Packaging Material; if the Data Element
is used, then Part 1 is always required
Note: Rack Type
Nissan ASN

Code Name
AMM Ammo Pack
AMP Ampoule
ATH Attachment
Description: In containers and shipping devices, a component that can be added
to provide additional functionality or security as required by the contents or method
of transportation/handling
BAG Bag
BAL Bale
BBL Barrel
BDG Banding
Description: Something that binds, ties, or encircles the package/container to
secure and maintain unit integrity
BDL Bundle
BEM Beam
BIC Bing Chest
BIN Bin
BLK Bulk
BLT Belting
Description: As pertains to containers and shipping devices, a method of securing
the contents to the conveyance device (or securing components of the shipping
device to each other) using one or more bands of flexible material having
high-tensile strength and a buckle or ratchet device for removing slack and
maintaining tension
BOB Bobbin
BOT Bottle
BOX Box
BRC Bracing
Description: Material or devices used to hold articles or sections of loads in
position to prevent shifting during transportation

Code Name
BRG Barge
BSK Basket or hamper
BXI Box, with inner container
BXT Bucket
CAB Cabinet
CAG Cage
CAN Can
CAR Carrier
CAS Case
CBC Containers of Bulk Cargo
CBY Carboy
CCS Can Case
CHE Cheeses
CHS Chest
CLD Car Load, Rail
CNA Household Goods Container, Wood
CNB Container, MAC-ISO, LT. WGT. 8x8x20 Foot Air
CNC Container, Navy Cargo Transporter
CND Container, Commercial Highway Lift
CNE Container, Engine
CNF Container, Multi-walled, Secured to Warehouse Pallet
CNT Container
COL Coil
CON Cones
COR Core
CRD Cradle
CRF Corner Reinforcement
Description: Usually in boxes or crates, additional material or components
attached to adjacent panels to add support or prevent crushing or separation
CRT Crate
CSK Cask
CTN Carton
CX2 CONEX
Description: A reusable container for shipment of cargo
CYL Cylinder
DBK Dry Bulk
DRK Double-length Rack
DRM Drum
DSK Double-length Skid
DTB Double-length Tote Bin
DUF Duffelbag
EGG Egg Crating
Description: In containers and shipping devices, usually describes a type of
interior dunnage which allows the contents to be individually segregated,
horizontally and vertically, to provide protection during transportation and storage
ENV Envelope
EPR Edge Protection

Code Name
Description: A right-angle piece placed over the outermost perimeter edges of a
container to distribute pressure and prevent collapse or cutting from banding,
strapping, or handling
FIR Firkin
FLO Flo-bin
FRM Frame
FSK Flask
FWR Forward Reel
HED Heads of Beef
HGH Hogshead
HPR Hamper
HPT Hopper Truck
HRB On Hanger or Rack in Boxes
HRK Half-Standard Rack
HTB Half-Standard Tote Bin
INT Intermediate Container
JAR Jar
KEG Keg
KIT Kit
KRK Knockdown Rack
KTB Knockdown Tote Bin
LBK Liquid Bulk
LID Lip/Top
Description: In packaging, the top or bottom of a container, usually the part that
closes the opening; may also be known as cap, over, or top
LIF Lifts
LNR Liners
Description: Any material that separates a product within a container from the
basic walls of the container
LOG Log
LSE Loose
LUG Lug
LVN Lift Van
MIX Mixed Container Types
Description: More than one type of container is included in a shipment (shipment
could consist of 3 pieces that include 1 box, 1 crate, and 1 basket)
ML2 MILVAN
Description: A military owned demountable container that conforms to US and
international standards and operates in a centrally controlled fleet for movement of
military cargo
MRP Multi-Roll Pack
MS2 MSCVAN
Description: A commercial (leased) or Government-owned shipping container
controlled by the Military Sealift Command
MXD Mixed
NOL Noil
PAF Pallet - 4 Way
Description: A pallet that permits entry of handling equipment on each of its four

Code Name
sides
PAL Pail
PAT Pallet - 2 Way
Description: A pallet that permits entry of handling equipment on opposing two of
its four sides
PCK Packed - not otherwise specified
PCS Pieces
PIR Pirns
PKG Package
PLC Primary Lift Container
Description: The largest (outermost) unitized package or articles secured together
that can be handled (usually mechanically) in common shop floor/warehouse
applications as a single entity; "primary" indicates preferred or mandatory
PLF Platform
PLN Pipeline
PLT Pallet
POV Private Vehicle
PRK Pipe Rack
PRT Partitioning
Description: The proceeds of applying separators or dividers
PWT Plastic-Wrapped Tray
QTR Quarter of Beef
RAL Rail (Semiconductor)
RCK Rack
REL Reel
RFT Reinforcement
Description: In containers and shipping devices, a component (usually temporary)
added to a container for a particular application to lend additional support under
severe applications
ROL Roll
RVR Reverse Reel
SAK Sack
SCS Suitcase
SHK Shook
SHT Sheet
Description: A thin layer of material usually used as a pad for extra protection by
isolating/separating tiers or layers of parts within the package
SID Side of Beef
SKD Skid
SKE Skid, elevating or lift truck
SLP Slip Sheet
Description: Shipping containers utilizing slip sheets, which are cardboard
platforms used to hold product for storage or transportation
SLV Sleeve
SPI Spin Cylinders
SPL Spool
SPR Separator/Divider
Description: In packaging, any material inserted between tiers or layers of articles

Code Name
to prevent contact and provide protection
SRW Shrink Wrap
Description: In packaging, a method of securing a unit load by placing a large
"bag" of plastic film over the components and applying heat to induce shrinkage
and cause the bag to tighten around the contents
STW Stretch Wrap
Description: In packaging, a high-tensile plastic film, stretched and wrapped
repeatedly around a unitized load to secure and maintain unit integrity
SV2 SEAVAN
Description: A commercial or government-owned (or leased) shipping container
which is moved via ocean transportation without wheels attached and is lifted on
and off a ship
TBE Tube
TBN Tote Bin
TKR Tank Car
TKT Tank Truck
TLD Intermodal Trailer/Container Load (Rail)
TNK Tank
TRC Tierce
TRK Trunk and Chest
TRU Truck
TRY Tray
TSS Trunk, Salesmen Sample
TUB Tub
UNP Unpacked
UNT Unit
VEH Vehicles
VIL Vial
VOC Vehicle in Operating Condition
VPK Van Pack
WHE On Own Wheel
WLC Wheeled Carrier
WRP Wrapped
Code Name
01 Aluminum
04 As Specified by the DOT
07 Burlap
10 Chemically Hardened Fibre
13 Cloth
16 Cloth Top
19 Cloth or Fabric
22 Compressed
25 Corrugated or Solid
28 Double-wall Paper
31 Fibre
34 Fibre (Paperboard)

Code Name
37 Fiberboard
40 Fiberboard Metal
43 Glass
46 In Inner Containers
48 Wire/Cord
Description: Something that binds, ties, or encircles the package/container to
secure and maintain unit integrity
49 Insulated
50 Steel - Vinyl Coated
Description: Steel that has been covered with a plastic material
51 Wire Mesh
52 Iron or Steel
53 Jumbo
54 Special Jumbo
55 Lead
58 Metal
59 Metal Cans
61 Moisture Resistant
64 Molded Plastic
67 Multiple-wall Paper (2 or more walls)
70 Multiple-wall Paper (3 or more walls)
71 Not Otherwise Specified
72 Paper - VCI
Description: Water-resistant paper that is treated by the addition of materials to
provide resistance to damage or deterioration by water in liquid form
73 Other than Glass
74 Other than Metal or Plastic Tubes, or Glass
75 Plastic - Vacuum Formed
Description: Packaging material that is formed by heating plastic sheet and
drawing it against the mold surface by evacuating the air between the sheet and the
mold
76 Paper
77 Plastic - Structural Foam
Description: A method of manufacturing containers and shipping devices by
mixing plastic resins with a foaming agent, heating it and injecting the mix into a
two-piece machined aluminum mold
78 Plastic - Injection Molded
Description: Packaging material that is formed by melting the material and then
forcing it under pressure into a cavity of a closed mold
79 Plastic
80 Polyethylene Lined
81 Plastic - Virgin
Description: Plastic in the form of pellets, granules, powder, floc, or liquid that has
not been subjected to use or processing other than for its initial manufacture
82 Pulpboard
83 Plastic - Regrind
Description: A plastic prepared from discarded articles that have been
reprocessed, often changing some of its original properties

Code Name
84 Polystyrene
Description: A polymer prepared by the polymerization of styrene as the sole
monomer
85 Rubber
86 Foam
Description: In packaging, a cushioning material used to reduce shock and
vibration or abrasion
88 Rubber and Fabric
89 Special
90 Standard
91 Stainless Steel
92 Tubes, Metal or Plastic
94 Wood
95 Single Wall Corrugated Board
Description: The structure formed by one corrugated inner member between two
flat facings; also known as double face
96 Double Wall Corrugated Board
Description: The structure formed by three flat facings and two intermediate
corrugated members
97 Triple Wall Corrugated Board
Description: The structure formed by four flat facings and three intermediate
corrugated members
TD102 80 Lading Quantity X N0 1/7 Used
Description: Number of units (pieces) of

the lading commodity
Note: Rack Quantity
Nissan ASN
Syntax Rules:
1. C0102 - If TD101 is present, then TD102 is required.
4. P0708 - If either TD107 or TD108 is present, then the other is required.
Example:
TD1*PLT90*23478

Pos: 130 Max: 12

TD3 Carrier Details (Equipment) Detail - Optional

Purpose: To specify transportation details relating to the equipment used by the carrier
Element Summary:
TD301 40 Equipment Description Code X ID 2/2 Used
Description: Code identifying type of

equipment used for shipment

Code Name
TL Trailer (not otherwise specified)
TD302 206 Equipment Initial O AN 1/4 Used
Description: Prefix or alphabetic part of

an equipment unit's identifying number
Note: Trailer Container Number
Nissan ASN
TD303 207 Equipment Number X AN 1/10 Used
Description: Sequencing or serial part of

an equipment unit's identifying number
(pure numeric form for equipment number
is preferred)
Note: Trailer Container
Nissan ASN
Syntax Rules:
1. E0110 - Only one of TD301 or TD310 may be present.
Example:
TD3*TL*1030*2096302

Pos: 150 Max: >1

REF Reference Identification Detail - Optional

Purpose: To specify identifying information
Element Summary:
REF01 128 Reference Identification Qualifier M ID 2/3 Must use
Description: Code qualifying the

Reference Identification

Code Name
IV Seller's Invoice Number
REF02 127 Reference Identification X AN 1/30 Used
Description: Reference information as

defined for a particular Transaction Set or
as specified by the Reference
Identification Qualifier
Note: Invoice Number
Nissan ASN
Syntax Rules:
1. R0203 - At least one of REF02 or REF03 is required.
Semantics:
1. REF04 contains data relating to the value cited in REF02.
Example:
REF*IV*8128946

Pos: 220 Max: 1

N1 Name Detail - Optional
Loop: N1 Elements: 3

Purpose: To identify a party by type of organization, name, and code
Element Summary:
N101 98 Entity Identifier Code M ID 2/3 Must use
Description: Code identifying an

organizational entity, a physical location,
property or an individual

Code Name
SU Supplier/Manufacturer
N103 66 Identification Code Qualifier X ID 1/2 Used
Description: Code designating the

system/method of code structure used for
Identification Code (67)

Code Name
92 Assigned by Buyer or Buyer's Agent
N104 67 Identification Code X AN 2/80 Used
Description: Code identifying a party or

other code
Note: Suplier Code
Nissan ASN
Syntax Rules:
1. R0203 - At least one of N102 or N103 is required.
2. P0304 - If either N103 or N104 is present, then the other is required.
Comments:
1. This segment, used alone, provides the most efficient method of providing organizational identification. To
obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction
processing party.
2. N105 and N106 further define the type of entity in N101.
Example:
N1*SU**92*003307

Pos: 220 Max: 1

N1 Name Detail - Optional
Loop: N1 Elements: 2

Purpose: To identify a party by type of organization, name, and code
Element Summary:
N101 98 Entity Identifier Code M ID 2/3 Must use
Description: Code identifying an

organizational entity, a physical location,
property or an individual

Code Name
ST Ship To
N102 93 Name X AN 1/60 Used
Description: Free-form name

Note: Plant Code
R = Service Parts
N = Aguascalientes 1 company
M = Motor
P = Civac
E = Export/ ILN
L = Aguascalientes 2 company
S = Service Parts Aguascalientes (WMS)
Nissan ASN
Syntax Rules:
1. R0203 - At least one of N102 or N103 is required.
2. P0304 - If either N103 or N104 is present, then the other is required.
Comments:
1. This segment, used alone, provides the most efficient method of providing organizational identification. To
obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction
processing party.
2. N105 and N106 further define the type of entity in N101.
Example:
N1*ST*N

Pos: 320 Max: 1

SAC Service, Promotion, Detail - Optional
Allowance, or Charge Loop: SAC Elements: 3
Information
Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for
the service, promotion, allowance, or charge
Element Summary:
SAC01 248 Allowance or Charge Indicator M ID 1/1 Must use
Description: Code which indicates an

allowance or charge for the service
specified

Code Name
A Allowance
SAC02 1300 Service, Promotion, Allowance, or X ID 4/4 Used

Charge Code
Description: Code identifying the service,

promotion, allowance, or charge

Code Name
I132 Total Invoice Amount
SAC05 610 Amount O N2 1/15 Used
Description: Monetary amount

Note: Total Invoice Amount
Nissan ASN, No negative values allowed
or quantity in zero.
Syntax Rules:
1. R0203 - At least one of SAC02 or SAC03 is required.
2. P0304 - If either SAC03 or SAC04 is present, then the other is required.
5. C1110 - If SAC11 is present, then SAC10 is required.
6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.
Semantics:
1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
2. SAC05 is the total amount for the service, promotion, allowance, or charge.

3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

4. SAC08 is the allowance or charge rate per unit.
5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase
order or invoice quantity.
6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable
to service, promotion, allowance, or charge.
7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by
the code used.
8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the
promotion.
9. SAC16 is used to identify the language being used in SAC15.
Comments:
1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be
used in conjunction to further the code in SAC02.
2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a
particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly
referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -
Dollars in SAC09.
Example:
SAC*A*I132***63533

Pos: 010 Max: 1

HL Hierarchical Level Detail - Mandatory

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments
Element Summary:
HL01 628 Hierarchical ID Number M AN 1/12 Must use
Description: A unique number assigned

by the sender to identify a particular data
segment in a hierarchical structure
HL02 734 Hierarchical Parent ID Number O AN 1/12 Used
Description: Identification number of the

next higher hierarchical data segment that
the data segment being described is
subordinate to
HL03 735 Hierarchical Level Code M ID 1/2 Must use
Description: Code defining the

characteristic of a level in a hierarchical
structure

Code Name
I Item
Comments:
1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating
line-item data to shipment data, and packaging data to line-item data.
2. The HL segment defines a top-down/left-right ordered structure.
3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction
set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which
case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each
subsequent HL segment within the transaction.
4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
5. HL03 indicates the context of the series of segments following the current HL segment up to the next
occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent
segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL
segment.
Example:
HL*2*1*I

Pos: 020 Max: 1

LIN Item Identification Detail - Optional

Purpose: To specify basic item identification data
Element Summary:
LIN01 350 Assigned Identification O AN 1/20 Used
Description: Alphanumeric characters

assigned for differentiation within a
transaction set
Note: Item Counter, incremented for each
LIN segment created
LIN02 235 Product/Service ID Qualifier M ID 2/2 Must use
Description: Code identifying the

type/source of the descriptive number
used in Product/Service ID (234)

Code Name
BP Buyer's Part Number
LIN03 234 Product/Service ID M AN 1/48 Must use
Description: Identifying number for a

product or service
Note: Part Number
Nissan ASN
LIN04 235 Product/Service ID Qualifier X ID 2/2 Used
Description: Code identifying the

type/source of the descriptive number
used in Product/Service ID (234)

Code Name
ON Customer Order Number
LIN05 234 Product/Service ID X AN 1/48 Used
Description: Identifying number for a

product or service
Note: RAN Number
Nissan ASN
Syntax Rules:
1. P0405 - If either LIN04 or LIN05 is present, then the other is required.


Semantics:
1. LIN01 is the line item identification
Comments:
1. See the Data Dictionary for a complete list of IDs.
2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color,
Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Example:
LIN**BP*74526EL000*ON*NZ31496

Pos: 030 Max: 1

SN1 Item Detail (Shipment) Detail - Optional

Purpose: To specify line-item detail relative to shipment
Element Summary:
SN102 382 Number of Units Shipped M R 1/10 Must use
Description: Numeric value of units

shipped in manufacturer's shipping units
for a line item or transaction set
Nissan ASN
SN103 355 Unit or Basis for Measurement Code M ID 2/2 Must use

been taken
Nissan ASN

Code Name
EA Each
PC Piece
Syntax Rules:
1. P0506 - If either SN105 or SN106 is present, then the other is required.
Semantics:
1. SN101 is the ship notice line-item identification.
Comments:
1. SN103 defines the unit of measurement for both SN102 and SN104.
Example:
SN1**90*EA

Pos: 040 Max: 1000

SLN Subline Item Detail Detail - Optional

Purpose: To specify product subline detail item data
Element Summary:
SLN01 350 Assigned Identification M AN 1/20 Must use
Description: Alphanumeric characters

assigned for differentiation within a
transaction set
Note: Part Number
SLN03 662 Relationship Code M ID 1/1 Must use
Description: Code indicating the

relationship between entities

Code Name
O Information Only
Description: Charges which relate to but may not be included in or added to the
unit price of the SLN. (i.e., compute WATS calculation based upon usage amounts)
SLN04 380 Quantity X R 1/15 Used
Description: Numeric value of quantity

Note: Default 0
SLN05 C001 Composite Unit of Measure X Comp Used
Description: To identify a composite unit

of measure(See Figures Appendix for
examples of use)
SLN05-01 355 Unit or Basis for Measurement Code M ID 2/2 Must use

been taken

Code Name
EA Each
PC Piece
SLN06 212 Unit Price X R 1/17 Used
Description: Price per unit of product,

service, commodity, etc.
Nissan ASN, No negative values allowed
or quantity in zero.

Syntax Rules:
1. P0405 - If either SLN04 or SLN05 is present, then the other is required.
2. C0706 - If SLN07 is present, then SLN06 is required.
3. C0806 - If SLN08 is present, then SLN06 is required.
Semantics:
1. SLN01 is the identifying number for the subline item.
2. SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in
a bill of materials.
3. SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
4. SLN08 is a code indicating the relationship of the price or amount to the associated segment.
Comments:
1. See the Data Element Dictionary for a complete list of IDs.
2. SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be
used as a subline number to relate to baseline number 1.
3. SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color,
Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Example:
SLN*74526EL000**A*0*EA*2726

Pos: 050 Max: 1

PRF Purchase Order Reference Detail - Optional

Purpose: To provide reference to a specific purchase order
Element Summary:
PRF01 324 Purchase Order Number M AN 1/22 Must use
Description: Identifying number for

Purchase Order assigned by the
orderer/purchaser
Nissan ASN
Semantics:
1. PRF04 is the date assigned by the purchaser to purchase order.
Example:
PRF*0631273

Pos: 150 Max: >1

REF Reference Identification Detail - Optional

Purpose: To specify identifying information
Element Summary:
REF01 128 Reference Identification Qualifier M ID 2/3 Must use
Description: Code qualifying the

Reference Identification

Code Name
LS Bar-Coded Serial Number
REF02 127 Reference Identification X AN 1/30 Used
Description: Reference information as

defined for a particular Transaction Set or
as specified by the Reference
Identification Qualifier
Note: Serial Number
Nissan ASN
Syntax Rules:
1. R0203 - At least one of REF02 or REF03 is required.
Semantics:
1. REF04 contains data relating to the value cited in REF02.
Example:
REF*LS*050131

Pos: 010 Max: 1

CTT Transaction Totals Summary - Optional

Purpose: To transmit a hash total for a specific element in the transaction set
Element Summary:
CTT01 354 Number of Line Items M N0 1/6 Must use
Description: Total number of line items in

the transaction set
Syntax Rules:
1. P0304 - If either CTT03 or CTT04 is present, then the other is required.
2. P0506 - If either CTT05 or CTT06 is present, then the other is required.
Comments:
1. This segment is intended to provide hash totals to validate transaction completeness and correctness.
Example:
CTT*8

Pos: 020 Max: 1

SE Transaction Set Trailer Summary - Mandatory

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the
beginning (ST) and ending (SE) segments)
Element Summary:
SE01 96 Number of Included Segments M N0 1/10 Must use
Description: Total number of segments

included in a transaction set including ST
and SE segments
SE02 329 Transaction Set Control Number M AN 4/9 Must use
Description: Identifying control number

that must be unique within the transaction
set functional group assigned by the
originator for a transaction set
Comments:
1. SE is the last segment of each transaction set.
Example:

Pos: Max: 1
GE Functional Group Trailer Not Defined - Mandatory

Purpose: To indicate the end of a functional group and to provide control information
Element Summary:
GE01 97 Number of Transaction Sets Included M N0 1/6 Must use
Description: Total number of transaction

sets included in the functional group or
interchange (transmission) group
terminated by the trailer containing this
data element
GE02 28 Group Control Number M N0 1/9 Must use
Description: Assigned number originated

and maintained by the sender
Semantics:
1. The data interchange control number GE02 in this trailer must be identical to the same data element in the
associated functional group header, GS06.
Comments:
1. The use of identical data interchange control numbers in the associated functional group header and trailer is
designed to maximize functional group integrity. The control number is the same as that used in the
corresponding header.
Example:

Pos: Max: 1
IEA Interchange Control Trailer Not Defined - Mandatory

Purpose: To define the end of an interchange of zero or more functional groups and interchange-related control
segments
Element Summary:
IEA01 I16 Number of Included Functional Groups M N0 1/5 Must use
Description: A count of the number of

functional groups included in an
interchange
IEA02 I12 Interchange Control Number M N0 9/9 Must use
Description: A control number assigned

by the interchange sender
Example:

856 Ship Notice/Manifest: Version: 1.3 Final

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

856 Ship Notice/Manifest: Version: 1.3 Final

Uploaded by

Copyright:

Available Formats

856 Ship Notice/Manifest

X12/V4010/856 : 856 Ship Notice/Manifest

Version: 1.3 Final

MIG_856_4010.ecs i For internal use only

856 Ship Notice/Manifest

LOOP ID - SAC >1

LOOP ID - HL 200000 C2/010L

MIG_856_4010.ecs 1 For internal use only

Pos Id Segment Name Req Max Use Repeat Notes Usage

MIG_856_4010.ecs 2 For internal use only

User Option (Usage): Must use

Description: Code to identify the type of

CodeList Summary (Total Codes: 7, Included: 1)

ISA02 I02 Authorization Information M AN 10/10 Must use

Description: Information used for

Description: Code to identify the type of

Description: This is used for identifying

Description: Qualifier to designate the

Description: Identification code

Description: Qualifier to designate the

MIG_856_4010.ecs 3 For internal use only

Ref Id Element Name Req Type Min/Max Usage

Description: Identification code

Description: Date of the interchange

ISA10 I09 Interchange Time M TM 4/4 Must use

Description: Time of the interchange

ISA11 I10 Interchange Control Standards M ID 1/1 Must use

Description: Code to identify the agency

ISA12 I11 Interchange Control Version Number M ID 5/5 Must use

Description: Code specifying the version

Description: A control number assigned

Description: Code sent by the sender to

Description: Code to indicate whether

Description: Type is not applicable; the

MIG_856_4010.ecs 4 For internal use only

Ref Id Element Name Req Type Min/Max Usage

MIG_856_4010.ecs 5 For internal use only

User Option (Usage): Must use

Description: Code identifying a group of

CodeList Summary (Total Codes: 240, Included: 1)

GS02 142 Application Sender's Code M AN 2/15 Must use

Description: Code identifying party

Description: Code identifying party

Description: Date expressed as

Description: Time expressed in 24-hour

Description: Assigned number originated

Description: Code identifying the issuer

MIG_856_4010.ecs 6 For internal use only

Ref Id Element Name Req Type Min/Max Usage

Description: Code indicating the version,

CodeList Summary (Total Codes: 39, Included: 1)

MIG_856_4010.ecs 7 For internal use only

Pos: 010 Max: 1

User Option (Usage): Must use

Description: Code uniquely identifying a

CodeList Summary (Total Codes: 298, Included: 1)

ST02 329 Transaction Set Control Number M AN 4/9 Must use

Description: Identifying control number

MIG_856_4010.ecs 8 For internal use only

Pos: 020 Max: 1

Notice Loop: N/A Elements: 4

User Option (Usage): Must use