Data sources

If a lower level other than monthly exists, you must directly adjust your database tables:

  1. Add the DetbudPeriodSetID parameter to the NONSTRUCTURE_PARAMS table of the database, using a database tool such as SQL Server Enterprise Manager. The DetbudPeriodSetID parameter identifies which hard-coded period (monthly, quarterly, semiannual) should be used as the monthly level.
  2. The numerical value assigned to the DetbudPeriodSetID parameter (PARAM_VALUE) should be the same number as the SET_ID value associated with the monthly level (12 or 13 periods) in the PERIOD_SET table. The monthly level is not the same as the Monthly periodicity in the PERIOD_SET table when a daily or weekly level exists.
    For example, in an application set up with weekly, monthly, quarterly, and yearly levels (note that only four levels are allowed in any application), the weekly level is assigned to the hard-coded Monthly periodicity (leaf level), the monthly level is then assigned to the hard-coded Quarterly periodicity, and the quarterly level is assigned to the Semiannual periodicity at the time the database is created. In this case, since the hard-coded Quarterly periodicity (monthly level) uses the SET_ID value of 2, the DetbudPeriodSetID parameter should likewise be assigned 2 as the PARAM_VALUE.

If this parameter is not set, the current default behavior is assumed (period leaf members are used). If the leaf member is not based on 12 or 13 periods, Detail Budgeting will fail.