This appendix describes the privileges that are required for connecting to SAP System, how you can test the connection outside of ODI using a standalone java utility, and how to uninstall SAP components.
This appendix contains the following sections:
For more information about the SAP BW KMs see Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator.
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 BW Knowledge Modules:
The authorizations required for setting up the configuration for the RKM SAP BW and installing the required RFC programs to retrieve the metadata about SAP tables are the same as the authorizations required for the RKM SAP ERP.
See Section B.1.1, "Authorizations Required for RKM SAP ERP Setup" for more information.
The authorizations required for running a reverse-engineering using the RKM SAP BW are the same as the authorizations required for the RKM SAP ERP.
See Section B.1.2, "Authorizations Required for RKM Execution" for more information.
The authorizations required for using the LKM SAP BW to Oracle (SQLLDR) are the same as the authorizations required for the LKM SAP ERP to Oracle (SQLLDR).
See Section B.1.3, "Authorizations Required for LKM Execution" for more information.
The authorizations required for using the LKM SAP BW to Oracle (SQLLDR) in a production environment are the same as the authorizations required for the LKM SAP ERP to Oracle (SQLLDR). In such environment, the ABAP code generated by the LKM is not installed by the LKM but simply executed.
See Section B.1.4, "Authorizations Required for LKM Execution for Production" for more information.
In addition to the Connection Testing described in the Getting Started with SAP ABAP Adapter guide, a test can be performed outside of ODI using a standalone java utility. This test is the same for SAP ERP and SAP BW.
See Section B.2, "SAP Connection Test" for more information.
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:
Open a command window.
Go to the <ODI_HOME>/odi_misc directory.
Make sure that JAVA_HOME points to a supported JVM.
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.
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.
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>
Enter you SAP connection information, which you have received from your SAP administrator.
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).
Delete the ODI_SAP_CON_POOL.jcoDestination file after execution, as it contains the SAP login credentials.
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:
Start the SAP GUI.
Connect to the SAP systems you want to uninstall.
Go to the transaction SE80.
Select the package or development class option from the drop down box.
Enter ZODIBW_PCKG in the package or development class field.
Right-click the ZODIBW_PCKG object below the object name tab.
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.
Go to transaction SE10. Select Modifiable and Workbench Requests. Click Display.
Select the transport requests which have the ODI Objects and Release them.
Now repeat the steps 3 to 7 to delete Development Class.
Go to transaction SE01. Select Modifiable and Workbench Requests. Click Display. Release the Transport Request which has ZODIBW_PCKG.