ARFC2ModelExecuteException: Typed model execution failed; see nested exception for details

[Former Member]

hi all,

my goal is to import and execute the rfc functional modules from sap back-end system. so below are steps configured:

1. created a DC (local) project > imported an rfc from back-end system using the below destinations > import was successfull

a. WD_MODELDATA_DEST

b. WD_RFC_METADATA_DEST

the above destinations were created in nwa > destinations > rfc destinations by basis!

2. mapped the model context with component controller & to view contexts

3. in component controller excecuteBAPI() method i've written below code:

Z_SYSTEM_ALERTS usModel = new Z_SYSTEM_ALERTS();

Z_System_Alerts_Input input = null;   

try

{

    input = new Z_System_Alerts_Input(usModel);

        input.setSystemID("234567");

        input.setPeriod(100);

        wdContext.nodeZ_System_Alerts_Input().bind(input);

        wdContext.currentZ_System_Alerts_InputElement().modelObject().execute();

//        wdContext.nodeOutput().invalidate();

} catch(ARFC2ModelExecuteException e){

    msgMgr.reportException( e.getLocalizedMessage());

    msgMgr.reportException(e.getStackTraceString());

}

4. in view init() i called below line:

wdThis.wdGetZSACompController().executeBAPI();

The program runs, but throws the below exception:

ARFC2ModelExecuteException: Typed model execution failed; see nested exception for details

i've tried to chk in sdn, but no useful:

- are there any missing dependencies like dc, jars, libraries ?

- is it important to import this HM-WDUIDMKTCNT sc?

- any code change required?

Any hint\help would be great to resolve this issue!

-Tnx,JB

[junwu · Accepted solution]

use wizard to generate all the code for the rfc call, don't write it manually.

[Former Member · Accepted solution]

thanks jun, i've first tried using service controller to generate code - result same error. but i found one thing wn tested in sandbox portal and it works as expected, no error, pulls all data too ... what i've created in sandbox is both the RFC destinations logon data as technical user only. but in development model data is using logon tickets..! not sure if this causing the error, waiting for basis to make this change and i deploy and see!

any inputs in using logon tickets for model destination please?? which one to use?

[Former Member · Accepted solution]

both the RFCs should be configured as technical user, this resolved the error specified in the first thread.

thanks,jb

[junwu · Accepted solution]

i think it is quite normal for model data destination using logon ticket. for the meta data destination, we use technical user.