X hits on this document

324 views

0 shares

1 downloads

0 comments

93 / 131

SAP ABAP ERP

Introduction

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

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

Overview

RKM SAP ERP enables Oracle Data Integrator to connect to SAP ERP system using SAP JCo libraries and perform a customized reverse engineering of SAP metadata.

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

Overview of the SAP ABAP Integration Process

Reverse-Engineering Process

Reverse-engineering is using the RKM SAP ERP. This knowledge module automatically installs the required RFC programs to retrieve the metadata about SAP tables. It can extract the list of SAP tables and display it in a tree Metadata Browser graphical interface. The user can select the list of tables to reverse-engineer from this interface. To call the uploaded ABAP code, the KM uses the OdiSAPAbapExecute open tool that must be installed prior to reverse-engineering.

In the reverse-engineering process, tables, 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 ERP 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 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, etc.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.

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

Knowledge Modules Reference Guide

93/131

Document info
Document views324
Page views327
Page last viewedSat Dec 03 17:49:07 UTC 2016
Pages131
Paragraphs3942
Words42855

Comments