Sunteți pe pagina 1din 8
Shahed Munir & Krishna Mohan, UK - England Generating a custom Load Plan for Custom

Shahed Munir & Krishna Mohan, UK - England

Generating a custom Load Plan for Custom Sources for a cleaner finish in OBIA with ODI

OBIA 11.1.1.8.1 11.1.1.7.1 WITH ODI (Oracle Data Integrator)

– 11.1.1.7.1 WITH ODI (Oracle Data Integrator) This Document is written by Shahed Munir and Krishna

This Document is written by Shahed Munir and Krishna Mohan of Deliver BI

Public Release Date: 01st September 2014

Version: 1.0

Table of Contents

Description Of Change

2

BIACM Config

2

Step 1: Creation of Custom Offering

2

Step 2: Creation of Source for the new offering

2

Step 3: Creation of Custom Functional Area

2

Step 4: Creation of relation between Offering and Functional Area

3

Step 5: Creation of fact group (Repeat for each Fact Group)

3

Step 6: Creation of Func Area to Fact Group Relation (Repeat for each Fact Group)

3

Linking BIACM Fact Groups to ODI Objects

4

Fact Model / Dimension Model

4

Load Plan Steps (provided only for SILs, but SDE steps will be the same)

5

Dev Components

5

Load Plan System Component (Required for a New Fact Group or Dim Group)

7

Generate the Custom Load Plan in BIACM

8

Description of Change

Description of Change Shahed Munir & Krishna Mohan, UK - England The creation of new offerings

Shahed Munir & Krishna Mohan, UK - England

The creation of new offerings or fact groups for BIACM load plans cannot be achieved using the out of box OBIA product. Here is the workaround.

Follow the steps below to create Custom Offering with custom facts and dimensions. This offers the flexibility to create load plans that are completely independent to out of box load plans. This approach also offers the capability to run custom plans at different frequency to OBIA out of the box plans

Offering Function Areas Fact Groups which then link to Dimension Groups

BIACM Config

Either run the samples below or you can use the working scripts in Load Plan Scripts 1 to 6 to generate the custom offering and fact groups. The scripts have been tested. The below samples are a guide. The fact Groups can be extended to support multiple sources or feeds. The Load Plan scripts are in a Zip file on our Box server in the same location as this document and will fall in line with the screen shot examples given in this document.

Step 1: Creation of Custom Offering

insert into c_bia_offering values

(0,'XXDBI_CUSTOM_OFRNG','XXDBI_CUSTOM_OFRNG','Deliver BI Custom Analytics',NULL,

1,'XXDBI','01-JAN-2014','BIApps','01-JAN-2014',-1);

Step 2: Creation of Source for the new offering

insert into c_bia_offering_ds_type_rel values

(null,'XXDBI_CUSTOM_OFRNG','EBS_12_1_3','BIApps','01-JAN-2014','BIApps','01-JAN-2014',-1);

Step 3: Creation of Custom Functional Area

insert into c_functional_area values

