Purchasing integration

Vendor (inbound)
The vendor inbound integration point uses the MXVENDOR_IFACE Maximo interface table and the COMPANIES Maximo destination table.
Company contact (inbound)
The company contact inbound integration point uses the MXVENDOR_IFACE Maximo interface table and the COMPCONTACT Maximo destination table.
Purchase requisition (outbound)
The purchase requisition outbound integration point uses the MXPR_IFACE Maximo interface table and the PO_REQUISITIONS_INTERFACE Oracle E-Business Suite applications destination table.
Purchase requisition status update (inbound)
The purchase requisition status update (inbound) integration point uses the MXPR_IFACE Maximo interface table and the PR Maximo destination table.
Purchase order (outbound)
The purchase order (outbound) integration point uses the MXPO_IFACE Maximo interface table and the PO_HEADERS_INTERFACE Oracle E-Business Suite destination table.
Purchase order lines interface (outbound) (POLINE)
The purchase order lines interface (outbound) (POLINE) integration point uses the MXPO_IFACE Maximo interface table and the PO_LINES_INTERFACE Oracle E-Business Suite destination table.
Purchase order lines interface (outbound) (CONTRACT)
The purchase order lines interface (outbound) (CONTRACT) integration point uses the MXPC_IFACE Maximo interface table and the PO_LINES_INTERFACE_ALL Oracle E-Business Suite destination table.
Purchase order distributions (outbound)
The purchase order distributions (outbound) integration point uses the MXPO_IFACE Maximo interface table and the PO_DISTRIBUTIONS_INTERFACE Oracle E-Business Suite destination table.
Purchase order cancel APIs (CONTRACTS)
The purchase order cancel APIs (CONTRACTS) integration point uses the PO_CANCEL_IFACE Maximo interface table. This table is also used to stage Purchase Out Update information. Multiple tables in the PO are updated by the Oracle API, PO_DOCUMENT_CONTROL_PUB.CONTROL_DOCUMENT.
Purchase order cancel APIs (PO)
The purchase order cancel APIs (PO) integration point uses the PO_CANCEL_IFACE Maximo interface table. This table is also used to stage Contract Out Cancel information. Multiple tables in the Purchasing module are updated by the Oracle API, PO_DOCUMENT_CONTROL_PUB.CONTROL_DOCUMENT. Refer to the Oracle Purchasing API documentation for details.
Purchase order update APIs
The purchase order update APIs integration point uses the PO_UPDATE_IFACE Maximo interface table. Multiple tables in the Purchasing module are updated by the Oracle API, PO_CHANGE_API1_S.UPDATE_PO. Refer to the Oracle Purchasing API documentation for details.
Purchase order (inbound)
The purchase order (inbound) integration point uses the MXPO_IFACE Maximo interface table and the PO Maximo destination table.
Purchase order line (inbound)
The purchase order line (inbound) integration point uses the MXPO_IFACE Maximo interface table and the POLINE Maximo destination table.
Purchase order cancel (outbound) contract (outbound)
The purchase order cancel (outbound) contract (outbound) integration point uses the MXPC_IFACE Maximo interface table and the PO_HEADERS_INTERFACE_ALL Oracle E-Business Suite destination table.
Contract (inbound)
The contract (inbound) integration point uses the MXPC_IFACE Maximo interface table and the PURCHVIEW Maximo destination table.
Contract line (inbound)
The contract line (inbound) integration point uses the MXPC_IFACE Maximo interface table and the CONTRACTLINE Maximo destination table.
Contract authorization (inbound)
The contract authorization (inbound) integration point uses the MXPC_IFACE Maximo interface table and the CONTRACTAUTH Maximo destination table.
Receipt (outbound)
The receipt (outbound) integration point uses the MXRECEIPT_IFACE Maximo interface table and the RCV_HEADERS_INTERFACE Oracle E-Business Suite destination table.
Receive transactions (outbound)
The receive transactions (outbound) integration point uses the MXRECEIPT_IFACE Maximo interface table and the RCV_TRANSACTIONS_INTERFACE Oracle E-Business Suite destination table.
Material receipt (inbound)
The material receipt (inbound) integration point uses the MXRECEIPT_IFACE Maximo interface table and the MATRECTRANS Maximo destination table.
Service receipt (inbound)
The service receipt (inbound) integration point uses the MXRECEIPT_IFACE Maximo interface table and the SERVRECTRANS Maximo destination table.
Rotating item receipt (inbound)
The rotating item receipt (inbound) integration point uses the MXRCVROTITM_IFACE Maximo interface table and the MATRECTRANS Maximo destination table.
Asset (inbound)
The asset (inbound) integration point uses the MXRCVROTITM_IFACE Maximo interface table and the ASSET Maximo destination table.
Invoice (outbound)
The invoice (outbound) integration point uses the MXINVOICE_IFACE Maximo interface table and the AP_INVOICES_INTERFACE Oracle E-Business Suite destination table.
Invoice lines (outbound)
The invoice lines (outbound) integration point uses the MXINVOICE_IFACE Maximo interface table and the AP_INVOICE_LINES_INTERFACE Oracle E-Business Suite destination table.
Invoice (inbound)
The invoice (inbound) integration point uses the MXINVOICE_IFACE Maximo interface table and the INVOICE Maximo destination table.
Invoice lines (inbound)
The invoice lines (inbound) integration point uses the MXINVOICE_IFACE Maximo interface table and the INVOICELINE Maximo destination table.

Parent topic: Integration Mapping for IBM Maximo Enterprise Adapter for Oracle Applications