Outbound integration processing

Edit online

The following diagram shows the outbound flow of data from the integration framework to Oracle E-Business Suite.

Diagram depicting the outbound flow of data from Maximo Manage to Oracle Applications

Oracle open interface tables

The Oracle open interface tables are a staging area where outbound integration transactions are stored until you initiate an Oracle E-Business Suite import process. These interface tables are standard, and are provided by the Oracle E-Business Suite.

PL/SQL trigger

When an outbound transaction is passed to an interface table, a trigger is run on the insert or update to the interface table. The trigger extracts the data from the interface table and passes it to the PL/SQL stored procedure for extra processing.

ERP exit procedures

The two ERP exit procedures are Java™‐language exit procedures and PL/SQL stored procedures. The user exit procedures are available for customization.

  • The Java‐language exit procedures validate and manipulate data as it moves between Maximo® Manage and the interface tables.
  • PL/SQL stored procedures and user exits manage data as it moves between the interface tables and Oracle E-Business Suite. The stored procedures contain predefined processing logic and must not be modified in any way.

Oracle Applications import process

An Oracle E-Business Suite import process retrieves data from an Oracle open interface table and creates or updates records in Oracle E-Business Suite database. Each outbound enterprise service has one import process.

Example of outbound processing by using triggers, transfer of purchase requisitions

The transfer events of purchase requisitions are the same for every outbound transaction. The initiating action, integration control names, exit procedure names, and interface table names differ by publish channel.

  1. Create and approve a purchase requisition.
  2. The integration framework creates the object structure (MXPR) from the applicable objects.
  3. The integration framework runs the processing class for the publish channel (MXPR_TOOA12).
  4. If custom processing rules exist, the integration framework applies them to the object structure in the order specified by the processing rule sequence number.
  5. If a Java user exit procedure exists, the integration framework runs the preprocessing method. You must use the preprocessing method to customize the internal record (IR), which contains the data in an integration framework format.
  6. The integration framework calls the Java ERP exit procedure (PROutExt), which does predefined Oracle E-Business Suite processing, and converts data from an object structure to a publish channel format. Both the internal record and external record (ER) exist. The ER contains the transaction data in an Oracle E-Business Suite format.
  7. If a Java user exit procedure exists, the integration framework runs the postprocessing method. Use the postprocessing method to customize the mapping between the IR and the ER.
  8. The integration framework writes the transaction to the outbound queue.
  9. The cron task that polls the outbound queue passes the message to a message router, which identifies and starts the interface table handler.
  10. The processing class that is associated with the handler writes records to the interface table (MXPR_IFACE) and the MXOUT_INTER_TRANS queue table. The latter specifies the action that Oracle E-Business Suite must do on the interface table records.
  11. A PL/SQL trigger and procedure combination on the MXPR_IFACE interface table moves the record from that table to the Oracle E-Business Suite PO_REQUISITIONS_INTERFACE open interface table.
  12. The PR Requisition Import request set, which Oracle E-Business Suite supplies, imports the PR directly into the Oracle E-Business Suite database with the necessary validations.