Dears,This is second part of my earlier blog where we will explore some more enhanced features of Oracle Customer Hub 8.2 v.
Data Relationship Management for Oracle Customer Hub – Advanced Customer Hierarchy Management
Advanced Customer Hierarchy Management is enabled within OCH through integration with Oracle Hyperion Data Relationship Manager (DRM). This expands hierarchy management capabilities with DRM‟s features made available for UCM accounts, account hierarchies and Dun & Bradstreet (D&B) hierarchies. In this advanced option, data stewards can create new hierarchies; drag and drop new account nodes into and out of a hierarchy; and compare, blend, merge, and delete hierarchies.
With OCH 8.2, users can also edit hierarchies within DRM by clicking the Advanced Hierarchy Management button. In a separate view, users select accounts from 3 places:
* UCM Account Hierarchies,
* UCM Accounts, and
* D&B Account Families.
Once selected, these hierarchies can be exported to DRM, where data stewards can use all DRM features for hierarchy management and manipulation. While working in DRM, data stewards can:
* Create hierarchies: using UCM accounts that were selected and imported into DRM.
* View hierarchies: UCM hierarchies can be browsed and compared to one another. Additionally, each account can be queried for and located across all hierarchies. Additional information on accounts within a hierarchy includes: siblings, parent, ancestors, children, descendants and links.
* Edit hierarchies: Data stewards can insert and remove UCM accounts from a hierarchy, drag and drop UCM accounts, and also delete, blend and merge hierarchies.
After performing changes in DRM, data stewards can return to OCH with the account hierarchies they had previously selected and sent to DRM. All changes in the selected hierarchies, as well as any newly created hierarchies in DRM, will be brought back to OCH upon committing a Save. This action also closes the DRM session, and purges all Hub data from the DRM application. Also, the modified hierarchies are versioned within OCH; in other words, the previous hierarchy version is stored as a History version and the updated hierarchy will be displayed as the current Customer Hub account hierarchy.
MDM Analytics
MDM Analytics dashboards enable data steward to quickly and proactively assess the quality of customer and contact dimensional data entering OCH. Through its ease of use, the dashboard accelerates the data‟s time-to-value and helps to drive better business results by:
1. Pinpointing where data quality improvement is needed;
2. Enabling the data stewards to take corrective action to improve the quality and completeness of the Customer and Contact data; and,
3. Helping to improve organizational confidence in the information.
Master Record Completeness Dashboard Page
The Master Record Completeness dashboard page presents the data steward(s) with a comprehensive view of their organization‟s Customer and Contact data completeness. The data steward(s) is able to quickly determine the state of their data quality and identify data entities. This helps to ensure that organizations have all of the necessary intelligence data to make correct business decisions.
Accuracy Dashboard Page The Accuracy Dashboard page presents the data steward(s) with a view of the activity against their Account and Contact in the system. This dashboard provides the data steward(s) the means to quickly highlight the Customer and Contact records in their system requiring additional attention.
List Import
Oracle OCH allows the business user to perform bulk import operations on Account and Contact records from external systems with easier error management. This functionality is now aligned with the List Import functionality of Siebel Marketing and can be deployed with or without mastering functionalities.
The configurable process allows the business user to import from the following file formats: Delimited text files (such as csv, tab delimited, fixed width, or other delimiter), and XML files. The automated process consists of two steps performed within OCH Administration screens and views: a list import into OCH SDH (Source Data History) tables, and then a batch process which calls existing OCH services for data cleansing, data matching and survivorship
OCH 8.2 delivers the following key benefits:
* Empowers business users to load data
o Configurable metadata driven approach
o Template driven approach
* Error resolution views
* List Import as a web service
Enhanced Stewardship OCH 8.2 Data stewardship capability has been enhanced to not only deliver richer set of features but also to provides a better user experience. The new enhancements and capabilities include:
· Enhanced Survivorship
o Rules Engine Based survivorship to define any rule beyond the seeded Rule Types. Survivorship rules are an automated means of controlling the quality of customer data stored in UCM. Out of the box, we support integration with Siebel Business Rules Engine (Haley) for Business logic based survivorship; integration with any other rules engine can be configured
o New Rule Types – Master and Slave in merge case. Master means the Survivor record selected by the user will win over the Victim record. Slave means the victim record selected by the user will win over the survivor record. In UCM connector case, when incoming request comes in, Master means the values stored in UCM will always win over the incoming record. Slave means the values sent by external application into UCM will always win over the values in the existing best version record.
o Configurable „Date Field enhancement enables customer to choose a different Date field other than the default “Updated” field as the comparison criteria when Recent/History comparison rules are executed.
o Household Survivorship can be configured
· Enhanced Merge/Un-Merge
o Guided Merge using Task Based User Interface allows end-user to review duplicate records and give ability to override the survivorship rules engine outcome in step by step process. Guided merge results in three versions of record in action and allows end user to decide how the final record version in the UCM should look like after the merge task is submitted for process
§ Survivor: The record whose row id will survive
§ Victim: The record that will be deleted
§ Suggested: Record generate as result of running through survivorship engine o Only supported for parent objects Account Contact
o Suspects – Incoming record posted to base table as Suspect awaiting Resolution. In previous UCM release, when a new incoming record is flagged as potential duplicate of existing records (manual review case), the new record is NOT created, and instead it is placed in the “Incoming Duplicates” views, waiting for data steward intervention. When Suspect Match feature is enabled, UCM will insert a new record for the manual review case and continue processing, while flagging the record for review later in “Existing Duplicates” views. Suspect record can be updated, deleted or merged via UI or incoming message. Data Steward can choose to approve suspect or can merge into an existing UCM record via Guided Merge or one step merge operation flag.
o Merge Request enhancement provide ability to submit merge request from edge systems using Web Services for two existing records. Synchronous response on the merge request status will be sent to the requestor, i.e. Pending, Rejected etc. Merge requests on records not existing in UCM database will be rejected.
o Enhanced Un-Merge User interface to list only previously merged records.
Data Relationship Management for Oracle Customer Hub – Advanced Customer Hierarchy Management
Advanced Customer Hierarchy Management is enabled within OCH through integration with Oracle Hyperion Data Relationship Manager (DRM). This expands hierarchy management capabilities with DRM‟s features made available for UCM accounts, account hierarchies and Dun & Bradstreet (D&B) hierarchies. In this advanced option, data stewards can create new hierarchies; drag and drop new account nodes into and out of a hierarchy; and compare, blend, merge, and delete hierarchies.
With OCH 8.2, users can also edit hierarchies within DRM by clicking the Advanced Hierarchy Management button. In a separate view, users select accounts from 3 places:
* UCM Account Hierarchies,
* UCM Accounts, and
* D&B Account Families.
Once selected, these hierarchies can be exported to DRM, where data stewards can use all DRM features for hierarchy management and manipulation. While working in DRM, data stewards can:
* Create hierarchies: using UCM accounts that were selected and imported into DRM.
* View hierarchies: UCM hierarchies can be browsed and compared to one another. Additionally, each account can be queried for and located across all hierarchies. Additional information on accounts within a hierarchy includes: siblings, parent, ancestors, children, descendants and links.
* Edit hierarchies: Data stewards can insert and remove UCM accounts from a hierarchy, drag and drop UCM accounts, and also delete, blend and merge hierarchies.
After performing changes in DRM, data stewards can return to OCH with the account hierarchies they had previously selected and sent to DRM. All changes in the selected hierarchies, as well as any newly created hierarchies in DRM, will be brought back to OCH upon committing a Save. This action also closes the DRM session, and purges all Hub data from the DRM application. Also, the modified hierarchies are versioned within OCH; in other words, the previous hierarchy version is stored as a History version and the updated hierarchy will be displayed as the current Customer Hub account hierarchy.
MDM Analytics
MDM Analytics dashboards enable data steward to quickly and proactively assess the quality of customer and contact dimensional data entering OCH. Through its ease of use, the dashboard accelerates the data‟s time-to-value and helps to drive better business results by:
1. Pinpointing where data quality improvement is needed;
2. Enabling the data stewards to take corrective action to improve the quality and completeness of the Customer and Contact data; and,
3. Helping to improve organizational confidence in the information.
Master Record Completeness Dashboard Page
The Master Record Completeness dashboard page presents the data steward(s) with a comprehensive view of their organization‟s Customer and Contact data completeness. The data steward(s) is able to quickly determine the state of their data quality and identify data entities. This helps to ensure that organizations have all of the necessary intelligence data to make correct business decisions.
Accuracy Dashboard Page The Accuracy Dashboard page presents the data steward(s) with a view of the activity against their Account and Contact in the system. This dashboard provides the data steward(s) the means to quickly highlight the Customer and Contact records in their system requiring additional attention.
List Import
Oracle OCH allows the business user to perform bulk import operations on Account and Contact records from external systems with easier error management. This functionality is now aligned with the List Import functionality of Siebel Marketing and can be deployed with or without mastering functionalities.
The configurable process allows the business user to import from the following file formats: Delimited text files (such as csv, tab delimited, fixed width, or other delimiter), and XML files. The automated process consists of two steps performed within OCH Administration screens and views: a list import into OCH SDH (Source Data History) tables, and then a batch process which calls existing OCH services for data cleansing, data matching and survivorship
OCH 8.2 delivers the following key benefits:
* Empowers business users to load data
o Configurable metadata driven approach
o Template driven approach
* Error resolution views
* List Import as a web service
Enhanced Stewardship OCH 8.2 Data stewardship capability has been enhanced to not only deliver richer set of features but also to provides a better user experience. The new enhancements and capabilities include:
· Enhanced Survivorship
o Rules Engine Based survivorship to define any rule beyond the seeded Rule Types. Survivorship rules are an automated means of controlling the quality of customer data stored in UCM. Out of the box, we support integration with Siebel Business Rules Engine (Haley) for Business logic based survivorship; integration with any other rules engine can be configured
o New Rule Types – Master and Slave in merge case. Master means the Survivor record selected by the user will win over the Victim record. Slave means the victim record selected by the user will win over the survivor record. In UCM connector case, when incoming request comes in, Master means the values stored in UCM will always win over the incoming record. Slave means the values sent by external application into UCM will always win over the values in the existing best version record.
o Configurable „Date Field enhancement enables customer to choose a different Date field other than the default “Updated” field as the comparison criteria when Recent/History comparison rules are executed.
o Household Survivorship can be configured
· Enhanced Merge/Un-Merge
o Guided Merge using Task Based User Interface allows end-user to review duplicate records and give ability to override the survivorship rules engine outcome in step by step process. Guided merge results in three versions of record in action and allows end user to decide how the final record version in the UCM should look like after the merge task is submitted for process
§ Survivor: The record whose row id will survive
§ Victim: The record that will be deleted
§ Suggested: Record generate as result of running through survivorship engine o Only supported for parent objects Account Contact
o Suspects – Incoming record posted to base table as Suspect awaiting Resolution. In previous UCM release, when a new incoming record is flagged as potential duplicate of existing records (manual review case), the new record is NOT created, and instead it is placed in the “Incoming Duplicates” views, waiting for data steward intervention. When Suspect Match feature is enabled, UCM will insert a new record for the manual review case and continue processing, while flagging the record for review later in “Existing Duplicates” views. Suspect record can be updated, deleted or merged via UI or incoming message. Data Steward can choose to approve suspect or can merge into an existing UCM record via Guided Merge or one step merge operation flag.
o Merge Request enhancement provide ability to submit merge request from edge systems using Web Services for two existing records. Synchronous response on the merge request status will be sent to the requestor, i.e. Pending, Rejected etc. Merge requests on records not existing in UCM database will be rejected.
o Enhanced Un-Merge User interface to list only previously merged records.
In my next blog we will see the Enhanced Data Quality and Integration Features that are available with OCH 8.2 V .
Your Partner and Companion
DC*
Hi...
ReplyDeleteAny idea of which all the companies use OCH 8.2