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 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 |
The following tables list the privileges required for using SAP ABAP 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 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) |
---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|