Reprocessing Interface Table Errors MEA (Maximo Enterprise Adapter for Oracle Applications) | IBM Maximo

When an error occurs in an Maximo outbound transaction, the adapter stops processing the transaction and updates the interface table status columns with information about the error. There is no user interface for correcting errors in the Maximo Asset Management interface tables, so you must update the record directly with a SQL tool.

Interface Table Status:
Every outbound interface table contains the following columns, which contain information about the status of the transaction:
OA_IFACESTATUS: The status of the transaction. It has three types:

1. DONE: The transaction was successful.
2. WARNING: The data was transferred but a problem was encountered.
3. ERROR: Due to a system or data error, the data transfer did not occur. Check OA_IFACEMESSAGE for error messages.

OA_IFACETIMESTAMP: The date and time the transaction completed or failed.

OA_IFACEMESSAGE: A general message about errors.

The triggers, which reside on the outbound interface tables, are of trigger type before insert or update. Therefore, directly updating the interface table transactions ensures that the transaction is processed.
Triggers do not exist for the inbound enterprise services. These processes are asynchronous and the integration framework retrieves the records.
The following steps describe how to update an outbound transaction with an error in the interface table, then send the transaction to the Oracle open interface tables again.

Import Data into Maximo using INTERFACE tables MIF – IBM Maximo

First of all, we need to have interface/intermediate tables to import something into Maximo from an external/3^rd party database. Suppose we want to import some inventory data or for instance we try to figure out with a real example. Let’s assume we need to import data from a legacy application into Maximo. That legacy application is actually an inventory issuance system already implemented somewhere, we have to integrate it with New Maximo Inventory system.

MATRECTRANS tables is actually the main table to

To import data into Maximo, few steps are required to configure step by step.

1.            Object Structure (OS)

2.            End Point (EP)

3.            Enterprise services (Inbound or to import data) (ES)

4.            Publish Channel (Outbound or export data, we will not use in this case) (PC)

5.            and Combine above all into an External System (ExS)

6.            Generate Interface tables

7.            Configure Cron task for Scheduling (CT)

8.            Done. Now insert data into Interface tables and Maximo will read as per given schedule in CT.

Object Structures (OS)