Mazda
/
Advance Shipping Notice
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Mazda. Contact Mazda for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Mazda logo

X12 856 Advance Shipping Notice

X12 Release 2002

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • sample 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/mazda/advance-shipping-notice/01HPSY5BJCD9NCKH3T4D496TDC
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
detail
HL Loop
MEA
15
Measurements
Max use 40
Required
TD1
18
Carrier Details (Quantity and Weight)
Max use 20
Optional
TD5
19
Carrier Details (Routing)
Max use 12
Required
TD3
20
Carrier Details (Equipment)
Max use 12
Required
REF
22
Reference Numbers
Max use 200
Required
HL Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Max use 1
Required
GS

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related Transaction Sets.

SH
Ship Notice/Manifest (856)
GS-02
142
Application Sender's Code
Required
Identifier (ID)
Min 2Max 12

Code identifying party sending transmission.

GS-03
124
Application Receiver's Code
Required
Identifier (ID)
Min 2Max 12

Code identifying party receiving transmission.

GS-04
29
Data Interchange Date
Required
Date (DT)
YYMMDD format

Date sender generated a functional group of transaction sets.

GS-05
30
Data Interchange Time
Required
Time (TM)
HHMM format

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.)

GS-06
28
Data Interchange Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender.

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version/Release/ Industry ID Code
Required
Identifier (ID)

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).

002002MNAO

Heading

ST
2
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set ID
Required
Identifier (ID)

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N0)
Min 4Max 9

Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)

BSN
3
Heading > BSN

Beginning Segment Receiving Advice

RequiredMax use 1

To transmit identifying numbers, dates and other basic data relating to the transaction set

Example
BSN-01
353
Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set.

00
Original
01
Cancel
05
Replace
12
Test
BSN-02
396
ASN Number
Required
String (AN)
Min 6Max 8

A unique control number assigned by the original shipper to identify a specific shipment.

Usage notes

Unique supplier defined 8 character code.

BSN-03
373
ASN Issue Date
Required
Date (DT)
YYMMDD format

Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).

  • BSN03 is the date the shipment transaction set is created.
BSN-04
337
ASN Issue Time
Required
Time (TM)
HHMM format

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.
DTM
5
Heading > DTM

Date/Time Reference

RequiredMax use 10

Indicates the date and time that the parts will arrive at MNAO.

Example
DTM-01
374
Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time.

  • At least one of DTM02 or DTM03 must be present.
Usage notes

Use "017" for delivery orders to indicate estimated date and time of arrival of parts.
Use “011” for shipment orders to indicate date and time shipment leaves supplier premises.

011
Shipped
017
Estimated Delivery
Required
Date (DT)
YYMMDD format

Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).

Required
Time (TM)
HHMM format

Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359).
Also see: Time Qualifier (176).

Heading end

Detail

HL Loop
RequiredMax >1
MEA
15
Detail > HL Loop > MEA

Measurements

RequiredMax use 40

To specify physical measurements, including dimensions, tolerances, weights and counts.

Example
MEA-01
737
Measurement Reference ID
Required
Identifier (ID)

Code specifying the application of physical measurement cited.

  • At least least one of MEA03 or MEA05 must be present.
PD
Physical Dimensions
MEA-02
738
Measurement Dimension Qualifier ID
Required
Identifier (ID)

Code identifying the type of measurement.

G
Gross Weight
N
Net Weight
MEA-03
739
Measurement Value
Required
Decimal number (R)
Min 1Max 10

The value of the measured dimension.

MEA-04
355
Unit of Measurement
Required
Identifier (ID)

Code identifying the basic unit measurement.

KG
Kilogram
LB
Pound
TD1
18
Detail > HL Loop > TD1

Carrier Details (Quantity and Weight)

OptionalMax use 20

To specify the transportation details relative to commodity, weight and quantity.

Example
TD1-01
103
Packaging Code
Required
Identifier (ID)
Min 5Max 5

Code identifying the type of packaging. Part 1. Packaging form. Part 2.
Packaging Material.

  • If TD101 is present, then TD102 is required.
Usage notes

Any ANSI defined code is acceptable

TD1-02
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity. Also see: Unit of Measurement Code (355.)

Usage notes

Number of packages of the type specified in TD101

TD5
19
Detail > HL Loop > TD5

Carrier Details (Routing)

RequiredMax use 12

To specify the carrier, sequence of routing and to provide transit time information

Example
TD5-01
133
Routing Sequence Code
Required
Identifier (ID)

Code describing the relationship of a carrier to a specific shipment movement.

B
Origin/Delivery Carrier
TD5-02
66
ID Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67).

02
TD5-03
67
ID Code
Required
Identifier (ID)
Min 2Max 4

Code identifying a party.

Usage notes

Carrier’s SCAC Code

Required
Identifier (ID)

Code specifying the method of transportation for the shipment.

A
Air
AE
Air Express
E
Expedited Truck
G
Piggyback
H
Customer Pickup
JT
Just-in-Time
LT
Less than truckload
M
Motor
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
UPS
W
Inland Waterway
ZZ
On Hand at pool
TD3
20
Detail > HL Loop > TD3

Carrier Details (Equipment)

RequiredMax use 12

To specify transportation details relating to the equipment used by the carrier.

Example
TD3-01
40
Equipment Description Code
Required
Identifier (ID)
Min 2Max 2

Code identifying type of equipment used for shipment.

Usage notes

Use any ANSI defined code

TD3-02
206
Equipment Initial
Optional
String (AN)
Min 1Max 4

Prefix or alpha part of an equipment unit's identifying number.

Usage notes

If TD504 indicates rail, piggyback or ocean shipment – use equipment owners code: otherwise not used

