Sizing the FCST_ITEM Table

  1. Calculate the total number of locations at all levels of the plan:
    number of departments (optional in Budget Management module, and never included in the solicitation process) + number of stores + number of districts + number of regions + number of divisions + 1 corporate

    See Location and Labor Budgeting Location Types.

  2. Calculate the total number of time periods included in the plan:

    52 or 53 weeks + 12 months + 4 quarters + 1 year

    = 69 or 70, where 70 is used as the conservative value for all further calculations.

    See Time Periods.

  3. Calculate the row count per version:
    total number of locations from step 1 x total number of time periods from step 2
  4. Determine how many versions are required:
    • Each budget has one version at all times (Master), even when locked.
    • Each forecast has two versions (Master and Sysforecast).
    • Each bottom-up projection has two versions (Master and Working).

    You must know how many plans are in the system at any given time to determine the number of total base versions that exist, regardless of the solicitation process.

Each time a budget or forecast undergoes the solicitation process, the application creates a Working version to track the changes for each user who edits it.

If using the in Phased view, the application also creates the Released by Me and Released to Me version for each user who edits the budget or forecast. Since nearly every user in the tree has a version that include everything below that user's location, there is essentially an extra version created for each level in the hierarchy involved in the solicitation process.

The number of the releasing levels is also an important factor. For example, if districts do not release the budget to the stores for solicitation, there is one less level, but there are three different versions. The actual usage varies depending on the number of locations participating in the solicitation process. These are conservative estimates.