Example of Consistent Planning
The following planning hierarchy exists for your information structure:
You create a plan for information structure S891 or for a planning type based on information structure S891.
You specify sales organization NORTH in the initial dialog box. In the planning table, you can enter planning data at either the aggregate level (in this case, the sales organization level) or the detailed level (in this case, the material level).
You plan the following invoiced sales values for the first quarter at the sales organizational level, that is, at the aggregate level:
January 1999 |
February 1999 |
March 1999 |
Unit |
10000 |
11000 |
12000 |
USD |
You then switch to the detailed level and change the planning data for material TOASTER:
January 1999 |
February 1999 |
March 1999 |
Unit | |
Old |
2450 |
2695 |
2940 |
USD |
New |
3000 |
3500 |
4000 |
USD |
In this example, the R/3 System carries out disaggregation on the basis of the proportional factors obtained with Master data
You then switch back to the aggregate level (the sales organizational level) and see that its planning data has changed:
January 1999 |
February 1999 |
March 1999 |
Unit |
10550 |
11805 |
13060 |
USD |
The aggregate data has changed automatically to reflect the changes you made at the detailed level.
You now save your data. The following data is stored on the database:
January 1999 |
February 1999 |
March 1999 |
Unit | |
Plush carpet |
750 |
825 |
900 |
USD |
Cotton roll |
1750 |
1925 |
2100 |
USD |
Toaster |
3000 |
3500 |
4000 |
USD |
Vacuum |
|
|
|
|
Coffee table |
1000 |
1100 |
1200 |
USD |
Telephone stand |
|
|
|
|
Because the data at the aggregate level is always the sum of the data at the detailed level, you save data at the detailed level only.