Dot Foods
/
Purchase Order Acknowledgment
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Dot Foods. Contact Dot Foods for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Dot Foods 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 samples
    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
    DTM
    150
    Date/Time Reference
    Max use 10
    Required
    DTM
    150
    Date/Time Reference
    Max use 10
    Required
    TD5
    240
    Carrier Details (Routing Sequence/Transit Time)
    Max use 12
    Required
    N1 Loop
    summary
    CTT Loop
    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

    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

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

    Usage notes

    If applicable

    DTM
    150

    Date/Time Reference

    RequiredMax use 10

    To specify pertinent dates and times

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

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

    009
    Process
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    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)

    DTM
    150

    Date/Time Reference

    RequiredMax use 10

    To specify pertinent dates and times

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

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

    068
    Current Schedule Ship
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    TD5
    240

    Carrier Details (Routing Sequence/Transit Time)

    RequiredMax use 12

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

    Example
    TD5-04
    91
    Transportation Method/Type Code
    Required

    Code specifying the method or type of transportation for the shipment

    H
    Customer Pickup
    M
    Motor (Common Carrier)
    N1 Loop
    RequiredMax 200
    Variants (all may be used)
    N1N1 Loop
    N1
    300

    Name

    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

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

    Name

    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

    SF
    Ship From
    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)

    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.
    N4
    330

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

    Detail

    PO1 Loop
    RequiredMax 100000
    PO1
    010

    Baseline Item Data

    RequiredMax use 1

    To specify basic and most frequently used line item data

    • PO102 is required.
    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.
    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

    BG
    Bag
    CA
    Case
    DR
    Drum
    EA
    Each
    GA
    Gallon
    PA
    Pail
    TE
    Tote
    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.
    UK
    U.P.C./EAN Shipping Container Code (1-2-5-5-1)
    PO1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    14 digit GTIN (SCC-14)

    PID Loop
    RequiredMax 1000
    PID
    050

    Product/Item Description

    RequiredMax use 1

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

    Example
    PID-01
    349
    Item Description Type
    Required

    Code indicating the format of a description

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

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

    SAC Loop
    RequiredMax 25
    SAC
    130

    Service, Promotion, Allowance, or Charge Information

    RequiredMax use 1

    To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

    Usage notes

    Any allowance that Dot maintains at the item level must be communicated on the 855 at the item level in order for the pricing to match. Please
    contact your Dot Foods' EDI Coordinator if you are unsure as to which allowances are maintained at the item level.

    Example
    SAC-01
    248
    Allowance or Charge Indicator
    Required

    Code which indicates an allowance or charge for the service specified

    • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
    A
    Allowance
    C
    Charge
    SAC-02
    1300
    Service, Promotion, Allowance, or Charge Code
    Required
    Min 4Max 4

    Code identifying the service, promotion, allowance, or charge

    SAC-05
    610
    Amount
    Required
    Min 1Max 15

    Monetary amount

    • SAC05 is the total amount for the service, promotion, allowance, or charge.
    • If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
    SAC-08
    118
    Rate
    Required
    Min 1Max 9

    Rate expressed in the standard monetary denomination for the currency specified

    • SAC08 is the allowance or charge rate per unit.
    SAC-15
    352
    Description
    Required
    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.
    Example
    CTT-01
    354
    Number of Line Items
    Optional
    Min 1Max 6

    Total number of line items in the transaction set

    CTT-02
    347
    Hash Total
    Optional
    Min 1Max 10

    Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

    ## Example:
    -.0018 First occurrence of value being hashed.
    .18 Second occurrence of value being hashed.
    1.8 Third occurrence of value being hashed.
    18.01 Fourth occurrence of value being hashed.

    1855 Hash total prior to truncation.
    855 Hash total after truncation to three-digit field.

    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

    Purchase Order Ack from Dot Foods 1

    ST*855*000000394~
    BAK*00*AD*019789-001*20091110~
    DTM*009*20091110*1358~
    DTM*068*20091119~
    TD5****H~
    N1*ST*DOT FOODS INC*9*0256712560101~
    N1*SF*ABC FOOD COMPANIES*9*0291850270000~
    N4*BALTIMORE*MD*212270000~
    PO1**54*CA*17.28**UK*00812704000107~
    PID*F****JR 24/20OZ GREEN APPLE~
    SAC*A*ZZZZ***28512***5.28*******PROMOTION ALLOWANCE~
    PO1**108*CA*17.28**UK*00812704000121~
    PID*F****JR 24/20 WATERMELON~
    SAC*A*ZZZZ***57024***5.28*******PROMOTION ALLOWANCE~
    SE*15*000000394~

    Purchase Order Ack from Dot Foods 2

    ST*855*0695~
    BAK*00*AC*987654-001*20090728~
    DTM*009*20090729*1358~
    DTM*068*20090803~
    TD5****H~
    N1*ST*DOT FOODS INC*9*0256712560101~
    N1*SF*ABC COMPANIES*9*1234567890000~
    N4*JACKSONVILLE*IL*62650~
    PO1*1*8*CA*1.33**UK*90070100046720~
    PID*F****3PC JM SBO HM WA CV 16/20 SBD~
    SAC*A*ZZZZ***23***0.01*******ALLOWANCE~
    PO1*2*180*CA*26.58**UK*10070100060492~
    PID*F****300CT PRCKD BACON REG SLICED~
    SAC*A*ZZZZ***76***0.29*******ALLOWANCE~
    PO1*3*1*CA*34.6**UK*10070100060478~
    PID*F****2/5# PRCKD BACON TOPPNG 1/4"GF~
    SAC*A*ZZZZ***66***0.38*******ALLOWANCE~
    PO1*4*4*CA*1.06**UK*90070100035861~
    PID*F****4PC JM SPICED LCHN MT COV ASM~
    SAC*A*ZZZZ***85***0.01*******ALLOWANCE~
    PO1*5*6*CA*1.79**UK*90070100043774~
    PID*F****3PC FDSRV RND BNL HAM WA 14/16~
    SAC*A*ZZZZ***98***0.02*******ALLOWANCE~
    PO1*6*2*CA*1.93**UK*90070100025367~
    PID*F****4PC J-MOR 1/2 CKD SALAMI COV~
    SAC*A*ZZZZ***66***0.02*******ALLOWANCE~
    PO1*7*2*CA*37.5**UK*10070100071559~
    PID*F****50LB CUBE SNOW CAP LARD~
    SAC*A*ZZZZ***34***0.42*******ALLOWANCE~
    PO1*8*30*CA*37.92**UK*10070100070620~
    PID*F****48-1LB CTN SNOWCAP LARD~
    SAC*A*ZZZZ***23***0.42*******ALLOWANCE~
    PO1*9*7*CA*16.56**UK*10070100018288~
    PID*F****16-12OZ JM SKNLS POL SAUS VP~
    SAC*A*ZZZZ***98***0.18*******ALLOWANCE~
    PO1*10*15*CA*23.85**UK*10070100065015~
    PID*F****15LB FDSER BULK BAC DS14/17RED~
    SAC*A*ZZZZ***56***0.26*******ALLOWANCE~
    PO1*11*8*CA*27.36**UK*00070100016294~
    PID*F****32-12OZ J-MOR HOT DOGS COLORED~
    SAC*A*ZZZZ***76***0.3*******ALLOWANCE~
    PO1*12*18*CA*46.56**UK*10070100060188~
    PID*F****24-1LB J-MOR BACON T VAC~
    SAC*A*ZZZZ***34***0.51*******ALLOWANCE~
    PO1*13*27*CA*26.25**UK*10070100065206~
    PID*F****15LB FDSRV BULK SL BCN14/17GLD~
    SAC*A*ZZZZ***66***0.29*******ALLOWANCE~
    PO1*14*2*CA*2.35**UK*90039073021301~
    PID*F****2-4LB KRET OLIVE LOAF~
    SAC*A*ZZZZ***96***0.03*******ALLOWANCE~
    PO1*15*1*CA*2.35**UK*90039073021332~
    PID*F****2-4LB KRET P&P LOAF~
    SAC*A*ZZZZ***11***0.03*******ALLOWANCE~
    PO1*16*75*CA*21.5**UK*10070043020362~
    PID*F****10LB PEYTON CHORIZO LINKS AC~
    SAC*A*ZZZZ***53***0.24*******ALLOWANCE~
    PO1*17*1*CA*28**UK*10039073040849~
    PID*F****14/8OZ KRET BRN SGR HAM ZIP PK~
    SAC*A*ZZZZ***55***0.31*******ALLOWANCE~
    PO1*18*24*CA*24.11**UK*10070100060546~
    PID*F****300CT PRCKD BACON THIN SLICED~
    SAC*A*ZZZZ***67***0.27*******ALLOWANCE~
    PO1*19*14*CA*1.61**UK*90070100044085~
    PID*F****2PC FSRV BQ 1827 BRAND HAM WA~
    SAC*A*ZZZZ***12***0.02*******ALLOWANCE~
    CTT*19*425~
    SE*67*0695~

    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.