Tables and Columns

You can perform impact analysis on tables and columns, using the Mapping Specification grid, and analyze its impact as source and target.

This topic walks you through the steps to view impact analysis of a table. Similarly, you can view impact of columns, systems, and environments.

A table can be a source, target, or both in a mapping specification. It can also be used for transformations, such as business rules and lookups in a mapping project. The impact analysis on a table helps you identify these impacts of the table on mapping projects.

To view impact analysis at table level, follow these steps:

Go to Application Menu > Data Catalog > Mapping Manager.
In the Workspace Mappings pane, click the required mapping.
The Mapping Specification grid appears.
Select a row.
Right-click system or environment and hover over Impact Analyzer Report.
The options available for Impact Analyzer Report appear.
Click Default Search (All Projects).
Impact analysis of the table appears.
It displays the asset hierarchy, sensitivity data indicator (SDI) classification, data quality analysis, and table's impact based on related assets in your metadata.
On the Tables tile, click Upstream.
The upstream dependencies of the table appears in a grid format.

Similarly, you can view downstream dependencies on the Downstream tab.
On the Upstream or Downstream tab, click an asset to view its lineage or impact analysis. For more information on running lineage analysis on assets, refer to the Running Lineage Analysis topic.

Use the Other Impacts tile, and click one of the following to view them:

Business rules
Source Extract SQL
Lookups

For example, the image below displays the In Lookups tab with lookup conditions that impacts the asset type. Also, you can switch between In Source Extract SQL and In Business Rules tabs to view relevant impacts.

You can also view the upstream and downstream dependencies of other impacted assets from selected tablet's perspective. For example, the image below displays upstream column dependencies from the table's perspective.