Attribute value showing "None" in Excel

[former_member591592]

Hello Experts !!

I am facing one issue and need your help. our Business Requirement is to do forecasting at Month / Product/ Stocking Location.

Stocking location is an attribute of Location Product Master data. We are arriving at this value by taking reference of “Location source” MDT. For Ex, if vendor is supplying to any location than that location is an stocking location, where as if any location is supplying to another location then supplying location will be “stocking location”.

In order to map this, we created an attribute “Stocking Location” and assigned that to master data Location Product.

I created a new planning level MTHPRODLOC1, and added this new attribute “stocking location” in Location product MDT.Now I created 2 KFs one to store history and another to store forecast result. loaded the master data via data integration app .I also loaded History at location level

Now running forecast at Product /Stocking Location.

I can see forecast value in KF KF1.But for stocking location attribute I am getting “ NONE” value.

When trying to add “new planning object” for product and stocking location I am getting below error

Can anybody suggest me what could be the issue and how to resolve this.

thanks for time

Regards,

Matt

[Irmi_Kuntze · Accepted solution]

Hi Matt

to be clear: You can add another attribute to an existing level, as long as the new attribute is not a key itself.

Adding it to all levels that have PRDID and LOCID as key can be quite some work, I know.

But if you enter it just to one or two levels, other existing cross-level calculations may not work anymore.

Example: You have MTHPRODLOC and WKPRODLOC, but you enter the new attribute only to MTHPRODLOC. Than if you have a calculation for some other KF defined at KF@WKPRODLOC and you need to sum up this value to MTHPROLOC , you will get an error as the info of the new attribute is not available when you make SUM(KF@WKPRODLOC).

Same would be when you aggregate WKPRODLOCCUST to WKPRODLOC, and the attribute would only be in WKPRODLOCCUST

If you stick with having a separate planning level, here again: if you do cross-level calculations with e.g. KF2@WKPRODLOCNEW = SUM(KF1@WKPRODLOC), you would run into an error as again you cannot fill the info of the missing attribute in WKPRODLOC

Hence, you either evaluate very careful where you may have cross-level calculations, or you simply add it to all levels 🙂

[former_member591592 · Accepted solution]

Hi Irmi,

I added this new attribute to all the planning level where i had Location Product and re loaded the data. now it is running fine and as expected.

Thanks for your input.

Regards,

Matt

[Irmi_Kuntze]

Hi Matt

why did you create a new planning level and did not just add the new attribute to the existing level? Would be possible as you did not add any new keys. The way you did means double maintenance of maintenance of planning level. But that should not be root cause for the error.

You did not maintain a stocking node value for all location products, so for those you will always have a none. But that does not explain your error either …

And you don't need to create planning combination manually for a planning level, if you had a key figure attribute on that level where there is any value maintained. Examples can be found on the response side quote a lot, there are these helper attributes assigned to a MD type and maintained with a value 1. But again, no reason for your error.

To be honest, I cannot see the why. But if you try to test with just adding the new attribute to all planning level that have location and product with LOCID and PRDID as key, and create the new KF there, you should not get any error in the first place.

Irmi

[former_member591592]

Hi Irmi,

Thanks for your response.

so as per your suggestion i should add this new attribute to all the PL with Loc ID and Prd ID as key, for ex, WKPRODLOCCUST, WKPRODLOC etc?

as i have just added this new attribute to MTHPRODLOC level only and at other PL at day and week level this attribute still doesn't exist.

Regards,

Matt

[Irmi_Kuntze]

looks like an inconsistency with the MD types or MD values

Did you get any indication / warning when you activated your planning area with the new planning level? Do you have in the new planning level the location flagged as key and the stocking node attribute as non-key? Did you get any warning or error message with the loading of data? Can you share the value you loaded for the stocking node? If stocking node is a key in the planning level, you cannot have it empty.

Without the log of any warning / error, it is hard to say what went wrong, so these are only ideas

[former_member591592]

Hi Irmhild,

Thanks for your response.

I did not get any any warning message while activating PA with new PL.i copied MTHPRODLOC PL and added my new attribute Stocking location in Location product MDT( screenshot attached). i have locid and prdid as key in location and product MDT respectively.

the values i loaded in Location product master data is also attached.

Kindly let me know if you see anything which is missing in set up.

Regards,

Matt