ICP dimension conflict with HFM

Question

Hi Guys,
I need your help for the following, I am using FDM 11.1.1.3 together with HFM 11.1.1.3.50. Now, in HFM the ICP dimension has been set up as follows (for which I have been told this is not best practice):
Parent: [ICP TOP]
Child1: [ICP NONE]
Child2: [ICP entities]
Children: 001 to 940
Apparently, FDM assumes that [ICP NONE] should be the parent. At least, I cannot export the ICP values for the entities like they should. Currently there is a workaround with logic accounts and a script in place:
-The script adds 'ICP.' in front of an account when it is carrying ICP.
-ICP mapping says export all to [ICP NONE] except when the account starts with L-
-Logic accounts have been created to duplicate each 'ICP.' account.
-The values of these L- logic accounts are then exported to the children of [ICP ENTITIES].
Needles to say this requires quite some maintenance since for each account that carries ICP values in a flat file, a new logic account needs to be created and mapped.
Any solution or suggestion how I can modify FDM and formulate the set up of the HFM ICP dimension? Or how I could minimize the maintenance? You would be of great help!
Kind Regards,
JDeM

Answer 1

Tnx for your reply Tony. You are correct and I am sorry I stated it wrong, what I meant is that because of the aggregatedweight set to 0, [ICP TOP] = [ICP NONE]. Sorry to confuse you, it is the first time I use FDM so need to familiarize myself with all this stuff :)
Just to inform you about the current mapping table:
-Current amount of valid ICPs = 80.
-All the others (919 in total) are mapped to [ICP NONE] in the explicit map.
-Next there is a like mapping:
ALL     All     #SCRIPT     LIKE * "IF varValues(14)= ""NET_INCOME"" Then Result=""[ICP None]"" Else IF (left(varValues(13),1)= ""I"" OR left(varValues(13),1)= ""T"") Then
Result=""[ICP None]"" Else Result= varValues(17) End IF End IF "
(The "'I"" refers to all these ICP. accounts.)
(The "'T"" refers to logic accounts used to cumulate some values)
(note that source ICP = Target ICP, so that is quite nice)
So if I understand you correctly Tony, if I would create 80 complex logic accounts like this (which only have to be extended when another location is added in HFM, which is rare):
i.e. ICP_ENTITY with Complex Criteria:
CALCSTMTACCOUNT--DIMENSION--CRITERIATYPE--CRITERIAVALUE--GROUPBY--GROUPLEVEL
ICP_ENTITY--------------ACCOUNT----LIKE-----------------*----------------------(blank)------0     
ICP_ENTITY--------------ICP-------------LIKE-----------------*----------------------L-006--------5
CALCSTMTACCOUNT--DIMENSION--CRITERIATYPE--CRITERIAVALUE--GROUPBY--GROUPLEVEL
ICP_ENTITY--------------ACCOUNT----LIKE-----------------*----------------------(blank)------0     
ICP_ENTITY--------------ICP-------------LIKE-----------------*----------------------L-007--------5
etc. for all 80 relevant ICPs. Then the amounts would be exported twice to the account? Once to [ICP NONE] and thanks to the logic, also once to the ICP mentioned in the flatfile (i.e. 006).
SH, I understand your point, however that kind of maintenance we already covered. However, each month we still need to create a new logic for each account that had never carried an ICP in the past. We cannot do this upfront since there are thousands of accounts and many different logic groups and parent mappings.
Edited by: JDeM on 6-apr-2011 6:21