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
Hi Mike,
Thanks for explaining. Do you have experiences working with 13 period time dimension? Does it create any problems for view dimension for example. Because you know you have that member Trailing12Months, is there going to be a Trailing13Months member created automatically?
Also the aggregation of time dimensions, when the user selects a year total the YTD data for P13 will be shown right?
V#YTD will automatically work with a P13 Time Profile, because it is same Year. There will NOT be a V#Trailing13MonthTotal that gets created.
If it were me I would not rebuild the application. It sounds like your business case is simply to enter Year End adjustments. You could accomplish this using the Flow dimension and a Data Entry Form that only is WF eligible in Period 12. So that YE Form will not appear as a valid WF task in Periods 1-11.
The best use case for a Period 13 application is if you must/need to do Cash Flow and FX in that Period. If the business simply needs to enter a plug or adjustment - create a member F#YE_Adj and promote that to a Form for manual input in Period 13 only in a WF. The CV Row/Col in that Form could be something like V#YTD:F#YE_Adj:Name(Period 13 Adj), but your base Time would be T#|WFYear|M12.
Hope this helps.
Hi Mike,
We have a similar case with our company, where there is a P13 in Oracle and we need to perform a year end adj in OneStream as well, if we wanted to go with the flow option with the data form. How can that be set up?
