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 th...
Forum Discussion
Do you find that the UD3 is necessary for adjustments versus the origin dimension? I’ve raised this in our design sessions and it seems like the origin dimension may work, but I’d rather set things up properly the first time rather than need to add the dimension later if we realize the origin dimension doesn’t suffice.
We make so many forecast/budget adjustments in our current tool which I have a separate dimension for layering, so my thought was to include a separate dimension in OneStream as well.
I was talking to our SI and talking through using a separate dimension, or the combination of a new scenario and the origin dimension.
Hi Jeff,
I went with UD3 because we already had UD3 as our datatype dimension which is essentially a more built out origin dimension. The origin dimension is specific to OS itself and cannot be edited. And regarding scenario, to Nick’s point above, the scenario dimension doesn’t aggregate/consolidate. Hope that’s helpful.
Thanks for the info! Definitely going to have to consider adding a UD for the data types since the origin dimension is not customizable.