SAP Screen Personas
For more information about the lowest support package level for SAP ABA and SAP Basis to install an SAP Basis Plug-In, see the SAP Service Marketplace. For more information about the lowest support package level for the corresponding SAP R/3 plug-in, see the SAP Service Marketplace. This level depends on the release of SAP R/3 or SAP R/3 Enterprise.
The SAP basis is often perceived as a brake within projects or when introducing new technologies. This is partly due to the late consultation of the SAP basis on the issues of technical feasibility as well as the integration of new technologies and applications into the existing system landscape. By implementing the recommendations, the SAP basis is repositioning itself in parts within the IT organisation. The SAP basis has a clearly defined self-understanding (inward-looking perception) as well as a clear positioning and a defined task area within the IT organisation (outward-facing perception), as shown in Figure 5. By integrating the SAP basis into the development of the IT strategy, the digitisation strategy and a clear communication with the CIO, the SAP basis has the opportunity to deal with technologies and topics at an early stage. As a result, the SAP basis is prepared for requests from business units or other IT departments and has the opportunity to approach them proactively. The SAP basis is supported by an IT service and IT product catalogue, which describes the scope of the SAP basis. For internal communication and communication with external service providers, as well as other suppliers, outsourcing partners or outsourcing partners and cloud service providers, there are up-to-date and meaningful documentation and process descriptions. For the control, measurement and monitoring of external partners, Service Level Agreements and meaningful key figures are also available.
Analysis and reflection of the existing system configuration
The SAP Patch Manager (SPAM) is the online correction support (OCS) customer site. The SPAM transaction gives you the ability to easily and efficiently import support packages provided by SAP into your system. Depending on the system used or the configuration of your system, you must insert different types of Support Packages [page 8]. You will receive support packages in SAPNet - Web Frontend, in SAPNet - R/3 Frontend or on Collection CDs. Since SPAM runs within the SAP system, you do not need to know the operating system to handle the transaction. In the language usage of SAP, the term patch has been replaced by the term support package. Note that you can only work with this transaction in SAP GUI for Java and SAP GUI for Windows.
It is therefore not unusual for the authorisation allocations to be regularly reviewed in the course of a revision or by external auditors. This is a very laborious process with SAPS standard tools. In this scenario, an authorisation administrator would first have to manually assign each employee to a specific manager and determine their roles. After that, these roles should be exported from the system (for example, to an Excel file) and then submitted to the supervisor so that he can decide whether the role assignment is appropriate or not.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
SAP application server monitoring, ABAP dump and system log analysis.
Standardised products can only be offered if process processes are standardised.