Example

For this example, there are 5 organizational levels, and 1438 locations.

Assumptions for the example

The example uses these assumptions:

  • No more than two budgets and two forecasts are in solicitation concurrently.
  • "In solicitation" means that the budget/forecast is unlocked.
  • Old budgets and forecasts must be removed/archived before creating new ones. Otherwise, the system exceeds the limits of the sizing.
  • If new budgets/forecasts are required, either remove old ones or extend the tablespaces according to the formulas above.
  • To add more versions for reporting purposes or for what-if scenarios, use the above formulas to determine how many copies you need and thus how many pages you must add to your data and index tablespaces.

There is also an index tablespace linked to this data, which must be sized accordingly. The amount of space required for an index tablespace varies with each data/index link, but for this particular combination, the application’s experience shows that the data tablespace needs to be about eight times the size of the index tablespace. The index tablespace uses smaller pages (exactly 1/8th the size of the data pages) so the ratio should be 1:1 between the index (WB_BDG04K02_IDX) and data (WB_BDG32K01_REG) tablespaces.

To be safe, add some factor to this number to account for overflow. This depends on your organization and whether you want to allocate a certain percentage extra and/or, for precautionary purposes, allow for a full extra solicitation budget.