Fault message monitoring

I have an asynchronous scenario of HTTP-> XI -> RFC. In my RFC function application errors may occur. I defined fault message type in my asychron inbound interface corresponding to exceptions of my RFC function.I tried to raise exception in my RFC function in following way:
message e001(CJ) with msg1_hlp raising UPDATE_NOT_POSSIBLE.
But I could not get fault message displayed in XI message monitor (SXMB_MONI).
Could somebody tell me what is the easiest way to show error messages in my case?
As far as I understand either I need to use BPM, or I need to use ABAP server proxy for raising exceptions. Must I use ABAP Proxy instead of RFC function? Then I may need to generate a ABAP Proxy to use as a wrapper for my RFC function, correct?
Thanks,
Hongbo

Hi,
Have you checked this blog, It will help,
<a href="/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1">Fault Message Types - A Demo</a>
Regards
Bhavesh

Similar Messages

Alert monitoring and fault message types

Hello,
this is a topic about two questions:
a) is it correct that alert monitoring is only possible in XI when using an integration process (BPM) and not for simple communication scenarios like IDOC -> file ?
b) how can I use the fault message in the message interface? (OK, I implement it, and then? where can I make it visible in the monitoring?)
10 points for answering in your own words instead of providing a link to SAP standard documentation!
(standard docs in XI look like they never giving a real answer, only something like 70 %! And the rest is trial and error!)
Oh, here is
c) When clicking on the alert inbox / configuration buttos in the RWB it looks like the addresses cannot be reached. How to fix that?
Best regards
Dirk

