Oracle Hyperion Financial Data Quality Enterprise Edition Source Adapter for SAP BW

Bristlecone Integration Components Installation Guide

Readme
Purpose ................................................................................................................................. 1
Overview ............................................................................................................................... 1
System Requirements for Bristlecone Integration Components ............................................ 1
Configuration ........................................................................................................................ 2
Configuring SAP Production Systems .................................................................................... 9
Using the SAP Adapter .......................................................................................................... 9
SAP Source Tables .......................................................................... Error! Bookmark not defined.

Purpose
This document provides information about the integration between SAP BW Infocube and Oracle
Hyperion Enterprise Performance Management (EPM) System.

Overview
This integration provides a solution to load data from SAP BW Infocube to Oracle Hyperion EPM
System. Data can be extracted from SAP BW for the following type of info cubes:

Aggregate Cube

Standard Info Cube

Virtual InfoProvider

Custom Info Cube

System Requirements for Bristlecone Integration Components

The following are system requirements for the Bristlecone integration components:

SAP System Version: BI 7.0

Recommended Release Versions for SAP ECC6.0 EHP3 system:

Kernel: 700_REL

Basis: 700

ABAP: 700

SAP_BW: 700

Supported EPM Version and required ODI/ODI Components Version

EPM Version

ODI/ODI Components Version

11.1.2.3

11.1.1.7+10.1.3.16 Open Tool + sapjco3.0.2

and above

NOTE: The SAP BW to FDMEE is currently supported only when FDMEE uses Oracle as database. The
support Microsoft SQL Server is currently being tested and certification will be announced shortly.

Configuration
This integration leverages the ODI SAP BW Adapter for performing the data extraction and loading from
SAP. In order to understand the overall processes of the integration please review the ODI SAP Adapter
documentation available at
http://docs.oracle.com/cd/E17904_01/doc.1111/e17466/sap_abap_bw.htm#ODIAA479. This section
provides the steps required to configure ODI and FDMEE to accomplish this data integration.

Prepare User in SAP for Use in ODI

The ODI SAP Adapter creates and executes various packages in order to perform data extraction from
SAP. A SAP user must be identified and prepared with appropriate authorizations for this integration.
This section outlines the required authorizations.
Authorizations Required to Execute RKM the first time
The RKM must be executed once in order to create some packages in SAP. These packages are
required for data load steps. After one successful execution of RKM it is not required to run the RKM
again. The authorization required to run the RKM the first time are listed below:
S. No
1

Auth Object
S_RFC

Fields
ACTVT
RFC_NAME
RFC_TYPE

S_TCODE

Value
16
*
*
AL11
SE10

TCD

SE11
SE16
SE37
SE38
SE80
SE91
SM21
SM50
SM58
SM59

ST22
SU53
3

S_ADMI_FCD

S_DATASET

S_GUI

ACTVT

S_RZL_ADM

ACTVT

S_TABU_DIS

ACTVT
DICBERCLS

02,03
*

S_DEVELOP

ACTVT
DEVCLASS
OBJNAME
OBJTYPE
P_GROUP

01, 02,
03
*
*
*
*

S_TRANSPRT

ACTVT
TTYPE

01, 02,
03
*

10

S_RS_ADMWB

ACTVT
RSADMWBOBJ

*
*

11

S_RS_ICUBE

ACTVT
RSICUBEOBJ
RSINFOAREA
RSINFOCUBE

*
*
*
*

12

S_RS_IOBJ

ACTVT
RSIOBJ
RSIOBJCAT
RSIOBJPART

*
*
*
*

13

S_RS_AUTH

BIAUTH

S_ADMI_FCD

NADM
PADM
SM21

ACTVT
FILENAME
PROGRAM

*
*
*

When the RKM is executed successfully, the following programs are created in SAP.

Function Group
ZODI_FGR

ZODI_FGR_PROD

Function
ZRFC_ABAP_INSTALL_AND_RUN

Created By
RKM

ZRFC_UPLOAD_INSTALL_WRAPPER

RKM

