![]() ProjMode and Inclusive DatesUsing ProjModes 3 and 4 for a subtle change in defining the finish date
| ||||||||
Certain values of ProjMode allow for including the finish date in calculating the amount in a projections function.
These two settings are therefore recommended where you have a specific reason to include the last day in the projection, for example if it specifies this in a business contract. As a general rule, we recommend sticking to ProjModes 0 and 1, which are more intrinsically consistent and logical. Note also that Loans would nearly always operate with an 'exclude the finish date' philosophy. How ProjModes 2 and 3 Work This is very simple. There are certain variables that are classified as 'finish' variables - you'll see them listed under each function definition inasmuch as they pertain to that function. In the input screening section of BF, if a ProjMode 2 or 3 is encountered, the finish variable(s) for that function is incremented one day. Then ProjMode is reset to 0 and 1 and execution continues. Note that it is just 'finish' variables that are dealt with this way. A variable like Finish will be adjusted in the manner described, but not a variable like Start or MidPoint. Where the 'finish' variable is part of a range, like ToDates, it is the last date in the range that is assumed to be the finish variable and is adjusted, the other dates remain unchanged. Therefore it is only the true end date of the projection that is shifted, the dates of any transition in rates or levels in the function are unchanged. |