Databases Reference
In-Depth Information
of a new contract, the MDM system user might first
configure the new guarantees needed by this contract, before
going on to configure it.
If only data tracking is used, it is not necessarily easy to
know that the update of the guarantees was made in the
context of the configuration of a contract. To overcome this
issue, the MDM system must include the concept of
“business transaction” which covers all updates that take
place in a certain scope, more precisely the context in which
it was used.
In our example, the MDM system should not see the
update of the contract as separate from the update of the
guarantees: the business transaction takes into account both
the updates to the contract and the guarantees. To obtain
this grouping, the MDM system passes the update date of
the business transaction to all the updates of business
objects involved at the heart of the transaction. In this way,
the updates to the contract and guarantees are given the
same time stamp. In this way, it is then easy to find all the
linked updates.
6.5.3.
Validity period
The validity period specifies at what moment the data is
valid. For example, a discount rate is only available during a
marketing campaign. The period can be limited to a start
date. For example, an option for a product is described in the
MDM system and becomes valid from a date fixed in
advance.
The same data element can be associated with several
periods of validity with different values according to
different periods. For example, a discount rate can be
different according to the year quarter and updated in
advance at the beginning of each year. A tariff calculation
