When to use lookup/sum versus when to refer cells in anaplan

phuongle · 2024-03-04T15:47:46+00:00

There was an error rendering this rich post.

I find a little bit confusing on when we would use the lookup or sum function rather than refer the cells in anaplan. Can you help me to explain more about this?

I also note that lookup is for looking up non-repetitive value on the source file, while sum is for summing up repetitive value on the source file. Depending on what the purpose is, lookup or sum is used. Is my understanding correct?

Accepted answers

All comments

rob_marshall

@phuongle

Take a look at this post, it might help you.

https://community.anaplan.com/discussion/156581/what-is-the-difference-of-sum-lookup-select

Dikshant

In order to understand whether to use SUM or LOOKUP, first you should identify the source and target modules based on your requirements. Once you identify the source and target modules, check the structure of both modules.

Sum: Many to One relationship, SUM function, is used for aggregating numeric values

Lookup: One to many relationship, LOOKUP function is used to retrieve a specific value

Examples:

SUM Function

Note: Target module dimension has to be a list format line item in source module

Formula: Employee Data.Salary[SUM: Employee Data.Location]

LOOKUP Function

Note: Source module dimension has to be a list format line item in target module

Formula: Location Module.Total Expense[LOOKUP: Location]

Quick Links

Can you help?

Unanswered questions

Dimensionality - Formula Help
I have a Price module where customers are ranked based on their unit prices. I also have a Comparison module, where I want to display the names and unit prices of top-ranked customers for comparison. The model includes a Customers list. In the Comparison module, I want to write formulas to bring in the customer names and…
Can there be a duplication in Process ID's
Can there be a duplication in Process ID's
Using Polaris and Classic
Client has spoke models built in Classic and now considering building Data Hub in Polaris in order to deal with sparsity. On the surface this seem possible but likely a bad idea. Has anyone done anything similar to this? Specifically, what did you have to do to ensure that data was compatible? Any thoughts or suggestions…