Skip to Content

Exception while executing ARFC2 Model

Hi Guys,

We are in the process of migrating our webdynpro java application from 7.0 to 7.5. We have migrated them successfully. Also migrated the ARFC function module to ARFC2 function modules as well.

Now while executing the function module, the RFC in the backend is raising some exception. I need to capture the exception text in webdynpro java. In previous versions it is working fine. But once migrated, I am not able to get the exception text. Instead it gives "Typed Model Execution failed. See nested exception for details."

Anything has changed in ARFC2 that we need to adapt here. It works fine in 7.0 though.

Below is the code I am using.

try{

// Model execution code here

}

catch (Exception e){

messageMgr.reportException(e.getMessage());

}

Regards,

Madhu

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • May 16 at 12:10 PM

    Hi Madhu,

    We recently faced the same issue and I hope this helps you and others.

    In order to return the exception raised rather than a generic ARFC2 exception we used the following:

    catch (ARFC2ModelExecuteException e){
        String s = e.getNestedLocalizedMessage();
        messageMgr.reportException(s.substring(s.lastIndexOf(':') + 1).trim());
    }
    

    Regards,

    Patrick.

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 26, 2017 at 05:48 PM

    Hi Madhu,

    First a quick note that I added "UI Web Dynpro Java" as a secondary tag for your question.

    Now, on to the question itself. Most likely this error (Typed model execution failed) is caused by a change in the way that your RFC Destinations from the Portal to the backend are handled with 7.5 vs 7.0. Specifically, check in NetWeaver Administrator that your "Metadata" destinations are using "Technical User" for the authentication method (with the user set to SAPJSF), and your "Model" or "normal" destinations use "Current User (Assertion Ticket)." In 7.0 you managed these as JCo Destinations from within the Portal interface (as web dynpro content), but in 7.5 they are managed as RFC Destinations in NWA.

    See Note 1929964 for more information.

    Cheers,
    Matt

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Matt,

      Thanks for the response. I have already checked the RFC destinations and correct authentication method is being used for both Metadata and Modeldata destinations.

      The issue here is, in the function module ABAPers are raising an exception deliberately saying NO_RECORDS_FOUND. Now I need to get it in front end. In 7.0, with the above code it was working fine. But in 7.5 it doesnot. Instead of getting the NO_RECORD_FOUND text it gives Typed model execution failed.

      Regards,
      Madhu

  • Jun 28, 2017 at 03:40 AM

    Hi Guys,

    Any suggestions?

    Regards,

    Madhu

    Add comment
    10|10000 characters needed characters exceeded