Load Plan Generator (OBIA)
Load Plan Generator is a utility from BI Apps to address the following requirements:
1. Trim the unnecessary tasks
You do not need to run the extract program for a source table if you do not deploy a specific BI Apps module.
You do not need to load a dimension table if the dimension is not used in any of the facts you deployed.
You do not need to load the domain member data if the domain is not used in any of your dimension table.
You do not need to load the subset of the data in the class dimension table if the data is not relevant to the subject area you deployed.
2. Organize the tasks in a sequence
You can ensure that the fact extract is completed before extract dimension data from the source system, so you won’t run into any dangling foreign key due to the data entry during the extraction process.
You can ensure that the dimension data are loaded and updated before the fact data are loaded into the data warehouse tables.
You can ensure that the post load processes to be executed in the end so it won’t block the valuable resources.
3. Support Multiple instances
When you are extract the data from multiple instances, no matter from the same or different sources, the Load Plan Generator learns your configuration from BI Apps Configure Manager and duplicate the tasks for different instances automatically.
4. Include the proper table maintenance logic in the right points
If you are running a full load, the generated load plan include the table maintenance logic so the target table can be truncated before the new data is being loaded.
If you are running an increment ETL load, the BI Apps table maintenance can detect it and skip the truncate operation. The table maintenance calls are added into the proper locations by the load plan generator.
5. Setting Variable Defaults
Some of the variables, such DATASOURCE_NUM_ID is set by Load Plan Generator in the proper location in the generated load plan.
There may be more. The above are what I can think of.