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

X12 856 Advance Ship Notice

X12 Release 5010

This X12 Transaction Set 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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    detail
    HL Loop
    HL
    0100
    Hierarchical Level
    Max use 1
    Required
    TD1
    1100
    Carrier Details (Quantity and Weight)
    Max use 20
    Required
    TD5
    1200
    Carrier Details (Routing Sequence/Transit Time)
    Max use 12
    Required
    TD3 Loop
    REF
    1500
    Reference Information
    Max use 1
    Required
    DTM
    2000
    Date/Time Reference
    Max use 10
    Required
    FOB
    2100
    F.O.B. Related Instructions
    Max use 1
    Required
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

    To start and identify an interchange of zero or more functional groups and interchange-related control segments

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code identifying the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    Min 10Max 10

    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)

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code identifying the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    Min 10Max 10

    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)

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    Min 15Max 15

    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

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    Min 15Max 15

    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

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I65
    Repetition Separator
    Required
    Min 1Max 1

    Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

    ^
    Repetition Separator
    ISA-12
    I11
    Interchange Control Version Number
    Required

    Code specifying the version number of the interchange control segments

    00501
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code indicating sender's request for an interchange acknowledgment

    0
    No Interchange Acknowledgment Requested
    1
    Interchange Acknowledgment Requested (TA1)
    ISA-15
    I14
    Interchange Usage Indicator
    Required
    Min 1Max 1

    Code indicating whether data enclosed by this interchange envelope is test, production or information

    I
    Information
    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Component Element Separator
    Required
    Min 1Max 1

    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

    RequiredMax use 1

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

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related transaction sets

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

    Code identifying party sending transmission; codes agreed to by trading partners

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

    Code identifying party receiving transmission; codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    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)

    GS-06
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    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

    005010
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

    Heading

    ST
    0100

    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 Identifier Code
    Required

    Code uniquely identifying a Transaction Set

    • The transaction set identifier (ST01) is 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
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    BSN
    0200

    Beginning Segment for Ship Notice

    RequiredMax use 1

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

    Usage notes

    The document with the transaction set purpose code “01 - Cancellation” or “17 –Cancel, to be Reissued” at the BSN02 element can only be submitted after the original ASN is submitted with the code "00 - Original".

    Example
    BSN-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    Usage notes

    Other codes are not accepted.

    00
    Original
    01
    Cancellation
    17
    Cancel, to be Reissued
    BSN-02
    396
    Shipment Identification
    Required
    Min 2Max 30

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

    Usage notes

    Ship Notice number.

    BSN-03
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    • BSN03 is the date the shipment transaction set is created.
    BSN-04
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    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.
    BSN-05
    1005
    Hierarchical Structure Code
    Required

    Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

    0001
    Shipment, Order, Packaging, Item

    Pick and Pack Structure

    0002
    Shipment, Order, Item, Packaging

    Standard Carton Pack

    Detail

    HL Loop
    RequiredMax 200000
    HL
    0100

    Hierarchical Level

    RequiredMax use 1

    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.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    Min 1Max 12

    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.
    HL-03
    735
    Hierarchical Level Code
    Required

    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
    HL-04
    736
    Hierarchical Child Code
    Optional

    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.
    TD1
    1100

    Carrier Details (Quantity and Weight)

    RequiredMax use 20

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

    Example
    TD1-01
    103
    Packaging Code
    Required

    Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required

    03
    Hard Wood
    05
    Soft Wood
    25
    Corrugated or Solid
    58
    Metal
    67
    Multiple-wall Paper (2 or more walls)
    72
    Paper - VCI
    94
    Wood
    BAG
    Bag
    BOX
    Box
    CAS
    Case
    CTN
    Carton
    DRM
    Drum
    PCS
    Pieces
    PLT
    Pallet
    SKD
    Skid
    TD1-02
    80
    Lading Quantity
    Required
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    TD1-06
    187
    Weight Qualifier
    Required
    Min 1Max 2

    Code defining the type of weight

    TD1-07
    81
    Weight
    Required
    Min 1Max 10

    Numeric value of weight

    TD1-08
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    01
    Actual Pounds
    50
    Actual Kilograms
    LB
    Pound
    TD5
    1200

    Carrier Details (Routing Sequence/Transit Time)

    RequiredMax use 12

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

    Example
    If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
    If Transit Time Direction Qualifier (TD5-10) is present, then Transit Time (TD5-11) is required
    TD5-01
    133
    Routing Sequence Code
    Optional
    Min 1Max 2

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

    TD5-02
    66
    Identification Code Qualifier
    Optional

    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)

    If information is available, the TD502 element is
    required.

    TD5-03
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Carriers SCAC. If information is available, the TD503 element is required

    TD5-04
    91
    Transportation Method/Type Code
    Required

    Code specifying the method or type of transportation for the shipment

    A
    Air
    AP
    Air (Package Carrier)
    D
    Parcel Post
    H
    Customer Pickup
    J
    Motor
    K
    Backhaul
    LT
    Less Than Trailer Load (LTL)
    M
    Motor (Common Carrier)
    MP
    Motor (Package Carrier)
    O
    Containerized Ocean
    R
    Rail
    T
    Best Way (Shippers Option)
    U
    Private Parcel Service
    TD5-05
    387
    Routing
    Required
    Min 1Max 35

    Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

    Usage notes

    The carrier name is required for all shipments

    TD5-06
    368
    Shipment/Order Status Code
    Optional
    Min 2Max 2

    Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction

    TD5-10
    732
    Transit Time Direction Qualifier
    Optional

    Code specifying the value of time used to measure the transit time

    CD
    Calendar Days (Includes weekends and Holidays)
    TD5-11
    733
    Transit Time
    Optional
    Min 1Max 4

    The numeric amount of transit time

    TD3 Loop
    OptionalMax 12
    Usage notes

    If Equipment Information is available the TD3 segment is required.

    TD3
    1300

    Carrier Details (Equipment)

    RequiredMax use 1

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

    Example
    TD3-01
    40
    Equipment Description Code
    Required
    Min 2Max 2

    Code identifying type of equipment used for shipment

    TD3-03
    207
    Equipment Number
    Required
    Min 1Max 15

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

    REF
    1500

    Reference Information

    RequiredMax use >1

    To specify identifying information

    Usage notes

    The REFBM and REFCN are both required.

    Examples:
    For Parcel Shipments:
    REFBM = Tracking Number
    REF
    CN = Tracking Number

    For TL/LTL Shipments:
    REFBM = Bill of Lading Number
    REF
    CN = PRO Number (if exists)
    If PRO Number does not exist then REF*CN = Bill of Lading Number

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number

    This code is used for the Bill of Lading Number and must be sent for all Warehouse/Store orders.
    Use the Tracking Number with this qualifier when shipping via Small Parcel Service

    CN
    Carrier's Reference Number (PRO/Invoice)
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 50

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    Usage notes

    This element must be only "A-Z", "a-z", "0-9" and "-".
    If REF01 = BM, REF02 = Bill of Lading Number
    If REF01 = CN, REF02 = Carrier's Reference Number

    DTM
    2000

    Date/Time Reference

    RequiredMax use 10

    To specify pertinent dates and times

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    011
    Shipped
    067
    Current Schedule Delivery
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    FOB
    2100

    F.O.B. Related Instructions

    RequiredMax use 1

    To specify transportation instructions relating to shipment

    Example
    FOB-01
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    BP
    Paid by Buyer
    CC
    Collect
    DE
    Per Contract
    PB
    Customer Pickup/Backhaul
    PC
    Prepaid but Charged to Customer
    PP
    Prepaid (by Seller)
    PS
    Paid by Seller
    FOB-02
    309
    Location Qualifier
    Optional
    Min 1Max 2

    Code identifying type of location

    • FOB02 is the code specifying transportation responsibility location.
    N1 Loop
    RequiredMax 200
    Variants (all may be used)
    N1N1 Loop
    N1
    2200

    Party Identification

    RequiredMax use 1

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

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    SF
    Ship From
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    1
    D-U-N-S Number, Dun & Bradstreet
    9
    D-U-N-S+4, D-U-N-S Number with Four Character Suffix
    92
    Assigned by Buyer or Buyer's Agent
    UL
    Global Location Number (GLN)
    N1-04
    67
    Identification Code
    Required
    Min 2Max 80

    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.
    N1 Loop
    RequiredMax 200
    Variants (all may be used)
    N1N1 Loop
    N1
    2200

    Party Identification

    RequiredMax use 1

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

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    1
    D-U-N-S Number, Dun & Bradstreet
    9
    D-U-N-S+4, D-U-N-S Number with Four Character Suffix
    92
    Assigned by Buyer or Buyer's Agent
    UL
    Global Location Number (GLN)
    N1-04
    67
    Identification Code
    Required
    Min 2Max 80

    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.
    HL Loop
    RequiredMax 1
    HL
    0100

    Hierarchical Level

    RequiredMax use 1

    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.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    Min 1Max 12

    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.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    Min 1Max 12

    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.
    HL-03
    735
    Hierarchical Level Code
    Required

    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
    HL-04
    736
    Hierarchical Child Code
    Optional

    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.
    1
    Additional Subordinate HL Data Segment in This Hierarchical Structure.
    PRF
    0500

    Purchase Order Reference

    RequiredMax use 1

    To provide reference to a specific purchase order

    Example
    PRF-01
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    10 digits AAFES Purchase Order Number

    PRF-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    • PRF04 is the date assigned by the purchaser to purchase order.
    N1 Loop
    RequiredMax 200
    N1
    2200

    Party Identification

    RequiredMax use 1

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

    Usage notes

    This segment must contain either the "Buying Party" or "Mark For" information.
    If N101 = BY, N104 = 4, 7, or 13 digits AAFES facility number.
    If N101 = Z7, N104 = 4, 7, or 13 digits AAFES facility number.

    Example
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    BY
    Buying Party (Purchaser)
    Z7
    Mark-for Party
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    9
    D-U-N-S+4, D-U-N-S Number with Four Character Suffix

    This qualifier is valid with both "Buying Party" and "Mark-for Party".

    92
    Assigned by Buyer or Buyer's Agent

    This qualifier is used when N104 = the AAFES 4-digit EDI facility code or 7-digit AAFES facility number.
    This qualifier is valid with both "Buying Party" and "Mark-for Party".

    UL
    Global Location Number (GLN)

    This qualifier is sent to identify the AAFES 13-digit facility number.
    This qualifier is valid with both "Buying Party" and "Mark-for Party".

    N1-04
    67
    Identification Code
    Required
    Min 2Max 80

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

    Bill To facility number (1018542, 0901, 0016955680901) is not accepted.

    HL Loop
    OptionalMax >1
    Usage notes

    Will accept either Tare or Pack Hierarchical Level or both.
    If the Pack Hierarchical Levels is not used, Tare Hierarchical Level is required

    Variants (all may be used)
    HLHL Loop
    HL
    0100

    Hierarchical Level

    RequiredMax use 1

    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.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    Min 1Max 12

    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.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    Min 1Max 12

    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.
    HL-03
    735
    Hierarchical Level Code
    Required

    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
    HL-04
    736
    Hierarchical Child Code
    Optional

    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.
    MAN
    1900

    Marks and Numbers Information

    OptionalMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    This segment is utilized in the Hierarchical Levels - Tare and Pack. It may be used in Tare, Pack or both levels.

    Example
    MAN-01
    88
    Marks and Numbers Qualifier
    Required

    Code specifying the application or source of Marks and Numbers (87)

    • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
    • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
    Usage notes

    If the Tare Hierarchical Levels is used, this element can be either the qualifier GM or UC at the Pack Hierarchical Level.
    If the Tare Hierarchical Levels is not used, this element can be only the
    qualifier GM at the Pack Hierarchical Level

    GM
    EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

    AAFES requires a twenty character GS1-128 Serial Shipping Container Code (SSCC) that includes the two digit application identifier (AI) and the Modulo 103 GS1-128 Symbol Check Character.

    UC
    U.P.C. Shipping Container Code
    MAN-02
    87
    Marks and Numbers
    Required
    Min 1Max 48

    Marks and numbers used to identify a shipment or parts of a shipment

    • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
    HL Loop
    RequiredMax 1
    Usage notes

    Will accept either Tare or Pack Hierarchical Level or both.
    If the Pack Hierarchical Levels is not used, Tare Hierarchical Level is required

    HL
    0100

    Hierarchical Level

    RequiredMax use 1

    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.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    Min 1Max 12

    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.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    Min 1Max 12

    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.
    HL-03
    735
    Hierarchical Level Code
    Required

    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
    HL-04
    736
    Hierarchical Child Code
    Optional

    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.
    LIN
    0200

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Example
    If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
    LIN-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    LIN-02
    235
    Product/Service ID Qualifier
    Required

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

    The Product/Service ID Qualifier in element LIN02 must match the Product/Service ID Qualifier transmitted on our purchase order

    EN
    EAN/UCC - 13
    EO
    EAN/UCC - 8
    IB
    International Standard Book Number (ISBN)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    The Product/Service ID in element LIN03 must match the Product/Service ID transmitted on our purchase order.

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    LT
    Lot Number
    VA
    Vendor's Style Number
    VC
    Vendor's (Seller's) Catalog Number
    LIN-05
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    SN1
    0300

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Example
    SN1-02
    382
    Number of Units Shipped
    Required
    Min 1Max 10

    Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

    Usage notes

    Zero quantity is not accepted.

    SN1-03
    355
    Unit or Basis for Measurement Code
    Required
    Min 2Max 2

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

    The Unit of Measurement in element SN103 must match the Unit of Measurement transmitted on our purchase order.

    PO4
    0600

    Item Physical Details

    OptionalMax use 1

    To specify the physical qualities, packaging, weights, and dimensions relating to the item

    Usage notes

    If element SN103 = CA or BX or CT or PL, the PO401 element is required at the Item Hierarchical Level.

    Example
    If either Size (PO4-02) or Unit or Basis for Measurement Code (PO4-03) is present, then the other is required
    If either Gross Volume per Pack (PO4-08) or Unit or Basis for Measurement Code (PO4-09) is present, then the other is required
    PO4-01
    356
    Pack
    Required
    Min 1Max 6

    The number of inner containers, or number of eaches if there are no inner containers, per outer container

    PO4-02
    357
    Size
    Optional
    Min 1Max 8

    Size of supplier units in pack

    PO4-03
    355
    Unit or Basis for Measurement Code
    Optional
    Min 2Max 2

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    • PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the unit of measure of the "Size" identified in the PO402.
      For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
    PO4-08
    385
    Gross Volume per Pack
    Optional
    Min 1Max 9

    Numeric value of gross volume per pack

    PO4-09
    355
    Unit or Basis for Measurement Code
    Optional
    Min 2Max 2

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    PID
    0700

    Product/Item Description

    OptionalMax use 200

    To describe a product or process in coded or free-form format

    Example
    PID-01
    349
    Item Description Type
    Required

    Code indicating the format of a description

    • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
    F
    Free-form
    PID-05
    352
    Description
    Required
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    HL Loop
    OptionalMax >1
    Usage notes

    Will accept either Tare or Pack Hierarchical Level or both.
    If the Pack Hierarchical Levels is not used, Tare Hierarchical Level is required

    Variants (all may be used)
    HLHL Loop
    HL
    0100

    Hierarchical Level

    RequiredMax use 1

    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.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    Min 1Max 12

    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.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    Min 1Max 12

    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.
    HL-03
    735
    Hierarchical Level Code
    Required

    Code defining the characteristic of a level in a hierarchical structure

    • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
    T
    Shipping Tare
    HL-04
    736
    Hierarchical Child Code
    Optional

    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.
    MAN
    1900

    Marks and Numbers Information

    RequiredMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    This segment is utilized in the Tare and Pack Hierarchical Levels. May be used in either Tare, Pack or both levels.

    Example
    MAN-01
    88
    Marks and Numbers Qualifier
    Required

    Code specifying the application or source of Marks and Numbers (87)

    • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
    • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
    Usage notes

    If the Tare Hierarchical Levels is used, this element must contain the qualifier GM.

    GM
    EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

    AAFES requires a twenty character GS1-128 Serial Shipping Container Code (SSCC) that includes the two digit application identifier (AI) and the Modulo 103 GS1-128 Symbol Check Character.

    MAN-02
    87
    Marks and Numbers
    Required
    Min 1Max 48

    Marks and numbers used to identify a shipment or parts of a shipment

    • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
    HL Loop
    RequiredMax 1
    Usage notes

    Will accept either Tare or Pack Hierarchical Level or both.
    If the Pack Hierarchical Levels is not used, Tare Hierarchical Level is required

    HL
    0100

    Hierarchical Level

    RequiredMax use 1

    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.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    Min 1Max 12

    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.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    Min 1Max 12

    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.
    HL-03
    735
    Hierarchical Level Code
    Required

    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
    HL-04
    736
    Hierarchical Child Code
    Optional

    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.
    LIN
    0200

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Example
    If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
    LIN-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    LIN-02
    235
    Product/Service ID Qualifier
    Required

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

    The Product/Service ID Qualifier in element LIN02 must match the Product/Service ID Qualifier transmitted on our purchase order

    EN
    EAN/UCC - 13
    EO
    EAN/UCC - 8
    IB
    International Standard Book Number (ISBN)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    The Product/Service ID in element LIN03 must match the Product/Service ID transmitted on our purchase order.

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    LT
    Lot Number
    VA
    Vendor's Style Number
    VC
    Vendor's (Seller's) Catalog Number
    LIN-05
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    SN1
    0300

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Example
    SN1-02
    382
    Number of Units Shipped
    Required
    Min 1Max 10

    Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

    Usage notes

    Zero quantity is not accepted.

    SN1-03
    355
    Unit or Basis for Measurement Code
    Required
    Min 2Max 2

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

    The Unit of Measurement in element SN103 must match the Unit of Measurement transmitted on our purchase order.

    PO4
    0600

    Item Physical Details

    OptionalMax use 1

    To specify the physical qualities, packaging, weights, and dimensions relating to the item

    Usage notes

    If element SN103 = CA or BX or CT or PL, the PO401 element is required at the Item Hierarchical Level.

    Example
    If either Size (PO4-02) or Unit or Basis for Measurement Code (PO4-03) is present, then the other is required
    If either Gross Volume per Pack (PO4-08) or Unit or Basis for Measurement Code (PO4-09) is present, then the other is required
    PO4-01
    356
    Pack
    Required
    Min 1Max 6

    The number of inner containers, or number of eaches if there are no inner containers, per outer container

    PO4-02
    357
    Size
    Optional
    Min 1Max 8

    Size of supplier units in pack

    PO4-03
    355
    Unit or Basis for Measurement Code
    Optional
    Min 2Max 2

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    • PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the unit of measure of the "Size" identified in the PO402.
      For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
    PO4-08
    385
    Gross Volume per Pack
    Optional
    Min 1Max 9

    Numeric value of gross volume per pack

    PO4-09
    355
    Unit or Basis for Measurement Code
    Optional
    Min 2Max 2

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    PID
    0700

    Product/Item Description

    OptionalMax use 200

    To describe a product or process in coded or free-form format

    Example
    PID-01
    349
    Item Description Type
    Required

    Code indicating the format of a description

    • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
    F
    Free-form
    PID-05
    352
    Description
    Required
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    Summary

    CTT
    0100

    Transaction Totals

    RequiredMax use 1

    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.
    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    SE
    0200

    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 Included Segments
    Required
    Min 1Max 10

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

    SE-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    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
    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
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Interchange Control Trailer

    RequiredMax use 1

    To define the end of an interchange of zero or more functional groups and interchange-related control segments

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample from AAFES 1

    ST*856*0456~
    BSN*00*SSH271019*20150422*185100*0001~
    HL*1**S~
    TD1*CTN*3****G*6.9*LB~
    TD5****M*FEDEXGROUND~
    REF*CN*SPR0271017~
    REF*BM*912273936811941~
    DTM*011*20150422~
    FOB*CC~
    N1*ST*1059967*92*1059967~
    N1*SF*VENDOR NAME*1*VENDOR DUNS#~
    HL*2*1*O~
    PRF*0070340956***20150415~
    N1*Z7**92*1771001~
    HL*3*2*P~
    MAN*GM*00000379770085821186~
    HL*4*3*I~
    LIN**UP*037977100266~
    SN1**18*EA~
    HL*5*2*P~
    MAN*GM*00000379770085821193~
    HL*6*5*I~
    LIN**UP*037977100266~
    SN1**18*EA~
    CTT*6~
    SE*26*0456~

    Sample from AAFES 2

    ST*856*0780~
    BSN*00*36051*20150428*1605*0001~
    HL*1**S~
    TD1*CTN*2****G*10*LB~
    TD5*O**RDWY*M*446-729532-X*PR~
    REF*BM*446-729532-X~
    DTM*011*20150427~
    FOB*PP~
    N1*SF*VENDOR NAME*1*VENDOR DUNS#~
    N1*ST**92*1059902~
    HL*2*1*O~
    PRF*0069423665***20150123~
    N1*BY**92*1059902~
    HL*3*2*P~
    MAN*GM*00000639540000047859~
    HL*4*3*I~
    LIN**UP*043589347630*VA*23842DL~
    SN1**24*EA~
    PID*F****AF CAP WM FLT OFF 25~
    HL*5*2*P~
    MAN*GM*00000639540000047866~
    HL*6*5*I~
    LIN**UP*043589347555*VA*23842DL~
    SN1**24*EA~
    PID*F****AF CAP WM FLT OFF 21~
    CTT*6~
    SE*27*0780~

    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.