Authorization Required for Designer User - Transaction (TX)
The following table has the list of required authorizations for Designer user who will record or design a new process and also run process.
- To Run a Process: Same as Authorization Required for Run Only User – Transaction (TX)
- To Design (record) a new Process, you need additional access as follows:
| Authorization Object | Function Group | What will be the impact if this access is missing |
|---|---|---|
| S_RFC | SBDR | User cannot add dynamically record and create new transaction process. Workaround is possible with alternative authorization or with file based import/export method. |
|
STTM |
User cannot record special controls within Transaction. There are some special SAP control framework objects like tree view, ALV grid etc. provide by SAP for some transactions, to record and playback these control in static mode, Process Runner provides an option during recording Record Controls (static recording only). If user selects this option and if STTM access is not assigned to the user, Process Runner will stop and display authorization error. User will either need STTM access or can continue recording without the “Record Controls…” option. |
|
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. |
|
SDIFRUNTIME |
User will not get field description of recorded process. Process file will still work fine. This is good to have feature. On failure, Process Runner automatically disables this feature for next call for that user. If SDTX and S_TABU_DIS on T100 are not possible, this authorization will serve as a backup to extract field description. Mandatory if you are using Process Runner DB. Irrespective to which RFC library you are using. |
| Authorization Object | Table | Table Authorization Group |
|
|---|---|---|---|
| S_TABU_DIS | DD03M | &NC& | User will not get field description of recorded process. On failure, Process Runner automatically disables this feature for next call for that user. Workaround is possible with SDIC access in S_TABU_DIS or SDIFRUNTIME (see 2nd line above). |
|
D020T | SS | User will not get field description of recorded process. On failure, Process Runner automatically disables this feature for next call for that user. |
Note: If you change 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.