Purchase order APIs

Purchase orders allow companies to exchange data about requests to purchase goods and services with upstream and downstream supply chain trade partners without giving these trade partners access to their serialization system of record. These purchase orders can be used to request specific products and quantities from their Partners and confirm that partners have the requested product and quantities on hand and intend to fulfill the request via a purchase order acknowledgment.

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement,; Function = Supply Chain, IT,

Purchase Orders (IDoc)

The Purchase Orders (POs) IDoc message sends a request and commitment from the buyer to pay the seller for the sale of specific products or services to be delivered in the future.

Companies can communicate using the standard IDoc format they normally use to communicate with Partners from their ERP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, companies must follow some TraceLink specific requirements for the message header control settings in all asynchronous IDoc message communications sent inbound to TraceLink.
  • Message Type: MPC_PURCHASE_ORDER (Purchase Order)
  • IDoc Format: ORDERS05
  • Transform Names:
    • B2B_IDoc_ORDERS05_PurchaseOrder_IB_V3
    • B2B_IDoc_ORDERS05_PurchaseOrder_OB_V1

When sending a PO IDoc message from your company inbound to TraceLink the following hierarchy must be adhered to for TraceLink to correctly process the B2B message.

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement,; Function = Supply Chain, IT,

Purchase Orders (X12)

The Purchase Orders (POs) X12 850 message sends a request and commitment from the buyer to pay the seller for the sale of specific products or services to be delivered in the future.

Companies can communicate using the standard X12 format they normally use to communicate with Partners from their SAP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, TraceLink only processes some of the elements included in the standard X12 message. TraceLink will not process elements that are included in the message but not present in message hierarchy provided.
  • Message Type: MPC_PURCHASE_ORDER (Purchase Order)
  • X12 Transaction: 850
  • Transform Names:
    • B2B_EDI_X12_850_PurchaseOrder_IB_V1
    • B2B_EDI_X12_850_PurchaseOrder_OB_V1

When sending a PO X12 850 message from your company inbound to TraceLink, the following hierarchy must be adhered to for TraceLink to correctly process the B2B message:

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement,; Function = Supply Chain, IT,

Purchase Orders (EDIFACT)

The Purchase Orders EDIFACT ORDERS message sends a request and commitment from the buyer to pay the seller for the sale of specific products or services to be delivered in the future.

Companies can communicate using the standard EDIFACT format they normally use to communicate with Partners from their SAP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, TraceLink only processes some of the elements included in the standard EDIFACT message. TraceLink will not process elements that are included in the message but not present in message hierarchy provided.
  • Message Type: MPC_PURCHASE_ORDER (Purchase Order)
  • EDIFACT Format: ORDERS
  • Transform Names:
    • B2B_EDI_EDIFACT_ORDERS_PurchaseOrder_IB_V1

    • B2B_EDI_EDIFACT_ORDERS_PurchaseOrder_OB_V1

When sending an EDIFACT ORDERS message from your company inbound to TraceLink, the following hierarchy must be adhered to for TraceLink to correctly process the B2B message:

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement,; Function = Supply Chain, IT,

Purchase Order Acknowledgments (IDoc)

The PO Acknowledgment IDoc message sends a response to a PO from the seller to the buyer. In addition to confirming the receipt of a new order, the acknowledgment tells the buyer if the PO was accepted, if there are any required changes, or if it was rejected.

Companies can communicate using the standard IDoc format they normally use to communicate with Partners from their ERP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, companies must follow some TraceLink specific requirements for the message header control settings in all asynchronous IDoc message communications sent inbound to TraceLink.
  • Message Type: MPC_PURCHASE_ORDER_ACK (Purchase Order Acknowledgment)
  • IDoc Format: ORDRSP.ORDERS05
  • Transform Names:
    • B2B_IDoc_ORDERS05_PurchaseOrderAcknowledgment_IB_V1
    • B2B_IDoc_ORDERS05_PurchaseOrderAcknowledgment_OB_V2

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement,; Function = Supply Chain, IT,

Purchase Order Acknowledgments (X12)

The PO Acknowledgment X12 855 message sends a response to a PO from the seller to the buyer. In addition to confirming the receipt of a new order, the acknowledgment tells the buyer if the PO was accepted, if there are any required changes, or if it was rejected.

Companies can communicate using the standard X12 format they normally use to communicate with Partners from their SAP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, TraceLink only processes some of the elements included in the standard X12 message. TraceLink will not process elements that are included in the message but not present in message hierarchy provided.
  • Message Type: MPC_PURCHASE_ORDER_ACK (Purchase Order Acknowledgment)
  • X12 Format: 855
  • Transform Names:
    • B2B_EDI_X12_855_PurchaseOrderAcknowledgment_IB_V1
    • B2B_EDI_X12_855_PurchaseOrderAcknowledgment_OB_V1

When sending a PO Acknowledgment X12 855 message from your company inbound to TraceLink, the following hierarchy must be adhered to for TraceLink to correctly process the B2B message:

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement,; Function = Supply Chain, IT,

Purchase Order Acknowledgments (EDIFACT)

The PO Acknowledgment EDIFACT ORDRSP message sends a response to a PO from the seller to the buyer. In addition to confirming the receipt of a new order, the acknowledgment tells the buyer if the PO was accepted, if there are any required changes, or if it was rejected.

Companies can communicate using the standard EDIFACT format they normally use to communicate with Partners from their SAP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, TraceLink only processes some of the elements included in the standard EDIFACT message. TraceLink will not process elements that are included in the message but not present in message hierarchy provided.
  • Message Type: MPC_PURCHASE_ORDER_ACK (Purchase Order Acknowledgment)
  • EDIFACT Format: ORDRSP
  • Transform Names:
    • B2B_EDI_EDIFACT_ORDRSP_PurchaseOrderAcknowledgment_IB_V1
    • B2B_EDI_EDIFACT_ORDRSP_PurchaseOrderAcknowledgment_OB_V1

When sending a PO Acknowledgment EDIFACT ORDRSP message from your company inbound to TraceLink, the following hierarchy must be adhered to for TraceLink to correctly process the B2B message: