As part of a main interface using this IKM for Event Queue controlled updates, this IKM can also be used in a nested or temporary interface to give additional functionality in the SQL generated for the nested SQL block. The main benefit is the ability to use the event queue table as the driving table in incremental load, but exclude the event queue table altogether in full load. Also, the use of hints is supported.
Prerequisites for Nested KM Usage
The main interface must use this KM.
The event queue table must be specified in the Event Queue Table option.
The interface must contain only the following:
Main source table
Event queue table
Join between these using ANSI syntax
Mapping Event Queue Columns
In some cases the event queue columns may need to be referenced in parent interfaces. They can be mapped directly in the nested interface if they are identified with the UD1 flexfield. This includes them in the generated SQL block only in incremental load when the event queue table is also included. For full load both the event queue table and any columns mapped from it will be excluded.
Options for Functionality
Event Queue Table — Explicitly name the event queue table that is controlling the incremental load. This should be one of the two source tables on the nested interface.
Options for Performance Tuning
Hints — This IKM allows the passing of hints into the generated SQL. See My Oracle Support document (ID 1963225.1) titled Oracle Business Intelligence Applications Version 11g Performance Recommendations.