Académique Documents
Professionnel Documents
Culture Documents
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
Virtual InfoProvider
Kernel: 700_REL
Basis: 700
ABAP: 700
SAP_BW: 700
11.1.2.3
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.
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
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
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
*
*
*
*
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.
Auth Object
S_RFC
S_DATASET
Fields
ACTVT
RFC_NAME
RFC_TYPE
ACTVT
FILENAME
PROGRAM
Value
16
*
*
*
*
*ZODI*
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.
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:
Server
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.
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
Workbench
Refer to the FDMEE Administration Guide for more details on the individual steps.