Hybrid Scenario – Pre-Aggregated Member Setup for Entity Summarization (V8.4)
Hi Team, I’m working on a Hybrid Scenario setup where the goal is to copy data from a source scenario to a management (MGT) scenario. This allows the MGT team to work with the data independently, using their own workflow with high-level access. So far, the base data copy works well. However, I want to summarize entity data in the target scenario so that users only see Entity parent nodes, while maintaining visibility of all other 17 dimension members (Account, UD1-UD8, etc.). To achieve this, I tried creating a dummy parent member (Entity X) in a new Entity dimension that mimics the top-level parent from the legal entity hierarchy (Entity Y). My intention was to use this structure in the Pre-Aggregated Members field in the Hybrid Scenario configuration, effectively copying: Entity X = Entity Y Unfortunately, this method worked successfully in Version 7.4, but does not appear to function as expected in Version 8.4. Maybe in version 9.0 +, we can successfully configure pre-aggregated entity mappings for Hybrid Scenarios? Can we customize this to version 8.0 and above? Would appreciate any advice or examples from the community if you’ve made this work in your applications. Thanks in advance! Chris
Disable eliminations and Develop Custom elim
Is there anyway we can develop a custom elimination process in the OS and attached with the cube. I see there is a "Custom" option in the cube properties but dont know what this function will do. FinanceFunctionType.ConsolidateElimination. I developed a custom rules which eliminate at first common parent dummy base member and it all ties when I sum but i wanted to get it roll up to Total Entity in USD.
Need help on 2 functions GetSessionDataTable and SetSessionDataTable
Hi All, I am trying to use getSessionDataTable and SetSessionDataTable for loading data from a file placed in harvest folder and then using the table to store it in cube with direct approach. Can anyone provide more insight on these functions? How is it work and if there are any challenge of using these functions?Cube | Data Access | Data Cell Access Security/Slice Security by U1#Geography
Data Management Access Security Please share your expertise to set up a Cube's Data Cell Access Security / Slice Security to limit data read access as outlined below: Dimension: U1# - Geography Total_Geography = Child 1 + Child 2 = Total / Top North_America = Child 1 / NA International = Child 2 / Int'l Slice Security: Access Level - Read Data by Geography - in a CV and a QV Total_Geo_Data = Read Total data | Read NA data and Read Intl data NA_Data = Read NA data | no data access = International and Total Intl_Data = Read Int'l data | no data access = North America and Total TY for your practical advice - SMEs.
