B Additional Information for SAP ABAP ERP Adapter

B.1 SAP ABAP ERP Required Privileges

A SAP dialog user is required for connecting to the SAP system, for the RKM installation, and for the LKM execution during development. A SAP RFC user is NOT sufficient. During development, this user must have a developer license key. License keys can be retrieved from http://service.sap.com. Any execution attempts without this developer license key will lead to failure and may cause the need for clean-up operations.For RKM and LKM execution in production, a SAP RFC user is sufficient. The following sections list the privileges required for using SAP ERP Knowledge Modules:

• Authorizations Required for RKM SAP ERP Setup

• Authorizations Required for RKM Execution

• Authorizations Required for LKM Execution

• Authorizations Required for LKM Execution for Production

B.2 SAP Connection Test

This connection test should be performed after configuring the SAP ABAP data server in the topology.

This test preforms the following operations:

• It establishes a test connection to the configured SAP system.

• It validates the proper setup of SAP JCo by displaying the About dialog.

This test is performed using an RKM called RKM SAP ERP Connection Test. This KM does not perform any reverse operation. It simply runs the connection test.

To run the connection test:

1. Create an SAP ERP Model based on the SAP ABAP technology and on the SAP ABAP logical schema using the standard procedure, as described in "Creating a Model" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

2. In the Reverse tab of the SAP ERP Model, select the RKM SAP ERP Connect Test.

3. Save the model.

4. Click Reverse-Engineer to start the reverse.

Within a few seconds, the SAP JCo About dialog should appear. If not, review the session execution log in the Operator Navigator.

B.3 SAP Stand-Alone Connection Test

In addition to the Connection Testing, a test can be performed outside of ODI using a standalone java utility. This utility is available with the Standalone agent.

To use a standalone java utility to test the connection:

1. Open a command window.

2. Go to the <ODI_HOME>/odi_misc directory.

3. Make sure that JAVA_HOME points to a supported JVM.

4. Make sure that you have installed SAP Java Connector and that the sapjco3.jar and the sapjco3 library are in the <ODI_HOME>/odi_misc directory.

5. Launch the utility using the following command:

   java –cp sapjco3.jar;../oracledi/agent/lib/odi-sap.jar oracle.odi.sap.km.test.JCoTest

   This command generates a ODI_SAP_CON_POOL.jcoDestination file in the folder <ODI_HOME>/odi_misc folder.

6. Use a text editor to open the ODI_SAP_CON_POOL.jcoDestination file. This file should look as follows:

   #for tests only!
   jco.client.lang=EN
   jco.destination.peak_limit=10
   jco.client.client=800
   jco.client.passwd=<SAP Password>
   jco.client.user=<SAP User>
   jco.client.sysnr=00
   jco.destination.pool_capacity=5
   jco.client.ashost=<SAP Application Server>
   

7. Enter you SAP connection information, which you have received from your SAP administrator.

8. Launch the utility using the same command. The utility uses the file that you have edited, and outputs the test results or the possible issues.

   In addition to just testing the SAP connection, the utility will also validate the existence of certain Function Modules required for the RKM. These are installed during first execution of the RKM (UPLOAD_ABAP = Yes).

9. Delete the ODI_SAP_CON_POOL.jcoDestination file after execution, as it contains the SAP login credentials.

B.4 Uninstalling ODI SAP Components

In case of upgrading to a newer ODI SAP Connector release or for permanently removing ODI connectivity, please follow the steps described in this section.

Please note that this will delete ALL components including generated extractor programs.

To upgrade to a newer ODI SAP Connector release or to permanently remove the ODI connectivity:

1. Start the SAP GUI.

2. Connect to the SAP systems you want to uninstall.

3. Go to the transaction SE80.

4. Select the package or development class option from the drop down box.

5. Enter ZODI_DEVCLASS in the package or development class field.

6. Right-click the ZODI_DEVCLASS object below the object name tab.

7. Select Delete in the drop down menu and delete the development class.

   If it does not allow deleting the development class individually, delete all the objects one by one and then delete the development class.

8. Go to transaction SE10. Select Modifiable and Workbench Requests. Click Display.

9. Select the transport requests which have the ODI Objects and Release them.

10. Now repeat the steps 3 to 7 to delete Development Class.

11. Go to transaction SE01. Select Modifiable and Workbench Requests. Click Display. Release the Transport Request which has ZODI_DEVCLASS.