IDOC to SOAP scenario and transport process

Scenario:-IDOC to SOAP:
We got the WSDl file from Target system and our current scenario is working perfectly fine in Dev.
Requirement:
I have to send the same IDOC to two different SOAP target system with different SOAP URL WSDL structure is same only the URl differ.
Solutions which I thought of:
1) Separate Design for both the scenarios in IR and one CS with two SOAP channel, interface and receiver determination and agreement.
2) Use the same WSDL file structure for both the case. this will avoid the separate IR configuration. in this case there will be common MM,IM. In ID the configuration will remain the same as the case one.
In 2 case I would like to know whether I can use the WSDL file which has the details of first SOAP target for the second SOAP target. Will this WSDL file act simply as structure? Does the URL mentioned in the WSDL file will create any problem?
Transport process:
SOAP WSDL file has different URL for DEV,QA and PROD. when I transport the IR from Dev to QA the Dev WSDl file will be reflected in QA as external definition, I wanted to know what is the best method to do the transport in the above situation.
Solution which I thought of
1) Go to QA IR and import the QA WSDL file.
2) Go to Dev and import the WSDl file of QA and import it in QA which avoids manual import in QA, if I go by this way will this affect the testing of my interfaces in Dev system.
What is the best method we do the transport for the above scenario.
Need ur suggestions?
chirag
Edited by: Chirag Gohil on Oct 1, 2008 1:29 PM

Hi Chirag,
As far as i know there wil not be any target URL in the WSDL File which we bought from the webservice application.
Can u please paste the WSDL File which u have .....
If we come to Dynamic URL Config means, as per my concern
You have only 2 Target locations to receive the Idoc. so its better to go a head with ur existing approch itself.
Why becase for Dynamic URL Config.....
we have to maintain the target URL's in One Table and need to use RFC lookup to pick this URL Dynamically based on some value from the Input file.
And also we need to use Standard UDF code for Dynamic config in Mapping .
And need to check the option Use ASMA in the Receiver SOAP CC.
Regards
Seshagiri

Similar Messages

IDoc to SOAP scenario is showing error

Dear Experts,
We were trying a scenario which is IDoc-XI 3.0->SOAP and where the WebService is situated outside our office network. Our network team have bypassed proxy for accessing that WebService URL and the same is accessible from our XI3.0 application server from browser. We have configured the scenario and when we have tested the scenario from RWB->Component M onitoring->Integration Engine->Test and this has worked fine. But when we have tested the scenario by triggering IDoc from the R/3 system, it is throwing the below mentioned error in both at the comm chanel and at the SXMB_MONI acknowledgement.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Service Error
points to be noted here:
1. Business Service has been configured correctly for triggering ALEAUD messages and ALEAUD messages are reaching R/3 successfully.
2. We have chosen option Keep Headers and Do not use SOAP header options.
3. We are passing some values to the SOAP Header from SOAP channel.
Please could somebody help us on the root cause of the error message.
We have run report IDX_NOALE for that particular IDoc so that it doesn't return any acknowledgement back to the R/3 system.
Thanks and regards,
Sugata
Edited by: Sugata Basu on Nov 19, 2011 12:40 PM

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Problem in IDOC to SOAP Scenario

Hi All,
we have an IDOC to SOAP scenario in which we have got WSDL from the client for the targets.. Please let us know the WSDL would be the message type and we need to create interface for it . Also the SOAP header is not appearing in the target xml.
Thanks

Hi ,
This means when the data is sent to the webservice it will contain the SOAP header just that we cannot see it in Moni . Also
What about the acknowledgement . Our message is successfull but with message that awaiting acknowledgement.
What we basically need a synchronous scenario of IDOC to SOAP but the response not going back to SAP-R3 . We recieve the response only in SAP-PI. Saw some blogs but the message is going back to SAP-R3. Please help us on this
Thanks
Edited by: vishal gadkari on Aug 22, 2009 4:15 PM

Idoc to soap scenario - soap response error

hi
i am using pi 731 single stack.
the scenario is idoc to soap. the message mapping is working fine and output is generated successfully.
the message is failing in mesage monitor and communication channel monitor. error is -
Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: VEN-OMI-1007:
This scenario is async scenario. How to soap remove this response message error.
rgds

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Explain about Idoc to soap scenario

Hi All,
I am beginner to sap pi can anybody help me out, How to perform Idoc to soap scenario...

Dear Gaffar,
Please use the search functionality to learn.
Redirecting...
http://www.google.com/cse?cx=013447253335410278659%3Ak8ob9ipscwg&ie=UTF-8&q=idoc+to+soap+scenario&siteurl=www.google.com…
try out the scenario,create the thread if you face any issues.

