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

Similar Messages

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

IDoc to Soap, with BPM - Permanent error in BPE inbound processing

Hi Experts,
IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
How to rectify this any issue???
Thanks-
sk

Hi,
The inbound processing encountered a permanent error and the queue therefore stopped.
The error message "Permanent error in BPE inbound processing" may be caused by the following:
- At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
Refer to the help in Note 1082099
- The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
- Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful.

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

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

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

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

PO is getting created but showing error is address with status of IDoc - 51

Hi Experts,
I am using IDoc type - PORDCR103
Process code - copy of IDOC_INPUT_PORDCR1 (Function Module)
After processing through WE19 it is generating an IDoc number with status - 51 showing error in Address , But it is creating a PO.
My requirement is In status -51 It should not create PO.
Inside IDOC_INPUT_PORDCR1 a Bapi 'BAPI_PO_CREATE1' is used for creating PO. Here In RETURN parameter of BAPI a Row is comming with Message type - E. Some other messages are also there of type 'S' and 'W'.
After processing , PO is getting created with staus - 51.
Please help me .
Thanks
Susanta
Edited by: Susanta22 on Oct 11, 2011 12:29 PM

Hi,
in ur code ur filling the idoc data rcord, control record ryt ..before u append data to idoc data , u r also validating and u might be doing in loop for appening the idoc data.
if there is any error in idoc then it won't distribute the data, it will be in error status only..u can only see the data in WE02. Then u can also change the data in WE02 and redistirbute it via BD87.
if u have any conerns let me know
Regards,
Nagaraj

Error on IDOC to SOAP

I am using IDOC to SOAP scenario for sending location details to the third party webservice. initially the scenario was working fine. Now its not working properly. Where I need to check to find out the problem.
Thanks & Regards,
Jay

Hey,
First check in the following transactions the status of IDOC.
WE02, WE03, WE05, BD87.
If the status of the idoc implies message is successfully send to XI, then login to XI and in sxmb_moni check the message in the payload.
if the message is successfully given away by XI then see whether the web services are deployed properly.

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 Receiver Fault Message Handling?

Hi,
I am working on IDoc to SOAP Scenario (IDoc -> PI -> SOAP). It is in async mode without BPM. This works fine as long as there is no error on the SOAP receiver side. How to handle the falut message raised by the SOAP receiver and send it back the SAP ECC.
Do I need to use ALEAUD IDoc for this? If Yes, how to configure this to handle fault message? Is there any other way of doing it?
Could you please give steps to handle the fault message?
Thank you.
Regards,
Cdr.

Have a look into the below threads -
How to capture SOAPFault in an Async/Sync Scenario without BPM
Acknowledgement Handling in IDoc to SOAP Scenario in PI 7.3

IDOC -XI-SOAP one sender different receivers based on condition

Hi All,
I have an IDOC to SOAP scenario.
For each record based on the input flag XI has to send the any one of the request ...like either create or update or delete request. All these message types are a part of single WSDL.
How can i do it?
Thanks in Advance
Jyothsna

hi There are two ways you can do this:
1. Without BPM - Since you have to create all the target messages adn you want either the 1st and second, or the first and third: create two multi-mapping with one and two, and one and three. In the receiver determination check the condtion based on which you decide the second or the third message has to be created and route it to the correct mapping accordingly.
2. with BPM, create all the target mapping. In the BPM check the condtion in the switch and do a send accordingly.
You can do this either on Receievr Determination or on Interface Determination.
Add multiple Receievrs/ Interfaces and then add the conditons on which the target should be choosen
to use Xpath for your receiver det. ref these blogs;
a combination of logics should help you in this case ...
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
pls reward points if solution found helpfull
regards
chandra.k

IDoc to SOAP scenario is showing error

Similar Messages

Maybe you are looking for