OBIA 11.1.1.8.

1 of Contents
1.0

Introduction

2.0

OBIA 11G Architecture

3.0

OBIA 11G Installation & Configuration

4.0

BIACM

4.1 Overview

4.2 Configuring Source(OLTP) database

4.3 Configuring Target(OBAW) database

5.0

Manage Business Intelligence Applications

6.0

Manage Preferred Currencies and Languages

7.0

Functional Setup Manager

8.0

Manage Load Plans

9.0

Monitoring Load plans

9.1 ODI Studio

10

9.2 ODI Console

11

10.0 Trimming RPD

12

11.0 Loading RPD into OBIS

14

12.0 Loading Catalog into OBIPS

14

13.0 Understanding HR Analytics

14

14.0 Understanding Finance Analytics

15

15.0 About configuring accounts file

16

16.0 About configuring Segment file

16

17.0 OBAW Customization Overview

17

17.1 Category I Customization : Adding Columns to Existing Fact or Dimension Tables

17

17.2 Category 2 Customization : Adding Extra Dimension Table

20

1.0

Introduction

1. OBIA stands for Oracle Business Intelligence applications or BI Apps or OOB(Out

Of Box) work

2. OBIA 11G released by oracle with the combination of OBIEE 11G + ODI 11G in the
year of 2013

3. OBIA 11G OOB work not available with ODI12C

4. OBIA 11G works only with 64 bit OS
5. The versions available are OBIA 11.1.1.7.0/7.1/8.1/9.1/9.2
6. OBIA available with OBIEE 11G + INFORMATICA +DAC combination and those
versions are OBIA 7.9.6.4/3/2/1...etc

7. As part of the OBIA 11G installation we will get mainly three components
a. BIACM (Configuration Manager)
b. FSM (Functional Setup Manager)
c. ODI Console
2.0

OBIA 11G Architecture

Components Deployed Into Manager Server "bi_server1"

Oracle BI Applications Configuration Manager(OBIACM) - This component is a

Web application that enables you to perform system setups, functionally configure
your BI Applications, and define, generate, run, and monitor load plans.
Functional Setup Manager(FSM) - This component is a Web application used by
Configuration Manager for sequenced task implementation and task dependency
management.
Load Plan Generator - This component is a set of jar files used to create load plans
in the Oracle Data Integrator Repository.
ATGLite - This component is a J2EE component used by Oracle BI Applications
Configuration Manager and Functional Setup Manager.

Components Deployed Into Managed Server "odi_server1"

ODI Console - This component enables you to control and monitor ETL.
ODI Agent - This component is a Java EE Agent, which handles schedules and
orchestrates sessions.

Oracle BI Applications Repositories

Oracle Business Analytics Warehouse(OBAW) - The Business Analytics

Warehouse is a unified data repository for all customer-centric data, which supports
the analytical requirements of the supported source systems. The Business Analytics
Warehouse is supported only on Oracle Database.
Business Intelligence Applications Components Repository (BIACOMP) - This
is the repository for Configuration Manager and Functional Setup Manager. It
contains load plan definitions as well as BI Applications product hierarchy, setup
objects, such as parameters and domain mappings, and a list of functional tasks.
This repository is supported only on Oracle Database.
Business Intelligence Applications I/O Schema - This schema is a mirror schema
and is used by all other components to read the BIACOMP schema. It supports
read/write of configuration and functional setup data through ETL processes.
Oracle Data Integrator Repository for BI Applications - This repository contains
the BI Applications-specific prebuilt ETL logic.

Client Tier
The client host machine shows the Configuration Manager and Oracle Data Integrator
Console accessed through Web browsers. ODI Studio is installed on a developer client
machine. For BI Applications usage, ODI SDK must be installed along with ODI Studio.
Additional Tools
Golden Gate is an optional tool integrated with Oracle BI Applications. It enables you to
optimize ETL loads and reduce impact on the source system, using a source-dependent
data store(SDS).
ETL Architecture

3.0

