Planning with SAP Controlling is very much integral part of this ERP software and here we are going to deal in detail about this.
- Planning quantities, prices, and revenue at the product / customer level is required
- Planning at the product group level is required, with systematic distribution of values to the product level
- Mass changes to plan values are required, for analyzing different business scenarios
- Transferring CO-PA plan data to Sales and Operations Planning is required, to aid production scheduling
Communicating the Budgets
Overview of Planning Framework
Taking into account a typical sales and profit planning process, a professional planning tool has to:
- Support the individual planning tasks by guiding the user to those planning levels he/she needs to plan. For example, a key account manager needs to plan on the key customer, sales organization and product level.Support the individual planners by providing personalized access to the desired plan data, using planning packages.
- Provide a set of relevant planning functions, such as valuations and simulations, in order to apply the desired planning packages by using planning methods and parameters.
Elements in Planning
It is possible to plan on many different levels in CO-PA during a planning process. For example, it's possible to plan on the product group level, or the product level, or the customer/product level, or maybe just the customer level. In fact, it is possible to plan on any profitability segment in CO-PA. By design, the system ensures that the data remains consistent across all levels throughout the planning process, meaning that subtotals will always roll up to totals, or values from different levels can always be reconciled, even if changes are being made on different levels during the process. Example: Planned quantities are first entered at the customer/product level, for two customers and three products. Then, by definition, the totals by product will coincide with the customer/product details. If additions are then made at the product level, then the additions will display at the customer/product leve l with an unassigned customer.
Derivation occurs automatically behind the scenes when planning data is saved. Since this is true, values planned under one or more characteristic values might automatically be summarized under other characteristics as well.Example: If the characteristics product group has been added to an operating concern and values are planned at the product level, then values will automatically roll up under the appropriate product groups, even though the product group was not directly specified when entering the plan data. Again,this rollup happens automatically every place where derivation occurs.