Same Scenario Across Two Cubes vs Separate Scenarios — Pros & Cons?
Hello everyone, I’m looking for feedback on the pros and cons of using a single Actual scenario across two cubes (e.g., Consolidation and FP&A) versus defining separate scenarios for each cube. For example: Option 1 (shared): Consolidation Cube : Actual (Scenario Type = Actual) FP&A Cube : Actual (Scenario Type = Actual) Option 2 (separate): Consolidation Cube : Actual (Scenario Type = Actual) FP&A Cube : Monthly (Scenario Type = Control) From your experience, how do these approaches compare in terms of data governance, maintenance, performance, flexibility for planning/reporting, and potential risks (e.g., unintended impacts between cubes)? Any best practices or lessons learned would be greatly appreciated. Thanks in advance!
Upgrade from 9.1 to 9.2
Hi, I would like to know if any major changes need to be carried over from 9.1 to 9.2 version upgrade. As we had some changes performed when we moved from 8.5.1 version to 9.1.0: Winscp to SSH.net Marketplace solutions to be upgraded to latest versions also Navigation center replaced applications reports, security audit reports. so, we had to remove the existing AR, SAR solutions. We had .vb in the extension wherever the xfbr has been referenced that extensions were no longer supported in 9 version. Thanks in Advance!Tech Talks After Hours: CPMx IFRS
Join Aymar Doat and Tom Linton as they explore CPM Express IFRS; a productized implementation accelerator that delivers a pre‑configured, unified financial consolidation and planning foundation with an IFRS emphasis requiring minimal configuration to rapidly improve time‑to‑value. To receive OnePoints for watching this Tech Talk video, please visit the link below: Tech Talks After Hours: CPMx IFRS
How to Add Adjustments with Add Back Category and Free-Form Add Back Name to Actuals in OneStream?
Hi Everyone, I’m working with Actuals data structured like the attached screenshot and want to add adjustments linked to this data. Key points: Adjustments must tie to Actuals by Company, Account, and Month Each adjustment includes: An Add Back Category An Add Back Name, which is free-form text and can vary monthly I want to maintain monthly detail and enable reporting and drill-down by both Add Back Category and Add Back Name My questions: What’s the best approach to model and load adjustments with both a Add Back Category and a free-form Add Back Name in OneStream? Should Add Back Name be a UD member with auto-create, a text attribute, or something else? How to avoid member explosion or reporting complexity given the free-form nature of Add Back Name? How can I ensure adjustments roll up correctly and maintain data integrity? Any recommendations for validation, governance, and reporting for this kind of adjustment detail? Thanks in advance for your insights!Sum PLP Register Column for all employees
In People Planning, is there a way to sum all the values in either the PLP register or calc plan for all employees to get a total to calculate an allocation. My client would like to allocate a Pension Pool by the Employee’s Wage / Total Employee Wages. I am trying to find a way to calculate the Total Wages for all Employees using Allocation Methods as they run by RegisterID/CalcPer. Any ideas.
