Click or drag to resize

856 - ASN

Purpose

This document provides the format and establishes the data contents of a Ship Notice/Manifest (ASN) set.

This implementation guide is tailored to Ultriva's use of the AISI X12 004010 Guidelines. Segment position, segment requirement designation, segment maximum use, loop repeat and element requirement designation are Ultriva specific and may differ from the AISI X12 standards. Segments show only those elements that Ultriva requires.

Segment Map

Segment

Name

Req

Max Use

Repeat

Header

ST

Transaction Set Header

M

1

BSN

Beginning Segment for Ship Notice

M

1

Detail

Loop: HL

1

HL

Hierarchical Level - Shipment

M

1

TD1

Carrier Details - Net Weight (Shipment)

M

1

TD5

Carrier Details - Routing Sequence/Transit Time (Shipment)

M

1

REF

Reference – Shipment ID Number (Shipment)

M

1

REF

Reference Way Bill No (Tracking No)

O

1

REF

Reference BOL

O

1

DTM

Date/Time Reference - Shipped

M

1

Loop id: HL/NI

1

N1

Name - Ship From (Shipment)

M

1

N1

Name - Ship To (Shipment)

M

1

Loop id: HL

>1

HL

Hierarchical Level – Order

M

1

PRF

Purchase Order Reference (Item)

M

1

Loop id: HL

>1

HL

Hierarchical Level (Item)

M

1

LIN

Item Identification (Item)

M

1

SN1

Item Detail (Shipment)

M

1

REF

Reference Kanban Card ID (Release ID)

M

1

SE

Transaction Set Trailer

M

1

ISA Interchange Control Header

Note Note

Purpose: To start and identify an interchange of one or more functional groups and interchange related control segments.

Example: ISA*00**00**01*001413764*ZZ*VEN1234567*990811*1530*U*00401*00000003*0*P*~

Element

Description

Values

Req

Comments

ISA01

Authorization Information Qualifier

00

M

Plan to use 00 (No authorization information present)

ISA02

Authorization Information

M

Will contain spaces

ISA03

Security Information Qualifier

00

M

Plan to use 00 (No security information present)

ISA04

Security Information

M

Will contain spaces

ISA05

Interchange ID Qualifier

01

M

Vendor qualifier

ISA06

Interchange Sender ID

000000000

M

Vendor id

ISA07

Interchange ID Qualifier

01

M

Customer supplied qualifier

ISA08

Interchange Receiver ID

000000000

M

Customer's ID

ISA09

Interchange Date

YYMMDD

M

Will contain the date of the interchange in the YYMMDD format

ISA10

Interchange Time

HHMM

M

Will contain the date of the interchange in HHMM format

ISA11

Interchange Control Standards ID

U

M

Will contain U (US EDI)

ISA12

Interchange Control Version Number

00401

M

Y2K compliant version 4010

ISA13

Interchange Control Number

M

Unique sequentially incrementing numbers

ISA14

Acknowledgement Requested

0

M

Plan to use 0 (No TA1 Acknowledgement requested)

ISA15

Usage Indicator

T or P

M

Will use T (test) or P (production) to indicate status of data

ISA16

Component Element Separator

M

Will contain spaces

GS Functional Group Header

Note Note

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

Example: GS*SH*001413764*VEN1234567*20000315*1530*12*X*00401~

Element

Description

Values

Req

Comments

GS01

Functional ID Code

SH

M

SH = 856, ASN

GS02

Application Sender’s Code

000000000

M

Vendor ID

GS03

Application Receiver’s Code

000000000

M

Customer’ ID

GS04

Date

CCYYMMDD

M

Date that vendor generated the functional group of transaction sets

GS05

Time

HHMM

M

Time that Customer generated the functional group of transaction sets

GS06

Group Control Number

M

Unique number assigned to the group header by Customer

GS07

Responsible Agency Code

X

M

Will contain X (Accredited Standards Committee X12)

GS08

Version/Release ID Code

004010

M

Will contain version/release of group being transmitted

ST Transaction Set Header

Note Note

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

Example: ST*856*00083~

Element

Description

Values

Req

Comments

ST01

Transaction Set ID Code

856

M

856 = ASN

ST02

Transaction Set Control Number

M

BSN Beginning Segment for Ship Notice

Note Note

Purpose: The BSN02 is a unique number that references the entire 856 Ship Notice.

Example: BSN*00*258522*200020830*144010~

Element

Description

Values

Req

Comments

BSN01

Transaction Set Identifier Code

00

M

00 = Original Order

