SAP job control
Roles
SAP Basis is also known as module BC or application Basis. In this context, SAP Basis refers to all transactions, programs and objects that control the functions of the overall system. This includes, among other things, user and authorization management as well as the configuration of interfaces via RFC.
This enhances the capabilities of SAP HANA base administrators and increases the level of service they should provide. Your Basis team can more easily fine-tune your data replication strategy to meet demanding disaster recovery and high availability standards.
On www.sap-corner.de you will also find useful information about SAP basis.
INTRODUCTION
Especially in larger companies, which also have multiple locations in different countries, it is often necessary to grant different employees the same permissions for different levels of organisation, such as accounting circles. In order to make maintenance and maintenance of the system easy in such a situation, it is useful to set the inheritance principle for SAP permissions. How does SAP Permissions Inheritance work? An inheritance is always about a master object passing certain properties to a derived (sub) object. Therefore, these properties do not need to be maintained several times. Also, changes to the master object are passed directly to the derived objects. This allows easier maintenance and drastically minimises the error rate. In the case of SAP Permission Inheritance, the required permissions are bundled in a Upper or Master role. Only the organisational levels have to be maintained in the roles derived from them. The permissions are automatically pulled from the master role. Create Inheritance for SAP Permissions The following shows how to create and use inheritances for SAP permissions. This requires only two steps: Creating a master role and defining derived roles. Step 1: Create a master role Inheritance always requires a parent role, because all properties are inherited from it. If this role, in which all shared permissions are bundled, is missing, the first step is to create this master role. To do this, open the PFCG transaction and enter the desired name of the master role in the Name field. It is possible to identify master and derived roles by using naming conventions. The "Single Role" button will then be used to create the desired role. In the following example I create the master role "findepartment_r".
If you want to evaluate for which tables a logging takes place, the table DD09L is suitable for this. The column "Log" shows you for which tables changes are logged.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
A customized cloud for the most diverse requirements of medium-sized companies is an important backbone for business success.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
When looking at the result, in addition to limiting the number of transactions that can be entered, another drawback of this variant becomes apparent: Although both associated roles are displayed, at first glance it is not possible to see which transaction is contained in which role.