TD3-03
207
Equipment Number
Required
String (AN)
Min 1Max 7

Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred).

Usage notes

Conveyance Number

REF
22
Detail > HL Loop > REF

Reference Numbers

RequiredMax use 200

To transmit identifying numbers associated with the named party.

Usage notes

Please note there is a required format for the REFDO segment. The first 6 digits are the Mazda PO number followed by the 3 digit Line Item sequence Number. Characters 1-6 are the Mazda PO number and 7-9 are the PO Line number. REFDO is a required segment.

Example
REF-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

Usage notes

Used at shipment and item levels. The use of at least one REF segment with a qualifier of “BM” or “AW” is required. The use of one REF segment to provide packing slip number is required at shipment or item level. The DO number must be provided for shipments against releases (830) and purchase orders (850).

AW
Airbill Number
BM
Bill of Lading
CO
Dealer Direct
DO
Delivery Order Number
FR
Freight Bill Number
HC
Heat Code
LS
Label Serial Number
LT
Lot Number
PK
Packing Slip
SN
Seal Number
VM
Vessel Name
REF-02
127
Reference Number
Required
String (AN)
Min 1Max 30

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).

N1 Loop
RequiredMax >1
N1
29
Detail > HL Loop > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name and code

Usage notes

Used to identify parties associated with the shipment. The ship-from and ship-to segments are mandatory.

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity or a physical location.

  • At least one of N102 or N103 must be present.
SF
Ship From
ST
Ship To
SU
Supplier
N1-03
66
ID Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67).

92
Assigned by Buyer
N1-04
67
ID Code
Required
Identifier (ID)
Min 2Max 5

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.
Usage notes

Code of issuer, shipper, or receiver.
Example:
"ST" = CH - receiver
"SF” = P1795 - shipper

Example values
  • CH
  • P1795
N1 Loop end
HL Loop
OptionalMax >1
LIN
8
Detail > HL Loop > HL Loop > LIN

Line Item Detail

RequiredMax use 1

To specify basic item identification data.

Example
LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

BP
Buyer's Part Number
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

Usage notes

Buyer part number

SN1
10
Detail > HL Loop > HL Loop > SN1

Item Detail (Shipment)

RequiredMax use 1

To specify line item detail relative to shipment

Usage notes

Used to denote ASN quantity.

Example
SN1-02
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 7

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set. Also see: Unit of Measurement Code (355).

Usage notes

Shows quantity shipped for part number referenced in the associated LIN segment

SN1-03
355
Unit of Measure Code
Required
Identifier (ID)
Min 2Max 2

Code identifying the basic unit measurement.

  • SN103 defines the unit of measurement for both SN102 and SN104.
SN1-04
646
Quantity Shipped to Date
Optional
Decimal number (R)
Min 1Max 9

Number of units shipped to date.

Usage notes

Used only with suppliers with CUM requirements

REF
22
Detail > HL Loop > HL Loop > REF

Reference

OptionalMax use 200

To transmit identifying numbers. Used to show shipping label serial numbers.

Usage notes

Please note there is a required format for the REFDO segment. The first 6 digits are the Mazda PO number followed by the 3 digit Line Item sequence Number. Characters 1-6 are the Mazda PO number and 7-9 are the PO Line number. REFDO is a required segment.

Example
REF-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

DO
Delivery Order Number
LS
Bar Coded Shipping Label
REF-02
127
Reference Number
Optional
String (AN)
Min 1Max 30

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).

Usage notes

Shipping label

CLD Loop
OptionalMax 200
CLD
24
Detail > HL Loop > HL Loop > CLD Loop > CLD

Customer's Load Detail

RequiredMax use 1

Gives information concerning number of containers and quantity per container.

Example
CLD-01
622
Number of Customer Loads
Required
Numeric (N0)
Min 1Max 5

Number of Customer-defined loads shipped by the supplier.

Usage notes

Number of Containers

CLD-02
382
Units Shipped
Required
Decimal number (R)
Min 1Max 7

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set. Also see: Unit of Measurement Code (355).

Usage notes

Number of units per container

CLD-03
103
Packaging Code
Required
Identifier (ID)
Min 5Max 5

Code identifying the type of packaging. Part 1. Packaging form. Part 2.
Packaging Material.

Usage notes

Any ANSI defined code is acceptable

CLD Loop end
HL Loop end
HL Loop end
Detail end

Summary

CTT
41
Summary > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set.

  • If CTT03 is present, then CTT04 is required.
Usage notes

Hash total of quantities shipped

CTT-02
347
Quantity Hash Totals
Required
Decimal number (R)
Min 1Max 10

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.

## Example:
-.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.
Usage notes

Hash total of quantities shipped (from SN102)

SE
42
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments, including the beginning (ST) and ending (SE) segments.

Example
SE-01
96
Number of Segments
Required
Numeric (N0)
Min 1Max 6

Total number of segments included in a transaction set including ST and SE segments.

SE-02
329
Transaction Set Control Number
Required
Numeric (N0)
Min 4Max 9

Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element.

GE-02
28
Data Interchange Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender.

EDI Samples

sample 1

ST*856*1019
BSN*00*052625*940513*1606
DTM*017*940514*1830
HL*1**S
MEA*PD*G*34270*LB
TD1*PLT90*1
TD5*B*02*RDWY*M
TD3*TL**1028A
REF*BM*KPX8901
REF*PK*849302
N1*SF**92*P1795
N1*ST**92*CH
HL*2*1*I
LIN**BP*GA2E68520D
SN1**20*PC
REF*DO*111786019
REF*LS*S23275
CLD*1*20*PLT90
CTT*2*20
SE*20*1019

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.