Demand Planning Configuration:

Planning object structure (MPOS): The planning object structure is an APO Info Cube saved in the database of the internal BW system, and displayed in the Data Warehousing Workbench under unassigned nodes (Info Cube generated for internal use only). Planning object structures can contain default or user characteristics created in the Data Warehousing Workbench.

Planning Book:
While the majority of the demand planning process will be executed as background jobs, participants in the process will need to have a tool for interactive correction of statistical forecasts, allowing data to be exchanged with possible other users. Planning books will consist of the following items: . Characteristics . Key Figures . Data Views . Macros . Forecasting functionality . Promotional Planning functionality . Interactive graphics Each planning book can contain multiple views, where you can group key figures for detailed analyses and planning tasks: . Custom data view(s) (configurable) - Unlimited . Univariate view (SAP Delivered) . MLR view (SAP Delivered) . Composite view (SAP Delivered) . Promotional Planning view (SAP delivered) Planning books and data views represent a section of the data of a planning area. When defining a planning book and a data view, you determine the extent of this section. a) We take data views to contain only those key figures which are actually needed for the planning process. Also, we should create macros for the data view of the planning book and not for the planning area. b) The data view taken in the planning book should cover the exact period required for the relevant planning process.