
Overview
Connectivity is the capability to connect systems or applications that have different technical communication capabilities to each other using SAP PI. Examples for technical communication capabilities are the HTTP protocol or a remote function call (RFC). The transformations of messages that are required at a technical level and that are necessary to connect the system to the runtime engine of SAP PI are performed by adapters. SAP PI provides a variety of adapters to connect applications that are based on completely different technical or application-specific protocols. The runtime engine transforms each incoming message into an internal message format first before the message can be processed. This is done by an adapter at the inbound side (also referred to as: sender adapter). Depending on the characteristics of the receiver system, an adapter at the outbound side (a receiver adapter) then transforms the internal message format into the format or protocol the receiver system can handle.
Do not confuse connectivity with mapping: Connectivity implies transformations between the technical or industry-specific protocols of the connected applications. A technical “protocol” can, for example, be a simple file format, or an IDoc format. An industry-specific protocol can be RosettaNet or EDI. In contrast to that, mapping is the transformation of the business data in the payload of the message, which can, for example, include the transformation of one data field format ( YYYYMMDD) to another ( YYYY-MM-DD).
|
Types of Systems or Applications |
Connectivity Options |
|---|---|
|
SAP & Non-SAP Systems |
|
|
Applications |
|
|
SAP Industry Business Packages |
|
|
Business to Business (B2B) Systems |
|
To ensure maximum connectivity options, SAP provides a large set of own-developed adapters, and also accepts adapters developed by partners.
Additionally, customers can develop their own adapters with SAP PI in case they do not find the adapter to fit their needs.