Need help to avoid hardcoding SELECT

Hello,

Need some guidance on how I can avoid hardcoding.

Let say I have a module A that applies to Country and Product (Coke and Pepsi) and line item as sales

I have another module B that applies to country and I want to create two line items Sales - Coke and Sales - Pepsi which I then want to compare variance.

This is the formula I am currently using

Sales - Coke = A.Sales[Select: Product.Coke]

Sales - Pepsi = A.Sales[Select: Product.Pepsi]

How can I avoid the hardcoding for SELECT? I tried creating a constant module and creating two lines item type Product. Using them in the SELECT like below gives me error

Sales - Coke - A.Sales[SELECT: Constants.Product1]

The name Constant.Product1 used in the SELECT clause is not recognized as a list member or version in the model

Any suggestions?

Accepted answers

rob_marshall

@sagarkpr

Instead of using SELECT, try using a lookup.

Sales - Coke - A.Sales[LOOKUP: Constants.Product1]

With that said, if you are going to hardcode both Coke and Pepsi as line items, why not have that list in defined in the module so your only line item is Sales?

Vamsi_Kaki

Hello @sagarkpr , If you would like to provide users to compare sales of selected products then,

Create a filter module (FL1) dimensioned by Users and Line items(Product1, Product2). These line items are product list formatted.
Then create Target module (TR1) dimensioned by Country, Users and Line items(Product1, Product2)
Now, reference sales from source module (dimensioned by Country n Products) by looking up Product1, Product2 line items from Filter module.

Source Module:

Filter Module:

Target Module:

Thanks,

Vamsi

All comments

rob_marshall

@sagarkpr

Instead of using SELECT, try using a lookup.

Sales - Coke - A.Sales[LOOKUP: Constants.Product1]

With that said, if you are going to hardcode both Coke and Pepsi as line items, why not have that list in defined in the module so your only line item is Sales?

sagarkpr

Thanks for the suggestion for Lookup, it worked. When I tried it before, it was giving me error. Must be typo.

As for not using Product as dimension in Module B. There are about 10 products and at any given time, I would like to compare two products.

rob_marshall

@sagarkpr

Then if you are comparing the two products and those two products can be dynamic (user selects it), then create a module (dimensionalized by Users - which could be expensive depending on the number of users defined in the model), with two line items: Product A and Product B (theses should be list formatted)…The you can use these for your lookup. Also, take a look at this document, it should help. While it is based on Native Versions, it can still by applied to your situation

https://community.anaplan.com/discussion/98336/variance-analysis-with-native-versions-made-easy

Vamsi_Kaki

Hello @sagarkpr , If you would like to provide users to compare sales of selected products then,

Create a filter module (FL1) dimensioned by Users and Line items(Product1, Product2). These line items are product list formatted.
Then create Target module (TR1) dimensioned by Country, Users and Line items(Product1, Product2)
Now, reference sales from source module (dimensioned by Country n Products) by looking up Product1, Product2 line items from Filter module.

Source Module:

Filter Module:

Target Module:

Thanks,

Vamsi

Quick Links

Can you help?

Unanswered questions

how to count how many times an action has run?
I want to create a line item which will increment by 1 every time an action is run manually. This action is an import which doesn't involve any file upload to anaplan. The module where I want this line item has users list & SKU list dimension. No time. So basically, I want to track how many users have selected an SKU and…
Missing Column Headers in Anaplan Export When Using API
Hi Community, I’m encountering an issue where an export created in Anaplan is missing column headers when retrieved via the API. However, when I manually run the same export from the Actions tab, the downloaded file includes the headers. Has anyone experienced this behavior before? I’d appreciate any insights into the root…
Importing from Data Hub: Incorrect or Missing Mappings in Target Model
When importing data from a Data Hub to another model, I'm seeing values in the target model that don't exist in the source. For example, seller assignments are being tagged with subregions that aren't present in the source data - some assignments are missing expected tags, while others are mapped to seemingly random…