SAP Basis Usage Procedure Logging in SAP Solution Manager

Direkt zum Seiteninhalt
Usage Procedure Logging in SAP Solution Manager
Active monitoring
SAP lockout issues: Call the SM12 transaction and make sure that there are no programmes named RDDIMPDP. For more information, see Note 11677. ADDON_CONFLICTS_? This step checks to see if there are conflicts between objects in the queue and add-ons installed. If there are such conflicts, SPAM will cancel and prompt you to play the appropriate Conflict Resolution Transports (CRTs).

This option is useful if several transactions are to be checked simultaneously for their existing assignment to a particular user. This variant must first identify all roles that have already been assigned to the user. This is done in the transaction SE16N by entering the table AGR_USERS. In addition, the limit of the maximum hit number can be set in this image. The user concerned must now be entered here. Furthermore, the output should be limited to the roles only. After the query is executed, all the roles assigned to the previously entered user are displayed. These are now completely marked and copied. Then in the transaction SE16N a step back is taken and this time the table AGR_1251 is selected. Now all the roles that have been copied previously are inserted here. In addition, the object S_TCODE and the transactions to be searched for are filtered. Warning: When entering transaction codes, be sure to be case-sensitive! At this point, the output can also be limited to the roles and object values (in this case, the transactions). After the query is executed, the transactions entered will now show those that the user can already perform. In addition, the role assigned to the transaction is shown. In conclusion, the SUIM is only partially suitable for identifying certain transactions with user assignment. Although the search using the S_TCODE permission object also allows you to view multiple transactions. However, since the result is missing the assignment of transactions considered to roles, the SUIM transaction can only be usefully used to check a single transaction for its existing assignment to a particular user.
SE24 Class Builder
SAP Basis refers to the IT underlying the SAP system. It includes various middleware programs and tools and is responsible for the smooth operation of the SAP system.

In order to reduce the complexity of the SAP basis operation and to accelerate and simplify the tasks of the SAPBasis and to create free capacities, standardisation and automation of the existing activities is required. Details can be found in chapters 7.7 and 9.5 of the Master's thesis.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.

In addition, most business processes are mapped in such a system and offer an attack surface for sabotage.

STEP 3: DETERMINATION OF THE OBJECTIVES The mission and vision of service providers will be determined in the framework of the setting of the objectives.
SAP Corner
Zurück zum Seiteninhalt