Authorizations Required For Scenario-Based Authorizations
To use scenario-based authorization, assign developers and administrators the relevant authorizations.
Start Authorizations
Assign the authorization object S_TCODE with the transactions as listed in the following table.
|
Transaction |
Description |
Role |
|
|---|---|---|---|
|
Developer |
Administrator |
||
|
SACF |
For developing scenario definitions and productive scenarios |
Yes |
No |
|
SACF_COMPARE |
For creating productive scenarios from scenario definitions |
Yes |
Yes |
|
SACF_INFO |
For an overview of all scenarios |
Yes |
Yes |
|
SACF_TRANSFER |
For file-based transport of scenario definitions and productive scenarios |
Yes |
Yes |
Development Authorizations
Assign the authorization object S_DEVELOP with the object types as listed in the following table. Available activities are 02 (Change), 03 (View), and 06 (Delete).
|
Object Type |
Description |
Role |
|
|---|---|---|---|
|
Developer |
Administrator |
||
|
SUCD |
Scenario definition |
Yes |
No |
|
SUCC |
Productive scenario |
Yes |
Yes |