AT&T
/
Purchase Order Acknowledgment
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from AT&T. Contact AT&T for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
AT&T logo

X12 855 Purchase Order Acknowledgment

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.

Delimiters
  • ~ Segment
  • * Element
  • > Component
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
    ST
    010
    Transaction Set Header
    Max use 1
    Required
    BAK
    020
    Beginning Segment for Purchase Order Acknowledgment
    Max use 1
    Required
    REF
    050
    PO Type
    Max use 1
    Required
    REF
    050
    Revision Number
    Max use 1
    Required
    PER
    060
    Administrative Communications Contact
    Max use 3
    Optional
    DTM
    150
    PO Received
    Max use 10
    Required
    DTM
    150
    Revision
    Max use 10
    Optional
    Ship To
    detail
    PO1 Loop
    PO1
    010
    Baseline Item Data
    Max use 1
    Required
    SLN Loop
    SLN
    490
    Subline Item Detail
    Max use 1
    Required
    PID
    510
    Product/Item Description
    Max use 1000
    Required
    PO3
    520
    Additional Item Detail
    Max use 25
    Required
    ACK
    530
    Line Item Acknowledgment
    Max use 104
    Required
    N9 Loop
    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 to identify 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 to identify 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

    Qualifier to designate 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

    Qualifier to designate 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
    I10
    Interchange Control Standards Identifier
    Required

    Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

    U
    U.S. EDI Community of ASC X12, TDCC, and UCS
    ISA-12
    I11
    Interchange Control Version Number
    Required

    This version number covers the interchange control segments

    00401
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
    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 sent by the sender to request an interchange acknowledgment (TA1)

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

    Code to indicate 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

    PR
    Purchase Order Acknowledgement (855)
    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

    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 used in conjunction with Data Element 480 to identify the issuer of the standard

    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

    004010
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

    Heading

    ST
    010

    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) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
    855
    Purchase Order Acknowledgment
    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

    BAK
    020

    Beginning Segment for Purchase Order Acknowledgment

    RequiredMax use 1

    To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates

    Usage notes

    Sample EDI:
    BAK00AT1317126200706110850**0001369955~

    Example
    BAK-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    BAK-02
    587
    Acknowledgment Type
    Required

    Code specifying the type of acknowledgment

    AC
    Acknowledge - With Detail and Change
    AT
    Accepted
    RD
    Reject with Detail
    BAK-03
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BAK-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BAK04 is the date assigned by the purchaser to purchase order.
    BAK-05
    328
    Release Number
    Required
    Min 1Max 30

    Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

    Usage notes

    This is the PO Release number for Blanket Release Orders. The Release Number should be returned if it is in the 850 Release Purchase Order.

    BAK-06
    326
    Request Reference Number
    Required
    Min 1Max 45

    Reference number or RFQ number to use to identify a particular transaction set and query (additional reference number or description which can be used with contract number)

    Usage notes

    Pass the Transaction Set Number that is being acknowledged to AT&T Mobility. This element will contain either 850 or 860.

    BAK-08
    127
    Reference Identification
    Required
    Min 1Max 30

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

    • BAK08 is the seller's order number.
    Usage notes

    The Supplier Order Number must be sent in the 855 PO Acknowledgement transaction.

    REF
    050

    PO Type

    RequiredMax use >1

    To specify identifying information

    Usage notes

    The REF02 "ZZ" element must contain the same value that was sent in the Original Purchase Order header REF02 "ZZ" element.

    If the REF*ZZ is present in the 850, the REF02 from the 850 must be sent back to AT&T Mobility.

    Sample EDI:
    REFZZHandset Device Accessory~

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

    Code qualifying the Reference Identification

    ZZ
    Mutually Defined
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    REF
    050

    Revision Number

    RequiredMax use >1

    To specify identifying information

    Usage notes

    The PO Revision Number is generated for each PO Change that is created in the AT&T Mobility ERP system. The PO Revision Number must be returned in the 855 PO Acknowledgement.

    The PO Revision Number will be sent in the EDI 860 Purchase Order Change transaction.

    Sample EDI:
    REFYBRevision Number~

    Example
    Variants (all may be used)
    REFPO Type
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    YB
    Revision Number
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    PER
    060

    Administrative Communications Contact

    OptionalMax use 3

    To identify a person or office to whom administrative communications should be directed

    Usage notes

    This segment mandatory for contact information if N1 segment is not included in data.

    Sample EDI:
    PERBDFirstName LastNameTE123-456-7890~

    Example
    If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    BD
    Buyer Name or Department
    PER-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Optional
    Min 2Max 2

    Code identifying the type of communication number

    PER-04
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    DTM
    150

    PO Received

    RequiredMax use 10

    To specify pertinent dates and times

    Usage notes

    The Purchase Order Date is required for all EDI 855 transactions. This is the date of the original Purchase Order.

    Sample EDI:
    DTM00820070620~

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

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

    008
    Purchase Order Received
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    DTM
    150

    Revision

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    The Purchase Order Revision Date as defined in the EDI 860 Purchase Order Change transaction.
    The Purchase Order Revision Date is only required if the EDI 855 is acknowledging an EDI 860.

    Sample EDI:
    DTM17120070630~

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

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

    171
    Revision
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    N1 Ship To
    RequiredMax >1
    Variants (all may be used)
    N1Supplier
    N1
    300

    Name

    RequiredMax use 1

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

    Usage notes

    Sample EDI:
    N1STShip To Name92Ship To 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

    Provide the Ship To Name from the Original Purchase Order if the N101 element contains qualifier "ST"

    N1-03
    66
    Identification Code Qualifier
    Required

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

    92
    Assigned by Buyer or Buyer's Agent
    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

    Provide the Ship To Code as it appears in the Original Purchase Order.

    N3
    320

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Usage notes

    Sample EDI:
    N3*STREET ADDRESS~

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

    Address information

    N4
    330

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Usage notes

    Sample EDI:
    N4CITYSTZIPCOUS~

    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.
    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.
    N4-03
    116
    Postal Code
    Required
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Required
    Min 2Max 3

    Code identifying the country

    PER
    350

    Administrative Communications Contact

    RequiredMax use >1

    To identify a person or office to whom administrative communications should be directed

    Usage notes

    This segment mandatory for contact information if N1 segment is included in data.
    Sample EDI:
    PERSTFirstName LastNameTE123-456-7890~

    Example
    If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
    If either Communication Number Qualifier (PER-07) or Communication Number (PER-08) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    ST
    Ship To Contact
    PER-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Required

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Required
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-05
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    FX
    Facsimile
    PER-06
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-07
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    EM
    Electronic Mail
    PER-08
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    N1 Supplier
    RequiredMax >1
    Variants (all may be used)
    N1Ship To
    N1
    300

    Name

    RequiredMax use 1

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

    Usage notes

    Sample EDI:
    N1SUSupplier Name92Supplier Code~

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    SU
    Supplier/Manufacturer
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    Provide the Supplier Site Name if the N101 element contains qualifier "SU".

    N1-03
    66
    Identification Code Qualifier
    Required

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

    92
    Assigned by Buyer or Buyer's Agent
    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

    Provide the Supplier Code as it appears in the Original Purchase Order.

    N3
    320

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Usage notes

    Sample EDI:
    N3*STREET ADDRESS~

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

    Address information

    N4
    330

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Usage notes

    Sample EDI:
    N4CITYSTZIPCOUS~

    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.
    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.
    N4-03
    116
    Postal Code
    Required
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Required
    Min 2Max 3

    Code identifying the country

    PER
    350

    Administrative Communications Contact

    RequiredMax use >1

    To identify a person or office to whom administrative communications should be directed

    Usage notes

    This segment mandatory for contact information if N1 segment is included in data.
    Sample EDI:
    PERSUFirstName LastNameTE123-456-7890~

    Example
    If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
    If either Communication Number Qualifier (PER-07) or Communication Number (PER-08) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    SU
    Supplier Contact
    PER-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Required

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Required
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-05
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    FX
    Facsimile
    PER-06
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-07
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    EM
    Electronic Mail
    PER-08
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    Detail

    PO1 Loop
    RequiredMax >1
    PO1
    010

    Baseline Item Data

    RequiredMax use 1

    To specify basic and most frequently used line item data

    • PO102 is required.
    Usage notes

    Sample EDI:
    PO11100EA424*SKRTL.12345VNVendor Item Number~

    Example
    PO1-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • PO101 is the line item identification.
    Usage notes

    The Original Purchase Order or Purchase Order Change line number

    PO1-02
    330
    Quantity Ordered
    Required
    Min 1Max 15

    Quantity ordered

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

    EA
    Each
    PO1-04
    212
    Unit Price
    Required
    Min 1Max 15

    Price per unit of product, service, commodity, etc.

    PO1-06
    235
    Product/Service ID Qualifier
    Required

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

    • PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    SK
    Stock Keeping Unit (SKU)
    PO1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    PO1-08
    235
    Product/Service ID Qualifier
    Required

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

    VN
    Vendor's (Seller's) Item Number
    PO1-09
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    SLN Loop
    RequiredMax >1
    SLN
    490

    Subline Item Detail

    RequiredMax use 1

    To specify product subline detail item data

    Usage notes

    Sample EDI:
    SLN00011O120EA290**SKRTL.29805~

    Example
    SLN-01
    350
    Assigned Identification
    Required
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • SLN01 is the identifying number for the subline item.
    • SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
    Usage notes

    The SLN01 must match the PO101 Line Number.

    SLN-02
    350
    Assigned Identification
    Required
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
    Usage notes

    Unique Counter for each SLN iteration.

    SLN-03
    662
    Relationship Code
    Required

    Code indicating the relationship between entities

    • SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
    O
    Information Only

    Charges which relate to but may not be included in or added to the unit price of the SLN.

    SLN-04
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    SLN-05
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-01
    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

    EA
    Each
    SLN-06
    212
    Unit Price
    Required
    Min 1Max 15

    Price per unit of product, service, commodity, etc.

    SLN-09
    235
    Product/Service ID Qualifier
    Required

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

    • SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    SK
    Stock Keeping Unit (SKU)
    SLN-10
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    PID
    510

    Product/Item Description

    RequiredMax use 1000

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

    Usage notes

    Sample EDI:
    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

    PO3
    520

    Additional Item Detail

    RequiredMax use 25

    To specify additional item-related data involving variations in normal price/quantity structure

    Usage notes

    The PO3 segment is only used to pass the Extended Price to the partner.

    Sample EDI:
    PO3UP**EST120*0EA*290.00~

    Example
    PO3-01
    371
    Change Reason Code
    Required

    Code specifying the reason for price or quantity change

    Usage notes

    The PO301 is not used as a Change to the Purchase Order but is used as per the X12 Standard requirements dictate.

    UP
    Unit Price
    PO3-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    PO3-03
    236
    Price Identifier Code
    Required

    Code identifying pricing specification

    EST
    Estimated Price
    PO3-04
    212
    Unit Price
    Required
    Min 1Max 15

    Price per unit of product, service, commodity, etc.

    Usage notes

    Extended Unit Price:
    Calculated as Line Item Quantity x Item Unit Price = Extended Unit Price

    PO3-06
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

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

    • PO307 defines the unit of measure for PO306.
    EA
    Each
    PO3-08
    352
    Description
    Optional
    Min 1Max 80

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

    Usage notes

    The PO308 segment is the Total for the line item - it is used for informational purposes only to support the calculation.

    ACK
    530

    Line Item Acknowledgment

    RequiredMax use 104

    To acknowledge the ordered quantities and specify the ready date for a specific line item

    Usage notes
    1. If BAK02 contains the qualifier "AT", the Estimated Delivery date must apply to all items on the Original Purchase Order. Do not use the "AT" qualifier in the BAK02 if there are changes to any line item.

    2. The N9 Loop is required per ACK loop if any of the following codes are used in the ACK01:
      ID, IF, IH, IR, IW, R1, R2, R3, R4, R5, R6, R7, R8

    Sample EDI:
    ACKIA120EA01720070608**SKRTL.29805~

    Example
    ACK-01
    668
    Line Item Status Code
    Required

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

    AA
    Item Accepted - Order Forwarded to Alternate Supplier Location
    AC
    Item Accepted and Shipped
    AR
    Item Accepted and Released for Shipment
    BP
    Item Accepted - Partial Shipment, Balance Backordered
    DR
    Item Accepted - Date Rescheduled
    IA
    Item Accepted
    IB
    Item Backordered
    IC
    Item Accepted - Changes Made
    ID
    Item Deleted
    IE
    Item Accepted, Price Pending
    IF
    Item on Hold, Incomplete Description
    IH
    Item on Hold
    IP
    Item Accepted - Price Changed
    IQ
    Item Accepted - Quantity Changed
    IR
    Item Rejected
    IS
    Item Accepted - Substitution Made
    IW
    Item on Hold-Waiver Required
    R1
    Item Rejected, Not a Contract Item
    R2
    Item Rejected, Invalid Item Product Number
    R3
    Item Rejected, Invalid Unit of Issue
    R4
    Item Rejected, Contract Item not Available
    R5
    Item Rejected, Reorder Item as a Just in Time (JIT) Order
    R6
    Item Rejected, Reorder Item as an Extended Delivery Order (EDO)
    R7
    Item Rejected, Reorder Item as a Drop Shipment
    R8
    Item Rejected, Reorder Item as a Surge Order
    SP
    Item Accepted - Schedule Date Pending
    ACK-02
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

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

    EA
    Each
    ACK-04
    374
    Date/Time Qualifier
    Required

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

    017
    Estimated Delivery
    ACK-05
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    ACK-06
    326
    Request Reference Number
    Optional
    Min 1Max 45

    Reference number or RFQ number to use to identify a particular transaction set and query (additional reference number or description which can be used with contract number)

    Usage notes

    Future usage

    ACK-07
    235
    Product/Service ID Qualifier
    Required

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

    SK
    Stock Keeping Unit (SKU)
    ACK-08
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    N9 Loop
    OptionalMax >1

    The N9 Loop is required per ACK loop if any of the following codes are used in the ACK01:
    ID, IF, IH, IR, IW, R1, R2, R3, R4, R5, R6, R7, R8

    N9
    563

    Reference Identification

    RequiredMax use 1

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    Sample EDI:
    N9ZZDETAIL MESSAGE NOTES~

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    ZZ
    Mutually Defined
    N9-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    MSG
    565

    Message Text

    OptionalMax use >1

    To provide a free-form format that allows the transmission of text information

    Usage notes

    Send additional message notes on why the item/component was rejected or changed.

    If the item was accepted with no changes, the N9/MSG loop is not required.

    Sample EDI:
    MSGFREE-FORM MESSAGE TEXTSS~

    Example
    MSG-01
    933
    Free-Form Message Text
    Required
    Min 1Max 264

    Free-form message text

    MSG-02
    934
    Printer Carriage Control Code
    Optional

    A field to be used for the control of the line feed of the receiving printer

    • MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.
    SS
    Advance to new line before print
    N1 Loop
    RequiredMax >1
    N1
    576

    Name

    RequiredMax use 1

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

    Usage notes

    The N1ST on the detail-level N1 should match the N1ST from the header-level.

    Sample EDI:
    N1STShip To Name92Ship To 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

    N1-03
    66
    Identification Code Qualifier
    Required

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

    92
    Assigned by Buyer or Buyer's Agent
    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.
    REF
    610

    Distribution List

    RequiredMax use 12

    To specify identifying information

    Usage notes

    Distribution Number is being sent with the Line Item. Default Distribution Number cannot be null.

    Sample EDI:
    REFKA1~

    Example
    Variants (all may be used)
    REFShipment ID
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    KA
    Distribution List
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    REF
    610

    Shipment ID

    RequiredMax use 12

    To specify identifying information

    Usage notes

    Shipment Number is being sent with the Line Item. Default Shipment Number cannot be null.

    Sample EDI:
    REFSI1~

    Example
    Variants (all may be used)
    REFDistribution List
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    SI
    Shipper's Identifying Number for Shipment (SID)
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Summary

    CTT Loop
    RequiredMax >1
    CTT
    010

    Transaction Totals

    RequiredMax use 1

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

    • The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
    Usage notes

    Sample EDI:
    CTT*1~

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    AMT
    020

    Monetary Amount

    RequiredMax use 1

    To indicate the total monetary amount

    • If AMT is used in the summary area, then AMT01 will = TT and AMT02 will indicate total transaction amount as calculated by the sender.
    Usage notes

    Sample EDI:
    AMTTT34800~

    Example
    AMT-01
    522
    Amount Qualifier Code
    Required

    Code to qualify amount

    TT
    Total Transaction Amount
    AMT-02
    782
    Monetary Amount
    Required
    Min 1Max 15

    Monetary amount

    Usage notes

    Total PO Amount.

    SE
    030

    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*855*0001~
    BAK*00*AT*1317126*20070611*0*850**0001369955~
    REF*YB*Revision Number~
    REF*ZZ*Handset Device Accessory~
    PER*BD*FirstName LastName*TE*123-456-7890~
    DTM*008*20070620~
    DTM*171*20070630~
    N1*ST*Ship To Name*92*Ship To Code~
    N3*STREET ADDRESS~
    N4*CITY*ST*ZIPCO*US~
    PER*ST*FirstName LastName*TE*123-456-7890~
    N1*SU*Supplier Name*92*Supplier Code~
    N3*STREET ADDRESS~
    N4*CITY*ST*ZIPCO*US~
    PER*SU*FirstName LastName*TE*123-456-7890~
    PO1*1*100*EA*424**SK*RTL.12345*VN*Vendor Item Number~
    SLN*0001*1*O*120*EA*290***SK*RTL.29805~
    PID*F****ITEM DESCRIPTION~
    PO3*UP**EST*120**0*EA*290.00~
    ACK*IA*120*EA*017*20070608**SK*RTL.29805~
    N9*ZZ*DETAIL MESSAGE NOTES~
    MSG*FREE-FORM MESSAGE TEXT*SS~
    N1*ST*Ship To Name*92*Ship To Code~
    REF*KA*1~
    REF*SI*1~
    CTT*1~
    AMT*TT*34800~
    SE*28*0001~

    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.