Lock Out Sold Entities, Keep Their Impact!
Managing Sold Entities Without Losing Consolidation Results. Hi Community, We’re looking to hear how others handle this in OneStream: When an entity is sold in a specific period (e.g., 2025M5), the requirement is to: ✅ Retain its posted journal values in group consolidation ❌ Prevent any further use of the entity (journals, data loads, forms) The challenge we've encountered is that setting In Use = False — even after journals are posted and consolidation has been run — can cause OneStream to drop that entity’s data from the group during future reconsolidation. This results in the loss of valid P&L impact from the sold entity. Our workaround: Keep In Use = True for the sold period Use workflow locks and security restrictions to block future changes Only set In Use = False once everything is finalized and locked 💡 Feature Suggestion: It would be incredibly useful to have a system property or override flag that allows us to: Set In Use = False to fully disable the entity in the workflow Still retains its consolidated values during reconsolidation How are you managing this today? Your thoughts! Thanks,
Consolidation in a Dynamic Cube
Hi Experts, I have a dynamic read only cube, source of this cube is a relational table having details like salary band, department, position, benefits %, tax %, etc. I am simulating some calculations in workspace assembly and setting records in the dynamic read only cube. I see expected data at base entity levels. How can I see correct data at the top entity level? Entity structure: I see same data at multiple levels. Asia and AllRegions data should not be same. Also drill down results are same at multiple levels which is weird. So if we are setting data at base entities in a dynamic cube, how does consolidation work here? JackLacava , would you please clarify this?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.
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.possible to post directly to "translated" without being overwritten? (for USD journal in EUR entity)
hi all, I just want to confirm the tool's approach: If I have a foreign entity (defined as EUR), can I post a journal entry directly to USD (Translated), and it won't be overwritten by the built-in currency translation? (in other words, it won't just overwrite translated with whatever is in local?) Or is there something else I have to do to accomplish a USD journal in a non-USD entity?
Consolitation Relationship Properties
Hi, I want the hierarchy illustrated below. Entity B owns 90% of entity C, and in the consolidation of entity B we calculate minority interests of 10%. At this step, I have no doubts. However, entity A owns entity B 100% and also owns entity C 100% (90% direct + 10% indirect). So, in the consolidation of entity A, we need to eliminate the calculation of minority interests done previously in the consolidation of entity B. I don't know how to set the properties to do this. Can someone help me?Actual at other FX rate (PY/Bud/PP) - Currency Neutral - How to view Fcst Scenario at other rate
Two part question. Comparing Actuals as other Rates to remove currency flux We want to take our Actuals and view at PYE, PYP & budget FX rates to take out flux in currency. Is there a feature (outside of creating BR's or Alt Rate types) to do this. We currently have built 3 scenario for the above rates and it works as expected for base level members. Where we run into issues is with converting to Reporting currency at parent members. Ex is converting our EMEA entity (currency - EUR) to USD. The BR seems to store the USD value at the base entity but is converting from EUR to USD at parent level using OS logic (ie current defined rate for Actual scenario). It is not consolidating up the USD value but converting from EUR at parent member. This BR was created almost 6 years ago when we implemented so hoping there is something out-of-the-box now that will do this. I am exploring creating 3 new Rate Types: PY Budget, PYE Actual & PYP Actual. I would copy all the PY rates into these 3 new rate types and then create 3 Actual scenarios, each using these new rates. The big issue is having to copy all the data over from Actuals and then reconsolidating. Hoping there is a better way. Fcst Currency Neutral - Having Fcst at the Budgeted rate We are US company with large % of our business from Europe and the flux in EUR to USD is distorting our review of how we are doing. Looking for a way to see our Fcst how we expect (current process) and at Budget rate. I could copy to new scenario that is set to Budget Rate but we have 12 Fcst scenarios and that would take up alot of resources to copy and consolidate as we would need to do this many times during Fcst process (ie it would not be something we only did once the Fcst was closed but during the process) Would this be a UD8 member and if so, how would it handle Base and Parent level members. Looking for best practice advice on how to handle these two issues.How to Run Workspace Assembly from a Data Management Step In 6 Easy Steps
This was originally a question.It took a while to figure out, so to save someone else the hours of trial and error, here is the process I use in detail, start to finish, to run a Workspace-based Data Management step in a Workspace Assembly business rule. Here's a How-to step by step: List of abbreviations used below: DM: Data Management WS: Workspace MU: Maintenance Unit BR: Business Rule AS: Assembly 1. Workspace:Set the NameSpace Prefix - this is what gets filled in at runtime for __WSNameSpacePrefix 2. Assemblies: Note these properties 3. Create the Assembly Business Rule:Create an "Extender" business rule, this is done by right clicking files and selecting "Extensibility Rules" Add some test code, to verify correct configuration, such as BRApi.ErrorLog.LogMessage(si, "Hello from the new extender!"then code the way you would any other extender 4. Create The Data Management Group: Create a DataManagement Group in the same workspace that the Assembly that has your business rule is in 5. Create a Data Management Step - Create a DM step in the new DM Group, reference the rule using the pattern: Workspace.{WorkspacePrefix}.{AssemblyName}.{BusinessRuleName} In this case it would be: Workspace.Current.DMTestAS.DMTestStepExtender Note: we could also use 'DMTestWS' instead of 'Current'.We use Current because the DM Step is in the same WS as the Extender Rule. 7. Done! Test the DM Step with run button and check the error log(System Tab -> Logging -> Error Log),for your test code's output.
