Compound Function SUM & LOOKUP OEG Enablement Scenario

rohan.deo
rohan.deo
in Modeling

I am following this micro-lesson https://anaplanenablement.s3.amazonaws.com/Academy/Platform/Level_3/NMX/L3_S2_T02_NMX/story.html on compound functions. I understand the overall point that these two functions should not be used in the same line item. However, I am not understanding this specific example. DAT01 is dimensioned by stores, region, time and CAL01 is as well. So the "Original Formula" is housed in the CAL01 module? Why is a SUM required if these modules have the same dimensions? Not understanding why the LOOKUP piece is required in the "Original Formula" in that case. What is the relationship between country and region here?. Would someone be able to clarify how this example works or break it down to explain it. Thanks!

image.png

Answers

  • MarkWarren
    MarkWarren

    The SUM is summing to Country and then the LOOKUP is mapping that Country level data to Stores. Yeah, a bit odd I know, why would you want to show all Country sales per Region for every store…

  • rohan.deo
    rohan.deo

    @MarkWarren - Thanks for the response. Would it be possible to see the blueprint views of these modules in the lesson? I am recreating this on my side and it would be useful to see them.

  • MarkWarren
    MarkWarren
    image.png
    image.png
    image.png
    • 'DAT01 Sales Volumes'.Volume[SUM: 'SYS01 Country Mapping'.Store to Country Mapping]
    • Intermediate Sum[LOOKUP: 'SYS01 Country Mapping'.Store to Country Mapping]
    • 'DAT01 Sales Volumes'.Volume[SUM: 'SYS01 Country Mapping'.Store to Country Mapping, LOOKUP: 'SYS01 Country Mapping'.Store to Country Mapping]

Categories