How to improve the performance of SAP standard implementations using SAP PI AAE


SAP PI Interview Questions and SAP PI Tutorials

SAP PI Interview Questions and SAP PI Tutorials

How to improve the performance of SAP standard implementations using SAP PI AAE

How to improve the performance of SAP standard implementation 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.

So wiht this wiki 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:

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 Scenario.

ProxybasedInterfaceflow

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

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

ESRContentSRMSERVERIC

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

SAP PI Interview Questions and SAP PI Tutorials

SAP PI Interview Questions and SAP PI Tutorials

ESRContentSAPAPPLandSAPSRMSERVER

ProcessIntegrationScenarioSE_Sourcing_Enhancements

For this interface there are no changes to be done for Message Mapping or Operation Mapping in ESR. So we move to Configuration in Integration Directory:

ConfigurationScenarioSE_Sourcing_Enchancements_AAE

Here we can skip Model Configurator as this wizard generates objects required in traditional implementation. We can manually configure objects as the number of Objects to be created is less in current scenario. Else we can go ahead with the Model Configuration and generate objects then remove non relevant objects and create relevant objects.

First we import/assign the business systems relevant for SAP ERP and SAP SRM to our configuration scenario.

Save and activate all the objects in Integration Directory.

Now will move to ABAP stack of ERP to create few configurations:

Create RFC destination of type G. This RFC destination is to point to SOAP adapter of SAP PI, earlier we used to create a type H connection that was pointing to Integration Engine of PI

  1. Execute TCODE: SXMB_ADMIN and click Integration Engine Configuration and create a new entry as follows:

Select the category as RUNTIME, Parameters as IS-URL, SubParameter as Sender/ReceiverID created in previous step and current value as dest://<Type G RFC Destination> which will be

One pain is: Steps 1-3 need to be repeated for number of interfaces that are implemented from ERP. Same way if the interfaces are executing from SRM to ERP then these steps needs to be executed in SRM.

I have taken ERP and SRM as standard implementation, but same can be implemented for any standard implementation if both the application systems are communicating using Proxy environment.

Sorry I couldn’t provide real-time values of performance variances. But as SAP says there will be definitely there will be hike in Performance chart.

I hope this will bring some idea to consultants in improving the performance of Interfaces for standard implementations between SAP Application servers.

Here we can skip Model Configurator as this wizard generates objects required in traditional implementation. We can manually configure objects as the number of Objects to be created is less in current scenario. Else we can go ahead with the Model Configurator and generate objects then remove non relevant objects and create relevant objects.

First we import/assign the business systems relevant for SAP ERP and SAP SRM to our configuration scenario.

BusinessSysteminID

We create communication channels both sender and receiver side holding adapter type as SOAP, and Message Protocol as XI 3.0

SenderSOAPCommunicationChannel

Here comes the first difference, we create sender communication channel of adapter type SOAP but XI 3.0 as Message Protocol. But to send Proxy message from ERP to SAP PI SOAP adapter we need to configure three steps in ABAP stack, will discuss once we finish explaining ID objects.

ReceiverSOAPCommunicationChannel

Second difference is to create a receiver communication channel of type SOAP adapter and select XI 3.0 as message protocol rather creating communication channel with adapter type XI. We need to provide Target URL as Integration Engine URL of SRM server which will be http://hostname:portnumber/sap/xi/engine?type=entry, here hostname and port number are of SRM server.

Then comes the Third object which is ICO – Integrated Configuration Object, this replaces all our traditional Receiver Determination, Interface Determination, and Receiver Agreement. Here we see how to create ICO object.

IntegratedConfigurationObjectsICO

In the first tab Inbound Processing: select the Sender Communication Channel which we have created in earlier step.

ICOInboundProcessing

In the next tab Receiver, select the Receiver SRM Business System.

ICOReceiver

In the next tab Receiver Interfaces provide the receiver interface details, and operation mapping if anything is required.

ICOReceiverInterfaces

In the next tab Outbound Processing provide the receiver SOAP communication channel that you have created in the earlier step.

ICOOutboundProcessing

Save and activate all the objects in Integration Directory.

Now will move to ABAP stack of ERP to create few configurations:

Step 1. Create RFC destination of type G. This RFC destination is to point to SOAP adapter of SAP PI, earlier we used to create a type H connection that was pointing to Integration Engine of PI

RFC Destination PI_ADVANCE_ADAPTER_ENGINE

Step 2. Next execute TCODE SXMSIF and provide Sender/ReceiverID: Any unique name corresponding to the Interface, then provide Sender Service, Interface name and Name Space

SXMSIF.

Step 3. Execute TCODE: SXMB_ADMIN and click Integration Engine Configuration and create a new entry as follows:

Select the category as RUNTIME, Parameters as IS-URL, SubParameter as Sender/ReceiverID created in previous step and current value as dest://<Type G RFC Destination> which will be dest://PI_ADVANCE_ADAPTER_ENGINE.

IntegrationEngineConfiguration1

As a result configuration looks like this

IntegrationEngineConfiguration2

One pain is: Steps 1-3 need to be repeated for number of interfaces that are implemented from ERP. Same way if the interfaces are executing from SRM to ERP then these steps needs to be executed in SRM.

I have taken ERP and SRM as standard implementation, but same can be implemented for any standard implementation if both the application systems are communicating using Proxy environment.

Sorry I couldn’t provide real-time values of performance variances. But as SAP says there will be definitely there will be hike in Performance chart.

I hope this will bring some idea to consultants in improving the performance of Interfaces for standard implementations between SAP Application servers

One pain is: Steps 1-3 need to be repeated for number of interfaces that are implemented from ERP. Same way if the interfaces are executing from SRM to ERP then these steps needs to be executed in SRM.

I have taken ERP and SRM as standard implementation, but same can be implemented for any standard implementation if both the application systems are communicating using Proxy environment.

Sorry I couldn’t provide real-time values of performance variances. But as SAP says there will be definitely there will be hike in Performance chart.

I hope this will bring some idea to consultants in improving the performance of Interfaces for standard implementations between SAP Application servers

 

SAP PI Interview Questions and SAP PI Tutorials

SAP PI Interview Questions and SAP PI Tutorials

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
PDF24    Send article as PDF   
This entry was posted in sap stap by step senarios and tagged . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *