Exception handling with fault message type not working

Hi,
I have a sync proxy to proxy scenario and I have created a fault MT and specified in the outbound and Inbound service interface...
*In Inbound proxy I have the following code--*......
RAISE EXCEPTION TYPE z_cx_test_fault
EXPORTING
standard = l_standard_data.
In the sender side abap code which calls the outbound proxy I have the follwing code -
CATCH cx_ai_system_fault INTO lo_cx_ai_system_fault.
txt = lo_cx_ai_system_fault->get_text( ).
WRITE txt.
CATCH z_cx_test_fault INTO lo_cx_test_fault.
txt = lo_cx_standard_message_fault->get_text( ).
WRITE txt.
CATCH cx_ai_application_fault INTO lo_cx_ai_application_fault.
txt = lo_cx_ai_application_fault->get_text( ).
WRITE txt.
when i test the inbound proxy separately I get the custom fault message properly...
however when i run the proxy to proxy sync scenario and the custom exceptionz_cx_test_fault  is raised inside the receiver proxy .......control goes to CATCH cx_ai_application_fault    and not CATCH  z_cx_test_fault .
I understand that cx_ai_application_fault is the super class of all the exception class but why does control go to its exception handling when a custom exception is raised...
Edited by: hema T on Feb 26, 2012 1:16 PM
Edited by: hema T on Feb 26, 2012 1:17 PM

Hi
I tried changing the sequence also but it did not work...
I can see an appropriate response coming from the receiver in SXMB_MONI of PI...this response has the "fault response "
"fault detail" data that I want.....however when the control goes to the sender why does it go to CATCH CX_AI_APPLICATION_FAULT and not not my CATCH z_cx_test_fault .
My observation - If I change the scenario to SOAP to Proxy sync..then the sender SOAP client gets the appropriate custom fault message back.
Edited by: hema T on Feb 27, 2012 1:17 PM
Edited by: hema T on Feb 27, 2012 1:17 PM

Similar Messages

  • Automizing error message with Fault Message Type

    (Request F6)  (Request F6)
    System -
    > XI -
    >        SAP (Doesn't have F6)
              <-- XI <--
          SAP (Doesn't have F6)
       (Respons: error)    (Respons. error)
    (Problem) When the request message doesn't content sufficient information that is required for respons then the XI team will get the message error and the responsibility to solve the problem. In this scenario it is the XI team that sends the error respons to the System.
    (Request (eg. F6) )  (Request (eg. F6))
    System -
    > XI -
    >        SAP (Doesn't have F6)
              <-- XI <--
          SAP (Doesn't have F6)
       (Respons: error)    (Respons. error)
    (Solution) We want to automatize the process so that the error message goes directly to the System via XI. In other words we only want an acknowledgment of the error in XI, we don't want to solve the error since we believe that it is the sender System that is responsible.
    We have seen that there is a Fault Message Type in the Message Interface and we are wondering if that is the way to do it? And it that case, how?

    Hi,
    Fault message is a error meesage. Its like an exception in simple terms. The fault message is used to
    store a log for application error. Fault messages is defined in IR.
    To give a overview on Fault messages it is mostly used in synchronous communication. When an error
    occurs at the inbound side instead of sending the response message back it sends a fault message back
    to the sender system to handle error.
    Fault Message are Msg type that provided whenever u create a namespace..they are usually used to get
    the exception or error mapped which has occured while execution of Application at the sender/receiver
    end....
    One scenario where i had used it from Soap to RFC where i defined the exception in rfc source code at
    r/3 end...I mapped that exception to Fault msg type that i created of my own type(didnt used the
    default)..
    Fault messages are used to propogate / send back the error message to the calling application. This is
    used when there is a failure and the sending system needs to know what the error was. This is more of
    catching Application Errors
    check this nice blog also
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
    Asynchronus RFC  exception handling
    XI Alerts are not getting triggered from proxy servers
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-
    a258cf083bca
    /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
    Fault Message
    Regards
    Seshagiri
    Edited by: N V Seshagiri on Feb 29, 2008 12:19 PM

  • Error handling using fault message type in outbound synchronous ABAP proxy

    Hi,
    We've a scenario, outbound synchronous ABAP proxy to synchronous SOAP receiver. The requirement is to send multiple records in a single rquest and get response for all the records sent (in the same response message).
    Say if I send 10 records from ECC, I should get 10 records as response from SOAP to ECC. But the problem here is, there could be some invalid requests, for which an invalid error status code should be sent as part of response.
    Source Structure
    Req_Proxy
        req (0..unbounded, string)
    Response Structure
    Resp_SOAP
      Resp (0..Unbounded)
           respString (0..1, String) (carries the actaul response message)
          status code (0..1, String) (carries the status of the response, for ex, 001 (successful), 002 (error))
    And now we are planning to make use of Fault Message Type, to track the errors from SOAP (status code 002). But, we are not sure on how to track this for all the requested records. Is it possible to track the errors for all the requested records in a singe call using fault message type? For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8 for valid and 2 for invalid accordingly.
    Please calrify.
    Thanks.
    Rohit

    For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8
    for valid and 2 for invalid accordingly.
    Check if you can modify the WSDL structure to include an error node that would get populated incase of invalid entries....this would mean that you get the success and failure details in the single message....also at the proxy-end make the necessary change in your DT.....may be then you do not need to use the fault message...
    Regards,
    Abhishek.

  • Creating new logical ports for WSDL with several port types not working

    Hi all,
    I am trying to integrate some BODS webservice into the BPM. I am using CE 7.2 Kernel Version:     7.20.3710. When I am trying to assign a provider system in the application configuration I get following error:
    The provider system successfully found the needed service, but its wsdl is without webservice policy. Thus the generated client configuration might not work because of different configurations between service and client (most probable a difference in the security settings). Either assign a provider system with access to wsdl with policy or manually create the client configuration.
    The regarding provider system is using a communication profil where the authentication method is set to "none". Normally this configuration should work, but it isn't.
    So I started to create new logical ports for each port type. But then I get the error:
    Port type name of loaded WSDL does not match the port type name of the Service Reference.
    I checked already the port type names in the WSDL but they are 100% the same. What I found was that the configuration is always trying to use the first port type in the WSDL. So I am not able to configure the other port types in the service group.
    I also tried to do the same thing using a WSDL with just one port type and surprise it is working...
    I hope somebody can help me out
    Thanks in advance
    Andy

    Hi Andy,
    Please check this Link: https://cw.sdn.sap.com/cw/docs/DOC-45012
    Regards,
    Naresh B

  • Types of fault message types

    Can someone tell me the different types of fault message types available in XI?

    Hi,
    Fault Message Types
    are used only for returining messages form the inobund side (application)
    http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/content.htm
    if you want to create error handling for a mapping
    you can use transformation step (in a BPM)
    add a block and catch the mapping error inside this block
    (and for instance send a file from this exception branch
    Refernces Fault message types for the Exception handling .
    Fault message types corresponding to the standard SOAP Fault type can be included (execepted in the outbound Asynchronous case)
    A fault message is a message that describes an application-specific error situation.
    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.
    · 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.
    · 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.
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
    Please see the below links
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-a258cf083bca
    /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    Thanks
    Swarup
    Edited by: Swarup Sawant on Mar 28, 2008 3:05 PM

  • Difference in Fault message types & exceptions for Webservice in ABAP

    Hello all,
    I am relatively new to the web service framework in SAP. My problem scenario is as follows.
    I have a WSDL file of a webservice from 3rd party non-SAP s/w  and I want to replicate the same webservice into SAP by creating FM in SE37 with same imp/exp parameters and functionality.
    So I first created a consumer proxy using the external WSDL file of non-SAP webservice. This generated imp/exp DDIC structures in SAP. Now I created a RFC FM in SE37 with similar Imp/exp parameters and relesed this FM as a webservice.  I then created another consumer proxy using WSDL of this newly created webservice in SAP.
    In the old consumer proxy I see a structure as SOAPFault as a Fault message type which has 3 fields ERRORCODE, TEXT, DETAILS but in the newly created consumer proxy I don't see Fault message types but i see exceptions which i mentioned in exception tabs while creating the FM. The imp/exp parameters are identical.
    So my question is while creating a web service in SAP using a FM in SE37, what needs to be done in order to get the Fault message types getting created automatically when we create a consumer proxy for this webserivice?
    Also based on the WSDL of 3rd party system , can i replicate the same web service in SAP ?
    Appreciate your expert advice on this.
    BR
    Nilesh Puranik

    Hi Krishna,
    I've read the SAP description about Fault Message Types but I'm still struggling on how to use them correctly.
    Why do we need them if I can't do nothing with it on the BPM side? After the mapping of the FMT, I'd like to acess it so that I can send a description back to the original system...The thing is, in BPM you can't acess the FMT, you can only create a new BRANCH (on a block step) for it...
    I've tried to acess the description text on trace which comes with the message, but it seems that the trace only serves for posting info, and not for getting any...
    The Mapping Runtime Constants have some information where you can read some descriptions, but nothing related to the errors....You can read the Receiver service, sender, interface_namespace, but nothing from the ERROR tag...
    Is there a way to get the description? Or anything related to the error tag?
    Thanks in advance

  • Fault message types: Why do we need them?

    Hi guys,
    I have a bpm scenario created, tested and working.
    This bpm starts with a async receive, a Sync Send to a R3 system by an ABAP proxy and a final async send to the original system.
    I'm contemplating exception handling and other type of errors. Meaning, if the abap proxy dumps I can raise an exception and map it on the XI environment. The thing is, on  sxmb_moni I get the exception handler, with the exception texts, id's, etc... from the R3 being mapped to the XI fault message type.
    But the problem is I can't get to map the text from the fault message type into any field from the response of the original system.
    I've searched the forum and I've seen that this area is surrounded by doubts and questions...
    But in the end I'm forced to place the question, why do I need the fault message types? What use can I give them, besides of the cute little thunder on the sxmb_moni?
    Thanks for your attention guys

    Hi Krishna,
    I've read the SAP description about Fault Message Types but I'm still struggling on how to use them correctly.
    Why do we need them if I can't do nothing with it on the BPM side? After the mapping of the FMT, I'd like to acess it so that I can send a description back to the original system...The thing is, in BPM you can't acess the FMT, you can only create a new BRANCH (on a block step) for it...
    I've tried to acess the description text on trace which comes with the message, but it seems that the trace only serves for posting info, and not for getting any...
    The Mapping Runtime Constants have some information where you can read some descriptions, but nothing related to the errors....You can read the Receiver service, sender, interface_namespace, but nothing from the ERROR tag...
    Is there a way to get the description? Or anything related to the error tag?
    Thanks in advance

  • Doubt on technical systems and fault message types

    Hi,
            I had still doubt & i'm not clear to answers i got yesterday , plz clarify my doubts
             1.what are fault message types and   how  do we catch any exceptions  in file to  proxy scenario , can any one give simple example ?
             2.How do we register a non-sap system(FTP SERVER) in SLD  ? what steps  should we follow? Does any one have blogs regarding this?
               Plz answer to this questions, good answers will be rewarded.

    Hi Smitha,
    <i>1. what are fault message types and how do we catch any exceptions in file to proxy scenario , can any one give simple example</i>
    Fault Message are Msg type that provided whenever u create a namespace..they are usually used to get the exception or error mapped which has occured while execution of Application at the sender/receiver end....
    One scenario where i had used it from Soap to RFC where i defined the exception in rfc source code at r/3 end...I mapped that exception to Fault msg type that i created of my own type(didnt used the default)..
    Refer this for Fault msg usage in Asynch scenarios.
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    Refer this for Fault msg usage in Synch scenarios.
    /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
    Refer this for Handling Exceptions
    http://help.sap.com/saphelp_nw04/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm
    <i>2.How do we register a non-sap system(FTP SERVER) in SLD ? what steps should we follow? Does any one have blogs regarding this?</i>
    For this you have to define the 3rd Party TS & BS in sld.
    Have a look at the following links...
    http://help.sap.com/saphelp_nw04s/helpdata/en/fa/0aad3efa11b300e10000000a114084/frameset.htm
    Cheers...
    Vasu
    <b>** REward POints if found useful **</b>

  • Guide for Fault Message Type

    Hi,
    I search a guide for configuration a "Fault Message Type".
    I have read, if there is a mapping error, XI will create a error handling in a xml-file.
    But I can not find this file.
    Can you help me please?
    Thanks.
    Regards
    Stefan

    Hi Stefan,
    Exception can be declared in BPM steps like Transform,send,Block and handled in Exception Branch.
    TO know more about BPM and its exception go throught this link,
    http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
    Cheers,
    Rashmi

  • Regarding mandatory fields, Context Objects and Fault Message Types

    Hi All,
    1) I am creating a structure with fields "Name", "Street" and "City". While creation i want to make "Name" fields as mandatory. Is it possible. If so how to achieve this.
    2) What is the purpose of Context Object and in which situation we will use this.
    3) What is the purpose of Fault Message Types and in which situation we will use this.
    4) I am doing file to file scenario, at sender side i have set the adapter as file and transport protocol as "FTP" . It is asking for "Server", "PORT" and "Login Details". What is this FTP, for this do i need to take any login details. I am totally not aware of FTP, could please explain more about this.
    Kindly look into the above points and respond point by point.
    Thanks in advance.
    Regards,
    Prem.S

    Hi prem,
    <b>1) I am creating a structure with fields "Name", "Street" and "City". While creation i want to make "Name" fields as mandatory. Is it possible. If so how to achieve this.</b>
    give occurence 1..unbounded. for the field name.
    <b>2) What is the purpose of Context Object and in which situation we will use this.</b>
    If u have multiple receiver system then to determine the reciever u can use context object.....
    the alternative of context objetc is X-Path...
    Check out these
    http://help.sap.com/saphelp_nw2004s/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/content.htm
    /people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
    Here is a scenario where context objects were used for BPM
    Technical Context Object in ccBPM
    Get the details here:
    http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm
    Technical Context Objects :
    http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm
    A list of the Technical Context Objects names can be found here:
    http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/content.htm
    Difference between context object and x-path:
    diff between context object and x path
    <b>3) What is the purpose of Fault Message Types and in which situation we will use this</b>
    whenever u want to catch some exception u can use fault message types.Just for a example u r sending some data to SAP system.But due to some reason the R/3 system is down.so in this case if u have implemented fault message ..u can get a error message specifying r/3 is down....
    Fault message implementation.
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    How to Guide
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40574601-ec97-2910-3cba-a0fdc10f4dce
    <b>4) I am doing file to file scenario, at sender side i have set the adapter as file and transport protocol as "FTP" . It is asking for "Server", "PORT" and "Login Details". What is this FTP, for this do i need to take any login details. I am totally not aware of FTP, could please explain more about this.</b>
    there are two transport protocol for File adapter
    1)FTP(File transfer protocol)
    to know abt FTP check here
    http://help.sap.com/saphelp_nw04/helpdata/en/43/0e16bfd7b021aee10000000a1553f6/content.htm
    2)NFS(Network File System)
    in server :Enter the host name or IP address of the FTP server.
    in PORT:Specify the port number of the FTP server.
                 The default is the standard port for the FTP server (21)
    check here
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
    Regards
    BILL
    <b>***reward with points if ity helps u!!</b>

  • How is the Fault Message Type used?

    Hi,
    I have a HTTP-SOAP scenario.I want to post a request to a HTTP Server using the SOAP receiver adapter and get the ackowledgement message from the receiver, if it was successful or not. Is this possible using the Fault Message type?
    If not how else can i capture the response in the EO mode?

    Hi Sivasakthi
    Yes you can capture soap response using SOAP fault message
    Check this link for embedded soap response
    http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
    With this you can refer to this blog as well
    Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
    Thanks
    Gaurav

  • Is it mandatory to use a Fault Message Type.

    Hi all
    I am currently doing a Soap-Proxy synchronous scenario,where by sending an employee id through webservice to SAP ECC ,employee details will be retreived from ECC as a response.
    In this scenario, is it necessary to specify the Fault Message Type in the outbound and inbound synchronous Message interfaces and do the corresponding message mapping for Fault message types.
    Asvance Thanks,
    Ram.

    Hi ram,
    It is not at all mendetary to use Fault message in ur case.Usually it depends upon requirement.If client want's to implement ...u have to use.
    generally fault messages are used wen u want to catch some exception viz. ECC server is down,Employee ID does not exist.,No record found for the given EmpID etc....ect.......
    See these to know more abt fault message type and its implementation........
    Fault message implementation.
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    How to Guide
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40574601-ec97-2910-3cba-a0fdc10f4dce
    With Integration Scenario
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/52398597-0601-0010-868a-fd95f8061d85
    How to Guide - Using Web Service
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f027dde5-e16e-2910-97a4-f231046429f2
    Presentation
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9f2ad490-0201-0010-a1bd-81d072f3c5ca
    Regards
    Biplab
    <i>***Reward with points if it helps you!!</i>

  • What is fault message type in mapping

    hi folks,
                what is the use of fault message type in message mapping . where do we use them .please spare a little time to type rather to refer to  other blogs. have a nice day

    Hi Bose
    Fault messages are used to propogate / send back the error maessage to the calling application. This is used when there is a failue and the sending system needs to know what the error was. This is more of catching Application Errors.
    Also please go through the link below to get the details for fault messages...
    http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
    fault message is a message that describes an application-specific error situation
    we have standardised fault message in XI.
    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.
    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.
    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
    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
    See the below links
    http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
    Asynchronus RFC  exception handling
    XI Alerts are not getting triggered from proxy servers
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-a258cf083bca
    /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
    Fault Message
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    You can use Fault messages when you want to handle errors at the Inbound side ie at the destination side.
    check this nice blog also
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    Fault Messages
    http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
    Usage of Fault Messages in Synchronous interfaces
    /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
    usage of fault messages in asynchronous interfaces
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    Have a look at "/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client"
    for more details  have a look on  these links
    <b>
    Fault messages -</b> /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    Also ref:
    <b>Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -</b>
    /people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
    check this out
    http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
    demo - /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1 - this is sure to help you.
    Thanks!!!
    Regards
    Abhishek Agrahari

  • Fault Message is not defined?

    Hi @,
    I am using BPM asyn sync for File2RFC scenarion and while activating the scenarion I am getting return code 99 and when i see the activation log I am getting errro description as Fault Message is not defined I have done the Fayult message mapping between Abstract Sync Message and RFC Sync message between their fault and exception types but still
    Help is urgent
    Regards

    Hi,
    you define the exception handler in the block properties. Define (via context) an exception branch for the block, where you jump into in case of errors and decide, what to do (f.e. alert or stop process).
    Regards,
    Udo

  • Fault Message Types

    Hi experts
    i have a following scenario. the scenario is SOAP to XI to ECC, and from XI to ECC RFC's are being used. i have doubt about the fault message types?
    what are fault message types and why should they be created???
    for the above required scenario does"fault message types are to be created or not" plz let me know.
    Thanx in advance

    Hi,
    >>ii have doubt about the fault message types? what are fault message types and why should they be created???
    According to help.sap.com http://help.sap.com/saphelp_nwpi71/helpdata/EN/dd/b7623c6369f454e10000000a114084/content.htm
    Fault message types are designed for application-specific errors that occur at the provider (inbound side) and that are reported back to the sender or persisted in monitoring.
    1) 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.
    2) 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 acknowledgment (see Acknowledgments).
    >>for the above required scenario does"fault message types are to be created or not" plz let me know.
    You can send the exception of RFC in Fault message type. (Provided the RFC raises an exception)
    Regards
    Suraj

