Issue Bringing List-Formatted Line Items Across Modules with Different Dimensions
Hi Community,
I'm currently building a report where I need to compare Budget and Actual values. As part of the client requirements, I need to include additional attributes for each employee (Resno), such as:
- Position Title
- Grade
- Supplier
These values are list-formatted line items in the source module, which has the following dimensions:
R1 Resno(Name_and_code_of_the_employee)
Year
Version(VO_Version)
In the target module, where I want to bring this data, the dimensions are:
IDLoader Staff
(a list containing encoded employee data)Year
Version(sVBudget)
I’ve tried using both SUM
and LOOKUP
, but due to the different dimensionality and the fact that the line items are list-formatted, the formulas don’t return any values.
We also attempted to create a mapping module, but as I understand it, when dealing with list-formatted line items, both source and target modules must share the same dimensions for the transfer to work.
Has anyone faced a similar issue or found a workaround for this type of case? Any advice would be greatly appreciated!
Thanks in advance 😊
Answers
-
Hi,
A few questions …
- What relationship does R1 Resno have with IDLoader Staff? Is it a 1 to 1 relationship or n to 1?
- Are
Version(VO_Version)and
Version(sVBudget) native or dummy versions?
Thanks
1 -
Hi!Thanks for your questions. Let me clarify both points:
- Relationship between R1 Resno and IDLoader Staff:
The relationship is based on the Resno code embedded in the IDLoader, which is used as a dimension in the source module. The IDLoader has a structure like this:Q10493BU10114SOV12025
, where the first segment (Q10493
) represents the Resno code.
In my target module, Resno is the main dimension, so extracting the Resno code from the IDLoader allows me to align and pull the data easily.
This is the logic I'm using to bring the information from the source to the target—please see the screenshot for a clearer reference.
Source Module
Target module
2. About Versions (VO_Version, sVBudget, sVActual):
This is a key part of the module. I’m not using native Anaplan Versions—VO_Version is a custom list.
Within this list, I have two subsets:sVBudget
→ to store budget valuessVActual
→ to store actual values
This structure allows me to compare both budgeted and actual amounts within the same module.
Let me know if you need any more clarification!
0 - Relationship between R1 Resno and IDLoader Staff:
-
Hi,
I'm confused.
In your original post, you said your source module has the following lists:
R1 Resno(Name_and_code_of_the_employee)
Year
Version(VO_Version)
and your target module has the following lists:
IDLoader Staff
(a list containing encoded employee data)Year
Version(sVBudget)
Then in your 2nd post, the screen shots show that your source module has the following lists:
IDLoader Staff
and your target module has the following lists:
R1 Resno
Can you show the 'Applies To' of your 2 modules?
Thanks
0 -
Hi,
You're absolutely right — I apologize for the confusion in my earlier message.
To clarify:
- The source module actually has the following dimensions:
IDLoader Staff
(a list containing encoded employee data)Year
Version
(subset:sVBudget
) - It looks like this:
- The target module uses these dimensions:
R1 Resno
(Name and code of the employee)Year
Version
(VO_Version
)
It looks like this:
The idea is to map the information from the source to the target by extracting the Resno code (e.g.,
Q10493
) from theIDLoader Staff
string, which makes the relationship possible since the Resno code is embedded at the beginning of the string.Thanks again for pointing that out!
0 - The source module actually has the following dimensions:
-
Hi,
Does the target module contain 'R1 Resno' or 'R1 Personnel' in its Applies To. You said it contains 'R1 Resno', but the screen shot shows 'R1 Personnel'.
Assuming you meant to say the target module contains 'R1 Personnel', then it should be possible to extract data from the source module by using SUM, since you have 'R1 Personnel' data in the source module (i.e. CAL01 - Staff xx Details.Name).
Moving onto the Versions part, what do you want to achieve again? You mention 'sV Actual', but i see 'V0 Versions' in the target module.
Thanks
0