Presupuesto del plan de merchandising para 5 años

Every reference data set (data table) or mapping that is created within

InfoSphere MDM Ref DM Hub has a default set of properties. These reference data set and mapping properties are defined by using reference data types. Every data set and mapping is associated with a data type definition.

The InfoSphere MDM Ref DM Hub system includes two basic data types, Default Reference Data Type and Default Mapping Type, which can be used to define a simple reference data set or mapping. An authorized user can create reference data types with additional properties to define more complex reference data sets or mappings.

Properties that are defined in a reference data type can be applied at the reference data set level, or at the value level for sets and mappings. At the value level, properties apply to all the rows of data in a data table or to all value mappings.

Reference data types have a data type property, which designates whether the reference data type is used to create reference data sets or mappings. After the reference data type is saved, its data type cannot be changed.

Business keys

Reference data types can be defined with compound keys. Up to four properties plus the code can be defined as constituent key parts of a unique reference data value key. Business keys apply only to reference data set data types; mapping set data types do not use business keys.

The business key feature is enabled for a reference data type in the Administration menu in the InfoSphere MDM Ref DM Hub UI. Selecting the business key check box for a reference data type is one way to ensure that the code for a reference data set is unique.

Chapter 1. Reference data management 29

InfoSphere MDM Reference Data Management Hub supports up to five

properties within a compound key for a set, where Key 1 is always the set code. The other four properties must have the Key property enabled within the reference data type definition.

Compound keys allow records with the same code to be saved, if the combined key is unique. The uniqueness check is done against the full key that is defined for the type. If the overall compound key is unique, the record can be stored. Importing values into a reference data set, defined as having a compound key, is the same as importing values into any other set. The same rules hold for the manual case: the key values cannot be null and the overall combination of keys and code must be unique for each value.

The business key check box and compound key definition can be applied for a reference data set with existing values if the values conform to the rules defined for the keys. The InfoSphere MDM Ref DM Hub checks for data integrity when the compound key settings for a reference data set type are changed, and does not allow actions that would create duplicate entries in the database where uniqueness is required.

Uniqueness is not enforced for the Code property unless the business key option is selected. Uniqueness is not enforced to support effective date-centric use cases that require multiple entries for the same code with different effective dates.

Reference data set data types

When you create a data type property of type Reference Data Set that points to a data set in the system, the options available must be from a current version of that set. A current version of the set is required to fill that property in a reference value.

The current version of a set is one that meets all of these conditions:

򐂰 The state is in an approved state for the lifecycle process or state machine.

򐂰 The effective date is the current date or earlier.

򐂰 The expiration date is after the current date.

Note: Name is also a required field for each reference value but is not used in

determining uniqueness of the compound key.

If more than one version meets these conditions, the most recent version is considered the current version.

Example

You create a reference data set named Countries, which contains reference values for country names. The status for the Countries data set is Approved. Its Effective date was last month, and its Expiration date is next year.

Next, you create a reference data type named Branches, which includes a Value Level property named Country. The data type for the Country property is

Reference Data Set, and its Related set is the Countries reference set. When you create a reference data set named Branches, basing it on the

Branches reference data type, the Country property is populated with the values from the Countries data set. Note that the Country property is populated with the values from the Countries data set only if the Countries data set has a current version.