Additional Blogs by SAP
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Results: Technology Integration Survey

gaby_wenneker
Discoverer
‎09-12-2011 10:05 AM
0 Kudos

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?

  1. 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)
  2. 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).
  3. SAP delivered integration content is broadly used or extended (about 60% of all integration), remaining integration is customer developed or partner delivered (primarily B2B)
  4. 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.
  5. 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.
  6. Most selected focus areas for enhancements are monitoring and error handling, both for direct (peer-to-peer) integration and mediated scenarios
  7. 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.

Popular Blog Posts