Leave Request : RFC_ERROR_SYSTEM_FAILURE

[Former Member]

Hi All,

I am getting the errror when i am sending the leave for approval. i.e When i click on 'send' button i get the error as :

The current application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE

com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The current application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)

I have done the parameter setting properly.Also in SPRO i have configured the necessary parameters for the leave.

Please help to get the problem resolved.

Regards

Pravesh

[siddharthrajora · Accepted solution]

you should do

workflow customizing via t-code SWU3.

Select "Configure RFC Destination", click on the button "Perform

automatic workflow customizing" on the tool bar.

When you see the flag in front of "Configure RFC Destination" turn to

green, that is OK.

Could you please goto SM59, check if RFC destination

WORKFLOW_LOCAL_800 exist under "Logical destinations"?

[Former Member · Accepted solution]

Hi Siddharth,

Thanks for your quick reply.

I have checked in SM59 > Logical Connnection.

I didn't see the WORKFLOW_LOCAL_800.

Please guide me.

Regards

[Former Member · Accepted solution]

hi siddharth,

As usual you have resolve my issue.

This is how it got resolved :

i have to create the user "WF-BATCH" user (work flow user) and run the TCode : SWU3

Under 'Maintain Runtime Environment' > Configuration RFC Destination is turns green .

I have checked SM59 under Logical Connections WORKFLOW_LOCAL_xxx ((xxx stands for the three-digit number of the client) is present.

Thanks !!

Regards

Pravesh

[siddharthrajora]

thanks for letting us know

[former_member214498]

Hi

I was facing the similar issue few days back. In Portal content, assign the authorization at this particular iview level which is opening for approval.

confident it will solve your issue.

Regards

Waz

[Former Member]

hi

i have doen the configuration correctly.

The error which i suspect is in creation of RFC destination.

When i am checking the RFC destination using TCode : SWU3

i am getting the following error :

RFC Destination Does Not Exist Automatic 20.05.2009 12:01:43 306087 SAP_BASIS Configure RFC Destination

Generic standard tasks = general Automatic 20.05.2009 11:58:12 306087 SAP_BASIS Classify Generic Standard Tasks as General

RFC Destination Does Not Exist Automatic 20.05.2009 11:53:22 306087 SAP_BASIS Configure RFC Destination

RFC Destination Does Not Exist Automatic 20.05.2009 11:52:18 306087 SAP_BASIS Configure RFC Destination

Unable to read RFC destination WORKFLOW_LOCAL_309 Automatic 20.05.2009 11:52:18 306087 SAP_BASIS Schedule Background Job for Missed Deadlines

.

.

.

RFC Destination Does Not Exist Automatic 20.05.2009 11:51:48 306087 SAP_BASIS Configure RFC Destination

Help is appriciated .

Regards

Pravesh

[Former Member]

Dont panic,

DO following thing 1st.

please find the following solution .it will definitely work .

If you leave configuration is done.

There was an incorrect data in your system. To do these please follow following process.

delete this request using

PTARQ> Delete documents (RPTARQDBDEl)

Please read the report documentation before

deleting the request but it should be safe as it is

a development system.

Please delete this with the above information or delete all

the records for the approver.

After this,, there will be some incorrect workitem in approver inbox.

You need to clear that also by Tcode - SWWL.

Regards,

Vivek Jadhav

[former_member214498]

Hi

I was facing the similar issue few days back. In Portal content, assign the authorization at this particular iview level which is opening for approval.

confident it will solve your issue.

Regards

Waz

[Former Member]

Ok,

Check one thing

Log in to SAP and goto trasaction "PTARQ" select "Determine Approver" in Determine approver screen

give the pernr no ( which one ur using on Portal ) and execute ....if its showing you data then check the DATA for the approver .....if it no then you need to assign the chief possition ..

[Former Member]

Hi ,

please find the following solution .it will definitely work .

If you leave configuration is done.

There was an incorrect data in your system. To do these please follow following process.

delete this request using

PTARQ> Delete documents (RPTARQDBDEl)

Please read the report documentation before

deleting the request but it should be safe as it is

a development system.

Please delete this with the above information or delete all

the records for the approver.

After this,, there will be some incorrect workitem in approver inbox.

You need to clear that also by Tcode - SWWL.

Regards,

Vivek Jadhav

[siddharthrajora]

Check if the user has the correct authorisations ? ALso his customisation in PTARQ?

Also can you check if a dump is createdin backend as well/

[Former Member]

hi Siddharth,

Authorization is correct. In fact i have given SAP_ALL.

Customization is proper.

How do i check that dump is created in backend. ?

how this will help to resolve the issue?

Regards

[Former Member]

hi siddharth,

the following is the details when i checked the error by ST22 :

Error analysis

Short text of error message:

Unable to read RFC destination WORKFLOW_LOCAL_30

Long text of error message:

Technical information about the message:

Message class....... "SWF_RUN"

Number.............. 617

Variable 1.......... "WORKFLOW_LOCAL_309"

Variable 2.......... "RFC_READ_DESTINATION_TYPE"

Variable 3.......... "DESTINATION_NOT_EXIST"

Variable 4.......... " "

Pls help !

[Former Member]

Pravesh,

check this thread

https://forums.sdn.sap.com/click.jspa?searchID=26299849&messageID=7485322

https://forums.sdn.sap.com/click.jspa?searchID=26299849&messageID=7072010

Thanks

Bala Duvvuri

[Former Member]

hi

i have already checked this threads.

but my problem still persist.

Help appreciated.

Regards

Pravesh