Skip to main content

Authorization Required for Run Only User – Transaction (TX)

The following section lists the required authorizations for Run Only user of Transaction (TX) when user is using SAP standard delivery. One of these sections and next section are applicable to most customers unless mentioned otherwise.

Authorization Object Function Group

 

What will be the impact if this access is missing
S_RFC SYST

 

Mandatory

 

SYSU

 

Mandatory if “Use NCo 3.0 Library” option is enabled in systems properties settings.

 

SDIFRUNTIME

 

Mandatory if “Use NCo 3.0 Library” option is enabled in systems properties settings.

 

RFC1

 

Critical. Workaround is possible

 

SBDC

 

Mandatory

 

STTF

 

User cannot read field values from transaction or cannot run in not-batch input mode - This is sparingly used feature of Process Runner and does not impact upload to most transaction.

 

SDTX See Note-1 below User will NOT get the message text when they RUN the transaction. Workaround is available. (Method 1)

 

SIGE See Note- 1 below User will NOT get the message text when they RUN the transaction. This access will be used if SDTX access is missing (Method 2)

 

BATG See Note- 1 below User will NOT get the message text when they RUN the transaction. This access will be used if SDTX and SIGE are missing. (Method 3)

 

BFHV

 

User will NOT be able to see the F4 help values which Process runner is retrieving using standard BAPI ‘BAPI_HELPVALUES_GET’. This access is required to use the F4 Help functionality which is available in Process Runner.

 

CVIN

 

User will NOT be able to see the F4 help values using standard BAPI ‘BAPI_HELPVALUES_GET’. This access is required to pass the authority check using FM ‘PLM_HELPVALUES_AUTHCHECK’.

 

LCO1

 

User will NOT be able to see the F4 help values using standard BAPI ‘BAPI_HELPVALUES_GET’. This access is required to pass the authority check using FM‘PARTNER_BAPI_F4_AUTHORITY’.

 

Authorization Object Activity What will be the impact if this access is missing
F_KNA1_GEN 03 (Display) User will NOT be able to see the F4 help values using standard BAPI ‘BAPI_HELPVALUES_GET’. This access is required to pass the authority check of BAPI ‘BAPI_HELPVALUES_GET’.
M_MATE_MAN 03 (Display) User will NOT be able to see the F4 help values using standard BAPI ‘BAPI_HELPVALUES_GET’. This access is required to pass the authority check of BAPI ‘BAPI_HELPVALUES_GET’.

 

Authorization Object

Object Type

Activity

This S_DEVELOP authorization is required only if (a) ECC6, Ehp5 or higher is in use AND (b) if you have already configured CCIMAILDIS field with value of X, E or F in SCC4 T-code AND (c) only for few specific situations as described in line below:

S_DEVELOP SCAT or ECSC 16 (Execute)

User cannot execute transaction in Non-Batch input mode Or cannot perform SAP to Excel function in Transaction mode. User will be presented with missing authorization help page. Either user disables this feature to continue or gets authorization mentioned in this line.

 

Authorization Object Table Table Authorization Group

 

S_TABU_DIS T100

S

S

User will not get the message text when they RUN the transaction. Workaround is available.

Note: When user runs a transaction in Process Runner, internally messages are captured in this function group. Transaction messages will not be fully expanded without this access. So either of these function groups should be maintained for user. Process Runner will automatically detect the access user has and will remember it. Simply providing one of these authorizations should be enough. If any user changes any of these security profiles for the other users, than user must perform “Reset” in Process Runner as described in Automatic Security Detection and Reset.

Was this article helpful?

We're sorry to hear that.