ZODI_ABAP_SYNTAX_CHECK
ZODI_BG_REPORT_SAVE_ACTV
ZODI_CUBE_SEARCH
ZODI_IOBJ_SEARCH
ZODI_ODSO_SEARCH
ZODI_OHDEST_SEARCH
ZODI_INFOAREA_GETLIST
ZODI_INFOAREA_GETDETAILS
ZODI_IOBJ_GETDETAILS
ZODI_CUBE_GETDETAILS
ZODI_ODS_GETDETAILS
ZODI_LKM_OPENHUB

RKM
RKM
RKM
RKM
RKM
RKM
RKM
RKM
RKM
RKM
RKM
RKM

ZODI_BG_CONTROLLER
ZODI_BG_CLEAN_SPOOL
ZODI_RSPC_API_CHAIN_START
ZODI_GET_MAX_REQID
ZODI_RFC_DELETE_FTP_FILE

RKM
RKM
RKM
RKM
RKM

Use
This takes the ODI Open Tool
generated code as input and
creates and activates the function
modules.
This is a wrapper over the
ZRFC_ABAP_INSTALL_AND_RUN

Deletes the file from FTP location.

This is used by LKM generated
function module when the file
transfer mode is set to FTP in ODI.

Authorizations required to Execute RKM after initial execution

If you are required to perform any customizations you will be required to execute RKM after initial run.
For subsequent use of RKM to reverse any SAP tables, set the UPLOAD_ABAP_CODE option as false in
RKM options in ODI. The authorizations are required to execute RKM.

S.No
1

Auth Object
S_RFC

Fields
ACTVT
RFC_NAME
RFC_TYPE

Value
16
*
*

S_TCODE

TCD

SE16

S_RS_ADMWB

ACTVT
RSADMWBOBJ

*
*

S_RS_ICUBE

ACTVT
RSICUBEOBJ
RSINFOAREA
RSINFOCUBE

03
*
*
*

S_RS_IOBJ

ACTVT

RSIOBJ
RSIOBJCAT
RSIOBJPART

*
*
*

BIAUTH

S_RS_AUTH

Authorization required to Execute LKM with Upload ABAP Option Enabled

When data loads are executed ODI creates and uploads a function module to SAP BW. This function
module is later executed to perform the data extraction from SAP BW. Note this function module is
created in development system and later transported to a production environment. The authorizations
required to run the LKM with Upload Option in a development environment are listed below:
S.No
1

Auth Object
S_RFC

Fields
ACTVT
RFC_NAME
RFC_TYPE

16
*
*

S_CTS_ADMI

CTS_ADMFCT

S_DATASET

S_DEVELOP

S_TRANSPRT

ACTVT
FILENAME
PROGRAM

Value

06, 33, 34
*
*ZODI*

ACTVT

01,02,03

DEVCLASS
OBJNAME
OBJTYPE
P_GROUP

*
*
*
*

ACTVT

S_RS_IOBJ

TTYPE

ACTVT
RSIOBJ
RSIOBJCAT
RSIOBJPART

*
*
*
*

The function module that gets created is described below:

Function Group
ZODI_FGR_PROD
number>

Function
ZODI_<number>_<number>

Created By
LKM

Use
This is the function module
created by
ZRFC_ABAP_INSTALL_AND_RUN
function module. Upon execution
this will extract the data from
SAP.

Authorization required to Execute LKM with Upload ABAP Option Disabled

In production environment, the LKM is executed with the UPLOAD_ABAP_CODE option set to false in
ODI. The authorizations required to execute LKM without uploading ABAP code are:
S.No
1

Auth Object
S_RFC

S_DATASET

Fields
ACTVT
RFC_NAME
RFC_TYPE
ACTVT
FILENAME
PROGRAM

Value
16
*
*
*
*
*ZODI*

Configuring ODI for use with SAP BW

