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
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
The segment is used to communicate the shipment ID number (SID). This shipment ID number represents the total contents of the materials from one destination to another destination. Often the Bill of Lading number is used, but it can be any number which is not repeated for 13 months by the supplier. The transaction purpose code associated indicates an original shipment. If a replacement ship notice is sent, then Deere requires the entire contents of the shipment data re-transmitted.
Code identifying purpose of transaction set
- 00
- Original
- 01
- Cancellation
- 05
- Replace
A unique control number assigned by the original shipper to identify a specific shipment
John Deere requires a unique shipment ID for 13 months. John Deere uses only the 13 left most characters for the ship ID. If packlist references are not sent in a reference segment, the SID will be used as the invoice number for ERS.
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.
Use format of HHMMSSDD.
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0003
- Shipment, Packaging, Order, Item
Estimated Delivery
To specify pertinent dates and times
Deere requires at least one DTM segment to communicate the time of shipment or the estimated time of arrival at the ship to location.
Code specifying type of date or time, or both date and time
- 017
- Estimated Delivery
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)
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
Shipped
To specify pertinent dates and times
Deere requires at least one DTM segment to communicate the time of shipment or the estimated time of arrival at the ship to location.
Code specifying type of date or time, or both date and time
- 011
- Shipped
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)
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
Detail
John Deere will use Shipment/Package/Order/Item hierarchical structure, and BSN 05 should reflect this ASN structure.
The first 'Hierarchical Level - Shipment' is number 1, and all segments until the next HL, segment relate to the header information; all information applies to the entire content of the shipment.
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.
Measurements
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
This is an optional segment at the shipment level containing total weight of the total shipment quantity.
Code identifying the broad category to which a measurement applies
- PD
- Physical Dimensions
Code identifying a specific product or process characteristic to which a measurement applies
- G
- Gross Weight
- N
- Actual Net Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- 01
- Actual Pounds
Only used by Worldwide Logistics.
- 24
- Theoretical Pounds
Only used by Worldwide Logistics.
- 50
- Actual Kilograms
Only used by Worldwide Logistics.
- 53
- Theoretical Kilograms
Only used by Worldwide Logistics.
- KG
- Kilogram
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
John Deere uses segment at the shipment level only.
The primary information Deere requires from this segment is the code for the transportation company moving the material.
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
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
SCAC code of carrier.
Code specifying the method or type of transportation for the shipment
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Code identifying type of location
- OR
- Origin (Shipping Point)
- PP
- Pool Point
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
John Deere uses segment at the shipment level only.
The trailer number (or other ID number of the carrier) is provided here within the equipment number field. If trailer number is not available, do not use the TD3 segment.
Code identifying type of equipment used for shipment
Prefix or alphabetic part of an equipment unit's identifying number
John Deere expects the SCAC code of the Carrier.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Reference Identification
To specify identifying information
John Deere requires the "2I" at the Shipment level for the shipment's logistic provider tracking number.
Other information related to the shipment may also be provided in additional Shipment level REF segments.
Code qualifying the Reference Identification
- 2I
- Tracking Number
- AW
- Air Waybill Number
- BM
- Bill of Lading Number
This number must not repeat within 13 months.
- FR
- Freight Bill Number
- IK
- Invoice Number
Manufacturer's invoice number for vehicle/component.
Required by Deere Mexican units at header-level or item-level location depending on shipment makeup for invoice matching.
- OC
- Ocean Container Number
- PK
- Packing List Number
This number must not repeat within 13 months.
- SN
- Seal Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Name
To identify a party by type of organization, name, and code
John Deere uses segment at the shipment level only to communicate business partner or location information.
There will be an associated DUNS number or another Deere unique number to cross reference entity information.
Code identifying an organizational entity, a physical location, property or an individual
- CS
- Consolidator
- SF
- Ship From
- ST
- Ship To
- SU
- Supplier/Manufacturer
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 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.
Reference Identification
To specify identifying information
John Deere uses this optional segment at the shipment level for N1 loop.
This REF segment is used to communicate the dock code "DK" if the ordering transaction included corresponding dock information.
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
John Deere uses this optional segment at the shipment level only for special charges related to the shipment.
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- C040
- Delivery
- D240
- Freight
- D500
- Handling
- G760
- Set-up
- H550
- Surcharge
- I260
- Transportation Direct Billing
- I280
- Transportation Vendor Provided
Monetary amount
- SAC05 is the total amount for the service, promotion, allowance, or charge.
- If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
If BSN 05 indicates Shipment/Package/Order/Item hierarchical structure, then the first 'Hierarchical Level - Pallet/Master Package' occurrence will start with 2 and all segments until the next Package level HL relate to the outer-most container/carton or pallet.
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.
Measurements
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
This is an optional segment containing total weight of the shipped quantity for the container/carton.
Code identifying the broad category to which a measurement applies
- PD
- Physical Dimensions
Code identifying a specific product or process characteristic to which a measurement applies
- G
- Gross Weight
- N
- Actual Net Weight
- WT
- Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- 01
- Actual Pounds
Only used by Worldwide Logistics.
- 24
- Theoretical Pounds
Only used by Worldwide Logistics.
- 50
- Actual Kilograms
Only used by Worldwide Logistics.
- 53
- Theoretical Kilograms
Only used by Worldwide Logistics.
- KG
- Kilogram
- LB
- Pound
Invoice Number
To specify identifying information
This optional segment at the Package level may be included to provide additional information depending on the makeup of the shipment.
Code qualifying the Reference Identification
- IK
- Invoice Number
Manufacturer's invoice number for vehicle/component.
Required by Deere Mexican units at header-level or item-level location depending on shipment makeup for invoice matching.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Packing List Number
To specify identifying information
This optional segment at the Package level may be included to provide additional information depending on the makeup of the shipment.
Code qualifying the Reference Identification
- PK
- Packing List Number
This number must not repeat within 13 months.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The packing list reference, when provided, will be used as the invoice number ERS.
Load Detail
To specify the number of material loads shipped
A Package level CLD segment is required when identifying a container/carton of shippable items, an outermost container/carton, or pallet with sub containers/cartons.
The Package level CLD number of loads must be 1 and the quantity equal either the number of shippable items or number of sub containers/cartons in the case of outer packaging or pallet.
Container/Packaging Specification Number
To specify identifying information
John Deere uses a Packaging level REF to provide additional references for each container/carton.
The "98" qualifier replaces the TD101 Packaging Code. If the containers loaded have an associated cost within Deere unit systems, the containers are paid with the material payment when the ERS process is in effect. The external packaging value is required when the shipment is a mix or master pallet/pack.
Code qualifying the Reference Identification
- 98
- Container/Packaging Specification Number
A numeric or alphanumeric identification assigned to a unique packaging/container configuration.
Used to communicate Deere packaging code.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Shipping Label Serial Number
To specify identifying information
John Deere uses a Packaging level REF to provide additional references for each container/carton.
The "LA" qualifier identifies the Shipping Label (License plate) for the container/carton. At the Pack level this "LA" refers to the outermost License Plate Number for the Master or Mix container.
Code qualifying the Reference Identification
- LA
- Shipping Label Serial Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
If BSN 05 indicates Shipment/Package/Order/Item hierarchical structure, then the first 'Hierarchical Level - Order' occurrence will start with 3 and all segments until the next Order level HL identifies an order.
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
This segment contains the Deere purchase order number for the material being shipped. John Deere requires this segment at the HL order level.
Identifying number for Purchase Order assigned by the orderer/purchaser
If BSN 05 indicates Shipment/Package/Order/Item hierarchical structure, then the first 'Hierarchical Level - Item' occurrence will start with 4 and all segments until the next HL relate to an item.
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
This segment contains the Deere material number being shipped. John Deere requires this segment at the item level.
The Purchase Order Line Number is required. The value can be retrieved from the 830 LIN01, the 850 PO101 or the 862 LIN segment in one of the value/pair segments with a "PL" qualifier. The Purchase Order Line Number is sent in one of the 856 LIN value/pair segments with a "PL" qualifier.
Paired elements starting at LIN02/LIN03 can be sent in any order. The qualifier identifies the business relevance of the value.
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.
- BP
- Buyer's Part Number
- CH
- Country of Origin Code
- PL
- Purchaser's Order Line Number
- SN
- Serial Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- CH
- Country of Origin Code
- PL
- Purchaser's Order Line Number
- SN
- Serial Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- CH
- Country of Origin Code
- PL
- Purchaser's Order Line Number
- SN
- Serial Number
Item Detail (Shipment)
To specify line-item detail relative to shipment
John Deere requires this segment at the item level.
The total shipped quantity is specified, along with the unit of measure. The segment is required of each part number (LIN segment). If this quantity does not agree with the total of all load quantities below, an EDI 824 error message is generated to the supplier and the lesser of the two quantities is assumed to be correct.
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.
Subline Item Detail
To specify product subline detail item data
Deere uses this segment for communicating configurable options on a base whole good machines identified at the line-item. Quantities, part number and descriptions should always be sent. Option pricing may be included in this segment, but the item price should include these costs.
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.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- A
- Add
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
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.
- BP
- Buyer's Part Number
- PD
- Part Number Description
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- PD
- Part Number Description
Measurements
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
This is an optional segment containing total weight of the shipped quantity for the line item.
Code identifying the broad category to which a measurement applies
- PD
- Physical Dimensions
Code identifying a specific product or process characteristic to which a measurement applies
- G
- Gross Weight
- N
- Actual Net Weight
- WT
- Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- 01
- Actual Pounds
Only used by Worldwide Logistics.
- 24
- Theoretical Pounds
Only used by Worldwide Logistics.
- 50
- Actual Kilograms
Only used by Worldwide Logistics.
- 53
- Theoretical Kilograms
Only used by Worldwide Logistics.
- KG
- Kilogram
- LB
- Pound
Reference Identification
To specify identifying information
This optional segment at the item level may be included to provide additional information/references for the identified material.
Code qualifying the Reference Identification
- DP
- Department Number
- IK
- Invoice Number
Manufacturer's invoice number for vehicle/component.
Required by Deere Mexican units at header-level or item-level location depending on shipment makeup for invoice matching.
- KB
- Beginning Kanban Serial Number
- LF
- Assembly Line Feed Location
- PK
- Packing List Number
This number must not repeat within 13 months.
- SE
- Serial Number
Used for whole good or component serial numbers.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The packing list reference, when provided, will be used as the invoice number ERS.
Load Detail
To specify the number of material loads shipped
Each containers/cartons should be referenced in a CLD segment with the sum of those CLD quantities equaling the SN1 quantity.
Use one CLD loop for each license plate number.
Reference Identification
To specify identifying information
This segment may be included to provide additional detail information.
The "KB" qualifier indicates the Kanban serial number for the load. If part is on Controlled Delivery (862 Shipping Schedule), a 'KB' (trigger number) qualifier in the REF segment is required for each load or container and cannot be duplicated. If used at this level the quantity in the CLD equals trigger quantity.
The "98" qualifier replaces the CLD03 Packaging Code. The internal packaging value is required for each CLD.
The "LA" qualifier identifies the Shipping Label (License plate) for the container/carton and is required for each CLD.
Code qualifying the Reference Identification
- 97
- Package Number
A serial number indicating unit shipped.
- 98
- Container/Packaging Specification Number
- CR
- Customer Reference Number
- IK
- Invoice Number
Manufacturer's invoice number for vehicle/component.
Required by Deere Mexican units at header-level or item-level location depending on shipment makeup for invoice matching.
- KB
- Beginning Kanban Serial Number
- LA
- Shipping Label Serial Number
- LT
- Lot Number
- PC
- Production Code
- RS
- Returnable Container Serial Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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.
John Deere requires CTT segment, the count all hierarchical levels used.
Total number of line items in the transaction set
Number of line items (CTT01) is the accumulation of the number of HL segments.
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
Hash Total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
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
Master Pallet/Pack
BSN*00*3660239*20190308*13450196*0003
DTM*011*20190306*13380000
HL*1**S
REF*2I*JDGV1234567
N1*ST*RYDER INTEGRATED LOGISTICS*1*964475974
HL*2*1*P
CLD*1*3
REF*98*PALLET1
REF*LA* DESUPPLIERID000A0641
HL*3*2*O
PRF*5500000002
HL*4*3*I
LIN**BP*Part345*PL*0020
SN1**30*PC
REF*DP*LSC
REF*PK*30601
CLD*1*10
REF*98*BOX25
REF*RS*RC123
REF*LA* DESUPPLIERID000A0642
CLD*1*10
REF*98*BOX25
REF*LA* DESUPPLIERID000A0643
CLD*1*10
REF*98*BOX25
REF*LA* DESUPPLIERID000A0644
CTT*1
SE*29*0021
Mixed Pallet/Pack
BSN*00*3660239*20190308*13450196*0003
DTM*011*20190306*13380000
HL*1**S
REF*2I*JDGV1234567
N1*ST*RYDER INTEGRATED LOGISTICS*1*964475974
HL*2*1*P
CLD*1*2
REF*98*PALLET3
REF*LA* DESUPPLIERID000A0645
HL*3*2*O
PRF*5500000003
HL*4*3*I
LIN**BP*Part678*PL*00010
SN1**15*PC
REF*DP*LSC
REF*PK*30601
CLD*1*15
REF*98*BOX90
REF*LA* DESUPPLIERID000A0646
HL*5*2*O
PRF*5500000004
HL*6*5*I
LIN**BP*Part901*PL*00020
SN1**10*PC
REF*DP*LSC
REF*PK*30601
CLD*1*10
REF*98*BOX25
REF*LA* DESUPPLIERID000A0647
CTT*2
SE*32*0021
Single Order
BSN*00*3660239*20190308*13450196*0003
DTM*011*20190306*13380000
HL*1**S
MEA*PD*G*22*KG
TD5*B*2*IDENTIFICATIONCODE
TD3*TL*XXXX*XXXXXXXXXX
REF*2I*JDGV1234567
N1*ST*RYDER INTEGRATED LOGISTICS*1*964475974
HL*2*1*P
CLD*1*1
HL*3*2*O
PRF*5500000001
HL*4*3*I
LIN**BP*Part123*PL*0010
SN1**5*PC
REF*DP*LSC
REF*PK*30601
CLD*1*5
REF*98*CB101008
REF*KB*00000000001
REF*LA*DESUPPLIERID000A0640
REF*RS*PD6776
CTT*1
SE*25*0021
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.