File Library

In some Hyperion Planning projects, security becomes so complex that it takes more than just putting 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 center from different regions around the Entity hierarchy? Moreover, that data is restricted according to the region’s security group using only one attribute dimension? Furthermore, each user can see aggregated values correctly for your region only?
This case study will show how to generate and maintain leaf level member security settings based on physical geography attribute dimension on one of Dell’s global Planning application using only ODI and planning application metadata repository information.