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

X12 856 Ship Notice/Manifest

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 sample
    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
    Bill of Lading Number
    Max use 1
    Required
    REF
    1500
    Carrier's Reference Number (PRO/Invoice)
    Max use 1
    Optional
    DTM
    2000
    Current Schedule Delivery
    Max use 10
    Optional
    DTM
    2000
    Shipped
    Max use 10
    Required
    HL Loop
    HL
    0100
    Hierarchical Level
    Max use 1
    Required
    PRF
    0500
    Purchase Order Reference
    Max use 1
    Required
    TD5
    1200
    Carrier Details (Routing Sequence/Transit Time)
    Max use 12
    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

    BSN00123456789200610191957~
    BSN00123456789200610191957*0004~

    Date formats - All dates within the ASN use the format as specified in the Data Element Table 373 (CCYYMMDD). This format does not permit the use of nonnumeric characters ("/" or "-"). Time formats. The time is based on a 24 hour clock where HH = (00-23) and MM = (00-59)

    Example
    BSN-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    BSN-02
    396
    Shipment Identification
    Required
    Min 2Max 30

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

    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
    Optional

    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
    0002
    Shipment, Order, Item, Packaging
    0004
    Shipment, Order, Item

    Detail

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

    Usage notes

    TD1PLT57*G120*LB40CF~
    Carrier Details (Quantity and Weight)

    The TD1segment is mandatory. All required fields must be present including the TD101 packing code.

    The TD108 'Weight' 'Weight Unit of Measure' must have a value of either LB or KG.

    The TD110 'Volume' 'Volume Unit of Measure' must have a value of CF

    Example
    If either Volume (TD1-09) or Unit or Basis for Measurement Code (TD1-10) is present, then the other is required
    TD1-01
    103
    Packaging Code
    Required
    Min 3Max 5

    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

    TD1-02
    80
    Lading Quantity
    Required
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    TD1-06
    187
    Weight Qualifier
    Required

    Code defining the type of weight

    G
    Gross 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

    KG
    Kilogram
    LB
    Pound
    TD1-09
    183
    Volume
    Optional
    Min 1Max 8

    Value of volumetric measure

    TD1-10
    355
    Unit or Basis for Measurement Code
    Optional

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

    CF
    Cubic Feet
    TD5
    1200

    Carrier Details (Routing Sequence/Transit Time)

    RequiredMax use 12

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

    Usage notes

    TD5*2FDEGMFedex Ground*CC~

    Status is required at all three levels, Shipment, Order and Item level TD506 in Shipment level, TD506 in Order level and SN108 in Item level.

    Carrier Details -TD5 03 Carriers ID 'SCAC' code is required. Be sure that you are providing the four alpha-characters of the carrier. The customer pick up 'SCAC' code is RTAD.

    TD504 'Transportation Method Code' is also a required field. Be sure that you are providing the correct 'Transportation Method Code'.

    Example
    TD5-02
    66
    Identification Code Qualifier
    Required

    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)
    TD5-03
    67
    Identification Code
    Required
    Min 2Max 80

    Code identifying a party or other code

    TD5-04
    91
    Transportation Method/Type Code
    Required
    Min 1Max 2

    Code specifying the method or type of transportation for the shipment

    Usage notes

    Any valid ANSI code

    TD5-05
    387
    Routing
    Optional
    Min 1Max 35

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

    TD5-06
    368
    Shipment/Order Status Code
    Required

    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

    CC
    Shipment Complete on (Date)
    CP
    Partial Shipment on (Date), Considered No Backorder
    PD
    Purchase Order Complete
    PR
    Partial Shipment
    SH
    Shipped (Date)
    SJ
    Shipped or Performed as Indicated

    A shipment or performance made according to the terms and conditions of a contract

    TD3 Loop
    OptionalMax >1
    TD3
    1300

    Carrier Details (Equipment)

    RequiredMax use 1

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

    Usage notes

    TD3ACZZ*12345~

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

    Code identifying type of equipment used for shipment

    TD3-02
    206
    Equipment Initial
    Required
    Min 1Max 4

    Prefix or alphabetic part of an equipment unit's identifying number

    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

    Bill of Lading Number

    RequiredMax use >1

    To specify identifying information

    Usage notes

    REFBMX1234567890~

    Example
    Variants (all may be used)
    REFCarrier's Reference Number (PRO/Invoice)
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    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

    REF
    1500

    Carrier's Reference Number (PRO/Invoice)

    OptionalMax use >1

    To specify identifying information

    Usage notes

    REFCNY0987654321~

    CARRIER’S PRO# (REF*CN)

    This value is key in matching the vendor’s ASN data to the carrier’s shipment status data. This value MUST be the carrier’s PRO# as it is sent in the 214 shipment status. If you are currently not capable of providing the PRO #, do not send this segment.

    Example
    Variants (all may be used)
    REFBill of Lading Number
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    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

    DTM
    2000

    Current Schedule Delivery

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    DTM06720061020*1530~

    Date formats
    All dates within the ASN use the format as specified in the Data Element Table 373 (CCYYMMDD). This format does not permit the use of non-numeric characters ("/" or "-").

    Time formats
    The time is based on a 24 hour clock where HH = (00-23) and MM = (00-59).

    Example
    Variants (all may be used)
    DTMShipped
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    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

    DTM-03
    337
    Time
    Optional
    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)

    DTM
    2000

    Shipped

    RequiredMax use 10

    To specify pertinent dates and times

    Usage notes

    DTM01120061020*1530~

    SHIP DATE and TIME (DTM*011)

    The shipment date and time are both mandatory fields. This information is used as a basis for determining if the ASN was received within 24 hours of the ship date and time.

    ASNs are expected and processed 7 days a week.

    Date formats
    All dates within the ASN use the format as specified in the Data Element Table 373 (CCYYMMDD). This format does not permit the use of non-numeric characters ("/"or "-").

    Time formats
    The time is based on a 24 hour clock where HH = (00-23) and MM = (00-59).

    Example
    Variants (all may be used)
    DTMCurrent Schedule Delivery
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    011
    Shipped
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

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

    Usage notes

    Ship Date

    DTM-03
    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)

    N1 Ship From
    RequiredMax >1
    Variants (all may be used)
    N1Ship To
    N1
    2200

    Party Identification

    RequiredMax use 1

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

    Usage notes

    N1SFVENDOR WAREHOUSE~

    Example
    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
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    Location name of shipment origin

    N4
    2500

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Usage notes

    N4HARRISBURGPA*12345~

    Example
    N4-01
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    Usage notes

    Location city name of shipment origin

    N4-02
    156
    State or Province Code
    Required
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    Usage notes

    Location state name of shipment origin

    N4-03
    116
    Postal Code
    Required
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    Usage notes

    Location zipcode of shipment origin

    N1 Ship To
    RequiredMax >1
    Variants (all may be used)
    N1Ship From
    N1
    2200

    Party Identification

    RequiredMax use 1

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

    Example
    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
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    Rite Aid DC 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
    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
    N3
    2400

    Party Location

    RequiredMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    Usage notes

    Rite Aid DC Address

    N4
    2500

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    Usage notes

    Rite Aid DC City

    N4-02
    156
    State or Province Code
    Required
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    Usage notes

    Rite Aid DC State

    N4-03
    116
    Postal Code
    Required
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    Usage notes

    Rite Aid DC Zip Code

    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

    Usage notes

    PRF*1234567~

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

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    Rite Aid's PO Number

    TD5
    1200

    Carrier Details (Routing Sequence/Transit Time)

    RequiredMax use 12

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

    Usage notes

    TD5******PD~

    Status is required at all three levels, Shipment, Order and Item level TD506 in Shipment level, TD506 in Order level and SN108 in Item level

    Example
    TD5-06
    368
    Shipment/Order Status Code
    Required

    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

    CC
    Shipment Complete on (Date)
    CP
    Partial Shipment on (Date), Considered No Backorder
    PD
    Purchase Order Complete
    PR
    Partial Shipment
    SH
    Shipped (Date)
    SJ
    Shipped or Performed as Indicated

    A shipment or performance made according to the terms and conditions of a contract

    HL Loop
    OptionalMax >1
    Variants (all may be used)
    HLHL LoopHLHL 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.
    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

    Usage notes

    LININ*1234567~
    LIN
    UI12345678901IN1234567~
    LIN**UP
    123456789012IN1234567~
    LINUA123456789012IN*1234567~
    LIN
    UA123456789012IN1234567UI12345678901UP123456789012~
    LIN**UK
    12345678901234IN1234567~
    LINVN01020304IN1234567UI*12345678901~
    LIN
    EN1234567890123IN*1234567~

    1.LIN02 and LIN03 must not be null.
    2.At least 1 of the above qualifier/ID combinations is mandatory.
    3.The qualifier/ID combination may appear in any order.
    4.RITE AID requires the same item number and qualifier to be returned on the ASN that was sent in the original purchase order.
    5.ID length specified corresponds to its preceding qualifier.

    RITE AID ITEM NUMBER USAGE
    1.Rite Aid’s item number, if available, should be returned.
    2.Rite Aid's item number is always sent in the Purchase Order.
    3.The "IN" qualifier MUST be used ONLY in conjunction with Rite Aid’s item number.
    4.Please follow X12 guidelines for correct qualifier use with UPC codes or vendor item numbers

    Example
    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.
    IN
    Buyer's Item Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Required

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

    EN
    EAN/UCC - 13
    ND
    National Drug Code (NDC)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UI
    U.P.C. Consumer Package Code (1-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    VN
    Vendor's (Seller's) Item Number
    LIN-05
    234
    Product/Service ID
    Required
    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

    Usage notes

    SN113CA1313CAAC~

    Status is required at all three levels, Shipment, Order and Item level TD506 in Shipment level, TD506 in Order level and SN108 in Item level.

    UNIT OF MEASURE (SN1 03) - The shipping unit of measure (CA or EA) in this element should match the order unit of measure sent in the Rite Aid purchase order.

    Example
    If either Quantity (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
    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

    SN1-03
    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

    • SN103 defines the unit of measurement for both SN102 and SN104.
    CA
    Case
    EA
    Each
    SN1-04
    646
    Quantity Shipped to Date
    Optional
    Min 1Max 15

    Number of units shipped to date

    SN1-05
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    • SN105 is quantity ordered.
    SN1-06
    355
    Unit or Basis for Measurement Code
    Optional

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

    CA
    Case
    EA
    Each
    SN1-08
    668
    Line Item Status Code
    Required

    Code specifying the action taken by the seller on a line item requested by the buyer

    AC
    Item Accepted and Shipped

    If Item quantity > 0

    BP
    Item Accepted - Partial Shipment, Balance Backordered

    If Item quantity > 0

    IB
    Item Backordered

    If Item quantity = 0

    IC
    Item Accepted - Changes Made

    If Item quantity = 0

    ID
    Item Deleted

    If Item quantity = 0

    IE
    Item Accepted, Price Pending

    If Item quantity = 0

    IH
    Item on Hold

    If Item quantity = 0

    IP
    Item Accepted - Price Changed

    If Item quantity = 0

    IQ
    Item Accepted - Quantity Changed

    If Item quantity = 0

    IR
    Item Rejected

    If Item quantity = 0

    IS
    Item Accepted - Substitution Made

    If Item quantity = 0

    IW
    Item on Hold-Waiver Required

    If Item quantity = 0

    R2
    Item Rejected, Invalid Item Product Number

    If Item quantity = 0

    R3
    Item Rejected, Invalid Unit of Issue

    If Item quantity = 0

    PO4
    0600

    Item Physical Details

    RequiredMax use 1

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

    Usage notes

    PO42412OZ***********6~
    PO4
    60020PC***********10~

    First Example: one case of cola (12 oz cans; 4 6-packs):
    Second Example: one case of cigarettes (20 pc packs; 60 cartons of 10 packs):

    Example
    If either Size (PO4-02) or Unit or Basis for Measurement Code (PO4-03) 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-14
    810
    Inner Pack
    Optional
    Min 1Max 6

    The number of eaches per inner container

    PID
    0700

    Product/Item Description

    RequiredMax use 200

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

    Usage notes

    PIDF***ITEM DESCRIPTION~

    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

    REF
    1500

    Reference Information

    OptionalMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    LT
    Lot Number
    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

    DTM
    2000

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    DTM03620061214~

    The Expiration Date is mandatory if applicable to product.
    Date formats - All dates within the ASN use the format as specified in the Data Element Table 373 (CCYYMMDD). This format does not permit the use of non-numeric characters ("/" or "-").

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    036
    Expiration
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

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

    HL Loop
    OptionalMax >1
    Variants (all may be used)
    HLHL LoopHLHL 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

    RequiredMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    MANGM0123456789~

    The Man segment is only mandatory if Pack Hierarchical Level HL is present

    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.
    GM
    EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
    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
    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

    Usage notes

    LININ*1234567~
    LIN
    UI12345678901IN1234567~
    LIN**UP
    123456789012IN1234567~
    LINUA123456789012IN*1234567~
    LIN
    UA123456789012IN1234567UI12345678901UP123456789012~
    LIN**UK
    12345678901234IN1234567~
    LINVN01020304IN1234567UI*12345678901~
    LIN
    EN1234567890123IN*1234567~

    1.LIN02 and LIN03 must not be null.
    2.At least 1 of the above qualifier/ID combinations is mandatory.
    3.The qualifier/ID combination may appear in any order.
    4.RITE AID requires the same item number and qualifier to be returned on the ASN that was sent in the original purchase order.
    5.ID length specified corresponds to its preceding qualifier.

    RITE AID ITEM NUMBER USAGE
    1.Rite Aid’s item number, if available, should be returned.
    2.Rite Aid's item number is always sent in the Purchase Order.
    3.The "IN" qualifier MUST be used ONLY in conjunction with Rite Aid’s item number.
    4.Please follow X12 guidelines for correct qualifier use with UPC codes or vendor item numbers

    Example
    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.
    IN
    Buyer's Item Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Required

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

    EN
    EAN/UCC - 13
    ND
    National Drug Code (NDC)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UI
    U.P.C. Consumer Package Code (1-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    VN
    Vendor's (Seller's) Item Number
    LIN-05
    234
    Product/Service ID
    Required
    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

    Usage notes

    SN113CA1313CAAC~

    Status is required at all three levels, Shipment, Order and Item level TD506 in Shipment level, TD506 in Order level and SN108 in Item level.

    UNIT OF MEASURE (SN1 03) - The shipping unit of measure (CA or EA) in this element should match the order unit of measure sent in the Rite Aid purchase order.

    Example
    If either Quantity (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
    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

    SN1-03
    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

    • SN103 defines the unit of measurement for both SN102 and SN104.
    CA
    Case
    EA
    Each
    SN1-04
    646
    Quantity Shipped to Date
    Optional
    Min 1Max 15

    Number of units shipped to date

    SN1-05
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    • SN105 is quantity ordered.
    SN1-06
    355
    Unit or Basis for Measurement Code
    Optional

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

    CA
    Case
    EA
    Each
    SN1-08
    668
    Line Item Status Code
    Required

    Code specifying the action taken by the seller on a line item requested by the buyer

    AC
    Item Accepted and Shipped

    If Item quantity > 0

    BP
    Item Accepted - Partial Shipment, Balance Backordered

    If Item quantity > 0

    IB
    Item Backordered

    If Item quantity = 0

    IC
    Item Accepted - Changes Made

    If Item quantity = 0

    ID
    Item Deleted

    If Item quantity = 0

    IE
    Item Accepted, Price Pending

    If Item quantity = 0

    IH
    Item on Hold

    If Item quantity = 0

    IP
    Item Accepted - Price Changed

    If Item quantity = 0

    IQ
    Item Accepted - Quantity Changed

    If Item quantity = 0

    IR
    Item Rejected

    If Item quantity = 0

    IS
    Item Accepted - Substitution Made

    If Item quantity = 0

    IW
    Item on Hold-Waiver Required

    If Item quantity = 0

    R2
    Item Rejected, Invalid Item Product Number

    If Item quantity = 0

    R3
    Item Rejected, Invalid Unit of Issue

    If Item quantity = 0

    PO4
    0600

    Item Physical Details

    RequiredMax use 1

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

    Usage notes

    PO42412OZ***********6~
    PO4
    60020PC***********10~

    First Example: one case of cola (12 oz cans; 4 6-packs):
    Second Example: one case of cigarettes (20 pc packs; 60 cartons of 10 packs):

    Example
    If either Size (PO4-02) or Unit or Basis for Measurement Code (PO4-03) 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-14
    810
    Inner Pack
    Optional
    Min 1Max 6

    The number of eaches per inner container

    PID
    0700

    Product/Item Description

    RequiredMax use 200

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

    Usage notes

    PIDF***ITEM DESCRIPTION~

    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

    REF
    1500

    Reference Information

    OptionalMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    LT
    Lot Number
    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

    DTM
    2000

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    DTM03620061214~

    The Expiration Date is mandatory if applicable to product.
    Date formats - All dates within the ASN use the format as specified in the Data Element Table 373 (CCYYMMDD). This format does not permit the use of non-numeric characters ("/" or "-").

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    036
    Expiration
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

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

    HL Loop
    OptionalMax >1
    Variants (all may be used)
    HLHL LoopHLHL 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.
    0
    No Subordinate HL Segment in This Hierarchical Structure.
    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

    MANGM0123456789~

    The Man segment is only mandatory if Tare Hierarchical Level HL is present

    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.
    GM
    EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
    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
    OptionalMax >1
    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.
    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

    Usage notes

    LININ*1234567~
    LIN
    UI12345678901IN1234567~
    LIN**UP
    123456789012IN1234567~
    LINUA123456789012IN*1234567~
    LIN
    UA123456789012IN1234567UI12345678901UP123456789012~
    LIN**UK
    12345678901234IN1234567~
    LINVN01020304IN1234567UI*12345678901~
    LIN
    EN1234567890123IN*1234567~

    1.LIN02 and LIN03 must not be null.
    2.At least 1 of the above qualifier/ID combinations is mandatory.
    3.The qualifier/ID combination may appear in any order.
    4.RITE AID requires the same item number and qualifier to be returned on the ASN that was sent in the original purchase order.
    5.ID length specified corresponds to its preceding qualifier.

    RITE AID ITEM NUMBER USAGE
    1.Rite Aid’s item number, if available, should be returned.
    2.Rite Aid's item number is always sent in the Purchase Order.
    3.The "IN" qualifier MUST be used ONLY in conjunction with Rite Aid’s item number.
    4.Please follow X12 guidelines for correct qualifier use with UPC codes or vendor item numbersLININ*1234567~
    LIN
    UI12345678901IN1234567~
    LIN**UP
    123456789012IN1234567~
    LINUA123456789012IN*1234567~
    LIN
    UA123456789012IN1234567UI12345678901UP123456789012~
    LIN**UK
    12345678901234IN1234567~
    LINVN01020304IN1234567UI*12345678901~
    LIN
    EN1234567890123IN*1234567~

    1.LIN02 and LIN03 must not be null.
    2.At least 1 of the above qualifier/ID combinations is mandatory.
    3.The qualifier/ID combination may appear in any order.
    4.RITE AID requires the same item number and qualifier to be returned on the ASN that was sent in the original purchase order.
    5.ID length specified corresponds to its preceding qualifier.

    RITE AID ITEM NUMBER USAGE
    1.Rite Aid’s item number, if available, should be returned.
    2.Rite Aid's item number is always sent in the Purchase Order.
    3.The "IN" qualifier MUST be used ONLY in conjunction with Rite Aid’s item number.
    4.Please follow X12 guidelines for correct qualifier use with UPC codes or vendor item numbers

    Example
    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.
    IN
    Buyer's Item Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Required

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

    EN
    EAN/UCC - 13
    ND
    National Drug Code (NDC)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UI
    U.P.C. Consumer Package Code (1-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    VN
    Vendor's (Seller's) Item Number
    LIN-05
    234
    Product/Service ID
    Required
    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

    Usage notes

    SN113CA1313CAAC~

    Status is required at all three levels, Shipment, Order and Item level TD506 in Shipment level, TD506 in Order level and SN108 in Item level.

    UNIT OF MEASURE (SN1 03) - The shipping unit of measure (CA or EA) in this element should match the order unit of measure sent in the Rite Aid purchase order.

    Example
    If either Quantity (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
    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

    SN1-03
    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

    • SN103 defines the unit of measurement for both SN102 and SN104.
    CA
    Case
    EA
    Each
    SN1-04
    646
    Quantity Shipped to Date
    Optional
    Min 1Max 15

    Number of units shipped to date

    SN1-05
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    • SN105 is quantity ordered.
    SN1-06
    355
    Unit or Basis for Measurement Code
    Optional

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

    CA
    Case
    EA
    Each
    SN1-08
    668
    Line Item Status Code
    Required

    Code specifying the action taken by the seller on a line item requested by the buyer

    AC
    Item Accepted and Shipped

    If Item quantity > 0

    BP
    Item Accepted - Partial Shipment, Balance Backordered

    If Item quantity > 0

    IB
    Item Backordered

    If Item quantity = 0

    IC
    Item Accepted - Changes Made

    If Item quantity = 0

    ID
    Item Deleted

    If Item quantity = 0

    IE
    Item Accepted, Price Pending

    If Item quantity = 0

    IH
    Item on Hold

    If Item quantity = 0

    IP
    Item Accepted - Price Changed

    If Item quantity = 0

    IQ
    Item Accepted - Quantity Changed

    If Item quantity = 0

    IR
    Item Rejected

    If Item quantity = 0

    IS
    Item Accepted - Substitution Made

    If Item quantity = 0

    IW
    Item on Hold-Waiver Required

    If Item quantity = 0

    R2
    Item Rejected, Invalid Item Product Number

    If Item quantity = 0

    R3
    Item Rejected, Invalid Unit of Issue

    If Item quantity = 0

    PO4
    0600

    Item Physical Details

    RequiredMax use 1

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

    Usage notes

    PO42412OZ***********6~
    PO4
    60020PC***********10~

    First Example: one case of cola (12 oz cans; 4 6-packs):
    Second Example: one case of cigarettes (20 pc packs; 60 cartons of 10 packs):

    Example
    If either Size (PO4-02) or Unit or Basis for Measurement Code (PO4-03) 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-14
    810
    Inner Pack
    Optional
    Min 1Max 6

    The number of eaches per inner container

    PID
    0700

    Product/Item Description

    RequiredMax use 200

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

    Usage notes

    PIDF***ITEM DESCRIPTION~

    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

    REF
    1500

    Reference Information

    OptionalMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    LT
    Lot Number
    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

    DTM
    2000

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    DTM03620061214~

    The Expiration Date is mandatory if applicable to product.
    Date formats - All dates within the ASN use the format as specified in the Data Element Table 373 (CCYYMMDD). This format does not permit the use of non-numeric characters ("/" or "-").

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    036
    Expiration
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

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

    HL Loop
    OptionalMax >1
    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

    RequiredMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    MANGM0123456789~

    The Man segment is only mandatory if Pack Hierarchical Level HL is present

    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.
    GM
    EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
    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
    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

    Usage notes

    LININ*1234567~
    LIN
    UI12345678901IN1234567~
    LIN**UP
    123456789012IN1234567~
    LINUA123456789012IN*1234567~
    LIN
    UA123456789012IN1234567UI12345678901UP123456789012~
    LIN**UK
    12345678901234IN1234567~
    LINVN01020304IN1234567UI*12345678901~
    LIN
    EN1234567890123IN*1234567~

    1.LIN02 and LIN03 must not be null.
    2.At least 1 of the above qualifier/ID combinations is mandatory.
    3.The qualifier/ID combination may appear in any order.
    4.RITE AID requires the same item number and qualifier to be returned on the ASN that was sent in the original purchase order.
    5.ID length specified corresponds to its preceding qualifier.

    RITE AID ITEM NUMBER USAGE
    1.Rite Aid’s item number, if available, should be returned.
    2.Rite Aid's item number is always sent in the Purchase Order.
    3.The "IN" qualifier MUST be used ONLY in conjunction with Rite Aid’s item number.
    4.Please follow X12 guidelines for correct qualifier use with UPC codes or vendor item numbers

    Example
    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.
    IN
    Buyer's Item Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Required

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

    EN
    EAN/UCC - 13
    ND
    National Drug Code (NDC)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UI
    U.P.C. Consumer Package Code (1-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    VN
    Vendor's (Seller's) Item Number
    LIN-05
    234
    Product/Service ID
    Required
    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

    Usage notes

    SN113CA1313CAAC~

    Status is required at all three levels, Shipment, Order and Item level TD506 in Shipment level, TD506 in Order level and SN108 in Item level.

    UNIT OF MEASURE (SN1 03) - The shipping unit of measure (CA or EA) in this element should match the order unit of measure sent in the Rite Aid purchase order.

    Example
    If either Quantity (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
    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

    SN1-03
    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

    • SN103 defines the unit of measurement for both SN102 and SN104.
    CA
    Case
    EA
    Each
    SN1-04
    646
    Quantity Shipped to Date
    Optional
    Min 1Max 15

    Number of units shipped to date

    SN1-05
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    • SN105 is quantity ordered.
    SN1-06
    355
    Unit or Basis for Measurement Code
    Optional

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

    CA
    Case
    EA
    Each
    SN1-08
    668
    Line Item Status Code
    Required

    Code specifying the action taken by the seller on a line item requested by the buyer

    AC
    Item Accepted and Shipped

    If Item quantity > 0

    BP
    Item Accepted - Partial Shipment, Balance Backordered

    If Item quantity > 0

    IB
    Item Backordered

    If Item quantity = 0

    IC
    Item Accepted - Changes Made

    If Item quantity = 0

    ID
    Item Deleted

    If Item quantity = 0

    IE
    Item Accepted, Price Pending

    If Item quantity = 0

    IH
    Item on Hold

    If Item quantity = 0

    IP
    Item Accepted - Price Changed

    If Item quantity = 0

    IQ
    Item Accepted - Quantity Changed

    If Item quantity = 0

    IR
    Item Rejected

    If Item quantity = 0

    IS
    Item Accepted - Substitution Made

    If Item quantity = 0

    IW
    Item on Hold-Waiver Required

    If Item quantity = 0

    R2
    Item Rejected, Invalid Item Product Number

    If Item quantity = 0

    R3
    Item Rejected, Invalid Unit of Issue

    If Item quantity = 0

    PO4
    0600

    Item Physical Details

    RequiredMax use 1

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

    Usage notes

    PO42412OZ***********6~
    PO4
    60020PC***********10~

    First Example: one case of cola (12 oz cans; 4 6-packs):
    Second Example: one case of cigarettes (20 pc packs; 60 cartons of 10 packs):

    Example
    If either Size (PO4-02) or Unit or Basis for Measurement Code (PO4-03) 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-14
    810
    Inner Pack
    Optional
    Min 1Max 6

    The number of eaches per inner container

    PID
    0700

    Product/Item Description

    RequiredMax use 200

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

    Usage notes

    PIDF***ITEM DESCRIPTION~

    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

    REF
    1500

    Reference Information

    OptionalMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    LT
    Lot Number
    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

    DTM
    2000

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    DTM03620061214~

    The Expiration Date is mandatory if applicable to product.
    Date formats - All dates within the ASN use the format as specified in the Data Element Table 373 (CCYYMMDD). This format does not permit the use of non-numeric characters ("/" or "-").

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    036
    Expiration
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

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

    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

    ST*856*673230873~
    BSN*00*111202*20131112*1032*0001~
    HL*1**S~
    TD1*PLT94*1464****G*189.250*LB*189.250*CF~
    TD5**2*RDWY*M**CC~
    REF*BM*6409527138~
    DTM*011*20131111*1930~
    N1*SF*VENDOR NAME~
    N4*RIVERSIDE*CA*92507~
    N1*ST*RITE AID WILSONVILLEDIST CENTER*9*0145788920080~
    N3*29555 SW BOONES FERRY ROAD~
    N4*WILSONVILLE*OR*97070~
    HL*2*1*O~
    PRF*6013687~
    TD5******CC~
    HL*3*2*I~
    LIN**IN*0031292*UI*01182233292~
    SN1**7*CA**7*CA**AC~
    PO4*72*************72~
    PID*F****RA GAUZE BND 2INX2.5YD~
    HL*4*2*I~
    LIN**IN*0352800*UI*01182252800~
    SN1**7*CA**7*CA**AC~
    PO4*36*************36~
    PID*F****RA GAUZE ROLLS 4IN 5CT~
    HL*5*2*I~
    LIN**IN*0352801*UI*01182252801~
    SN1**5*CA**5*CA**AC~
    PO4*36*************36~
    PID*F****RA GAUZE ROLLS 3IN 5CT~
    HL*6*2*I~
    LIN**IN*0393445*UI*01182254439~
    SN1**11*CA**11*CA**AC~
    PO4*48*************48~
    PID*F****RA NONSTICK PAD 3X4 10CT~
    CTT*6~
    SE*37*673230873~

    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.