SDE : SDE stands for Source Dependent Extract. In the first phase, SDE tasks
extract data from the source system and stage it in staging tables. SDE tasks are
source specific.
SIL: SIL stands for Source Independent Load. Load tasks transform and port the
data from staging tables to base fact or dimension tables. SIL tasks are source
independent.
PLP: PLP stands Post Load Process. PLP tasks are only executed after the
dimension and fact tables are populated. A typical usage of a PLP task is to
transform data from a base fact table and load it into an aggregate table. PLP tasks
are source independent.

OBIA 11G Installation & Configuration

1. Please refer my website rritec.com the link is OBIA 11.1.1.8.1 INSTALLATION

2. http://rritec.blogspot.in/2014/09/obia-111181-installation.html
4.0

BIACM

1. Go to console http:rritec:7001/console
2. provide username and password as weblogic and RRitec123
3. Click on Environment
4. Click on Servers Click on Control Select
Click on Yes wait till the state turned into running

5. Go to BIACM http://rritec:9704/biacm

Click on Start

6. BIACM stands for Business Intelligence Applications Configuration Manager

7. provide username and password as biapps and RRitec123

4.1

Overview

1. It is useful to understand previously configured system setups , Load plan

executions ,parameters of offerings and domain mappings of offerings
4.2

Configuring Source(OLTP) database

1. Default vision database installed with EBS installation , with the name of VIS
2. Apps user is a master user and will be able to communicate with all modules like
AP,AR,GL..etc

3. Make sure we are able to connect OLTP and DW databases

4. In Tasks pane under System Setups Click on Define Business Intelligence

Applications Instance

5. Click on Source Systems Tab Click on add

Select as shown below

6. Click on next
7. Under context details select context as global
8. Under connection details Provide below information

9. Click on test
10. Copy folder etl from C:\OBIEE_HOME\Oracle_BI1\biapps to
C:\OBIEE_HOME\Oracle_ODI1\oracledi

11. Click on technology :File system provide below info

12. Click on

4.3

Configuring Target(OBAW) database

1. This tab is configured already at the time of OBIA installation and configuration
2. Click on Target Warehouse observe OBAW schema name ,database name and
files path .

3. Click on Done
5.0

Manage Business Intelligence Applications

1. It is useful to select required applications like HR analytics ,Finance analytics ,sales

analytics ,price analytics, marketing analytics supply chain analytics ..etc

2. Under system setups Click on Manage Business Intelligence Applications

3. Select Human Resource analytics

4. Click on save Click on done

6.0

Manage Preferred Currencies and Languages

1. Click on Manage Preferred Currencies

2. Observe all parameters
3. Similarly Click on Manage Warehouse Languages and notice that America
language is selected

7.0

Functional Setup Manager

1. It is useful to configure required tasks such as domain values ,parameter vales ..etc
2. Click on Perform functional configuration Then FSM portal will open provide
username and password as biapps and RRitec123

3. Observe the application all options

Create Project
Click on Create provide name as
HRAnalytics click on next Enable include option for
Click on save and open project

1. Click on

2. Under Task expand

change required

parameters
Example1 : Configure Prune Days
Set how many days of data it has to read and reprocess in ELT loads

8.0

Manage Load Plans

1. Under Load plans Administration Click on Manage Load Plans Click on add
2. Any analytics need minimum two load plans
a. Domain loads
b. Data Loads
Domain loads

1. Enter the name as HR Domain Load Select Load plan type as Domain only
extract and load Source instance as VIS

2. Click on next Select as shown below save

3. Select the HR Domain Load Click on Generate

changed as

observe like status

After few mins it will show succeeded

4. Open ODI studio Under Load Plans and Scenarios Expand Generated Load
Plans open our load plan Right click on required step scenario and navigate
back using open linked object

5. Select HR Domain Load Click on execute Provide below info

6. Click on OK
9.0

Monitoring Load plans

1. We can monitor load plans in two ways

a. OODI Studio operator
b. ODI console

9.1

ODI Studio

1. Open ODI studio Click on connect and provide below details

2. Click on OK
3. open operator navigator
4. Expand Load Plan Execution All Execution

5. Right click on execution plan open click on steps and observe run status

9.2

ODI Console

1. It is useful to monitor ,debug,run,restart,change connection information ..etc

