X12 855 Purchase Order Acknowledgment (GSA OMS)
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- PR
- Purchase Order Acknowledgement (855)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
- AK
- Acknowledge - No Detail or Change
- AT
- Accepted
- RJ
- Rejected - No Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
Use to identify the number of a release, call or delivery order against a basic award instrument to which this transaction set applies. Cite the number from BEG04 of the applicable 850 transaction set. Purchase Order/delivery order placed here.
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
Use to identify the effective date of the award instrument to which this transaction set applies. Cite the number from BEG05 of the applicable 850 transaction set.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Use to identify the award instrument number to which this transaction set applies. Cite the number from BEG03 of the applicable 850 transaction set. Contract number placed here.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- PO
- Party to Receive Invoice for Goods or Services
- SE
- Selling Party
Code designating the system/method of code structure used for Identification Code (67)
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.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Use this segment when BAK02 is code AC to identify a rejected line item or to identify the corrected line item information when it differs from that information contained in the applicable 850 transaction set.
- When one or more line items are rejected, identify the line items in this segment and cite the appropriate code in ACK01.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Cite the same PO101 line item number as contained in the 850 transaction set.
Quantity ordered
Use to identify the quantity accepted by the selling party. If the total quantity ordered is accepted, cite the quantity that was shown in the 850 transaction set.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Use to identify the unit of measure applicable to the quantity cited in PO102. If the unit of measure that was shown in the 850 transaction set is accepted, cite that unit of measure.
Price per unit of product, service, commodity, etc.
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.
Cite the appropriate code to identify the corrected line item information when different from that contained in the 850 transaction set.
- Use the LIN segment for the identification of manufacturers and associated part numbers.
- FS
- National Stock Number
- MG
- Manufacturer's Part Number
- PD
- Part Number Description
- VP
- Vendor's (Seller's) Part Number
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
Use this segment when BAK02 is code AC to provide information related to the line item identified in PO101. If a line item is rejected, cite the appropriate code in ACK01.
Code specifying the action taken by the seller on a line item requested by the buyer
- AC
- Item Accepted and Shipped
- IA
- Item Accepted
- IB
- Item Backordered
- ID
- Item Deleted
- IR
- Item Rejected
- IS
- Item Accepted - Substitution Made
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code specifying type of date or time, or both date and time
- 011
- Shipped
- 068
- Current Schedule Ship
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- FS
- National Stock Number
- MG
- Manufacturer's Part Number
- PD
- Part Number Description
- PQ
- Product ID Attribute Code
- VP
- Vendor's (Seller's) Part Number
- ZZ
- Mutually Defined
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- 2I
- Tracking Number
- IL
- Internal Order Number
- RQ
- Purchase Requisition Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Summary
Transaction Totals
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.
Total number of line items in the transaction set
Use to identify the total number of PO1 segments contained in this transaction set.
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.
-.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.
Use to identify the sum of the quantities (PO102) for all PO1 segments.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
EDI_855_1.txt
GS*PR*TESTISA*GSAOMST*20160328*2110*459213845*X*004010~
ST*855*459213863~
BAK*00*AC*BPA NUMBER*20160328*PO NUMBER****20160328~
PO1*1*2*EA*18.8**FS*7510000861234~
ACK*IA*2*EA*068*20160401~
N9*IL*FB230060883DRG~
CTT*1~
SE*7*459213863~
GE*1*459213845~
IEA*1*459213809~
EDI_855_2.txt
GS*PR*TESTISA*GSAOMST*20160311*1246*000003259*X*004010~
ST*855*000003259~
BAK*00*AC*BPA NUMBER*20160304*PO NUMBER****20160311~
N1*BY*George Doukas~
N1*SE**9*151041234~
PO1*1*1*EA*217.96**FS*7510015181234~
ACK*IA*1*EA~
N9*IL*N0018960641234~
PO1*2*1*EA*217.96**FS*7510015184567~
ACK*IA*1*EA~
N9*IL*N00189606430BG~
CTT*2~
SE*12*000003259~
GE*1*000003259~
IEA*1*000003259~
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.