This section covers restrictions on reverse-engineering E-Business Suite Tables: The tab Selective reverse cannot be used with this Knowledge Module. Option Min Rows requires Oracle statistics to be computed on all tables.
If the Oracle user defined in the Oracle Data Integrator data server is not the owner of the tables to reverse, you must define synonyms for this user on all tables you wish to reverse.
Only KeyFlexfields are supported. Descriptive FlexFields are not supported.
Using E-Business Suite as a Source in an Integration Interface
When using E-Business Suite as a source, you extract data from the Applications to integrate them into another system (Data warehouse, other database...).
Extracting data from E-Business Suite is performed with regular integration interfaces sourcing from an Oracle Database. For a list of the KMs available for such an integration interface, refer to the Oracle Database chapter in this manual.
Using E-Business Suite as a Target in an Integration Interface
The E-Business Suite IKM is used in integration interfaces that have E-Business Suite interface tables as a target. This IKM works similarly to the IKM Oracle Incremental Update, with some specific options for OpenInterfaces. For the IKM Incremental Update usage and restrictions please refer to the Oracle Database section of this manual.
Integrating Data into E-Business Suite through the OpenInterface
Oracle Data Integrator uses the "OpenInterface" API to write to E-Business Suite. A transaction that loads Oracle application is a batch identified by its Group ID. For example, if you load interface tables to create a product in E-Business Suite, all of these loading operations as well as the calls to the validation and processing programs will use this batch's Group ID. For more information on OpenInterfaces, please refer to the API and OpenInterface Guide of the respective E-Business Suite module or the E-Business Suite Repository.
The configuration of integration interfaces for actions specific to E-Business Suite (Group ID handling, programs execution) is detailed below.
Managing Group IDs
In the first integration interface loading a group of interface tables in one single batch, you must force the creation of a Group ID.
To create a Group ID in an integration interface:
Set the following in the KM options: Set OA_CREATE_NEW_GROUP_ID to YES Provide a Group ID Name in the OA_GROUP_ID_NAME option. Warning: The Group ID Name must be unique at a given instant. You must use the OA_REMOVE_GROUP_ID option to remove a Group ID at the end of the batch processing. Give a valid SQL expression for the Group ID value (use an Oracle Database sequence value - <SEQUENCE_NAME>.NEXTVAL - for instance) in the OA_GROUP_ID_EXPRESSION option.
In the integration interface mapping, select the flag UD1 for all the columns of the interface table you wish to load with the Group ID value and set the mapping value to 0.
Knowledge Modules Reference Guide