- Revision History
- Overview
- Feature Summary
-
- Customer Data Management
-
- Use REST Resources to Identify Duplicate Organization and Person Records
- Display the Match Rule Name on the Duplicate Identification Page
- Use Address Locale Object in Import Management
- Use REST APIs to Track Status of Bulk Export Jobs
- Delete Child Records for Inactive or Merged Parent Records
- Use New Exportable Attributes to Analyze Duplicate Resolution Data
-
- Customer Data Management
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 18 DEC 2020 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.
Column Definitions:
Features Delivered Enabled
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Action is Needed BEFORE Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Use REST Resources to Identify Duplicate Organization and Person Records |
||||||
Display the Match Rule Name on the Duplicate Identification Page |
||||||
Use New Exportable Attributes to Analyze Duplicate Resolution Data |
||||||
Use REST Resources to Identify Duplicate Organization and Person Records
Use the Customer Hub Organization and Customer Hub Person REST resources to determine whether external customer records have matching records in the Customer Data Management registry.
You can use this feature to enable external customer record creation processes to check whether matching records already exist in the Customer Data Management registry. By replicating the same type of interactive duplicate identification process that's provided by the standard Customer Center interface's integration with the Data Quality solution, external processes can avoid creating duplicate records.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
All roles that have access to the base Person and Organization resources can use this enhancement.
Display the Match Rule Name on the Duplicate Identification Page
Display the match rule name that helps identify duplicate records on the Duplicate Identification page. Seeing the match rule name helps you better understand how the defined match rules are applied so that you can find potential duplicate records. The match rule name helps you to identify applicable rules, tune them, and observe the effects of those changes.
Knowing which rules are being applied makes it possible for you to fine tune them. You can fine tune match rules and test the effects of rule changes in the duplicate identification result sets. The display of the match rule name simplifies the validation of the match configuration and lets data stewards easily understand why a duplicate set was formed while reviewing resolution requests.
Steps to Enable
The Match Rule column is hidden by default. To expose the Match Rule column:
- Navigate to the Duplicate Identification Batch page from the Customer Data Management springboard.
- Drill down the Duplicate Identification Batch page for a specific record.
- In the Duplicate Sets table, click the Duplicate ID.
- On the details screen, select Match Rule from View > Columns menu.
- Click Done.
The Match Rule name column is now visible in the Duplicate Set details screen.
Tips And Considerations
For the Driving Record in a batch duplicate set, the Match Rule name column is blank because a match rule is not applied to identify a driving record.
Key Resources
See the information on submitting duplicate requests in the "Identify Duplicates" chapter in the Using Customer Data Management for CX Sales and B2B Service guide.
Role Information
- Sales Administrator
- Master Data Management Application Administrator
- Application Implementation Consultant.
Use Address Locale Object in Import Management
You can now use the Address Locale object to provide transliterated address details. The Address Locale object is a child object of the Address object in Import Management and REST APIs.
The Address Locale record holds a 1-to-1 mapping to the Address record.
Transliterated values can be stored and managed for address records and provide the support required for localization.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
See the "Import Your Data" chapter in the Understanding Import and Export Management guide.
Use REST APIs to Track Status of Bulk Export Jobs
You can now use the Export Activities REST API to track the completion of bulk export jobs. The export jobs raise business events when completed.
This feature supports integration developers using Oracle Integration Cloud or any other integration engines. You can track the completion of bulk export jobs created through REST APIs, and notify the users when a preregistered condition is met without repetitive polling. This avoids the wastage of resources because of any repetitive polling process.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
You can configure and register your REST end point to receive notification whenever your import job completes. To receive an import completion notification through REST services, you must define the REST service end point in Application Composer.
Key Resources
See the "Export Your Data" chapter in the Understanding Import and Export Management guide.
Delete Child Records for Inactive or Merged Parent Records
Delete child objects and related entities when the parent record is in an inactive or merged status. When you delete parent record like account, contact, household, hub person or hub organization from UI pages, webservices or file import, all child entities like contact points, relationships, address, source system references and so on are not deleted automatically. Now you can perform delete operation by running batch job manually or schedule it on a regular basis.
You should be able to inactivate all related child entities for the already inactivated parent party record. This resolves data integrity concerns and prevent export of child records of inactive parent records using Export Management.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
To delete the records, run the scheduled process Delete Child Entities of Inactive Party Records.
Here are the supported parameters:
- Date range: Provide the date range to process all party records based on when they were inactivated or merged.
- Party ID: Used to process the specific party record based on the party identifier.
- Party Number: Used to process the specific party record based on the Party Number.
Key Resources
See the "Sales and B2B Service Scheduled Processes" chapter in the Understanding Scheduled Processes guide.
Role Information
- Sales Administrator
- Master Data Management Application Administrator
Use New Exportable Attributes to Analyze Duplicate Resolution Data
Analyze the nature and lifecycle of the duplicate resolution request data using new export attributes. You can use the newly added fields on the Resolution Request export and REST object to support reporting requirements. To conduct operational analysis of the data stewardship process, you need access to information about the nature and lifecycle of the Resolution Request object. This enhancement increases the amount of information available in the Resolution Request export object to better support a wider range of reporting requirements. New fields on the Resolution Request export and REST object have been added, to support reporting use cases.
The new fields improve reporting and integration capabilities for these use cases:
- End User Analysis: Understand which individuals and sales organizations are submitting resolution requests as they use Accounts, Contacts, and Households or other custom interfaces that let non-Data Steward users create resolution requests.
- Customer Data Audit: Conduct detailed audits of the customer data objects selected in merge requests and fully document the pre-merge and then the post-merge shape of the customer records.
- Operations Research: Conduct operations research on resolution request backlog management, request dispositions, aging, and productivity.
To support these end-user analyses, the Resolution Request export and REST API object includes user identities that allow joins to be formed with HZ (Person profile), MOT (Territories), Source System References, and JTF (Resources) product areas. Attributes added are:
- RequestedById
- RequestedBy
- AssignedToId
- AssignedTo
- SubmittedById
- SubmittedBy
- SubmittedDate
- ReviewRequiredFlag
- HasBeenReviewedFlag
- RuleBasedMasterFlag
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
After upgrade, the new attributes are automatically available in the REST resolutionRequests resource object, and in the export object, Duplicate Resolution Request.
Role Information
- Sales Administrator
- Master Data Management Application Administrator
- Application Implementation Consultant