What will be the SAP Basis trends in the next few years?
ORGANISATION IN CHANGE
What are the requirements and benefits of a modern identity management system (IDM) in the GRContext and what should be taken into account in application processes? Modern companies need to be able to effectively control their employees' access and system permissions to ensure optimal corporate control and monitoring. This need can also be inferred from legal requirements. IDM is the user and permission management within an organisation. These systems are an essential part of the internal control system. This includes the continuous monitoring and allocation of access possibilities as well as the systematic securing of functional separation (SoD - Segregation of Duties) in the IT systems. This is primarily intended to better manage relevant business and financial risks and to prevent criminal acts. The management of user and permission structures must ensure that, when the roles and responsibilities change, the privileges of the employees concerned in the systems are adjusted. Failure to do so will result in a multi-department employee having extensive privileges that can be critical in combination. Trust is good, control is better In order to avoid employees being entitled beyond your area of competence, user data and permissions must be continuously adjusted to the current requirements. It therefore makes sense to regularly carry out a recertification process in which the role owner and the manager sign off in compliance with the four-eye principle that the employee is entitled to the current privileges or may have to be deprived of rights from previous activities. Provisioning as a central function of the IDM Provisioning components form a central function of IDM systems, which provide users with individual access rights for the required IT resources according to their task.
Application layer: The application layer is the central component of the SAP ERP system and is therefore also referred to as the base system. All applications and calculations are executed here. The application layer communicates with both the database layer and the presentation layer. On the one hand, it requests data from the database layer, processes it and then passes it on to the presentation layer. On the other hand, data that is newly entered in the presentation layer is passed on to the database layer and stored there.
Planning & Design
If table logging is active in your system, you can specify which tables are to be logged in transaction SE13. For an active logging it is necessary to set the flag "Log data changes".
The Advanced Memory thus contains mainly user contexts of different work processes, if these cannot be loaded completely into the roll area. Since the storage area is accessible for all work processes, the work processes can also access external user contexts that lie here. In addition, the Advanced Memory contains a global area where data can be stored independently of user contexts. The extended memory size is determined by the values of em/initial_size_MB and em/global_area_MB. The first parameter determines the size of the storage area in which user contexts can be stored, and the second determines the size of the global area. Parameters for Private Storage Last but not least, there is the private storage, which is only used when the user context of a work process has used up all the other storage areas available to it, i.e. its share of the extended memory and its rolling area. In this case, the workprocess goes into PRIV mode. A workprocess in private mode is bound to its current user context and will not become free for other tasks until the current request is completed. If it has used up all the private memory allocated to it, the workprocess will then be restarted and the memory released. This behaviour is controlled with the abap/heaplimit parameter. At times, the user context may exceed the value of abap/heaplimit. The parameters abap/heap_area_total, abap/heap_area_dia and abap/heap_area_nondia define an upper limit for private storage. The abap/heap_area_total parameter defines how much private storage all workprocesses can use in total. The parameters abap/heap_area_dia and abap/heap_area_nondia, on the other hand, determine how much private storage a single (non-)dialogue workprocess can use.
"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.
There was even a case where the SAP environment required a review of the data center power and cooling.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
The comparison can be done in any client.