With the rapid changes in IT and the ever-increasing challenges in the age of digitalization companies need to look at integration and automation in order to focus on the company’s core business.

SAP’s goal is to facilitate and simplify the future integration of cloud and hybrid landscapes using two complementary solution approaches:

  • Public, fully documented application programming interfaces (APIs).
  • Route-through middleware integration content.

The focus is on the strategic middleware and core services of SAP Integration Suite as Integration Platform-as-a-Service (iPaaS) or a current version of SAP on-premise software SAP Process Integration & Orchestration (PI/PO)

Future public APIs will be the elemental foundation on which SAP, its customers and its partners run integrations. The use of standardized APIs will enable customers and partners to reduce the complexity of integration projects, resulting in a lower total cost of ownership (TCO).

Reduce operational costs

To further reduce operational costs we offer our expertise in the automation environment. Extensive possibilities for automation are offered by SAP Landscape Management (LaMa). This is a solution that simplifies and standardizes customers’ SAP operating processes. Repetitive, time-consuming tasks can thus be automated and adapted to specific needs. SAP LaMa provides complete transparency over the SAP system landscape (and non-SAP) and the ability to perform centralized system-wide operations while taking into account system dependencies.

Imagine that you have found an error in your production SAP system that is severely impacting your operations. Imagine further that you have “any number” of temporary test/QAS systems available that can be started to recreate specific errors. You select one of the available test/QAS systems, start it and copy your production system to the selected test/QAS system with one click: 100% automated. Now you can take your time to fix the error without endangering other parts of the production system. After fixing the error, the temporary test/QAS system is shut down again and costs you only the stand-by mode. This scenario is a prime example of how we run automation for our customers.

In addition to SAP Landscape Management, we rely on the automation and monitoring capabilities of SAP Solution Manager and/or our own monitoring mechanisms, which we use, for example, with Check_MK for automated monitoring of system landscapes.