Skip to Content

​Statistical Forecast Run Time

In APO DP, we have run our statistical forecast at the aggregation level of Location_Material until now. The planning objects for each job were ~3000 and the job run time was ~300 seconds. Now we have a requirement to run the stat at Location_Material_Customer_Country Level increasing the number of planning objects to ~30000 and the run time to ~40000 seconds. Can someone please advise why such a drastic increase in the job run time and if there is a way to reduce it? We have tried running the job by splitting the selections, still do not see any major improvement in the run time.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • May 11, 2018 at 08:29 AM

    Hi Manjunath,

    If you have added huge number of count defiantly run time can increase but 40000 seconds, its seriously very huge. Check whether resources are fully available when you triggered the stat forecast by using T code - RSBATCH. In SM37 you can check any wait time. if yes contact to your basis team to add more hardware resource. (Please perform test 3-4 times, may be on that particulate day some unknown system issue)

    You can try below options -

    1. Use parallel processing profile based on availability of WIP resources.

    2. Delete Obsolete CVCs

    3. Assign correct aggregation level

    4. Check with basis team about hardware compatibility.

    Please also refer



    Add comment
    10|10000 characters needed characters exceeded