This appendix includes the following sections:
For more information about the SAP BW KMs see Connectivity and Knowledge Modules Guide for Oracle Data Integrator.
For connecting to the SAP system a SAP dialog user is required for RKM installation and LKM execution during development. A SAP RFC user is not sufficient.
This user has to 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.
Later for RKM execution and LKM execution in production a SAP RFC user is sufficient.
These SAP user types can be used for the following operations:
Table A-1 Required SAP User Types
|
The following tables list the privileges required for using SAP BW Knowledge Modules:
Consider the following points while configuring the SAP privileges:
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 authorizations are required for RKM SAP BW setup.
Note:
Developer Key is required in this authorization.
Object | Field Name | Value (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for RKM SAP BW execution.
Object | Field Name | Value (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for LKM SAP BW execution.
Note:
Developer Key is required in this authorization.
Object | Field Name | Value (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for LKM SAP BW execution in production.
Object | Field Name | Value (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for LKM SAP BW execution as background process.
Note:
Developer Key is required in this authorization.
Object | Field Name | Value (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for LKM SAP BW execution as background process in a SAP production environment.
Object | Field Name | Value (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In addition to the Connection Testing described in the Getting Started with SAP ABAP BW Adapter for Oracle Data Integrator, 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 SAP Connection Test for more information.