Planning: Daily Data to Daily Import to a Monthly App
Have you seen a KB / post that met the requirements for daily data? Please share your experience / practical advice to help us meet daily data requirements. - for Planning - flat files: Daily Data per Month - flat files: Daily Import - Reporting by Day by Month Thank you folks for sharing your expertise.
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.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.
Supplied Parameters in Workspaces
Hello, I have a button which is fed from a List Box seen below Upon clicking this button, I would like Users to navigate to another Dashboard where the label component and cube view open with this button selection. Are supplied parameters the way to accomplish this? If so, what are the correct configurations to achieve this. Thanks for your help!Using OneStream to Track Inflation and Related Metrics
Hi everyone, I’m interested in learning how other organizations are leveraging OneStream to track inflation and other account-related metrics. Currently, our approach involves using the Account dimension to explicitly separate inflation impacts for specific expense categories. For example: FOOD_BEV – Food & Beverage Expense INFL_FOOD_BEV – Inflation related to Food & Beverage Expense These inflation rates are externally calculated and loaded via XFD uploads. To support different reporting views, we load the data into three separate accounts: _PER – Monthly _QTR – Quarterly _ANN – Annual We also use a view dynamic account without a suffix, which adjusts based on the selected view. Exploring Alternative Approaches I’m considering whether using a User Defined (UD) dimension might offer more flexibility. For instance: Keep the account as FOOD_BEV Use the UD to switch between metrics like: "Dollars" (actuals/estimate) "Inflation" (loaded via XFD) "Per Guest" (dynamically calculated) "Pricing" (potentially another loaded or calculated metric) This method could streamline the structure and allow for more dynamic reporting, especially if inflation rates are only loaded monthly and calculated for QTD/YTD using weighted averages. Open to Ideas I’d love to hear how others are handling similar use cases. Are you using UD dimensions for this type of analysis? Are there better ways to structure inflation tracking in OneStream? Thanks in advance for sharing your insights! — Jeremy Morgan
Confirmation Rules - Time Frequency
Hi there, We've developed rules that works properly in actuals with monthly frequency. Is there a way to use the same rules in other frequencies? I tried to link them to a budget scenario with yearly tracking frequency (Scenario property), but they are applied at the end of the year (for instance 2022) instead of each month. This behavior is kept even after changing to Monthly frequency, or "Member Filter" using "T#|WFYear|.Base". Is there a filter on the time from the WF itself? Ideally, we'd like to keep the actuals conf rules as they are. Thank you for the help. Regards
