Release
MONITORING
SAP Basis ensures smooth operation of the SAP Basis system. The SAP Basis system is a kind of operating system of the R/3 system or SAP ERP. It includes the three layers database, application and presentation. In addition, Basis includes many SAP middleware programs and administration tools. With Basis SAP applications can be used compatible and independent of operating system and database and can be enriched with the necessary data.
There are the following reasons that may lead to the termination of this step: CANNOT_GET_OBJECT_LIST: The Object List for a Support Package could not be found because the Support Package does not exist. CANNOT_CHECK_LOCKS: An error occurred while detecting the locks of an object in the queue. OBJECTS_LOCKED_IN_REQUESTS: Objects found in unreleased jobs. Release these jobs before you resume playing. SCHEDULE_RDDIMPDP In this step the transport daemon (programme RDDIMPDP) is planned. There are the following reasons that may lead to the termination of this step: CANNOT_SCHEDULE_RDDIMPDP: The RDDIMPDP job could not be scheduled. Enter the transaction SM37 (job selection), enter the following parameters, and select Next: Job Name RDDIMPDP Username Start by Event SAP_TRIGGER_RDDIMPDP Select the job that was cancelled and view the job log.
SPRO Implementation Guide
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.
SAP Basis is responsible for the smooth operation of programs in the SAP system. It acts like an operating system for R/3 and subsequent releases including S/4HANA. Every operating system provides an environment in which programs can run, such as MS Office on Microsoft Windows. In the same way, the SAP Basis system with the NetWeaver and HANA platforms provides an environment in which SAP programs can run. In this context, the NetWeaver platform itself relies on server operating systems such as Windows and Linux.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
The website www.sap-corner.de offers many useful information about SAP basis.
Capacity must be built to provide the necessary space for pilot and research projects and to meet the increased demands.
And most Basis administrators only used it at all because SAP virtually forced them to use SolMan to download updates.