Generalise business rule to fetch common inputs region wise

Question

Hi,
Our entity dimension is changed to program(Which means projects) dimension which will include the location as a parent and under that are the list of programs specific to that location. our legal entity is a custom dimension. This change is done to enable the workflow program wise. Now there are certain planning assumptions which are common across programs in a country. The common inputs are captured against a member in entity and legalentity dimension. The member names are something like IND_Prog_assumptions in entity dimension and India_Assumptions in Legalentity dimension. The hierarchy is something like below
LegalEntity,India,Chennai,Location1
LegalEntity,India,Chennai,Location2
LegalEntity,India,India_Assumptions
Entity,IND_Programs,Prog1
Entity,IND_Programs,Prog2
Entity,IND_Programs,IND_Prog_Assumptions
There are sone calculations which will involve pulling the data from these common inputs. I have written a business rule by fixing each and every location separetely. Is there a way to generalise this? i.e. Check what the current location is. And then get the corresponding member like IND_Prog_assumptions for that location. Basically one fix statement which will do the calculation based on the selected entity and legalentity dimension.
FIX(@DESCENDANTS(India),@DESCENDANTS(IND_Direct))
"Shrinkage %" = @ROUND(((India_Assumptions->IND_Prog_Assumptions->"Holidays in a year")/(India_Assumptions->IND_Prog_Assumptions->"Total working days in a year"))*100,2);
ENDFIX
FIX(@DESCENDANTS(USA),@DESCENDANTS(USA_Direct))
"Shrinkage %" = @ROUND(((USA_Assumptions->USA_Prog_Assumptions->"Holidays in a year")/(USA_Assumptions->USA_Prog_Assumptions->"Total working days in a year"))*100,2);
ENDFIX
Edited by: ragavhere on May 8, 2010 4:59 PM
Edited by: ragavhere on May 8, 2010 5:07 PM

Answer 1

Hi msandrews,
Thanks for your response. Your suggestion worked well.
But now the problem is different coz the requirement has changed. The common inputs are captured against the members like IND_Prog_Assumptions,US_Prog_Assumptions,Phillippines_Prog_Assumptions in the Entity dimension and India_Assumptions,USA_Assumptions,Phillippines_Assumptions in the Legalentity dimension. These common inputs have to be pushed to the other programs in the entity dimension as well as in the location dimension region wise. For eg. the value captured against IND_Prog_Assumptions and India_Assumptions have to be copied to the programs which run in india and the value captured USA_Prog_Assumptions and USA_Assumptions have to be copied to the programs running in USA. The hierarchy of LegalEntity and Entity dimension is here again for your reference.
LegalEntity,Global,APAC,India,Chennai,Location1
LegalEntity,Global,APAC,India,Chennai,Location2
LegalEntity,Global,APAC,India,India_Assumptions
LegalEntity,Global,APAC,Phillippines,City1,Location1
LegalEntity,Global,APAC,Phillippines,City1,Location2
LegalEntity,Global,APAC,Phillippines,Phillippines_Assumptions
LegalEntity,Global,North_America,USA,City1,Location1
LegalEntity,Global,North_America,USA,City1,Location2
LegalEntity,Global,North_America,USA,USA_Assumptions
Entity,Global_Direct,IND_Direct,SD_IND,Prog1
Entity,Global_Direct,IND_Direct,SD_IND,Prog2
Entity,Global_Direct,IND_Direct,BD_IND,Prog1
Entity,Global_Direct,IND_Direct,BD_IND,Prog1
Entity,Global_Direct,IND_Direct,IND_Prog_Assumptions
Entity,Global_Direct,US_Direct,SD_US,Prog1
Entity,Global_Direct,US_Direct,SD_US,Prog2
Entity,Global_Direct,US_Direct,BD_US,Prog1
Entity,Global_Direct,US_Direct,BD_US,Prog1
Entity,Global_Direct,US_Direct,USA_Prog_Assumptions
Entity,Global_Direct,Phillippines_Direct,SD_Phillippines,Prog1
Entity,Global_Direct,Phillippines_Direct,SD_Phillippines,Prog2
Entity,Global_Direct,Phillippines_Direct,BD_Phillippines,Prog1
Entity,Global_Direct,Phillippines_Direct,BD_Phillippines,Prog1
Entity,Global_Direct,Phillippines_Direct,Phillippines_Prog_Assumptions
I tried to do something with DATACOPY. But nothing worked out. I am confused in proceeding.
Your help is highly appreciated.
Regards,
Ragav.