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 includes the following sections:
For more information about the SAP ERP KMs see Connectivity and Knowledge Modules Guide for Oracle Data Integrator.
An 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, an SAP RFC user is sufficient.
These SAP user types can be used for the following operations:
Table B-1 Required SAP User Types
| Operation | Required SAP User Type |
|---|---|
|
RKM: Setup |
SAP Dialog user |
|
RKM: Reverse Engineering |
SAP Dialog user or SAP RFC user |
|
LKM: Development |
SAP Dialog user or SAP RFC user |
|
LKM: Production |
SAP Dialog user or SAP RFC user |
The following tables list the privileges required for using SAP ABAP Knowledge Modules:
Authorizations Required for LKM SAP ERP Upload (Background mode)
Authorizations Required for LKM SAP ERP Execution (Background mode)
Authorizations Required for LKM SAP ERP Upload (Dialog mode)
Authorizations Required for LKM SAP ERP Execution (Dialog mode)
Consider the following points while configuring the SAP privilieges:
S_DATASET is an authorization object that controls access to physical file, so you need to provide access to SAP directories & folder mounted path. The values provided here are sample paths, you need to provide your landscape directories path or provide *(all).
NR or (NR) means NOT REQUIRED.
The following SAP authorizations are required for first time installation of the RKM SAP ERP.
Note:
Developer key is required in this authorization.
| Object | Field Name | Value (4.6c) | Value (4.7) | Value (ECC 5) | Value (ECC 6) |
|---|---|---|---|---|---|
|
|
|
|
|||
|
|
|
||||
|
|
|
||||
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|||
|
|
|
||||
|
|
|
||||
|
|
|
|
|
||
|
|
|
|
|||
|
|
|
|
|
||
|
|
|
||||
|
|
|
||||
|
|
|
||||
|
|
|||||
|
|
|
|
|
||
|
|
|
The following SAP authorizations are required for reverse engineering the SAP models using RKM SAP ERP.
| Object | Field Name | Value (4.6c) | Value (4.7) | Value (ECC 5) | Value (ECC 6) |
|---|---|---|---|---|---|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|||
|
|
|
|
|||
|
|
|
|
The following SAP authorizations are required for running mappings using the SAP ERP LKMs in a SAP development environment when LKM option BACKGROUND_PROCESSING is set to true (recommended default).
Note:
Developer Key is required in this authorization.
| Object | Field Name | Value (4.6c) | Value (4.7) | Value (ECC 5) | Value (ECC 6) |
|---|---|---|---|---|---|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|||
|
|
|
||||
|
|
|
|
|||
|
|
|
|
|||
|
|
|
||||
|
|
|
||||
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
|
||
|
|
|
|
|||
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
The following SAP authorizations are required for running mappings using the SAP ERP LKMs in a SAP production environment when LKM option BACKGROUND_PROCESSING is set to true (recommended default).
| Object | Field Name | Value (4.6c) | Value (4.7) | Value (ECC 5) | Value (ECC 6) |
|---|---|---|---|---|---|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|||
|
|
|
|
|||
|
|
|
|
|||
|
|
|
||||
|
|
|
|
|||
|
|
|
||||
|
|
|
|
|
|
The following SAP authorizations are required for running mappings using the SAP ERP LKMs in a SAP development environment when LKM option BACKGROUND_PROCESSING is set to false (non-default).
Note:
Developer Key is required in this authorization.
| Object | Field Name | Value (4.6c) | Value (4.7) | Value (ECC 5) | Value (ECC 6) |
|---|---|---|---|---|---|
|
|
|
|
|||
|
|
|
||||
|
|
|
||||
|
|
|
|
|||
|
|
|
|
|||
|
|
|
||||
|
|
|
||||
|
|
|
|
|
|
|
|
|
|||||
|
|
|
||||
|
|
|
|
|||
|
|
|||||
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|||
|
|
|
The following SAP authorizations are required for running mappings using the SAP ERP LKMs in a SAP production environment when LKM option BACKGROUND_PROCESSING is set to false (non-default).
| Object | Field Name | Value (4.6c) | Value (4.7) | Value (ECC 5) | Value (ECC 6) |
|---|---|---|---|---|---|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|||
|
|
|
|
|||
|
|
|
||||
|
|
|
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:
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 Developer's Guide for Oracle Data Integrator.
In the Reverse Engineer tab of the SAP ERP Model, select the RKM SAP ERP Connect Test.
Save the model.
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. Please verify that the output of task "Test SAP Connection" contains Successfully connected to SAP System. If not, the connection test has failed and the connection problem must be analyzed.
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/sdk/lib 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/sdk/lib directory.
Launch the utility using the following command:
On Windows:
java -cp sapjco3.jar;odi-sap.jar oracle.odi.sap.km.test.JCoTest
On Linux/UNIX:
java -cp sapjco3.jar: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/sdk/lib folder.
For more information, see "Appendix C, SAP Stand-Alone Connection Test" in the Getting Started with SAP ABAP ERP Adapter for Oracle Data Integrator.
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_BASE and UPLOAD_ABAP_CODE set to true).
Delete the ODI_SAP_CON_POOL.jcoDestination file after execution, as it contains the SAP login credentials.
During first-time installation the RKM installs some ODI objects into the SAP system. This installation consists of two parts: some base objects and some RFCs. When the RKM options UPLOAD_ABAP_BASE and UPLOAD_ABAP_CODE are both set to true, the base objects and the RFCs are installed. Such full installation requires that no ODI SAP objects are installed in the SAP system.
See Uninstalling ODI SAP Components for information about how to uninstall ODI SAP Components if needed.
If the ODI objects installed into your SAP systems have been installed by RKM SAP ERP v32 or later, or RKM SAP BW v23 or later, there is no need for reinstalling the base objects and it is sufficient to update just the RFCs. Reinstalling the RFCs is achieved by executing a reverse engineering with the RKM option UPLOAD_ABAP_BASE set to false and RKM option UPLOAD_ABAP_CODE set to true.
For removing ODI connectivity from the SAP system, 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 ZODI_RKM_PCKG in the package or development class field. Note that for older installations the package name is ZODI_DEVCLASS.
Right-click the ZODI_RKM_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 ZODI_DEVCLASS.
Repeat the above steps for package name ZODI_LKM_PCKG. This applies only to the installations done by RKM SAP ERP v32 or later.