Period Management in the Condition Technique 

Use

In business terms, period management in the condition technique is the same as period management for the commission system. Period management in the condition technique covers the following areas:

·        Auditability

Changes to condition records, processors and processing periods are recorded in full.

·        Management of validity periods

The different versions of a condition record are represented:
Old, but valid statuses, and current but invalid statuses of a condition record are stored such that they can be reconstructed. Time consistency between condition records is ensured. Changes can be made that are not valid until a certain time in the future, or that are retroactive and apply to existing statuses.

·        Management of processing times

Different processing statuses are represented and different processing times are recorded.

Time management in the condition technique records all changes (for example, to commission contracts) that are made to condition records. This enables you to reconstruct old but valid versions that are no longer valid for the current period. You can thus ensure that there is time consistency between condition records.

It is possible to make retroactive changes in the condition technique as well as changes that are valid in the future. These changes are represented in the commission system by means of the validity periods.

The system does not create any change documents.

Integration

There is comprehensive documentation on Period and Version Management in the commission system.

Features

Period management in the condition technique takes into account the period analysis of a condition record. This means that a condition record can have different contents within its validity period due the changes made. Therefore it is possible to have different versions of a condition record since each change triggers a new version.

A new version of a condition record does not have to be effectively valid at the time of processing. For this reason, with every change a differentiation is made between the effective validity and the technical validity (processing time). If the effective validity is before the processing time, you are dealing with a retroactive change.

Object status and version status can have the following values:

	Version Status
Object Status		Active	Parked
	Valid	X	X
	Invalid	X	X

An object that has been flagged for deletion is given the Invalid object status and the version status Parked.

Changing a Condition Record

If new condition records are created for a certain period in the system, these overwrite the old statuses in the system from the same period of time. All older versions that are not in this period of time and are not overwritten are thus still valid. The condition records are overwritten by new ones in the database.

In the above example, three versions were created. The one that is valid on 05/15/03 and entered on 09/12/03 is version 2.

The object status is valid at all times and the versions are active at all times.

Deleting a Condition Record

An existing condition record is deleted in the system and given the Invalid object status. Old statuses are also overwritten in this case.

In the above example, two versions were created. Version two is used on 08/30/03 and has the status of 09/12/03, meaning that there is no condition record.

Parked Version of a Condition Record

A condition record that has the Parked status is ignored when the condition record is determined in the commission case. The one that is valid on 08/30/03 and entered on 09/12/03 is version 1.