Exception Management Guide

10.5.5
- 10.5.4
- 10.5
- 10.4.0

Back Next

Bad Records Example

You are a data steward at a retail organization. You are concerned that the product inventory records might contain errors. The errors might cause the organization to order more products or fewer products than it can sell.

You define the following process to investigate and correct the errors:

You ask a developer to configure one or more mappings to find and fix the errors in the data set.

The mappings also calculate a numeric score for each record in the data set. The scores represent the data quality of the records. Some records have marginal scores that indicate that the mappings cannot verify all of the data quality issues that the records contain.

The developer configures an additional mapping that reads the numeric scores. The developer adds the mapping to a workflow that includes a Mapping task and a Human task.

The Mapping task runs the mapping. The Mapping task writes the records to different tables based on the scores that they contain.

The Human task distributes the records with marginal scores to tasks that you and other users can open in the Analyst tool.

You log in to the Analyst tool, and you open a task. The task organizes the exception records in one or more tables. Each table can contain 100 records.

You perform one the following actions on each record:

You correct the errors in the record, or you decide that the current record is correct.

You update the record status to indicate that the record is valid.

You determine that the record does not contain any valid data.

You update the record status to indicate that the record is not valid.

You decide that you cannot verify the accuracy of the record.

You update the record status to indicate that the record needs further analysis by another user or by another Informatica process.

Before you update a record, verify that the task is open in edit mode. To enter edit mode, click the

Edit

button in the open task.

When you finish work on all of the records in the task, you update the task status. The task status indicates that the records are ready for the next stage in the data quality process.

The next stage for the data depends on the configuration of the Human task. For example, the Human task might include additional steps that assign the records to other users for review.

Rename Saved Search

Table of Contents

Exception Management Guide

Exception Management Guide

Bad Records Example

Bad Records Example