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
- None included
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
BSN05 indicates the structure of the 856 and tells Sears how to process the document.
Only one data structure may be used within a single transaction set.
That is, if packaging levels are used, they may appear below or above the item level, but their placement must be consistent within the same transaction set. The code in BSN05 will indicate the order in which the levels are used.
The shipment identification number in BSN02 must be a unique number and must remain unique for 30 days. Sears will check for duplicates using the reference number in BSN02. If a duplicate is encountered, the transaction set will be rejected.
Time created (BSN04) is required on all DRP, RIM, SAS, ISOS and RSOS ship notices. This data element is used in the duplicate checking process. A 24 hour clock is used.
If you are using Standard Carton Pack (BSN02 contains 0002) then HL03 of the pack-level HL segment must contain P. Do not use T (Tare) even if you are shipping on pallets; always use P (Pack).
Code identifying purpose of transaction set
- 00
- Original
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.
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0001
- Shipment, Order, Packaging, Item
- 0002
- Shipment, Order, Item, Packaging
- 0004
- Shipment, Order, Item
Detail
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
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
This segment is mandatory in all DRP, RIM, SAS, RSOS, and ISOS
ship notices.
The lading quantity reflects the total number of shipping units (cartons, pallets, packages) in the shipment as consigned to the carrier. The gross weight reflects the total weight in pounds of the shipment as stated on the associated Bill of Lading and as consigned to the carrier.
For ship notices that contain a Tare or Pack level (BSN05 contains 0001 or 0002) the quantity in TD102 must equal the total number of MAN segments reported in all Tare or Pack levels included in the ship notice.
Per standards, if either TD109 or TD110 is present, then the other is required. These elements are not mandatory for Sears.
Number of units (pieces) of the lading commodity
The number of packages in the shipment
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CF
- Cubic Feet
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
2 - 4 SCAC code
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
This segment is required on DRP, RIM, SAS and SIMI ship notices to specify the trailer number for Truckload shipments. This segment is not used for LTL shipments.
Code identifying type of equipment used for shipment
- TL
- Trailer (not otherwise specified)
Prefix or alphabetic part of an equipment unit's identifying number
2 - 4 SCAC code (trailer prefix)
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
1 - 10 Trailer number
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- AO
- Appointment Number
- BM
- Bill of Lading Number
- BN
- Booking Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- SN
- Seal Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
2 - 12 Shipment Reference Number (REF01=AO)
2 - 12 Bill of Lading Number (REF01=BM)
17-17 Standardized Bill of Lading Number (REF01=BM)
2 - 12 Booking Number (REF01=BN)
2 - 13 Carrier's Reference Number (PRO/Invoice) (REF01=CN)
2 - 12 Seal Number (REF01=SN)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
The information in this segment may be used to contact the vendor about problems with their 856. The email address information is preferred, the telephone number is also helpful.
The contact information sent in this segment is not currently stored in any database. It may be used to help in locating a contact at the vendor, but this is not always available to all levels that address errors; e.g. the application.
The telephone number must contain numerics only; do not include dashes or parentheses.
The PER segment can be used to send both the phone number and email address.
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- EM
- Electronic Mail
- TE
- Telephone
Complete communications number including country or area code when applicable
1 - 80 Email address (PER Qualifier=EM)
10 - 15 Telephone number with area code and extension, if
applicable (PER Qualifier=TE)
Code identifying the type of communication number
Complete communications number including country or area code when applicable
Date/Time Reference
To specify pertinent dates and times
This segment is required on all ship notices to specify the actual ship date (DTM*011).
The N1 segment at the shipment level identifies the shipper and the ship to location for the physical shipment - the same details as entered on the associated Bill of Lading.
For RIM, if the buyer has instructed you to ship directly to the retail
store, ignore the N1ST from the original PO. Send the unit number from the N1Z7 segment from the PO as the shipment level N1ST; the N1Z7 is not required at the order level.
The N1*ST segment is required on all ship notices except ISOS and RSOS Direct-to-Customer, or Ship-to-Installer orders to identify the ship to unit number. This may be a store, distribution center or crossdock facility, or consolidation point for the order.
ISOS and RSOS do not require an N1ST segment if the merchandise is shipping direct-to-customer. The N1ST is required, however, for all shipments to a Sears’ facility. If the buyer has instructed you to ship directly to the retail store, , ignore the N1ST from the original PO. Send the unit number from the N1Z7 segment from the PO as the shipment level N1ST; the N1Z7 is not required at the order level.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
4 - 7 Ship To; use only when N101 contains code ST
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
Purchase Order Reference
To provide reference to a specific purchase order
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- 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.
- S
- Structured (From Industry Code List)
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
- VI
- Voluntary Inter-Industry Commerce Standard (VICS) EDI
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
- FL
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Number of units (pieces) of the lading commodity
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- DP
- Department Number
- IA
- Internal Vendor Number
- MR
- Merchandise Type Code
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
3 - 3 Department number
9 - 9 Internal vendor number
2 - 6 Merchandise Type Code
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- Z7
- Mark-for Party
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
4 - 7 Sears’ unit number
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
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment, at the tare level, is used to specify the identification numbers for a pallet. This segment is required when the Tare level is used.
The Tare level may be used only in a Pick and Pack data structure.
Only one MAN segment will be present in each HL-Tare loop. Use code GM in MAN01 to specify the SSCC-18 serial shipping container code.
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
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
20 - 20 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.
- P
- Pack
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
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.
- CP
- Carrier-Assigned Package ID Number
- GM
- SSCC-18 and Application Identifier
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
1 – 48 Carrier-Assigned Package ID number
20 - 20 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
Item Identification
To specify basic item identification data
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 - 13 European Article Number (LIN Qualifier=EN)
4 - 5 Sears-assigned item number (LIN Qualifier =IN)
3 - 3 Sears’ SKU number (LIN Qualifier =IZ)
12 - 12 U.P.C. number (LIN Qualifier =UP)
1 - 30 Vendor's Style Number (LIN Qualifier =VA)
1 - 15 Vendor's Item Number (LIN Qualifier =VN)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Item Detail (Shipment)
To specify line-item detail relative to shipment
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
- ST
- Set
Subline Item Detail
To specify product subline detail item data
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- 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.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
- S
- Substituted
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- RE
- Retail Price per Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- 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.
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 - 13 European Article Number (LIN02=EN)
4 - 5 Sears-assigned item number (LIN02=IN)
3 - 3 Sears’ SKU number (LIN02=IZ)
12 - 12 U.P.C. number (LIN02=UP)
1 - 30 Vendor's Style Number (LIN02=VA)
1 - 15 Vendor's Item Number (LIN02=VN)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See SLN10
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See SLN10
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See SLN10
Purchase Order Reference
To provide reference to a specific purchase order
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction
- CP
- Partial Shipment on (Date), Considered No Backorder
Summary
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.