Results: Technology Integration Survey
Beginning of August 2011, the SAP Product Architecture team posted a survey on integration technologies used in our customer base today. More than 80 participants completed the survey. Thanks a lot! We’ll use the results to further improve our products and solutions.
So what are the findings?
- Integration remains extremely heterogeneous since nearly all customers use ten or more integration technologies (e.g. RFC/BAPI, web services, ALE/iDoc, EDI, Enterprise Services, file transfer)
- While most customer projects have a focus on RFC/BAPI and ALE/iDoc (~30% of the integration scenarios), newer projects tend to also use web services and Enterprises Services (~25% of the integration scenarios).
- SAP delivered integration content is broadly used or extended (about 60% of all integration), remaining integration is customer developed or partner delivered (primarily B2B)
- Nearly all respondents have deployed SAP-to-SAP, SAP-to-non-SAP, and B2B integration scenarios, SAP-to-SaaS emerges as new scenario; for large customers, SAP-to-non-SAP integration becomes dominant.
- Stability and backwards compatibility, error handling and standards-based integration technologies are the three most important integration quality aspects from a customers’ point of view. Models and semantics are rated lower.
- Most selected focus areas for enhancements are monitoring and error handling, both for direct (peer-to-peer) integration and mediated scenarios
- We identified four different groups of customers with different integration style and landscapes:
- “Connect”: Customers with smaller landscapes (SAP ERP or R/3), using mainly direct SAP delivered or extended integration between SAP systems (often RFC/BAPI), needing efficient error handling in peer-to-peer integration scenarios
- “Extend”: Mid-size landscapes with high share of customer developed integration, extending SAP systems through peer-to-peer integration; early adopters of web services and SAP NetWeaver Composition Environment (CE) needing efficient development and extension tools
- “Integrate”: Mid-size to large SAP landscapes connected through SAP NetWeaver Process Integration (PI) by many different integration technologies, however, also other middleware solutions deployed to integrate non-SAP systems needing efficient error handling
- “Orchestrate”: SAP NetWeaver PI used as central integration and orchestration platform for large SAP and non-SAP applications landscapes needing governance and standards
What is your integration style? Share with us your experience and feedback.