- Revision History
- Overview
- Feature Summary
-
- Customer Data Management
-
- Address Cleansing Now Supports Multi-Select
- Use Import and Export Management to Create, Update, Delete, and Export the Customer Hub Person Entity
- Provide Support for Importing Additional Attributes Using the Hub Organization Import Object
- Manage Generic Source System Object Using REST APIs
- Use Organization REST Resource to Manage Generic Organization Data
- Use Person REST Resource to Manage Generic Person Data
-
- Customer Data Management
- IMPORTANT Actions and Considerations
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 |
|---|---|---|---|
| 17 DEC 2020 | Provide Support for Importing Additional Attributes Using the Hub Organization Import Object | Updated document. Revised feature information. | |
| 18 SEP 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 |
|
||
Provide Support for Importing Additional Attributes Using the Hub Organization Import Object |
||||||
Use Organization REST Resource to Manage Generic Organization Data |
||||||
Address Cleansing Now Supports Multi-Select
Select multiple address cleansing results and collectively accept or reject them at once. Currently, as a data steward, you have to select each address cleansing result within a batch individually and click the Accept or Reject button. You can now use the multi-select check boxes to select more than one address cleansing result at a time.
This enhancement provides a fast and efficient way for data stewards to quickly dispose of cleansed address results.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
See the Cleanse Addresses chapters in these guides:
Role Information
- Data Steward
Use Import and Export Management to Create, Update, Delete, and Export the Customer Hub Person Entity
Create, update, delete, and export comprehensive person profiles that are used as the common basis for many types of person entities, such as contacts.
With this enhancement, you can use a single import or export format to manage the generic person profile information shared by multiple person object types.
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 for CX Sales and B2B Service guide.
Role Information
- CRM Administrators
- Data Stewards
These roles have import authority and can access this new HubPerson Entity through standard Import Management processes.
Provide Support for Importing Additional Attributes Using the Hub Organization Import Object
Additional attributes are now available in the field definition of the Hub Organization import object to help integrate it with geography name referencing. The newly added fields are:
- ThirdPartyFlag
- ValidatedFlag
- CleanlinessScore
- CompletenessScore
- DataConfidenceScore
- DatafoxCompanyId
- DuplicateIndicator
- DuplicateScore
- EnquiryDuns
- EnrichmentScore
- LastScoreUpdateDate
- RecencyScore
- ValidityScore
This feature provides consistency and full functionality, with appropriate field support and integrations.
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 for CX Sales and B2B Service guide.
Role Information
Roles that have access to APIs or have access to the HubOrganization import object have the new fields available.
Manage Generic Source System Object Using REST APIs
You can use REST APIs to create, update, delete, and get the new Generic Source System object. The Generic Source System object identifies the information cross-referenced to existing source systems and base tables, including the source of the data and its date parameters, status, and Source System IDs. Essentially, the Generic Source System object maintains cross references between various external source systems and the base master system.
This feature gives you full support of source system identifiers and makes it easier to maintain source cross references.
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.
Tips And Considerations
A known issue exists with the Upsert API. If you have trouble in your environment with this API, use the Patch API instead.
Key Resources
See the Source System References task in the REST API for CX Sales and B2B Service guide.
Role Information
Customer administration and development roles have access to use these REST APIs, as needed, for customer integrations.
Use Organization REST Resource to Manage Generic Organization Data
Use the REST resource based on the generic Organization object to manage organization data.
This feature provides functionality in the new Import and Export Management framework that used to exist in the File-Based Import framework.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Plan to use the generic hubOrganization for import and integration to external systems when the organization being referenced is not a sales-related organization. For example, the organization could be from a financial system, an HR system, a partner organization, or a marketing organization.
- You need an active license for Oracle Customer Data Management.
Key Resources
See the Organizations task in the REST API for CX Sales and B2B Service guide.
Role Information
Users with the Data Steward and CRM Administrator roles have authority to execute import activity and web service REST APIs for the generic hubOrganization object.
Use Person REST Resource to Manage Generic Person Data
Use the REST resource based on the generic person object to manage person data. You can also use this resource to import person data through the import REST APIs.
This feature provides functionality in the new Import and Export Management framework that used to exist in the File-Based Import framework.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- The hubPerson is a generic object that allows a multitude of external systems to import person based data into Customer Hub. All create, update, delete APIs are available for processing data. With this feature customers can move to standard import processing and move away from classic import.
- You need to have a license for Oracle Customer Data Management to use this feature.
Key Resources
See the Person task in the REST API for CX Sales and B2B Service guide.
Role Information
Data Stewards and CRM Administrators have the authority to access the import facility and all REST APIs for this hubPerson object.
IMPORTANT Actions and Considerations
This section includes details about additional changes that might change the way your products work.
DEPRECATED FEATURES
From time to time, Oracle deprecates existing Cloud service features. This section identifies the features in this Cloud service that have been deprecated.
| Deprecated Feature | Deprecation Target | Additional Information |
|---|---|---|
| Address Duplicate Identification Configuration on the Manage Enterprise Data Quality Match Configuration Page |
21A |
This deprecated configuration will be hidden in 21A. The visibility of this configuration is controlled by the profile option ORA_ZCQ_ENABLE_ADDR_MATCH_OBJECT. Hiding this deprecated configuration helps avoid confusion and avoids the use of the configuration by mistake. If the deprecated configuration is already active in your application environment, then the configuration continues to be visible and active. Address records are child objects of organization (account) and person (contact). As such, we recommend that you perform the address duplicate identification as part of the organization and person duplicate identification process. |