856 Advanced Shipping Notice

07/12/06
Ship Notice/Manifest - 856
856 Ship Notice/Manifest
X12/V4010/856: 856 Ship Notice/Manifest
Version: 1.4 Final
Created:
Modified:
Notes:
NINSTi85641ANY_TP_Guidelines.ecs
07/12/2006
12/27/2006
1
For internal use only
07/12/06
Ship Notice/Manifest - 856
856
Ship Notice/Manifest
Functional Group=SH
This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest
Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The
transaction set can be used to list the contents of a shipment of goods as well as additional information relating to
the shipment, such as order information, product description, physical characteristics, type of packaging, marking,
carrier information, and configuration of goods within the transportation equipment. The transaction set enables the
sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered
flexibility to convey information.The sender of this transaction is the organization responsible for detailing and
communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The
receiver of this transaction set can be any organization having an interest in the contents of a shipment or
information about the contents of a shipment.
Heading:
Pos
010
020
Id
ST
BSN
040
DTM
Segment Name
Transaction Set Header
Beginning Segment for Ship
Notice
Date/Time Reference
Req
M
M
Max Use
1
1
M
10
Segment Name
Req
Max Use
Hierarchical Level
Reference Identification
M
O
1
>1
Name
M
1
Hierarchical Level
Purchase Order Reference
M
M
1
1
Hierarchical Level
Item Identification
Item Detail (Shipment)
Product/Item Description
M
M
M
O
1
1
1
1
Name
O
1
Req
O
M
Max Use
1
1
Repeat
Notes
Usage
Must use
Must use
Used
Detail:
Pos
Id
LOOP ID - HL
010
HL
150
REF
LOOP ID - N1
220
N1
LOOP ID - HL
010
HL
050
PRF
LOOP ID - HL
010
HL
020
LIN
030
SN1
070
PID
LOOP ID - N1
220
N1
Repeat
1
Notes
C2/010L
Usage
Must use
Used
200
Used
200000
Must use
Must use
200000
Must use
Must use
Must use
Used
200
Used
Summary:
Pos
010
020
Id
CTT
SE
Segment Name
Transaction Totals
Transaction Set Trailer
Repeat
Notes
N3/010
Usage
Used
Must use
Notes:
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.
User Note 1:
Trading Partner Guidelines
NINSTi85641ANY_TP_Guidelines.ecs
2
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 010
Max: 1
Heading - Mandatory
Loop: N/A
Elements: 2
ST Transaction Set Header
User Option (Usage): Must use
To indicate the start of a transaction set and to assign a control number
Element Summary:
Ref
ST01
Id
143
ST02
329
Element Name
Transaction Set Identifier Code
Description: Code uniquely identifying a
Transaction Set
All valid standard codes are used.
Transaction Set Control Number
Description: Identifying control number that
must be unique within the transaction set
functional group assigned by the originator
for a transaction set
Req
M
Type
ID
Min/Max
3/3
Usage
Must use
M
AN
4/9
Must use
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).
NINSTi85641ANY_TP_Guidelines.ecs
3
For internal use only
07/12/06
Ship Notice/Manifest - 856
BSN Beginning Segment for Ship
Notice
Pos: 020
Max: 1
Heading - Mandatory
Loop: N/A
Elements: 4
User Option (Usage): Must use
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Element Summary:
Ref
BSN01
Id
353
BSN02
396
BSN03
373
BSN04
337
Element Name
Transaction Set Purpose Code
Description: Code identifying purpose of
transaction set
Code Name
00
Original
01
Cancellation
Shipment Identification
Description: A unique control number
assigned by the original shipper to identify a
specific shipment
Date
Description: Date expressed as
CCYYMMDD
Time
Description: Time expressed in 24-hour
clock time as follows: HHMM, or HHMMSS,
or HHMMSSD, or HHMMSSDD, where H =
hours (00-23), M = minutes (00-59), S =
integer seconds (00-59) and DD = decimal
seconds; decimal seconds are expressed as
follows: D = tenths (0-9) and DD =
hundredths (00-99)
Req
M
Type
ID
Min/Max
2/2
Usage
Must use
M
AN
2/30
Must use
M
DT
8/8
Must use
M
TM
4/8
Must use
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.
NINSTi85641ANY_TP_Guidelines.ecs
4
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 040
Max: 10
Heading - Mandatory
Loop: N/A
Elements: 4
DTM Date/Time Reference
User Option (Usage): Used
To specify pertinent dates and times
Element Summary:
Ref
DTM01
Id
374
DTM02
373
DTM03
337
DTM04
623
Element Name
Date/Time Qualifier
Description: Code specifying type of date or
time, or both date and time
Code Name
011
Shipped
017
Estimated Delivery
Date
Description: Date expressed as
CCYYMMDD
Time
Description: Time expressed in 24-hour
clock time as follows: HHMM, or HHMMSS,
or HHMMSSD, or HHMMSSDD, where H =
hours (00-23), M = minutes (00-59), S =
integer seconds (00-59) and DD = decimal
seconds; decimal seconds are expressed as
follows: D = tenths (0-9) and DD =
hundredths (00-99)
Time Code
Description: Code identifying the time. In
accordance with International Standards
Organization standard 8601, time can be
specified by a + or - and an indication in
hours in relation to Universal Time
Coordinate (UTC) time; since + is a
restricted character, + and - are substituted
by P and M in the codes that follow
All valid standard codes are used.
Req
M
Type
ID
Min/Max
3/3
Usage
Must use
X
DT
8/8
Must use
X
TM
4/8
Used
O
ID
2/2
Used
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.
User Note 1:
Both DTM type 011 (Shipped Date) and DTM type 017 (Expected Delivery Date) are required.
NINSTi85641ANY_TP_Guidelines.ecs
5
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 010
Repeat: 1
Mandatory
Loop: HL
Elements: N/A
Loop HL
To identify dependencies among and the content of hierarchically related groups of data segments
Loop Summary:
Pos
010
150
220
Id
HL
REF
Segment Name
Hierarchical Level
Reference Identification
Loop N1
Req
M
O
O
Max Use
1
>1
Repeat
200
Usage
Must use
Used
Used
User Note 1:
************************
SHIPMENT LEVEL HL LOOP
************************
NINSTi85641ANY_TP_Guidelines.ecs
6
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 010
Max: 1
Detail - Mandatory
Loop: HL
Elements: 3
HL Hierarchical Level
User Option (Usage): Must use
To identify dependencies among and the content of hierarchically related groups of data segments
Element Summary:
Ref
HL01
Id
628
HL02
734
HL03
735
Element Name
Hierarchical ID Number
Description: A unique number assigned by
the sender to identify a particular data
segment in a hierarchical structure
Hierarchical Parent ID Number
Description: Identification number of the
next higher hierarchical data segment that
the data segment being described is
subordinate to
Hierarchical Level Code
Description: Code defining the
characteristic of a level in a hierarchical
structure
Code Name
S
Shipment
Req
M
Type
AN
Min/Max
1/12
Usage
Must use
O
AN
1/12
Used
M
ID
1/2
Must use
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.
NINSTi85641ANY_TP_Guidelines.ecs
7
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 150
Max: >1
Detail - Optional
Loop: HL
Elements: 2
REF Reference Identification
User Option (Usage): Used
To specify identifying information
Element Summary:
Ref
REF01
Id
128
REF02
127
Element Name
Reference Identification Qualifier
Description: Code qualifying the Reference
Identification
Code Name
AW
Air Waybill Number
PK
Packing List Number
Reference Identification
Description: Reference information as
defined for a particular Transaction Set or as
specified by the Reference Identification
Qualifier
Req
M
Type
ID
Min/Max
2/3
Usage
Must use
X
AN
1/30
Used
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.
NINSTi85641ANY_TP_Guidelines.ecs
8
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 220
Repeat: 200
Optional
Loop: N1
Elements: N/A
Loop N1
To identify a party by type of organization, name, and code
Loop Summary:
Pos
220
Id
N1
Segment Name
Name
Req
M
Max Use
1
Repeat
Usage
Used
User Note 1:
Both N1*SF (Ship From) and N1*ST (Ship To) are required either here or within every item level HL. Both of
these N1 segments require N1_03 and N1_04.
The "Ship From" N1_04 must contain the exact "Supplier" location (N1_04) from the original Order or Order
Change
The "Ship To" N1_04 must contain the exact "Ship To" location (N1_04) from the original Order or Order Change.
The item level ship to location must be sent wherever it is different from the header level ship to location.
Item level N1 will take precedence, should both be sent.
NINSTi85641ANY_TP_Guidelines.ecs
9
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 220
Max: 1
Detail - Mandatory
Loop: N1
Elements: 4
N1 Name
User Option (Usage): Used
To identify a party by type of organization, name, and code
Element Summary:
Ref
N101
Id
98
N102
93
N103
66
N104
67
Element Name
Entity Identifier Code
Description: Code identifying an
organizational entity, a physical location,
property or an individual
Code Name
SF
Ship From
ST
Ship To
Name
Description: Free-form name
Identification Code Qualifier
Description: Code designating the
system/method of code structure used for
Identification Code (67)
User Note 1: Please use only code "92"
Code Name
92
Assigned by Buyer or Buyer's Agent
Identification Code
Description: Code identifying a party or
other code
Req
M
Type
ID
Min/Max
2/3
Usage
Must use
X
AN
1/60
Used
X
ID
1/2
Must use
X
AN
2/80
Must use
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.
User Note 1:
Both N1*SF (Ship From) and N1*ST (Ship To) are required either here or within every item level HL. Both of
these N1 segments require N1_03 and N1_04.
The "Ship From" N1_04 must contain the exact "Supplier" location (N1_04) from the original Order or Order
Change
The "Ship To" N1_04 must contain the exact "Ship To" location (N1_04) from the original Order or Order Change.
The item level ship to location must be sent wherever it is different from the header level ship to location.
Item level N1 will take precedence, should both be sent.
NINSTi85641ANY_TP_Guidelines.ecs
10
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 010
Loop HL
Repeat:
200000
Mandatory
Loop: HL
Elements: N/A
To identify dependencies among and the content of hierarchically related groups of data segments
Loop Summary:
Pos
010
050
Id
HL
PRF
Segment Name
Hierarchical Level
Purchase Order Reference
Req
M
M
Max Use
1
1
Repeat
Usage
Must use
Must use
User Note 1:
************************
ORDER LEVEL HL LOOP
************************
NINSTi85641ANY_TP_Guidelines.ecs
11
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 010
Max: 1
Detail - Mandatory
Loop: HL
Elements: 3
HL Hierarchical Level
User Option (Usage): Must use
To identify dependencies among and the content of hierarchically related groups of data segments
Element Summary:
Ref
HL01
Id
628
HL02
734
HL03
735
Element Name
Hierarchical ID Number
Description: A unique number assigned by
the sender to identify a particular data
segment in a hierarchical structure
Hierarchical Parent ID Number
Description: Identification number of the
next higher hierarchical data segment that
the data segment being described is
subordinate to
Hierarchical Level Code
Description: Code defining the
characteristic of a level in a hierarchical
structure
Code Name
O
Order
Req
M
Type
AN
Min/Max
1/12
Usage
Must use
O
AN
1/12
Used
M
ID
1/2
Must use
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.
NINSTi85641ANY_TP_Guidelines.ecs
12
For internal use only
07/12/06
Ship Notice/Manifest - 856
PRF Purchase Order Reference
Pos: 050
Max: 1
Detail - Mandatory
Loop: HL
Elements: 2
User Option (Usage): Must use
To provide reference to a specific purchase order
Element Summary:
Ref
PRF01
Id
324
PRF02
328
Element Name
Purchase Order Number
Description: Identifying number for
Purchase Order assigned by the
orderer/purchaser
Release Number
Description: Number identifying a release
against a Purchase Order previously placed
by the parties involved in the transaction
User Note 1: Must send PRF_02 for Blanket
PO's.
Do not send PRF_02 for non-Blanket PO's.
Req
M
Type
AN
Min/Max
1/22
Usage
Must use
O
AN
1/30
Used
Semantics:
1. PRF04 is the date assigned by the purchaser to purchase order.
User Note 1:
Must send PRF_02 for Blanket PO's.
Do not send PRF_02 for non-Blanket PO's.
NINSTi85641ANY_TP_Guidelines.ecs
13
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 010
Loop HL
Repeat:
200000
Mandatory
Loop: HL
Elements: N/A
To identify dependencies among and the content of hierarchically related groups of data segments
Loop Summary:
Pos
010
020
030
070
220
Id
HL
LIN
SN1
PID
Segment Name
Hierarchical Level
Item Identification
Item Detail (Shipment)
Product/Item Description
Loop N1
Req
M
M
M
O
O
Max Use
1
1
1
1
Repeat
200
Usage
Must use
Must use
Must use
Used
Used
User Note 1:
************************
ITEM LEVEL HL LOOP
************************
NINSTi85641ANY_TP_Guidelines.ecs
14
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 010
Max: 1
Detail - Mandatory
Loop: HL
Elements: 3
HL Hierarchical Level
User Option (Usage): Must use
To identify dependencies among and the content of hierarchically related groups of data segments
Element Summary:
Ref
HL01
Id
628
HL02
734
HL03
735
Element Name
Hierarchical ID Number
Description: A unique number assigned by
the sender to identify a particular data
segment in a hierarchical structure
Hierarchical Parent ID Number
Description: Identification number of the
next higher hierarchical data segment that
the data segment being described is
subordinate to
Hierarchical Level Code
Description: Code defining the
characteristic of a level in a hierarchical
structure
Code Name
I
Item
Req
M
Type
AN
Min/Max
1/12
Usage
Must use
O
AN
1/12
Used
M
ID
1/2
Must use
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.
NINSTi85641ANY_TP_Guidelines.ecs
15
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 020
Max: 1
Detail - Mandatory
Loop: HL
Elements: 7
LIN Item Identification
User Option (Usage): Must use
To specify basic item identification data
Element Summary:
Ref
LIN01
Id
350
LIN02
235
LIN03
234
LIN04
235
LIN05
234
LIN06
235
LIN07
234
Element Name
Assigned Identification
Description: Alphanumeric characters
assigned for differentiation within a
transaction set
User Note 1: Must match ORIGINAL LINE
ITEM NUMBER FROM ORDER
Product/Service ID Qualifier
Description: Code identifying the
type/source of the descriptive number used
in Product/Service ID (234)
Code Name
BP
Buyer's Part Number
EC
Engineering Change Level
VP
Vendor's (Seller's) Part Number
Product/Service ID
Description: Identifying number for a
product or service
Product/Service ID Qualifier
Description: Code identifying the
type/source of the descriptive number used
in Product/Service ID (234)
Code Name
BP
Buyer's Part Number
EC
Engineering Change Level
VP
Vendor's (Seller's) Part Number
Product/Service ID
Description: Identifying number for a
product or service
Product/Service ID Qualifier
Description: Code identifying the
type/source of the descriptive number used
in Product/Service ID (234)
Code Name
BP
Buyer's Part Number
EC
Engineering Change Level
VP
Vendor's (Seller's) Part Number
Product/Service ID
Description: Identifying number for a
product or service
Req
O
Type
AN
Min/Max
1/20
Usage
Must use
M
ID
2/2
Must use
M
AN
1/48
Must use
X
ID
2/2
Used
X
AN
1/48
Used
X
ID
2/2
Used
X
AN
1/48
Used
Syntax Rules:
1.
2.
3.
4.
5.
6.
7.
P0405 - If either LIN04 or LIN05
P0607 - If either LIN06 or LIN07
P0809 - If either LIN08 or LIN09
P1011 - If either LIN10 or LIN11
P1213 - If either LIN12 or LIN13
P1415 - If either LIN14 or LIN15
P1617 - If either LIN16 or LIN17
NINSTi85641ANY_TP_Guidelines.ecs
is present, then the other is required.
is present, then the other is required.
is present, then the other is required.
is present, then the other is required.
is present, then the other is required.
is present, then the other is required.
is present, then the other is required.
16
For internal use only
07/12/06
8.
9.
10.
11.
12.
13.
14.
P1819 - If either LIN18 or LIN19
P2021 - If either LIN20 or LIN21
P2223 - If either LIN22 or LIN23
P2425 - If either LIN24 or LIN25
P2627 - If either LIN26 or LIN27
P2829 - If either LIN28 or LIN29
P3031 - If either LIN30 or LIN31
Ship Notice/Manifest - 856
is present, then the other is required.
is present, then the other is required.
is present, then the other is required.
is present, then the other is required.
is present, then the other is required.
is present, then the other is required.
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.
User Note 1:
LIN_01 must match ORIGINAL LINE ITEM NUMBER FROM ORDER
Whenever it is available per the order or order change, each LIN segment must include Buyer Part Number (BP).
If Buyer Part Number is not available, LIN must include the Vendor Part Number (VP).
NINSTi85641ANY_TP_Guidelines.ecs
17
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 030
Max: 1
Detail - Mandatory
Loop: HL
Elements: 3
SN1 Item Detail (Shipment)
User Option (Usage): Must use
To specify line-item detail relative to shipment
Element Summary:
Ref
SN101
Id
350
SN102
382
SN103
355
Element Name
Assigned Identification
Description: Alphanumeric characters
assigned for differentiation within a
transaction set
Number of Units Shipped
Description: Numeric value of units shipped
in manufacturer's shipping units for a line
item or transaction set
Unit or Basis for Measurement Code
Description: Code specifying the units in
which a value is being expressed, or manner
in which a measurement has been taken
All valid standard codes are used.
Req
O
Type
AN
Min/Max
1/20
Usage
Used
M
R
1/10
Must use
M
ID
2/2
Must use
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.
NINSTi85641ANY_TP_Guidelines.ecs
18
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 070
Max: 1
Detail - Optional
Loop: HL
Elements: 2
PID Product/Item Description
User Option (Usage): Used
To describe a product or process in coded or free-form format
Element Summary:
Ref
PID01
Id
349
PID05
352
Element Name
Item Description Type
Description: Code indicating the format of a
description
All valid standard codes are used.
Description
Description: A free-form description to
clarify the related data elements and their
content
Req
M
Type
ID
Min/Max
1/1
Usage
Must use
X
AN
1/80
Used
Syntax Rules:
1.
2.
3.
4.
5.
C0403 - If PID04 is present, then PID03 is required.
R0405 - At least one of PID04 or PID05 is required.
C0703 - If PID07 is present, then PID03 is required.
C0804 - If PID08 is present, then PID04 is required.
C0905 - If PID09 is present, then PID05 is required.
Semantics:
1. Use PID03 to indicate the organization that publishes the code list being referred to.
2. PID04 should be used for industry-specific product description codes.
3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the
specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.
4. PID09 is used to identify the language being used in PID05.
Comments:
1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then
both PID04 and PID05 are used.
2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.
3. PID07 specifies the individual code list of the agency specified in PID03.
NINSTi85641ANY_TP_Guidelines.ecs
19
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 220
Repeat: 200
Optional
Loop: N1
Elements: N/A
Loop N1
To identify a party by type of organization, name, and code
Loop Summary:
Pos
220
Id
N1
Segment Name
Name
Req
O
Max Use
1
Repeat
Usage
Used
User Note 1:
Both N1*SF (Ship From) and N1*ST (Ship To) are required either here at every Item Level or within Shipment
Level HL. Both of these segments require N1_03 and N1_04.
The "Ship From" N1_04 must contain the exact "Supplier" location (N1_04) from the original Order or Order
Change
The "Ship To" N1_04 must contain the exact "Ship To" location (N1_04) from the original Order or Order Change.
The item level ship to location must be sent wherever it is different from the header level ship to location.
Item level N1 will take precedence, should both be sent.
NINSTi85641ANY_TP_Guidelines.ecs
20
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 220
Max: 1
Detail - Optional
Loop: N1
Elements: 4
N1 Name
User Option (Usage): Used
To identify a party by type of organization, name, and code
Element Summary:
Ref
N101
Id
98
N102
93
N103
66
N104
67
Element Name
Entity Identifier Code
Description: Code identifying an
organizational entity, a physical location,
property or an individual
Code Name
SF
Ship From
ST
Ship To
Name
Description: Free-form name
Identification Code Qualifier
Description: Code designating the
system/method of code structure used for
Identification Code (67)
User Note 1: Use code "92" only
Code Name
92
Assigned by Buyer or Buyer's Agent
Identification Code
Description: Code identifying a party or
other code
Req
M
Type
ID
Min/Max
2/3
Usage
Must use
X
AN
1/60
Used
X
ID
1/2
Must use
X
AN
2/80
Must use
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.
User Note 1:
Both N1*SF (Ship From) and N1*ST (Ship To) are required either here at every Item Level or within Shipment
Level HL. Both of these segments require N1_03 and N1_04.
The "Ship From" N1_04 must contain the exact "Supplier" location (N1_04) from the original Order or Order
Change
The "Ship To" N1_04 must contain the exact "Ship To" location (N1_04) from the original Order or Order Change.
The item level ship to location must be sent wherever it is different from the header level ship to location.
Item level N1 will take precedence, should both be sent.
NINSTi85641ANY_TP_Guidelines.ecs
21
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 010
Max: 1
Summary - Optional
Loop: N/A
Elements: 1
CTT Transaction Totals
User Option (Usage): Used
To transmit a hash total for a specific element in the transaction set
Element Summary:
Ref
CTT01
Id
354
Element Name
Number of Line Items
Description: Total number of line items in
the transaction set
Req
M
Type
N0
Min/Max
1/6
Usage
Must use
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.
NINSTi85641ANY_TP_Guidelines.ecs
22
For internal use only
07/12/06
Ship Notice/Manifest - 856
Pos: 020
Max: 1
Summary - Mandatory
Loop: N/A
Elements: 2
SE Transaction Set Trailer
User Option (Usage): Must use
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning
(ST) and ending (SE) segments)
Element Summary:
Ref
SE01
Id
96
SE02
329
Element Name
Number of Included Segments
Description: Total number of segments
included in a transaction set including ST
and SE segments
Transaction Set Control Number
Description: Identifying control number that
must be unique within the transaction set
functional group assigned by the originator
for a transaction set
Req
M
Type
N0
Min/Max
1/10
Usage
Must use
M
AN
4/9
Must use
Comments:
1. SE is the last segment of each transaction set.
NINSTi85641ANY_TP_Guidelines.ecs
23
For internal use only
07/12/06
Ship Notice/Manifest - 856
Table of Contents
Ship Notice/Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Beginning Segment for Ship Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Loop HL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Loop N1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Loop HL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Purchase Order Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Loop HL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Item Detail (Shipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Loop N1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
NINSTi85641ANY_TP_Guidelines.ecs
i
For internal use only
Similar pages