HS.ImpactStatus Functionality

You might notice that the rules seem to always seem to pull data from other points of view (Year, Scenario, Period, and Value). That is true, with only a couple of exceptions. The Impact Status rule is one of those exceptions. This rule can go to another point of view and change the status of that entity to be impacted. Consider this typical example: You want to have a rule that determines the opening balance for an account (Retained Earnings). Now assume that at some point you might need to go back into last year’s data and make changes that affect the ending earnings of that year.

Since there is no link between the current and prior year, after changes in last year have been made, the status of the current year will continue to show OK. In order for the change to be reflected in next year’s opening equity, users typically would have to go into the subsequent year and run a Force Calculate because the entity would have a status of OK. However, you don’t want to do that. In fact, if you are asking users to run Force Calculate in your application, you could have a problem. But since we cover that in another chapter, let’s stick to the ImpactStatus. If the change were in the first period of a year, that would impact all future periods where there is data in the same year. However, crossing subcube boundaries (year, scen....