A SAP ABAP ERP Required Privileges
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.
Important points to consider
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.
Authorizations Required for RKM SAP ERP 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.
It is not required in TR-based installation.
Note:
Developer key is required in this authorization.
Object | Field Name | Value (ECC6-EHP3) | Value (ECC6-EHP7) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
S_CTS_SADM |
CTS_ADMFCT |
NR |
TABL |
S_CTS_SADM |
DESTSYS |
NR |
|
S_CTS_SADM |
DOMAIN |
NR |
* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
S_TABU_NAM |
ACTVT |
NR |
02, 03 |
S_TABU_NAM |
TABLE |
NR |
* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
S_PROGRAM |
P_ACTION |
NR |
BTCSUBMIT, SUBMIT, VARIANT |
S_PROGRAM |
P_GROUP |
NR |
* |
S_SYS_RWBO |
ACTVT |
NR |
01, 02, 03, 05, 06, 23 |
S_SYS_RWBO |
DESTSYS |
NR |
* |
S_SYS_RWBO |
DOMAIN |
NR |
'' |
S_SYS_RWBO |
TTYPE |
NR |
DTRA |
|
|
|
|
|
|
|
|
S_IDOCDEFT |
ACTVT |
NR |
3 |
S_IDOCDEFT |
EDI_CIM |
NR |
|
S_IDOCDEFT |
EDI_DOC |
NR |
|
S_IDOCDEFT |
EDI_TCD |
NR |
|
Authorizations Required for RKM SAP ERP Execution
The following SAP authorizations are required for reverse engineering the SAP models using RKM SAP ERP.
Object | Field Name | Value (ECC6-EHP3) | Value (ECC6-EHP7) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Authorizations Required for LKM SAP ERP Upload
The following SAP authorizations are required for running mappings using the SAP ERP LKMs in SAP development environment with Upload ABAP Option Enabled.
Note:
Developer Key is required in this authorization.
Object | Field Name | Value (ECC6-EHP3) | Value (ECC6-EHP7) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* |
|
|
|
* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Authorizations Required for LKM SAP ERP Execution
The following SAP authorizations are required for running mappings using the SAP ERP LKMs in a SAP production environment, when LKM option Upload ABAP Code is disabled (QA or Production).
Object | Field Name | Value (ECC6-EHP3) | Value (ECC6-EHP7) |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* |
* |
|
|
SAPLSLOG*, SAPLSTRF*, SAPLZODI*, ZODI*, SAPLZODI_FGR_PROD* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|