X12 856 Ship Notice/Manifest
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
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
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- 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).
- 856
- Ship Notice/Manifest
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
BSN01 - To correct or change an ASN, the Purpose code should be 07 for type "B" orders (REF02 of REF*PHC of 850=B) only. Otherwise, duplicate "00" ASNs will be be automatically rejected.
BSN02 - The Shipment Identification must always be unique for every ASN and must not contain any spaces.
ASNs must contain POs of the same Process Handling Type. Only one Process Handling type per ASN (850 – REF02 in the REF*PHC).
Example: BSN00TOR123456720030501165924
Code identifying purpose of transaction set
- 00
- Original
- 07
- Duplicate (re-submission)
A unique control number assigned by the original shipper to identify a specific shipment
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
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)
- BSN04 is the time the shipment transaction set is created.
Detail
Example: HL*1**S
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- 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.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- S
- Shipment
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Example: TD1PLT9020***G15546*LB
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
- BAG
- Bag
- BBL
- Barrel
- BDL
- Bundle
- BOX
- Box
- BXI
- Box, with inner container
- CAN
- Can
- CAS
- Case
- COL
- Coil
- CRT
- Crate
- CTN
- Carton
- DRM
- Drum
- JAR
- Jar
- KIT
- Kit
- LIF
- Lifts
- PCS
- Pieces
- PKG
- Package
- PLT
- Pallet
- ROL
- Roll
- SLV
- Sleeve
- SPL
- Spool
- TBE
- Tube
- TRY
- Tray
- UNT
- Unit
- 90
- Standard
Number of units (pieces) of the lading commodity
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Example: TD5***MCANADIAN TIRE
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
If trailer number not available use 99NNNN (where NNNN is the Vendor ID, the same as REF02 in REF segment with ‘VR’ qualifier).
Appointment Vendors:
If your firm uses a prepaid carrier to send product to our distribution center, you will be given an appointment number. The appointment number must be entered in the trailer field (TD303) in the ASN. The correct format for the appointment number is A#####, where #### is the appointment number.
In order for the DC to be ready to receive your product at your scheduled dock time, we require your ASN the night before your appointment.
Put “COMC” in the TD505 segment to indicate that you are using a common carrier.
Example:
TD5**MCOMC
TD3*TL*A12345
Example: TD3TLXYZ*998670
Code identifying type of equipment used for shipment
- TL
- Trailer (not otherwise specified)
Prefix or alphabetic part of an equipment unit's identifying number
Reference Identification
To specify identifying information
Example: REFVR9999
Code qualifying the Reference Identification
- VR
- Vendor ID Number
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Example: PERDIDAVID ALEXANDERTE416-333-3333
Code identifying the major duty or responsibility of the person or group named
- DI
- Delivery Instructions Contact
Code identifying the type of communication number
- TE
- Telephone
Date/Time Reference
To specify pertinent dates and times
Example: DTM01120030501
Name
To identify a party by type of organization, name, and code
Example: N1ST**92016136689003
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 9
- Distribution Center
Code identifying a party or other code
- 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.
CTC Distribution Centre or EAP Depot number from PO.
Example: HL101*O
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- 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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- O
- Order
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Example: PRF99991234**20030214
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Example: TD1PLT9020***G15546*LB
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
Number of units (pieces) of the lading commodity
The Pack level is optional, but one of the Tare or the Pack level must be present. For cross-dock or direct ship PO's (850 BEG02 = RA or DS), the Pack level is MANDATORY.
Example: HL3020*P
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- 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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- P
- Pack
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Example: TD1***G15546*LB1245CF
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
If the Pack level is used without the Tare level, the MAN segment must appear in the Pack level. The MAN segment is mandatory and must appear in EITHER the Tare level or the Pack level.
For cross-dock and direct ship PO's (850 BEG02 = RA or DS), the MAN segment at the Pack level is MANDATORY.
Example: MANGM00000999990000123464
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- SSCC-18 and Application Identifier
Name
To identify a party by type of organization, name, and code
This iteration of the N1 segment will only be sent for Cross Dock or Direct Ship orders (850 BEG02 = RA or DS). For Cross Dock and Direct Ship this segment is mandatory.
A new store will have a prefix of "7" in front of the original store number to differentiate between to the current and new locations. (eg. current store # 0126 new store # 70126).
Example: N1MA**920126
Code identifying an organizational entity, a physical location, property or an individual
- MA
- Party for whom Item is Ultimately Intended
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent (Store)
Code identifying a party or other code
- 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.
Format: (NNNN – existing store or NNNNN – New store)
Example: HL4030*I
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- 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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
For country of origin use ISO 3166-1 alpha 2 codes.
For United States use ISO 3166-2 extension codes to indicate the state of origin.
Example codes:
Canada CA
China CN
Mexico MX
US- Illinois US-IL
US- Ohio US-OH
If a product has some from one country and some from another then separate for each country of origin.
Example: LIN1SK099-9999-6*CHCA
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
PO101 of 850 PO.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- 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.
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Format: (NNN-NNNN-N)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CH
- Country of Origin Code
Item Detail (Shipment)
To specify line-item detail relative to shipment
Example: SN1*24EA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Date/Time Reference
To specify pertinent dates and times
The DTM segment is MANDATORY for Legacy PO's (850 REFPHC, when REF02 = B) and optional for AOM POs (850 REFPHC, when REF02=A).
Example: DTM01020030501
The Tare level is optional, but one of the Tare or the Pack level must be present. For cross-dock and direct ship PO's (850 BEG02 = RA or DS), the Pack level is MANDATORY.
Example: HL2010*T
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- 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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- T
- Shipping Tare
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Example: TD1***G15546*LB1245CF
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
The MAN segment within the Tare level indicates a pallet is present.
If the Tare level is used without the Pack level, the MAN segment must appear in the Tare level. The MAN segment is mandatory and must appear in EITHER the Tare level or the Pack level.
The MAN segment at the Tare level is optional. For cross-dock and direct ship PO's (850 BEG02 = RA or DS), the MAN segment at the Pack level is MANDATORY.
Example: MANGM00000999990000123456
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- SSCC-18 and Application Identifier
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- 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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
For country of origin use ISO 3166-1 alpha 2 codes.
For United States use ISO 3166-2 extension codes to indicate the state of origin.
Example codes:
Canada CA
China CN
Mexico MX
US- Illinois US-IL
US- Ohio US-OH
If a product has some from one country and some from another then separate for each country of origin.
Example: LIN1SK099-9999-6*CHCA
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
PO101 of 850 PO.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- 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.
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Format: (NNN-NNNN-N)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CH
- Country of Origin Code
Item Detail (Shipment)
To specify line-item detail relative to shipment
Example: SN1*24EA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Date/Time Reference
To specify pertinent dates and times
The DTM segment is MANDATORY for Legacy PO's (850 REFPHC, when REF02 = B) and optional for AOM POs (850 REFPHC, when REF02=A).
Example: DTM01020030501
The Pack level is optional, but one of the Tare or the Pack level must be present. For cross-dock or direct ship PO's (850 BEG02 = RA or DS), the Pack level is MANDATORY.
Example: HL3020*P
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- 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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- P
- Pack
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Example: TD1***G15546*LB1245CF
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
If the Pack level is used without the Tare level, the MAN segment must appear in the Pack level. The MAN segment is mandatory and must appear in EITHER the Tare level or the Pack level.
For cross-dock and direct ship PO's (850 BEG02 = RA or DS), the MAN segment at the Pack level is MANDATORY.
Example: MANGM00000999990000123464
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- SSCC-18 and Application Identifier
Name
To identify a party by type of organization, name, and code
This iteration of the N1 segment will only be sent for Cross Dock or Direct Ship orders (850 BEG02 = RA or DS). For Cross Dock and Direct Ship this segment is mandatory.
A new store will have a prefix of "7" in front of the original store number to differentiate between to the current and new locations. (eg. current store # 0126 new store # 70126).
Example: N1MA**920126
Code identifying an organizational entity, a physical location, property or an individual
- MA
- Party for whom Item is Ultimately Intended
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent (Store)
Code identifying a party or other code
- 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.
Format: (NNNN – existing store or NNNNN – New store)
Example: HL4030*I
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- 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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
For country of origin use ISO 3166-1 alpha 2 codes.
For United States use ISO 3166-2 extension codes to indicate the state of origin.
Example codes:
Canada CA
China CN
Mexico MX
US- Illinois US-IL
US- Ohio US-OH
If a product has some from one country and some from another then separate for each country of origin.
Example: LIN1SK099-9999-6*CHCA
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
PO101 of 850 PO.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- 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.
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Format: (NNN-NNNN-N)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CH
- Country of Origin Code
Item Detail (Shipment)
To specify line-item detail relative to shipment
Example: SN1*24EA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Date/Time Reference
To specify pertinent dates and times
The DTM segment is MANDATORY for Legacy PO's (850 REFPHC, when REF02 = B) and optional for AOM POs (850 REFPHC, when REF02=A).
Example: DTM01020030501
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- 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.
Example: CTT*5
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)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Direct Ship Channel Multiple Stores Multiple Cartons Multiple SKU's MAN Segment at Pack
GS*SH*SENDERGS*RECEIVERGS*20240507*185839*000000001*X*004010~
BSN*00*CAL1234568*20030501*165924~
HL*1**S~
TD1*CTN90*5****G*46*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
HL*2*1*O~
PRF*01132460***20030214~
HL*3*2*P~
MAN*GM*00000999990000123463~
N1*MA**92*70042~
HL*4*3*I~
LIN*1*SK*099-9998-8***CH*CA~
SN1**5*EA~
HL*5*2*P~
MAN*GM*00000999990000123470~
N1*MA**92*70042~
HL*6*5*I~
LIN*2*SK*099-9999-6***CH*CA~
SN1**10*EA~
HL*7*2*P~
MAN*GM*00000999990000123487~
N1*MA**92*0126~
HL*8*7*I~
LIN*3*SK*099-9999-6***CH*CA~
SN1**10*EA~
HL*9*2*P~
MAN*GM*00000999990000123494~
N1*MA**92*0126~
HL*10*9*I~
LIN*3*SK*099-9999-6***CH*CA~
SN1**10*EA~
HL*11*2*P~
MAN*GM*00000999990000123500~
N1*MA**92*0419~
HL*12*11*I~
LIN*4*SK*099-9998-8***CH*CA~
SN1**5*EA~
HL*13*11*I~
LIN*5*SK*099-9999-6***CH*CA~
SN1**5*EA~
CTT*13~
GE*1*000000001~
IEA*1*000000001~
Multiple cartons Multiple items Multiple items in one carton MAN Segment at Pack Level
GS*SH*SENDERGS*RECEIVERGS*20240507*185356*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*CTN90*3****G*149*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991235***20030214~
HL*20*10*P~
MAN*GM*00000999990000123463~
HL*30*20*I~
LIN*1*SK*099-9997-0***CH*CA~
SN1**48*EA~
DTM*010*20030501~
HL*40*10*P~
MAN*GM*00000999990000123470~
HL*50*40*I~
LIN*1*SK*099-9997-0***CH*CA~
SN1**24*EA~
DTM*010*20030501~
HL*60*40*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**24*EA~
DTM*010*20030501~
HL*70*10*P~
MAN*GM*00000999990000123487~
HL*80*70*I~
LIN*1*SK*099-9998-8***CH*CA~
SN1**48*EA~
DTM*010*20030501~
CTT*9~
GE*1*000000001~
IEA*1*000000001~
Multiple pallets Multiple cartons One item MAN Segment at Tare 1
GS*SH*SENDERGS*RECEIVERGS*20240507*185453*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*CTN90*36****G*300*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991235***20030214~
HL*20*10*T~
MAN*GM*00000999990000123463~
HL*30*20*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**400*EA~
DTM*010*20030501~
HL*40*10*T~
MAN*GM*00000999990000123472~
HL*50*40*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**400*EA~
DTM*010*20030501~
HL*60*10*T~
MAN*GM*00000999990000123487~
HL*70*60*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**400*EA~
DTM*010*20030501~
CTT*8~
GE*1*000000001~
IEA*1*000000001~
Multiple pallets Multiple cartons One item MAN Segment at Tare 2
GS*SH*SENDERGS*RECEIVERGS*20240507*185935*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*CTN90*36****G*300*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991235***20030214~
HL*20*10*T~
MAN*GM*00000999990000123463~
HL*30*20*I~
LIN*1*SK*099-9999-6***CH*CN~
SN1**400*EA~
DTM*010*20030501~
HL*40*10*T~
MAN*GM*00000999990000123472~
HL*50*40*I~
LIN*1*SK*099-9999-6***CH*CN~
SN1**400*EA~
DTM*010*20030501~
HL*60*10*T~
MAN*GM*00000999990000123487~
HL*70*60*I~
LIN*1*SK*099-9999-6***CH*VN~
SN1**400*EA~
DTM*010*20030501~
CTT*8~
GE*1*000000001~
IEA*1*000000001~
Multiple Stores Multiple Cartons Multiple SKU's MAN Segment at Pack
GS*SH*SENDERGS*RECEIVERGS*20240507*185601*000000001*X*004010~
BSN*00*CAL1234567*20030501*165924~
HL*1**S~
TD1*CTN90*5****G*46*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689007~
HL*2*1*O~
PRF*01132459***20030214~
HL*3*2*P~
TD1******G*9*LB*2*CF~
MAN*GM*00000999990000123463~
N1*MA**92*70042~
HL*4*3*I~
LIN*1*SK*099-9998-8***CH*CA~
SN1**10*EA~
HL*5*2*P~
MAN*GM*00000999990000123470~
N1*MA**92*70042~
HL*6*5*I~
LIN*2*SK*099-9999-6***CH*CA~
SN1**10*EA~
HL*7*2*P~
MAN*GM*00000999990000123487~
N1*MA**92*0126~
HL*8*7*I~
LIN*3*SK*099-9998-8***CH*CA~
SN1**10*EA~
HL*9*2*P~
MAN*GM*00000999990000123494~
N1*MA**92*0126~
HL*10*9*I~
LIN*3*SK*099-9998-8***CH*CA~
SN1**10*EA~
HL*11*2*P~
MAN*GM*00000999990000123500~
N1*MA**92*0419~
HL*12*11*I~
LIN*4*SK*099-9998-8***CH*CA~
SN1**5*EA~
HL*13*11*I~
LIN*5*SK*099-9999-6***CH*CA~
SN1**5*EA~
CTT*13~
GE*1*000000001~
IEA*1*000000001~
One Carton Multiple PO's Multiple SKU's MAN Segment at Pack
GS*SH*SENDERGS*RECEIVERGS*20240507*185726*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*CTN90*1****G*20*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*38670~
REF*VR*9999~
PER*DI*KATHY SMITH*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991235***20030214~
HL*20*10*P~
MAN*GM*00000999990000123463~
HL*30*20*I~
LIN*1*SK*099-9997-0***CH*CA~
SN1**10*EA~
DTM*010*20030501~
HL*40*1*O~
PRF*99991236***20030214~
HL*50*40*P~
MAN*GM*00000999990000123463~
HL*60*50*I~
LIN*1*SK*099-9998-8***CH*CA~
SN1**5*EA~
DTM*010*20030501~
HL*70*1*O~
PRF*99991237***20030214~
HL*80*70*P~
MAN*GM*00000999990000123463~
HL*90*80*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**5*EA~
DTM*010*20030501~
CTT*10~
GE*1*000000001~
IEA*1*000000001~
Sample 1
GS*SH*SENDERGS*RECEIVERGS*20240507*190113*000000001*X*004010~
BSN*00*TOR1234567*20030501*165924~
HL*1**S~
TD1*PLT90*20****G*15546*LB~
TD5****M*CANADIAN TIRE~
TD3*TL*XYZ*998670~
REF*VR*9999~
PER*DI*DAVID ALEXANDER*TE*416-333-3333~
DTM*011*20030501~
N1*ST**9*2016136689003~
HL*10*1*O~
PRF*99991234***20030214~
TD1*PLT90*20****G*15546*LB~
HL*20*10*T~
TD1******G*15546*LB*1245*CF~
MAN*GM*00000999990000123456~
HL*30*20*P~
TD1******G*15546*LB*1245*CF~
MAN*GM*00000999990000123464~
HL*40*30*I~
LIN*1*SK*099-9999-6***CH*CA~
SN1**24*EA~
DTM*010*20030501~
CTT*5~
GE*1*000000001~
IEA*1*000000001~
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.