SAP Basis SUIM User information system

Direkt zum Seiteninhalt
SUIM User information system
RFC Security, Science-Fiction and Theatre
SAP Basis Administration Batch Control Job Control A large proportion of batch jobs run at night, while IT systems are available for dialog and online applications during the day. Meanwhile, web applications demand computer capacity around the clock. Even dialog systems are no longer in operation only from 8 a.m. to 6 p.m., but between 7 a.m. and 10 p.m. or longer. The time window for administration tasks is increasingly shifting toward transaction processing. This leaves less and less time for mission-critical batches, which can lead to disruptions and terminations. Whereas batch processing used to be a mainframe domain, companies today usually have to control background processing in heterogeneous operating system environments and client-server applications. For this reason, cross-platform, integration-capable job schedulers that can respond to unplanned events are in demand.

In every company with several SAP systems, there is a person responsible for the complete SAP Basis topics, usually there is even a separate department for this. This person ensures the trouble-free operation of the SAP systems. The person responsible also accompanies maintenance work or upgrades and intervenes in special situations, such as poor performance. Even for companies that hand over operation of the SAP Basis to an external service provider, there are often tasks from the user and authorization management environment at this point.

On www.sap-corner.de you will also find useful information about SAP basis.
Cloud services SAP (SCC, SCI, HCI)
The Log function displays logs for SPAM steps using the tp transport control programme. After successfully inserting the queue, you should always check these logs. Associating the SPAM steps with log files Step Log file DISASSEMBLE_PATCH Generate Cofile TEST_IMPORT Testimport IMPORT_OBJECT_LIST Commandfile Import DDIC-IMPORT DD-Import IMPORT_PROPER DD-Activation Import ADO-Import Verification Versions Method Execution ABAP/Dynpro Generation Procedure To get to the log display, select Image Jump Log Queue. Importance of Return Codes Return-Code Meaning 0 or 4 System information and warnings Warnings are generally uncritical for the system. However, you should check them anyway, as in rare cases follow-up errors may occur. Larger 4 Serious errors that must be fixed before you can successfully complete the commit. Confirm Queue Usage Confirm the successful insertion of the Queue in your system. This ensures that additional support packages can be used in the future. Without this confirmation, it is not possible to insert additional support packages. If you have not yet confirmed successful support packages, you will be prompted to confirm these support packages when upgrading your system. Prerequisites You have successfully imported one or more Support Packages. Procedure Confirm successful insertion of the Support Packages into your system with the Support Package.

Regular maintenance tasks or the standard procedures must be described and defined to build checklists based on them and to control compliance with this standard. The SAPSolution-Manager can also support this as a tool of SAP e.g. through the Guided Procedures. In this context, it is also necessary to document the functionality of an underlying application and thereby determine what testing and monitoring activities are necessary. This is a reconciliation process between the SAP basis, other IT departments and, if necessary, the business areas concerned. The defined standard and the system's IST situation must be fully documented and regularly checked for compliance. This can be done through automated monitoring, validation using tools such as SAP-LVM (Landscape Virtualisation Management) or SAP Solution Manager, as well as manual checklists. Only the regular review of the standards guarantees their compliance. It can also support the regular use of SAP services such as Go-live Checks or Early Watch. Examples of how to standardise procedures are listed here: ・ Naming of system instances and logical hosts, or at least one central registry in a directory service, or LVM or SAP customer portal ・ Centrally starting and stopping systems, such as via the LVM ・ Categorising SAP instances by T-shirt size to define profile standards and cost them.

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

SAP Basis is the foundation of every SAP system.

The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.


In case of non-compliance, for example due to project influences or technological problems, the exception must be returned to the standard in a timely manner.
Zurück zum Seiteninhalt