cancel
Showing results for 
Search instead for 
Did you mean: 

RHMOVE30 giving timeout

Former Member
0 Kudos

Hi,

I'm working on 4.6C. For a recent development I tried report RHMOVE30 to send the task attributes from development system to quality

However the report gives a timeout even when run in background.

I tried to debug and found that form FILL_STRU_TURBO in LRHASF00 (SAPLRHAS) is filling table OBJECT_TAB with duplicate entries which spawn to an ever-growing number of records.

Not sure what could be the problem.

Regards

Manish

Accepted Solutions (0)

Answers (1)

Answers (1)

morten_nielsen
Active Contributor
0 Kudos

Hi

The Report RHMOVE30 is used for transporting your organisation structure, so it could contain a lot of data. If your going to use this report you need to make sure that you are using the correct evaluation path. The fact that you are getting duplicate entries teels me that you should try another evaluation path

What starting point / evaluation path are you using ?

If your certain, you can try to run it in background (F9).

Regards

Morten Nielsen

Former Member
0 Kudos

Hi,

Thanks for replying.

I'm using eval path TASKHIER. Moreover I tried running in backgound, gives the same result.

Infact I was incorrect in mentioned the word 'timeout' for this issue. The report consumes a lot of memory and ends in a dump. This happens in background also.

I tried running the report for my subworkflows which do not have any more nested subworkflow. It runs fine.

However when I run it for the main workflow template that has around 6 at 1st level and 2 at 2nd level the report gives error.

Regards

Manish

morten_nielsen
Active Contributor
0 Kudos

Hi

The evaluation path TASKHIER works just fine for me.

I guess your problem could be that you have an "endless loop". This can be caused if you have workflows calling them selves, recursive assignment etc.

I would suggest that you assign the agents manually.

Regards

Morten Nielsen

Former Member
0 Kudos

Thanks for the suggestion.

However

1. There are no recursive workflow calls.

2. Most of the tasks are general tasks and a couple have rules assigned to them.

What is bothering me is why it is happening; and unfortunately I'm not able to figure it out.

Thanks anyways.

Manish