Oracle BI Application Setup & Configuration V1.4

Oracle BI Application Setup and Configuration Roadmap
Document ID:
Release Date:
Oracle BI Application Setup & Configuration

29-Mar-13
Change History
Author
Parag Devdas, Amar Shirke, Rahul
Ranade
Version No.
V1.0
Date
29-Mar-13
V1.1
16-Apr-2013

Ranade
V1.2
26-Apr-2013

Ranade
V1.3
2-May-13

Ranade
V1.4
8-May-13

Ranade
Note: This template has been designed considering source as Oracle EBS R12 and Target as Oracle Databas
on Roadmap
& Configuration
Change History
Overview Of Changes
-
Authorised By
Added Pre-requisites for OBIA

Added Financial Analytics Template
Added SCM-OM Analytics Template & Comment
Addressed
Added Procurement & Spend Analytics Template
EBS R12 and Target as Oracle Database/DWH
Navigate to Index
e to Index
Oracle Business Application 7.9.6.4
Configuration of Oracle BI Appli

1.1
1.2
1.3
Oracle BI Application Setup

Pre-requisites for OBIA
Oracle BI Application Directory Structure
Deployed Component URL's
1.4
General Recommendation
2
2.1
2.2
2.3
Post Installation System Configuration

Informatica Configuration
DAC Configuration
OBIEE Configuration
3
3.1
3.2
4
Configuring Common Areas and Dimensions

DAC
Informatica
Configuring Functional Areas
4.1
Oracle Human Resource Analytics
4.2
Oracle Financial Analytics
4.3
Oracle Supply Chain & Order Management Analytics
4.4
Oracle Procurement & Spend Analytics
guration of Oracle BI Application

Link To Navigate
Status
Click here
Click here
Click here
Click here
Link To Navigate
Status
Click here
Click here
Click here
Link To Navigate
Status
Click here
Click here
Embedded Object
Status
Comment
Comment
Comment
Comment
Double click this icon to open the Analytics Specific
configuration

configuration

configuration

configuration
NA
Completed
Pending
WIP
Back To Index
Pre-requisites for OBIA 7.9.6.4

This section covers required Pre-requisite for setting up Oracle BI Application environment
Sr. Number
Configuring Informatica PowerCenter Components
List of Software to be install for OBIA 7.9.6.4
Hardware Matrix
Required Database Schemas for OBIA Components
Creation of Users, Table space, SSE Role and DB Privileges
Data Sources and Associated DATASOURCE NUM ID Values
Code Page and Data Movement requirement
Maintenance/Service Account
Sr# 1:
List of Softwares to be install for OBIA 7.9.6.4:

Component Name
OBAW
Oracle Database Client
Version
Oracle Database 11g Release 2 (11.2.0.1.0) for Microsoft Windows x6
(64-bit) (Part 1 of 2)
Oracle Database 11g Release 2 (11.2.0.1.0) for Microsoft Windows x6

(64-bit) (Part 2 of 2)
Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft
Windows x64 (64-bit)
Oracle Business Intelligence Data Warehouse Administration Console

11g and Informatica PowerCenter and PowerConnect Adapters 9.1 fo
Windows x86 (64-bit) (Part 1 of 4)

DAC & Informatica
PowerCenter(Client and Server)


