You can track the changes to all budget values of a phase using a date. To do this, on the project tab set the system setting Track budget value changes on phase to YES.

From this point onwards, for each change to a budget value, a so-called BudgetChange object is created in the background, which saves the old value with the current date (and time). By clicking on the button with three dots, you can view the budget value changes for each field and, where necessary, you can add further information:

By historicizing the budget values, it is possible to create interesting evaluations about the progress of the project.

In order for the budget changes entered in the list to be listed correctly in the background, the following renderers must be used in the list settings for the planned value fields:

dbmTim.BudgetWertRenderer for the following members:

• PlanWertExt
• PlanWertInt
• PlanKostenLeistung
• PlanSpesenWert
• PlanKostenSpesen
• PlanAuslagenWert
• PlanKostenAuslagen

dbmTim.BudgetMinuteRenderer for the following members:

• PlanMinutenInt

The user right to change or delete budget items is linked to the write permission on the relevant member.

The user right for double-clicking on the budget field with the display of the tracked list is linked to the read permission on the relevant member.

OCL operator bdgvalue is available for time-dependent access to budget values of phases:

<Projektphase>.bdgvalue(membername, datum, status)

• membername: The desired member from which the budget values are to be evaluated, e.g. 'PlanMinutesInt’, 'PlanVertext’, etc.
• date: The date value. If there are several BudgetChange objects on this day, the last one of the day is taken.
• status: Status filter. Can be -1 (all statuses), 0 (Ooffer), 1 (accepted), 2 (completed), 3 (rejected). If a status is specified (i.e. not -1), an additional check is made to see if the date passed is less than the date of change to that status (see date fields on the Further info page). If yes, i.e. the status was not reached on that date, 0.00 is returned.

bdgvalue('planWertExt’, encodeDate(2019,08,01), -1)

returns the relevant budget value (currency).

All BudgetChange objects are associated with the phase (BudgetChanges – phase). The following OCL expressions provide a filtered list of BudgetChange objects for each budget field:

• Planned hours: changesPlanMinutenInt
• Planned fee: changesPlanWertExt
• Planned internal fee: changesPlanWertInt
• Planned cost: changesPlanKostenLeistung

• Planned amount: changesPlanSpesenWert
• Planned cost: changesPlanKostenSpesen

• Planned amount: changesPlanAuslagenWert
• Planned cost: changesPlanKostenAuslagen

changesPlanWertExt.list.oclAsType(BudgetChange)->orderby(datum)

returns the list of budget changes (BudgetChange objects) in the field Services > Fee, sorted by date.

BudgetChange objects have the following members:

• newMinuten (Integer)
• oldMinuten (Integer)
• newWert (Currency)
• oldWert (Currency)
• comment (String)
• datum (DateTime)
• membername (String)
• modifier (String)
• phase (Phase)

BudgetChange objects are standard user entries and can therefore be shown in lists (expression and SQL folders, link types).