Skip to end of metadata
Go to start of metadata

About Integration Repository

Integration Repository, earlier known as Interface Documentation, in SAP Solution Manager 7.2 as part of Solution Documentation provides the possibility to centrally document interfaces in the solution landscape. Basically, all interface technologies which exist in an SAP landscape are available, including SAP PI interfaces where the processing is done through different kinds of adapters. Each interface can be specified individually, as every interface technology provides a set of so-called interface attributes which comes out-of-the-box. In case further interface attributes are needed it is possible to create custom attributes and use them in the same way as the attributes delivered by SAP. Moreover, custom-specific interface technologies can be defined in case the standard technologies are insufficient to describe the interface properly.

How does Integration Repository help you?

In today’s distributed solution landscapes it is essential to have a central view of the existing interfaces and their technical details. Different tools may exist in various places which cater to the task of documenting single parts of interfaces, or only small portions of the interface information available in your landscape. Concentrating all this information centrally in SAP Solution Manager increases the visibility and helps avoid duplicate maintenance of said interface data in different tools.

In addition, the effect of planned downtimes in your solution landscape can be judged more easily, especially if the interfaces are assigned to business processes. Then it is directly clear which business processes will be affected once a system is shut down for maintenance, and corresponding measures can be taken in advance. Furthermore, if there is a critical situation in your landscape, like a system has stopped unexpectedly, or a particular interface has become stuck due to technical errors, you can identify the affected business processes directly in SAP Solution Manager without having the need to access the managed systems and laboriously search for the necessary information.

Many customers still use offline documents like spreadsheets to list their interfaces. This is usually cumbersome to handle and often poses the risk that data gets lost or outdated information is used due to improper document management. The Integration Repository application aims at replacing such kind of maintenance mode. Although it will create some initial effort to transfer the offline documentation into the SAP system it is worthwhile to do so. Interfaces and their attribute data can then benefit from all features Solution Documentation provides. This particularly means that different versions of the same interface can exist in parallel, and attribute data for the same interface may vary per site or system role.

In addition, integration with the Interface & Connection Monitoring application is available: interface attribute data maintained in Integration Repository can be used to configure Interface Channels for monitoring & alerting, without having the need to enter the same data into the system again. This integration reflects the best practice-like approach for Interface Management in SAP Solution Manager as indicated in below figure.­



Effectively, Integration Repository gives you the following benefits:

  • Gain a central view of all the interfaces in your landscape, including their technical and functional details
  • Get rid of outdated excel sheets and human errors occuring on it
  • Monitor your business critical interfaces and track issues arising out of interface failures immediately

Technical Aspects

  • The Integration Repository application, although tightly bound to Solution Documentation, is a stand-alone application with separate data persistency. It acts as external application to Solution Documentation, and can be called from there as an element of an Interface object in the Interface Library.
  • Integration Repository allows you to maintain the same interface in different contexts within the same solution – be it in different sites or system roles within the same branch, or across system boundaries. This represents the lifecycle of an interface as it is used in the real world: interfaces can be either created newly during an implementation project, or existing interfaces can be adjusted during an upgrade project.
  • Interfaces exist in the whole landscape (in development, test, and productive environment), but may have slightly different attribute data due to specific, system-dependent attributes. All these aspects are covered by Integration Repository application – see the subsequent chapters for further details.
  • Technically, the different variations of the same Integration Repository are persisted separately but held together by a common identifier, the so-called LIFO ID (“Logical Interface Object”). This guarantees that system-independent attributes of the same interface are always in sync between different contexts.
  • If an interface gets updated during an upgrade project the corresponding Integration Repository object can be copied into the Maintenance branch of the solution, too, and later, when released to Production branch, it replaces the previous version of the Integration Repository object without disruptions.


  • No labels