Hello guys,
these answers send me more happy to weekend!
Ok, not easy now to give points. Nobody answered 100 % but in total you solved my problems and answered my questions!
The OSS Michal gave solved my problem with the RWB access to alert config. (Where does this placing of the 5xx00 come from I had to replace in different places by 80xx ? >-( )
Thanks for the new challenge, Michal! we are working on SP12 and happy about it running now!
Hope to find a developer with your skills to implement alert messaging w/o using BPM!
Thanks for the answer about fault message and the link, Sudhir! Ok, with the rest, Michal was a little bit faster!
Best regards
Dirk

System Error in Message Monitoring while it shows checked flag in SXMB_MONI

Hia,
We are working on ABAP Proxy --> SAP PI 7.1 --> SOAP (Asynchronous Scenario).
(ECC -> PI -> Legacy CRM)
I have following queries:
1. While sending messge across to Legacy system, we can see CHECKED flag in SXMB_MONI but there is System Error in Message Monitoring. When checked legacy system is unable to receive any message. Cannot understand the issue.
2. Is there any way to check in PI system whether the message has reached Legacy System other than making scneario synchronous?
Regards

System is getting connected and able to send asynchronous messages to legacy system. But getting following error while sending synchronous error:
2010-05-10 13:15:05     Information     Delivering to channel: CC_SOAP_SOReject_Out
2010-05-10 13:15:05     Information     SOAP: request message entering the adapter with user J2EE_GUEST
2010-05-10 13:15:05     Information     SOAP: completed the processing
2010-05-10 13:15:05     Information     SOAP: continuing to response message f33caa90-5c07-11df-c659-96d147c2ff0f
2010-05-10 13:15:05     Error     SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     Error     Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.. Setting message to status failed.
2010-05-10 13:15:06     Error     The message status was set to FAIL.
I have already checked Data Structure and it is fine.
Regards
In this scenarios we are using XSLT mapping using CDATA.
Please suggest solution.

System Error in Message Monitoring -Proxy to SOAP async scenario

Hi All,
My scenario is ABAP Proxy---> SAP PI 7.1 ---> WEbService(Asynchronous SOAP ).
In Moni message is showing successful Flag, but message has got stuck in "system Error" at message monitoring.I can't see any Audit log in Message monitoring .
but in related Soap Receiver communication channel i can see the below Error
"2010-08-11 09:54:15 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 Information SOAP: sending a delivery error ack ...
2010-08-11 09:54:15 Information SOAP: sent a delivery error ack
2010-08-11 09:54:15 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005. "
Please help , what could be the problem.
Thanks in Advance.
Jyoti

Hi Jyoti,
>Is there any specific setup required at Provide side while moving to Acceptance system
I dont think so.
Please compare EXACTLY the settings of the two Comunication Channels, especially the server path. Please assure that you ve sent exactly the same message content from Acceptance system.
Regards,
Udo

Fault messages in target web service (microsoft visual studio) -experience?

Hi guys!
We use async scenario : SAP_R3 (ABAP Proxy) -> XI -> Web Service (SOAP). Target web service is created in microsoft visual studio. Standard scenario worx fine. We send data from r3, the web service processes them. However, we want to use also fault messages in case, there will be exception rised in the target web service and let operator in sxmb monitor know, that there's a problem. These fault messages should be used as acknowledgement. But we have serious problem with implementing fault messages in the target web service in the visual studio. Does someone have experience with this?
Thanx a lot for info!
Olian

Hi
see the below links
Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a61ff
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-a258cf083bca
Troubleshooting SOAP Message - XI - /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
Troubleshooting - RFC and SOAP scenarios-/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Regards
Chilla

SOAP error in audit log of message monitor

Hi,
I am using RPC wsdl file for idoc-xi-soap services. When I am doing the testing for the scenario in the message monitor I am getting the following audit log:
2008-02-29 15:21:48 Success Message successfully received by messaging system. Profile: XI URL: http://EMHBSSAP05.bekaertcorp.local:56600/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2008-02-29 15:21:48 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-02-29 15:21:48 Success The message status set to DLNG.
2008-02-29 15:21:48 Success Delivering to channel: ZCC_Material_SOAP
2008-02-29 15:21:48 Success MP: Entering module processor
2008-02-29 15:21:48 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2008-02-29 15:21:48 Success Message successfully put into the queue.
2008-02-29 15:21:48 Success The message was successfully retrieved from the receive queue.
2008-02-29 15:21:48 Success SOAP: request message entering the adapter with user J2EE_GUEST
2008-02-29 15:21:48 Success SOAP: completed the processing
2008-02-29 15:21:48 Success SOAP: continuing to response message a9ea9a30-e6d1-11dc-c8bd-001a4b0658c1
2008-02-29 15:21:48 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
2008-02-29 15:21:48 Success SOAP: sending a delivery error ack ...
2008-02-29 15:21:48 Success SOAP: sent a delivery error ack
2008-02-29 15:21:48 Success Acknowledgement creation triggered for type: SystemErrorAck
2008-02-29 15:21:48 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
2008-02-29 15:21:48 Success Acknowledgement creation triggered for type: AckNotSupported
2008-02-29 15:21:48 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
2008-02-29 15:21:48 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:.
2008-02-29 15:21:48 Success The message status set to WAIT.
Can anybody suggest what is the meaning and root cause for the error:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
Thanks & Regards
Prabhat

go to sxi_monitor and get the inbound message, later go to IR an do a TEST mapping.
any error occur?if yes, paste it here
generally soap fault o soap exception relate to an error from WS side,but before say nothing check you have all data and transformation OK.
hope it helps

Fault message handling in BPM

Hi again xi fighters
I created a business process with a synchronous sending step. I defined all interfaces and implemented also an own fault message type within the synchronous abstract interface. If the used RFC got the correct data the sync. sending step worked proper and also the business process worked fine. If I providing wrong data to the RFC to force him to throw an exception the Business process received the fault message. Then I just want to send the received fault message asynchronously to a file adapter within the defined exception branch. And now the question no-one answered in several discussion threads ;-<
How can I send the message? I am not able to implement a new variable in the container for the fault message type. Any advises here?????
Please help me, before I got inshane of SAP ;->>
Regards Oliver
Message was edited by: Oliver Bluhm
Hi everybody
any ideas, or is the question not clear. Please have a look and let me know you exlperience!
Regards Oliver

Hi Oliver,
how do you know, that is impossible to read the content of the fault message in the exception branch? Did someone from SAP say that? For days I read all the notes, blogs, help,.. and didn't find an answer.
It should work.
1. I have an integration process in XI sending a sync message to R3.
- OK
2. In the generated proxy class I raise an exception of the generated exception proxy class.
- OK
3. The exception message is shown in the message monitoring, containing also all our customer-data.
- OK
4. The integration process in XI activates the correct exception branch.
- OK
Missing: How do I get a grip on the data in the error message?
Kind regards Philipp
Message was edited by:
 Philipp Jakob

PI 7.1 Adapter Module Development - Identify SOAP Fault Message

Hi Experts,
here's a PI 7.1 Adapter Module Development issue I hope you can help me to resolve. It's about identifying SOAP fault messages.

Scenario at a glance:
Adapter Modules placed in the modules chain at request and response time in a synchronous Scenario:
- Request: SOAP Axis to RFC 
- Response and Fault Response: RFC to SOAP Axis

The issue is how to identify SOAP fault message in SOAP Axis Adapter Module in the response message:
The client gets SOAP fault messages like the follwong one:
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <ns1:exception xmlns:ns1="http://typen.geschaeftsstelle.pab.barmer.de">
 <ns1:errortext>bla bla bla ...</ns1:errortext>
 </ns1:exception>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>


But when trying to access the tags faultcode and/or faultstring in the adapter module via xPath expressions I do not get them. Obviously the SOAP Fault tags are built AFTER the adapter module has been passed. So my question is:
How can I clearly/uniquely detect a SOAP fault response message (and distinguish it from a "normal" response message) in my SOAP Axis Adapter Module?

I tried it the following way:


// Check Message Payload for SOAP Fault Message via xPath expressions
...
// SOAP Fault Code
zv_xPression = zc_constXPattern.replaceFirst("&", "faultcode");
zv_soapFaultCode = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// SOAP Fault String
zv_xPression = zc_constXPattern.replaceFirst("&", "faultstring");
zv_soapFaultString = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// check for SOAP Fault Message
if (zv_soapFaultCode.equals("") && zv_soapFaultString.equals("")) {
 // Create Audit Log entry - NOT a SOAP Fault Message
 zv_msgText = zc_constModuleName + " 0190: xPath - OK! This message is NOT a SOAP Fault Message";
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.SUCCESS, zv_msgText);
 zv_faultCheck = false;
}
else {
 ...
 // Create Audit Log entry - SOAP Fault Message
 zv_msgText = zc_constModuleName 
 + " 0200: xPath - this message is a SOAP Fault Message. " 
 + " - Faultcode is: " + zv_soapFaultCode 
 + " - Faultstring is: " + zv_soapFaultString; 
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
 ...
}
...

