Using organizational units as dimensions

Using an organizational unit as a dimension does not represent a separate dimension type. Specifying a special calculation rule copies the name of the organizational unit to the relevant functions of the process instance as an attribute.

Example

The following file extracts from the measure configuration illustrate the creation of a dimension from organizational units:

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE keyindicatorconfig SYSTEM

'KeyindicatorConfiguration.dtd'>

<keyindicatorconfig>

...

<calcattr name="AT_ORGUNIT" type="OT_FUNC">

<calcclass name= "com.idsscheer.ppm.server.

keyindicator.attributecalculator

.ZAttributeCalculatorOriginator"/>

</calcattr>

...

<oneleveldim name="ORGUNIT" dimtype="FUNCTION"

internal="no">

<description language="de" name="Processor"/>

<leveldesc>

<dimitem attrname="AT_ORGUNIT" colname="FIRST_ID"

calculated="TRUE">

<description language="de" name="Processor"/>

</dimitem>

</leveldesc>

</oneleveldim>

...

</keyindicatorconfig>

The AT_ORGUNIT attribute is created for each function instance and is assigned the name of the organizational unit as its value. This attribute is used to create the one-level function dimension ORGUNIT.

The AT_ORGUNIT attribute is one of the default attributes in the PPM system and does not need to be defined.