MANAGED SERVICES
SPAM/SAINT - the update tools integrated in ABAP
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".
With the function module SWNC_COLLECTOR_GET_AGGREGATES one can determine the most important SAP Basis transactions. After all, each SAP Basis expert sees different transactions as important.
Training - Administration SAP HANA
The presentation layer is the top layer of the R/3 SAP Basis system and includes the communication with the user. Here, the data is graphically prepared for the user on the end device by means of software components from the application programs of the application layer. The presentation layer is the interface to the user (SAP GUI).
The presentation layer is the interface to the users. Through a graphical interface, users enter data or interact with data through the applications. This presentation layer exchanges data with the application layer.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
The establishment of technology architects also ensures that the overall picture is not left out of sight in the context of the SAP product portfolio.
Execute ABAP/Dynpro generation This option determines whether the programmes and screens shipped with the support packages should be generated during the commit.