If you have a scenario where you need to plan across multiple fiscal years, then you need to go to Application Properties and set Allow Loads After Workflow View Year to "True".
OneStream EmployeeHi Scott,
An alternative that could be used would not preserve the "old" people plan in the same scenario if planned annually.
If such a rolling/working scenario is used then the plan from WFYear M1 to WFYear M24 could transform, for example, into the WFYear1 M1 to WFYear+1 M12 in the transformation rules. There may be a need for a code adjustment if only 12 periods of the workflow year are transferred.
Is the concept to update the people plan on a monthly basis?
Generally customers have a scenario for each period of the year in that case.
The tracking frequency is also about locking certain periods, so if the plan does not get updated on a monthly basis, but only yearly, then monthly data tracked yearly could suffice.
Is everything else to be entered in the scenario also to be planned in the same way, i.e. on the same time horizons?
Your post resounds as though you prefer a more formalized process, the range scenarios allow for Yr2 data to be kept while planning the same year as Yr1 in a new ranged scenario. Allowing two different formal plans to be compared with each other and later to Actual data. Several customers that I know of have a start year prefix on a larger set of ranged scenarios. How long is each scenario to be kept if this is case?
It sounds like a wider discussion with your Architect.
