Cross-System DQ - Orphan Keys Rule – Help Center

Introduction

The "Orphan Keys" rule identifies a situation where a group of records of a particular type exists in one system but is absent in another system where it should also be present, categorized by their shared attributes or types.

For instance, shipments designated for Customer X might be recorded in one system, but not included in another system's list of shipments organized by customer. Also, Product Category B could be listed among shipments, yet it doesn't appear in the list of products. This discrepancy points to a mismatch in data synchronization or categorization between the systems.

In summary, the Orphan Keys rule reveals differences between datasets in various systems, underlining the importance of organizing data consistently across different platforms.

For further information about the rule detail page including scope, threshold, notifications, etc., please see the detailed article Rule Detail page.

Detailed Steps:

Step 1: Access Data Dictionary

Step 2: Select Table & Available Rules

Select the table name then select the Data Quality tab and choose Available Rules.

Step 3: Add a New Rule (Cross-System DQ → Orphan Keys)

Select the "⊕ Add Rule" button, then choose the "Cross-System DQ" category. From the list of options, click on "Orphan Keys"

Step 4: Basic Input Setup<></>

In the Rule Wizard's Basic Input section, you need to fill in the Rule Description, Column name, Reference source, Reference table and reference column name corresponding to the table in which you want to search for the orphan records.

Step 5: Validate & Run the Rule

After saving the rule, you'll see its definition. Click "Run" to execute and test the rule.

Cross-System DQ - Orphan Keys Rule

In this Article

In this Article

Introduction

Detailed Steps:

0 Comments