X hits on this document





106 / 131



This section provides an introduction and the methodology to work with the adapter, which lets Oracle Data Integrator connect to SAP-BW system using SAP Java Connector (SAP JCo) libraries. This adapter allows mass data extraction from SAP-BW systems.

If this is the first time you are using the SAP ABAP – BW connector, it is recommended to use the Getting Started Guide for SAP ABAP - BW. It contains the complete pre-requisites list as well as step- by-step instructions including SAP connection testing.


RKM SAP BW enables Oracle Data Integrator (ODI) to connect to SAP BW system using SAP JCo libraries and perform a customized reverse-engineering of SAP BW metadata.

LKM SAP BW to Oracle (SQLLDR) is in charge of extracting and loading data from SAP BW system (source) to an Oracle Staging Area.

Overview of the SAP ABAP - BW Integration Process

Reverse-Engineering Process

Reverse-engineering is using the RKM SAP BW. This knowledge module automatically installs the required RFC programs to retrieve the metadata about SAP BW data targets. It can extract the list of SAP BW data objects and display it in a tree Metadata Browser graphical interface. The user can pick and choose BW data store objects to reverse-engineer from this interface. The KM uses the OdiSAPAbapExecute open tool to call ABAP code. The open tool must be installed prior to reverse-engineering.

In the reverse-engineering process, data targets, primary keys, foreign keys and index are reverse- engineered into an Oracle Data Integrator model.

Integration Process

Data integration from SAP is managed by the LKM SAP BW to Oracle (SQLLDR). This KM can be used for interfaces sourcing from SAP via ABAP and having a Staging Area located in an Oracle Database engine.

The KM first generates optimized ABAP code corresponding to the extraction required for a given interface. This code includes filters and joins that can be processed directly in the source SAP BW server. This ABAP program is uploaded and can be executed using the OdiSAPAbapExecute open tool to generate the extraction file.

The KM then transfers this extraction file to a preconfigured FTP server. This file is downloaded from this server using FTP, SFTP, SCP, and so forth to the machine where the Oracle Staging Area is located, and finally loaded using SQL*Loader to the Staging Area. The agent can also directly read the extraction file on the FTP server’s disk if the FTP server is installed on the ODI agent machine.

The rest of the integration process (Data quality check and integration) is managed with regular Oracle Data Integration KMs.

Knowledge Modules Reference Guide


Document info
Document views443
Page views446
Page last viewedMon Jan 16 13:40:58 UTC 2017