Forecasting Adjustments
Hello! I have a question about other customer experiences and best practices regarding forecasting adjustments. We have forecast scenarios set up and previously would copy the entire scenario as the base for additional “adjustment” scenarios. We used these to toggle on or off certain risk adjustments in future periods but in order to save space and stop replicating so much data, we’re trying to move to another method instead. In our application, we have our UD3 set up as a more detailed Origin dimension where specific layers of adjustments are added (journal entries are split into more detail for GAAP or non-GAAP for example). This is where we were planning to add the adjustments but I wanted to check in with everyone else first to see if anyone has experience. Basically what we want is one scenario where I can pull a UD3 “base” of the expected forecast data then “base+adj1” which would be an alternate hierarchy of the base data plus adjustment 1. Then we’d replicate that alternate hierarchy as needed for specific adjustments. Would love to hear how you’re accomplishing this - any feedback would be appreciated!
Entity Name Changes
Hi Team, I would like to understand how you are managing the Entity changes on a monthly basis. For eg: the Entity name in 2021 M6 is San_Jose_213 and it is changed to SFO_213 in 2021 M7. If I choose the rename option, then 2021M6 cube data will override but custom tables created for our requirement will remain with the old MEP name. On the other hand, if I chose to create a new entity how to intact both the entities for future referenceMetadata import automation
Hi Can anyone suggest , how can we automate loading of metadata into onestream from a flat file /table. What is the format of the file. I am aware of loading using xml from utilizing the metadata excel builder utility , but my client wants to automate metadata update in Onestream. I am not finding much documentation around that. How is this achieved ?
Intercompany security issue across cubes
Originally posted by Katarina Sterley We have 4 extensions to our main cube and now we have a problem with the standard intercompany matching reports. The end users do not see the transactions on the lowest level from another cube. They only see the IC transactions within their own cube. If they look at the main account they see the transactions but that is not displayed in the standard intercompany matching report within the workflow. Like this from quickview: From Workflow report: Any suggestion on how we should solve this? Kind regards Katarina
Mid-Year Divestiture Reversing full YTD Data
Hi All, We have a client who wants to exclude a subsidiary from their reporting rollup starting mid year in May 2022. Unfortunately the consolidation view is set to YTD so it appears that when we switch the consolidation percentage to zero then it reverses all of the YTD data for the whole year opposed to just excluding the data beginning in May. Is there a simple solution to resolve this? Or is a business rule required when divesting mid year? It seems like a requirement that should be pretty common and have a pretty straightforward solution like in Hyperion but we haven't had any luck so far. Any thoughts or guidance is greatly appreciated. Best, Joe
