Forum Discussion
Koemets
3 years agoContributor
I saw it more than once, OS behaves oddly with certain combination of view settings (between datasource, scenario etc) and pushes "ghost" YTD offset from current period to next, treating it as if zero periodic value was loaded into the next period
I'd like to piggyback on full clear idea. That's a good start. Then load M4 and see if YTD value offsets in M5. Then start playing with views and maybe turn off the next period retention to see if that affects it. And if yes, then you will know the cause and will be able to start addressing that particular issue.
Related Content
- 11 months ago
- 7 months ago
- 11 months ago