BSN02

Shipment Identification

M

This identification is assigned by the shipper and cannot repeat in a calendar year

BSN03

Date - Transaction

CCYYMMDD

M

BSN04

Time - Transaction

M

HL Hierarchical Level – Shipment

Note Note

Purpose: There is one Shipment HL per ASN (The Shipment HL has children (orders), so its HL04 is 1.).

Example: HL*1**S*1~

Element

Description

Values

Req

Comments

HL01

Hierarchical ID Number

1

M

The value of the shipment HL01 is always 1

HL03

Hierarchical Level Code

S

M

S Shipment

HL04

Hierarchical Child Code

1

M

1 Additional Subordinate HL Data Segment in this Hierarchical Structure

TD1 Carrier Details – Net Weight (Shipment)

Note Note

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

Example: TD1*PCS*1****A3*4620*LB~

Element

Description

Values

Req

Comments

TD101

Packaging Code

PCS

M

TD102

Lading Quantity

1

M

TD106

Weight Qualifier

A3

M

N Actual Net Weight

A3 Shippers Weight

TD107

Weight

N

M

TD108

Unit or Basis for Measurement Code

LB

M

LB Pounds

TD5 Carrier Details (Routing Sequence/Transit Time)

Note Note

Purpose: To specify the carrier and sequence of routing and provide transit time information.

Example: TD5**2*DLNT**DLNT*CC~

Element

Description

Values

Req

Comments

TD502

Identification Code Qualifier

TD503

Identification Code

M

CarrierCode – Should Match that in Ultriva

TD505

Routing

TD506

Shipment/Order Status Code

REF Shipment ID Number (Shipment)

Note Note

Purpose: This REF is used to send Shipment ID Number for this transaction set. This shipment transaction is for an order.

Example: REF*MA*258522~

Element

Description

Values

Req

Comments

REF01

Reference Identification Qualifier

MA

M

MA Ship Notice/Manifest Number

REF02

Reference Identification

M

REF Shipment ID Number (Shipment)

Note Note

Purpose: This REF is used to send Shipment ID Number for this transaction set. This ref is used to send the tracking number of the carrier for the shipment.

Example: REF*WY*258522~

Element

Description

Values

Req

Comments

REF01

Reference Identification Qualifier

WY

M

WY Way bill number of the shipper

REF02

Reference Identification

M

DTM Date/Time Reference – Shipped

Note Note

Purpose: This DTM is used to provide the vehicle departure date and time.

Example: DTM*011*20020830*144010*ED~

Element

Description

Values

Req

Comments

DTM01

Date/Time Qualifier

001

M

001 = Shipped

DTM02

Date

CCYYMMDD

M

Delivery Requested Date in CCYYMMDD format

DTM03

Time

Use sender's local time

DTM04

Time Code

CD Central Daylight Time

CS Central Standard Time

ED Eastern Daylight Time

ES Eastern Standard Time

MD Mountain Daylight Time

MS Mountain Standard Time

PD Pacific Daylight Time

PS Pacific Standard Time

N1 Ship From (Shipment)

Note Note

Purpose: This N1 is used to identify the Ship From location.

Example: N1*SF*XYZ*1*123263~

Element

Description

Values

Req

Comments

N101

Entity ID Code

SF

M

SF = Ship From

N102

Name

M

Ship From Name

N103

Identification Code Qualifier

M

N104

Identification Code

M

N1 Ship To (Shipment)

Note Note

Purpose: This N1 is used to identify the Ship To location.

Example: N1*ST*ABC*92*000A~

Element

Description

Values

Req

Comments

N101

Entity ID Code

ST

M

ST = Ship To

N102

Name

M

Ship To Name

N103

Identification Code Qualifier

M

N104

Identification Code

M

HL Hierarchical Level – Order

Note Note

Purpose: ASN is generated for each order. Each order-level HL will be followed by an item-level HL for each item on that order. HL01 is used to indicate the number of occurrences of the HL segment, and the value of HL01 is "1" for the initial HL segment and is incremented by one in each subsequent HL segment within the transaction set. HL02 identifies the hierarchical ID number of the segment to which the current HL segment is subordinate. The HL02 for the Order HL is always 1, since its parent is the shipment. The Order HL has children (items), so its HL04 is 1.

Example: HL*2*1*O*1~

Element

Description

Values

Req

Comments

HL01

Hierarchical ID Number

2

M

The HL occurrence number, incremented sequentially from the ID Number of the Shipment level HL

HL02

Hierarchical Parent ID Number

