on 08-14-2009 2:02 PM
Hi,
I am designing SOAP to Idoc interface. I will be receiving SOAP request & need to create Purchase order in ECC. Once order is created , i need to send back PO no & line item back to SOAP system.
I have completed SOAP to Idoc set up & it is working fine. I do not know how to send back PO no with line items.
Can anybody explain me what are the steps I need to follow?
Regards,,,
Sunil Joyous
You have to compromise a bit.
Your concern about monitoring is very appropriate. Idocs are best and easiest. But your requirement involves synchronous configuration and Idoc does not support it. Therefore if you have standard RFC available, use it.
Or another design (a poor one) could be that in the inbound processing code of Idoc, you may trigger another custom RFC to send data to PI.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prateek,
Your idea is not bad. Once I create a purchase order, i can trigger std PO outbound idoc via output control. This outbound Idoc can be sent to SOAP adopter.
But now I have another question.
Now I have two scenario,
1 -- SOAP to Idoc (Inbound) : here I have generated WSDL file
2 -- Idoc to SOAP (Outbound) : Do I need to create WSDL file here or should I ask SOAP request provider to supply WSDL file
Regards,,,
Sunil Joyous
Hi,
I suggest you to go for SOAP to RFC Synchronous scenario. Wherein, you can pass the PO details back to SOAP.
Regards,
Venu V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
According to me, you donu2019t require to debug any problem in R/3. Just search for standard BAPI (and get the required fields data to be passed on to R/3 to create PO), if it fulfils your requirements then go for it or you can ask for a custom RFC for your specific requirements from r/3 developers.
Thanks & Regards,
Venu V
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.