Direkt zum Seiteninhalt
SAP administrators can basically be found wherever SAP systems are used. These are now numerous industries and departments of companies. SAP systems can be found in accounting, costing, activity-based costing and controlling. In all these areas, they take care of the smooth functioning and development, thus helping the company to make internal processes more efficient and consequently save costs and resources.

Creating the master role: Now maintain the permissions that are the same for all affected employees. In the example shown above, I assign the "findepartment_r" role as an example the "F-02" transaction authorisation.
Update of the SAP system to newer versions
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.

A simpler option is to output the transactions used by the expert as a list and to obtain an overview of the task areas. The function block SWNC_COLLECTOR_GET_AGGREGATES is very suitable for exporting the used transactions in a list. As an alternative, one can directly use the workload monitor in the transaction code ST03N.

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

We use a standardised approach to determine your current security situation.

A negative consequence during the operational operation can be largely excluded.
Zurück zum Seiteninhalt