This appendix lists the required privileges for accessing the SAP system using 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.
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:
The following authorizations are required for setting up the configuration for the RKM SAP BW and install the required RFC programs to retrieve the metadata about SAP tables.
| Object | Field Name | Value |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Footnote 1 For SAP BW 7.0 only. Not for SAP BW 3.5.
The following authorizations are required for running a reverse-engineering using the RKM SAP BW.
| Object | Field Name | Value |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RSICUBEOBJ |
|
|
|
RSINFOAREA |
|
|
|
RSINFOCUBE |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Footnote 1 For SAP BW 7.0 only. Not for SAP BW 3.5.
The following authorizations are required for using the LKM SAP BW to Oracle (SQLLDR). This set of authorization is needed to install the ABAP code generated by the LKM and execute it.
| Object | Field Name | Value |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for using the LKM SAP BW to Oracle (SQLLDR) in a production environment. In such environment, the ABAP code generated by the LKM is not installed by the LKM but simply executed.
| Object | FIeld Name | Value |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following authorizations are required for manual testing of ODI generated extraction RFCs e.g. in SE37.
| Object | FIeld Name | Value |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|