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.
Reprocessing Interface Table Errors:
To reprocess the transaction, complete the following steps:
1. Back up the interface table that contains the transaction in error.
2. Identify the record and note the values in the TRANSID and TRANSSEQ fields.
3. Use a SQL update statement to correct the incorrect data in the record in the interface table.
4. Use the following SQL update statement to set the OA_IFACESTATUS, OA_IFACETIMESTAMP, and OA_IFACEMESSAGE columns in the record to Null and pass the record from Maximo Asset Management to the Oracle open interface table:
update INTERFACETABLE
set OA_IFACESTATUS = NULL,
OA_IFACETIMESTAMP = NULL,
OA_IFACEMESSAGE = NULL
where TRANSID = 'transid value' and
TRANSSEQ = 'transseq value';
commit;
The trigger does not reprocess a transaction until you set OA_IFACESTATUS to null.
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.
Reprocessing Interface Table Errors:
To reprocess the transaction, complete the following steps:
1. Back up the interface table that contains the transaction in error.
2. Identify the record and note the values in the TRANSID and TRANSSEQ fields.
3. Use a SQL update statement to correct the incorrect data in the record in the interface table.
4. Use the following SQL update statement to set the OA_IFACESTATUS, OA_IFACETIMESTAMP, and OA_IFACEMESSAGE columns in the record to Null and pass the record from Maximo Asset Management to the Oracle open interface table:
update INTERFACETABLE
set OA_IFACESTATUS = NULL,
OA_IFACETIMESTAMP = NULL,
OA_IFACEMESSAGE = NULL
where TRANSID = 'transid value' and
TRANSSEQ = 'transseq value';
commit;
The trigger does not reprocess a transaction until you set OA_IFACESTATUS to null.
No comments:
Post a Comment