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

Similar Messages

IDOC to XML SOAP Scenario

Hi All,
I want to implement IDOC to XML SOAP scenario for 3 different IDOC types.
Should i implement it under same namespace or use different namespace for each IDOC to XML scenario.
Thanks,
Vishal

Hi,
depends on your requirement and your XML SOAP receiver
there are no general rules
Regards,
Michal Krawczyk

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 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

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

Hi, In a IDOC --- XI(BPM)--- SOAP Sync Scenario failrure.

Hi, In an IDOC ->XI(BPM)->SOAP Sync Scenario I observed recently messages are failing in SXMB_MONI with an error as:
com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: http://172.16.209.162/esdryrun/ContractData_Push. at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
friends, could u plz help on this.
Thanks,
satya.

Hello,
This indicates a configuration issue with this SOAP receiver adapter. Please check the on line help for the configuration of the SOAP adapter (the link is below). Please set the indicator in the "SOAP Action" field.
Configuring the Receiver SOAP Adapter
http://help.sap.com/saphelp_nw70/helpdata/EN/29/5bd93f130f9215e10000000a155106/frameset.htm
(Below is the extract from the link)
SOAP Action
Specify the SOAP action. The action specifies the value for the
SOAPAction in Web service messages; set the indicator.
Regards,
Sarah

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 - 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.

Error handling in File - XI - SOAP scenario without BPM

Hello!
We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
Regards, Tanja

Hi Tanja,
>>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
I think, you should check that out. It is assumedly only 2 days work to build a scenario:
IDoc -> BP
BP <-> SOAP/HTTP
BP -> IDoc (Acknowledgement)
In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
>>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
Filling of ALEAUD fields:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
I ve done such a scenario several times. That works without any problems.
Regards,
Udo

Error in IDOC(ALEAUD) to file Scenario

Hi ..
we have a client requirment were they want the ALEAUD acknowledgement in the form of file.
So we are creating a IDOC to file scenario, where IDOC is ALEAUD which is mapped to create a file in the traget system. but when we post the IDoc we get thwe following error.
*Note: have a small doubt. Can we use ALEAUD Idoc as a normal IDoc to File Scenario. because with the documents i understand that ALEAUD is a acknowledgment IDoc which is generated based on the request IDOC. but in our scenario we are manually using the structure of ALEAUD in the source system*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Kindly help me out .
Thanks in advance
Deepika

Hello,
If you need to send the ALEADUIT back to the SAP system if the file returns a successful ack, then you will need to have a BPM with a separate SEND step to send back the ALEAUDIT.
And check this ......
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
*******Reward points if found useful

HTMLError in sxmb_moni, Idoc to ABAP Proxy Scenario

Hi Friends
I am trying to send data from R3 to SCMTM system(SAP System), via Idoc to ABAP Proxy Scenario ,I am getting the following under HTMLError in sxmb_moni
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Any ideas will be helpful.

Hi,
I faced similar problem. it was due to configuration problem in SXMB_ADM. corss check specific server confiration in SXMB_ADM.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Reyaz

Synch SOAP scenario - access request data as part of response mapping?

Hello experts,
I have a synch SOAP scenario which is working but I want to improve the error handling.
Under normal situation I send the SOAP request and the remote web service responds with a given message structure which includes my invoice number as a key field. I then create an IDOC with this number and processing is great.
However, sometimes there is an error response from the web service which follows a different message structure and does not include the invoice number :-(
There could be many reasons for this error such as a field was missing or wrong format or even we ran out of prepaid web service calls (this is to get a government approval of invoice which we pay for in groups of approvals).
When they respond with an error I would like to send this information in IDOC to SAP, but I have no invoice number to tie the response to. Therefore the information is kind of useless in ERP. Is there a way in PI for a response message to reference the synchronous request data we sent to the web service in the first place?
Many thanks for your ideas,
-Aaron

Hi Aaron,
Also you can define static variables Sharing data between message mapping in PI 7.1
About Mark suggestion you have an interesting Adarsh Dhingra's blog here Sharing data between two message mappings through Dynamic Configuration
I think the better way is to use the Harish approximation because is the solution more standard.
Regards.

Regarding receiver determination problem in IDOC-XI-XML file scenario

Dear All ,
In IDOC-XI-xml file scenario , I have configured SLD , IR . But in ID , after file adapter , reciever agreement configuration when I am doing receiver determination configuration I am not able to insert mapping program in configuration overview of receiver determination as I am not getting "New Specific" option in mapping .
Can anybody suggest what could be the reason behind this .
Thanks in Advance
Prabhat

Hi PRabhat,
In RCVR determination, you need to select the party & service (as appropriate) save the obeject
then refresh the configuration overview of recr det.
then you can see the partner/service
then you can open it & add the necessary objects.
Regards
Vishnu

Fault message in sender SOAP scenario

Hi mates,
I've a o/b synch MI which is exposed as a web service. I've specified the fault message with faultcode, faultstring, faultactor and detail. I've a BPM as the receiver for this synch infterface. This BPM implements synch-asynch bridge.
Now the question is...How can I specify that a particular fault message needs to be returned to the SOAP caller. I can send the response for the SOAP caller using the send step with mode 'Closes S/A bridge'.
I appreciate you inputs.
thx in adv
praveen

Moorthy,
I've the FM in my BPM. But...how can I append this to Response message as these have two different MTs?
Do you mean to say my response message should have a node for fault message data?
I'm trying to implement sth like in this blog <a href="/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client">Propagation of meaningful error information to SOAP Client</a>
To achieve FM in SOAP scenario, should I be using <b>only</b> a non-BPM receiver like a R/3 system using FM with exception as the receiver? Can this be not possible if I use BPM as receiver?
thx in adv
praveen

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

IDOC to websevice (SOAP) scenario

Similar Messages

Maybe you are looking for