Problem in Validation of ICP dimension

Question

Hi,
We have a problem in validating ICP members in FDQM.
We have few accounts for which ICP value needs to be present.
In our existing mapping in FDQM,we have an explicit map,which maps source flex to ICP account.We have a default map which maps flex that do not have ICP to [ICP None].
The problem now, is with the existing mapping,if the acount is an ICP account and if it is not included in explicit mapping,it is getting mapped to default [ICP None].
Since we are not getting any kickouts for ICP accounts, it is giving us problem in performing eliminations in HFM.
Could any one suggest any work around where,when any ICP account is not maaped in FDQM,it should give a kickout rather than mapping to [ICP None].
Appreciate your help.
Thanks

Answer 1

There are some partial truths to all of the above....the most accurate being that if ICP None as an acceptable member for Accounts flagged as ICP then you will have problems because it is a valid intersection.
But there are bigger things to think about. What values come into the icp dimension? Is there always a value being passed through or is that value sometimes blank?
If there is always a source value then you do not have to use Explict types of mappings. All you have to do is make sure that your *-to-[ICP None] mapping is ALWAYS the last mapping entry in the Like type. Think of it as a catch-all. You just have to map your source-to-target values appropriately.
If the values coming in are blank then you can still use the above procedures. If you do not use a *-to-[ICP None] mapping and a value comes in as blank then FDM will automatically place [ICP None] in the extract field....it does not map it to ICP None though!!!!!
Are your source values the same as those in HFM? These are things to think about when mapping.
Quick note...if a value comes in blank and you try to drill back then you may end up with a false "Show Conversion Rules" view. For example, you have two rows imported with every dimension being the exact same EXCEPT the ICP dimension, where one has a value and the other is blank then you will end up seeing the value that is not blank when you select the "Show Conversion Rules" option. To remedy this I've created an Import Format script for the ICP dimension and check the value coming in...if it is blank then I change the value to "Blank" and map "Blank" to [ICP None]". This allows me to use the Drill-down/Drill-back features correctly.
Mappings are very simple no matter what dimension but yes, ICP is the trickiest because ICP None can be a valid intersection.
Lastly, you could have you very last mapping as a *-to#Script....or a Conditional Mapping where your scripting is checking is as such....(See conditional maps in the admin guide for further info)
'varValues(14) is the Target Account
'varValues(17) is the source ICP value
If varValues(17) = "" Then *'1*
Select Case varValues(14) *'2*
Case +1stHfMAccount that is ICP, etc+
Result = "BAD ICP" *'3*
Case Else
Result = "[ICP None]" *'4*
End Select
Else
Result = "[ICP None]"
End If
1 - If the icp value is blank then check the list of all HFM Accounts that should have an IC Partner. You have to get the list of all accounts flagged as ICP from HFM and continue to update this mapping accordingly.
2 - Check to see what the Target account is
3 - If the source account is mapped to an ICP account in HFM and the value is blank then mapped the ICP value to "*BAD ICP*" because *BAD ICP* is not an account in HFM which will cause an Invalid Intersection Report
4 - If the mapped account is not an ICP account in HFM then map it to [ICP None]
Hired by Upstream, bought by Hyperion, then bought by Oracle...I've been there.
-Matt
Edited by: MattWalker on Feb 26, 2009 11:58 PM
Edited by: MattWalker on Feb 26, 2009 11:59 PM
Edited by: MattWalker on Feb 27, 2009 12:02 AM