Purpose
For all standard and individual conditions, this report checks whetherthe condition has:

• Validity periods with the same valid-from date and/or


• Overlapping validity periods.

If any such periods exist, the report corrects them.

Features
The system executes the following processes once for unbufferedconditions (table FICOT_CONDI) and once for buffered conditions(FICOT_CONDI_BUFF). Only undeleted records are affected.


• Validity periods with same valid-from date

The report identifies all condition records for which at least one otherrecord exists with the same valid-from date in the same condition. Themultiple records are transferred to an internal table.
For each condition, the report keeps the entry that has the latestrelease date for all validity periods with the same valid-from date.(The release dates are also set if no release is defined; the releasedates are then the same as the creation/change date).
Deleted status is assigned to all other entries. Deletedstatus is also assigned to the related item records (FICOT_POS orFICOT_POS_BUFF).

• Overlapping validity periods

The report identifies all condition records of each condition that haveoverlapping validity periods and transfers them to an internal table.
(Validity periods overlap if a period has a valid-to date that is afterthe valid-from date of another period for the same condition.)
If another period starts during the validity period of a record, thenthe valid-to date of the record is set to the calendar day before thevalid-from date of the other period.
If the simulation indicator is set, then no updates are made, rather alog of the incorrect records is issued that distinguishes betweenrecords with the same valid-from date and records with overlappingvalidity periods.

Selection
You can enter a range of contract IDs for the report. Report can also bestarted in parallel for different internal contract IDs.
A checkbox is used to control whether the report runs a simulation runor an update run.
If the checkbox is selected, then no changes are made in the database,rather a log of the incorrect records is issued.

Output
The report issues a log of all incorrect condition records. The log alsoissues the number of incorrect records (for a simulation) or changedrecords (for an update run).