SAP Integration Process Background

Oracle Data Integrator creates an ABAP program to extract the data from SAP into a file and then transfers the file to a FTP Server or Shared File system. The ABAP program is generated based on the mappings in the import format and options defined in the rule. The ABAP program is created and uploaded to SAP system when you run a data load rule. In the SAP deployment, ABAP programs are created and modified in a development environment and locked from modification in the production environment.

To support this requirement, ODI provides an option UPLOAD_ABAP_CODE in the SAP Load Knowledge Module. This option is set to "Yes" in a development environment, and "No" in a production environment. The ABAP programs are transferred from development to production using SAP Transport requests.

Because the ABAP code that is run in a production environment is not modified, users should create the import format in the exact format as the development environment. In addition, there are options in the data rule that impact the logic of the ABAP program. These options must be set to the same value as they are set in the development environment. Changing these options in the data rule in a production environment does not have any impact on the extraction process. If changes are required to these options, make them in the development environment and the ABAP code transported to the production environment. The options that impact the ABAP code generation are noted in the SAP adapter sections.