Table of Contents

Search

  1. Preface
  2. Using Metadata Manager
  3. Viewing Metadata
  4. Searching Metadata
  5. Working with Shortcuts and Folders
  6. Editing Metadata
  7. Working with Data Lineage
  8. Sharing Metadata
  9. Business Glossaries
  10. Using the URL API
  11. Configure the Web Browser
  12. Glossary

Metadata Manager User Guide

Metadata Manager User Guide

Differences between Impact Summary and Related Catalog Objects

Differences between Impact Summary and Related Catalog Objects

When you view details for a metadata object in the metadata catalog, the impact summary and related catalog objects display different information.
The impact summary lists all high-level objects, such as tables and reports, that impact and are impacted by the metadata object that you are viewing. The impact summary does not list lower-level objects such as columns and data attributes. Objects in the impact summary have a data flow relationship with the object that you are viewing.
Related catalog objects have a direct association with the metadata object that you are viewing. The association can represent a data flow relationship between the objects or a non-data flow relationship such as a primary-key to foreign-key relationship between columns in relational tables. Related catalog objects can be high-level or lower-level objects.
For example, a PowerCenter resource contains mapping m_EmailPromo. The mapping reads from Oracle table CUST, filters the customer data, and writes the filtered data to flat file TargetedCustomers.csv. The mapping is used in PowerCenter session s_EmailPromo. Workflow wf_EmailPromo runs the session.
When you view mapping m_EmailPromo in the metadata catalog, you see the following metadata details:
Related Catalog Objects
Lists PowerCenter Session task instance s_EmailPromo because there is a direct association between the mapping and the Session task instance.
The related catalog objects does not list Oracle table CUST or flat file TargetedCustomers.csv because they are related to objects within the mapping. Oracle table CUST is related to the source definition instance within the mapping. Similarly, flat file TargetedCustomers.csv it is related to the target definition instance within the mapping.
Impact Summary - Downstream
Lists flat file TargetedCustomers.csv because data flows from the mapping to this high-level object.
Impact Summary - Upstream
Lists Oracle table CUST because data flows from this high-level object into the mapping.

0 COMMENTS

We’d like to hear from you!