This process is described in the Using Open Tools section of the Oracle Data Integrator Tools Reference Manual. The class name for this open tool is: oracle.odi.sap.km. OdiSapAbapExecute
Working with the SAP ABAP BW KMs
The Oracle Data Integrator SAP ABAP BW KMs enable to reverse and extract data from SAP BW. To use SAP BW data in your Oracle Data Integrator integration projects, you must:
Define the Topology.
Set up the Project.
Create a model and reverse-engineer SAP BW data targets.
Design an Interface using the LKM SAP BW to Oracle (SQLLDR). Use the SAP BW data store
object(s) as source of such an integration interface.
Defining the Topology
You must perform the following operations after installing or upgrading your Oracle Data Integrator version:
Connect to Topology Manager.
If the SAP ABAP technology does not exist in your Master Repository, import the SAP ABAP technology in Synonym INSERT_UPDATE mode from the /impexp folder.
Perform an upgrade of the Master Repository. Refer to the Oracle Data Integrator Installation Guide on OTN for more information on the Master Repository upgrade process.
In Topology Manager, open the JavaBeanShell technology and check on the Language tab that the JYTHON language is listed. If not, add it.
Create a File data server pointing to an existing FTP server into which the extraction file will be pushed from SAP and picked up for SQL*Loader. Set the parameters for this data server as follows: Host (Data Server): FTP server IP host name or IP address. User: Username/login Id for FTP server. Password: Password for the username/login Id.
In this File data server create a Physical Schema representing the folder in the FTP host where the extraction file will be pushed. Specify the Data and Work Schemas as follows: Data Schema: Path on the FTP server to upload or download extraction files from the remote location. This path is used when uploading extraction files from the SAP BW system into the FTP server. It is also used by a remote agent to download the extraction files. Note that this path must use slashes and must end with a slash character. Work Schema: Local path on the FTP server’s machine. This path is used by an agent installed on this machine to access the extraction files without passing via the FTP server. This access method is used if the FTP_TRANSFER_METHOD parameter of the LKM SAP BW to Oracle (SQLLDR) is set to NONE. As Work Schema is an OS file name, slashes/ backslashes should be used according to OS. Path names need to end on slash/ backslash.
Path names given on Data and Work schemas are not necessarily the same: the FTP service may provide access to a FTP directory named /sapfiles while the files are can be stored locally in c:\inetpub\ftproot\sapfiles.
Refer to the File Transfer Configurations section in the SAP ABAP chapter of the Oracle Data Integrator Knowledge Modules Reference Guide.
Knowledge Modules Reference Guide