Forum Discussion
We have a similar situation where we want to use Org by Period and the Actuals consolidation view is set to YTD. We are testing changing the consolidation view to periodic and it appears to resolve the issue but I am worried about other impacts. Curious as to why you couldn't just change the consolidation view? Are you concerned about the performance impact or inaccurate data?
- jreis3 years agoNew Contributor II
Thanks for the response! Agreed changing the consolidation view was our preferred approach as well but when I went to test that in a Dev app I found that changing the consolidation view actually changed the final data in the actual scenario over multiple years when comparing back to production.
That being said, it is possible these differences could be due to specifically how we had our member formulas and/or business rules written. But because they are in a go-live state and there are multiple years of variances I am hesitant to make that switch and try to troubleshoot the data variance and rules across the entire app. Once I have time I think I am going to try the approach ChristianW mentioned above about creating just a new rule to carry the data for the remainder of the year and will report back on whether it is successful.
- camagruder3 years agoNew Contributor III
Thanks for the response. I wanted to follow-up and let you know that we did end of changing the consolidation view on the scenario to Periodic vs using a BR. We did a lot of testing and migrated it to production last week and have not had any issues.
Related Content
- 2 years ago
- 2 years ago