The Oracle Business Analytics Warehouse tables are automatically deployed during the installation process when the Business Analytics Applications Suite Repository Creation Utility (RCU) executes a shipped DDL script.
The RCU does not prompt for which tablespace to assign to the individual tables and related indexes nor does it provide a mechanism for you to alter the shipped DDL. To introduce changes to the Oracle Business Analytics Warehouse data model, you use Oracle Data Integrator (ODI) to generate a new DDL script.
You may want to regenerate the Oracle Business Analytics Warehouse DDL for these reasons:
You may want to modify the Oracle Business Analytics Warehouse, either by modifying existing tables or creating new ones.
You may want to have separate development environments. In this case you must use ODI to generate the DDL to be executed in these environments to deploy the Oracle Business Analytics Warehouse tables rather than run the RCU for each environment.
The default tablespace assigned to the Oracle Business Analytics Warehouse database user is used for all tables and indexes when those objects are created by the RCU. You may want to assign different tablespaces to the DW tables other than the default tablespace associated with the database user.
If a patch or upgrade is applied that alters an ODI data store or introduces a new ODI data store, the corresponding database table must be altered or created.
You can make changes directly in the database but these changes must be synchronized with the ODI Repository. This is done by running the Reverse Knowledge Module (RKM) of Oracle BI Applications to bring in the changes into ODI. If this RKM is not run, ODI will not be aware of these changes, which can lead to problems when populating the affected warehouse table.