Repository Creation Utility (11.1.1.7.0) for Microsoft Windows (64-bit

RCU for OBIEE 11g
Oracle Business Intelligence, v. 11.1.1.7.0
OBIEE 11g
Oracle Business Intelligence Applications 7.9.6.4 for Microsoft
Windows
BI APPS 7.9.6.4
OBIEE 11g Client Tool
Oracle Business Intelligence Developer Client Tools Installer

(11.1.1.7.0) for Microsoft Windows x86 (64-bit)
JDK: 1.7.0_07+ (64 bit) or 1.6.0_35+ 64
JDK
Oracle Business Intelligence Applications Licensing and Packaging

Guide 7.9.6.4
Documentation
Oracle Business Intelligence Enterprise Edition 11g Release 1

(11.1.1.7)
Sr# 2:
Hardware Matrix:
Hardware recommendations for Oracle BI Applications
Configuration
SMALL
Target Tier
Target Volume
Up to 200 Gb
# CPU cores
16
Physical RAM
32-64 Gb
Storage Space
Up to 400 Gb
Storage System
Local (PATA, SATA, iSCSI), or

NAS, preferred RAID
configuration
Oracle BI Enterprise Edition / ETL Tier

# CPU cores
Physical RAM
Storage Space
8
8 Gb
100 Gb local
Notes:
Consider implementing Oracle RAC with multiple nodes to accommodate large numbers of concurrent use
To ensure the queries scalability on OBIEE tier, consider implementing OBIEE Cluster or Oracle Exalytics.
It is recommended to set up all Oracle BI Applications tiers in the same local area network. Installation o
execution in the overall ETL window.
Sr# 3:
Required Database Schemas for OBIA Components:

Target Data Volume
Data Warehouse Size
Temporary Tablespace
DATA Tablespace
INDEX Tablespace
Oracle Business Analytics Warehouse Tablespaces

SMALL
Up to 200 Gb
50 75 Gb
150 Gb
50 Gb
Note : You should use Locally Managed tablespaces with AUTOALLOCATE clause. DO NOT use UNIFORM ext
Schema Required For

OBIEE Repository
Schema Name
DEV_MDS
DEV_BIPLATFORM
OBIA Datamarts
DEV_TGT_DW
Informatica Repository
DEV_INFO_REPO
DAC Repository
DEV_DAC_REPO
Schema Required For

OBIEE Repository
Schema Name
TEST_MDS
TEST_BIPLATFORM
OBIA Datamarts
TEST_TGT_DW
Informatica Repository
TEST_INFO_REPO
DAC Repository
TEST_DAC_REPO
Sr# 4:
Creation of Users, Table Space, SSE Role and DB Privileges:

Before we install Oracle BI Application, we need to create database instance for following components:
1. OBIEE Repository
2. DAC Repository
3. Informatica Repository
4. Oracle Business Analytics Warehouse
Also, OBIEE Repository Schema can be created using repository creation utility (RCU).
Create SSE Role Script needs to be executed by system user
CREATE ROLE SSE_ROLE;
GRANT CONNECT TO SSE_ROLE;

GRANT RESOURCE TO SSE_ROLE;
GRANT SELECT ANY TABLE TO SSE_ROLE;
GRANT INSERT ANY TABLE TO SSE_ROLE;
GRANT UPDATE ANY TABLE TO SSE_ROLE;
GRANT DELETE ANY TABLE TO SSE_ROLE;
GRANT GRANT ANY OBJECT PRIVILEGE TO SSE_ROLE;
GRANT GRANT ANY PRIVILEGES TO SSE_ROLE;
create
create
create
create
create
tablespace
tablespace
tablespace
tablespace
tablespace
CREATE
CREATE
CREATE
CREATE
CREATE
USER DEV_MDS IDENTIFIED BY lntpoc123 DEFAULT tablespace DEV_MDS_TS TEMPORARY ta

USER DEV_BIPLATFORM IDENTIFIED BY lntpoc123 DEFAULT tablespace DEV_BIPLATFORM_TS TEMPO
USER DEV_INFO_REPO IDENTIFIED BY lntpoc123 DEFAULT tablespace DEV_INFO_REPO_TS TEMPOR
USER DEV_DAC_REPO IDENTIFIED BY lntpoc123 DEFAULT tablespace DEV_DAC_REPO_TS TEMPOR
USER DEV_TGT_DW IDENTIFIED BY lntpoc123 DEFAULT tablespace DEV_TGT_DW_TS TEMPORA
GRANT CONNECT,
GRANT CONNECT,
GRANT CONNECT,
GRANT CONNECT,
Page Up
DEV_MDS_TS datafile 'DEV_MDS_TS.dbf' size 500m autoextend on next 100m maxsize 10

DEV_BIPLATFORM_TS datafile '\DEV_BIPLATFORM_TS.dbf' size 500m autoextend on next
DEV_INFO_REPO_TS datafile '\DEV_INFO_REPO_TS.dbf' size 500m autoextend on next 10
DEV_DAC_REPO_TS datafile '\DEV_DAC_REPO_TS.dbf' size 500m autoextend on next 100
DEV_TGT_DW_TS datafile '\DEV_TGT_DW_TS.dbf' size 2000m autoextend on next 100m
resource TO DEV_MDS ;
resource TO DEV_BIPLATFORM ;
resource TO DEV_INFO_REPO ;
resource TO DEV_DAC_REPO ;
GRANT CONNECT, resource, CREATE VIEW TO DEV_TGT_DW;

GRANT SSE_ROLE TO DEV_TGT_DW, DEV_MDS,DEV_BIPLATFORM,DEV_INFO_REPO,DEV_DAC_REPO;
Sr# 5:
Data Sources and Associated DATASOURCE_NUM_ID Values:

Data Source Name
JDE_8_11_SP1_CTRL
JDE_8_11_SP1_DATA
JDE_8_11_SP1_DD
JDE_8_11_SP1_FlatFile
JDE_8_11_SP1_SYS
JDE_8.12_CTRL
JDE_8.12_DATA
JDE_8.12_DD
JDE_8_12_FlatFile
JDE_8.12_SYS
JDE_9.0_CTRL
JDE_9.0_DATA
Data Source Number
17
15
25
JDE_9.0_DD
JDE_9_0_FlatFile
JDE_9.0_SYS
JDEW_9_2_CTRL
JDEW_9_2_DATA
JDEW_9_2_DD
JDEW_9_2_FlatFile
JDEW_9_2_SYS
ORA_11_5_8
ORA_11_5_8_Flatfile
ORA_11_5_9
ORA_11_5_9_Flatfile
ORA_11_5_10
ORA_11_5_10_Flatfile
ORA_R12
ORA_R12_Flatfile
ORA_R1211
ORA_R1211_Flatfile
ORA_R1212
ORA_R1212_Flatfile
ORA_R1213
ORA_R1213_Flatfile
PSFT_8_4_FINSCM
PSFT_8_4_FlatFile
PSFT_8_8_FINSCM
PSFT_8_8_FlatFile
PSFT_8_8_HCM
PSFT_8_9_FINSCM
PSFT_8_9_FlatFile
PSFT_8_9_HCM
PSFT_8_9_HCM_FlatFile
PSFT_9_0_ELM
PSFT_9_0_HCM
PSFT_9_0_FINSCM
PSFT_9_0_FlatFile
PSFT_9_1_ELM
PSFT_9_1_HCM
PSFT_9_1_FINSCM
PSFT_9_1_FlatFile
SEBL_63
SEBL_6_3_Flatfile
SEBL_753
SEBL_7_5_3_Flatfile
25
24
2
5
4
9
26
27
1000
7
8
6
11
10
12
13
28
29
SEBL_771
SEBL_7_7_1_Flatfile
SEBL_78
SEBL_7_8_Flatfile
SEBL_80
SEBL_8_0_Flatfile
SEBL_811
SEBL_8_1_1_Flatfile
SEBL_VERT_753
SEBL_VERT_7_5_3_Flatfile
SEBL_VERT_771
SEBL_VERT_78
SEBL_VERT_7_8_Flatfile
SEBL_VERT_80
SEBL_VERT_80_Flatfile
SEBL_VERT_811
Maximo_75
UNIV
30
3
Sr# 6:
Code Page and Data Movement Requirement

1. Globalization Overview:
Informatica can process data in different languages. Some languages require single-byte data, while othe
a) Locale: Informatica requires that the locale settings on machines that access Informatica applications
language, territory, encoding of character set, and collation order.
b) Data Movement Mode: The PowerCenter Integration Service can process single-byte or multibyte data
movement mode for multibyte data.
c) Code Pages: Code pages contain the encoding to specify characters in a set of one or more languages.
movement, you must ensure compatibility among code pages for Informatica and environment componen
characters.
The PowerCenter Integration Service and PowerCenter Client code pages must be subsets of t
use the system code pages of the machines they are installed on, you must verify that the system code pa
For accurate data movement, the target code page must be a superset of the source code pa
process all characters, resulting in incorrect or missing data.
2) Code Page Compatibility Summary:
The following table summarizes code page compatibility between sources, targets, repositories, the Adm
Component Code Page
Code Page Compatibility
Source (including relational, flat

file, and
XML file)
Subset
Subset
Subset
Subset
of
of
of
of
Target (including relational, XML

files, and
flat files)
Superset of source.
Superset of lookup data.
Superset of stored procedures.
Superset of External Procedure or Custom transformation procedure
PowerCenter Integration Service process creates external loader dat
flat file code page.
Lookup and stored procedure

database
Subset of target.
Superset of source.
External Procedure and Custom

transformation procedures
Subset of target.
Superset of source.
Domain Configuration Database
Compatible with the PowerCenter repository.

Compatible with the Metadata Manager repository.
PowerCenter Integration Service

process
Compatible with its operating system.

Subset of the PowerCenter repository.
Subset of the Metadata Manager repository.
Superset of the machine hosting pmcmd.
Identical to other nodes running the PowerCenter Integration Service
PowerCenter repository
Compatible with the domain configuration database.

Superset of PowerCenter Client.
Superset of the nodes running the PowerCenter Integration Service p
Superset of the Metadata Manager repository.
A global PowerCenter repository code page must be a subset of a loc
PowerCenter Client
Machine running pmcmd
Machine running pmrep
Administrator Tool
Subset
Subset
Subset
Subset
Subset
Metadata Manager repository
Compatible with the domain configuration database.

Subset of the PowerCenter repository.
Superset of the Administrator tool.
Superset of the PowerCenter Integration Service process.
of
of
of
of
of
target.
lookup data.
stored procedures.
External Procedure or Custom transformation procedure co
the
the
the
the
the
PowerCenter repository.
PowerCenter Integration Service process.
Metadata Manager repository.
3)Character Data Movement Modes:

1. ASCII: The US-ASCII code page contains a set of 7-bit ASCII characters and is a subset of other characte
byte.
2. Unicode: The universal character-encoding standard that supports all languages. When the PowerCent
Integration Service runs in Unicode data movement mode, it allots up to two bytes for each character. Ru
Note: You can also use ASCII or Unicode data movement mode if the source has 8-bit ASCII data. The Powe
performance, use the ASCII data movement mode. For example, if the source contains characters from th
Requirement
Source Code Page
Target Code Page
Required Data Movement Mode
Sr# 7:
Maintenance/Service Account:
Service Account: This account will be use to Install, configure and development of all BI Components inc
Maintenance Account: This account is use for executing online project activity including monitor and ex
These accounts needs to be created for:
1. OBIEE Instance
2. Informatica & DAC Server Instance
3. DB Servers
4. Remote Desktops
Application environment
ng Informatica PowerCenter Components
Status
Comment
be install for OBIA 7.9.6.4
Schemas for OBIA Components
Table space, SSE Role and DB Privileges
ssociated DATASOURCE NUM ID Values
a Movement requirement
ce Account
7.9.6.4:
Version
g Release 2 (11.2.0.1.0) for Microsoft Windows x64
)
Part Number
Size
V20610-01 Part 1 of 2
1.2G
g Release 2 (11.2.0.1.0) for Microsoft Windows x64

)
V20610-01 Part 2 of 2
961M
V20609-01
587M
elligence Data Warehouse Administration Console

