Considerations When Using IS-to-Oracle Applications Transactions
IS-to-Oracle Applications transactions defined with the
Oracle Apps Adapter insert data into the Oracle Applications open interface tables.
Errors that occur while data is inserted into the open interface tables insertion are reported when the service executes.
After an IS-to-Oracle Applications transaction has executed successfully, you should schedule a call to the Error Log Service (created at the same time as the Oracle Applications transaction service) to make sure no errors occurred during the Oracle Applications import process.
Alternatively, you can publish the Error Log Service or a web page that calls it so the partner that sent the transaction can check if there is an error.
Many Oracle Applications transactions contain a CREATED_BY column. If you want to track transactions inserted by the
Oracle Apps Adapter, create an Oracle Applications user and set the CREATED_BY input column with that user name.
Within a flow, you can map values to a service’s dataRecord input record, and to the queryParams input record for the service’s associated error service.