Specifications

132 CHAPTER 7 Master Data Services
FIGURE 7-5 Attributes and validation issues
Business Rules
One of the goals of a master data management system is to set up data correctly once and to
propagate only valid changes to downstream systems. To achieve this goal, the system must
be able to recognize valid data and to alert you when it detects invalid data. In MDS, you
create business rules to describe the conditions that cause the data to be considered invalid.
For example, you can create a business rule that species the required attributes (also known
as elds) for an entity. A business entity is likely to have multiple business rules, which you can
sequence in order of priority, as shown in Figure 7-6.
FIGURE 7-6 The Product entity’s business rules
Figure 7-7 shows an example of a simple condition that identies the required elds for the
Product entity. If you omit any of these elds when you edit a Product member, MDS notes
a validation issue for that member and prevents you from using the master data model until
you supply the missing values.