Improving the performance of SAP standard implementations using SAP PI Advance Adapter Engine (AAE)

By Praveen Kurni, Yash Technologies

With this weblog I want to showcase, how to improve the performance of SAP standard implementations using SAP PI AAE stands for Advance Adapter Engine. As we know any standard implementation of ESOA interfaces for any Application/Module, we will go with configuration scenario by importing the process integration scenarios provided by SAP in ID. This can be done by any functional consultants like SRM, SCM consultant if he knows basic wizard based configurations in PI server for application related implementation. I don’t think, all functional developers are aware of AAE in SAP PI, with which we can increase performance of interfaces. Technically we know how to use AAE to improve the performance for any custom built applications like client specific implementation Ex: File to JMS. Because such implementation projects require PI consultants, and they know how to utilize the latest features available in PI custom implementations.

Using this blog let me showcase with ERP to SRM example, how to improve the performance of SAP standard implementations using SAP PI AAE targeting functional consultants, and also PI consultants who didn’t try implementing AAE in standard implementations.

We have some articles/blogs available in SDN to explain about the functionality of AAE, and how to use AAE. Please find some below:

• SAP NetWeaver Process Integration 7.1: Advanced Adapter Engine

• How to Set Up the Communication between ABAP Backend and SOAP Adapter using XI Protocol

• Local Processing in the Advanced Adapter Engine using PI 7.1

Before continuing to the topic discussion let us see traditional configuration.

Let me illustrate with an example by taking SAP SRM 7.0 and SAP ERP 6.0 EHP 4 communicating through SAP PI EHP1. To implement standard ESOA content we need to import ESOA content in to ESR, and identify the Process Integration Scenarios.  

Fig: Proxy based Interface flow.  

Once we identify the relevant Process Integration Scenario in ESR, we will move to Integration Directory and create a Configuration Scenario by using identified Process Integration Scenario. By utilizing Model Configurator feature in Integration Directory, we create configuration objects we click next, next, next. But if we understand the runtime flow, then we see performance is hindered by creating such objects. Normally most of the standard implementation scenarios go without any mappings, not many routing techniques, and CCBPM. All the scenarios executed using this traditional way will goes through Integration engine of PI for processing. Someone can say Proxy is adapter less so this can work much faster than other features. Yes Proxy is adapter less, but still you need to configure XI adapter at receiver communication channel and also message processing must pass through integration engine tedious pipeline steps which is time taking process by processing. When there is mapping/no mapping, no routing and no CCBPM used (take variable combination) why not we use AAE.

Now, we will see how we can utilize AAE feature of PI 7.1 for standard implementation. To utilize the feature of AAE we need to configure new ICO object as explained in the article, and little configuration in Application Servers.  Let us see how to configure the objects in the same example taken above.

Configuration steps for standard implementation ERP – PI – SRM

Identify the Process Integration Scenario in relevant SWCV. As an example I’m taking SE_SOURCING_ENHANCEMENT process integration scenario in imported ESR content SRM SERVER IC 7.0

Fig: ESR Content: SRM SERVER IC.

To implement this Process Integration Scenario we need to import ESR content SAP APPL 6.04 for ERP end, and SAP SRM SERVER 7.0 end.

Fig: ESR Content: SAP APPL and SAP SRM SERVER

Fig: Process Integration Scenario: SE_Sourcing_Enhancements

Click here to continue...