Oracle Customer Hub (UCM) Master Data Management Reference > Using Oracle Data Governance Manager >

Scenarios for Using Oracle Data Governance Manager

This topic describes how Oracle Data Governance Manager might be used. You might use Oracle Data Governance Manager differently, depending on your business model. It includes the following scenarios:

• Using Data Governance Home Page
• Using Data Governance Master Data Module (Data Steward)
• Consolidating Records in Oracle Data Governance Manager
• Viewing and Fixing Rejected Records in Oracle Data Governance Manager
• Viewing and Fixing Multiple Rejected Records in Oracle Data Governance Manager
• Consolidating Completed Records in Oracle Data Governance Manager (Data Steward)
• Manually Reviewing Suspect Records in Oracle Data Governance Manager (Data Steward)
• Manually Reviewing Completed Records in Oracle Data Governance Manager
• Viewing Graphs of All Records That Were Part of Batch Jobs
• Cleansing Records in Data Governance Manager

Using Data Governance Home Page

A data steward logs in to Oracle Data Governance Manager and views the home page. From the home page, the data steward can choose from five modules: Master, Govern, Share, Cleanse, and Consolidate. The data steward drills down on the details of the five modules to perform data governance tasks. A login screen validates the user ID and password. Data access is determined by the views already set up in Oracle Customer Hub (UCM).

Using Data Governance Master Data Module (Data Steward)

From the home page, the data steward clicks the Master section to view the activity records on mastered records in Oracle Customer Hub (UCM). The Master Data section displays a summary of the mastered account and contact records for each day, week, month, and all options, which query against all data in Oracle Customer Hub (UCM) Server. The results are displayed graphically.

Consolidating Records in Oracle Data Governance Manager

From the home page, the data steward clicks the Consolidate section. From the Consolidate screen the data steward can view all batch jobs with the related statistics run within a defined period, such as the past hour, day, week, year, and so on.

Viewing and Fixing Rejected Records in Oracle Data Governance Manager

From the home page, the data steward clicks the Consolidate section. From the Consolidate screen the data steward clicks the Rejected Records pie chart from a batch report to view all rejected records from that batch job. If the data steward finds a record that was rejected by mistake, corrections can be made from this view, and the fixed records are saved when the batch job is rerun. Additionally, the data steward might update multiple batch records at once.

Viewing and Fixing Multiple Rejected Records in Oracle Data Governance Manager

From the home page, the data steward clicks the Consolidate section. From the Consolidate screen the data steward clicks the Rejected Records pie chart from a batch report to view all rejected records from that batch job. If the data steward finds a record that was rejected by mistake, corrections can be made from this view, and the fixed records are saved when the batch job is rerun. Additionally, the data steward might update multiple batch records at once.

Consolidating Completed Records in Oracle Data Governance Manager (Data Steward)

From the home page, the data steward clicks the Consolidate section and views records processed by a batch job. The data steward can view the total number of inserted and updated records from the batch process.

Manually Reviewing Suspect Records in Oracle Data Governance Manager (Data Steward)

The Suspect Record Details allows the data steward to choose whether records in the queue are duplicates. From this screen, the data steward can either merge two duplicate records or create a new record. The data steward can then approve or merge the records. To approve means that the two suspect records are processed as separate records. To merge means the data steward considers the two records to be the same and merges them during the next batch process.

Manually Reviewing Completed Records in Oracle Data Governance Manager

Following a manual merge process the Batch Import screen is displayed. From this screen, the data steward can read the flat file structures and start the batch import processes. Oracle Customer Hub (UCM) Web services enable batch template files to be pulled from Oracle Customer Hub (UCM). After the data steward chooses the template choice, the data steward can view the content of the subsequent data file before importing the data in to Oracle Customer Hub (UCM). Following review of the data, the data steward clicks the Import button. Any errors during the file parsing are captured in an error table that can then be reviewed and acted upon by the data steward.

Viewing Graphs of All Records That Were Part of Batch Jobs

A data steward logs in to Oracle Data Governance Manager and views the home page. From the home page, the data steward chooses the Share module. The Share screen allows the data steward to view a graphical representation of all records that were part of batch jobs using the following criteria: modified, unmerge, and merge.

Cleansing Records in Data Governance Manager

From the Data Quality screen, the data steward can monitor the integrity of Oracle Customer Hub (UCM) data through the Completeness metric. Data completeness is measured at both the master records level and at the source system level. The data steward can click each node from the system list to view details about the incomplete data from each node.