a PowerCenter and PowerConnect Adapters 9.1 for
t) (Part 1 of 4)
V35747-01 Part 1 of 4
1.1G

t) (Part 2 of 4)
V35747-01 Part 2 of 4
2.0G

t) (Part 3 of 4)
V35747-01 Part 3 of 4
2.0G

t) (Part 4 of 4)
V35747-01 Part 4 of 4
2.0G
g Release 2 Client (11.2.0.1.0) for Microsoft

t)
n Utility (11.1.1.7.0) for Microsoft Windows (64-bit)

325M
elligence, v. 11.1.1.7.0
Disk 1 (1of2)
Disk 1 (2of2)
Disk 2 (1of2)
Disk 2 (2of2)
1.7G
1.4G
1.8G
1.7G
V35873-01
559M
elligence Applications 7.9.6.4 for Microsoft
elligence Developer Client Tools Installer

rosoft Windows x86 (64-bit)
204M
bit) or 1.6.0_35+ 64
elligence Applications Licensing and Packaging
elligence Enterprise Edition 11g Release 1
V35866-01
48K
E28280-01
2.7G
commendations for Oracle BI Applications

MEDIUM
LARGE
Target Tier
Comment
200 Gb to 1 Tb
1 Tb and higher
32
64*
64-128 Gb
256+ Gb*
400 Gb 2 Tb
2T b and higher
Depending on the number of planned concurrent u

you may have to plan for more memory on the tar
the queries workload.
High performance SCSI or SAN with 16 High performance SCSI or SAN

Gbps HBA or higher, connected over
with 24 Gbps HBA or higher,
fiber channel / 2xGb Ethernet NIC
connected over fiber channel /
2xGb Ethernet NIC
le BI Enterprise Edition / ETL Tier
Comment
16
32
16 Gb
32 Gb
200 Gb local
400 Gb local
Specification depends upon data size and Number

Disclaimer: Hardware should be consulted with Or
to accommodate large numbers of concurrent users accessing web reports and dashboards.
implementing OBIEE Cluster or Oracle Exalytics.
ers in the same local area network. Installation of any of these three tiers over Wide Area Network (WAN) may cause additional delays d
omponents:
siness Analytics Warehouse Tablespaces

MEDIUM
200 Gb to 1 Tb
75 300 Gb
150 800 Gb
50 200 Gb
LARGE
1 Tb and higher
150 250Gb
> 800 Gb
> 200 Gb
AUTOALLOCATE clause. DO NOT use UNIFORM extents size, as it may cause excessive space consumption and result in queries slower per
Oracle Development Environment

Host:Port:Service
Notes
This schema required for
metadata services
This schema required for BI

Platform
Size Required
5 GB
5 GB
Schema required for holding

datawarehouse objects and data
150 GB
For holding informatica repository

object and data
5 GB
For holding DAC repository

objects and data
5 GB
Oracle Test Environment

Host:Port:Service
le and DB Privileges:
te database instance for following components:
ository creation utility (RCU).
Notes
This schema required for
metadata services
This schema required for BI
Platform
Schema required for holding
datawarehouse objects and data
Size Required
5 GB
5 GB
300 GB
For holding informatica repository

object and data
5 GB
For holding DAC repository

objects and data
5 GB
bf' size 500m autoextend on next 100m maxsize 1000m;

IPLATFORM_TS.dbf' size 500m autoextend on next 100m maxsize 1000m;
FO_REPO_TS.dbf' size 500m autoextend on next 100m maxsize 2000m;
C_REPO_TS.dbf' size 500m autoextend on next 100m maxsize 2000m;
DW_TS.dbf' size 2000m autoextend on next 100m maxsize 5000m;
FAULT tablespace DEV_MDS_TS TEMPORARY tablespace temp quota unlimited ON users;

DEFAULT tablespace DEV_BIPLATFORM_TS TEMPORARY tablespace temp quota unlimited ON users;
DEFAULT tablespace DEV_INFO_REPO_TS TEMPORARY tablespace temp quota unlimited ON users;
DEFAULT tablespace DEV_DAC_REPO_TS TEMPORARY tablespace temp quota unlimited ON users;
DEFAULT tablespace DEV_TGT_DW_TS TEMPORARY tablespace temp quota unlimited ON users;
TFORM,DEV_INFO_REPO,DEV_DAC_REPO;
RCE_NUM_ID Values:
ement
me languages require single-byte data, while other languages require multibyte data. To process data correctly in Informatica, you must
on machines that access Informatica applications are compatible with code pages in the domain. You may need to change the locale sett
tion order.
Service can process single-byte or multibyte data and write it to targets. Use the ASCII data movement mode to process single-byte data
cify characters in a set of one or more languages. You select a code page based on the type of character data you want to process. To en
pages for Informatica and environment components. You use code pages to distinguish between US-ASCII (7-bit ASCII), ISO 8859-1 (8-bit A
werCenter Client code pages must be subsets of the PowerCenter repository code page. Because the PowerCenter Client and PowerCent
talled on, you must verify that the system code pages are subsets of the PowerCenter repository code page.
de page must be a superset of the source code page. If the target code page is not a superset of the source code page, the PowerCenter
data.
y between sources, targets, repositories, the Administrator, tool, PowerCenter Client, and PowerCenter Integration Service process:
Code Page Compatibility
ata.
ocedures.
Procedure or Custom transformation procedure code page.
data.
procedures.
al Procedure or Custom transformation procedure code page.
ation Service process creates external loader data and control files using the target
e PowerCenter repository.
e Metadata Manager repository.
s operating system.
rCenter repository.
data Manager repository.
chine hosting pmcmd.
nodes running the PowerCenter Integration Service processes.
e domain configuration database.

enter Client.
des running the PowerCenter Integration Service process.
tadata Manager repository.
er repository code page must be a subset of a local PowerCenter repository.
rCenter repository.
rCenter Integration Service process.
rCenter repository.
rCenter repository.
data Manager repository.
e domain configuration database.

rCenter repository.
ministrator tool.
werCenter Integration Service process.
ASCII characters and is a subset of other character sets. When the PowerCenter Integration Service runs in ASCII data movement mode, e
that supports all languages. When the PowerCenter

e, it allots up to two bytes for each character. Run the PowerCenter Integration Service in Unicode mode when the source contains mult
mode if the source has 8-bit ASCII data. The PowerCenter Integration Service allots an extra byte when processing data in Unicode data
xample, if the source contains characters from the ISO 8859-1 code page, use the ASCII data movement.
Values
nfigure and development of all BI Components including OBIEE/Informatica/DAC/OBAW. Basic purpose of this account is to serve BI Apps
g online project activity including monitor and execute ETL process. Basic purpose of this account is to maintain the BI Apps enviroment
AC Server Instance
Exception
*Oracle Database 11.2.0.1 requires Patches 9739315 and 9255542 to be
applied for the Oracle Business Analytics Warehouse.
* Installer is available for only Microsoft Windows x86 (32-bit). If BI

installation is on Linux machine, then firstly BI Apps need to be installed on
Windows machine and then transfer the respective BI Apps files to
Middleware directory.
OBIEE 11.1.1.7.0 (Simple Install and Enterprise Install) installs default

Oracle WebLogic Server 10.3.5 which is certified with JDK version 1.6.0_35+
64. whereas if you choose for Software Only install you can install weblogic
server version 10.3.6 which supports JDK version 1.7.0_07+ 64
Note: 1) JDK 7 certification is available only with WLS 10.3.6+/FMW
11.1.1.6+.
2) JDK 6 certification is available only with WLS 10.3.1-10.3.5/FMW
11.1.1.1.0 - 11.1.1.5.0.
Comment
of planned concurrent users, running OBIEE reports,

more memory on the target tier to accommodate for
Comment
n data size and Number of Application Users.

