Request/Response Bean for IDOC_AAE adapter
Here is my first blog in SCN.
In SAP PI 7.31, we have the option of using adapter modules for IDOC_AAE adapter. This is a very interesting option. Generally IDOC is Asynchronous. But in this scenario, we will see how it will work as Synchronous.
This is a scenario for Request/Response Bean for IDOC_AAE adapter.
Here I am considering my scenario as test purpose. It is not a real time scenario. My only concentration in this blog is on Request/Response Bean for IDOC_AAE.
My scenario is that I want to take an IDOC from ECC and send it to some RFC which is synchronous one and I place response RFC data into a file in some other location.
I have Imported IDOC and RFCs from SAP R/3 System and created one Data type, Message Type for File structure.
Here, for this Request/Response Bean the trick is that create one Operation Mapping with only Asynchronous IDOC and RFC thing. Then create the ID part.
In ID Part, create the below steps.
Import Business System from SLD for both IDOC and RFC and create one Business component for FILE.
Create one Sender IDOC Communication Channel and one RFC receiver Channel and one File Receiver Channel.
I am concentrating only on IDOC Communication channel for Request/Response bean. Remaining both RFC and File will be same as it is for other general cases.
Sender IDOC Communication Channel Configuration:
For sender IDOC_AAE, use RFC Parameters as it is. You can use default also for RFC Server parameters.
In Adapter module of IDOC_AAE, add the below steps.
Adapter Namespace: http://sap.com/xi/XI/System.
Adapter Type: File
Otherwise it is throwing CPACachelookup error.
Now Create ICO for this object as it is with Asynchronous Operation Mapping created before.
Coming back to ESR.
Create 1 Synchronous Service for Idoc and response message as follows:
Sender Service Interface:
Request Message as: Use your IDOC Message.
Response Message: Use your File Message Type.
Now change the operation mapping for Idoc to RFC used in ICO
a. Remove Idoc interface as sender
b. Enter synchronous interface created above using IDoc and response message types
c. maintain both request and Response Mapping
Trigger the IDOC from ECC.
Now go to Communication Channel and check your interface.
Check In Message Monitoring
Here you will get 2 messages one for request and one for response.
Finally, the File has been created in the target Directory.
This is for Request and Response Bean for IDOC_AAE.
Note: If we try to change the ICO now, it will throw error as operation mapping is now synchronous with different sender interface. So if there is a need to change ICO, then first operation mapping needs to point to asynchronous interface again and activate the ICO object. Then again change operation mapping with synchronous interface and activate the operation mapping.