IDOC to SOAP Scenario : Connection Refused

Hi Everybody,
I am working on Idoc to SOAP Asynchronous scenario.
I have an issue with the connection from SOAP to the websystem at the receiver.
Around 60% of the messages are processed successfully and the rest of the messages throws up errors at the receiver Adapter.
Below is the log from Communication channel for the unsuccessful messages.
Message processing started
request entering
SOAP: call failed: java.io.EOFException: Connection closed by remote host.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connection closed by remote host.: java.io.EOFException: Connection closed by remote host.
Is there any setting we need to make for the SOAP adapter to reduce these failures?
Or is it a problem with the receiver websystem?
Can somebody help me out on this?
Thanks & Regards,
Zabiulla

Hi,
For some reason the client (from the server's point of view - it might be some other device between the actual client and the server) is closing connection during the SSL handshake. As we can't get more info from the standard J2EE Dispatcher log files, we need more detailed info.
Please check
1. Execute network router trace utility (tracert for Windows systems or traceroute for UNIX flavours) to the J2EE Engine's host. It will show the active and non stealth routers between the client and the server:
c:\> tracert [J2EE_host] (windows)
$ traceroute [J2EE_host] (UNIX)
2. Activated low level SSL tracing
regards
Aashish Sinha

IDOC to SOAP Scenario

Hi All
Scenario is IDOC to SOAP.
As there is SOAP as a receiver side I asked to client to provide me WSDL file so that I can import into my PI. But Client sent me a BAPI structure instead of WSDL file.
So I want to ask is this posible to implement receiver SOAP using BAPI.
Regards
Dheeraj Kumar

Hi,
>>>Receiver side is portal so how come I can use RFC adapter?
portal has nothing to do with bapis - it's a display later for documents from the backend system (if we're talking about SAP)
so instead of doing a SOAP call you can use RFC adapter to connect directly to the "BAPI" engine - which is ERP
if you want to use SOAP - you need a WSDL - but the WSDL can be generated from BAPI too (keep that in mind)
Regards,
Michal Krawczyk

STO with WM with shipping and transportation process

Hi ,
Can anyone explain the process STO with WM with shipping and transportation?. What are all the config needs to be done for shipping and transportation?
Regards,
abi

<STO with shipping>
[1]
Please set shipping data for the receiving plant and supplying plant.
img -> mm -> purchasing -> PO -> set up stock transfer order -> define shipping data for plant.
receiving plant <> ship to party
supplying plant <> sales area.
[2]
Please assign delivery type and checking rule.
img -> mm -> purchasing -> PO -> set up stock transfer order -> assign delivery type and checking rule.
[3]
Maintain shipping point determination:
[4]
Maintain and assign confirmation control key (if you are using two step STO and want to post GR via inbound delivery).
This is the same as normal PO.
==========================================================
WM and transportation.
This is basically the same as normail WM and transportation.
Once outbound delivery (replenishment delivery) is created, the process is the same as normal outbound delivery.

Business Scenario and Business Process in IR

Business Scenario vs Business Process in IR???
Pls give the example for BPEL???

Business Scenario - it is nothing but how the business is done in a particular scenario. It mainly is documented in your Functional Spec.
Integration Scenario - http://help.sap.com/saphelp_nw04/helpdata/en/88/7adb7a030b424b8ef29b99461e52a8/content.htm
/people/venkat.donela/blog/2006/02/17/companion-guide-to-integration-scenario
/people/siva.maranani/blog/2005/08/27/modeling-integration-scenario146s-in-xi
Integration Process / BPM -
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm

Unable to convert sender service for IDoc to SOAP Scenario

Hi,
I tried to find the solution my way and by using the search function but without any success. I have the folowing scenario:
SYS(my sap system) => IDoc => PI (Process Integration) => SOAP => XML
When i send the IDoc to the PI System and open SXI_Moni the folowing error is shown:
"Unable to convert the sender service receiver_service to an ALE logical system"
I read about Adapter Specific Identifies so i go to ID->Service without partner->Business System->MyBusinessSystem(SYS) then in Menü on Services and checked Adapter Specific Identifies. They are like maintained in SLD.
Next is a Cache refresh i tried a full one but no impact
Then i tried a header mapping in receiver agreement. I mapped there the receiver party to the definied receiver party and the receiver_service to the service.
I have no idea
Thanks for help, be sure that helpful answers will be awarded
regards
Matthias
P.S. What causes this error ? For my opinion ALE has already done all neccesary things (The Idoc is in PI System and the data is available in mesaage payload) so why didn't the pi map it and send it via Soap?

