File Transfer Configurations Considerations for SAP BW Integration

7-10 Oracle® Fusion Middleware Application Adapters Guide for Oracle Data Integrator

7.7 Considerations for SAP BW Integration

This section includes the following topics: ■ File Transfer Configurations ■ Controlling ABAP Uploading ■ Log Files ■ Limitation of the SAP BW Adapter

7.7.1 File Transfer Configurations

The ODI SAP adapter extracts data using ABAP programs. At the end of the extraction process these ABAP programs upload the data to a FTP server. For better performances this FTP server should be located on the same machine as the run-time agent. If the agent is not located on the same machine as the FTP server, it will download the file from the FTP server before loading it to the staging area using SQLLoader. This download operation is performed using FTP, SFTP or SCP. Figure 7–1 Configuration 1: FTP Server is installed on an ODI Agent machine This image shows the file transfer configuration where the FTP server is installed on an ODI Agent machine. The configuration shown in Figure 7–1 is used, when FTP_TRANSFER_METHOD = NONE. In this configuration the following data movements are performed: 1. The ABAP program extracts the data and uploads the data file to the FTP server. 2. SQLLoader reads locally the data file and loads the data into the Oracle staging area. This configuration requires the following Topology settings: 1. Create a File data server pointing to the FTP server: ■ Host Data Server: FTP server host name or IP address. ■ User: User name to log into FTP server. ■ Password: Password for the user. 2. 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: ■ Directory Schema: Path on the FTP server for uploading SAP extraction files. SAP ABAP BW 7-11 ■ Directory Work Schema: Local path on the FTP server’s machine containing the SAP extraction file. The agent and SQLLoader read the extraction files from this location. Figure 7–2 Configuration 2: FTP Server is not installed on ODI Agent machine This image shows the file transfer configuration where the FTP server is not installed on an ODI Agent machine. The configuration shown in Figure 7–2 is used, when FTP_TRANSFER_METHOD is FTP, SFTP or SCP. In this configuration the following data movements are performed: 1. The ABAP program extracts the data and uploads the data file to the FTP server. 2. The ODI agent downloads the file from the FTP server into the directory given by KM Option TEMP_DIR. 3. SQLLoader reads the data file from this TEMP_DIR and loads the data into the Oracle staging area. This configuration requires the following Topology settings: 1. Create a File data server pointing to the FTP server: ■ Host Data Server: FTP server host name or IP address. ■ User: User name to log into FTP server. ■ Password: Password for the user. 2. 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: ■ Directory Schema: Path on the FTP server for uploading SAP extraction files. ■ Directory Work Schema: undefined; this path is left blank, as data files are never accessed directly from the FTP servers file system.

7.7.2 Controlling ABAP Uploading