Special feature for calculation of critical time attributes

In the calculation rule (calcattr), for the critical time attribute, you need to assign the delete XML attribute the value yes (CTK: Enable the Delete attribute value check box). If no result value can be calculated, the previous dimension value must be deleted from the database before a new calculation can take place.

Example

Extract from the calculation rule for the Critical goods issue date attribute

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

<!DOCTYPE keyindicatorconfig SYSTEM

"KeyindicatorConfiguration.dtd">

<keyindicatorconfig>

...

<calcattr name="AT_CRITICAL_WAUS_DATE"

type="PROCESS" delete="yes">

...

</keyindicatorconfig>

Use PPM Customizing Toolkit to define, calculate, and register critical time dimensions.
In the Measures and dimensions module, you can use the Dimensions component to conveniently enter the required definition information. You can create the definitions of the calculation rules for the critical times in the Calculated attribute types component.
Register critical time dimensions to the preferred process type groups or process types using the Process tree component on the Process analysis dimensions tab in the Processes module.

Example

The following example calculates the Critical goods issue date. Instances in which no goods issue has been posted within four days of the Create delivery function (SAP.LIEF) being executed are classed as critical, i.e., the Post goods issue function (SAP.WAUS) does not occur in the process instance. The calculation rule for the AT_CRITICAL_WAUS_DATE attribute calculates the critical time by adding a time span of four days (354600 seconds) to the time of the earliest occurrence of the Create delivery function.
The calculation is made to the nearest hour (precision="hour" XML attribute for the CRT_TIME_WAUS dimension). For example, if the earliest reference time (AT_TIME) for the Create delivery function in a process instance is 13.07.03 20:26:55, based on the above calculation rule the critical goods issue date, correct to the nearest hour, is thus calculated as 17.07.03 20:00.

The result of a calculated critical time attribute must always be available in a time stamp format (TIME data type).

This extract from the measure configuration shows the definition of the critical time dimension CRIT_TIME_WAUS. The attribute and value combination earlyalert="yes" identifies it as an Early alert system time dimension.

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

<!DOCTYPE keyindicatorconfig SYSTEM

"KeyindicatorConfiguration.dtd">

<keyindicatorconfig>

...

<calcattr name="AT_CRITICAL_WAUS_DATE"

type="PROCESS" delete="yes">

<calculation>

<if>

<not>

<exists>

<attribute name="AT_OBJNAME_INTERN" nodetype=

"OT_FUNC" objectname="SAP.WAUS"

onerror="CONTINUE"/>

</exists>

</not>

<then>

<addtimespan>

<min>

<attribute name="AT_TIME" nodetype="OT_FUNC"

objectname="SAP.LIEF"

onerror="EXIT_NO_WARNING"/>

</min>

<constant>

<dataitem value="345600.0">

4,000

<datatype name="TIMESPAN">Time span

</datatype>

<scale name="DAY" factor="86400.0">Day(s)

</scale>

</dataitem>

</constant>

</addtimespan>

</then>

</if>

</calculation>

</calcattr>

...

<timedim name="CRIT_TIME_WAUS" dimtype="PROCESS"

precision="HOUR" attrname="AT_CRITICAL_WAUS_DATE"

calculated="TRUE" internal="yes" earlyalert="yes"

storage="INCUBE" importmode="OPTIONAL">

<description name="kritischer Warenausgangstermin"

language="de"/>

</timedim>

...

</keyindicatorconfig>

The Early alert system component of the Instance controlling module in the PPM front-end checks whether critical goods issue dates have been exceeded. In the example, it is assumed that the critical dimension CRIT_TIME_WAUS is registered at the Order processing\Standard order process type.

ppm_customizing_34

The current deviation from the critical goods issue date at the time of execution is specified in the analysis area in the Absolute deviation [Days] column. The execution time for the early alert check is the current system time. In the example, after executing the early alert check for the Critical goods issue date dimension, all process instances of the Standard order process type in which the critical goods issue date has been exceeded are displayed in a process instance table. For the process instance selected in the illustration the critical goods issue date has currently been exceeded by 983.843 days. This is the absolute deviation in days from the critical goods issue date at the current execution time (in the example 10.08.05 15:31).

Alternatively, you can identify critical process instances using the runppmanalytics command line program using the -earlyalert option (see PPM Operation Guide).