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.

Similar Messages

Error in IDOC to SOAP

I am doing IDOC to SOAP(3rd party) scenario and I get this error
<?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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have searched the forums and there is lot of info on this,
According to this blog
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
He says Click on the Business System and see the adapter specific Identifiers,So do I have to click on my 3rd pary Business System here? since for IDOC sender there will be no BS.Am I correct.
Thanks

Hi Guest
first login to SDN with good name
This problem occurs due to INVALID SENDER SERVICE
kindly check in your configuration whether you have given a valid name to your sender service and also check the conditions in RCVR deetermination
if not modify that and activate again .Make a CACHE refresh
hope this will work for you
Regards
sandeep
PS if helpful kindly reward good points

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

Idoc to SOAP Interface error.

Hi Experts,
Scenario is Idoc to SOAP ..
New to SOAP scenario -- so could anyone please help me out..
Here everything is good at PI, the problem we are facing is at the target system the payload is not getting delivered at the specified URL in SOAP receiver communication channel.
When i trigger the Idoc from ECC it is successful when i see in SXMb_moni of PI and when i see the status of receiver comm channel (RWB --> Adapter Engine --> Communication Channel Monitoring --> Receiver SOAP Adapter ) there the status is green and i could see the message id.
Here my doubts is there any possiblity of getting that URL from the message id which i see in the RWB --> Adapter Engine --> Communication Channel Monitoring --> Receiver SOAP Adapter
How to check whether that particular URL is working fine or not.
Thanks,
--Sai,

HI Raja,
Thanks for your valuable response..
one quick question.
Is URL present in the message id ..
i see the message iD in RWB--> Adapter Engine --> Comm channel Monitoring --> SoAP Receive Adapter..
When i open the message id there i see the message content tab in that we have 2 options soap conent & payload.
payload is the data which will be delivered to the target system..
Soap Content has the sender system and Receiver system details -- But i just want to know whether this soap content will have the target URL..
and when i checked in SXMB_MONI even i couldn't find the target URL anywhere.
But client is asking me to get the URL from the message id.
Thanks,
--Sai

IDOC to SOAP

Dear All,
My scenario is IDOC to SOAP(Asynchronous) .
In MONI ,I am able to see the succesful message but in receiver communication channel, I am getting the following below error,
SOAP:call failed:java.net.ConnectException:Connectiontimedout:
Please suggest me on this.
Regards,
Lavanya B.

Hi Lavanya,
Its very hard to tell exactly where it is going wrong. Some issues are already mentioned by prateek. Apart from it you can take the receiver payload and see whether it is the same as expected by the webservice or not. If possible try to load this payload manually so that if any issues are there you may come to know.
Regards,
---Satish

IDOC --- XI ----- SOAP

Hi All,
Our Scenario is IDOC XI SOAP synchronous.
We get data from IDOC to XI and send it to SOAP, I get response back from SOAP which is sent to R3 by STATUS IDOC.We have implemented BPM in our scenario and there is no Exception handling.
My question is, if the SOAP server is down then I get a System Error.What we want to know is
1. Whether it is possible to send the failed IDOC again to SOAP from XI and get the response back( I guess this is not possible in our case). Does Exception handling enables this feature ??
2. Is it possible to know the status of SOAP server in BPM so that we can keep the incoming IDOCs in queue and send them once the SOAP is up?
3. If Exception handling/Fault messages concept is implemented then can we send response back to STATUS IDOC from XI(Note: We need the incoming IDOC number must for this as R3 should know which IDOC is failed).
Points will be rewarded for helpful answers.
Thanks & regards,
Satish

Hi Satish,
1. Whether it is possible to send the failed IDOC again to SOAP from XI and get the response back( I guess this is not possible in our case). Does Exception handling enables this feature ??
Ans) It is possible to resend the data from the XI system if it is failed and sits in the Adapter engine (Message monitoring) here you can resend it once the SOAP server is up.............
2. Is it possible to know the status of SOAP server in BPM so that we can keep the incoming IDOCs in queue and send them once the SOAP is up?
Ans) Yes it is possible to know the status of the SOAP , for this you need to include a step in the BPM to have a lookup at the server(SOAP)...Once it is up the workflow can be restarted again manually.................
3. If Exception handling/Fault messages concept is implemented then can we send response back to STATUS IDOC from XI(Note: We need the incoming IDOC number must for this as R3 should know which IDOC is failed).
Ans) Yes if the exception handling is done then it is important to have the incoming idoc number so that the response will be send with this idoc number and also the status of the mentioed idoc ..you can achive this with exception handling
Regards
Sai
Reward with points will helpfull

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