ld be consulted with Oracle.
use additional delays during ETL Extract mappings
ult in queries slower performance.
TNS Names Entry
Comments
For creation of this schema sys
password is required hence DBA
help is required.
Schema or new database instance

will be required Along, with the
connect and resource. *
Disclaimer: Schema size may vary
based on Customer Source system
data size and data retentioning
DWH
TNS Names Entry
Comments
For creation of this schema sys
password is required hence DBA
help is required.
Schema or new database instance

will be required.
Informatica, you must set up the following items:
o change the locale settings. The locale specifies the
process single-byte data. Use the Unicode data
want to process. To ensure accurate data

CII), ISO 8859-1 (8-bit ASCII), and multibyte
r Client and PowerCenter Integration Service each
page, the PowerCenter Integration Service may not
on Service process:
data movement mode, each character requires one
he source contains multibyte data.
g data in Unicode data movement mode. To increase
ount is to serve BI Apps environment
the BI Apps enviroment.
NA
Completed
Pending
WIP
Back To Index
Summary of Oracle Home Locations for the components in Oracle BI Applicati

Oracle Home Directory
DAC_HOME
INFA_HOME
MW_HOME
DOMAIN_HOME
ORACLE_HOME
ORACLE_INSTANCE
Installed BI Apps 7.9.6.4 Directory Structure :
Note: From BI Apps installation, files and directories need to be transferred to OBIEE 11g, Informatica and D
OBIEE 11g Instance
OracleBIAnalyticsApps.rpd
EnterprisebusinessAnalytics.rpd
EnterpriseBusinessAnalytics.zip
system-jazn-data.xml
EnterpriseBusinessAnalytics.ldif
Installed OBIEE 11.1.1.7.0 Directory Structure :
Note: Below listed BI Apps files must be copied from BI Apps installable direcotry to Middleware.
File/Directory Name
OracleBIAnalyticsApps.rpd
EnterprisebusinessAnalytics.rpd
EnterpriseBusinessAnalytics.zip
system-jazn-data.xml
EnterpriseBusinessAnalytics.ldif
Installed Informatica 9.1 HotFix 2 Directory Structure :
Page Up
Page Up
File/Directory Name
Oracle_BI_DW_Base.rep
SrcFiles-CSV files
LkpFiles-CSV files
Enable communication between

