Forum Discussion
If the forecast scenario leverages the "No Input Periods" setting, e.g. for a 2PLUS10 scenario the number of no input periods property is 2, then you can use an XFBR string.
In the XFBR string you would pass in the current scenario, and if the povtime <= the no input periods you could return "Top" for one of the dimension members in those columns, thus making those columns green / read only.
Or you could split the column set into 2 columns where the first column uses
T#POV.AllPriorInYearInclusive
T#POV.AllNextInYear
And in the first column refer to Ux#Top so that those months are non-inputtable.
- Tom_R1 day agoNew Contributor III
Thank you for the reply. However I am not getting the expected results. When I have an XFBR that sets a dimension to a non-base level making a column read only, the result of the distribution excludes that column, and adjusts the remaining two in the quarter to equal the amount entered.
For example, I have the three columns for the quarter, periods 4, 5 and 6. The equal $13,348, $12,888 and $19,298 respectively, for a total of $45,534. When I set the quarter to $48,000 and have period 4 set as read only, the result I get for the quarter is $61,348. The value is distributed evenly between periods 5 and 6, setting them to equal $48,000. The read only column is excluded from the distribution of the newly entered value and then added back at the end, leaving me with a value well above my target.
Any ideas how to solve for this would be appreciated.
Thanks,
Related Content
- 2 years ago
- 1 year ago