SHARING OF THE SAP basis INTO A SINGLE APPLICATION AND INFRASTRUCTURE-RELATED LAYER
Provision of services and basics
In the context of the SAP basis, the deployment of an SAP application server for any SAP system can be used as an example. Parameters include processor count, memory, disk space, operating system, and run-time environment.
The SAP Basis Plug-In is backward compatible and follows the release and maintenance strategy of the SAP R/3 Plug-In. SAP ships it together with the SAP R/3 Plug-In.
Offline / Online ReDO Logs
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.
At the same time, there is a need to return the solutions to the SAP standard. A collaborative approach between departments and IT technology is required to assess IT technical and business benefits. It is also necessary to check whether the adaptation of business processes to avoid modifications to the implementation may be more effective and therefore more cost-effective. This must be evaluated and decided jointly. As a result, we recommend defining and implementing business standards for creating and maintaining solutions.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
SAP has also already invested in Gardener and is also intensifying its partnerships with IBM and Red Hat Openshift.
If administrators or admin teams want to maintain an overview, they have to rely on meaningful monitoring.