Maybe you are looking for

  • Problem for Goods Receipt for Subcontracting Purchase Order

    Dear all, Presently, we are using SAP version 4.6C and we need to introduce GR for Subcontracting Purchase Order. We have developed a ABAP program to handle subcon Goods Receipt by uploading flat-files from our subcontractor. The scenario is as follo

  • Java threads. Are they running at the same time?

    Hello everybody. I am implementing a multiagent system in java and at some point in the program i need a specific function (from a specific class) to run at the same time in several "copies". Those functions are communicating with each other with som

  • Tried to update to iOS 4.3, after that IPad won't work, HELP!!

    So I hooked up my 64GB+3G t itunes and started to update my IPad, Took an hour to backup and then I came back to check on the IPad, It said there was an error updating. I was like no worry I will just stay with the 4.2.1 update. But when I ejected my

  • Windows 7 / 2008 duplicate static address when using 802.1x / MAB - ISE

    Hi all! ISE 1.1.3 Cisco 3750 switches Windows XP / 7 / 2008 clients I'm having some weird issues were if a client connects to a switchport and happens to be using a static IP address then the client warns of a duplicate address problem.  Also the cli

  • ACR & Bridge Panel artifacts

    I am posting here as it might get seen by Adobe engineers. It is difficult to find a bug report link for Bridge CS6 (unless I am completely missing something). I am running the following machine: MacBook Pro 17" (late 2011) - highest spec model that


HashFlare