Hudson's Bay
/
Purchase Order Acknowledgment
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Hudson's Bay. Contact Hudson's Bay for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Hudson's Bay 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
    Reference Identification
    Max use 1
    Required
    DTM
    150
    Date/Time Reference
    Max use 10
    Required
    N1 Loop
    N1
    300
    Name
    Max use 1
    Required
    detail
    PO1 Loop
    PO1
    010
    Baseline Item Data
    Max use 1
    Required
    CTP
    040
    Resale
    Max use 1
    Required
    CTP
    040
    Unit cost price
    Max use 1
    Required
    SDQ
    190
    Destination Quantity
    Max use 500
    Required
    summary
    CTT Loop
    CTT
    010
    Transaction Totals
    Max use 1
    Required
    SE
    030
    Transaction Set Trailer
    Max use 1
    Required
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

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

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

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

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

    Example
    BAK-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    16
    Proposed
    BAK-02
    587
    Acknowledgment Type
    Required

    Code specifying the type of acknowledgment

    AP
    Acknowledge - Product Replenishment
    BAK-03
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    The PO number is pre-issued by HBC. The PO number is are 11-digits (i.e. 7-digit Purchase Order Number plus 4-digit ship-to location).

    BAK-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BAK04 is the date assigned by the purchaser to purchase order.
    REF
    050

    Reference Identification

    RequiredMax use >1

    To specify identifying information

    Usage notes

    Example: REFDP556

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    DP
    Department Number
    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

    Usage notes

    Category Number

    The REF02 should include HBC assigned department. Please confirm department number with your buying office.

    DTM
    150

    Date/Time Reference

    RequiredMax use 10

    To specify pertinent dates and times

    Usage notes

    Example: DTM01020200113

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    010
    Requested Ship
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    N1 Loop
    RequiredMax >1
    N1
    300

    Name

    RequiredMax use 1

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

    Usage notes

    Example: N1ST**920596

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    ST
    Ship To
    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

    Ship-to Location Code

    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

    Example: PO119EA*EN3661601679711

    Example
    If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other is required
    If either Product/Service ID Qualifier (PO1-10) or Product/Service ID (PO1-11) is present, then the other is required
    If either Product/Service ID Qualifier (PO1-12) or Product/Service ID (PO1-13) is present, then the other is required
    If either Product/Service ID Qualifier (PO1-14) or Product/Service ID (PO1-15) is present, then the other is required
    PO1-01
    350
    Assigned Identification
    Required
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

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

    Quantity ordered

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

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

    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.
    EN
    European Article Number (EAN) (2-5-5-1)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    PO1-07
    234
    Product/Service ID
    Required
    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)

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

    Identifying number for a product or service

    PO1-10
    235
    Product/Service ID Qualifier
    Optional

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

    IZ
    Buyer's Size Code
    PO1-11
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PO1-12
    235
    Product/Service ID Qualifier
    Optional

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

    BO
    Buyers Color
    PO1-13
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PO1-14
    235
    Product/Service ID Qualifier
    Optional

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

    IN
    Buyer's Item Number
    PO1-15
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    CTP
    040

    Resale

    RequiredMax use >1

    To specify pricing information

    Usage notes

    Example: CTP*RES272

    Example
    Variants (all may be used)
    CTPUnit cost price
    CTP-02
    236
    Price Identifier Code
    Required

    Code identifying pricing specification

    RES
    Resale
    CTP-03
    212
    Unit Price
    Required
    Min 1Max 15

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

    • See Figures Appendix for an example detailing the use of CTP03 and CTP04.
    • See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
    Usage notes

    Retail Price

    CTP
    040

    Unit cost price

    RequiredMax use >1

    To specify pricing information

    Usage notes

    Example: CTP*UCP1121EA

    Example
    Variants (all may be used)
    CTPResale
    CTP-02
    236
    Price Identifier Code
    Required

    Code identifying pricing specification

    UCP
    Unit cost price
    CTP-03
    212
    Unit Price
    Required
    Min 1Max 15

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

    • See Figures Appendix for an example detailing the use of CTP03 and CTP04.
    • See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
    CTP-04
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    Usage notes

    Buying Pack Qty

    CTP-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
    Min 2Max 2

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

    SDQ
    190

    Destination Quantity

    RequiredMax use 500

    To specify destination and quantity detail

    Usage notes

    As many as 10 locations may be included within the SDQ segment. Multiple SDQ segments may be sent. For store addresses, please refer to the store and DC list available at hbcediextranet.hbc.com/.

    Example:
    SDQEA92VT11013VT11043VT11063VT11073VV11083VT11093VV11113TW11123TW11133CX11143

    Example
    If either Identification Code (SDQ-05) or Quantity (SDQ-06) is present, then the other is required
    If either Identification Code (SDQ-07) or Quantity (SDQ-08) is present, then the other is required
    If either Identification Code (SDQ-09) or Quantity (SDQ-10) is present, then the other is required
    If either Identification Code (SDQ-11) or Quantity (SDQ-12) is present, then the other is required
    If either Identification Code (SDQ-13) or Quantity (SDQ-14) is present, then the other is required
    If either Identification Code (SDQ-15) or Quantity (SDQ-16) is present, then the other is required
    If either Identification Code (SDQ-17) or Quantity (SDQ-18) is present, then the other is required
    If either Identification Code (SDQ-19) or Quantity (SDQ-20) is present, then the other is required
    If either Identification Code (SDQ-21) or Quantity (SDQ-22) is present, then the other is required
    SDQ-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
    SDQ-02
    66
    Identification Code Qualifier
    Required

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

    • SDQ02 is used only if different than previously defined in the transaction set.
    92
    Assigned by Buyer or Buyer's Agent
    SDQ-03
    67
    Identification Code
    Required
    Min 2Max 80

    Code identifying a party or other code

    • SDQ03 is the store number.
    Usage notes

    Alphanumeric Store Code

    SDQ-04
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    SDQ-05
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Alphanumeric Store Code

    SDQ-06
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-07
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Alphanumeric Store Code

    SDQ-08
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-09
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Alphanumeric Store Code

    SDQ-10
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-11
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Alphanumeric Store Code

    SDQ-12
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-13
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Alphanumeric Store Code

    SDQ-14
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-15
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Alphanumeric Store Code

    SDQ-16
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-17
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Alphanumeric Store Code

    SDQ-18
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-19
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Alphanumeric Store Code

    SDQ-20
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-21
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Alphanumeric Store Code

    SDQ-22
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    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

    Example: CTT*12

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

    Total number of line items in the transaction set

    Usage notes

    Number of PO1 segments.

    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

    GE

    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

    IEA

    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*373864199
    BAK*16*AP*37386410596*20200106
    REF*DP*556
    DTM*010*20200113
    N1*ST**92*0596
    PO1*1*9*EA***EN*9991601679711
    CTP**UCP*112*1*EA
    CTP**RES*272
    SDQ*EA*92*TR1613*1*TR1560*1*TQ1601*3*TR1637*1*TR1604*1*TR1606*1*LS1617*1
    PO1*2*2*EA***EN*9999601684296
    CTP**UCP*25.05*1*EA
    CTP**RES*80.5
    SDQ*EA*92*TR1613*2
    PO1*3*7*EA***EN*9991601676284
    CTP**UCP*56*1*EA
    CTP**RES*175
    SDQ*EA*92*TR1613*1*TR1560*1*TQ1601*1*TR1637*1*TR1604*1*TR1606*1*LS1617*1
    PO1*4*10*EA***EN*9991601670442
    CTP**UCP*35.25*1*EA
    CTP**RES*72
    SDQ*EA*92*TR1613*2*TR1560*1*TQ1601*3*TR1637*1*TR1604*1*TR1606*1*LS1617*1
    PO1*5*1*EA***EN*9991601666896
    CTP**UCP*12.4*1*EA
    CTP**RES*32
    SDQ*EA*92*TR1963*1
    SE*600*373864199

    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.