X12 855 Managed Functions 855 to cXML
This guide describes the X12 855 specification for converting an X12 855 to a cXML Order Acknowledgement.
- ~ 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
Code identifying purpose of transaction set
"01" means (Original) --> "new"
"05" means (Replace) --> "update"
- 00
- Original
- 01
- Cancellation
- 02
- Add
- 03
- Delete
- 04
- Change
- 05
- Replace
- 5C
- Chargeable Resubmission
- 06
- Confirmation
- 07
- Duplicate
- 08
- Status
- 10
- Not Found
- 11
- Response
- 12
- Not Processed
- 13
- Request
- 14
- Advance Notification
- 15
- Re-Submission
- 16
- Proposed
- 17
- Cancel, to be Reissued
- 18
- Reissue
- 19
- Seller initiated change
- 20
- Final Transmission
- 21
- Transaction on Hold
- 22
- Information Copy
- 24
- Draft
- 25
- Incremental
- 26
- Replace - Specified Buyers Parts Only
- 27
- Verify
- 28
- Query
- 30
- Renewal
- 31
- Allowance/Addition
- 32
- Recovery/Deduction
- 33
- Request for Payment
- 34
- Payment Declined
- 35
- Request Authority
- 36
- Authority to Deduct (Reply)
- 37
- Authority Declined (Reply)
- 38
- No Financial Value
- 39
- Response to Proposed Trip Plan
- 40
- Commitment Advice
- 41
- Corrected and Verified
- 42
- Temporary Record
- 43
- Request Permission to Service
- 44
- Rejection
- 45
- Follow-up
- 46
- Cancellation with Refund
- 47
- Transfer
- 48
- Suspended
- 49
- Original - No Response Necessary
- 50
- Register
- 51
- Historical Inquiry
- 52
- Response to Historical Inquiry
- 53
- Completion
- 54
- Approval
- 55
- Excavation
- 56
- Expiration Notification
- 77
- Simulation Exercise
- CN
- Completion Notification
- CO
- Corrected
- EX
- Final Loading Configuration
- GR
- Granted
- PR
- Proposed Loading Configuration
- RH
- Release Hold
- RV
- Revised Loading Configuration
- SU
- Status Update
- ZZ
- Mutually Defined
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
- AD
- Acknowledge - With Detail, No Change
- AE
- Acknowledge - With Exception Detail Only
- AH
- Acknowledge - Hold Status
- AK
- Acknowledge - No Detail or Change
- AP
- Acknowledge - Product Replenishment
- AT
- Accepted
- NA
- No Acknowledgment Needed
- RD
- Reject with Detail
- RF
- Reject with Exception Detail Only
- RJ
- Rejected - No Detail
- RN
- Rejected - Not as Agreed
- RO
- Rejected With Counter Offer
- RV
- Rejected - Violates Industry Practices
- ZZ
- Mutually Defined
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.
(Purchase Order date, copied from the 850's BEG05)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BAK08 is the seller's order number.
Date expressed as CCYYMMDD
- BAK09 is the date assigned by the sender to the acknowledgment.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Code identifying an organizational entity, a physical location, property or an individual
Sample is "BY" -> Buying Party (Purchaser)
Code (Standard ISO) for country in whose currency the charges are specified
Sample codes:
CAD -> Canadian Dollars
GBP -> British Pound
USD -> US Dollars
AUD -> Australian Dollars
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Line number from 850 PO
This is the line number from the buyer's PO that this acknowledgement relates to.
Must match counterpart line number from 850. To reference a specific line item in the Purchase Order, you must copy the exact value of PO101 from the line of the 850 you are confirming.
Total amount that the Buyer ordered. This must be an exact copy of its counterpart from the 850.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code identifying the type of unit price for an item
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO106,107 product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
Code specifying the action taken by the seller on a line item requested by the buyer
- AA
- Item Accepted - Order Forwarded to Alternate Supplier Location
- AC
- Item Accepted and Shipped
- AR
- Item Accepted and Released for Shipment
- BP
- Item Accepted - Partial Shipment, Balance Backordered
- DR
- Item Accepted - Date Rescheduled
- IA
- Item Accepted
- IB
- Item Backordered
- IC
- Item Accepted - Changes Made
- ID
- Item Deleted
- IE
- Item Accepted, Price Pending
- IF
- Item on Hold, Incomplete Description
- IH
- Item on Hold
- IP
- Item Accepted - Price Changed
- IQ
- Item Accepted - Quantity Changed
- IR
- Item Rejected
- IS
- Item Accepted - Substitution Made
- IW
- Item on Hold-Waiver Required
- R1
- Item Rejected, Not a Contract Item
- R2
- Item Rejected, Invalid Item Product Number
- R3
- Item Rejected, Invalid Unit of Issue
- R4
- Item Rejected, Contract Item not Available
- R5
- Item Rejected, Reorder Item as a Just in Time (JIT) Order
- R6
- Item Rejected, Reorder Item as an Extended Delivery Order (EDO)
- R7
- Item Rejected, Reorder Item as a Drop Shipment
- R8
- Item Rejected, Reorder Item as a Surge Order
- SP
- Item Accepted - Schedule Date Pending
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
Reference number or RFQ number to use to identify a particular transaction set and query (additional reference number or description which can be used with contract number)
Use the code VP to indicate that the next element contains the vendor part number
- VP
- Vendor's (Seller's) Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
Line Item Schedule
To specify the data for scheduling a specific line-item
- The SCH segment is used to specify various quantities of items ordered that are to be scheduled. When this segment is used the unit of measurement code (SCH02) should always be identical to the unit of measurement code in the associated PO1 segment (PO103) and the sum of values of quantity (SCH01) should always equal the quantity ordered (PO102) in the PO1 segment.
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
- SCH05 specifies the interpretation to be used for SCH06 and SCH07.
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.
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.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
A free-form description to clarify the related data elements and their content
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.
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
855 Vroozi Items Accepted
GS*PR*075322693*MFVZHEBXXXXXON*20221005*0034*13*X*004010~
ST*855*0013~
BAK*06*AK*2000535644*20220901****624748*20220901~
DTM*067*20221006~
DTM*068*20221006~
PO1*1*2*EA*136.7*CP*VP*WBEWTA67-PB-385-1A-80-F2-CBG*BP*1042215~
ACK*IA*2*EA*068*20221006**VP*WBEWTA67-PB-385-1A-80-F2-CBG*BP*1042215~
PO1*2*2*EA*109.56*CP*VP*EWTA-MPB-335-9A-80-100-FA2-CBK*BP*1286413~
ACK*IA*2*EA*068*20221006**VP*EWTA-MPB-335-9A-80-100-FA2-CBK*BP*1286413~
PO1*3*2*EA*104.75*CP*VP*63412FTLAKX4*BP*1208996~
ACK*IA*2*EA*068*20221006**VP*63412FTLAKX4*BP*1208996~
SE*11*0013~
GE*1*13~
IEA*1*000000013~
855 Vroozi Items Rejected
GS*PR*075322693*MFVZHEBXXXXXON*20221005*0034*13*X*004010~
ST*855*0013~
BAK*06*AK*2000535644*20220901****624748*20220901~
DTM*067*20221006~
DTM*068*20221006~
PO1*1*2*EA*136.7*CP*VP*A3L850-03-BLK-S*BP*VEN1000086~
ACK*IR*2*EA****VP*A3L850-03-BLK-S*BP*VEN1000086~
SE*7*0013~
GE*1*13~
IEA*1*000000013~
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.