2. Go to portal http://rritec:15001/odiconsole
3. provide username and password as biapps and RRitec123

4. Click on sign in
5. Expand Runtime
6. Expand Session/load plans executions
7. Expand load plan executions
8. observe the status
9. if you want details then click on view option
10. Finally it should show succeeded

11. Similarly create and execute data load plan

Note you have to select load plan type as

10.0

Trimming RPD

1. Oracle BI Applications release 11.1.1.8.1 delivers a full RPD file with projects for all
the BI Applications modules. This full RPD is deployed to the BI Server. You can
trim the RPD so that it includes only the projects that are relevant to your
deployment. Although optional, trimming the RPD makes the BI Server startup
process faster and also makes patching quicker.

2. Run bi-init.cmd file from location

C:\OBIEE_HOME\instances\instance1\bifoundation\OracleBIApplication\coreapplica
tion\setup

3. In above command prompt type cd

C:\OBIEE_HOME\instances\instance1\bifoundation\OracleBIServerComponent\core
application_obis1\repository

4. Then prepare the file with required projects .

5. The list of projects in the 11.1.1.8.1 RPD includes the following:

ExtractProjects -B
C:\OBIEE_HOME\instances\instance1\bifoundation\OracleBIServerComponent\core
application_obis1\repository\OracleBIApps_BI0002.rpd -O
C:\OBIEE_HOME\instances\instance1\bifoundation\OracleBIServerComponent\core
application_obis1\repository\001OBIA.rpd -I "Financial Analytics Fusion Edition" -I
"Human Resources Analytics Fusion Edition"

6. paste this code in command prompt press enter

7. Then it will ask password of main OOB RPD ,provide as RRitec123
8. It will take around 5 mins ,once it completes ,we can find trimmed RPD in repository
location
C:\OBIEE_HOME\instances\instance1\bifoundation\OracleBIServerComponent\core
application_obis1\repository

11.0

Loading RPD into OBIS

1. Open RPD in offline mode

2. Change static repository variables values as OLAP_DSN ='ORCL' and
OLAP_USER='DEV_DW'

3. In physical layer expand Oracle Data Warehouse database object > double click
on connection pool Oracle Data Warehouse Connection Pool change the
password as RRitec123 and conform the password as RRitec123.

4. Similarly change other connection pool Oracle Data Warehouse Repository

Initblocks Connection Pool password

5. Save rpd
6. Using known process load this rpd into OBIS
7. Open RPD in online mode conform the OBIA RPD loaded or not
12.0

Loading Catalog into OBIPS

1. With installation of OBIA 11G catalog created in the folder catalog with the name of
OracleBIApps

2. Load this catalog into OBIPS

3. Open analytics and observe the obia catalog is loaded or not by observing
predefined dashboards and reports
13.0

Understanding HR Analytics

1. Go to Dashboards menu > Click on Human capital management >observe pre

defined dashboards

2. Click on Time and labor dashboard observe the data

3. Time and labor dashboard has star schemas
a. W_TLB_PRCSD_F (Fact - HR - Time and Labor - Processed Time)
i. W_TLB_TIMECARD_D
ii. W_HR_POSITION_D
iii. W_DAY_D
iv. W_INT_ORG_D
v. W_PAY_GRADE_D
vi. W_PAY_PAYROLL_D
vii. W_TLB_CONSUMER_D
viii. W_COMPA_RATIO_BAND_D
ix. W_BUSN_LOCATION_D
x. W_JOB_D
xi. W_INTL_ASSGN_D
xii. W_PRD_OF_WRK_BAND_D..etc
b. W_TLB_RPTD_F(Fact - HR - Time and Labor - Reported Time)
i. W_USER_D
ii. W_TASK_D ..etc

14.0

Understanding Finance Analytics

1. Go to Dashboards menu >

15.0

About configuring accounts file

1. Get proper version source file from ETL folder (example

C:\OBIEE_HOME\Oracle_BI1\biapps\etl\data_files\src_files\EBS_12_1_1\file_group
_acct_codes_ora)

2. This file has 4 columns

a. CHART OF ACCOUNTS ID
b. FROM ACCT
c. TO ACCT
d. GROUP_ACCT_NUM

