X12 855 Purchase Order Acknowledgment
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
Example: BAK00AD013271064520090612
Code specifying the type of acknowledgment
- AD
- Acknowledge - With Detail, No Change
Identifying number for Purchase Order assigned by the orderer/purchaser
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Example: CURSEUSD
Reference Identification
To specify identifying information
Example: REFCO11KH111D
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
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
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
Name
To identify a party by type of organization, name, and code
In this Header position of the Purchase Order Acknowledgment document, this segment identifies the destination party.
Example: N1BYPURCHASING PARTYZZ0000011111
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
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
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
In this Header position of the Purchase Order Acknowledgment document, this segment provides additional detail to the N1 Segment.
Example: N2*TRADING PARTNER
Address Information
To specify the location of the named party
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
Geographic Location
To specify the geographic place of the named party
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
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
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.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
In this Header position of the Purchase Order Acknowledgment document, this segment identifies the responsible contact.
Example: PERCNJOHN DOE
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
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
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type of unit price for an item
- CA
- Catalog
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
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
Product/Item Description
To describe a product or process in coded or free-form format
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
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
A free-form description to clarify the related data elements and their content
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.
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
Monetary Amount
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.
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
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample
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.