Optimization of the SAP infrastructure
WE19 Test tool for IDoc processing
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.
Through a sound expertise in the SAP technology environment, it is recommended to bring the know-how of the SAP basis into the IT strategy and IT roadmap. For this, the responsibility lies primarily with the CIO as the carrier and responsible of the IT strategy and the IT organisation. Likewise, the SAP basis should serve as a sparring partner for individuals and boards (such as enterprise architects) that significantly influence the strategy.
SAP Basis
SAP Basis is structured as a classic three-tier model. It contains the following components: Database layer (relational database management system) / Application layer (application server and message server) / Presentation layer (graphical user interface).
Ten years ago, SAP HANA was little more than a promise that made SAP CEO Hasso Plattner's eyes light up. It's hard to imagine that all SAP customers will have completely replaced their Oracle and Microsoft databases in just ten years.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
In order to carry out its activities, it is necessary to have already acquired practical experience in the operation of its thematic focus.
Migrations, e.g. operating system or database change (homogeneous and heterogeneous system copies).