Local Processing - SAP PI Advanced Adapter Engine

Posted on Feb. 05, 2010 at 10.00 AM - KL, Malaysia

Integrated configuration is a new feature which SAP introduced in PI version 7.1 and above. The features maximize the usage of advanced adapter engine even for routing the message; as such the message does not have to go through integration engine anymore to be sent over to the receiver. This feature is also called as local processing. Based on the SAP research, the performance of local processing is 6 to 8 times faster than normal processing which involves both integration and advance adapter engine.

Local processing is available for all java based adapters to java based adapter, and proxy to Java based adapters, or vice versa. There is additional configuration which needs to be done for proxy related integration though. For more information, please see this link http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?QuickLink=index&overridelayout=true

The scenario we are going to see over here is RFC to FILE where the sender is SAP system and the receiver is File server.File Receiver Adapter configuration is NOT shown over here, but it's pretty easy to configure it.

1. Create RFC Sender Adapter and register it as BIT400_ID in the PI gateway

2. Create RFC destination in SAP Back End pointing to the registered program ID in PI gateway

3. Import BAPI metadata from SAP ECC to SAP PI, so that we can use that in the subsequent configuration

4. Create integrated configuration for local processing in Advanced Adapter Engine

a. Inbound Processing tab

b. Receiver Interfaces tab

c. Outbound Processing tab

5. Create ABAP program to call the the RFC through the RFC destination which is created at step 2. Don't forget to use COMMIT WORK to actually execute the program successfully after calling the RFC.

Life is beautiful! Let's make it meaningful and colorful!