Filter objects to reduce the complexity of the data lineage diagram. For example, you run data lineage analysis on a relational table to determine which columns are used in business intelligence reports. The relational table is created from a PowerCenter mapping, and the mapping has multiple sources. Because you do not need to know how the table is created, you can filter the PowerCenter mapping. When you filter the mapping, Metadata Manager removes the mapping and the mapping source objects from the data lineage diagram.

Alternatively, you view a data lineage diagram that contains many objects that are linked to business glossary terms. You do not need to view the business terms to complete your analysis. You can use a filter to remove all of the business terms from the diagram.

When you filter an object, Metadata Manager removes the filtered object from the data lineage diagram. Metadata Manager also removes the upstream or downstream objects that are in the same data path as the filtered object.

For example, you run data lineage analysis from a PowerCenter mapping with the following lineage:

Microsoft SQL Server table → PowerCenter mapping* → Oracle table → Business Objects report

If you filter the Oracle table, Metadata Manager removes the Oracle table and the downstream Business Objects report from the data lineage diagram.

Metadata Manager does not remove the upstream or downstream objects if they are in the data path of other objects.

You can filter any lineageable object in the data lineage diagram except for the source object, its parent objects, or its child objects.

Metadata Manager retains the filters for the data lineage diagram when you close and reopen the diagram within the same session. Metadata Manager also retains filters when you navigate through generations and when you switch between the summary and detail views. If you refresh the data lineage diagram, Metadata Manager removes all filters.