Compound Master data attribute to filter key figure data

[former_member762558]

Hello Experts,

I have key figure "KF1"@Week-Product-Customer-Location level & Compound MDT (Product Group -Customer Region) have the attribute "Flag"

Note: Product Group(Key) & Cust Region (Key) in compound MDT & "Flag" is attribute of the compound MDT,

Product Group attribute of Product MDT & Cust Region attribute of Customer MDT

Based on the "Flag" attribute data we need to apply filter for key figure "KF1" ? As "Flag" attribute is not part of the Planning level Week-Product-Customer-Location, we are not able to filter the data for key figure "KF1".

Note:- We already used the virtual master data option but this will have the performance impact & maintaining "flag" at Product-Customer level will be huge number of data set.

Let me know your suggestion

[Irmi_Kuntze · Accepted solution]

ok, got it, will not work because there is no real link between the objects. I would work with virtual MD types, as that is exactly the use case for using them. And as in any case you need to provide some extra links that need to be reviewed, in regards to performance you just cannot change it

(except you would work with the flag on detailed level, or have some additional dummy attribute assigned to both product family and customer region that is then assigned as key field to the planning area, with all consequences on additional key fields...)

But you can make it least worse with working with e.g. integer attributes using values 1 and 0

Check the model config guide on help for virtual MD types. But we aware that you should assign the attributes you want to filter on should be assigned not from the virtual MD type as that will lead to errors when working with MD specific versions

[former_member762558 · Accepted solution]

Thanks for the updates, Yes we have build the virtual MD type to drill down the Time series analysis results from different level to lowest level (Product-Customer-Location) due to some performance impact we recommended not use the virtual master data.

Let me check the different configuration approach

[Irmi_Kuntze]

you said your MD type is compound, so you have a single MD type Product group and one Customer Region which you then compound ? And you have additionally assigned the Product group to MD type Product and Customer Region to MD type Customer?

So the product group and the customer region are assigned to the planning area via the single MD types Product and Customer or from Product group and Customer Group?

I am not understanding the full picture here

[former_member762558]

First, Product group and the customer region are assigned to the planning area via the single MD types Product and Customer.

Requirement is Planner wants to maintain "FLAG" (Pre-define some values) based on this "FLAG" value we need to run the forecasting jobs, This "FLAG" will be maintained at higher level Product Group & Cust Region. as they don't want to maintain at Product -Customer level due to huge data set.

To meet this we have created Simple MD type Product group and Customer Region then compound MDT (Product Group & Cust Region) with "FLAG" attribute also tried with Simple MD type (Product group(key) and Customer Region(key) & "FLAG" attribute both the approach will not help in reading key figure data (History(KF1)@ Week-Product-Customer-Location level)

Both approach we are not able to assign the "FLAG" attribute to planning level Week-Product-Customer-Location

[Irmi_Kuntze]

I do not understand why you cannot assign the flag. You have in the planning level as root the PRDID and the CUSTID and LOCID. ProductGroup is attribute of MD type Product and CustRegion is attribute of MD type Customer, right? Then you should be able to assign the attribute FLAG as well.

I have not tried that approach yet, if it is really only for filtering maybe virtual MD is easier. What other reasons do you have for the MD type Product Group -Customer Region as compound?

[former_member762558]

Yes Correct, Product Group attribute of Product MDT & Cust Region is attribute of Customer MDT & "FLAG" is attribute of compound MDT (Product Group & Cust Region), As per the configuration we are not able to assign "FLAG" attribute to Planning level WK-Product-Customer-Location level.(i have validated this config its not working )

Yes by virtual master data i'm able to achieve(to bring the "FLAG" attribute data to Product Customer) but its having performance impact

Objective is to set the "FLAG" at Product Group -Customer Region (to identify the combinations) create Planning filter based on the "FLAG" attribute data & run forecasting jobs accordingly

[Irmi_Kuntze]

Have you tried to assign the attribute FLAG to the planning level (as non-root)?

You can only to filter by something if it is assigned to the planning level, there is no workaround.

And it should be possible, as the roots of the MD type should be assigned to the planning level already.

[former_member762558]

Hi Irmhild,

We are not able to assign "FLAG" attribute to planning level, as Product Group & Cust Region are non-root attribute in the planning level (Week-Product-Customer-Location)

Based on this "FLAG" attribute data we not only apply filter also we need to run the different forecasting jobs (History(KF1)@ Week-Product-Customer-Location level)