Sap Apo DP Nutsell
Sap Apo DP Nutsell
Sap Apo DP Nutsell
The demand planning process describes each activity in the Demand Planning (DP) cycle. In general, it can be assumed that the
order of the processes presented here is the order in which should proceed through the DP cycle. However, since DP is represented
as a cycle, not a linear path, business may decide to repeat certain activities or to proceed in a different order.
Why Demand Planning : Demand planning is the most crucial aspect of any organization, be it the services or the
manufacturing sector. It is always demand planning or sales forecasting. Deman Planning is used or rather responsible for
estimating demands for the manufactured goods and work towards activities like supply of raw materials, production capacity, and
Master Data : Data that is created centrally and it is valid for all applications. It remains constant over the time but we
need to update it on regular basis. For Example: Vendor is a type of master data that is used for creating purchase orders
or contracts. Likewise we have material master data, customer master data, vendor master data, pricing/conditions
master data, warehouse management master data (storage bin master data) etc.
In terms of APO:
Master Data :Master Data for APO is characteristics or characteristics value combinations.
2)
Transactional Data : Data that is associated with processing of business transaction is Transactional data.
In terms of APO it is generally the key figures.
3)
Planning Area: Planning area in APO are the central data structure for demand planning and supply network planning.
The planning area specifies the following:
a)
b)
c)
d)
e)
4)
Planning Book: Planning book defines the context the layout of the interactive planning screen. They are used in DP &
SNP. A planning book is based on a planning area.
5)
MPOS(Master Planning Object structure) : A master planning object structure contains plannable characteristics for
one or more planning areas. In short it is generally where the CVCs(characteristics value combinations) are stored. It is
important to mention that you cannot create a Planning Area without MPOS. Its actually stored in the BI
environment technically.
6)
CVC( Characteristics Value Combinations) : A characteristic value combination is a record with values assigned to the
characteristics of the MPOS. A characteristic value combination is the combination of characteristic values with which we
want to plan. It is sometimes referred to as a characteristic combination. We can only plan data if you have defined such a
combination. Characteristic value combinations are planned for MPOS. The combinations are then valid for all planning
areas based on this planning object structure.
7)
Keyfigures: Contains data that is represented as a numerical valueeither a quantity or a monetary value. Examples of
key figures used in Demand Planning are planned demand and actual sales history. Examples of key figures used in
Supply Network Planning are production receipts and distribution receipts .
Now we will configure a simple Demand Planning scenario with configuration steps and screen shots.
We will start by taking an example with a Pen company. The Pen by itself is a Finished Product and then the nature of the
Pen (Product Category) like Ball Point Pen, or Ink Pen and again it is further subdivided into Gel or Plain and if it is Ink Pen, then it
Is subdivided into Chinese or Plain, etc etc( Product Hierarchy).
So if we look at the above example Product, Product Category, Product Hierarchy all form the Characteristics.
The number of Pens to be produced and the number of parts required to produce Pen all form the key figures.
(Eg: 500 Pens to be manufactured in a Plant A, the 500 forms, the key figures.)
Select the Planning Object structure Folder highlighted and do a right click.
It will ask to create a Planning object structure that is MPOS.
Enter the name here for the MPOS to be created. Once we provide a name it will take us to the following screen.
Here we have given the name as ZZCGTR, and we have not actually activated the MPOS as it is a client system.
Since its not active its showing the status as RED, else for an active MPOS, it will be green.
Now go to the Key figure tab to see the available key figures.
In real time it is always advisable to keep the advisable to keep the Additional Field 1-5 as it is. In future if we want to add
any additional key figure to the planning area we can simply modify these buffer fields.
For practice purpose we can select and rename to our new Planning Area: ZZ_SPLAR.
ZZ_SDEPDM Dependent Demand.
ZZV_TOTDM
Total Demand
ZZ_SLHIST
Sales History
To create the Planning Object structures we first need to create the info objects in BW/BI environment
Select Info provider as highlighted and then right click on the top as highlighted in yellow. It will prompt for Create
InfoArea.
Here since we are working on a client system, we are not authorized to create an InfoArea.
Once you create it, it will create a transport object.
Here onwards we will see the snap shot from a different system not associated with the client.
10
So here we need to create 2 info object catalogues, one for characteristics and other for key figures.
11
12
13
14
15
And enter the key figures discussed above. We discussed three key figures , but for practice purpose we can give more
than that. In the subsequent snapshots, we will have more than 3 key figures.
16
17
It is now active as shown in green. Similarly create the same for other key figure.
Important note.: Key figure can be added here at any point of time , but it should be avoided to change in the MPOS.
Once the BW part is complete , our next step is to create the MPOS.
As stated above Go to /SAPAPO/MSDP_ADMIN and follow the steps of creating MPOS.
Right click on the Folder
18
In the next screen enter the long text and also select the planning object structure.
Once all the object structures are activated. This in turn will activate an infocube in the same name in BW.
19
20
21
22
23
Please note in the locking logic tab : Unlock the deactivate , the Activate Live Cache Lock.
24
25
26
27
28
This is nothing but the transaction code /n/SAPAPO/MC62 by which we can create the CVCs.
29
30
31
32
33
34
35
36
37
38
39
40
41
42
We need to select all the key figures from the Planning object and Characteristics from the Planning Area.
43
44
45
46
47
48
The next step is to select a model for the master profile to do the forecast.
Here we choose univariate forecaste profile:
49
50
51
52
53