x

The Instance Layer defines instances and dictionary entities, their relationships, and entity attributes defining the following logical data layers:

• L1 (for example, Canonical Layer) to store source data.
• L2 to store cleansed data.
• L3 to store match output information.

The following list describes the tabs found in an Instance entity.

• General. Basic definition of an instance entity: column names, properties, prefixes, descriptions, and so on.
• Matching. Matching process definition, including definition of additional columns.
• Advance Settings. Special types of columns with special behavior, such as independence on model importer and special features, to support match process and status calculations.

The following list describes the tabs found in a Dictionary entity.

• General. Basic definition of a dictionary entity: column names, properties, descriptions, and so on. It is designed for code book or a lookup type of entity. It has to be related to an instance entity using a 1:N relationship (dictionary entity is the parent).
• Advance Settings. Special (technical) types of columns with special behavior, such as independence on the model importer and special features.

The following list describes the tabs found in a Relationship.

• General. Basic definition of a relationship between two instance entities.

  Note: The relationship is oriented from a child to a parent entity (N:1). For example, it points from a child to a parent entity.

• Copy Columns from Parent to Child. Definition of attributes copied from the parent to the child entity.
• Copy Columns from Child to Parent. Definition of attributes copied from the child to the parent entity. Note that there is an N:1 relationship.

x

The Master Data Layers define one or more Master Data Layers.

Each Master Layer defines master andv (virtual) instance entities, their relationships, and entity attributes defining the L4 logical layer to store merged output (for example, golden or master records).

The following list describes the tabs of the Master Entity.

• General. Basic definition of master entities, such as columns names, properties, prefixes, descriptions, and so on.
• Advanced Settings. Special (technical) types of columns with special behavior, such as independence on the model importer and special features to influence merge process behavior.

The following list describes the tabs of the Instance entity.

• General. Basic definition of (virtual) instance entities such as link to the Instance Layer.

The relationship is the definition between two masters, master and instance, or instance entities.

Note: The relationship is oriented from a child to a parent entity (N:1), for example, it points from a child to a parent entity.

x

Reference data supports and automates reference data mastering. There are two types of reference data (also called dictionary):

• Translation. Used to translate source system-dependent codes to master codes (source system independent).
• Master. Used mainly for data providing to deliver additional information for the master code, such as master name and description(s).

Each definition automatically creates the following artifacts with a predefined structure (typical settings):

• A build plan to generate a lookup file and a Lookup step (usually applicable for a Translation dictionary).
• Entity definition, load operation, and a plan to load data in (usually applicable for a Master dictionary).

To deliver full functionality, reference data definitions have to be used on an Instance or Master entity.

Note: Sources have to be created in an external tool.

The following list describes the tabs of a Dictionary.

• General. Basic definition of each reference data dictionary, such as load and usage settings.
• Additional Columns. Definition of attributes that are added on top of the predefined ones.