SARE Archive Explorer
Authorizations
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.
However, the tasks also include strategic and planning aspects. For example, administrators define requirements and standards, select and control upgrades or extensions, implement monitoring processes, and take care of necessary backups and emergency management.
Point-in-Time Recovery
To view the software components installed in your SAP system with their respective package levels, select Status Package Levels. A dialogue box appears listing the installed software components with additional information. For more information on this dialogue, please refer to the Online Manual. SPAM: ABAP/Dynpro Generation Usage For performance reasons, the SPAM is set by default to prevent ABAP/Dynpro generation from occurring during the commit. The corresponding programmes are not generated until they are called. However, you can set the SPAM so that the generation takes place during the recording. It is quite possible that the SPAM will report errors during generation because, for example, a self-written or modified report is syntactically wrong and refers to an object that is being played over the cue. Often it is desirable to ignore the generation errors for the time being and to fix them after inserting them. Prerequisites to play Support Packages.
The Technical Lead functions as the work package leader or sub-project manager within the SAP basis when the project is the focus of the SAP basis. The Technical Lead will become more important in the future as the SAP basis acts as a technology consultant and more projects and project activities are expected in the future. This role must be filled more and more often. Due to the increased demands, this role and the associated activities must be professionalised through training and further training.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
SAP recommends a role design for Fiori permissions based on the defined catalogues and groups in the launchpad.
As a company, you have to decide whether you want to leave the support of your system within your company or place the "Basis" in the hands of an SAP expert.