(0,'XXDBI_OFFER1','XXDBI_OFFER1','Deliver BI Functional Area 1,null,1,'BIApps','01-JAN-

2014','BIApps','01-JAN-2014',-1);

insert into c_functional_area values

Shahed Munir & Krishna Mohan, UK - England (0,'XXDBI_OFFER2', 'XXDBI_OFFER2','Deliver BI

Shahed Munir & Krishna Mohan, UK - England (0,'XXDBI_OFFER2', 'XXDBI_OFFER2','Deliver BI Functional Area 2',null,1,'BIApps','01-JAN-

2014','BIApps','01-JAN-2014',-1);

Step 4: Creation of relation between Offering and Functional Area

insert into c_bia_offering_funcarea_rel values

(0,'XXDBI_CUSTOM_OFRNG','XXDBI_OFFER1','BIApps','01-JAN-2014','BIApps','01-JAN-2014',-1);

insert into c_bia_offering_funcarea_rel values

(0,'XXDBI_CUSTOM_OFRNG','XXDBI_OFFER2','BIApps','01-JAN-2014','BIApps','01-JAN-2014',-1);

Step 5: Creation of fact group (Repeat for each Fact Group)

insert into c_fact_group values

(0, 'XXDBI_OFFER1_FG1', 'XXDBI_OFFER1_FG1','Deliver BI Functional Area 1 - Fact Group 1',null,null

,'BIApps','01-JAN-2014','BIApps','01-JAN-2014',-1);

Step 6: Creation of Functional Area to Fact Group Relation (Repeat for each Fact Group)

insert into c_funcarea_factgroup_rel values

(null, 'XXDBI_OFFER1','XXDBI_OFFER1_FG1','BIApps','01-JAN-2014','BIApps','01-JAN-2014',-1);

Shahed Munir & Krishna Mohan, UK - England Linking BIACM Fact Groups to ODI Objects

Shahed Munir & Krishna Mohan, UK - England

Linking BIACM Fact Groups to ODI Objects

Login to ODI Studio.

The following step lets ODI know the association between Offerings / Functional Areas (defined in BIACM) to the models and mappings that will be run as part of load plan

Fact Model / Dimension Model

When creating new FACT/Dimension Model (Table) carry out the following:

Navigation - Models --> Oracle BI Applications --> Oracle BI Applications --> Fact -->

The navigation above is just an indicator the flexfields can be applied directly do dimensions.

Pick the model and navigate to Flexfields tab

- Uncheck the Default checkbox against OBI Fact Group

- In the value field enter DRM_FG1 Or Whatever the fact group ID may Be.

enter DRM_FG1 – Or Whatever the fact group ID may Be. Foreign Key Reference must exist

Foreign Key Reference must exist on the Model table _D that requires loading. It can reference itself if need be. This is applied to a Dimension table so that the Load Plan will not errorSo if you don’t have a fact tabletreat the dimension table as a fact.

have a fact table … treat the dimension table as a fact. To make sure that

To make sure that the flexfields are populated correctly so that the load plan can pick up the interfaces. I like this piece of SQL if you have more than 1 model you can see if they all have the flexfield value filled ready for a custom load plan.

Shahed Munir & Krishna Mohan, UK - England This piece of sql can be executed

Shahed Munir & Krishna Mohan, UK - England

This piece of sql can be executed as BIACOMP User in the database (sqlplus or toad).

select distinct t.i_table,t.res_name from snp_table t, snp_ff_valuew ff

where t.i_table=ff.i_instance and ff.ff_code='OBI_FACT_GROUP' and short_txt_value in ('DRM_FG1')

Load Plan Steps (provided only for SILs, but SDE steps will be the same)

Dev Components The Scenarios for the Packages created will need to be added into new load plan steps.

SDE Mappings must be referenced from the SDE and relevant source container.

BIAPPS Load Plan --- > SDE --- > EBS_12_1_3

BIAPPS Load Plan --- >Load Plan Dev Components -- > SIL

In Designer go to Loan Plans and Scenarios

Navigate to: LOAD PLAN DEV COMPONENTS SIL

Navigate to: LOAD PLAN – DEV COMPONENTS – SIL Create a Load Plan Dev Step: Name

Create a Load Plan Dev Step:

Name of Load Plan Component :

3 SIL FAC DRM_FG1

Shahed Munir & Krishna Mohan, UK - England - Rename the root step to DRM_FG1

Shahed Munir & Krishna Mohan, UK - England

Shahed Munir & Krishna Mohan, UK - England - Rename the root step to DRM_FG1 or

- Rename the root step to DRM_FG1 or fact group name

Goto Steps Tab

- Add the scenario that needs to be executed.

- Remember to set the scenario version to -1 (Save the Step then go back into the Scenario step and change the version to -1). Steps have a version number of -1 as they are the 1 st packages that were created for the interfaces

the 1 s t packages that were created for the interfaces Add as many Steps as

Add as many Steps as you like for Dimensions or facts . Remember the Fact_group flexfield must be enabled on the models for the relevant steps created.

Shahed Munir & Krishna Mohan, UK - England Load Plan System Component (Required for a

Shahed Munir & Krishna Mohan, UK - England

Load Plan System Component (Required for a New Fact Group or Dim Group)

This step loads all object or steps within a Parent load plan step in dev components.

In Designer goto Loan Plans and Scenarios

Navigate to: BIAPPS Load Plan Load Plan System Components SIL 2 SIL Fact Group

Load Plan System Components  SIL  2 SIL Fact Group Then Navigate to: Root step

Then

Plan System Components  SIL  2 SIL Fact Group Then Navigate to: Root step 

Navigate to: Root step parallel PROC_Serial

Add Load Plan System Step

Note: This can be created directly under main parallel step but at the end of PROC Serial. Does not have to be a subjob of PROC_Serial. Just Right click OUT on the Step and Right Click and down

Basically create this step under PROC_SERIAL will be a neater finish like below screen shot.

PROC_SERIAL will be a neater finish like below screen shot. Create a step for $${3 SIL

Create a step for $${3 SIL FACT DRM_FG1}

Shahed Munir & Krishna Mohan, UK - England The Load Plan System step must contain

Shahed Munir & Krishna Mohan, UK - England

The Load Plan System step must contain the Load Plan Dev Component Parent step name in $${}

As shown in the above screen shots we have placed $$ ---> Eg:- $$(3 SIL Fact DRM_FG1 ) ---> So when the LPG generates the Final Load plan $$(3 SIL Fact DRM_FG1 ) would be replaced with the content inside it.

Once these steps have been completed then its time to Test the new Offering and Fact Group in BIACM

Generate the Custom Load Plan in BIACM

Login to BIACM

Create a New Load Plan SIL / PLP Only if there is no SDE Needed

Pick the Custom Offering and Fact Group that was created with the scripts 1-6 and Generate the Load plan.

was created with the scripts 1-6 and Generate the Load plan. As you can now see

As you can now see RX Custom Analytics has is its own offering and a custom fact group. This offering and load plan can be scheduled independently for custom source data.