![]() ![]() If you change the default ODI repository ID, make sure the new value is greater than 500.Ī load plan is an executable object that comprises and organizes the child objects (referred to as steps) that carry out the ETL process. A load plan is made up of a sequence of several types of steps. Each step can contain several child steps. ![]() ![]() You define a load plan in Oracle BI Applications Configuration Manager by selecting a data source and one or more fact groups.ĭepending on the step type, the steps can be executed conditionally, in parallel or sequentially. This selection determines which steps need to be performed during the ETL process. Each fact group belongs to a specific functional area or areas that are associated with one or more offerings, which, in turn, are related to a data server. A transactional data source is associated with one or more data servers.Īfter you define the load plan, you then generate it to build it in the ODI repository. You then execute the load plan to perform the ETL process.įor more information about working with Oracle BI Applications load plans, see Chapter 2, "Managing Load Plans." For information about the topic of load plans in the context of Oracle Data Integrator, see Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator. Oracle BI Applications has two ETL modes for loading data into the Oracle Business Analytics Warehouse: full and incremental.ĭuring a full load, Oracle BI Applications extracts:Īll records from tables that are sources for dimension tables. Records created after an "Initial Extract Date" from tables that are sources for fact tables. The Initial Extract Date defines a cut-off so that not all records are loaded into the data warehouse. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |