Analytical dimensions

BPDANALYSIS_01 - 12

For Budgeting & Planning, the analysis dimensions are placeholder dimensions except for BPDANALYSIS_06 which is used by Decision packages and BPDANALYSIS_12 which is used by Strategy Management. In the standard application, these dimensions are not used. They offered additional analysis for individual customer requirements.

Each of the analysis dimensions contains these structures:

  • TOTAL_ANALYSISXX. This element is used as standard read reference in reports and scripts.
  • N.A. The unassigned element below TOTAL element used as standard write reference in reports and scripts.

The ID of these standard elements cannot be changed.

Modification of the dimension:

The TOTAL element and the unassigned element N.A. will be generated automatically by Designer. These elements cannot be changed (ID). The attributes are individually editable.

Interaction with sub plans:

Sub plans can use analysis dimensions as long as it is defined that the sub plan and the main cube always use the same analysis dimensions. This can be realized within an industry-specific application or a customer-specific sub plan integration.

BPDANALYSIS_06 system attributes

Built-in system attributes should not be deleted.

  • Dimension provides placeholder elements for Decision packages.
  • Elements can be added, next free element (no Name stored) is used by the creation process.
  • New elements must follow the same type of "serial number".
  • WORKBOOK_ID. By creating a Decision package, the workbook ID (UN) (from the workbook) is stored in this attribute field.
  • STEP_ID. By creating a Decision package, the STEP ID (UN) – selected financial planning step - is stored in this attribute field, planning step is already selected within the workbook.
  • VERSION_ID. After selection of a version within Decision package (depending on configuration set/step selection), the VERSION ID (UN) is stored in this attribute field.
  • ENTITY_ID. After selection of an entity within decision package (depending on configuration set/step/version selection), the entity ID (UN) is stored in this attribute field
  • ORGANIZATION_ID. If enabled for step/configuration set/version/entity the ORGANIZATION ID (UN) is stored in this attribute field
  • USER_ID. Storing logged in user who created the decision package.
  • STATUS. 1/0 => 1 is set to activate the decision package in navigation (make it visible), automatically set within creation process.
  • WF_TRACKING_ID. Tracking ID used within workflow cubes is stored in this attribute field
  • CYCLE_ID. By creating a decision package, the CYCLE ID (UN) is stored in this attribute field, configuration set is already selected within the workbook
  • TACTIC_UN. Selected TACTIC_UN by creating a decision package.
  • DISPLAY_ID. Created automatically, requested to be displayed as ID within configuration widget.

BPDANALYSIS_12

  • Used by Strategy Management.
  • Elements are created directly within the application.