Process Integration is an Integral part of SAP Net weaver.The aim of PI is to integrate different versions of both SAP and non-SAP systems implemented on different flat forms (Java, ABAP, and so on). PI enables you to implement cross-system business processes.PI is based on an open architecture, makes use of open standards and OFFERS services that are essential in a heterogeneous and complex

system landscape: namely a runtime infrastructure for message exchange, configuration options for managing business processes and message FLOW, and options for transforming message contents between the sender and receiver systems.

The application-specific contents are transferred from the sender to the receiver in a FREELY defined XML schema (XML: extended Markup Language) using the Integration Engine. The structure of a message is therefore determined by the interface data structures used.

The central concept is that, during the design phase, all interfaces required are INITIALLY developed independently of a platform and made available in the form of a WSDL description (WSDL: Web Service Description Language). Using this description you can, for example, define mappings between interfaces without this having an EFFECT on an existing system landscape. All design phase data is saved in the Integration Repository to be implemented later in a particular system landscape. In this second phase, the configuration phase, you can select components, interfaces, and mappings saved in the Integration Repository that are appropriate for your system landscape and business processes, and assign them to each other in logical routing. The data resulting from this configuration process is saved in the Integration Directory and you can call and evaluate it from the runtime of the PI.

Features:

PI enables you to do the following:- Develop cross-system applications. You can exchange multiple system messages using the runtime infrastructure and synchronous or asynchronous communication. You can either develop new and platform

-independent interfaces, or connect to existing interfaces at runtime, using adapters.

Adjust message values and structures for the receiver, using mappings.

- Centrally maintain the message flow between logical systems in the system landscape, using logical routing.- Connect the logical receiver to a technical system, using Services; this system can easily be switched using this abstraction level (technical routing). Describe your system landscape as the basis for the description of your cross-system business process.

Process Integration is an Integral part of SAP Net weaver.The aim of PI is to integrate different versions of both SAP and non-SAP systems implemented on different flat forms (Java, ABAP, and so on). PI enables you to implement cross-system business processes.PI is based on an open architecture, makes use of open standards and offers services that are essential in a heterogeneous and complex

system landscape: namely a runtime infrastructure for message exchange, configuration options for managing business processes and message flow, and options for transforming message contents between the sender and receiver systems.

The application-specific contents are transferred from the sender to the receiver in a freely defined XML schema (XML: extended Markup Language) using the Integration Engine. The structure of a message is therefore determined by the interface data structures used.

The central concept is that, during the design phase, all interfaces required are initially developed independently of a platform and made available in the form of a WSDL description (WSDL: Web Service Description Language). Using this description you can, for example, define mappings between interfaces without this having an effect on an existing system landscape. All design phase data is saved in the Integration Repository to be implemented later in a particular system landscape. In this second phase, the configuration phase, you can select components, interfaces, and mappings saved in the Integration Repository that are appropriate for your system landscape and business processes, and assign them to each other in logical routing. The data resulting from this configuration process is saved in the Integration Directory and you can call and evaluate it from the runtime of the PI.

Features:

PI enables you to do the following:- Develop cross-system applications. You can exchange multiple system messages using the runtime infrastructure and synchronous or asynchronous communication. You can either develop new and platform

-independent interfaces, or connect to existing interfaces at runtime, using adapters.

Adjust message values and structures for the receiver, using mappings.

- Centrally maintain the message flow between logical systems in the system landscape, using logical routing.- Connect the logical receiver to a technical system, using Services; this system can easily be switched using this abstraction level (technical routing). Describe your system landscape as the basis for the description of your cross-system business process.