Dec 04

SAP Integration Optimization

In any SAP implementation, there are a multitude of tasks and specialties happening all at once in preparation for Go-Live. Priority tasks such as business blue-printing and SAP core module configuration (FI/CO, MM, SD, etc.) take precedence over integration technologies such as ALE, XI/PI, and IDocs, as these are widely viewed as the “plumbing” of the SAP landscape. This SAP “plumbing” is needed, but “hidden in the walls” of the ERP system, and is rarely architected and managed at an Enterprise level. In larger ERP implementations, it’s very common for different groups to integrate to various systems independently and without regard to what other teams are doing. Legacy technologies may be incorporated as quick fixes, with plans to decommission later. Some teams may use a custom point-to-point integration approach, other teams will utilize IDocs, others will send messages to XI/PI via BAPI’s, and others may customize standard interfaces or use flat files.

After the system goes live, there may be a time period of stabilization, with a frantic scramble to make the system operational. Additionally, over several years, different projects and technologies will be incorporated. In larger companies, this can mean thousands of interfaces using dozens of different technologies coexisting in the support infrastructure. This “Band-Aid” approach to integration is typically never thought of as inefficiency that can be addressed to save real money in the organization, but merely viewed as a black box, or something the organization has to “live with.“

Even though the integration may fundamentally work well enough to run the business, there is definite and achievable ROI in re-architecting and optimizing the integration processes, especially in larger companies that have thousands of interfaces and hundreds of ways to connect them!

The return on investment of any project in SAP can have varied measures of success. Integration projects are no exception. Unique problems associated with company specific architecture impact the overall return. Listed below are the top seven identifiable ROI areas in integration technologies:

  1. Greatly increase cost savings in new development
  2. Reduce or eliminate the maintenance cost of multiple middleware technologies
  3. Provide better system performance during interface operation, speeding up the effective speed of the SAP system for end users
  4. Reduce the workload of users responsible for resolving errors, freeing them up to be productive on essential business tasks
  5. Reduce charge backs by retailers for improperly formed EDI
  6. Reduced head count by middleware consolidation
  7. Reduced hardware cost

To read more about these cost saving techniques please download the whitepaper here or simply click on the “Learn More” tab to the right to request this and other DataXstream white papers.

Avatar

About The Author

Leave a reply

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

This site uses Akismet to reduce spam. Learn how your comment data is processed.