Tips: Integrating SAP and non-SAP solutions

The result is differentiated Software-landscapes with different solutions that need to communicate with each other if they are to add up their strengths.

If it does not succeed in Applications quickly and easily and can be integrated into ever new Business processes to include, the overall synergistic benefit is eliminated by the complexity of the integration scenarios.

Therefore should Company, instead of manual one-to-oneInterfaces between non-SAPsolutions and SAP, use a tool that provides fast and code-free Integration enables.

This reduces complexity and risk of heterogeneous Software-landscapes, increases their flexibility and adaptability, and simplifies the care, maintenance, and monitoring of such best-of-breedInfrastructures.

When selecting integration technology, consider the following ten tips:

 1. use a loosely coupled Software-Architecture

The programming of fixed Interfaces between SAP and Non-SAP–Applications seems to be a simple matter at first glance.

But then the problems begin: An inextricable Software-complex, which leads to unstable and risky integration scenarios.

Therefore you should use a Technology with which you can select loosely coupled Software-architectures can be implemented.

This allows you to select different Infrastructure- and topology approaches such as hub-and-spoke concepts, Enterprise Service Bus or SOA to be realized.

All your in-house solutions should be loosely coupled instead of hardwired. In a hub-and-spoke model with a SAP-system in the center, you can, for example, exchange individual solutions without the other Applications be affected by it.

Fixed programmed one-to-oneInterfaces lead to spaghetti topologies with which you can no longer react agilely to changes.

 2. use standardConnectors

If you use standardConnectors instead of individually programmed Interfaces avoid risky programming projects.

Custom programming is always lengthy and risky. StandardConnectors, which is specially designed for SAP are designed and use BAPI, RFC, IDOC, and Web services perform the same tasks without requiring the same effort.

In best practice examples, integration platforms are regularly deployed to support such Connectors offer as standard.

Sinterfaces are thus configured rather than programmed. Unterprise can thus focus on the Business processes focus and no longer have to worry about the technical aspects of the Integration take care of - however, the Integration platform and the Connectors from SAP be certified.

 3. utilize a visual business process and Integration-Flow design tool

The combination of visual business process design with Tools, which support the implementation of the visual models, creates a common view of IT-managers and IT-stakeholders on the integration links between SAP and Non-SAP-solutions.

Therefore, the integration technology used for planning and implementing integration solutions should have a graphical user interface that allows you to visualize the processes for technicians and non-technicians.

 4. configure integration modifications instead of programming them

The world doesn't stand still, and the corporate world certainly doesn't. Therefore change Business processes steady.

The IT must support this constant change by changing business rules and technical configurations at high frequency.

When a Integration is hard-coded with a third-party system like Salesforce.com, changes become difficult.

Ideally, changes in the SAP- or Non-SAP-system, such as creating new data fields, field names, field types or field sizes, only takes a few mouse clicks to customize the data exchange via the hub.

 5. use a Platform- and Database-independent integration technology

The software landscape in most Company is heterogeneous. Integration often has to connect entire system worlds that previously worked in isolation and separately.

This leads back to the Connectors-Tip: The integration technology should Connectors for all important system worlds, so that they can be Platform-independent can be used.

Therefore choose a Platform, which also Connectors offers for the latest solutions.

Then there is a high probability that also for new Applications and systems the respective necessary Connectors be made available.

 6. pay attention to experiences with similar business and technology scenarios

Invoicing processes are not always Company similar. As a rule, the same solutions are also involved.

Therefore, a mature integration technology has the advantage that with it already many Business processes have been implemented, which can serve as a model for their own integrations.

You don't always have to reinvent the wheel. The experience of the integration platform provider often makes it possible to realize the quick wins on which IT- and line managers are dependent on the support of the topManagement to secure

 7. use a Business process-monitor

A business process monitor as part of your integration technology allows you to identify the errors in daily operations and manage their elimination.

Therefore, the data connections between the solutions should be monitored.

The monitor should be configurable so that you can view the most important information in a dashboard and determine what data goes into the log as an attachment.

 8. automated Documentation is mandatory

If your integration project is not adequately documented, project-critical information can be lost, such as when employees move to other functions or jobs.

At the same time Documentation a tedious, laborious and time-consuming process.

If your integration technology is self-documenting, project team members are more likely to add notes that are useful from a business and technical perspective.

 9. pay attention to SAP-certified Integration

For the Integration of SAP and Non-SAP-solutions, it is important to focus on SAP-certified Technologies from established SAP-partners.

Especially when urgent support becomes necessary for whatever reason.

 10. look at the experience in the SAP-Ecosystem

Certified Connectors are one thing. The establishment and reputation of the technology provider is another.

Therefore, you should be sure that your technology partner is not new to the SAP-Ecosystem and can prove its firm establishment with awards and case studies.

Follow these ten tips, will Integration to an everyday task that can be accomplished with reasonable financial and human resources.

Then and only then will you realize the potential of a best-of-breed software landscape with SAP can use in the center.