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
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 |
Testing ODI Generated Extraction RFCs |
SAP Dialog user or SAP RFC user |
The following tables list the privileges required for using SAP BW Knowledge Modules:
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 authorizations are required for first time installation of RKM SAP BW.
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 first time installation of RKM SAP BW.
Object | Field Name | Value (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for running the mappings using SAP BW 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 (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for running the mappings using SAP BW LKMs in a SAP production environment when LKM option BACKGROUND_PROCESSING
is set to true
(recommended default).
Object | Field Name | Value (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for running the mappings using the SAP BW 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 (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for running the mappings using the SAP BW LKMs in a SAP production environment when LKM option BACKGROUND_PROCESSING
is set to false
(non-default).
Object | Field Name | Value (BW 3.5) | Value (BI 7.0) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|