Planning Sequence/Function times out

[Former Member]

Hello,

I have the following issue. I have a planning layout and many planning sequences/functions attached to the push buttons on the layout. The problem is that when I am trying to execute any of the planning sequences attached to the buttons (click the button), the "wheel keeps spinning" and eventually the application times out without computing anything. it works fine in Development and QA systems, but not in P. the only difference between the 3 environments is the Support Stack level. in P we are still on SPS 11 and D and QA is SPS 13.

I suppose there can be multiple reasons for why this is happening, but what should I be looking for first? Why does it time out? It does not seem to matter how many records PF is processing, because it times out with 4 records and 40K records. Any ideas or pointers to look at?

Thanks

[Former Member · Accepted solution]

Hi AG,

please try if your planning sequences run in the back-end report RSPLS_PLSEQ_EXECUTE. If you have variables you need to define a variant to start it in the back-end. You should measures the time here ...

And what kind of time out are you getting? Is it a portal time out? In this case you should consider that in you production system much more data may be read and that executing the planning sequences may take longer -> time out ...

Hope this helps ...

Matthias Nutt

SAP Consulting Switzerland

[Former Member · Accepted solution]

Hi Matthias,

I am trying to use that program on the backend to execute my PS, but I get the following error anytime I try to execute any plannig sequence - RSPLS411. Do you know what this might be?

Also, the timeout looks like is coming from web dispatcher in the portal which is now 15 minutes. However, if it is only 4 records the systems need to compute it still times out after 15 minutes, which should not take that long in the first place.

AG

[Former Member · Accepted solution]

HI AG,

to take a look at the error message use TA SE91. RSPLS is the mesage class, 411 is the message number.

The error message you are seeing is rather generic. To take a look at the details, you need to debug the execution.

Please make shure, that you are using the correct variant, if you have variables in you planning sequence.

Bye Matthias

[Former Member · Accepted solution]

I narrowed the problem down. It seems to only time out now if one of the variables contains a hierarchy node instead of an individual item.

[Former Member · Accepted solution]

hi, in that case the SPS difference seems to be important. As far as I rememeber some improvements have been done in the area of hierachy nodes. bye Matthias