Workaround for HFM Drill-Through when using custom dimensions ( 4) in FDM

Question

Hi all,
we have the following scenario:
- Target Custom 3 is defined as a combination of Target Product and Target Cost Center
- Target Product needs to be obtained by mapping field "PRODUCT" in the source file
- Target Cost Center needs to be obtained by mapping field "CC" in the source file
So,
One approach would be to enable Custom5 and Custom 6 dimensions in FDM, and configure sequence so these two dims are mapped before custom 3 which has a conditional map to get
values from target c4 and c5 (using varvalues...)
The issue here is that drill-through does not work as the sql query for the intersection is looking for UD5x and UD6X as NULL, N, or [NONE], and these two columns have a value as they were mapped.
Trying to solve this issue, we configured C5 and C6 as lookup dimensions so we could create the mapping tables for them although in order to import data from source file fields we used attr2 and attr3. Besides UD5 and UD6, as expected, were not displayed in the Import and Validate/Export grids
Then the idea was to update the work table with attr2->ud5 and attr3->ud6 in a event script (importaction or befprocmap..) so ud5 and ud6 are mapped.
The problem is that we noticed that ud5 and ud6 are not updated from attributes. It seems that as they are configured as lookup dims, values may be mapped but not copied from work table to tdataseg.
If this would work, then after custom3 is mapped we could set ud5x and ud6x to [none] in order the drill-through query to work.
Having all in custom 3 dim and use mappings on combinations is not desired by the customer as they want to keep product and cc mappings separately.
I was thinking to use a dummy location for product and cost center mappings and then emulate mappings using SQL but would like to avoid this.
Any other suggestion?
Thanks!

Answer 1

The criteria for mapping C3 is:
- If Plan = 6 Then Target C3 = SUBACCOUNT
- If Plan <> 6 AND Account IN range [70000,70999] Then Target C3 = Target CC
- If Plan <> 6 AND Account NOT IN range [70000,70999] Then Target C3 = Target CC_Target Product
Fields in the file
- PLAN
- ACCOUNT
- SUBACCOUNT
- Source CC
- Source Product
So current solution actually is to put that logic in the import format so:
- If Plan = 6 Then Source C3 = SUBACCOUNT
- If Plan <> 6 AND Account IN range [70000,70999] Then Source C3 = "RULE2"
- If Plan <> 6 AND Account NOT IN range [70000,70999] Then Source C3 = "RULE3"
In the mapping of C3, we managed a simple script mapping checking the source C3
If source c3 = RULE 2 -> Target C3 = Target CC
If source C3 = RULE 3 -> Target C3 = Target CC_Target Product
Else Target C3 = source C3 (which is SUBACCOUNT)
C5 (Cost Center) and C6 (Product) are mapped before C3.
In order to make Drill-Through working, we save UD5X and UD6X in ATTR2, ATTR3 so the user can see it, and we set then UD5X and UD6X to [None] so the Drill_Through SQL Query returns the values from FDM. If after loading the user goes to validate step, he will see [None] in C5 and C6 but actually this does not really matter as C3 has already been mapped and is the value to be loaded. If the want to review target product or target cc then they drill down to attribute information.
regards