Hi Matthias
>>I dont know if its helpful but in SLD are only the system of our landscape so i have no entry for the external Party.
Party information is generally not required to be maintained in SLD
>>Adapter Specific Identifies
What is the value you have given for sender Business system->adapter specific identifier. Is it the same as the partner profile name in sender SAPECC. if not try making them same.
Regards
Suraj

IDOC - SOAP scenario

Hi Guys,
I have configured the IDOC-SOAP scenario and i am sending to the target business partner with the soap receiver adapter.
I did not get any wsdl from the business partner instead i got the xml structure, target url and soap action. I have created a xsd for the given xml and send the data to the business partner.
The data is reacing the target system but the xml document has error saying "invalid at the top level of the document" and no xml is seen. I also get an acknowldegment error in sxmb_moni as
OUTBINDING CO_TXT_Routing_Back_Error
Error occured during back routing, error in communication channel
any help would be appreciated
Thanks,
Raj

I think this comes because XI requests Acknowledgement-IDocs by default. In many cases nobody processes these IDocs and so you get this error. Have a look at OSS-note 777175:
You are using Exchange Infrastructure 3.0 and receive IDocs using the IDoc
adapter. You want to be able to request acknowledgments separately in the
XI for each sending system and interface. In the IDXNOALE exception table,
you can deactivate acknowledgments for certain systems or interfaces.
Previously, you could only maintain the table with transaction SE16.
Report IDX_NOALE is delivered with Support Package 10. With the report, you
can add, delete and display table entries.
Report IDX_NOALE is extended with additional functionality as of Support
Package 11. This allows a sender system to request or deny acknowledgements
for all message types centrally. You can set exceptions to this central
setting by message type. Generic exceptions (for example, message type
'ORD*') are not supported. Entries that are already present in the table
are unchanged.
To perform these activities, you need the authorization to maintain IDoc
metadata (Object 'S_IDOCMETA' ID 'ACTVT' FIELD '02').
Hope this helps.

IDOC to websevice (SOAP) scenario

Hi Experts
I have a IDOC to SOAP scenario, i have searched for the step to step guide in SDN, but could not find it
Please let me know the step to step process for a IDOC to (webservice) SOAP scenario, like DT, MT etc.. and further steps
Regards
Lara

Hi Vijay
Thanks for the info shared.
below are the points observed from the links
My Scenario:
Source : IDOC
Target : SOAP
mode : Asynchronous
1. Import the IDOC which will be used in the message mapping at the source side
2. Create SOAP Datatype, Message Type, Service Interface.
3. Imoport the IDOC in message mapping and the SOAP message type that we have created in the above step
4. Operations Mapping and activate the scenario (same as normal idoc to file scenario)
5. Create Integration Scenario, SOAP Receiver Communication channel, Receiver Agreement, Receiver Determination, Interface Determination
Please let me know if anything else am I missing in this scenario
Regards
Lara

IDOC to SOAP asynchronous scenario Error handling

Need an expert!!!!!!!!! advise on error handling for IDOC--PI--
SOAP scenario.This is a asynchronous scenario where PI is calling a Legacy system using SOAP adapter.My question is how i can do error handling in this scenario.If i get an alert in pi with payload variable that would be fine, do i need to use BPM and if that is tthe case what will be steps.
Appreciate your help.
Manish

Hello Manish,
My question is how i can do error handling in this scenario.
Use the standard alert framework. Search on SDN / SAP Help for details.
do i need to use BPM and if that is tthe case what will be steps.
BPM is not required to raise alerts, as this is an async call.
Regards,
Neetesh

IDOC to File Scenario - Configuration steps need to be done in R3 and XI

Hi Experts,
I am working with IDoc to File scenario. Can someone please explain, what are the steps or configuration things need to be done in R3 and as well as in XI too.
Thanks in advance.
Regards,
Sree

Hi Sree,
I thought i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this answers your query.
Regards,
Abhy Thomas

Idoc to Soap BPM issue

Hello Experts,
I have implemented idoc to SOAP scenario using BPM. In which idoc data is sent to CRM webservice.
But my BPM scenario is not able to handle the idocs that are coming in quick succession in SAP PI.
For one idoc i get successful response and the other i gets stuck.
Please reply
Thanks in advance,
Vishal

The BPM goes like this ..
step1. BS system -
> Integration Process IP
step2. IP -
> CRM system
If 2 idocs comes to XI system ...first idoc goes successfully to CRM system
and the second idoc is stucka after step 1 .

IDOC to SOAP scenario and transport process

Similar Messages

Maybe you are looking for