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?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.
Attribute Members on Entity Dimension Do Not Translate ?
I'm using attribute members, unfortunately on the entity dimension, so the associated data is stored and not dynamically calculated on Parent Entities. These attributes members do not translate to foreign currencies during the consolidation process ! I'm using a 'Custom Translation', and when I execute the method 'Api.Data.Calculate()' or 'Api.Data.CalculateForTranslation()' the attribute cells do not translate. The only way I was able to actually convert them is by using Data Buffers and forcing the conversion. Is there a reason why ADC methods do not translate attributes ? Is there a hidden property to activate in order to take these members into account ? Should I use 'Api.Data.Translate()' instead of ADC ? Thanks
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.
