Example: Period-Managed Master Data (SAP Library

Example: Period-Managed Master Data

(Two-dimensional period management.)

The following example explains the functional scope of period management for master data. It shows when new versions of a contract (for example, an insurance contract, mobile phone contract) are created and how the versions replace each other.

Actions that create new policy versions:	Version
The commission contract is created on 15.01.98. It is to begin retroactively on 01.01.98 and be valid until 01.01.99.	1
A change is made on 15.02.98, which is to come into effect on 01.04.98.
Version 1 of the commission contract must be replaced by a new version that differs to version 1 in terms of time only.	2
The contract change came into force from 01.04.98. This change is to remain valid until the end of the contract.	3
Another change is made on 12.09.98, which is to be retroactively effective from 01.08.98. Three new contract versions are then created, and only one of these is effectively and technically valid.
As every version must have its own continuance, a new version is produced for Version 2 that does not differ temporally or effectively from Version 2.	Stays as 2
The temporal validity of version 3 is changed by the amendment.	4
The contract change came into force from 12.09.98. This change is to remain valid until the end of the contract.	5

Example: the commission contract was changed on 12.09.98, with retroactive effect from 01.08.98. During commission settlement on 14.09.98, the retroactively changed version of the contract was used as the basis to determine the remuneration amount, although the change was only made after the start of the commission.

If the settlement had taken place on 10.09.98, the remuneration would have been calculated based on version 3. A retroactive change to the policy means that commission settlement has to be repeated for all commissions calculated between 01.08 and 12.09.98.