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

Similar Messages

File-PI-SOAP Interface error

Dear All,
We are trying a interface in which we wanted to do Post Goods Issue in SAP from a file. We have exposed our Z-RFC which will do PGI as webservice and has imported its WSDL in PI.
Then, we have created a File-PI-SOAP interface. Now, when we are testing the interface we are getting success message in SXMB_MONI but in RWB, message for picking the file is success and when I am opening the message details its showing
" 500 Internal Server Error" ""Application error occurred during the request procession."
Details: "The WebApplicationException log ID is [001A64D0A1FC005F0000004600002E4800CEA8DA2043BF9A]."
Same error is showing for the receiver message but at payload I am able to see the correct values.
Kindly let us know, if any configurations are to be required to remove thsi error.
Regards,
NJ

Hi,
>500 Internal Server Error
does mean the server does not understand the request. I your case: You want to make use of a service which assumedly no exist. May be you have to release or activate it or to do something in SOAMANAGER. Please check your service first with SOAP UI.
Regards,
Udo

I am triggering My IDOC for XI interface Error passing data to port

Hi All
when i checked the partner profile , it is givng the error as this one , and i dont to how to go for this one
No Message Control entry for this entry

Hi Sridhar,
Cross check with this weblog:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Sachin

Error while testing File-PI-SOAP interface

Dear All,
We are working on File-PI-SOAP interface in which we have exposed a functional module from ECC server as receiver webservice. When we are testing the the interface we are getting following error :
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/PLAIN; HTTP 407 Proxy Authentication Required.
In the receiver SOAP communication channel we have provided the required ECC login & proxy authentication credentials and also we are able to open the URL from PI server. Kindly let us know what more settings are required o make this interface running.
Regards,
NJ

Hi,
This is a synchronous interface and I want to send the output from webservice as a file to third party system.
We are just working on a demo interface, so we have created a webservice of a function module of ECC and also our interface is File-PI-SOAP.
We have also given the login credentials for proxy authentication but still we are getting the error the
SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/PLAIN; HTTP 407 Proxy Authentication Required
Kindly let us know, how can we resolve this error.
Regards,
NJ

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

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.

Error in IDOC ststus , for interface IDOC to File

Hi All,
iI am doing IDOC to file interface , in which i am using IDOC Orders05, we are using the same IDOC for other interface to connect with DOTNET connectors , when i trigger the IDOC ORDERS05 for my interface when i check the ststus , in which it is pointing the to partner No and Port to that dontnet, not to my Iterface for SAP XI , anyone there to help me in this isssue
Thanking you
Sridhar

Hello,
While sending Idoc you will be providing the Port which in turn needs RFC Destination and this is one which takes the document to External system configured in RFC.
If you need to send the idoc to External Systems other than R/3 then you need to use T type connection which uses JCO for estblishing session. if it is R/3 then requires logon credentails and type 3 for configuring RFC.
HTH
Rajesh

SOAP Receiver- Error While Sending Message: 500 Internal Server Error

Hello,
Our scenario: IDoc to SOAP
I have added a third party system in the SLD and have used the same in my ID configuration.
An idoc will be triggered from R/3, which will received in PI, PI will transform the IDoc into SOAP message for the third party system.
I have tested the scenario in ID from Interface Determination and its successful.
But when i try to try to test it from RWB, using Test Message in Adapter Engine, I get an error,
"Error while sending message:500 Internal server error"
If we test it using a testing software like SOAP UI, it works fine but from PI we get the error mentioned above.
Regards,
Abhishek

Hello,
Since the IDOC adapter resides on the ABAP stack, you can use this URL instead (it will be sent to the integration engine as Venkata suggested)
http://host:port/sap/xi/engine?type=entry
Also check your firewall settings from PI to the third-party system.
Hope this helps,
Mark
Edited by: Mark Dihiansan on Feb 7, 2012 11:48 AM

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

Xi sending the IDOC to R/3: Error

Hi
I am sending the idoc from XI, i am getting following error " <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>".
Kindly let me know have i done anything wrong in configuration in XI and r/3 for posting IDOC.
<?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_WRONG_INTF</SAP:Code>
<SAP:P1>MI_In_IDOCDebmas</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_In_IDOCDebmas</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
did you import correct IDOC type in the Integration Repository?
do u have external definition created for mapping ? Check those all are correct?
Re-import the IDOC into the IntegratioN Repository and activate again..
Also make sure that you are using IDOC itself as an Message Interface during Interface Mapping. No need of creating new Message Interface for the IDOC.
I think you have done mistake in creating the Message Interface for the IDOC. It is not required Use the same IDOC itself
related tips:
File-IDOC, idoc interface error
Hope this helps,
rgds,
Moorthy
Message was edited by:
Krishna Moorthy P

Idoc to soap sync without bpm. is it possible? Helping me..

Hi Experts,
i have a small clarification Idoc to soap sync interface in sap pi 7.0. i created IDoc to Soap sync using BPM but some times the signals are stuck due to load issue in swpr, while reprocess those signals all going successfully to the receiver. So We are trying to eliminate BPM.
I just wanted to know Idoc to Soap sync scenario without BPM is possible or not in SAP PI 7.0?
if it is possible kindly send me the links
Regards,
Kiran polani

Hi Kiran,
Could you please let us know the exact requirement. How do you want to send the response back to IDOC?
ASync - Sync Bridge with IDOC sender is not possible in PI 7.0.
If It is something like IDOC --> SOAP --> IDOC , And If the SOAP request is small then you can use SOAP Lookup in IDOC to IDOC Scenario.
In The mapping You can do a lookup and get the response from SOAP(Webservice) and map that to your Target IDOC.
This is one possible way for you without BPM in PI7.0.
Please let me know if you need more details about this.
Thanks
Jyothi A

Idoc to SOAP Interface error.

Similar Messages

Maybe you are looking for