Expand +



Optimize mass processing to avoid APO bottlenecks and improve DP performance

by The Tip Doctor

March 29, 2011

Tip Doctor, Insider Learning Network.

This tip from from SCM Expert knowledgebase article “23 Ways to Squeeze Better Performance from APO DP Processing and Reporting“ by Hayrettin Cil, and Mehmet Nizamoglu, Senior Consultant.

Performance bottlenecks in APO Demand Planning (DP) can manifest themselves in a number of ways:  Planning preparation steps such as data loads into liveCache, realignment runs, or background processes can take longer than expected. End users may experience longer refresh times for planning book data.

Proper setup and execution of the data loads into SAP Business Information Warehouse (BW) have a significant impact on performance. Data loads from liveCache into BW for reporting and backup purposes may take long hours. Such performance bottlenecks result in longer planning cycles and reduce DP's effectiveness. Since different departments use DP results to serve different performance can have ripple effects.

Good performance comes from good design. In particular, DP developers should focus on three areas to optimize DP performance: planning object structure and planning area design, planning book and data view design, and mass processing.

This tip is focused on mass processing. The most preferred and convenient way to carry out planning processes involving large data volumes is running these functions in the background using mass processing. The maj or areas that you may face potential performance problems or that are performance sensitive are:

  • Macro calculations
  • Automated forecast jobs in the background
  • Data extraction from liveCache and updating data targets (This data extraction can be for either backup purposes or extraction to BW for reporting purposes. However, as previously stated, extraction from liveCache should be limited as much as possible.)

While working with background jobs in DP, I recommend that you use the log function (set Generate log indicator in the planning job). However, you should delete log files on a regular basis because performance deteriorates as the log file size grows. Check the log file size via the table /SAPAPO/LISLOG.

For more details and tips on structuring planning objects, as well as SCM Expert articles on designing planning areas, planning books, and data views, see the SCM Group on Insider Learning Network.

An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!