Adobe
/
Purchase Order Acknowledgment
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Adobe. Contact Adobe for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Adobe 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 free 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
    CUR
    040
    Currency
    Max use 1
    Optional
    REF
    050
    Reference Identification
    Max use 1
    Optional
    TD5
    240
    Carrier Details (Routing Sequence/Transit Time)
    Max use 12
    Optional
    N1 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

    Example: BAK00AD013271064520090612

    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

    AD
    Acknowledge - With Detail, No Change
    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
    Optional
    Min 1Max 30

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

    BAK-07
    367
    Contract Number
    Optional
    Min 1Max 30

    Contract number

    CUR
    040

    Currency

    OptionalMax use 1

    To specify the currency (dollars, pounds, francs, etc.) used in a transaction

    Usage notes

    Example: CURSEUSD

    Example
    CUR-01
    98
    Entity Identifier Code
    Required

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

    SE
    Selling Party
    CUR-02
    100
    Currency Code
    Required
    Min 3Max 3

    Code (Standard ISO) for country in whose currency the charges are specified

    REF
    050

    Reference Identification

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Example: REFCO11KH111D

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    CO
    Customer Order 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

    TD5
    240

    Carrier Details (Routing Sequence/Transit Time)

    OptionalMax use 12

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

    Usage notes

    In this Header position of the Purchase Order Acknowledgment document, this segment identifies carrier sequence data for the entire order. 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; use TD503 to identify the actual routing sequence, specified by the part identified in TD502.

    Example: TD5*910000011111

    Example
    If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
    TD5-02
    66
    Identification Code Qualifier
    Optional

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

    • When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
    91
    Assigned by Seller or Seller's Agent
    ZZ
    Mutually Defined
    TD5-03
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    N1 Loop
    OptionalMax >1
    N1
    300

    Name

    RequiredMax use 1

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

    Usage notes

    In this Header position of the Purchase Order Acknowledgment document, this segment identifies the destination party.

    Example: N1BYPURCHASING PARTYZZ0000011111

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    BT
    Bill-to-Party
    BY
    Buying Party (Purchaser)
    CA
    Carrier
    II
    Issuer of Invoice
    PR
    Payer
    SE
    Selling Party
    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    91
    Assigned by Seller or Seller's Agent
    93
    Code assigned by the organization originating the transaction set
    94
    Code assigned by the organization that is the ultimate destination of the transaction set
    ZZ
    Mutually Defined
    N1-04
    67
    Identification Code
    Optional
    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.
    N2
    310

    Additional Name Information

    OptionalMax use 2

    To specify additional names or those longer than 35 characters in length

    Usage notes

    In this Header position of the Purchase Order Acknowledgment document, this segment provides additional detail to the N1 Segment.

    Example: N2*TRADING PARTNER

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N2-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    Usage notes

    Example: N2*TRADING PARTNER

    N3
    320

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Usage notes

    In this Header position of the Purchase Order Acknowledgment document, this segment identifies the street number and name of the destination party.

    Example: N31111 Main StreetVENDOR A11111

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

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    330

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Usage notes

    In this Header position of the Purchase Order Acknowledgment document, this segment identifies the city, state/province, and postal code of the destination party.

    Example: N4SAN JOSECA951102704US

    Example
    N4-01
    19
    City Name
    Optional
    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
    Optional
    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
    Optional
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    PER
    350

    Administrative Communications Contact

    OptionalMax use >1

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

    Usage notes

    In this Header position of the Purchase Order Acknowledgment document, this segment identifies the responsible contact.

    Example: PERCNJOHN DOE

    Example
    PER-01
    366
    Contact Function Code
    Required

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

    CN
    General Contact
    PER-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    Detail

    PO1 Loop
    OptionalMax >1
    PO1
    010

    Baseline Item Data

    RequiredMax use 1

    To specify basic and most frequently used line item data

    • PO102 is required.
    Usage notes

    In this Detail position of the Purchase Order Acknowledgment document, this segment identifies specific part numbers. There is one PO1 segment for each different part number. The Product ID Qualifiers and Product ID should completely specify the parts being ordered.

    For Adobe's AVL 5.0 Licensing Program, the PO107 SKU will extend to 15 digits.

    Example: PO10000101EA369CAMG00065008880AD01A00BP*T05249

    Example
    If Unit or Basis for Measurement Code (PO1-03) is present, then Quantity Ordered (PO1-02) is required
    If Basis of Unit Price Code (PO1-05) is present, then Unit Price (PO1-04) is required
    If either Product/Service ID Qualifier (PO1-06) or Product/Service ID (PO1-07) is present, then the other is required
    If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other is required
    PO1-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • PO101 is the line item identification.
    PO1-02
    330
    Quantity Ordered
    Optional
    Min 1Max 15

    Quantity ordered

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

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

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

    PO1-05
    639
    Basis of Unit Price Code
    Optional

    Code identifying the type of unit price for an item

    CA
    Catalog
    PO1-06
    235
    Product/Service ID Qualifier
    Optional

    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.
    MG
    Manufacturer's Part Number
    PO1-07
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PO1-08
    235
    Product/Service ID Qualifier
    Optional

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

    BP
    Buyer's Part Number
    PO1-09
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PID Loop
    OptionalMax >1
    PID
    050

    Product/Item Description

    RequiredMax use 1

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

    Usage notes

    In this Detail position of the Purchase Order Acknowledgment document, this segment identifies the free-form description.

    Example: PIDF***PHSP,CS4,WIN,AOO,UE,001,N/A

    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
    Optional
    Min 1Max 80

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

    Summary

    CTT Loop
    OptionalMax >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

    In this Summary position of the Purchase Order Acknowledgment document, this segment identifies the Purchase Order Acknowledgment's number of line items.

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

    OptionalMax 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

    In this Summary position of the Purchase Order Acknowledgment document, this segment identifies the Purchase Order Acknowledgment's number of line items.

    Example: CTT*1

    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

    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*852281220
    BAK*00*AD*0132710645*20090612
    CUR*SE*USD
    REF*CO*11KH111D
    TD5**ZZ*0000011111
    TD5**ZZ*0000011111
    TD5**ZZ*0000011111
    TD5**91*0000011111
    TD5**ZZ*0011111111
    N1*BY*PURCHASING PARTY*ZZ*0000011111
    N2*TRADING PARTNER
    N3*1111 Main Street*VENDOR A11111
    N4*SAN JOSE*CA*951102704*US
    N1*BT*BILL TO PARTY*ZZ*0000022222
    N2*TRADING PARTNER
    N3*2222 Main Street*VENDOR A22222
    N4*SAN JOSE*CA*951102704*US
    N1*PR*PAYER PARTY*ZZ*0000033333
    N2*TRADING PARTNER
    N3*3333 Main Street*VENDOR A33333
    N4*SAN JOSE*CA*951102704*US
    N1*CA*OTHER CARRIER-NOTE IN SHIP INSTRUC.*ZZ*0000444444
    N2*OTHER CARRIER-NOTE IN SHIP INSTRUC.
    N3*4444 MAIN ST.
    N4*SANTA CLARA*CA*95050*US
    N1*II*ADOBE SYSTEMS INCORPORATED*91*0000012137
    N2*ADOBE SYSTEMS INCORPORATED
    N3*345 PARK AVENUE
    N4*SAN JOSE*CA*95110*US
    N1*SE*ADOBE SYSTEMS INCORPORATED*91*ADUS
    N2*ADOBE SYSTEMS INCORPORATED
    N3*345 Park Avenue
    N4*SAN JOSE*CA*95110*US
    N1*ST*SHIP TO PARTY*ZZ*0055555555
    N2*TRADING PARTNER
    N3*5555 161TH AVE
    N4*SEATTLE*WA*98134*US
    PER*CN*JOHN DOE
    PO1*000010*1*EA*369*CA*MG*00065008880AD01A00*BP*T05249
    PID*F****APRO,9.0,WIN,AOO,UE,1PK,N/A
    CTT*1
    AMT*TT*369
    SE*43*852281220

    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.