on 01-10-2013 5:00 AM
Hi Gurus,
Scenario is IDOC to HTTPS synchronous scenario:
Idoc will be sending to PI where PI posts HTTPS post to the 3rd party external system, then the 3rd party external system sends back the HTTPS response and that needs to be mapped with the idoc structure and push that information again to the R/3 ECC system.
I just want to know how synchronous IDOC interface to be implemented.
I assume like IDOC to HTTPs post -- One Async scenario & HTTPS Response to IDOC another Async scenario -- will this work.
Please suggest...
Thanks,
--Sai
Hi,
>>>I just want to know how synchronous IDOC interface to be implemented.
you may need to use a few flows for that
1. IDOC to file - async
2. file - sync https - file (with request response beans - async-sync bridge)
3. file - IDOC
this way you can do it without a BPM and should work very fast,
Regards,
Michal Krawczyk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mich,
2. file - sync https - file (with request response beans - async-sync bridge)
Can you elaborate this more..
so totally it will be 3 interfaces right as per your suggestion.
But the dependency here is once the idoc gets the response i mean
IDOC -- PI -- HTTPS POST
HTTPS Response -- PI -- IDOC
If the response i get then only the next idoc should process.
But here as the sender is IDOC we cannot configure that EOIO i believe
Please suggest how should i goahead.
Thanks,
--Sai
Hi,
>>>>2. file - sync https - file (with request response beans - async-sync bridge)
this is how to set it up - async-sync-async (so file-https-file)
http://wiki.sdn.sap.com/wiki/display/XI/Using+Request+Response+Bean+Module+in+FILE+Adapter
>>>>If the response i get then only the next idoc should process.
it's possible to use EOIO with IDOCs but not in this case - in this case it's better to develop something which will pprevent "next" idoc creation before the response is received - this way it will be much more realiable,
Regards,
Michal Krawczyk
Hi Sai,
IDoc does not support Synchronous communication. Its always better if you go for Proxy at SAP side.
Otherwise go for Acknowledgment, find the below blog:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sen,
Could you please guide me in approaching solution for this requirement..
IDOC ---PI-- HTTPS, HTTPS response -- PI -- IDOC
Here the ultimate dependency is once i get the responce back i need to trigger the next idoc,
But as per the mich suggestion in the above thread, he suggest to control the generation of next idoc based on response of the previous one.
But they dont have such control in place to check..
So could you please suggest the possibe ways to drive the solution.
Thanks,
Sai
Hello,
I don't think this is possible using HTTP Adapter since the response would be 'instantaneous' and would be treated as a single call.
Here are some approaches:
1. Use a function module(with IDoc fields) to trigger a synchronous call
2. Use ABAP Proxy (also synch)
3. Use AS2 adapter (two asynch scenarios with Idoc Acknowledgement and MDN)
4. Use BPM (to capture synch response).
Hope this helps,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.