1

M

This will always be 1 on the Order HL, in reference to the Shipment level HL

HL03

Hierarchical Level Code

O

M

O Order

HL04

Hierarchical Child Code

1

M

1 Additional Subordinate HL Data Segment in this Hierarchical Structure. This code indicates that there are child data segments subordinate to this level

PRF Purchase Order Reference

Note Note

Purpose: To provide reference to a specific purchase order.

Example: PRF*265857***20101209~

Element

Description

Values

Req

Comments

PRF01

Purchase Order Number

M

PRF04

Date

CCYYMMDD

M

HL Hierarchical Level – Item

Note Note

Purpose: The HL01 is used to indicate the number of occurrences of the HL segment, and the value of HL01 is "1" for the initial HL segment and is incremented by one in each subsequent HL segment within the transaction set. HL02 identifies the hierarchical ID number of the segment to which the current HL segment is subordinate. The HL02 for the Item HL is the number used in its parent Order HL01. The Item HL has no children, so its HL04 is 0, or it may be omitted.

Example: HL*3*2*I~

Element

Description

Values

Req

Comments

HL01

Hierarchical ID Number

3

M

The HL occurrence number

HL02

Hierarchical Parent ID Number

2

M

HL03

Hierarchical Level Code

I

M

I Item

HL04

Hierarchical Child Code

0

M

No Subordinate HL Data Segment in This Hierarchical Structure.

Notes: This code indicates that there are child data segments subordinate to this level.

LIN Item Identification (Item)

Note Note

Purpose: To specify the basic and most frequently used shipment line item data.

Example: LIN*1*VO*WV8860B1309/P*BP*318618-000~

Element

Description

Values

Req

Comments

LIN01

Assigned Identification

1

LIN02

Product/Service ID Qualifier

VO

M

Vendor's Order Number

LIN03

Product/Service ID

M

LIN04

Product/Service ID Qualifier

BP

M

BP –customer item number

LIN05

Product/Service ID

M

SN1 Item Detail (Shipment)

Note Note

Purpose: To specify line-item detail relative to shipment.

Example: SN1**200*EA~

Element

Description

Values

Req

Comments

SN102

Number of Units Shipped

M

No of unit shipped on the for the card

SN103

Unit or Basis for Measurement Code

EA

M

EA Each

REF Kanban Release ID

Note Note

Purpose: To specify the Kanban Release ID for the line item data.

Example: REF*LF*KCD3VZ8AWHEJ-002-8* Release ID~

Element

Description

Values

Req

Comments

REF01

Service ID

LF

M

Means Next field is Kanban Release ID

REF02

Service ID Qualifier

KCD00000-0001

M

Kanban Release ID

REF03

Service ID Description

RELEASE ID

M

Description of REF02 field

SE Transaction Set Trailer

Note Note

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments.

Example: SE*00083~

Element

Description

Values

Req

Comments

SE01

Number of Included Segments

M

A count of the number of segments in the transaction

SE02

Transaction Set Control Number

M

Will match the transaction set control number in the ST02 element

GE Functional Group Trailer

Note Note

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

Example: GE*3*0003~

Element

Description

Values

Req

Comments

GE01

Number of Transaction Sets Included

M

Number of transactions in functional group

GE02

Group Control Number

M

Control Number

IEA Interchange Control Trailer

Note Note

Purpose: To define the end of an interchange of one or more functional groups and interchange-related control segments.

Example: IEA*4*0003~

Element

Description

Values

Req

Comments

IEA01

Number of Included Functional Groups

M

Number of functional groups in interchange

IEA02

Interchange Control Number

M

Control Number (must match ISA control number)

Sample 856

ISA*00* *00* *01*001100000 *01*000012000*101216*1409*U*00400*000000034*0*T*>~

GS*SH*001325240*001100000*000012000*1409*34*X*004010~

ST*856*0001~

BSN*14*9167401*20101215*1719*0002~

HL*1*1*S~TD1*PCS*1****A3*4620*LB~

TD5**2*DLNT**DLNT*CC~REF*MA*9167401~

REF*WY*530626~DTM*011*20101215~

N1*SF*SDC-Distribution Center~

N1*ST*AMERICAN SHIP*92*AMC~

HL*2*1*O~

PRF*265857***20101209~

HL*3*2*I~

LIN*1*VO*SSW860B1309/P*BP*001E18-000~

SN1**200*EA~

REF*LF*KCD2WZ8AWHEJ-002-8~

SE*17*0001~

GE*1*34~

IEA*1*000000034~