3. The staging mapping name and table

a. SDE_ORA_Stage_GroupAccountNumberDimension.W_ORA_GROUP_AC
COUNT_NUM_D_TMP
b. W_ORA_GROUP_ACCOUNT_NUM_D_TMP
c. W_GL_ACCOUNT_DS

4. The warehouse mapping name and table

a. SIL_GLAccountDimension.W_GL_ACCOUNT_D
b. W_GL_ACCOUNT_D
16.0

About configuring Segment file

1. Get proper version source file from ETL folder (example

C:\OBIEE_HOME\Oracle_BI1\biapps\etl\data_files\src_files\EBS_12_1_1\
file_glacct_segment_config_ora)

2. This file has 4 columns

a. CHART OF ACCOUNTS ID
b. SEG1
c. SEG1_VALUESETID
d. etc

3. The staging mapping name and table

a. SDE_ORA_Stage_GLAccount_SegmentConfig_Extract.W_GLACCT_SEG_
CONFIG_TMPW_ORA_GROUP_ACCOUNT_NUM_D_TMP
b. W_GLACCT_SEG_CONFIG_TMP

c. SDE_ORA_GLAccountDimension.W_GL_ACCOUNT_DS
d. W_GL_ACCOUNT_DS

4. The warehouse mapping name and table

a. SIL_GLAccountDimension.W_GL_ACCOUNT_D
b. W_GL_ACCOUNT_D

17.0

OBAW Customization Overview

1. Customization Scenarios

2. Avoid the Impact of Patch Installation on Customization by Createing custom folders

to isolate the customizations .Example: Custom_SDE,Custom_SIL

17.1

Category I Customization : Adding Columns to Existing Fact or Dimension

Tables

1. Category 1 customizations involve extracting additional columns from source

systems for which pre-packaged adapters are included (for example, Oracle
eBusiness Suite) and loading the data into existing Oracle Business Analytics
Warehouse tables

2. Oracle Business Intelligence Applications recognizes two types of customization:

extension and modification. The supported extension logic allows you to add to
existing objects. For example, you can extract additional columns from a source,
pass them through existing mappings, and populate new columns added to an
existing table. Generally, Oracle Business Intelligence Applications does not allow
you to modify existing logic or columns. You should not change existing calculations
to use different columns, and you should not remap existing columns to be loaded
from different sources.

3. For example, if you want to calculate revenue differently from the existing logic, you
should create a new column (for example, X_REVENUE) and populate it with a
custom mapping expression. You can then remap the Oracle Business Intelligence

repository to point to the new X_REVENUE column.

4. Most data stores have a single placeholder column named X_CUSTOM. Each ETL
task has mapping expressions to populate this column. These serve as templates
for customizing ODI data stores and interfaces. When creating new custom
columns, follow the naming convention of including the X_ prefix to help distinguish
custom columns.

Process

1. Create new SDE and SIL Adaptor folders (do not copy existing Adaptor folder as
this will copy all subfolders). Rename folders to include 'Custom' or some other
useful identifier in the name, and set Release Tag to match that of the existing
Adaptor folder. Do this for both the SDE and SIL folders.
i. Go to Designer navigator Expand BI Apps Project
ii. Right Click on Mappings folder Create a new sub folder with the
iii.

iv.
v.
vi.
vii.
viii.

name of Custom_SIL
Similarly create folders with the name of Custom_SDE ,Custom_PLP
Click the Connect Navigator button in the Designer tab Select Edit
Release Tags.
Select the release tag that corresponds to your source. For example,
EBS_12_1_1
Select the custom_SDE folder you created and add it to the release
tag.
Click NextClick Finish.
Repeat the above steps(4th to 7) for the CUSTOM_SILOS and
Custom_PLP folder, associating it with the BIA_11 Release Tag.

2. Enable versioning for the preconfigured Task Folder to be customized. The version
comment should indicate this is the base version of the task. Subsequent patches
applied to this task in the future would require increasing the version in the comment
so that it can be compared to the original task to identify any changes.