But zv_soapFaultCode and zv_soapFaultString are always empty (with other payload tags this coding works fine).

Any ideas? 
Thanx very much in advance!
Regards,
Volker

Hi Alex!
Like already mentioned I solved my problem by identifying the SOAP exception with the messageClass attribute of the PI message header. Acess code:
try {
String zv_msgClass = zv_piMsg.getMessageClass().toString();
} catch (Exception e) {
zv_msgText = zc_constModuleName
+ " E0110: Message processing terminated."
+ " Reason: Error while getting MessageClass "
+ zv_dataSource
+ e;
// create trace and audit log entry (severity ERROR) for exception
zv_location.errorT(ZV_SIGNATURE, zv_msgText);
zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
ModuleException me = new ModuleException(e);
zv_location.throwing(ZV_SIGNATURE, me);
e.printStackTrace();
throw me;
} // end of try-catch-block
But I do not think this will solve your problem. I am almost sure, that something in your Axis configuration is wrong/missing. If a handler cannot be instatiated then it really may be missing. Have a look at defaultTrace.trc. Maybe you will find more suitable information about the root cause of your problem. Also have a look at NWA under software components and/or application modules if you can find/see your modules.
But there is a general issue when trying to catch PI fault messages. If e.g. the requestor tries to login with wrong userid/pasword, then you will have no chance to catch this kind of error - at least as far as I know. Because in this very early stage of PI message processing no module is called.
One last question: Did you develop your own Adapter or just an adapter module? In the first case: Is your adapter started and healthy? Have a look at RWB -> communication channel monitoring.
Regards,
Volker

Handling Fault Messages

