Databases Reference
In-Depth Information
6.6.2.
Integrity constraints
Integrity constraints are expressed in the data model.
They are automatically taken into account by the MDM
system at the time of data validation.
It is possible to distinguish three types of integrity
constraint: enumerations, referential integrity constraints
and business states.
6.6.2.1.
Enumeration
An enumeration lays down that the value of a data
element is retrieved from a list of pre-established values. For
example, the color of a product is selected from a list (red,
green, blue). This list is itself a master data element.
Consequently it benefits from the same governance functions
as versions or use contexts. In this way it is possible to
define different lists of color by context. At the time of
choosing a color for a product, the MDM system displays the
list according to the management of use contexts. For
example, if the context corresponds to geographical zones,
updates can be language dependent: [
red
,
green
,
blue
], [
rot
,
grün
,
blau
], etc.
We have already seen that the contexts are not described
in the data model. The governance functions of the MDM
system allow us to configure more contexts dynamically,
provided that we have the appropriate permissions.
6.6.2.2.
Referential integrity constraints
Referential integrity constraints are expressed in the data
model through associations between business objects. For
example, if a Product is attached to at least one Factory, it
appears in the data model as a “one to many” relationship
(1.n) between product and factory. At the time of entry or
update of a product, the MDM system forces the user to
attach at least one factory code to it.
