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 JUN 2021 | 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:
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. |
Customer Must Take Action 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 |
|
||
Make Historical Data Available to Attribute Survivorship Processing During Updates |
||||||
Reconfigure Address Cleansing Parameters Before Submitting an Address Cleansing Job |
||||||
Use D&B Attribute Mapping for Account and Contact Batch Enrichment |
||||||
Review the Effects of Attribute Survivorship on Updates
Use the Organization and Person Profile History pages to review which field updates were accepted or rejected based on the application of attribute survivorship logic. With this enhancement, each profile history entry lists the names of the attributes whose values changed during the update operation. The history also lists the names of the attributes whose values didn't change because the survivorship rules determined that the incumbent value was of higher quality than the new value. The enhanced Profile History page lets you easily differentiate between changes that were accepted per survivorship logic versus those changes that were accepted because survivorship was not configured for those attributes.
See Which Field Updates Were Accepted or Rejected
These enhancements to the Profile History page provide transparency and auditability for master records when survivorship rules have been applied to updates. The enhancements are useful for the testing and validation of survivorship-on-update processing logic.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
These enhanced Profile History pages show the effects of survivorship on updates made by both REST and Import Management interfaces.
Role Information
Any user who has access to the Organizations and Persons pages can use these enhancements. In particular, the enhancements were designed to support the duties of users with these job roles:
- Customer Data Steward
- Data Steward Manager
- Master Data Management Application Administrator
Make Historical Data Available to Attribute Survivorship Processing During Updates
Synchronize historical data with the attribute survivorship processing during update operation. This feature lets you build the attribute source change history for a newly configured attribute.
Synchronize Historical Data
This feature increases the reliability and accuracy of survivorship on update logic by making relevant attribute change history information available to the survivorship framework when new attributes are added to the source confidence setup.
Steps to Enable
To use this feature, follow these steps:
- Click Navigator > My Enterprise > Setup and Maintenance work area.
- Go to the Manage Source System Confidence task by selecting the offering as Customer Data Management and the functional area as Customer Hub.
- Add new attributes to your source confidence configuration as dictated by your customer data management process.
- After saving your new source confidence configurations, click the Synchronize button on the Manage Source System Confidence setup page.
- Accept the default recommended synchronization time frame or specify your own.
- Click the Submit button to launch the synchronization job.
Tips And Considerations
- The synchronization process is only needed when source confidence is configured for a new attribute the first time. For example, adding a third source system to an attribute that already has source confidence setup for two source systems doesn't require synchronization.
- The synchronization module analyzes your setup data and calculates the data window for synchronization based on when the source system was enabled. You can override this value based on personal knowledge of when a field started being used, or any other potential optimizations you may be aware of.
- Even if you choose not to synchronize the history of a newly added attribute, the attribute source change history will still be tracked going forward.
Key Resources
- See the "Duplicate Resolution Setup" chapter in the Implementing Customer Data Management for CX Sales and B2B Service guide.
Role Information
This feature is available to users with the Master Data Management Application Administrator role.
Reconfigure Address Cleansing Parameters Before Submitting an Address Cleansing Job
Fine-tune the address cleansing configuration parameters such as Minimum Verification Level and Minimum Verification Score prior to submitting an address cleansing job. The default configuration continues to be defined in the Setup and Maintenance task, Manage Address Cleansing Configurations, but this feature allows additional tuning of these parameters at each batch job level.
As a data steward, you can now reconfigure the address cleansing configuration parameters for a specific address cleansing job by overriding the address cleansing parameter settings for the application. As a data steward, you control the address cleansing batch job configuration because the configuration parameters can be tuned while creating a batch job. You can fine-tune your batch jobs without affecting other batch jobs that are submitted by other data stewards, or without changing the default configuration applicable for all batch jobs.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See the "Cleanse Addresses" chapter in the Using Customer Data Management for CX Sales and B2B Service guide.
Use D&B Attribute Mapping for Account and Contact Batch Enrichment
Use Account and Contact Enrichment by Dun & Bradstreet (D&B) attribute mapping for batch enrichment of account and contact data in Customer Data Management. Also, you can now map predefined Account and Contact Enrichment by D&B attributes to all attributes available from Dun & Bradstreet.
If you're a user of Account and Contact Enrichment by D&B who uses batch enrichment, you can now leverage custom attribute mappings and map key attributes, such as competitor, using this new mapping.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
See this content:
- "Configure Oracle DaaS and Oracle DataFox for Data Enrichment" chapter in the Implementing Customer Data Management for CX Sales and B2B Service guide
- "Enrich Data" chapter in the Using Customer Data Management for CX Sales and B2B Service guide.