So, with the Galaxy of Demand Planning: Fine Architecture and the base principles already resided in the live cache of SDN, it has become my responsibility not to stop the flow.
I had actually thought of giving some implementation part here, at least to the extent of creating Planning Object Structure (POS) and Planning Area (PA)……………but, I thought, you should understand the flow as you create them……….I mean, you should know what needs to be already there to have a complete POS and the PA.
So, in view of that and in view of me trying to make this blog easy to understand……….let’s implement the top-down approach in our learning. However, I feel it better to let you have the feel of creating a POS and so are the below details of POS.
To create the POS, you will go to the transaction /SAPAPO/MSDP_ADMIN, wherein you will see either the Planning Areas or the Planning Object Structures. Then, in case if you view the PAs, select the POS tab as below:
Then, we see the list of POSs in the screen as below:
The green status means that it is activated. The ‘red’ means it is yet to be activated.
To create a POS,
Once this is done, give the text description for this POS, and, as told Galaxy of Demand Planning: Fine Architecture and the base principles, assign some characteristics for this from left to right. Then, click the activate button on the top-left.
Now, you will see the activated POS in the POS list.
Let the top-down approach begin now:
We shall go to create the PA now. It is same as above. Select the PA in the header and you will see the list of PAs.
When you try to create the planning area, the system will come up with the below questions.
So, in the first check-box, you will give the name for your area, and the second one is your POS. The third check-box has LCA:meaning, ‘Live Cache Anchor’-this acts as a database for the data in DP (More on this in the coming articles). Note that the data of the planning area is stored in the memory called Live Cache.
The other mandatory fields for the PA are the SBP and the Unit of Measurement (UOM).
Let’s discuss the SBP later.
But what is this UOM?
………Uuuhm, ok, let me go this way. I hope you know what a PA contains: key-figures! And you know what I meant by saying key-figures: transactional data.
Now, you knew one thing for clear: Anything that can be expressed in numbers is a key-figure. If I say ‘Quantity’, then, it should be expressed in numbers……..’Weight’-this also has to be…………’Demand’ and this also has to be…….so, this way, all these type of things come under key-figures. Just like how we tagged different characteristics with the POS; in the same way will we be doing for the PA, but we tag the key-figures instead of characteristics. But that’s a different issue………..let’s discuss it later.
Let’s understand what that UOM means. So, when you think of ‘Quantity’, it can be expressed in some unit, say kg or gram or mg. So is the case with ‘weight’. But, what about price? That should be dollar or euro or pound. Now, suppose that I attaché these key-figures for a planning area I am going to create, then, what would you recommend for the UOM-which actually is given for the whole planning area and not for the individual key-figures?!
Uh……ok then, here comes the need of SNP-and you can say: the initial shadow of SNP in DP. But don’t worry about that, I am nowhere going to explain the details of SNP, and frankly, you don’t need to know now itself.
By default, when you give the UOM a unit, then, all the key-figures in the PA take up that UNIT, however, in SNP, if you go to the transaction /sapapo/mat1, you will be able to assign the unit of measurement for each key-figuredifferently……………..this is the SNP part.
So, does that mean that, if I want to have key-figures for a PA which have different units of measurement, then, I need to have those many different PAs, as far as DP is concerned?
Uh…………..yes, and logically, you can make that statement…….but because SNP is already there helping you out in that situation, please don’t state like that :-).
The same is the case w.r.t the currency field in the above list of questions for having a PA.
Going to SBP……………….
Now, as PA demands SBP, you need to first go create a SBP, for which the transaction is /sapapo/tr32.
Here, as said Galaxy of Demand Planning: Fine Architecture and the base principles, you tell the system in which buckets (Day/Week/Month……….) the planning data should be stored at the detailed level and between what periods (start andend dates). But again, there is a requirement here-the Time Stream ID, and hence to create a SBP, it is recommended to create a Time Stream ID, though it is not required. For this, you need to go the transaction /sapapo/calendar.
So, here, as you create the Time Stream ID, you should tell the same what calendar it should use…….
Here, in case if you want some calendar already defined by SAP for you, to make your life easier; then, you can choose any of the existing calendars, but what in case if none of them meet your business requirements? Then, SAP has given to you the freedom for creating your own calendar for which the transaction is SCAL.
Here, when you try to create the Factory calendar, it will ask which Holiday calendar has to be used.
But again, say, if you now try to create the Holiday Calendar first and then come to factory calendar, then, the factory calendar comes up with one more question: “What days should I treat as holidays in my holiday calendar?”
What if you don’t have a day in the standard SAP which you want to keep as holiday?
With this selected, you will get the options of how to create holidays with the following details. But rather than me explaining step-by-step everything, I would want you to explore the details.
Best of Luck!