Performance issue in Demand planning

[Former Member]

Hi Experts,

I want to know the performance factors included in Demand planning.

What is the effect of reduction in initialization period of planning area?

Deletion of obsolete planning version?

Is this feasible to delete the old data from live cache to improve performance and data storage requirement in APO?

Thanks & Regards,

Ankit Joshi

[Former Member]

Hello Ankit,

When you are working in Production Support, its possible to occur performance issues on Realignment.

For avoiding the issues on Realignment performance, Need to apply the required steps mentioned in the SAP Note

812045  - Realignment exceptions and performance.

Regards,

SV

[marianoc]

Hi Ankit,

There are lot of things to do and consider when we talk about performance in APO. I just wanted to recommend to read these articles:

Kind Regards,

Marinao

[satish_waghmare3]

Hello Ankit,

I suggest following -

1. Regarding MPOS - Limit number of characteristics. Be watchful of number of CVCs in MPOS. Have a process of obsolete CVC cleanup.

2. Regarding Planning Area - Limit the number of key figures in planning area where possible. Number of keyfigure in Livecache have an impact on performance. Do not burden the livecahe with additional data, you have other means to store the date like infocube etc.  Initialize the Planning area specific to keyfigure Example History keyfigure do not need to be initialized for full forecast horizion, it can be initialized only upto current month. 

3. Regarding Planning Book - Avoid too many key figures, unnecessary time horizons and inefficient macro codes/calculations. If possible reduce the characteristics to commonly used aggregation levels.

Create simple planning books for performance sake. Number of keyfigures in a PBook, and not a dataview drives the performance.

4. Regarding DP Job - Carefully select the aggregation levels and selection ID.  Do not select Check log option if not required.  Setup parallel processing profile. Combine macros as part of one activity rather than running it as a separate job.  Or use the option of collective macro when possible.

Hope this will help

Thank you

Satish Waghmare

[Former Member]

Hi Ankit

"I want to know the performance factors included in Demand planning"

Three factors determine planning area performance:

Dimension definition in the planning object structure

        Too many characteristics with in POS

Number of key figures in planning area

        Too many keyfigures

Time horizons

        Too many time buckets and planning time buckets too long than needed.

DP performance can also depend on several  other factors such as the number of characteristic combinations, amount of history data, macros etc.

Having too many macros and drill downs have adverse effect on planning books

"What is the effect of reduction in initialization period of planning area?"

Always good to have just as much needed as this will save a lot of database space and there by performance

"Deletion of obsolete planning version?"

the same, it will improve performance. We need to have a job that periodically drops past periods and add future periods, although ensuring that we are not dropping too many periods that would reduce your history availability.

"Is this feasible to delete the old data from live cache to improve performance and data storage requirement in APO?"

Yes, that's what the initialization/dropping old periods in above point meant.