Informatica PowerCenter & DAC
Installed DAC 11.1.1.6.4 Directory Structure :
File/Directory Name
Export Directory
DeleteTriggers.list
parameterfileOLTP.txt
parameterfileDW.txt
me Locations for the components in Oracle BI Applications 7.9.6.4 deployment.
Description
Location of the DAC Server installation (for example, \orahome\10gR3_1\bifoundation\)
User-specified location of the Informatica installation directory on the machine that hosts Informatica PowerCenter Serv
User-specified location of the Oracle Fusion Middleware home (for example,\FM1_11g\)
Location of the Oracle BI Domain (for example,\MW_HOME\user_projects\domains\bifoundation_domain
Location of the Oracle BI EE Infrastructure home (for example, MW_HOME\Oracle_BI1\)
Location of the Oracle Instance home (for example, MW_HOME\instances\instance1)
4 Directory Structure :
files and directories need to be transferred to OBIEE 11g, Informatica and DAC instance as follows.
Informatica Server Instance
Oracle_BI_DW_Base.rep
SrcFiles
LkpFiles
Import the Oracle BI Applications Identity Store (LDIF) File Into the Embedded LDAP Server through Weblogic Console. Re
7.0 Directory Structure :
must be copied from BI Apps installable direcotry to Middleware.

File/directory to Be Copied from BI Apps Direcotry to Following Location
ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_obis<n>\repository
ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_obis<n>\repository
ORACLE_INSTANCE\bifoundation\OracleBIPresentationServicesComponent\coreapplicationobips<n>\catalog
DOMAIN_HOME/config/fmwconfig.
Import the Oracle BI Applications Identity Store (LDIF) File Into the Embedded LDAP Server through Weblogic
Console. Refresh the GUIDs after importing the LDIF file.
1 HotFix 2 Directory Structure :
File/directory need to copy from BI Apps Direcotry to Following Location

INFA_HOME\server\infa_shared\Backup
INFA_HOME\server\infa_shared\SrcFiles
INFA_HOME\server\infa_shared\LkpFiles
DAC uses the Informatica pmrep and pmcmd command line programs to communicate with Informatica PowerCenter.
PowerCenter Client bin folder for enableling Communication Between Informatica PowerCenter and DAC.
From: INF
4 Directory Structure :
File/directory to Be Copied from BI Apps Direcotry to Following Location
DAC_HOME\dac\export directory
on the machine hosting the DAC Client
DAC_HOME\dac\conf directory on the DAC
Client machine.
DAC_HOME\dac\Informatica\parameters\input directory on the DAC Server machine.
DAC_HOME\dac\Informatica\parameters\input directory on the DAC Server machine.
t.
Description
ca PowerCenter Services (for example,\informatica\9.0.1\)
ain
DAC Client & Server Instance

export directory
DeleteTriggers.list3
parameterfileOLTP.txt
parameterfileOLAP.txt
Weblogic Console. Refresh the GUIDs after importing the LDIF file.
Note to Remember
This repository onlyh contains selected BI Analytics module during BI Apps Installation
This repository contains all Analytics module by default
The Presentation Catalog file i.e. EnterpriseBusinessAnalytics.zip must be unzipped and the contents
copied into this \catalog\ directory.
This xml files needs to be transfferd incase of Linux environment. If your deployed BI EE system with
Oracle BI Applications is different from the BI EE system used to install Oracle BI Applications, then
you must apply the security policy to the BI Domain
Default location for LDIF file:
$ORACLE_BI_HOME\biapps\admin\provisioning\EnterpriseBusinessAnalytics.ldif
Note to Remember
An Informatica Repository file called Oracle_BI_DW_Base.rep is installed in
ORACLE_HOME\biapps\dwrep\Informatica\Repository directory during the Oracle BI Apps installation.
We must move this file to INFA_HOME\server\infa_shared\Backup and load the contents of this REP
file into the Informatica repository.
We need to copy source files from the Oracle BI Apps installation directory to the Informatica
directory on the Informatica PowerCenter Services machine.
We need to copy lookup files from the Oracle BI Apps installation directory to the Informatica
directory on the Informatica PowerCenter Services machine.
ca PowerCenter.
We need to manually copy pmcmd into the
DAC.
From: INFA_HOME\server\bin To: INFA_HOME\clients\PowerCenterClient\client\bin
Note to Remember
DAC metadata file which need to be copied to DAC client machine

DAC metadata file which need to be copied to DAC client machine
DAC Metadata file which need to be Copied to DAC Server machine
DAC Metadata file which need to be Copied to DAC Server machine
Back To Index
Default URL's after deployment & configuration of typical Oracle BI Applicati

Component
Analytics (Answers)
Weblogic Console
Enterprise Manager
Informatica Administration Tool
Oracle DB Enterprise Manager
oyment & configuration of typical Oracle BI Applications 7.9.6.4

Default URL's
http://hostname:port/analytics
http://hostname:port/console
http://hostname:port/em
https://hostname:port/adminconsole
https://hostname:port/em
Default Port
9704
7001
7001
6005
1158
Comme
Listed port# are typical installation port.
per client business requirement.
Comment
typical installation port. However, Port# can be set up as
ss requirement.
Back To Index
DataBase Specific Parameter in OBIA Installation Directory

Using Oracle Template Files:
To configure the Business Analytics Data Warehouse on Oracle databases more easily,
refer to the parameter template files (that is, the init<DB version>.ora files).
These files are located in <DRIVE>:\<Oracle BI Applications install directory>\dwrep\Documentation\
A separate parameter template file is provided for each database version.
(init9iR2.ora, init10gR2.ora, init11g.ora)
For example, the parameter template file for Oracle 11g databases is named init11g.ora.
The parameter template files provide parameter guidelines based on the cost-based
optimizer for Oracle 10g and 11g. Use these guidelines as a starting point. You will
need to make changes based on your specific database sizes, data shape, server size
(CPU and memory), and type of storage. The database administrator should make
changes to the settings based on performance monitoring and tuning.
Copy the appropriate template file into your $ORACLE_HOME/dbs directory. Then,
review the recommendations in the template file, and make the changes based on your
specific database configuration.
more easily,
ry>\dwrep\Documentation\
med init11g.ora.
based on your
Back To Index
Setting Up Informatica PowerCenter 9.1 Hotfix 2

This section covers the following Informatica PowerCenter set up and configuration.
Sr#
1
2
3
4
5
6
7
8
Sr# 1:
Sr# 2:
Sr# 3:
Sr# 4:
Page Up
Sr# 5:
Sr# 6:
Sr# 7:
Sr# 8:
p Informatica PowerCenter 9.1 Hotfix 2
n covers the following Informatica PowerCenter set up and configuration.

Configuring Informatica PowerCenter Components
Creating the Informatica Repository Service
Creating the Informatica Integration Service
Restoring the Pre-built Informatica Repository
Setting up the Informatica Domain and Repository in Informatica PowerCenter Client Tools
Setting PowerCenter Integration Services Relaxed Code Page Validation
Setting PowerCenter Integration Services Custom Properties
Creating the Repository Administrator User in the Native Security Domain
Configuring Relational and Application Connections in Informatica Workflow Manager
To create the Informatica Repository Service:
1. Open Informatica Administrator.

2. In the Domain Navigator, select the root Domain, then click Actions, then New, then PowerCenter Repository Service, t
display the New PowerCenter Repository Service wizard.
3. Specify the properties for this new PowerCenter Repository Service:
Properties
Name
Location
Licence
Node
4. Specify the database properties for this new PowerCenter Repository Service:
Database Properties
Database Type
Username
Password
Connection String
Code Page
5. Select the No content exists under specified connection string. Create new
content. radio button.
6. Click Finish.
To create the Informatica Integration Service:
1. Open Informatica Administrator.

2. In the Domain Navigator, select the root Domain, then click Actions, the New, then PowerCenter Integration Service, t
display the New PowerCenter Integration Service wizard.
3. Specify the properties for this new PowerCenter Integration Service:
Properties
Name
Location
Licence
Node
4. Click Next.
5. Specify the PowerCenter Integration Service and its login credentials:
6. Select the Repository Service that you created.
Login Credentials
username
password
7. Select the data movement mode.
Data Movement Mode
8. Click Finish.
Note: The Integration Service will only start if the Repository Service is operating with the Operating Mode set to 'Norma
Restoring the Pre-built Informatica Repository for Environments in English:

1.
Repository
Service
created.
2. In
In Informatica
the General Administrator,
Properties areaselect
of thethe
Properties
tab,
make that
sure was
the OperatingMode
value
is Exclusive.
3. In the
Actions menu at the top right-hand side, choose Actions, then Repository
Contents, then Delete Contents.
4. At the Delete Contents for <repository name> dialog box, enter the repository username and password (for example,
Administrator\Administrator),
then
clickOK. side, choose Actions, then Repository
5. In the Actions menu at the top
right-hand
Contents, then Restore.
6. At the Restore Contents for <repository name> dialog, enter the repository username and password (for example,
Administrator\Administrator), then clickOK.
7. Choose Actions > Restore Contents.
8. At the Restore Contents dialog, select Oracle_BI_DW_Base.rep from the Select Backup File drop-down list.
9. Select the Restore as New check box.
10. Click OK to start the restore process.
11. When the restore process is complete, click Close.
12. When a repository is restored, the repository becomes a standalone repository. After restoring the repository, you nee
to promote it to a global repository.
13. Change the OperatingMode value to Normal.
a. Go to the Properties tab.
b. In the General Properties area, click Edit.
c. if
Click
OperatingMode
drop-down
and select
Note:
you the
do not
set the Operating
Mode list,
to Normal,
the Normal.
Integration Service will
not restart.
14. If prompted, enter the repository username and password.
To set up the Domain:

1. Start Informatica PowerCenter Designer.
2. Choose Repository, then Configure Domain, to display the Configure Domains dialog.
3. Click the Add a new Domain icon to display the Add Domain dialog.
4. Use the Add Domain dialog to specify the following:

Field Name
Domain Name
Gateway Host
Gateway Port
5. Click OK.
6. In the Repositories list, select the check box for the Repository that you want to use.
To set up the Repository:
1. In the Informatica PowerCenter Designer Choose Repository, then Add to display the Add Repository dialog.
Field Name
Repository Service Name
Username
2. Click OK.
3. In the Repositories tree, double click on the Repository that you specified in the previous step.
4. Specify a user name and password and make sure that the Domain field displays the domain that you specified in the p
Field Name
Username
Password
5. Click Connect
6. Expand the repository in the Repositories list to display the contents.
To setup Integration Services Relaxed Code Page Validation:

1.
2.
3.
4.
5.
Log into Informatica Administrator.

Select the Integration Service.
Select the Properties tab.
In the Configuration Properties area, click Edit.
Deselect the 'ValidateDataCodePages' check box.
To set Informatica PowerCenter Integration Services Custom Properties:

1.
2.
3.
4.
In Informatica Administrator, select the Integration Service.

Click the Properties tab.
In the Custom Properties area, click Edit.
Use the New option to display the New Custom Property dialog, and add the following Custom Properties:
Custom Properties Name
overrideMpltVarWithMapVar
5. Click OK.
To use the default Administrator user in the native security domain:

1.
in tothe
theSecurity
PowerCenter
Console Security
as Administrator.
2. Log
Display
tab byAdministration
clicking the Configure
icon in the top, right
corner of the Informatica Administrator work area.
3. In the Users area, expand the Native directory and select Administrator.
Note:
Do not
an existing
user
an LDAP
domain.
4. Display
theselect
Privileges
tab, and
usefrom
the make
sure
that the correct Domain and
Repository Service are selected.
5. Click OK.
To create a new Repository Administrator defined in the native security domain:

1. Log in to the PowerCenter Administration Console as Administrator.
2. Display the Security tab by clicking the Configure Security icon in the top, right corner of the Informatica Administrato
3. In the Users area, click Actions, then Create User to display the Create User dialog.
Note: Do not create this user in an LDAP domain.
4. Use the Create User dialog to specify the user details, then click OK.
5. In the Users area, select the new user, display the Privileges tab, then click Edit to display the Edit Roles and Privilege
6. Use the Roles tab and Privileges tab to select the appropriate Domain and Repository Service.
7. Click OK.
To Configure Relational and Application Connections in Informatica Workflow Manag

1.
2.
3.
4.
On the Informatica PowerCenter Client machine, start Informatica PowerCenter Workflow Manager.
Connect to repository and provide credential of Administrator user. Also verify Domain is added.
Select Connections, then Relational to display the Relational Connection Browser.
Here you need to create connection for transactional (OLTP) database, and a connection for the Oracle Business Analy
Connection object Defination for OLTP:

Field Name
Connection Name
User Name
Password
Connect String
Code Page
Connection object Defination for OLAP:
Field Name
Connection Name
User Name
Password
Connect String
Code Page
Status
Values
Values
Comment
Values
Values
Values
6005
Values
n the previous task.

Values
Custom Properties
Value
Notes
Yes
Enables Informatica to
evaluate
parameters within
mapplets.
nistrator work area.
ivileges dialog.
Manager:
s Analytics Warehouse (OLAP) database.
Values
Values
NA
Completed
Pending
WIP
Back To Index
Data Warehouse Administration Console (DAC 11.1.1.6.4) Configuration:

This section covers the following DAC set up and configuration.
Sr#
1
2
3
4
5
6
7
8
9
Sr# 1:
Sr# 2:
Sr# 3:
Sr# 4:
Sr# 5:
Page Up
Page Up
Sr# 6:
Sr# 7:
Sr# 8:
Sr# 9:
ndex
Warehouse Administration Console (DAC 11.1.1.6.4) Configuration:
ction covers the following DAC set up and configuration.

Configuring DAC Platform
Known Issues in DAC11g
Creating a DAC Connection and Logging Into DAC
Configure DAC Server
Importing Metadata into the DAC Repository
Creating the Oracle Business Analytics Warehouse Tables
To configure the connection between the DAC Server and the DAC Repository using the DAC Client
Setting DAC System Properties
Registering Informatica Services in DAC
Setting Physical Data Sources
Known Issues in DAC11g

Issues
Error occurs when we run bat file to start the DAC server and DAC client applicable to DAC
11.1.1.6.4 version in windows 7 64 bit environment.
To create a DAC Connection and login to DAC for the first time:
1. Start the DAC Client by navigating to the DAC_HOME\dac directory and
double-clicking the startclient.bat file.
2. Click Configure.
3. In the Configuring ... dialog, select Create Connection, and then click Next.
4. Enter the appropriate connection information:
Field Name
Connection Name
Connection Type
Connection String
Database Host
Database Port
Optional URL
Optional Driver
Authentication File
5. To Create a new authentication file:

a. Click in the Authentication File field of the Configuring... dialog.
b. In the Authentication File dialog, select Create authentication file.
c. Navigate to the folder where you want to save the new authentication file, and click OK.
d. In the Create Authentication File dialog, enter a unique name for the authentication file, and click OK
e. Enter the Table Owner Name and Password for the database where the repository will reside.
f. In the Configuring... dialog, click Test Connection to confirm the connection works.
g. Click Generate Random Encryption Key.
h. Click Apply, and then click Finish.
6. In the Login... dialog, do the following:
a.Select the appropriate Connection from the drop-down list.
b.Enter a the User Name (for example, Administrator).
c.Enter a Password (for example, Administrator).
d.In the Authentication Type drop down list, select DAC.
d.Click Login.
7. When prompted to create a repository, click Yes.
This process creates DAC repository tables.
To configure DAC Server:
1. In DAC, select Tools, then DAC Server Management, then Repository Configuration to display the Repository Configurat
Field Name
Mode
Host
Alternate Host
Port
2. Save the details.
To import metadata into the DAC Repository:
1. In DAC, select Tools, then DAC Repository Management, then Import to display
the Import dialog.
Make sure that the correct DAC_HOME\dac\export\ directory is displayed at the top of the dialog.
2. In the Categories area, select the Logical check box and the System check box.
3. In the Applications List table, use the check boxes in the Selected column to specify the source system applications fo
a. Select the check box next to Universal.
b. Select the check box for any other business applications that you want to deploy.
4. Select the Truncate Repository Tables check box.
5. Select the Enable Batch Mode check box.
6. Click OK to display the Importing tables dialog.
7. To confirm that you want to import the seed data selected, re-type the text in the text box and click Yes.
8. If prompted to verify that you want to continue with the Import, click Yes.
9. Click OK.
To create Oracle Business Analytics Warehouse tables:

1. In DAC, select Tools, then ETL Management, then Configure.
2. In the Sources dialog, select the database platform for the target data warehouse and source transactional database.
3. Click OK to display the Data Warehouse Configuration Wizard.
4. On the Data Warehouse Configuration Wizard > Configuration page, select the Generate create statements for Data Wa
5. Click Next to display the Data Warehouse/Data Warehouse SQL page.
5. Enter the details for the

Oracle Business Analytics Warehouse database:
Field Name
Container
Is Unicode
Execute
Physical Data Source

Change default
parameter file
6. Click Start.
To configure the connection between the DAC Server and the DAC Repository using
1. In DAC, select Tools, then DAC Server Management, then DAC Server Setup.
2. Click Yes to display the Server Configuration dialog.
3. In the Repository Connection Information tab, enter the appropriate information:
Field Name
Connection Type
Connection fields:
Instance
Database Host
Database Port
Table owner name
Password
4. Click Test Connection to make sure the DAC Repository connection works.
5. Click Save.
To set DAC System Properties:

1. In DAC, navigate to the Views menu, then select Setup, then DAC System Properties.
2. Set values for the following properties:

Property
DAC Server Host
DAC Server OS
InformaticaParameterFileLocation
Repository Name
To register Informatica Services in DAC:

1. In DAC, navigate to the Setup view, and then display the Informatica Servers tab.
a. Informatica Integration Service Registration
Field Name
Name
Type
Service
Domain
Login
Password
Num Parallel Workflows per EP
Repository Name
Inactive
b. Informatica Repository Service Registration
Field Name
Name
Type
Hostname
Server Port
Domain
Login
Password
Num Parallel Workflows per EP
Repository Name
Inactive
To specify transactional and data warehouse data sources:

1. In DAC, from the Views menu, select Setup, then Physical Data Sources.
Field Name
Name
Type
Connection Type
Instance or TNS Name or Connection String or
Database Name
Table Owner
Table Owner Password
Num Connections Per EP
DB Host
Port
Source Priority
Data Source Number
Default Index Space
2. Click Test Connection to make sure the connection works.
3. Click Save.
on:
rst time:
Status
Workaround
Comment
Comment
Configure the following two lines in config.bat file from DAC Server JAVA_HOME should be set to
installed Java SDK (no spaces in the path).
DAC_HOME should point to the location where DAC is installed (no spaces in the path).
Values
Required Values
Unique name for connection
Type of database
Oracle (OCI8), use the tnsnames
entry/Oracle (Thin), use the instance
name.
Database Host Name
Database Port
Can be used to override the standard URL
for this connection.
Can be used to override the standard
driver for this
connection.
Create a new authentication file.
entication file, and click OK.
e for the authentication file, and click OK.
where the repository will reside.
the connection works.
ation to display the Repository Configuration dialog.
Values
Standalone
Description
Keep Standalone Mode for OBIA 7.9.6.4
Specify the machine that hosts DAC
Server
Unspecified
3141
Keep Default
the top of the dialog.
specify the source system applications for which you will import the ETL metadata, as follows:
n the text box and click Yes.
ouse and source transactional database.
e Generate create statements for Data Warehouse Tables check box.
Values
Description
Keep blank
Name of the source business applications.

Specifies whether the data warehouse
database is Unicode.
Use this option if you want DAC to
execute the SQL script automatically
after it is generated.
Select the required target data source.

Use this button to display the Choose
default parameter file dialog, which
enables you to specify a different schema
template.
nd the DAC Repository using the DAC Client:
Values
Description
Select the type of database.
Oracle(Thin)
Instance Name of Database.
Database Host Name.
Database Port.
Table owner name, using the account that
you created a database to store the DAC
Repository.
Password for above database account.
Values
Value Required
Enter the name or IP address of the
machine that hosts the DAC Server.
Enter the operating system of the
machine that hosts the DAC Server.
Possible values are Windows, AIX, Solaris,
HP-UX, Linux (case sensitive).
Enter the path to the Informatica source

file directory, for example: INFA_HOME\
server\infa_shared\SrcFiles.
Informatica PowerCenter Repository

Service Name
Values
Enter or Select
A name to identify the PowerCenter
Integration Service in DAC.
Informatica
Informatica.
The name of the PowerCenter Integration
Service that is being used.
The Informatica domain name.
Informatica Repository user name.
Informatica Repository user password.
Maximum number of workflows that can

be executed in parallel on the
Informatica PowerCenter Integration
Services service. If the number of sessions
is zero or is not specified, the DAC Server
assigns the default value of 10.
The name of the PowerCenter Repository

Service.
Indicates whether the PowerCenter
Integration Services service will
participate in the ETL process.
Values
Enter
A name to identify the PowerCenter
Repository Service in DAC.
Repository
Repository.
The host name or IP address of the
machine that is running the Informatica
Server.
6005
The Port number of the Gateway Node

that is being used for the Informatica
PowerCenter domain.
The Informatica domain name.
Informatica Repository user name.
Informatica Repository user password.
Maximum number of workflows that can
be executed in parallel on the
Informatica PowerCenter Integration
Services service. If the number of sessions
is zero or is not specified, the DAC Server
assigns the default value of 10.
The name of the PowerCenter Repository

Service.
Indicates whether the Repository Service

will participate in the ETL process.
OLTP Values
OLAP Values
Source
warehouse
Comment
C Server JAVA_HOME should be set to a directory where you have
ed (no spaces in the path).
NA
Completed
Pending
WIP
Oracle(Thin)
Oracle(OCI8)
Back To Index
Configuring the Oracle BI Repository Connections:
This section covers configuring the predefined repository connections and variables in the RPD file after d
Sr#
1
2
3
Configuring the Oracle BI Repository Connections

To specify the database type for connection pools
To specify connection details for connection pools
To Configure Oracle BI Repository Variables
Sr# 1:
To specify the database type for connection pools

1.
2.
3.
4.
Using the Oracle BI Administration Tool, open the OracleBIAnalyticsApps.rpd file.

In the Physical pane, double-click the Oracle Data Warehouse and Oracle EBS OLTP object.
Display the General tab.
Use the Database field to specify your database type.
Field Name
Database
5. Save the repository.
6. Click Yes to Check Global Consistency.
Sr# 2:
To specify connection details for connection pools

1. Using the Oracle BI Administration Tool, open the OracleBIAnalyticsApps.rpd file.
2. In the Physical pane: Expand the respective node, and double-click Connection Pools
Field Name
Call Interface
Maximum Connections
Data Source Name
User Name
Password
Page up
3. Save the repository.

4. Click Yes to Check Global Consistency.
Sr# 3:
To Configure Oracle BI Repository Variables

1.
2.
3.
4.
Using the Oracle BI Administration Tool, open the OracleBIAnalyticsApps.rpd file.

On the Manage menu, click Variables to display the Variable Manager.
Expand the Variables\Static node.
Edit the following variables, which apply to all deployments:
Variable Name
GLOBAL_CURRENCY1
GLOBAL_CURRENCY2
GLOBAL_CURRENCY3
OLAP_DSN
OLAP_USER
OLAPTBO
ORA_EBS_OLTP_DSN
ORA_EBS_OLTP_USER
variables in the RPD file after deploying OBIEE repository into DEV server..
Status
Comment
Values for Oracle Data Warehouse
Values for Oracle EBS OLTP
on pools
AnalyticsApps.rpd file.
use and Oracle EBS OLTP object.
on pools
ble-click Connection Pools
Values for Oracle Data Warehouse Connection
Values for Oracle EBS OLTP Connection Pool
Pool
VALUEOF(OLAP_DSN)
VALUEOF(OLAP_USER)
Values
VALUEOF(ORA_EBS_OLTP_DSN)
VALUEOF(ORA_EBS_OLTP_USER)
NA
Completed
Pending
WIP
Back To Index
This section contains mandatory and additional configuration tasks that apply to Oracle BI Applications deployed with
various source systems.
Configuring source system parameter tab in DAC :

Sr No.
Task
Parameter in DAC
Initial Extract Date
$$INITIAL_EXTRACT_DATE
Configuring Global Currencies
$$GLOBAL1_CURR_CODE $
$GLOBAL2_CURR_CODE $
$GLOBAL3_CURR_CODE
Exchange Rate Types
$$GLOBAL1_RATE_TYPE $
$GLOBAL2_RATE_TYPE $
$GLOBAL3_RATE_TYPE $
$DEFAULT_LOC_RATE_TYPE
Configuring Calendars
$$GBL_CALENDAR_ID
Configuring Data Source Num ID
$$GBL_DATASOURCE_NUM_ID
Configuration of Product Hierarchy (Except $$PROD_CAT_SET_ID1-$

for GL, HR Modules)
$PROD_CAT_SET_ID10
$$INV_PROD_CAT_SET_ID1-$
$INV_PROD_CAT_SET_ID10
Configuring Physical Data Sources tab in DAC :

Sr No.
1
2
3
Task
Data Source Number for Source
Data Source Number for Target
Data Source Number for ORA_R12_Flatfile
Parameter in DAC
Data Source Number
Data Source Number
Data Source Number
Configuring Task tab parameter in DAC :

Sr No.
Task
Parameter in DAC
SDE_ORA_ProductDimension
$$MASTER_ORG
Oracle BI Applications deployed with any source system, as well as mandatory and additional tasks that are specific to the
Required values from source(Oracle EBS)
Mandatory/Opti
onal
Beginning of an Accounting Period
Transactional currency code(Required 3

maximum currency code)
According to currencies defined
Enterprise Calendar (period_set_name||'~'||

period_type)
This parameter is the data_source_num_id with

which you have loaded the EBS calendars
Values obtain from

source(Oracle EBS)
Purchasing Category Set
Inventory Category Set
Mandatory/Optional
Parameter
Values
M
M
M
Comment
All values should be same
for source, target, and
flatfile
Mandatory/Optional
Parameter
Values
OOTB Default values
'204'
nal tasks that are specific to the
OOTB Default values

Jan 01, 1970
Comment
Date to extract the Data from EBS source.
USD
Corporate
$$DEFAULT_LOC_RATE_TYPE (the conversion rate type for document

currency to local currency conversion)
Accounting~41
Use the query from EBS source "SELECT period_set_name || ~||

period_type FROM gl_periods;"
9 Keep the default value
You configure these parameters and create new PROD_CAT_SETn and

INVPROD_CAT_SETn parameters in DAC, based on the Oracle EBS Category
Set IDs that you want to load into the Oracle Business Analytics
Warehouse.
27
Remark
Comment
Remark
To define multiple
master organizations,
specify a
comma-separated list
of organization codes
in single quotation
marks (for
example, '204', '301').
Remark
Back To Index
Sr No.
BI APPS Components
Link to Navigate
Group_Acct_Names
Informatica- SrcFiles
Group_Acct_Codes
Grpact_Fstmt
Description
Reference to Configuration
Guide
This file specifies the group account

names and their corresponding group
account codes
This file maps General Ledger accounts 3.2.1.4 About Mapping Oracle
GL Natural Accounts to Group
to group account codes
Account Numbers
This file maps Financial Statement Item
Codes to group account codes
Comment
Status
NA
Completed
Pending
WIP
Back To Index
Description
Examples
Last Updated By
Last Updated On
GROUP_ACCOUNT_NUM
ACC DEPCN
ACC LIAB
AP
AR
CASH
CMMN STOCK
COGS
CONT EXP
DEPCN
EMP BENFT
EMP SUPP
EMP OVERTIME
FG INV
FREIGHT
GEN PAYROLL
GOODWILL
INC TAX
INT EXP
LT DEBT
MKTG PAYROLL
OTHER ASSET
OTHER CA
OTHER CL
OTHER EQUITY
OTHER INC
OTHER LIAB
OTHER MKTG EXP
OTHER OPER EXP
OTHER R&D EXP
OTHER SLS EXP
PPAID EXP
PPE
PREF STOCK
PURCH
RET EARNING
REVENUE
RM CONS
GROUP_ACCOUNT_NAME
ACC DEPCN
ACCRUED LIABILITIES
ACCOUNTS PAYABLES
ACCOUNTS RECEIVABLE
CASH
CMMN STOCK
COST OF GOODS SOLD
CONTRACTING EXPENSES
DEPRECIATION EXPENSES
EMPLOYEE BENEFITS RELATED EXPENSES
EMPLOYEE SUPPORT AND CAFETERIA EXPENSES
EMPLOYEE OVERTIME
FINISHED GOODS INVENTORY
FREIGHT EXPENSES
GENERAL ADMIN AND OTHER PAYROLL
GOODWILL
INCOME TAX
INTEREST EXP
LONG TERM DEBT
MARKETING PAYROLL
OTHER ASSET
OTHER CURRENT ASSET
OTHER CURRENT LIABILITY
OTHER EQUITY RELATED
OTHER INCOME
OTHER LIABILITY
OTHER MARKETING EXPENSES
OTHER OPERATING EXPENSES
OTHER R&D EXPENSES
OTHER SALES EXPENSES
PREPAID EXPENSES
PPE
PREFERRED STOCK
PURCH
RETAINED EARNING
SALES REVENUE
RM CONS
RM INV
R&D PAYROLL
SLS PAYROLL
ST BORR
TAX LIAB
VARIANCE EXP
WIP INV
DEFERRED REVENUE
UNAPPORTIONED AUTH
APPORTIONMENT
ALLOTMENT
COMMITMENT
OBLIGATION
EXPENDITURE
ANT RES
APPROP RELZ
CONT AUTH
BORR AUTH
OTHER RES
PPV
RAW MATERIAL INVENTORY

R&D PAYROLL
SALES PAYROLL
ST BORR
TAX LIABILITY
PRODUCT VARIANCE EXPENSES
WIP INV
DEFERRED REVENUE
UNAPPORTIONED AUTHORITY
APPORTIONMENT
ALLOTMENT
COMMITMENT
OBLIGATION
EXPENDITURE
ANTICIPATED RESOURCES
APPROPRIATIONS REALIZED
CONTRACT AUTHORITY
BORROWING AUTHORITY
OTHER RESOURCES
PPV
LANGUAGE
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
Back To Index
Description
Examples
Last Updated By
Last Updated On
CHART OF ACCOUNTS ID
FROM ACCT
101
101
101
101
101
101
101
101
101
101
101
101
TO ACCT
GROUP_ACCT_NUM
10001
10522 CASH
11000
11299 AR
11500
11999 AR
21500
21500 AR
42000
42220 PURC
13300
13350 FG INV
13200
13201 WIP INV
42605
42605 PPV
62300
62300 EMP SUPP
21200
21499 AP
21501
22600 AP
13100
13130 RM INV
Back To Index
Description
Examples
Last Updated By
Last Updated On
GROUP_ACCT_NUM
ACC DEPCN
ACC LIAB
AP
AR
CASH
CMMN STOCK
COGS
CONT EXP
DEPCN
EMP BENFT
EMP SUPP
EMP OVERTIME
FG INV
FREIGHT
GEN PAYROLL
GOODWILL
INC TAX
INT EXP
LT DEBT
MKTG PAYROLL
OTHER ASSET
OTHER CA
OTHER CL
OTHER EQUITY
OTHER INC
OTHER LIAB
OTHER MKTG EXP
OTHER OPER EXP
OTHER R&D EXP
OTHER SLS EXP
PPAID EXP
PPE
PREF STOCK
PURCH
RET EARNING
REVENUE
RM CONS
RM INV
R&D PAYROLL
SLS PAYROLL
ST BORR
TAX LIAB
VARIANCE EXP
WIP INV
OTHERS
DEFERRED REVENUE
PPV
Mapped FIN_STMT_ITEM_CODE and GL_ACCT_CAT_CODE based on GROUP_ACCT_NUM

Status information is required to keep track of the accounting document status
Siebel Analytics
24-Aug-05
FIN_STMT_ITEM_CODE
OTHERS
OTHERS
AP
AR
OTHERS
OTHERS
COGS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
REVENUE
OTHERS
OTHERS
OTHERS
OTHERS
OTHERS
TAX
OTHERS
OTHERS
OTHERS
REVENUE
OTHERS
GL_ACCT_CAT_CODE
BS
BS
BS
BS
BS
BS
PL
PL
PL
PL
PL
PL
BS
PL
PL
BS
PL
PL
BS
PL
BS
BS
BS
BS
PL
BS
PL
PL
PL
PL
BS
BS
BS
BS
BS
PL
BS
BS
PL
PL
BS
BS
PL
BS
BS
BS
BS

Oracle BI Application Setup & Configuration V1.4

Uploaded by

Copyright:

Available Formats

Oracle BI Application Setup & Configuration V1.4

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle BI Application Setup & Configuration V1.4

Uploaded by

Copyright:

Available Formats

Oracle BI Application Setup and Configuration Roadmap

Oracle BI Application Setup & Configuration

Parag Devdas, Amar Shirke, Rahul

Parag Devdas, Amar Shirke, Rahul

Parag Devdas, Amar Shirke, Rahul

Parag Devdas, Amar Shirke, Rahul

Added Pre-requisites for OBIA

EBS R12 and Target as Oracle Database/DWH

Oracle Business Application 7.9.6.4

Configuration of Oracle BI Appli

Oracle BI Application Setup

Post Installation System Configuration

Configuring Common Areas and Dimensions

Oracle Human Resource Analytics

Oracle Financial Analytics

Oracle Supply Chain & Order Management Analytics

Oracle Procurement & Spend Analytics

guration of Oracle BI Application

Double click this icon to open the Analytics Specific

Double click this icon to open the Analytics Specific

Double click this icon to open the Analytics Specific

Pre-requisites for OBIA 7.9.6.4

Configuring Informatica PowerCenter Components

List of Software to be install for OBIA 7.9.6.4

Required Database Schemas for OBIA Components

Creation of Users, Table space, SSE Role and DB Privileges

Data Sources and Associated DATASOURCE NUM ID Values

Code Page and Data Movement requirement

List of Softwares to be install for OBIA 7.9.6.4:

Oracle Database Client

Oracle Database 11g Release 2 (11.2.0.1.0) for Microsoft Windows x6

Oracle Business Intelligence Data Warehouse Administration Console

Oracle Business Intelligence Data Warehouse Administration Console

Oracle Business Intelligence Data Warehouse Administration Console

Oracle Business Intelligence Data Warehouse Administration Console

Repository Creation Utility (11.1.1.7.0) for Microsoft Windows (64-bit

OBIEE 11g Client Tool

Oracle Business Intelligence Developer Client Tools Installer

Oracle Business Intelligence Applications Licensing and Packaging

Oracle Business Intelligence Enterprise Edition 11g Release 1

Local (PATA, SATA, iSCSI), or

Oracle BI Enterprise Edition / ETL Tier

Required Database Schemas for OBIA Components:

Oracle Business Analytics Warehouse Tablespaces

Schema Required For

Schema Required For

Creation of Users, Table Space, SSE Role and DB Privileges:

GRANT CONNECT TO SSE_ROLE;

USER DEV_MDS IDENTIFIED BY lntpoc123 DEFAULT tablespace DEV_MDS_TS TEMPORARY ta

DEV_MDS_TS datafile 'DEV_MDS_TS.dbf' size 500m autoextend on next 100m maxsize 10

GRANT CONNECT, resource, CREATE VIEW TO DEV_TGT_DW;

Data Sources and Associated DATASOURCE_NUM_ID Values:

Data Source Number

Code Page and Data Movement Requirement

2) Code Page Compatibility Summary:

Code Page Compatibility

Source (including relational, flat

Target (including relational, XML

Lookup and stored procedure