13 Period time dimension vs UD
Hello everyone, We have a client that uses 13 period time dimension in their current system that we are moving to onestream at the moment. They use period 13 to load TB' post adjustments even inp...
Forum Discussion
You could do it two ways:
- Have an app with a custom Time dimension, as described above, or:
- Have an app with the traditional Time, but with Scenarios set to work on a 13-period range.
There are trade-offs in complexity for each approach, choice will likely come down to personal preference of implementors.
Hi JackLacava
Are you talking about the setting below 'Number of No Input Periods Per Workflow Unit'?
Can you let me know how that works?
You don't need noinput periods. Just look up the "Range" Tracking Frequency. For example, this configuration allows you to enter monthly-level data for 13 periods.
I see, but then 13th period is 2024M1 which is needed for January data for next year. Still interesting.
Thank
