Make the Most of APO

DP Reporting in BW

  • by Hayrettin Cil, Senior Consultant, Turquoise Consulting
  • August 1, 2004
The ability to produce fast, accurate APO Demand Planning (DP) reports requires close collaboration between the APO and BW teams. You want to optimize the data flow between DP and BW, and the advice and best practices presented here will help you achieve this goal.
Key Concept
Demand Planning (DP) is the tool used within the SAP SCM architecture for advanced planning and forecasting. The outcome of DP is plan/forecast information, which is stored in APO's liveCache during runtime. To effectively report demand forecast and merge this information with actual data for forecast, accuracy analysis in BW is central for businesses to effectively manage their DP processes and improve their sales and operations planning processes.

Optimizing your APO Demand Planning (DP) reporting and work processes is based on the dynamics of data flow from APO DP into its reporting engine, SAP Business Information Warehouse (BW). By explaining the relationship between APO and BW, I'll show demand planners and managers, sales managers, BW analysts, and BW and APO developers how to create useful, comprehensive reports in the BW environment. In addition, I will provide tips on how the APO and BW teams can work together efficiently. The collaboration between APO and BW teams ensures maximum efficiency of the systems and should lead to effective reports for the end-user community.

The BW team must consider design and development factors of the BW architecture when introducing DP data. Keep in mind the following data-related factors:

  • Data volume and historic information storage

  • Load management

  • Transformation requirements, data realignments, and data manipulations in DP and its implications

  • Time stamping and version management

Key reporting considerations include:

  • Key performance indicators (KPIs)

  • Reporting requirements

  • Frequency

The previous points as well as the BW and APO installation scenario determine the BW architecture. Figure 1 shows a recommended BW architecture. For instance, it is a good idea to decouple the most current DP results from previous DP results by storing the most current results and previous results in separate InfoProviders. The majority of DP reports are executed using the latest DP results and keeping the dataset small by using a separate InfoProvider expedites the process. Additionally, use MultiProviders to generate all the reports for actual, plan, and forecast/plan versus plan comparison-type reporting. This approach reduces development and maintenance efforts for querying.

Hayrettin Cil

Hayrettin Cil is a senior SAP Business Intelligence Consultant with extensive experience in Strategic Enterprise Management (SEM), Business Information Warehouse (BW), Advanced Planning and Optimization (APO), and SAP R/3 Sales and Distribution, Financials, and logistics. He has been a speaker at various BW and SCM conferences, and has worked in the consumer goods, pharmaceutical, retail, chemical, oil and gas, public sector, and high tech industries. Hayrettin has a bachelor of science degree in industrial engineering and operations research and a master of science degree in financial management.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.