In most cases, organizations that adopt SAP software remain heterogeneous enterprises. In heterogeneous enterprises, most SAP implementations must be integrated with various non-SAP enterprise systems, portals, messaging infrastructure, security, systems of record, systems of engagement, and so on. Organizations can enhance and extend pre-built capabilities in SAP software with a hybrid integration strategy to maximize ROI in their SAP investment and achieve a balanced enterprise architecture approach.
From an architecture perspective the strategy should involve three types of systems i.e. Systems of Record, Systems of Engagement, Systems of Interaction.
ESB provides a common, application independent, integration backbone for the business
Accelerate SAP integration into a heterogeneous enterprise and cloud applications
Use standard, non-customized SAP applications
One of the primary business drivers for adopting a packaged ERP solution such as SAP is the business value achieved from using pre-built, ready for use components. Configuration changes can be made with minimal effort and in a version-safe manner. However, custom development can require
more effort and takes away from the value provided from a packaged application. Even modest customizations can lead to a chain of dependencies that inhibit taking advantage of new features and functions in SAP software, or upgrading SAP software cost effectively in the future.
Reuse pre-built SAP integration
Even organizations with significant alignment with SAP rarely use SAP for more than 60% of their total business automation needs, according to IBM practitioners with extensive experience in SAP projects. This fact makes the enterprise integration of large-scale SAP implementations a key
success factor of the overall SAP transformation program.
Use best-in-class technologies when extending beyond the SAP domain
In cases where data or processes need to extend outside of SAP, use industry-leading, application-independent software technology.
Use open, well-established standards
Standards-based implementation of integration logic greatly reduces the chance of vendor lock-in. It also increases the availability of tools that easily connect with the solution and provide support for development, monitoring, and testing.