on 09-12-2017 1:52 PM
Dear experts,
I created a Key Figure (say NOAGGREGATION@PERPRODLOC) which plays an important role on its lowest possible aggregation level (DAYPRODLOC), but will always show more or less "wrong" results when aggregated in one of the "standard" ways. (through both higher time buckets or other product/location characteristics).
In order to not confuse planners who might want to look at a higher aggregation level (e.g. month instead of day), my requirement looks something like this:
If request level equals the base planning level (DAYPRODLOC), show the corresponding stored values at this planning level- otherwise show NULL.
While playing around with the request calculation (also including intermediate planning levels similar to a last period aggregation), I was not able to achieve the desired result.
Anybody here with some ideas or who has experienced a requirement like this before?
Best regards
Holger
Hi Holger,
Can you confirm technical weeks involved in your planning levels?
Best Regards,
Lingaiah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
12 | |
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.