Install ODI Studio and SAP JCO
1. Use ODI_Studio_11123.zip included as part of EPM 11.1.2.3 Media Kit to install ODI Studio.
ODI Studio may be installed on any server that has access to the ODI Repository.
2. The SAP JCo files must be installed with ODI Studio by following the steps documented in
section 7.2.3.1 at http://docs.oracle.com/cd/E17904_01/doc.1111/e17466/sap_abap_erp.htm#CHDDBIIH.
3. Download the Open Tool for SAP (odi-sap.jar) from Bristlecone website
(http://www.bristleconelabs.com/edel/edel_login.asp) and copy to <ODI_HOME>\oracledi.sdk\lib. If
file already exist overwrite it.
4. Connect to the ODI Designer and go to the menu option ODI Add/Remove Open Tools. Type
the Class Name oracle.odi.sap.km._OdiSapAbapExecute in the Open Tool Class Name text box
and press the Add Open Tool button. If added successfully the Open Tool version 10.1.3.16 will
be shown.

Setup Topology and Work Repository

1. Refer to the Admin Guide for Oracle Hyperion Financial Data Quality Management ERP
Integration Adapter for Oracle Applications for the prerequisites to configure ODI.
2. User can create new contexts if required. However a default context Global will be available for
use with predefined logical and physical schemas.
3. Configure Topology in ODI
Setup FSMOUNT:
The SAP Adapter Project for EPM Release 11.1.2.3 leverages the LKM SAP BW TO ORACLE
(SQLLDR) for Oracle targets(FDMEE schema on oracle DB) for extracting and loading data. This
KM requires a folder that is accessible from the SAP system and the ODI Agent. This is typically
done by sharing a folder of the ODI Agent machine with SAP Systems. This folder is to transfer
data files and other KM files (log, ctl and out files) generated during the extraction process. This
is called FSMOUNT. The user needs to configure this in the ODI Topology. To do the same
please follow the steps given below:

Open the Physical Schema of the server FDMEE_SAP_FSMOUNT(under File Technology)

to make the following settings.
o

In the option Directory(Schema) set the shared drive location where the files will
get created(eg: \\10.30.0.51\FDM_FSMOUNT\).

In the option Directory(Work Schema) set the local location of the mounted
folder (eg: C:\FDM_FSMOUNT\).

Map the FSMOUNT Physical Schema to the Logical Schema File Server for SAP ABAP if
not already done for the context in question.

The user needs to map this shared location on the SAP System. This folder should be mounted
in the SAP System by the local SAP BASIS Admin.
Setup SAP BW Data Server:
The next step is to configure the connection to the SAP Data Server.

Go to ODI Topology Physical Architecture Technologies SAP ABAP

A default SAP Data Server (SAP_SERVER) will be available. Provide the necessary server
and user information to connect to the SAP BW server.

Provide the flex field information for the above SAP Data Server.

Create a Physical Schema for the above created SAP Data Server.

If more data servers are required create new SAP Data Servers and provide the
information to connect to these servers.

Map the Logical Schema (SAP_SOURCE) and Physical Schema for the SAP servers if not
already done for the context in question.

4. Go to the SAP Data Server flex fields to check whether Extract Timeout Flex Field is present or
not. If not present then connect to the Master Repository database schema that was created as
part of ODI Setup and execute the following SQL statement:

INSERT INTO SNP_FLEX_FIELD

(I_FF,I_OBJECTS,FF_NAME,FF_CODE,FF_DESC,FF_TYPE,NUM_VALUE,SHORT_TXT_VALUE,FF_ORDER,F
F_TECHNO) VALUES (62999,1400,'Extract Timeout','SAP_EXTRACT_TIMEOUT',null,'N',0,null,130,'SAP_ABAP');
5. If the SAP Adapter Model Folder shows an error post import double click on the model inside
this folder and select the RKM in the reverse engineer tab.
6. Reverse Engineer Info Cube 0FIGL_C01 using ODI Studio. The detail steps are documented in
section 7.5.2 at
http://docs.oracle.com/cd/E17904_01/doc.1111/e17466/sap_abap_bw.htm#ODIAA479 This
step is required for loading some generic development classes to SAP.
Install SAP JCO in Server
1. Download patch 16790429 from Oracle Support site and install it
2. Download SAP JCo 3.0 to server
3. Copy sapjco3.jar to <EPM_MIDDLEWARE_HOME>\odi\odi_misc dir. Typically
<EPM_MIDDLEWARE_HOME> is C:\Oracle\Middleware
4. For Windows copy sapjco3.dll to lib dir as follows
a. For Windows 32 bit <EPM_ORACLE_HOME>\products\FinancialDataQuality\lib
b. For Windows 64 bit <EPM_ORACLE_HOME>\products\FinancialDataQuality\lib\64-bit
For Unix copy libsapjco3.so to dir as follows
c. For Unix/Linux 32 bit <EPM_ORACLE_HOME>\products\FinancialDataQuality\lib
d. For Unix/Linux 64 bit <EPM_ORACLE_HOME>\products\FinancialDataQuality\lib\64-bit
5. Stop and Start

Server

Configuring FDMEE for SAP BW Source System

6. Log into FDMEE using EPM Workspace.
7. Navigate to the Source System page and define a new source system with following values:
a. Source System Type SAP BW.
b. Specify the ODI Context defined during ODI Topology configuration. The default context is
GLOBAL.
8. Navigate to the Source Adapter page and create a new source system of Type SAP BW.
9. Set the ODI Project Code to AIF_SAP_BW. Specify the Adapter Key, Adapter name, Package
name and SAP BW Infocube Name in alphanumeric character and click Save.
10. Now click on Import Cube Definition button. A prompt will come for selecting the Context for
the SAP BW source system. A successful import message will be shown if import is successful.
Upon successful import of cube definition, source columns from the SAP BW Infocube would be
visible under the source column tab of the adapter.
11. Classify the Key Figure source columns as Fact, Fiscal Year column as Year and Fiscal Period
column as Period in the source column tab.
12. Filters can be created on the source columns with condition type as Explicit.
13. Click on Generate Template Package to create a package in ODI under the SAP BW Adapter
project. A successful package creation message will be shown in FDMEE if the creation of
package is successful in ODI.

Configuring SAP BW Production Systems

The ODI SAP Knowledge Modules dynamically create and upload ABAP program to the SAP system
during ODI Scenario execution. However the upload of ABAP programs may not be feasible in all
environments in a customer deployment. In the development environment user will have more open
access to upload new programs and create fresh objects while in QA and Production the access to
create and upload new programs will be limited. ODI provides the user ability to control when
programs can be uploaded. The recommended process for this integration is as follows:
Customers develop and test their integration in a Development environment. In this environment the
option to Upload ABAP program will be set to Yes. The steps to perform this are as follows:

In the ODI Topology->Physical Architecture open the SAP Development Server by double
clicking it.

Go to the flex fields tab and set the SAP Allow ABAP Upload flex field to 1.

When ready to deploy to QA or Production environment customers must create a transport request in
the source and release the request to the target system. In the target environments the option to
Upload ABAP program will be set to 0. The steps to perform this are as follows:

In the SAP Development system create a workbench transport request for the Package named
ZODI_LKM_PCKG and release the request to the target SAP system.

In the ODI Topology ->Physical Architecture open the SAP QA/Production Server by double
clicking it

Go to the flex fields tab and set the SAP Allow ABAP Upload flex field to 0

NOTE: If you want to test concurrent user loads in development environment set the SAP Allow ABAP
Upload to 0. Without setting this value if multiple users will try to upload the same ABAP programs
and will result in errors.

Using the SAP Adapter

The following steps are to be performed in FDMEE to load data using FDMEE SAP Adapter

In the Import Format page define a new import format for importing the data. Select the
SAP source systems defined in step 1 of Configure FDMEE section and the appropriate
adapter created as per the Configure FDMEE section. Map the source columns to the
appropriate target dimensions.
After all the import format mappings are complete press the Regenerate ODI Scenario
button. This step will generate ODI Scenario based on the import format mappings.
In the Locations page define a new location using the import format
In the Data Rule page define a new data rule. Select the appropriate period mapping
method. Provide a value for the parameters.
Execute the data rule using one of methods:
FDM Import Page

Data Rule Execution

Workbench

Batch Execution Script

Refer to the FDMEE Administration Guide for more details on the individual steps.