IC Elimination and USD Overrides
Our Currency Override formula in the Flow Dim (EndBal_Input) has been working great, no issues. We have been using IC Elim's on all of our Balance Sheet accounts except Equity/Investments. All of our E/I accounts are Currency overrides. We turned this IC on in January and are now noticing that the Elim amt is the FX calc'ed value and not the Currency Override value. Thus not zeroing out at O#:Top. Not sure how to adjust the O#Elimination member at the parent level for IC members. Any suggestions on how I might go about fixing. Not sure if I need to include a fourmla in the Flow Dim to handle different Origins or if it is handled elsewhere. Just looking for ideas to think about. In my example below you can see the Elim amount is using the Closing FX rate and not the Fixed USD amt or rate. Clarke
Cube Properties Best Practices!
Given a situation, determine the correct properties for the Cube. Certification Exam. Workflow The most common setting Is Top Level Cube for Workflow (Main Cube) = True Project requirements dictate Suffixes for varying Workflow by Scenario Type Assigning Suffix by Scenario Type allows the same Entity to be assigned to different Workflows in different Workflow Cube Root by Scenario Type The best practice is to configure a suffix early on for common Scenario Types regardless of whether they get used. NOTE: These settings cannot be updated once data is loaded to a specific Scenario Type. Leaving blank is defining the suffix as well. Calculation Consolidation and Translation Algorithm Type Most common setting = Standard Settings based on design decisions on how consolidation and translation to be customized. Recommendation – Only change from Standard to Custom on sporadic cases. Elimination and Translation logic should be done either on the Member using O#Elimination or C#Elimination or using Translate as part of the Finance Business Rule and assigning it to Cube. Use Standard Using Business Rules for FX Rates for Translation Algorithm Type in the above case. Calculation Properties: Business Rules Cube Properties: FX Rates Cube Properties: Set Default Currency FX Rates for the Cube. The most common settings for the Cube are shown in the screenshot. Default Currency is dependent on the currency of the application. NOTE: Triangulation is dependent on default currency Best Practice – Control the FX Rates by Scenario. Deep dive of FX Rates discussed during setting Scenario settings. For more -OneStream Certified Professional (OCP) – Lead Architect Certification Prep Webinar in Navigator.
YTD Entity Ending Mid Year
When loading a YTD feed for an entity, if that entity is terminated mid-year (possibly moved to a new entity due entity structure changes) the imputed periodic value translates at the current period FX rate causing there to be a residual USD value remaining in the first period where no balances exist. This issue is discussed on page 77 of the Foundations book, however the explanation on that page seems to indicate that this is mathematically correct, and therefore seems to infer that it is therefore a correct accounting presentation. Has anyone found any combination of scenario, workflow, or cube settings that has prevented this from happening, or have you used a business rule or some other process to remove these values from periods where no activity or balances should appear?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?