1. Right-click the Task folder SILOS and select Version > Create Version.
2. Accept the default version number, 1.0.0.0.
3. Add a description indicating that this is the original version of this task
3. Duplicate the Task folder SIL_AbsenceEventDimension to be customized by
copying it.

4. Cut and paste the copied task folder to the Custom adaptor Custom_SIL and
rename it by removing the 'Copy of' prefix.

5. Using the same method as in step 2, enable versioning of copied Task folder. The
version comment should indicate this is the original version. This versioning enables
comparison of the customized task to a copy of the original version to determine all
changes that have been introduced.

6. Create another version of the copied task. The version comment should indicate this
is the customized version. Use the same steps as above.

7. Version the Model that the data stores to be customized exists in, for example,
Oracle BI Applications. Sub models and data stores cannot be versioned. The
version comment should indicate this is the base or original version.

8. Create a new version of the model, with a version comment indicating that this is
where customizations are introduced. The models can now be compared to show
differences. If the model ever needs to be patched, the model should be versioned
again so that the patched version can be compared to the custom and original
version.

9. Apply customizations to the datastore and task. Customizations should be additive

as much as possible rather than overwriting existing content. For example, if you
don't like the way a particular column is calculated, add a new custom column and
map it in the way you prefer. In the RPD, have the logical column point to this new
custom column rather than the original column.
a. Connect to schema DEV_DW and add the column
Alter table W_ABSENCE_EVENT_D add X_RRITEC_Load_Date date
b. Expand Models Expand Oracle BI Applications Expand Dimensions
c. Open table Absence Event Dimension (W_ABSENCE_EVENT_D) go to
Columns tab click on add and name it as X_RRITEC_Load_Date and
select data type as date
d. Open the interface SIL_AbsenceEventDimension.W_ABSENCE_EVENT_D
from folder Custom_SIL / SIL_AbsenceEventDimension
e. Select X_RRITEC_Load_Date column and write the expression as sysdate
f.

Save close

10. Prior to generating scenarios, ensure the 'Scenario Naming Convention' User
Parameter has a value of %FOLDER_NAME(2)%_%OBJECT_NAME%
a. Go to ODI menu Click on user Parameters then make sure below
syntax

11. Delete the scenario associated with the original task and generate a new scenario
for the custom task using the same scenario name as the original. ODI enforces
unique scenario names, so you should use the same scenario name for the custom
task so that the load plan executes this ETL task rather than the original ETL task.

1. Expand SILOS Expand SIL_AbsenceEventDimension Expand

packages Expand SIL_AbsenceEventDimension Expand Scenarios
delete the scenario SILOS_SIL_ABSENCEEVENTDIMENSION

2. Navigate to the folder Custom_SIL / SIL_AbsenceEventDimension

expand packages Right click on package SIL_AbsenceEventDimension
Click on generate scenario and name it as
SILOS_SIL_ABSENCEEVENTDIMENSION and keep the version number as
001
3. Check the Generate scenario as if all underlying objects are materialized
4. Checkbox Click OK. Select Use All from the Startup Parameters dropdown Click OK.
5. When you execute the load plan, it now executes the custom task rather than
the original task. In the future if you make changes to any of the interfaces or
the package, you can either regenerate the existing scenario or generate a
new scenario. Unless you need separate scenarios, it is recommended that
you regenerate the existing scenario. To do this, right-click the scenario and
select Regenerate.
12. Execute the Load Plan.
a. Expand Load Plans and Scenarios Expand BIAPPS Load Plan Expand
Load Plan Dev Components Expand SIL open 3 SIL Dims
ABSEVT_DIM observe it by doing reverse engineering and run it .
17.2

Category 2 Customization : Adding Extra Dimension Table

1. STEP 1: Create custom table in database and import into ODI

a. Make a copy of W_ABSENCE_EVENT_D and name it as
WC_ABSENCE_EVENT_D
b. Open oracle BI Application model provide mask as WC% import the table
WC_ABSENCE_EVENT_D

2. STEP2: Move table to proper folder

a. Drag and drop this table onto dimension sub model

3. Step3 : Using Custom table create interface

4. Step4 : Create a package
5. Step 5 : Create Scenario on the package
6. Step 6: Add this scenario to custom load plan