Has anyone ever seen odd results from a user canceling a Forced consolidation, and subsequently running a normal consolidation? A later Forced consolidation seemed to have cleared up the issue. I maybe on a wrong path to what happened, but that's the best I can figure that happened.
Hi John
Maybe because of this behavior of consolidate and force consolidate is causing the issue you're facing.
Thanks, Omkareshwar
Archetype Consulting
Force Consolidation ignores DataUnit status and starts recalculating from the first period in the year. If you abort it, there is a chance that some data in previous periods will have changed but later periods have not had a chance to pick up changes; and there might be a possibility that the status of later periods will not be trustful, hence Consolidate might skip recalculating units that actually should be recalculated. Another Force will start again from the first period and churn through everything, ensuring all is in tip-top shape by the time it reaches the last period.
