FAQs on Execution Type Behavior of Processes and SAP Systems
This topic answers the frequently asked questions regarding the behavior of Processes and SAP Systems in the desktop product when you configure Execution Type in the Control Panel.
Execution Type Behavior of Processes and SAP Systems
Processes (TCode)
| Permitted actions | User Role | Result |
|---|---|---|
| Record | Designer | Can record |
| Record | Run Only | Cannot record |
| Run | Designer | Can run |
| Run | Run Only | Can run |
| Record + Run | Designer | Can record and run |
| Record + Run | Run Only | Can run but cannot record |
SAP Systems
| Permitted actions | User Role | Result |
|---|---|---|
| Record | Designer | Can record |
| Record | Run Only | Cannot record |
| Run | Designer | Can run |
| Run | Run Only | Can run |
| Record + Run | Designer | Can record and run |
| Record + Run | Run Only | Can run but cannot record |
Note: Types are independent. In SAP systems, if only Record is defined, Run is not allowed unless explicitly added.
Combination Scenarios
- TCode FB50 (Run)+ SAP System ECC6 (Record) → User cannot run FB50 on ECC6.
- SAP system ME8 (Test Run + Debug) + TCode AS02 (Run) → User can Test Run and Debug on ME8 but cannot Run AS02.
Execution Behaviour of Process and SAP System in Groups
-
Same Process/SAP System (Allow and Block) with Multiple Execution Types in One Group.
Group Settings: Allow all defined Process/SAP system is enabled.
Outcome:
- User will be allowed access to all defined SAP systems and processes.
- Even if some are blocked, the Allow all setting overrides the block.
-
Same Process/SAP System Assigned to Two Groups (Allow in One, Block in Another)
User is part of both groups.
Outcome:
- User will be allowed access because being in a group where it's allowed takes precedence.
- Execution Types: All defined types across groups are combined.
- Example: If MM02 is allowed with Test in one group and Error Run in another, the user gets both.
- If Run is not defined in any group, the user won’t get it.
-
Same Process with Different Delay Calls and Thread Values with Multiple Execution Types
Group Setting: Allow all the processes defined in Cloud Hub control panel is enabled.
Outcome:
- Threads: User gets the maximum thread value defined for that process.
- Delay Between Calls: User gets the maximum delay defined for that process.
- These values are per process, not across all processes.
-
Same SAP System with Different RFC Settings and Execution Types
Group Setting:Allow all the SAP System defined in Cloud Hub control panel is enabled.
Outcome:
- RFC: If one definition enables and another disables RFC, RFC will be enabled.
- Execution Types: Combined per SAP system.
- Example: If ME8 has Test Run in one group and Run in another, the user gets both.
Execution Behaviour of Process and SAP System in Older Versions
Same Process/SAP System with Mixed Settings (Allow, Block, Different delays/Threads and Allow RFC) in Version 25.1 and Previous Versions (with Cloud Changes)
- Execution type restrictions do not work on the product side.
- If a Process/SAP system is defined multiple times with different execution types:
- The system will take the first record from the list.
- All settings (threads, delay, RFC, etc.) from that first record are applied.
- Subsequent entries are ignored.