AasKF - Alternate Configuration Question

[willsuus]

Hello,

We are trying to change our existing AasKFs to use the alternate configuration as the load is over 1 million planning points and therefore we can not yet normalize our system.

In the pdf file that outlines the steps, it references creating a new plannning level, DAYZID. If the lowest time level we use is technical week, do we not need to create DAYZID? Or, for that matter, DAYplanninglevelZID, DAYplanninglevel?

The documentation is a bit confusing so any helpful hints would be greatly appreciated.

Thank you,

Susan

[willsuus]

To clarify, we do have Days in our Time Profile but the lowest planning level we use is technical week.

[Irmi_Kuntze]

Hi Susan

admittingly, the documentation is not too easy to understand.

If you need technical week level only, then I suggest you adjust the configuration to technical weeks.

What I have done in my configuration is that I created the MD type ZSMDT with one attribute ZAAKFDAY and one second attribute ZAAKFWK (instead of only one ZAAKF), both of type decimal, and one common entry for the identifier ZID only.

Then there are two attributes as key figures as well, with ZAAKFDAY on base planning level DAYZID and ZAAKFWK on WKZID. Rest accordingly.

However, depending on the use case why you have your AAKF in the first place, there my be other solutions. What is the reason why you use an AAKF? Is it to initialize a planning level, or to make an attribute value visible across all periods, or because it was created as such in the template planning area, or...?

Yours

Irmi

[willsuus]

We have Safety Stock defined as a AasKF and it loads > 1 million points so we need to change the way it is loaded since we can not normalize our system with a load that large. So, it is the same value loading but we need it across all time periods (by technical week). The same is true for minimum lot size. If you have an alternate solution, I would certainly be open to exploring it.

[willsuus]

Once the key figure is changed to PRODLOC, for example, do you still have to do all the transformations with ZID?

[neeraj_deshkar1]

Hi Susan,

You can create another of let's say KF2.

So KF2@wkprodloc = KF1@prodloc

Specify some other kf e.g. independentdemand as additional input.

-- Neeraj

[willsuus]

Thank you, Neeraj.

In general, I guess the only issue with having to load some data in this manner rather than as an AasKF is that you don't have historical values. So, if safety stock was at a given level last month and was changed this month, you would not be able to see this change.

[neeraj_deshkar1]

Hi Susan,

We faced this issue. The solution we applied was to create a time independent planning level and assign to attribute as KF. e.g. use planning level as PRODLOC instead of WKPRODLOC. This resolves issue of 1 million records.

Hope this clarifies the issue.

-- Neeraj

[willsuus]

Thank you, Neeraj, for your response. So, if I assigned the Key Figure Safety Stock to PRODLOC instead of WKPRODLOC, it would only load one point? Then how would I get it to be available for all technical weeks? (Sorry if this is a simple question, but I just need to understand exactly what needs to be done).