SAP SOP Set Parameters for Info Structures and Key figures
Study Material Contributed by Ulhas Kavle - Senior SAP Consultant
The next step after creating the information structure would be to set the flexible planning related configuration parameters for the structure. The transaction code to set these parameters is MC7F.
Fig – SOP_2
The following are some of the important factors which are set where configuring the information structure’s planning parameters:
A) Planning Method:
In case you are using a flexible-planning-based-self-defined information structure, the next step after the creation of this information structure should be to define the planning method. There are actually 2 types of planning methods offered by SAP right now, which is consistent planning or level by level planning.
The planning method determines the method of disaggregation of data and the storage of data at various levels of planning.
In Consistent planning the data is consistently maintained between the planning level (planning hierarchy), i.e. any change in data at any one level is automatically disaggregated or aggregated to all the other levels, this defines the consistency in key figure data between the levels.
The consistent planning method uses only one information structure to enable it to keep the data consistent. And since it has only one information structure in which the data is stored, you would need to create only one planning hierarchy master data. The planning hierarchy master data would defines the actual values of the characteristics levels and the disaggregation percentages between the levels. The system uses these disaggregation percentages and calculates the proportional factors between the levels; these proportional factors are used for automatic disaggregation or aggregation.
The data is consistent planning is therefore inarguably stored at the most detailed level and passed to the higher levels consistently and automatically. Consistent planning forms one solid unit hierarchy of the characteristics combinations, i.e., any change in the key figures at any level for any of the characteristics is automatically propagated to all the levels in the structure.
Illustration for Consistent Planning
Automatic Disaggregation of the Total Sales Order Qty in Consistent Planning
Automatic Aggregation of the Total Sales Order Qty in Consistent Planning
Aggregation is carried out when the plan is opened at higher levels.
Any change in key figure data at one level is consistently reflected at all the levels, i.e. automatic aggregation and disaggregation between levels.
The Distribution channel = AA’s data is increased from 180 Units to 210 Units in Consistent Planning
Level by Level planning:
In level by level planning method, the plan is prepared for each level; the disaggregation or aggregation of key figures values from one level to the other level is triggered out manually. Therefore it would not be wrong to say that the data at each level in a planning table (information structure) can be changed without affecting data at other levels.
In level by level planning when disaggregation is done, the key figure data lying at the lower most level will get overwritten by the disaggregated data from the higher levels and vice-versa.
Plans at various levels are discrete and independent of other levels; they may not be tuned with each other till the aggregation and disaggregation is carried out.
Also it would not be wrong in saying that you would be working with one information structure whose planning method is “level by level planning method”
To have the data at the lower levels, the higher level data has to be disaggregated manually level by level (use disaggregation function in the planning table). Nevertheless one can set up automatic background jobs to execute the disaggregation function.
Illustration for Level by Level Planning
Level by Level planning data at the highest level in the planning table
Trigger Disaggregation to the Next Level - Distribution Channel Level (See below)
Trigger Disaggregation to the Next Level - Division Level (See below)
Trigger Disaggregation to the Next Level - Material Level (See below)
Any Change at a Level would remain their till Disaggregated or Aggregated is Triggered (See below)
Trigger Aggregation to the Higher Level after the Change – Sales Organization Level (See below)
Trigger Disaggregation to all Lower Level after the Change – Level by Level (See below)
B) Planning Periods:
Here you have to set the planning period that you would use in planning. Changing the type of period at a later stage is not possible. So it is recommended to include the period type very carefully.
C) Other parameters:
Other parameters like the planning plant defines the plant and its resources that will be used for rough cut planning, unit of measure, currency, factory calendar to know the days of the month available for the plan, Switching off DB update restricted to planning type key figures, ALE permitted etc. Selecting the “switching off the database” indicator would allow more than one users save the planning.
Key figures planning parameters
Fig – SOP_3
There are some planning parameters which are to be set for the key figures of the information structure as shown in the screen above. For example for the key figure KWMENG – Order quantity, you could select parameters such as:
“Allow forecast for the key figures” – if forecasting is not selected for the key figure, then forecasting is not possible for the key figure in the planning table.
“Allow time based disaggregation”, “decide type of aggregation” (average value of the total key figures value of a lower level is aggregated to the higher level or the total of key figure values of the lower level is aggregated to the higher level or no aggregation is to be carried out at all from the lower level to the higher level). It is always recommended to use total aggregation method.
An example of “Total Aggregation” can be as below, where the Sales organization is the top most level, then the distribution channel and then the division and finally the material level.
Follow the topics for SAP SOP in the sequence Mentioned Below
All the site contents are Copyright © www.sapsword.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies. The site www.sapsword.com is in no way affiliated with SAP AG. Every effort is made to ensure the content integrity.
Information used on this site is at your own risk.
The content on this site may not be reproduced or redistributed without the express written permission of
www.sapsword.com or the content authors.