SM04 Evaluate user sessions
In order to ensure the stability of the systems and to reduce the risk through proprietary developments, release and patch management must be implemented. Standardised procedures can help to introduce proprietary developments, such as test strategies or service level agreements (SLAs). It is also important to align the productivity setting of customer applications with the maintenance windows and RTO (Recovery-Time-Objective).
The definition, organisational structure as well as the naming of the SAP basis is historically conditioned by previous SAP software versions and components. This also results in the perception of the SAP basis and the related focus of the SAP NetWeaver and the ABAP system core, which is still widely used today. However, the scope of activities has changed significantly in terms of tasks and technology and will continue to change in view of SAP's perspective and product strategy and the changing roles of IT. In order to accommodate this change and to change perceptions both in the overall context of the SAP ecosystem and within its own company, the SAP basis must develop a new self-understanding and establish a marketing for the publication of its own performance. The underlying information can be found in the master thesis in chapters 7.4 and 9.2.
SUBJECT MATTER EXPERT (SME)
The role of the SME describes an expert in a particular field, such as SME databases or SME-SAP-HANA, in the context of SAP products and is gaining in importance due to new technologies and thematic areas. The role of the SME thus corresponds to an expert role in the technology environment. It has a good network within the IT departments and, if necessary, to other business units within the company. In order to carry out its activities, it is necessary to have already acquired practical experience in the operation of its thematic focus. Expert tools are also used to fulfil his task. Through the exact definition of disciplines, the SME assumes the informally many tasks of the traditional SAP basis administrator and also new disciplines in the course of new technologies. In addition to the existing features, there will be in the future such as SME-Cloud, SME-SAP-HANA/Databases, SME-Supplier-Management, SME-Security, SME-Compliance, SME-Landscape-Virtualisation-Management (SME-Landscape-Virtualisation-Management) and SMESolution-Manager. SME-Cloud is in contact with the global cloud manager (if it exists in the company). In addition, an expression SME-Security is in contact or reported to the global corporate security sector. An expression SME-Supplier-Relationship-Management or Supplier-Management is orientated both internally (coordination with other departments) and externally (coordination and communication with suppliers). The SME cloud is a special feature of SME Supplier Management.
In the case of distributed or local SAP systems, it can also be helpful if departments or decentralized IT units can schedule their own jobs themselves. It is important that the associated approval processes can also be mapped and easily tracked. This brings convenience, flexibility and a degree of freedom without neglecting operational security. The integration of the business departments can relieve the IT administrator and turn background processing into an end-to-end process integrated into the organization.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
In addition, type a short description as usual and confirm.
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
I hope that with this I can give you some guidance so that you can avoid these mistakes.