Databases Reference
In-Depth Information
If necessary, the MDM system allows us to set up a
specific governance function which is not available to all
users, which nullifies all or part of the referential integrity
constraints. This might prove necessary to facilitate the
entry of certain data or the time of automatic data load. The
MDM system has, in addition, a function through which a
report detailing all the cases where the referential integrity
constraints of the database have not been respected.
The data cardinality is also managed in the form of
master data in the MDM system. This allows the referential
integrity constraints to be customized with a simple
parameterization, according to the use contexts, without
modifying the data model.
6.6.2.3.
Business states
In the previous chapter, dedicated to the maturity model
of the MDM system, we have already mentioned the
importance of the modeling of the lifecycle of the business
objects and the use of the business states to enforce data
validation rules. The objective is to prevent forbidden data
updates due to the business objects' states' values. These
states are also master data elements. A decision table is put
in place, for each business object, which allows us to specify
the constraints through the states which affect the data
updates: this table details the data of the business object
which can be modified for each state.
The entry of the decision tables happens in the same way
as for other master data. Consequently, it is possible to allow
several different updates for the same decision table,
according to the versions and use contexts which have to be
taken into account.
At the time of update of a business object, the MDM
system automatically uses the decision table for this object
in order to validate the update requested. This decision table
