In some Hyperion Planning projects, security becomes so complex that it takes more than just granting access to some security groups on the high-level members of the dimensions. Global companies often have the necessity to create multiple Planning applications to meet the diverse regions of the globe. However, what happens when the business requires a single application with a single plan type that contains cost centers from different regions around the entity hierarchy? Moreover, is that data restricted according to the region’s security group using only one attribute dimension? Furthermore, does each user need to see aggregated values correctly for your region only? This paper demonstrates how to generate and maintain leaf-level member security settings based on attribute dimension on a global Hyperion Planning application using only ODI and Hyperion Planning application metadata repository information.
Congratulations to the 2021 ODTUG Officers Congratulations to the newly elected officers of the ODTUG Board of Directors! One of the things that sets ODTUG apart is the dedication of our volunteers a...
ODTUG would not be the organization it is without all our amazing volunteers! First, we would like to thank everyone who has given their time and dedication to making each of our communities one of a ...
UPS6756, #154 4403 Oleander Drive, Suite C
Wilmington, NC 28403