This post covers how to configure load plan generator in ODI and necessary configuration steps to do at Business Intelligence Application Configuration Manager and Business Intelligence Application Functional Manager to run finance full load
Load Plan : From ODI 11.1.1 it has new feature called load plan which is used to populate warehouse tables in groups (fact and dimension) in a sequential order or parallel ( Execution Plans in DAC)
A Load Plan is an executable object in Oracle Data Integrator that can contain a hierarchy of steps that can be executed conditionally, in parallel or in series. The leaves of this hierarchy are Scenarios. Packages, interfaces, variables, and procedures can be added to Load Plans for executions in the form of scenarios.
Sample Load plan in BIApps 11.1.1.7.1 you can see sequential steps like PRE_SDE,SDE,SIL and parallel loads (SIL Dimension group ,Fact Group) each one is defined as step (#)
Refer ODI documentation for more information on load plans ( more easy than DAC )
If you followed by earlier post Installation and configuration of BIApps 11.1.1.7.1 once you done with those steps to configure Oracle BI load generator open ODI Studion and Goto ODI --> Oracle BI Load Plan Generator and give your OBIACM schema details then Test Connection --- save and Close
it automatically generates load plan as shown below
Business Intelligence Configuration Manager for full load:
Registering Source Systems and Propagating Connection Details to ODI
- Launch Oracle BI Applications Configuration Manager using the URL http://<host>.<port>/biacm, and log in as the BI Applications Administrator user
- Select the Define Business Intelligence Applications Instance link, which appears under System Setups.Click the Add icon.
- The Register Source dialog is displayed.Click Next. The Register Source in Oracle Data Integrator Topology page is active
![]()
- You should already configure ODIAgent using weblogic to select Logical Agent /Physical Agent to see plans and scenarios using ODI Console look at document to deploy and configure Agent as J2EE component.
- In the context section I prefer to select Global (default) if you are clear and know already mapping of Logical Schema and Physical schema in topology manager then choose Register New Context and give Unique Context Name.
- The source system can be multiple like siebel , people Soft,EBS 11.X.X but you cannot enable multiple instances of same source in below example I configured EBS 12.1..3 two times with different data_source_id but only one is enabled or suppose you have two source instances, Oracle EBS and PeopleSoft, and you are deploying Financial Analytics. If Financial Analytics will only source from PeopleSoft, then you would disable the Oracle EBS source instance for the Financial Analytics offering.
Use Oracle BI Applications Configuration Manager to enable the Oracle BI Applications offerings
Now Open ODI studio and Topology to configure your EBS source as shown below
![]()
Second tab Business Intelligence Applications offerings and associated sources will show the Application(module) you enabled and source which is enabled (VISION) as shown in above figure (Registering Source Systems and Propagating Connection Details to ODI)
You can use the Manage Preferred Currencies dialog to edit the default currency display names. You edit preferred currency name values to change the currency labels that are displayed in all modules associated with BI dashboards. For example, you might want to change the 'Local Currency' label from 'Ledger Currency' to 'Local Currency'.
From the tasks pane select Manage Preferred Currencies and edit the names
Running the Domains Load Plan
You must define, generate, and run a domains load plan to load source-specific data into Oracle BI Applications Configuration Manager tables. This enables Configuration Manager to display the appropriate source-specific values as choices in drop-down lists for setup objects.
For this click on Manage Load Plans and click on plus (+) sign to create new load plan where load plan type Select Domain-only Extract and Load (SDE and SIL) and Source Instances as VISION which is enabled while registering source system with ODI in above system (VIS - Disabled )
Select Fact Groups which are enabled using Manage BI application offerings
Once it is created successfully click on RUN button to start the actual load
Click on execution details icon next to RUN button it will take you to load plan administration screen
but I would prefer you to watch execution scenarios using ODI operator
As you are seeing from last couple of screen I got many issues while running my first full load (VISION- SOURCE) it has duplicates while creating indexs (unique key indexs)
ODI-1232: Procedure TABLE_MAINT_PROC execution fails.
ODI-1228: Task TABLE_MAINT_PROC (Procedure) fails on the target ORACLE connection BIAPPS_DW.
Caused By: java.sql.SQLException: ORA-20000: Error creating Index/Constraint : W_EMPLOYEE_DS_U1 => ORA-01452: cannot CREATE UNIQUE INDEX; duplicate key
SQLs used to remove duplicate keys : (used the same for other tables)
select integration_id, datasource_num_id, src_eff_from_dt, count(*)
from w_employee_ds
group by integration_id, datasource_num_id, src_eff_from_dt
having count(*)>1;
delete from w_employee_ds where integration_id='PER~2901' and datasource_num_id=11;
finally my dashboard looks as below
