Authorization Required for Designer User and Run Only User - Transaction (TX)
The following table has the list of required authorizations for Designer user and Run Only user of Transaction (TX) technology when insightsoftware Add-On Package is installed in user’s SAP system and Process Runner is setup to use this package only.
Note: Use this section only if you are advised to do so by insightsoftware. Otherwise follow the Authorization Required for Run Only User – Transaction (TX) and Authorization Required for Designer User - Transaction (TX) chapters.
| 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 property settings. |
|
SDIFRUNTIME | Mandatory if “Use NCo 3.0 Library” option is enabled in systems property settings. |
|
RFC1 | Critical. Workaround is possible. |
|
Y_SDTX | Mandatory (Please note if you implemented PAT file, then use Y_PROCESS_RUNNER_TX, Otherwise use custom Function Group that user created as per documentation that was provided. |
- If user was using Process Runner with SAP standard function modules and now using insightsoftware Add-On Package (i.e. /INNOWERA/PROR or Y_PROCESS_RUNNER_TX), user does not need to provide authorization for standard function groups SBDC and STTF as referenced in Appendix I and II above.
- Above three function groups are required for this Add-on Package. So, insightsoftware suggests that user revoke the rights for all other unnecessary standard RFC function groups including STTF, SBDC and SBDR. This will also ensure that no other programs or software which uses standard SAP function groups can access user’s SAP system using RFC.
Note: If any user changes any of these security profiles for the other user, than user must perform “Reset” in Process Runner as described in Automatic Security Detection and Reset.