A SAP ABAP BW Required Privileges
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:
A.1 Important points to consider
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.
A.2 Authorizations Required for RKM SAP BW Upload
The following SAP authorizations are required, only in rare cases when explicitly requested by Oracle product support. For standard installations, these authorizations are not required.
Note:
Developer Key is required in this authorization.
| Object | Field Name | Value (BI 7.0) | Value (BI 7.5) |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A.3 Authorizations Required for RKM SAP BW Execution
The following authorizations are required for RKM SAP BW execution.
| Object | Field Name | Value (BI 7.0) | Value (BI 7.5) |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A.4 Authorizations Required for LKM SAP BW Upload (Background & Foreground)
The following authorizations are required for LKM SAP BW execution in a SAP development environment.
Note:
Developer Key is required in this authorization.
This section contains authorizations for both background and foreground executions.
| Object | Field Name | Value (BI 7.0) | Value (BI 7.5) |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A.5 Authorizations Required for LKM SAP BW Execution (Background & Foreground)
The following authorizations are required for LKM SAP BW execution in a SAP production environment.
This section contains authorizations for both background and foreground executions.
| Object | Field Name | Value (BI 7.0) | Value (BI 7.5) |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|