Tightening Authorizations on Existing Code (New)

With this method, you can create a switchable detour around code for which you need to tighten the authorizations. This enables you to enhance your application without completely disrupting your current processes, giving you time to plan for a redesign.

Some reasons why you must build such a detour in your application include the following:

When you created your application, you did not cover all possible use cases.
Legal requirements have been tightened.
New technical advances provide the means to bypass your existing security concept.

As a developer, you modify your application to cover scenarios for which your want to tighten the authorizations. You define these scenarios with a development object, namely a scenario definition. The scenario definition includes the scenario objects to be checked or ignored in the scenario. SAP can deliver scenario definitions with new developments. Every SAP scenario refers to an SAP Note with a scenario description.

As an administrator, you decide when and how the scenario runs. Until a scenario is active, the application retains its old behavior. When you activate a scenario, you can override the settings to meet your needs. You can then transport the scenario as a customizing object through your system landscape.