SAP Authorizations Best Practices Benefit from PFCG Roles Naming Conventions - SAP Basis

Direkt zum Seiteninhalt
Best Practices Benefit from PFCG Roles Naming Conventions
Do you need to integrate the S_TABU_NAM authorization object into your existing permission concept? In this tip, we show you the steps that are necessary to do this - from maintaining the suggestion values to an overview of the eligible tables. You have added the S_TABU_NAM authorization object to your permission concept, so that users can access the tables not only through the S_TABU_DIS authorization object, but also through S_TABU_NAM. This directly regulates access to the tables via table permission groups or, if access is not allowed through table permission groups, via the table permission (see Tip 73, "Use table editing authorization objects"). Do you want to identify the tables or created parameter transactions that allow access to only specific tables to maintain SU24 for these suggested values in the transaction? This makes it easier to maintain PFCG roles. Furthermore, a tool would be useful to give you an overview of the tables for which a user is entitled.

The SAP CO module is the module for classic controlling in a company. Part (the responsible area) of it is the control and analysis of costs. This also includes the control of the cost types and the cost rates that are incurred and posted in the company. Controlling then usually reports directly to the company management. It is supported by the tools from the SAP CO module, which can provide comprehensive evaluations and analyses. SAP CO can be subdivided into several further subareas. These include, for example, CO-PC (Product Cost Accounting), CO-PA (Profitability Analysis) or PCA (Profit Center Accounting).
Object S_BTCH_ADM (batch administration authorization)
Create a function block in the Customer Name Room. You can choose the supplied SAMPLE_INTERFACE_00001650 as the template. For us, it has proven itself, in the name of the new function block, the name BTE and the number of the template (here: 1650).

The path with the associated permission group DEVL contains the local temporary files of the ABAP Frontend Editor of the ABAP development environment (transactions SE38, SE80, SE24, etc.). The two paths with the ADMN permission group show how logically related paths can be grouped into a S_PATH permission check. The two entries with the FILE permission group show how paths for Windows can be completed in systems with application servers of different operating systems. The core.sem and coreinfo entries are required to write run-time errors in the SNAP snapshot table. The dev_ and gw_ entries allow you to view files from the developer trace and Gateway Log in the ST11 transaction. If the suggestion in the first entry of the table is too restrictive, you can choose the alternative in the following table. This entry only forces a permission check on S_PATH and the ALL permission group; You should, however, only grant such permission very restrictively.

Secure your go-live additionally with "Shortcut for SAP systems". You can assign necessary SAP authorizations quickly and easily directly in the system.

This implementation of the BAdIs complements the Business Transaction Event 1650 described in the second example.

Note that the PFCG transaction is actually executed, so the role is actually created in the system! Now maintain the permissions and organisation levels.
Zurück zum Seiteninhalt