X12 856 Ship Notice/Manifest
This standard provides the standardized format and establishes the data contents of a ship notice/manifest transaction set within the context of an electronic data interchange (EDI) environment. A ship notice/manifest 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
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.
Code identifying party receiving transmission.
Date sender generated a functional group of transaction sets.
Time (HHMM) expressed in 24-hour clock time when the sender generated a functional group of transaction sets (local time at sender's location).
(Time range: 0000 through 2359.)
Assigned number originated and maintained by the sender.
Code used in conjunction with the version data element to identify the issuer of the standard.
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, and industry ID of the EDI standard being used. Positions: 1 - 3, Major Version Number; Positions: 4 - 6, Release Level of Version; Positions: 7 - 12, Industry or Trade Association ID (Optionally assigned by user).
- 002002FORD
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) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).
- 856
- X12.10 Ship Notice/Manifest
Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)
Beginning Segment for Ship Notice
To transmit identifying numbers, dates and other basic data relating to the transaction set
Code identifying purpose of transaction set.
- 00
- Original
- 01
- Cancellation
- 05
- Replace
- 08
- Status
Arrival
- 12
- Not Processed
A unique control number assigned by the original shipper to identify a specific shipment.
ASN number - Unique supplier assigned number that is not to be repeated within a one year period. Packing slip number should be used as the ASN number. Although the standard allows a 30 character ASN number, Ford's
maximum is 11 characters.
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
- BSN03 is the date the shipment transaction set is created.
Date of ASN creation (YYMMDD).
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359).
Also see: Time Qualifier (176).
- BSN04 is the time the shipment transaction set is created.
Time of ASN creation (HHMM).
Date/Time Reference Estimated Delivery
To specify pertinent dates and times
An occurrence of the "DTM" segment with a code value of "011" is mandatory in the Heading area. Use a date/time qualifier (DTM01) value of "011" (shipped date/time) for shipment orders or a date/time qualifier (DTM01) value of "017" (expected delivery date/time) for the delivery orders.
Code specifying type of date or time, or both date and time.
- At least one of DTM02 or DTM03 must be present.
Actual date and time of arrival. Used only by
pool/consolidation points for arrival ASNs.
- 017
- Estimated Delivery
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359).
Also see: Time Qualifier (176).
Date/Time Reference Received
To specify pertinent dates and times
An occurrence of the "DTM" segment with a code value of "011" is mandatory in the Heading area. Use a date/time qualifier (DTM01) value of "011" (shipped date/time) for shipment orders or a date/time qualifier (DTM01) value of "017" (expected delivery date/time) for the delivery orders.
Code specifying type of date or time, or both date and time.
- At least one of DTM02 or DTM03 must be present.
Estimated date and time of arrival - required for delivery
orders. Not used by assembly plants.
- 050
- Received
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359).
Also see: Time Qualifier (176).
Date/Time Reference Shipped
To specify pertinent dates and times
An occurrence of the "DTM" segment with a code value of "011" is mandatory in the Heading area. Use a date/time qualifier (DTM01) value of "011" (shipped date/time) for shipment orders or a date/time qualifier (DTM01) value of "017" (expected delivery date/time) for the delivery orders.
Code specifying type of date or time, or both date and time.
- At least one of DTM02 or DTM03 must be present.
Date and time shipment leaves supplier premises -
required for shipment orders.
- 011
- Shipped
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359).
Also see: Time Qualifier (176).
Detail
The HL segment is used to identify levels of detail information using hierarchical structure, such as relating line item data to shipment data and packaging data to line item data. Ford needs are satisfied by the use of the shipment and item levels. At least one occurrence of the HL at the shipment and item level is mandatory for original (BSN01 = "00") ASNs.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
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
Measurements
To specify physical measurements, including dimensions, tolerances, weights and counts.
At shipment hierarchical level:
- Gross weight of shipment (mandatory)
- Net weight of shipment (mandatory for rail shipments)
At item hierarchical level:
- Gross piece weight (optional)
- Net piece weight (optional)
Code specifying the application of physical measurement cited.
- At least least one of MEA03 or MEA05 must be present.
- PD
- Physical Dimensions (Product Ordered)
Code identifying the type of measurement.
- At least one of MEA03 or MEA06 must be present.
- G
- Gross Weight
- N
- Actual Net Weight
The value of the measured dimension.
- If MEA03 is present, then MEA05 or MEA06 is required.
Value referred to by MEA02.
Code identifying the basic unit measurement.
- KG
- Kilogram
- LB
- Pound
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight and quantity.
For purchased parts use number of pallets, loose cartons, separate bins etc. If mixed loose packaging types in shipment, use a TD1 for each type.
Code identifying the type of packaging. Part 1. Packaging form. Part 2.
Packaging Material.
- If TD101 is present, then TD102 is required.
Number of units (pieces) of the lading commodity. Also see: Unit of Measurement Code (355.)
- If TD103 is present, then TD104 is required.
Number of packages of the type specified in TD101.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier, sequence of routing and to provide transit time information
One TD5 is mandatory for each shipment. Up to three TD5 segments can be used. However, the second and third should only be used to specify additional carrier identifiers (TD503).
Code describing the relationship of a carrier to a specific shipment movement.
- At least one of TD502, TD504, or TD505 must be present.
- B
- Origin/Delivery Carrier (Any Mode)
Code designating the system/method of code structure used for Identification Code (67).
- If TD502 is present, then TD503 is required.
- 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; use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
Standard Carrier Alpha Code (SCAC)
- 02
- Standard Carrier Alpha Code (SCAC)
Code identifying a party.
- If TD507 is present, then TD508 is required.
Carriers SCAC code.
OVLD
RDWY
JONS
Code specifying the method of transportation for the shipment.
- If TD510 is present, then TD511 is required.
Note: A data maintenance request to add the TD504 Mode Codes identified
with an "*" is pending with ANSI X12.
- A
- Air
- AE
- Air Express
- C
- Consolidation
- E
- Expedited Truck
- G
- Piggyback
- H
- Customer Pickup
- JT
- Just in time
- LT
- Less Than Trailer Load (LTL)
- M
- Motor (Common Carrier)
- O
- Containerized Ocean
- PA
- Pooled Air
- PC
- Private Carrier
- PG
- Pooled Piggyback
- PP
- Pool to pool
- PR
- Pooled Rail
- PT
- Pooled Truck
- R
- Rail
- RR
- Roadrailer
- S
- Ocean
- U
- Private Parcel Service
- W
- Inland Waterway
- ZZ
- On hand at pool
Code identifying type of Location Identifier (310) used.
- OR
- Origin (Shipping Point)
- PP
- Pool Point
Code which identifies a specific geographic location.
If air shipment - use airport code (ex. "BUF").
If shipment is from supplier to pool point - use Ford assigned code for pool point.
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier.
The use of one TD3 segment at the shipment level is mandatory by Ford. Only one TD3 segment is used per shipment. The TD3 segment is used to specify the conveyance number.
Code identifying type of equipment used for shipment.
- If TD302 is present, then TD303 is required.
TL
RR
Prefix or alpha part of an equipment unit's identifying number.
- If TD304 is present, then TD305, and TD306 are required.
If the TD504 indicates rail, piggyback or ocean shipment - use equipment
owner's code; otherwise not used.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred).
Conveyance number.
143607
1028A
Reference Numbers
To transmit identifying numbers.
Used at the shipment level for:
- Seal number - If seal number is available, specify it using this segment with a SN qualifier. Up to two seal numbers can be specified.
- Packing slip number - Transmit at shipment level if only one packing slip/shipper number for an ASN.
- Air bill number - Required if air shipment.
- Freight bill number - If available.
- Bill of lading - Required for ground, ocean, etc. transport types.
Note: The use of at least one REF segment with a qualifier of BM or AW is required.
Used at the item level for:
- Lot number - Required if applicable.
- Packing slip numbers - Transmit at item level if more than one packing
slip/shipper number for an ASN.
Note: The use of one REF segment to provide packing slip number is required at either the shipment or item level.
Note: The REF number element (REF02) must be left justified. Do not send
leading spaces or zeroes in this element.
Note: Assembly division only uses the last 6 characters of the reference number for REF segments with a REF01 qualifier of "FR", "PK", "BM", and "AW".
Code qualifying the Reference Number.
- At least one of REF02 or REF03 must be present.
- AW
- Air Waybill Number
- BM
- Bill of Lading Number
- CO
- Customer Order Number
- DO
- Delivery Order No.
- FR
- Freight Bill Number
- HC
- Heat Code
- LS
- Bar Coded Label Serial Number
- LT
- Lot Number
- PK
- Packing List Number
- SN
- Seal Number
- VM
- Vessel Name
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Ford will accept up to 16 characters for air and freight bill numbers; 17
characters for Dealer Direct data, and up to 12 characters for Vessel name. For all other entries in REF02, Ford will accept up to 11 characters except in the case of assembly division as specified in the note in general information.
07374288
850514
Date/Time Reference
To specify pertinent dates and times
The DTM segment is used at the item level to identify original supplier ship date and time. This use of the DTM segment is for Freight consolidators (pools) only.
Code specifying type of date or time, or both date and time.
- At least one of DTM02 or DTM03 must be present.
- 011
- Shipped
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359).
Also see: Time Qualifier (176).
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Used for international shipments only.
Code identifying payment terms for transportation charges.
- If FOB03 is present, then FOB02 is required.
- (FOB01) - indicates party will pay the carrier.
- CC
- Collect
- PP
- Prepaid (by Seller)
Code identifying the trade terms which apply to the shipment transportation responsibility. Six digit codes represent INCOTERMS.
Code identifying type of Location Identifier (310) used.
- FOB06 is the code specifying title passage location.
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
Name
To identify a party by type of organization, name and code
The ship-from "SF" and ship-to "ST" segments are mandatory at the shipment level, and must be identical to those used in the corresponding 830 (Material Release) and 862 (Shipment Schedule) N1 segments. Used at item level by pools and consolidators to identify the original supplier ship-from code at any subsequent shipping point.
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- IC
- Intermediate Consignee
- SF
- Ship From
- ST
- Ship To
- SU
- Supplier/Manufacturer
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying a party.
- 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.
If N101 - "ST", receiving plant.
If N101 - "SF", ship-from location.
If N101 - "SU", Supplier/Manufacturer
If N101 - "IC", Intermediate Consignees
1602A
P5008
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Used for international shipments only.
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Used for international shipments only.
- SE
- Selling Party
Code (Standard ISO) for country in whose currency the charges are specified.
- If CUR09 is present, then CUR07 is required.
Allowance, Charge or Service
To specify allowances, charges or services
Used for international shipments only.
Code which indicates an allowance or charge for the service specified.
- If ITA02 is present, then at least one of ITA03, or ITA13 is required.
- C
- Charge
Code identifying the agency assigning the code values used in data element 560.
- At least one of ITA06, ITA07, or ITA08 must be present.
- AX
- ANSI X12
Code identifying the special service.
- If ITA08 is present, then ITA09 is required.
- HC
- Handling Service
Code indicating method of handling for an allowance or charge.
- If ITA10 is present, then ITA11 is required.
- 06
- Charge to be Paid by Customer
Total dollar amount for the allowance or charge.
Handling charge total amount.
The HL segment is used to identify levels of detail information using hierarchical structure, such as relating line item data to shipment data and packaging data to line item data. Ford needs are satisfied by the use of the shipment and item levels. At least one occurrence of the HL at the shipment and item level is mandatory for original (BSN01 = "00") ASNs.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
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 subordinated 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 Detail
To specify basic item identification data.
For purchased parts, there will be one "LIN" segment in each item loop. It is used for buyer's part number and part number for returnable containers. This segment is mandatory for all ASNs. Ford part numbers may consist of a prefix, base, suffix and control code. Any of these, except the base, may or may not be present. The portions of the part number are delimited by one space. When shipping returnable containers,
whether empty or in use, create an item level for each returnable container part number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If LIN06 is present, then LIN07 is required.
- LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
Identifying number for a product or service.
- If LIN08 is present, then LIN09 is required.
Ford part number in form of prefix, base, suffix and control code - delimited by a space; or Ford returnable container part number.
ZE21
E6SP 7E396
7E396 AA 040
E6SP 7E39 AA 040
Item Detail (Shipment)
To specify line item detail relative to shipment
Used to show the quantity being shipped, the unit of measure, and the cumulative
year-to-date shipments. For Purchased parts, required at the item level
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set. Also see: Unit of Measurement Code (355).
Shows quantity shipped for part number referenced in the associated LIN
segment.
Code identifying the basic unit measurement.
- SN103 defines the unit of measurement for both SN102 and SN104.
Use unit of measure code shown on Ford material release (830).
Number of units shipped to date.
For CMMS plants, the cumulative quantity shipped for this model year,
including this ASN. Not used for returnable containers.
Subline Item Detail
To specify product subline detail item data
Used for international shipments only.
Code indicating the relationship of the subline item to the baseline item.
- If SLN09 is present, then SLN10 is required.
- SLN03 through SLN28 provide for eleven (11) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- I
- Included
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
- If SLN11 is present, then SLN12 is required.
Use quantity from SN102.
Code identifying the basic unit measurement.
- If SLN13 is present, then SLN14 is required.
Use Unit of Measure from SN103.
Price per unit of product, service, commodity, etc.
- If SLN15 is present, then SLN16 is required.
Unit price of part identified in LIN. Used for customs purposes only.
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser.
05141985JMM
4401985
Reference Numbers
To transmit identifying numbers.
Used at the shipment level for:
Seal number - If seal number is available, specify it using this segment with a
SN qualifier. Up to two seal numbers can be specified.
Packing slip number - Transmit at shipment level if only one packing slip/shipper
number for an ASN.
Air bill number - Required if air shipment.
Freight bill number - If available.
Bill of lading - Required for ground, ocean, etc. transport types.
Note: The use of at least one REF segment with a qualifier of BM or AW is
required.
Used at the item level for:
Lot number - Required if applicable.
Packing slip numbers - Transmit at item level if more than one packing
slip/shipper number for an ASN.
Note: The use of one REF segment to provide packing slip number is required at
either the shipment or item level.
Note: The REF number element (REF02) must be left justified. Do not send
leading spaces or zeroes in this element.
Note: Assembly division only uses the last 6 characters of the reference number for
REF segments with a REF01 qualifier of "FR", "PK", "BM", and "AW".
Code qualifying the Reference Number.
- At least one of REF02 or REF03 must be present.
- AW
- Air Waybill Number
- BM
- Bill of Lading Number
- CO
- Customer Order Number
- DO
- Delivery Order No.
- FR
- Freight Bill Number
- HC
- Heat Code
- LS
- Bar Coded Label Serial Number
- LT
- Lot Number
- PK
- Packing List Number
- SN
- Seal Number
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Note: Ford will accept up to 16 characters for air and freight bill numbers; 17
characters for Dealer Direct data, and up to 12 characters for Vessel name.
For all other entries in REF02, Ford will accept up to 11 characters except in
the case of assembly division as specified in the note in general information.
07374288
850514
Load Detail
To specify the number of material loads shipped.
This segment is used by the supplier to inform Ford of the number of containers (e.g.
pallets), and the quantity per container. Not used for returnable containers.
Number of Customer-defined loads shipped by the supplier.
Number of containers (skids, pallets, etc.)
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set. Also see: Unit of Measurement Code (355).
Quantity per load (number of units per container).
Code identifying the type of packaging. Part 1. Packaging form. Part 2.
Packaging Material.
Reference Numbers
To transmit identifying numbers.
Used to show shipping label serial numbers. If container has several sub-containers of
same part - show only master label serial number for container.
Code qualifying the Reference Number.
- At least one of REF02 or REF03 must be present.
- LS
- Bar Coded Label Serial Number
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Shipping label serial number.
S23275
M874210
Date/Time Reference
To specify pertinent dates and times
The DTM segment is used at the item level to identify original supplier ship date and
time. This use of the DTM segment is for Freight consolidators (pools) only.
Code specifying type of date or time, or both date and time.
- At least one of DTM02 or DTM03 must be present.
- 011
- Shipped
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359).
Also see: Time Qualifier (176).
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
Total number of line items in the transaction set.
- If CTT03 is present, then CTT04 is required.
Sum of values of the specific 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 leftmost 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.
- If CTT05 is present, then CTT06 is required.
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 assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)
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.
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.