2 Replies Latest reply on Mar 3, 2020 8:44 PM by Mikkis

    Forecast consolidation issue - Erroneous data

    3133850

      In our HFM application, the March Forecast scenario is seeded from the February Forecast scenario. The seeding process is working as expected. In the March Forecast, the month of January and February equals Actuals, while March - December equal the February Forecast until the business begins to update the forecasted months (March - December) in this example.

       

       

      If the business submits data to one account (example Gross Sales account 400105) and consolidates all 12 months, all accounts on the P&L are impacted erroneously when in theory, only account 400105 should have changed. If the business submits data to one account (example Gross Sales account 400105) and consolidates only the forecasted months (March - December), the consolidation works as expected, only changing account 400105. This issue was able to be replicated in our QA environment. Please note, this did not happen in our Feb_Fcst scenario in either Production or QA.

       

      Is anyone aware of a 'bug' or an issue due to a recent patch?

        • 1. Re: Forecast consolidation issue - Erroneous data
          CBarbieri

          There is not enough information in your post to answer this. The "seeding process", data submission process, and your consolidation process are specific to your application. Data changes to a single account will cause that entity's calc status for the value member, it's ancestors, and the entity's ancestors, to be impacted for the period in which data changes, through all periods that have data until the end of the current year. There is not a calc status per account but instead per entity-value-year-period-scenario combination. The scope of impacting is also a function of whether you load through FDMEE, or use a form, and whether that form has one or multiple periods. When you calculate data, all impacted data units in the form are calculated. If you force calculate, all data units in the form will be calculated, regardless of their status, so you have to factor this in as well. I wouldn't be quick to imagine a bug is at play (they are rare) but would focus on understanding the application design and process first.

           

          - Chris

          • 2. Re: Forecast consolidation issue - Erroneous data
            Mikkis

            This may be a stretch but did you seed Periodic or YTD? And what are your Scenario settings for Zero View for Non-Adjs? Is the submission for forecast periodic or YTD?