XI SOAP adapter : Error during parsing the SOAP part

Hello experts,
We have several scenarios SOAP to IDocs.
We are on XI 3.0 SP19, and since 9/6/09 around 4:00 PM GMT, our SOAP channels used to communicate with a specific 3rd party all stoped accepting incoming SOAP requests. All the messages are stucked on third party side, and we get the following error in the defaulttrace and application logs :
#1.5#001125A5BCD00066000076850013109E00046BF6A963E479#1244607054865#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.mo.Message.reparseRootDocument()#PIMSOAP#21217##pxaci_PXA_6443451#PIMSOAP#a71ebfa0556d11decc24001125a5bcd0#SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#com.sap.aii.messaging.mo.Message#Plain###Error during parsing the SOAP part --- java.lang.NullPointerException#
It happened at the same time on all the environments for every interfaces using SOAP message from this sender to XI. That's the reason why we think it is a global issue, but we can not find anything concerning this error. Has anybody encountered this error or would have any clue of where it comes from ?
Many thanks,
Best regards,
Guislain

Hello Michal,
Thanks a lot for your help. Actualy we have tested with SOAP UI yesterday and this is what came out of the tests :
test 1 : we tried to call the XI service with the wsdl and put dummy data inside --> test OK
test 2 : we loaded in SOAP UI one of the file from our partner and tried to call the service --> test NOT OK
test 3 : we realized that there were some blank lines at the beginning of the file provided by the partner. we removed these blank lines --> test OK.
So we first thought that the format of the file sent by the partner was wrong and this is why we were getting the parsing error, because of these blank line. The thing is that these blank lines have always been here ! We have checked with old successful messages and they contain also these lines and if we test them in SOAP UI we get an error also. so it does not seems to come from this.
Moreover, as I said in my previous message, it happened on all the environments approximatly at the same time, so we are suspecting a global problem, but which one ? That's the million dollar question
Would you have any other ideas ?
Thanks a lot,
Best regards,
Guislain

IDOC to SOAP synchronous scenario

Hi All,
We have an IDOC to SOAP synchronous scenario in which IDOCs are sent to SOAP by calling a service and then SOAP sends a response back to XI . The response is not sent to SAP- R3. Please suggest on this
Thanks

Hello Rajesh,
Thanks for your good justification.
Here I have also replicated same kind of scenario and having same kind of issue.
One thing just wanted to confirm - Even though SOAP adapter expects HTTP 200 response back from webservice, still SOAP channel is getting into red with following , and as we have Alert configured ...Alert mail also receiving as part of Error only. So How can we avoid that response ? Is there have any parameter to handle or suppress the response back?
Thanks!
Goutam

HTTP response code 500 : Error during parsing of SOAP header

Hi Experts,
I have a MAIL to IDOC scenario. An external third party emails invoices to our inbox - which we pick up and process the attachment. All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
When I look at the SOAP header of the failed message I see the values from the dump in this field:
<sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
Can anyone tell me what SHeaderTHREAD-INDEX does? Or what my problem is (Our email is Outlook)
ERROR MESSAGE.........
SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

We work with Microsoft Outlook, but I'm sure this could work with any email system.
This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company. This is set up as a regular email account. On this email put a forward rule to email2 for a particular sender/subject. email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
Doing this accomplishes a couple of things:
1) We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
Hope this helps your situation.

Messages get lost between IE and AE (IDoc to SOAP - Async)

Dear Experts,
in a IDoc to SOAP (Async) scenario a message was not transferred. I could not see any error message in RWB or ABAP Monitoring. When I enter RWB, the column engine is "Integration Engine" and the status is "Successful". At the same time other message with the same message interface were transmitted and they have engine "All" and status "Successful".
Why was this message not passed on to Adapter Engine? How can I restart the processing, so that the message is transfered?
Best regards,
David

Thank you for your answers:
@ Divyesh:
I can't resend the message. It does not have an error status. It says "Successful", although it only can be seen in Integration Engine, not Adapter Engine. There are not SM58 errors.
@ Krish:
In ABAP Monitoring all steps were performed as expected. Before and after this message some other messages with the same message interface were transmitted and they are visible in ABAP Monitoring, Inegration Engine and Adpater Engine.
@Hareenkumar:
In SAP everything looks like expected.
The only difference between this message and other messages sent at the same time (which were transmitted correctly) is that in RWB Message Monitoring (Component: Integration Server) the Engine is "Integration Engine" instead of "All". And the message is not visible when you select for component "Adapter Engine".
Do you have another idea?
Thanks in advance,
David

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

Error on IDOC to SOAP

Similar Messages

Maybe you are looking for