Hi,
I have this synchronous scenario : RFC > (XI without Integration Process) > SOAP.
Imagine that there is a problem with SOAP System and i get (don't worry about the error itself):
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException:
invalid content type for SOAP:
TEXT/PLAIN; HTTP 400 Bad Request</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tried to add ExchangeFaultData into SOAP Interface, and mapping it but it didn't work.
Can i get this exception mapped into RFC exception?

The usage of your fault message is not correct, since it is designed to handle application error, in your case, it is technical error, it should be handled by alert framework.
Liang
===========SAP Definition================
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
u2022 In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
u2022 The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement (see Acknowledgments).
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information.
========= End of SAP Definition================

Fault message in asynchronous ABAP Proxy

Hi,
I have a question about fault messages in asynchronous ABAP proxy server.
The configured scenario is SOAP XI ABAP Proxy. Between XI and the ABAP Proxy I have configured an inbound asynchronous interface with a fault message, and then I have generated all the classes and implemented some code for exception handling in the ABAP Proxy side successfully.
When I tested negative cases, the exception raises and it is visible in the SXMB_MONI transaction in the R/3 side, but this exception is not displayed in the SXMB_MONI of XI it just displays a successful delivery to the ABAP Proxy message.
According the XI documentation it says In the asynchronous case, you can see a fault message in the monitoring of the Exchange Infrastructure. But this is not working.
Am I missing something?

Hi,
This parameters are form group RUNTIME.
Please check it:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/content.htm
Regards,
Wojciech

Emulate Fault message in BPM

Hello
I have read all related topics
fault message in BPM process
Alert monitoring and fault message types
Using Fault Message Type in BPM
but no answer..
I have synch BPM that send synch request to RFC and a mapping step. Then I have to catch exception (of send step or mapping) and send fault message in exception handler.
I haven't a proxy. I want to create fault message manually and send it. Is it possible? I cannot create an interface of fault message type.

Hi Sergey,
As far as I know, it's possible to catch the mapping/send exception.
It's also easy to define an exception branch for this exception, and inside the exception branch, send a "normal" message in a send step.
However, as far as I know there's no way of specifying a BPM send step that sends a fault message.
At least in my experience, regular messages are just as useful when sending error information.
Cheers,
Ofer

Fault Message generated in ABAP Inboud Async Proxy not visible XI Moni

Hi
    I developed a ABAP Inbound AsyncProxy, which raises an exception using a fault message type. The SMB_MONI in the Business System is displaying the message as Application Error. But the XI Monitor is showing it as sucesfully processed.
    How do I monitor application errors from XI Monitor when I am sending Asynchronous Messages using ABAP Proxies?
    The business system in context is R/3 Enterprise System which is has got the APINT patch on it.
Thanks in advance...
Regards
KP

I'm developing a Java Proxy and I'm experiencing the same problem. The exception is raised by my Java Proxy and it can be checked in RWB Message Monitoring of my central adapter engine. It can alse be checked in the MessagingSystem.
Unfortunately, no message is returned to SAP XI, at least, I cannot see anything in SXI_MONITOR (SXMB_MONI).
The point is: does ir make sense to generate a fault message in xml just to be checked in an html monitor? The xml tags don't appear correctly in html format and I had to debug my application in order to find out that the exception was correctly returned.
If anyone here have advanced in this issue, please let me know.
Best regards,
Ricardo Bochner.

** Fault Message will support in JDBC Sender Adapter ?

Hi friends,
Will Fault message be supported when JDBC is receiver ? If it is, how do we raise exception, when any error comes in JDBC side ?
Kind Regards,
Jeg P.

HI,
This is not possible. Fault message types are only supported for ABAP/Java Proxies. The JDBC adapter does not provide fault messages.
You should avoid synchronous database insert as your sender program will dump, when a runtime error occurs in XI.
Refer similar discussion and solution
Treatement of Fault Messages in Synchronous Scenarios?!
Check this links
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Alert monitoring and fault message types
Thanks
swarup

SOAP adapter engine with system error, problem with fault message.

HI,
I have IDOC -> PI -> SOAP scenario.
Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
The error is at PI -> SOAP.
I have wsdl provided by the receiver webservice. Which I have imported.
And created a service interface against this wsdl. I tried changing it to both sync and async.
I have also provided fault message.
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
action = processDocument. Also provided user id and password.
I have a
Sender Agreement
Receiver determination
Interface determination
Receiver Agreement
I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
How does the receiver know which service interface is it? The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
Service interface name which I created in the ER. Where in the document the Reciever interface name is sent?
Where can I see the generated soap document for the receiver?
Is there some setting/configuration required in PI for this to work?
I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
When I provide the service interface name in the communication channel I get a valid fault message.
Similarly
When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
The fault message what I see in SOAPUI has the below format.
<soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
 <faultcode>axis2ns1:Server</faultcode>
 <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
 database default values were set. See the associated message for more information.
 BMXAA4190E - Country NZ is not in the value list.</faultstring>
 <detail>
 <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
 - Validation failed when the database default values were set. See the associated message for more information.
 BMXAA4190E - Country NZ is not in the value list.
 /Exception>
 </detail>
</soapenv:Fault>
And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
the above. Is this the problem? Can I change the data type here to be the same as above?
Audit log in the RWB adapter engine.
Time Stamp Type Description
30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
30.09.2011 15:10:57 Information SOAP: completed the processing
30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
30.09.2011 15:10:57 Error MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException
30.09.2011 15:10:57 Error Adapter Framework caught exception: null
30.09.2011 15:10:57 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.
30.09.2011 15:10:57 Information The message status was set to WAIT.
30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
15:15:57 NZDT 2011.

I tried changing it to both sync and async.
I have also provided fault message.
dont feel that you need to do above steps.
I have a
Sender Agreement
ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
When I see the message content, the SOap document shows me the details about IDOC
this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
How does the receiver know which service interface is it?
receiver need not know about the SI created in PI.
The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same?
you should the WSDL (external definition) as the Request Message in your service interface.
Is there some setting/configuration required in PI for this to work?
nothing specific...AFAIK
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
Things to check:
WSDL structure in PI and in target system is exactly the same.
does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
target system is up and running?

Using Fault Message Type in BPM

Hi,
In my BPM Scenario, I am using a synchronous send step in which I am using a fault message type.For giving the container for the fault message in the Properties area of the send step, I want to define a container corresponding to the Fault message Type I have already defined.How can I achieve this since it is not possible by defining an Abstract Interface? Can someone please explain how to do this?
Thanks and Regards,
Soumya.

Hi Soumya,
Here are the links for two threads. one has discussed fault mssage type in bpm and the other the general application of a fault message type.
thread1:- Alert monitoring and fault message types
thread2:- fault message in BPM process
Regards,
Sushumna

Fault message monitoring

Similar Messages

Maybe you are looking for