oracle · 2018-07-11 · nokia geography reference data: ... oracle customers that have purchased...

OracleCustomer Data Management CloudGetting Started with Your CustomerData Management Implementation

Release 13 (update 18B)

Oracle Customer Data Management CloudGetting Started with Your Customer Data Management Implementation

Release 13 (update 18B)Part Number E94228-02Copyright © 2011-2018, Oracle and/or its affiliates. All rights reserved.

Author: Jesna Narayanan

Contributor: Tracie Felker, Virinder Kaur, Ashwini Malthankar, Nandakishore Palasala, Parth Shah, Abhishek Sura, Vijay Tiwary, Jiri Weiss,

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected byintellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, ordecompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them tous in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then thefollowing notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulationand agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operatingsystem, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictionsapplicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use inany inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. OracleCorporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks orregistered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks ofAdvanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. OracleCorporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, andservices unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for anyloss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreementbetween you and Oracle.

The business names used in this documentation are fictitious, and are not intended to identify any real companies currently or previously in existence.

Oracle Customer Data Management CloudGetting Started with Your Customer Data ManagementImplementation

Contents

Preface i

1 About this Guide 1Purpose and Scope .................................................................................................................................................. 1

Audience ................................................................................................................................................................... 1

How to Use This Guide ............................................................................................................................................ 1

What You Will Be Able to Do After Completing the Setups in This Guide .................................................................. 1

2 Signing In and Performing Preliminary Setup Tasks 3Preliminary Setup Tasks: Overview ........................................................................................................................... 3

Signing In for the First Time ...................................................................................................................................... 3

Familiarizing Yourself with Useful Toolbar Icons ........................................................................................................ 3

Accessing Setup Tasks ............................................................................................................................................ 4

Enabling the Customer Data Management Offering for Implementation ..................................................................... 5

Verifying the Need for Additional Licenses ................................................................................................................ 6

Enabling Quick Access to Setup Tasks .................................................................................................................... 7

3 Setup Task Overview 9Prerequisites for Setting Up the Customer Data Management Cloud Service ............................................................ 9

Setup Tasks Completed for You in Oracle Customer Data Management Cloud Service ........................................... 10

Setup Task Summary ............................................................................................................................................. 11

4 Creating Setup Users 15Setup Users Creation .............................................................................................................................................. 15

About Creating Setup Users ................................................................................................................................... 16

Creating a Job for Provisioning Setup Users ........................................................................................................... 20

Creating the Provisioning Rule for Setup Users ....................................................................................................... 21

Creating Setup Users .............................................................................................................................................. 22

Designating a Single User to Receive All Credential E-Mails .................................................................................... 23

Granting the Initial User the Same Privileges as Other Setup Users ......................................................................... 24

Resetting User Passwords ...................................................................................................................................... 24


5 Creating Customer Data Management Application Users 27Application Users Creation: Overview ...................................................................................................................... 27

Creating Customer Data Management Application Users ........................................................................................ 27

6 Setting Up Geography Data 29Geography Setup: Overview ................................................................................................................................... 29

Specifying the Geography Data Supplier: Procedure ............................................................................................... 31

Importing Geography Reference Data ..................................................................................................................... 31

GBG | Loqate Geography Reference Data: Explained ............................................................................................. 33

Nokia Geography Reference Data: Explained .......................................................................................................... 34

Importing Third Party Geography Data Using File Based Import .............................................................................. 37

Setting Up Geocoding and Address Cleansing ....................................................................................................... 38

Setting Up Geography Validation ............................................................................................................................ 39

Turning on Validation for Address Import ................................................................................................................ 43

7 Importing Accounts and Contacts Using Import Management 45About Import Management ..................................................................................................................................... 45

Importing Your Data ................................................................................................................................................ 49

8 Importing Accounts and Contact Using File-Based Import 57Account and Contact Import .................................................................................................................................. 57

About Importing Accounts and Contacts ................................................................................................................ 59

About Importing Addresses for Accounts and Contacts .......................................................................................... 60

Exporting Account Owner Party IDs ........................................................................................................................ 63

Specifying the Industry Classification for Accounts .................................................................................................. 63

Downloading Templates for Importing Accounts and Contacts ............................................................................... 64

Understanding the Account Import Template .......................................................................................................... 65

Understanding the Contact Import Template .......................................................................................................... 69

Researching Additional Account and Contact Attributes for Import ......................................................................... 73

Creating a New Mapping for a Changed Import Template ...................................................................................... 74

Importing the Accounts and Contacts Files ............................................................................................................ 75

Troubleshooting Common Import Errors ................................................................................................................. 76

9 Importing Accounts and Contacts Using Simplified View Import Objects 79Importing Data Using Simplified View Import Objects: Overview .............................................................................. 79

Importing Contacts Using the Contact - Simplified View Import Object: Procedure .................................................. 79

Importing Accounts using the Account - Simplified View Import Object: Procedure ................................................. 91


10 Configuring Profile Options 105Customer Hub Profile Options Setup: Overview .................................................................................................... 105

Managing Customer Hub Profile Options .............................................................................................................. 107

11 Configuring Address Verification 109Address Verification: Setup Overview .................................................................................................................... 109

Managing Server Configurations for Cleansing ...................................................................................................... 110

Configuring the Address Verification Cloud Service ............................................................................................... 110

Managing Enterprise Data Quality Cleansing Configurations .................................................................................. 112

Setting Up Address Cleansing and Address Validation .......................................................................................... 117

Enabling Search Mode for Address Verification Cloud Service .............................................................................. 120

12 Configuring Duplicate Identification 123Duplicate Identification: Setup Overview ................................................................................................................ 123

Managing Server Configurations ........................................................................................................................... 123

Managing Enterprise Data Quality Matching Configurations ................................................................................... 124

Mapping Matching Attributes ................................................................................................................................ 125

Managing Key Generation: Explained .................................................................................................................... 126

Selecting Sources of Match Rules and Scoring: Points to Consider ...................................................................... 127

Managing Custom Match Rules and Scoring: Explained ....................................................................................... 128

Creating Custom Match Rules: Procedure ............................................................................................................ 128

13 Configuring Duplicate Resolution 131Duplicate Resolution: Setup Overview ................................................................................................................... 131

Managing Source System Confidence .................................................................................................................. 132

Managing Survivorship Rules ................................................................................................................................ 132

Defining Survivorship Rules ................................................................................................................................... 133

Defining Set Master Record Rules ........................................................................................................................ 136

Defining Set Attribute Value Rules ......................................................................................................................... 145

Managing Agreement Rules .................................................................................................................................. 152

Defining Agreement Rules ..................................................................................................................................... 153

Running the Request Dispatch Job ...................................................................................................................... 155

High Volume Batch Deduplication: Best Practices and Guideline .......................................................................... 155

Purging Duplicate Resolution Data: Explained ....................................................................................................... 158


14 Configuring Data Enrichment 159Configuring Social Data and Insight Cloud Service for Data Enrichment and Address Verification: Overview ........... 159

Creating a DaaS User and Assigning Role: Procedure .......................................................................................... 160

Configuring Integration to Data Cloud: Procedure ................................................................................................. 161

15 Configuring Automerge 163Automerge: Setup Overview ................................................................................................................................. 163

Understanding How Records are Selected for Automerge .................................................................................... 164

Implementing Automerge ...................................................................................................................................... 164

16 Integrating Customer Data Management with Other Cloud Services 167Customer Data Management Cloud Integration Approaches: Explained ................................................................ 167

Merge Operation Process During Integration Cloud Service Based Integration: Explained ...................................... 169


Preface

i

PrefaceThis preface introduces information sources that can help you use the application.

Using Oracle Applications

Using Applications HelpUse help icons to access help in the application. If you don't see any help icons on your page, click your user imageor name in the global header and select Show Help Icons. Not all pages have help icons. You can also access OracleApplications Help.

Watch: This video tutorial shows you how to find help and use help features.

You can also read Using Applications Help.

Additional Resources

• Community: Use Oracle Cloud Customer Connect to get information from experts at Oracle, the partnercommunity, and other users.

• Guides and Videos: Go to the Oracle Help Center to find guides and videos.

• Training: Take courses on Oracle Cloud from Oracle University.

ConventionsThe following table explains the text conventions used in this guide.

Convention Meaning

boldface Boldface type indicates user interface elements, navigation paths, or values you enter or select.

monospace Monospace type indicates file, folder, and directory names, code examples, commands, and URLs.

> Greater than symbol separates elements in a navigation path.

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website.

Videos included in this guide are provided as a media alternative for text-based help topics also available in this guide.

https://fusionhelp.oracle.com/

https://fusionhelp.oracle.com/

https://apex.oracle.com/pls/apex/f?p=44785:265:0::::P265_CONTENT_ID:10552

https://apex.oracle.com/pls/apex/f?p=44785:265:0::::P265_CONTENT_ID:10552

http://www.oracle.com/pls/topic/lookup?ctx=cloud&id=OACPR2531440

https://appsconnect.custhelp.com/

http://docs.oracle.com/

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=906

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc


Preface

ii

Contacting Oracle

Access to Oracle SupportOracle customers that have purchased support have access to electronic support through My Oracle Support. Forinformation, visit My Oracle Support or visit Accessible Oracle Support if you are hearing impaired.

Comments and SuggestionsPlease give us feedback about Oracle Applications Help and guides! You can send an e-mail to:[email protected].

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

mailto:[email protected]


Chapter 1About this Guide

1

1 About this Guide

Purpose and ScopeThis guide describes how to get started with the implementation of Customer Data Management cloud service capabilitiessuch as duplicate identification, duplicate resolution, address verification, and data enrichment. This guide uses the defaultsettings provided by Oracle and does not provide detailed explanations of all available features.

This document supplements standard product documentation, which you are encouraged to review. To find documentationand other learning resources, such as guides, white papers, and videos, visit the Help Center for Oracle Customer DataManagement Cloud.

Related Topics

• Oracle Customer Data Management Cloud

AudienceThis document is for Oracle customers (System Integrators, Sales Consultants) and Support involved in implementation of theCustomer Data Management Cloud Service. The tips and techniques detailed in this document may not be suitable for an on-premise deployment.

How to Use This GuideHere's how to use this guide:

• Use the Setup Task Overview chapter to get an overview of the tasks covered in this guide.

• Read the brief Setup Overviews at the beginning of each chapter to understand the setups the chapter covers. Usethe Setup Overview as a guide to the setups you must perform. The remaining topics in the chapter provide thestep-by-step details of how to perform each of those setups.

• Refer to other guides for full explanation of the different features and options.

What You Will Be Able to Do After Completing the Setupsin This GuideAfter completing the setups in this guide, you should be able to:

• Identify duplicates:

◦ Identify potential duplicate account, contact, and address records in real time when your application userscreate a customer record, thus preventing entry of duplicate records.

http://docs.oracle.com/cloud/latest/?tab=2


Chapter 1About this Guide

2

◦ Identify potential duplicates using batch processing for records already in the database or potential duplicatesof the records in the database within an import batch

◦ Identify duplicates during import of customer data for records already in the database.

• Resolve duplicates: Consolidate the identified duplicates by merging or linking them.

• Verify addresses: Cleanse an address to confirm to postal requirements and verify that the address is an actualpostal address.

• Enrich Data: Enrich account and contact data to ensure it's comprehensive


Chapter 2Signing In and Performing Preliminary Setup Tasks

3

2 Signing In and Performing Preliminary SetupTasks

Preliminary Setup Tasks: OverviewBefore you start implementing your Customer Data Management application according to the instructions in this guide, youmust complete the preliminary tasks listed in the following table.

Step Description Where to Get More Details

Complete the Service Administrator ActionList

Complete the actions listed in the ServiceAdministrator Action List provided by Oracle

See Signing In for the First Time topic in thischapter.

Enable the Customer Data Managementoffering for implementation

Enable the Customer Data Managementoffering for implementation in the Setup andMaintenance work area.

See the Enabling the Customer DataManagement Offering for Implementationtopic in this chapter.

Ascertain that you have the required licenses

Verify that you have all the additional licensesrequired for your implementation of theCustomer Data Management capabilities.

See the Verifying the Need for AdditionalLicenses topic in this chapter.

Install the CDM Implementation Project

Install the CDM implementation project intoyour environment to speed up your access tothe implementation tasks. You can download the implementationproject from support. oracle.com and uploadit into your environment.

See the Enabling Quick Access to SetupTasks topic in this chapter.

Signing In for the First TimeAs part of your Oracle Sales Cloud Service, you are provisioned two Customer Data Management Cloud environments,production and test. When your test environment is ready, Oracle sends a Welcome e-mail to the person designated as theService, Account, and Identity Domain administrator when you signed up with the Oracle Customer Data Management Cloud.

The Welcome e-mail to the administrator for the Oracle Customer Data Management Cloud contains all the details aboutyour test and production environments, login credentials, and an Action List. Before you sign in for the first time, read theenvironment access e-mail, complete the tasks in the Service Administrator Action List, and familiarize yourself with thedifferent user interfaces and basic navigation.

Related Topics

• Service Administrator Action List

http://download.oracle.com/tutorials/docs/Service-Administrator-Action-List.pdf



4

Familiarizing Yourself with Useful Toolbar IconsThe topic lists the most useful tool bar icons in the applications home page.

The following figure lists the tool bar icons.

1 2

3

4

5

The following table lists the functions of the tool bar icons in the application home page.

Callout Number Icon Name Function

1

Navigator

Opens the Navigator.

2

Home

Returns you to the simplified UI springboard.

3

Favorites and Recent Items

Marks a page as favorite and providesaccess to recently viewed pages.

4

Show Help

Turns on contextual help.

5

This icon displays the user name.

Clicking the user name on the toolbar, opensthe Settings and Actions menu. From themenu, you can sign out, and personalize theUI, access help, and navigate to the Setupand Maintenance work area.

Accessing Setup TasksYou perform setup tasks in the Setup and Maintenance work area and in other work areas of the application. This topicexplains the different ways of accessing these setup tasks.



5

Speeding Up Access to Setup Tasks Using the Implementation ProjectYou gain faster access to the setup tasks covered in the Getting Started with Your Oracle Customer Data ManagementCloud Implementation guide by downloading and installing an implementation project provided by Oracle. The implementationproject complements the structure of this guide and provides a direct link to each core setup task.

If you do not use the implementation project, then you must navigate to each individual task separately. Depending on thetask, you must either search for the task by name in the Setup and Maintenance work area or navigate to a different workarea using the Navigator.

Searching for Setup Tasks in the Setup and Maintenance Work AreaYou can also search for individual tasks by name in the Setup and Maintenance work area. Use the percent sign (%) torepresent missing letters or words. For example, to find the Manage HCM Role Provisioning Rules task, you can search formanage HCM % rules. The searches are not case-sensitive.

Navigating to Other Work Areas for SetupWhen you are not using the implementation project, you can use the Navigator to access other work areas involved in setup.You can open the Navigator by clicking its icon in the toolbar.

The Navigator, shown in the following figure, lists all of the application work areas that are available based on the permissionsassigned to each user, rather than on the features you have purchased. Because a setup user has a broad range ofpermissions, not all of the selections are applicable to your setup. Aside from the Setup and Maintenance work area, you useonly a small number of the available work areas accessible from the Navigator menu. The most important of these include:

• My Team

◦ Users, Roles and Delegations

Use this work area for creating and managing individual users in the UI. The Users, Roles and Delegations taskin the Setup and Maintenance work area opens the same work area.

• Tools

◦ Scheduled Processes

Use this work area for scheduling and monitoring background processes. The Scheduled Processes workarea is not available when you first sign in as the initial user. You must grant yourself the additional privilegesas described in this guide.

◦ Application Composer

Use Application Composer to configure and enhance your application.

• Customer Data Management

Use the different work areas under this heading for functional setup and to create data used to test your CustomerData Management application.

Note: The Customer Data Management Cloud Service uses File-Based Data Import. The Data Importfunctionality that lets you import data in bulk is available only for an on-premise implementation.



6

Enabling the Customer Data Management Offering forImplementationBefore you start work, you must enable the functional areas of the Customer Data Management Cloud that you are going touse for implementation. Enabling the different areas makes it possible for you to track the progress of your implementationfrom within the Setup and Maintenance work area and, in some cases, even turn on applicable features and UI regions. Youcan enable only the functional areas you are implementing now and, if required, add more later on.

To enable the functional areas:

1. Navigate to the Setup and Maintenance work area.2. Click the Customer Data Management offering icon.3. Click Configure.

The Configure Customer Data Management page appears.4. Select the Enable for Implementation option, highlighted in the preceding figure, for the functional areas you are

setting up. For the implementation of Customer Data Management documented in this guide, select Define DataQuality, Define Customer Hub Configuration, and Customer Data Management Business Intelligence Analytics.

5. Click Actions and select Go to Offerings.

You are returned to the Setup and Maintenance page.

Verifying the Need for Additional LicensesYou can only enable the functional areas for which your company has purchased licenses.

Customer Data Management is shipped free of cost with some Oracle Cloud Services such as Oracle Sales Cloud. An OracleSales Cloud license provides you access to the following customer data management functionality:

• Customer Data Management Dashboard

• Data Steward Productivity Tools

• File-Based Import and Data Import

• Manual Merge and Auto-Merging

• Survivorship and Agreement Rules

• Audit Reporting

• Link and Relate

• Account Hierarchy Management

To make use of the all the capabilities of the Customer Data Management Cloud Service, you require the following additionallicenses:

• Oracle Fusion Data Quality Cloud Service: This service enables you to identify potential duplicates records in thedatabase or potential duplicates of the records in the database within an import batch. You can use this servicefor both real-time and batch duplicate identification. Note that a standalone customer of the Customer DataManagement Cloud Service must purchase the Oracle Fusion Data Quality Cloud Service because both the cloudservices are sold together.



7

• Address Verification Cloud Service: This service enables you to cleanse an address to conform to postalrequirements and verify that the address is an actual postal address.

• Oracle Social Data and Insight Cloud Service: This service enables you to enrich account and contact data to ensureit is comprehensive.

Enabling Quick Access to Setup TasksThe Oracle Customer Data Management Cloud: Getting Started with Your Implementation guide describes how to speedup your initial setup using an implementation project supplied by Oracle. The implementation project serves as a launch padfor many of the setup tasks covered in this guide, so you don't have to search for individual setup tasks or navigate to workareas, including the scheduled processes.

Downloading the Implementation Project to Your DesktopDownload the implementation project to your desktop from the Oracle Customer Data Management Cloud: Getting Startedwith Your Implementation: Implementation Project (Doc ID 2211294.1) available on support.oracle.com.

There are two variations of the implementation project that you download depending on how much functionality you want toset up:

• Quick Setup Basic Customer Data Management: Use this implementation project for setting up the customer datamanagement functionality shipped with Oracle Sales Cloud:

◦ Customer Data Management Dashboard

◦ Data Steward Productivity Tools

◦ File-Based Import and Data Import

◦ Manual Merge and Auto-Merge

◦ Survivorship and Agreement Rules

◦ Audit Reporting

• Quick Setup Customer Data Management Cloud Service: Use this implementation project to set up all thecapabilities of the Customer Data Management cloud service, acquired through the following additional licenses:

◦ Oracle Fusion Data Quality Cloud Service: This service enables you to identify potential duplicates recordsalready in the database or potential duplicates of the records in the database within an import batch. You canuse this service for both real-time and batch duplicate identification.

◦ Address Verification Cloud Service: This service enables you to cleanse an address to confirm to postalrequirements and verify that the address is an actual postal address.

◦ Oracle Social Data and Insight Cloud Service: This service enables you to enrich account and contact data toensure it is comprehensive.

The Getting Started with Your Oracle Customer Data Management Cloud Implementation guide covers the tasks in bothvariations.

Installing the Implementation Project You DownloadedInstall the implementation project by uploading the configuration package file using these steps:

1. Navigate to the Setup and Maintenance work area.



8

2. Click the Tasks menu icon.3. Click the Manage Configuration Packages link.

The Manage Configuration Packages page appears.4. Click Upload.

The Upload Configuration Package page appears.5. Click Browse and select the compressed file with the implementation project you downloaded.6. Click Get Details.

Click Done on the Manage Configuration Packages page.7. Click Submit.

The application displays a message that the import is successful and the implementation project was created.8. Click OK to close the message window.9. Click Done on the Manage Configuration Packages page.

You are returned to the Setup and Maintenance work area page.10. Click Implementation Projects.

The Implementation Projects page appears listing your project.11. Click the name link to open the implementation project.

Using the Implementation Project As a Launchpad for Your TasksFollow these steps to use the implementation project as the launchpad for your implementation tasks.

1. Navigate to the Setup and Maintenance work area by clicking the icon on the springboard.

The Setup and Maintenance page appears.2. Click Implementation Projects.

The Implementation Projects page appears listing your project.3. Click the name link for the project.

The implementation project displays the folders containing the individual tasks in the Task Lists and Tasks region.4. Click a folder to open it and click the Go to Task icon for a task. This icon is highlighted in the preceding figure.

When you complete a task, you are returned to the project.


Chapter 3Setup Task Overview

9

3 Setup Task Overview

Prerequisites for Setting Up the Customer DataManagement Cloud ServiceThe prerequisites for setting up the Customer Data Management Cloud Service can be broadly grouped into two categories,prerequisite implementation decisions and additional licenses.

Prerequisite Implementation DecisionsYou have the following two options for setting up the Customer Data Management Cloud Service:

• Standalone Implementation: You want to use Oracle Customer Data Management Cloud Service individually oralong with a non-Oracle cloud services. The Getting Started with Your Customer Data Management Implementationguide describes all the setup steps required for a standalone implementation of the Oracle Customer DataManagement Cloud Service. However, to use the Customer Data Management Cloud Service with a non-Oraclecloud service, you will have to set up that non-Oracle cloud service separately.

• Add-on Implementation: You want to use the Oracle Customer Data Management Cloud Service with anotherOracle cloud service, such as Sales Cloud. Details for this implementation option can be found in the respectiveGetting Started guide for your other Oracle cloud service. For example, if you want to use Customer DataManagement Cloud Service with Sales Cloud you should see Getting Started with Your Sales Cloud Implementationin the Help Center.

Note that the implementation tasks may vary slightly depending on the implementation option that you select.

Prerequisite Additional LicensesCustomer Data Management is shipped free of cost with some Oracle Cloud Services such as Oracle Sales Cloud. An OracleSales Cloud license provides you access to the following customer data management functionality:

• Customer Data Management Dashboard

• Data Steward Productivity Tools

• File-Based Import and Data Import

• Manual Merge and Auto-Merging

• Survivorship and Agreement Rules

• Audit Reporting

However, to make use of the all the capabilities of the Customer Data Management cloud service, you require the followingadditional licenses:

• Oracle Fusion Data Quality Cloud Service: This service enables you to identify potential duplicates records already inthe database or potential duplicates of the records in the database within an import batch. You can use this servicefor both real-time and batch duplicate identification.

• Address Verification Cloud Service: This service enables you to cleanse an address to confirm to postal requirementsand verify that the address is an actual postal address.



10

• Oracle Social Data and Insight Cloud Service: This service enables you to enrich account and contact data to ensureit is comprehensive.

Note that a standalone customer of the Customer Data Management Cloud Service must also purchase the Oracle FusionData Quality Cloud Service, because these two cloud services are always sold together.

Setup Tasks Completed for You in Oracle Customer DataManagement Cloud ServiceSetup Tasks Completed for You in Oracle Customer Data Management Cloud When Oracle provisions a Customer DataManagement Cloud Service environment, we generally set up some basic information about your company that you providewhile signing up for the service. This initial setup includes company name, corporate address, legal entity, business unit,corporate currency, and the creation of an initial user. You can verify the values using the tasks provided in this topic. You canreach the tasks directly from the implementation project provided by Oracle, or by searching for the tasks in the Setup andMaintenance work area.

Note that if you are setting up Oracle Customer Data Management Cloud Service together with another cloud service suchas Oracle Global Human Resources Cloud, Oracle Procurement Cloud, and Oracle Financials Cloud, then Oracle does notcomplete any of these tasks in your environment. In such shared Global Single Instance (GSI) environments, you must set upenterprise structures, such as legal entity and business unit, in the other cloud services according to the instructions providedin their respective implementation guides. All guides are available on docs.oracle.com.

The following table lists the information that are pre-entered by Oracle on your environment while setting up your cloudservice.

What Oracle Enters for You Description Setup Task Name

Your company name

Access this task to view the Oracle enteredcompany name based on the information youprovided.

Manage Enterprise HCM Information

Your corporate address

This is the address you provided. As a bestpractice, use the same legal corporateaddress used for tax information. To reviewand edit the address, you must search forthe address first by the country where it islocated. If you do make any changes, thenyou must remember to click Save and Closefor the changes to be saved.

Manage Legal Addresses

A legal entity When you create a user who is an employee,

you must specify the legal entity listed in thistask. In the Create User UI, the legal entity iscalled the Legal Employer.

The legal entity name Oracle enters for youis your enterprise name followed by the suffix

Manage Legal Entity HCM Information



11

What Oracle Enters for You Description Setup Task Name

LE. Follow these steps to verify the legalentity name:

1. On the Manage Legal Entity HCMInformation page, click Advanced toaccess the Advanced Search page.

2. In the Legal Entity Name field, changethe Start with operator to Containsand enter LE as the search parameter.

3. Click Search.

Creates a business unit and sets thebusiness unit as the default.

Oracle creates one business unit for creatingyour employee users. The business unitname is your enterprise name followed by thesuffix BU. Oracle then sets the profile optionHZ_ DEFAULT_ BU_CRM to that businessunit.

Manage Common CRM Business Unit ProfileOptions

In addition, Oracle creates one user for you. This is the initial user you received in the welcome e-mail. The initial user isprovisioned with the following job roles:

• Application Implementation Consultant

• IT Security Manager

• Application Diagnostic Administrator

The initial user can create other users, change security settings, and perform many, but not all, implementation tasks. Theuser is not provisioned with all the security permissions required to complete the setups in this guide, but has the ability toassign these roles to herself and to others. For example, the initial user does not have the permission to set up search andrun and monitor scheduled processes.

Setup Task SummaryThe following table summarizes the setups covered by this guide and the setup tasks that you use to carry them out.

You can access most of the setup tasks from a folder in the implementation project you downloaded. For tasks that are not inthe project, you must navigate to specific work areas or tasks described in the following table.

Implementation Step Setup Description Task Names Implementation Project Folder

Create Setup Users

Grant yourself the additionalprivileges that you need tocomplete the setups in this guideand create any additional usersto help you with setup. Setup users are not part of yourresource organization. Theycan be systems integrators youhired for the implementation, forexample.

• Manage Job• Manage HCM Role

Provisioning Rules• Manage Users

Create Setup Users

Create Application Users

Create a few application usersto test your setups. You need to

Manage Users

Create Customer DataManagement Application Users



12


ensure that the provisioning rulesyou created work as intended.

Import Geographies

Import geography reference datafor the countries where you dobusiness and set up validationfor required address elements.This step is required to validateaddresses. You must enforce validation foraddresses you import, by settingthe profile option GeographyAddress Validation Enabledto Yes using the ManageAdministrator Profile Values task.

• Manage Geographies• Manage Administrator

Profile Values

Set Up Geography Data

Importing Account, Contact, andother Customer information

Get ready to import accountsand contacts by:

• Registering theapplication that's thesource of your accountand contacts data

• Exporting the Party IDs ofthe sales resources youcreated earlier

• Specifying whichindustry classificationcategory you are using bysetting the profile optionMOT_INDUSTRY_CLASS_CATEGORY.

Import your accounts andcontacts from a file usingtemplates you can downloadand modify.

• Manage TradingCommunity SourceSystems

• Schedule Export Process• Manage Administrator

Profile Values• Manage File Import

Mappings• Manage File Import

Activities

Import Accounts and Contacts

Configure Profile Options

Review and update profileoptions to optimize theimplementation of the CustomerData Management Cloud Serviceaccording to your businessrequirements.

Manage Customer Hub ProfileOptions

Define Customer HubConfiguration

Configure Address Verification This step includes address

cleansing and addressverification setup. Addresscleansing is a process thatcorrects, parses, and completesaddress data based on postalrequirements.

Address verification requires aseparate license for the AddressVerification Cloud Service. Thisservice enables you to cleansean address to conform to postal

• Manage ServerConfigurations

• Manage EnterpriseData Quality CleansingConfigurations

• Manage Sales Cloud toData Cloud Integration

• Manage AdministratorProfile Values

• Manage Geographies

Define Data Quality



13


requirements and verify thatthe address is an actual postaladdress.

You can set up addressverification by:

• Enabling the serverconfigurations forcleansing

• Configuring the addressverification cloud service

• Managing enterprisedata quality cleansingconfigurations

• Defining addresscleansing and addressverification

Configure Duplicate Identification Complete this set up to identify

duplicates in the followingsituations:

• Identify potential duplicateaccount, contact, andaddress records inreal-time when yourapplication users createa customer record. Thisprevents the entry ofduplicate records.

• Identify potentialduplicates in batch modefor records already in thedatabase or within thebatch file itself.

• Identify duplicates duringimport of customer datafor records already in thedatabase.

Duplicate identification uses theEnterprise Data Quality (EDQ)service. You require a separatelicense for the Data QualityCloud Service.

You can set up duplicateidentification by:

• Enabling the serverconfigurations formatching

• Manage ServerConfigurations

• Manage EnterpriseData Quality MatchingConfigurations




14


• Setting up EnterpriseData Quality matchingconfigurations

Configure Duplicate Resolution Complete the following set up

to consolidate duplicates bymerging or linking them:

• Defining source systemconfidence

• Creating appropriatesurvivorship and mergeagreement rules

• Manage Source SystemConfidence

• Manage SurvivorshipRules

• Manage Customer HubProfile Options

• Manage Agreement Rules• Run Request Dispatch

Job


Configure Auto Merge

Set up the automergefunctionality to merge duplicaterecords through automatedprocessing without any approvalor intervention from the datasteward.


• Define Survivorship• Define Data Quality

• Define Customer HubConfiguration

• Define Data Quality

Note that the implementation steps may vary slightly depending on the implementation option that you select, standaloneimplementation or add-on implementation. However, the following implementation tasks are common to all options:

• Configure Profile Options

• Configure Address Verification

• Configure Duplicate Identification

• Configure Duplicate Resolution

• Configure Auto Merge


Chapter 4Creating Setup Users

15

4 Creating Setup Users

Setup Users CreationThe initial user created for you by Oracle is configured to perform the security tasks, which include the creation of other usersand the granting of additional privileges. After you have signed in for the first time, you are ready to provide yourself withadditional privileges and to create other users who will help you with application setup. This chapter assumes that the usersdoing the setup are not resources who are part of the resource organization. However, there is nothing stopping you fromproviding setup privileges to users who are.

The following table lists the setup tasks to create setup users. The topic About Creating Setup Users provides the conceptualoverview of creating setup users. Detailed steps are provided in procedures in this chapter. You can access all tasks from theCreate Setup Users folder in your implementation project.

Step Description Task Name Where to Get More Details

Create a job for ProvisioningSetup Users

Create a job, Customer DataManagement Administrator,which you can later assign to allusers who are performing setupand are not part of your resourceorganization. What you name the job doesn'tmatter. You use the job only as acondition in the rule to provisionsetup users with the permissionsthey require to complete allsetups.

Manage Job

See Creating a Job forProvisioning Setup Users topic inthis chapter.

Create a rule to provision roles tothat job

Create a role provisioning rulethat automatically provisionsthe following job roles to allusers with the Customer DataManagement Administrator job:

• ApplicationImplementationConsultant

• IT Security Manager• Application Diagnostic

Administrator• Master Data Management

Application Administrator

Manage HCM Role ProvisioningRules

See Creating the ProvisioningRule for Setup Users topic in thischapter.

Create setup users andassociate the job and roles tothem.

Create each setup user as auser of type employee with theCustomer Data ManagementAdministrator job and associatethe job and roles to them.

Manage Users

See Creating Setup Users topicin this chapter.



16


Grant the Initial User the SamePrivileges as Other Setup Users

Grant yourself, the initial user,the same additional privileges theother setup users have by editingthe initial user profile.

Manage Users

See Granting the Initial User theSame Privileges as Other SetupUsers topic in this chapter.

About Creating Setup UsersAlthough the initial user can perform many of the setup tasks in this guide, this user cannot perform all of them withoutadditional privileges. For example, the initial user cannot run scheduled processes, including the geography import task andindexing for searches.

About Security and the Initial Setup TasksOracle follows the industry standard Role Based Access Control approach to security. In Oracle Applications Cloud, theprivileges are bundled in:

• Job roles, which correspond to the jobs that the person is doing in your organization.

• Abstract roles, which permit users to carry on tasks that are common to all employees or resources.

For example, the Sales Manager job role makes it possible for a user to perform all of the sales manager duties, such asreviewing sales team performance and approving forecasts. The Employee abstract role adds the ability to access reportsand manage personal profile information. The Resource abstract role makes it possible for a user to be assigned as a salesresource to accounts and opportunities.

To perform the initial setup tasks mentioned in this guide, you must provision users with all the job roles granted to the initialuser. These job roles are:

• Application Implementation Consultant (job role)

Provides access to all the setup tasks across all products.

• IT Security Manager (job role)

Provides access to the security tasks, including the ability to assign other enterprise roles.

• Application Diagnostics Administrator (job role)

Provides access to the diagnostic tests and data.

In addition, you may also provision them with:

• Employee (abstract role)

Provides access to BI reports and the ability to run and monitor background processes.

• Master Data Management Application Administrator

Permits the setup user to perform the same functional setups as a customer data management administrator.

• Customer Data Steward (job role)



17

Performs customer data management activities including data import, cleansing, duplicate identification, andduplicate resolution. In addition, the Customer Data Steward can perform the following few tasks in the Setup andMaintenance work area:

◦ Manage Organization Party Tree

◦ Manage Person Party Tree

◦ Manage Group Party Tree

◦ Manage Customer Data Hub Note Descriptive Flexfields

• Data Steward Manager (job role)

Manages customer data stewards and has additional privileges including assigning requests. In addition, theCustomer Data Steward can perform the following few tasks in the Setup and Maintenance work area:

◦ Manage Organization Party Tree

◦ Manage Person Party Tree

◦ Manage Group Party Tree

◦ Manage Customer Data Hub Note Descriptive Flexfields

To perform the initial setup tasks in this guide using the initial user, you must provision these additional roles to yourself aswell.

In Oracle Customer Data Management Cloud, you provision job roles and abstract roles to users using role provisioning rules.If users meet the conditions of the rule, the application provisions them with the job roles and abstract roles that you want to



18

assign to the user. The following figure shows how the role provisioning rule conditions must be met to provision the job rolesand abstract roles.

Abstract Role

Role Provisioning RuleCondition 1

Condition 2...

Job Role1

User

Job Role 2

The role provisioning rules you use to provision customer data management application users and the initial setup users havedifferent conditions.

Provisioning Customer Data Management Application UsersYou provision job roles to customer data management users, including data steward managers and customer data stewardbased on the role the user plays in the resource organization. This resource role is the job title which appears under the username in the Resource Directory.



19

The following figure shows resource directory page with the resource role appearing as job tittle under the user namehighlighted with the callout 1.

1

Special Provisioning Rule for Setup UsersBecause users doing the initial setup aren't part of your company's resource organization, you don't want them to be a partof the resource hierarchy and you don't want them to appear in the Resource Directory. For these reasons, you do not createsetup users as resources, and you do not assign them resource roles.

Because setup users don't have resource roles, you must create a special role provisioning rule that uses a different field asthe condition. You create a Customer Data Management Administrator job, a field not normally used in Oracle Customer DataManagement Cloud, and provision the setup user with job roles based on this job. Customer Data Management Administrator



20

job contains roles such as Application Implementation Consultant, Application Diagnostic Administrator, It Security Manager,Sales Analysis, and Customer Data Management Administrator.

You can provision the following roles using

The following figure illustrates the two provisioning rules used to provision the Customer Data Management administratorjob role and employee role to the setup user. The employee role provisioning rule is already set up for you by Oracle unlessyou are implementing your application in a Global Single Instance environment. In GSI environments, you must set up allprovisioning rules yourself.

What Happens When You Create UsersWhen you create users, Oracle Customer Data Management Cloud:

• Creates accounts, user names, and temporary passwords

• Provisions the job roles and abstract roles the users require to carry out their jobs

• Sends users an e-mail with their sign-in credentials

Tip: System notification e-mails, including the initial e-mail with sign-in information, do not include the URL foraccessing Oracle Customer Data Management Cloud. You must provide this URL to users separately.



21

Creating a Job for Provisioning Setup UsersUse this procedure to create a job that you can use to assign setup users with implementation privileges. You use this job asa condition in the provisioning rule you create and assign the job to the users.

Perform the following steps to create a job:

1. Sign in as the initial user.2. If you downloaded and imported the implementation project, then open the task Manage Job from the

implementation project. Alternatively, you can search for the same Manage Job task by name in the Setup andMaintenance work area.

To open the task from the implementation project:

a. Navigate to the Setup and Maintenance work area by clicking the Setup and Maintenance icon on thespringboard. The springboard is the page you see when you first sign in.

b. Click Implementation Projects.c. In the Search Results region on the Implementation Projects page, click the name link for the project.d. Open the Create Setup Users folder.e. Click the Go to Task icon for the Manage Job task.

The Manage Jobs page appears.3. Click Create.

The Create Job: Basic Details page appears.4. Enter Customer Data Management Administrator in the Name field.5. Enter a name without spaces, for example CDM_Administrator, in the Code field.6. You can keep the other field values as they are because you are creating this job only for the purposes of

provisioning job roles to setup users.7. Click Next until you reach the end of the process train.8. Click Submit on the last page, and close the warning by clicking Yes.

The job may take a couple of minutes to create. You can use search on the Manage Job page to verify that it has beencreated.

Creating the Provisioning Rule for Setup UsersUse this procedure to create the provisioning rule which automatically provisions users assigned the Customer DataManagement Administrator job with the job roles required to perform the initial setup in this guide.

To create the provisioning rule:

1. Sign in as the initial user and open the Manage HCM Role Provisioning Rules task from the implementationproject. Alternatively, you can search for the task by name in the Setup and Maintenance work area.

The Manage Role Mappings page appears.2. Click Create.

The Create Role Mapping page appears.



22

3. In the Mapping Name field, enter Customer Data Management Administrator, or another name that will helpyou identify this mapping in the future.

4. In the Conditions region, select Customer Data Management Administrator, the job you created earlier, from theJob list. If the job does not appear in the list, click Search and search for it using the full name.

5. Select Active from the HR Assignment Status list.

This additional condition ensures that any provisioned job roles are automatically removed if the user is terminated.6. In the Associated Roles region, click Add and select each of the following job roles:

◦ Application Implementation Consultant

◦ IT Security Manager

◦ Application Diagnostics Administrator

◦ Master Data Management Application Administrator

7. Make sure the Autoprovision option is selected for all the job roles.8. Click Save and Close.

Creating Setup UsersAfter you have created the provisioning rules, you are ready to create other setup users in the UI.

To create a setup user:

1. While signed in as the initial user (or a setup user, if you already created another one), open the Manage Users taskin the implementation project. Alternatively, you can click the Users, Roles and Delegations link under the MyTeam heading in the Navigator.

The Manage Users page appears.2. Click Create.

The Create User page appears.3. Enter the user's name and a unique e-mail in the Personal Details region.

The application automatically sends the initial sign-in credentials to this e-mail when you save the record.4. In the User Details region, enter the user name.

Note: If you leave the User Name field blank, then the application automatically creates a user namefor you. By default, the application uses the e-mail as the user name.

5. In the User Notification Preferences region, select the Send user name and password option. The option to sendthe user name and password through e-mail is available only before you save the user record for the first time. Youdo not see the User Notification Preferences region and cannot change your selection after you create the user.

Note: If you do not select this option, the application does not send the initial password to the userand you must reset the user password manually using the procedure described in the Resetting UserPasswords topic.

6. In the Employment Information region, enter the following:

◦ Select Employee from the Person Type list.



23

◦ From the Legal Employer list, select the only value available, the legal employer Oracle created for you usingthe information you provided when you signed up with Oracle Customer Data Management Cloud.

◦ From the Business Unit list, select the only value available, the business unit created for you when yousigned up.

◦ From the Job list, select Customer Data Management Administrator, the job you just created. If the job isnot in the list, then you must search for it by clicking Search.

7. Click Autoprovision Roles

The Role Requests region displays the following roles:

◦ Application Diagnostics Administrator

◦ Application Implementation Consultant

◦ IT Security Manager

◦ Employee

◦ Master Data Management Application Administrator

The role request process may take a few minutes to complete because it is fulfilled by a process which is set to runperiodically. You can view the status of the request any time you edit this user. When the process is complete, theroles appear in the Current Roles region.

8. Click Save and Close.

If you have not selected the Send user name and password option, then you must reset the password using theprocedure described in the Resetting User Passwords topic.

Tip: The e-mail with the user name and password does not include the URL of your application. You must providethe URL to users separately.

Designating a Single User to Receive All Credential E-MailsYou can redirect the e-mails with user credentials and temporary passwords to a single user. For example, you may wantto send all of the credential e-mails to one of the setup users, so that you can sign in as different sales users and test yoursetups.

Note: The application sends the e-mails with initial passwords only once. If you send the initial e-mails to one ofthe setup users, then you must forward the credentials to the real user, if required.

To redirect the credential e-mails to a single user:

1. While signed in as a setup user, open the task Manage Enterprise HCM Information from the implementationproject. Alternately, search for the task by name in the Setup and Maintenance work area.

The Enterprise page appears.2. Click Edit on the Enterprise page, and select Correct.

The Edit Enterprise page appears.3. In the User and Role Provisioning Information region, select Yes from the Send User Name and Password list and

enter the e-mail of the user to receive the credential e-mails in the Alternate Contact E-Mail Address field.4. Make sure the Send User Name and Password option is set to Yes.5. Click Submit.



24

6. Close the warning by clicking Yes.7. Click Done.

The user e-mail you specified continues to receive all credentials e-mails until you clear the Alternate Contact E-MailAddress field.

Granting the Initial User the Same Privileges as Other SetupUsersUse this procedure to grant the initial user the same privileges as the other setup users:

1. While signed in as the initial user (or a setup user, if you already created another one), open the Manage Users taskin the implementation project. You can also click the Users, Roles and Delegations link under the My Teamheading in the Navigator.

The Users, Roles and Delegations page appears.2. Enter the first name of the initial user in the Keywords field and click Search.3. Select the name link in the Search Results.

The Edit User page appears.4. In the Employment Information region, select Customer Data Management Administrator (or the name that

you gave for the job) from the Job list. This is the job you created earlier. If the job is not listed, then click Searchand search for it by name.

5. Click Autoprovision Roles.

The Role Requests region displays the following roles:

◦ Customer Data Steward

◦ Employee

◦ Data Steward Manager

Your role request process may take a few minutes to complete because it is fulfilled by a process which is set to runperiodically. You can view the status of the request any time you edit this user. When the process is complete, theroles appear in the Current Roles region.


If you are signed in as the initial user, you must sign in again for the new privileges to take effect.

Resetting User PasswordsUse the Users tab in the Security Console work area to reset user passwords. You can have the application send out an e-mail notification with the URL the users can use to create the password themselves, or you can create passwords of yourown choosing. If you are creating users for testing, then entering your own password using the manual option makes itpossible for you to sign in as the user.

To reset the password, do the following:

1. While signed in as a setup user, navigate to Tools and then to the Security Console work area.



25

You can close any warnings regarding the scheduling of the Import Users and Roles Application Security Data job.2. Click the Users tab.3. Search for the user using one of the following:

◦ First or last name, but not both

◦ User name

The following figure shows the Users tab in the Security Console work area.

1

4. From the Action menu (callout 1 in the preceding figure), select Reset Password.

The Reset Password window appears.5. If you want the application to send an e-mail to users with a URL that they can use to create their own passwords

and sign in to the application, then select the Automatically generate password option.6. If you want to change the password yourself, then:

a. Select the Manually change the password optionb. Enter the new password twice.

7. Click Reset Password.

If you selected the Automatically generate password option, then the application sends out the e-mail enablingthe user to change the password and sign in. No notification is sent if you selected the manual option.



26


Chapter 5Creating Customer Data Management Application Users

27

5 Creating Customer Data ManagementApplication Users

Application Users Creation: OverviewCustomer data management application users can be broadly grouped into two:

• Managers Users: These have the job role Data Steward Managers

• Individual Users: These have the job role Customer Data Stewards

The following table lists the steps to create Customer Data Management users in the Create User page, which you open fromthe Manage Users work area.


Create Data Steward Managers

Create one or more DataSteward Managers dependingon your business requirements.

Manage Users

The Creating Customer DataManagement Application Userstopic.

Create Customer Data Stewards

Create one or more CustomerData Stewards depending onyour business requirements.

Manage Users

The Creating Customer DataManagement Application Userstopic.

Creating Customer Data Management Application UsersUse this procedure to create customer data management application users in the UI. To create a user, do the following:

1. While signed in as a setup user, open the Manage Users task from the implementation project. You can also openthis task by clicking Users, Roles and Delegations under the My Team heading in the Navigator, or you can searchfor the task by name in the Setup and Maintenance work area.

2. Click Create. The Create User page appears.3. Enter the user's first and last names and a unique e-mail address in the Personal Details region.

The application normally sends the initial sign-in credentials to this e-mail when you save the record. If you earlierspecified an alternate e-mail in the Enterprise page, the mail is sent to the alternate e-mail address instead.

If you do want the e-mail to be sent to the user, you must remove that alternate e-mail address from the Enterprisepage.

4. The application automatically fills the current date in the Hire Date field and uses that date as the start date for theresource.

5. In the User Details region, enter the user name.

If you leave the User Name field blank, then the application automatically creates a user name for you. By default, theapplication uses the e-mail as the user name.


Chapter 5Creating Customer Data Management Application Users

28

6. In the User Notification region, leave the Send User Name and Password option selected if you want the credentialse-mail to be sent to the alternate user you specified.

7. Make the following entries in the Employment Information region:

◦ Select Employee from the Person Type list.

◦ From the Legal Employer list, select the legal employer Oracle created for you using the information youprovided when you signed up with Oracle Customer Data Management Cloud. There should be only one valueavailable: your company name followed by the suffix LE.

◦ From the Business Unit list, select the business unit created for you when you signed up. There should be onlyone value available: your company name followed by the suffix BU.

Neither the legal employer name nor the business unit name is visible in the application, so the names need notcorrespond to actual entities in your company.

8. In the Resource Information region, from the Resource Role list, select the role the user plays in your implementation.For example:

◦ For Manager, Customer Data Management, select the predefined resource role Data Steward Manager.

◦ For Customer Data Steward, select the predefined resource role Customer Data Steward

9. Click Autoprovision Roles. The application provisions the job and abstract roles according to the role provisioningrules.


The application creates the user. Unless you deselected the Send User Name and Password option, the applicationalso sends the e-mail with the user name and password.


Chapter 6Setting Up Geography Data

29

6 Setting Up Geography Data

Geography Setup: OverviewYou must import and set up reference geography data for the countries where you do business if you are setting up salesterritories using geography as one of your dimensions or if you want to validate address entry. Alternatively, you can verifyaddress data by the Address Verification Cloud Service. However, note that you require a separate license for the AddressVerification Cloud Service. Suppose your organization is doing both. Further suppose that it plans to set up sales territoriesbased on states in the US, so it must import geography data for the US. Also, your organization wants its salespeople to usea list of values to enter the states in their addresses. The state in the address must be validated because invalid entries wouldcause opportunities to be left out of forecasts.

You must enable validation to the level of granularity you need for your territories. For example, if your organization decided toset up territories at the postal code level, then it should set up validation for state, city, county, and postal code.

Oracle licenses geography data that you can import, at no additional cost, into Oracle Applications Cloud. Oracle is in theprocess of changing suppliers for its licensed data from Nokia to GBG | Loqate. GBG | Loqate offers more complete andmore accurate data for more than 240 countries. During the transition, Oracle is making available a growing subset of theGBG | Loqate country data. New customers must import the GBG | Loqate data for countries where data is available, andcan import the Nokia data for the rest. When Oracle completes the transition, Oracle customers can either update theirgeography data to GBG | Loqate or continue using Nokia. Oracle will no longer update Nokia data for countries that areavailable through GBG | Loqate. The countries available from GBG | Loqate are listed in the GBG | Loqate GeographyReference Data: Explained topic. The countries available from Nokia are listed in the Nokia Geography Reference Data:Explained topic.

Alternatively, you can license geography data from another supplier and import it from a file. For more information aboutimporting third party geography data, see the Define Geographies chapter of the Implementing Customer Data Managementguide available on docs.oracle.com.

The following table lists the tasks you must complete to set up geography. You can access all tasks for this setup from theSetup Geography Data folder in your implementation project.


Find Geography Data

Review the list of availablecountries from GBG | Loqateand Nokia.

N/A

For GBG | Loqate, see the GBG| Loqate Geography ReferenceData: Explained topic in thischapter. For Nokia, see the NokiaGeography Reference Data:Explained topic in this chapter.

Set up the Supplier forGeography Data

If GBG | Loqate geography dataexists for the country you wantto import, then set the profileDaaS GBG | Loqate Data ImportEnabled (ORA_ HZ_ ENABLE_DAAS_LOQATE) to Yes. Bydefault this profile is set to Noand imports Nokia data.

Manage Administrator ProfileValues

Specifying the Geography DataSupplier topic in this chapter.



30


Import Geography Data

Search for the country youwant to import on the ManageGeographies page and selectthe Import Geography Dataaction. The Import Geography Dataaction is disabled if Oracle-licensed geography data or anythird-party geography data isalready imported for the countryor geography data and hierarchydata is already manually createdfor the country or GBG | Loqateand Nokia do not support thecountry. In this case, you mustlicense geography data fromanother supplier and import itfrom a file. For more informationabout importing third partygeography data, see the DefineGeographies chapter of theImplementing Customer DataManagement guide available ondocs. oracle.com.

Manage Geographies

Importing Oracle-LicensedGeography Reference Data topicin the Implementation Guide.

Set up Geography Validation For the countries you imported,

enable validation down toaddress level required for yourterritories and specify whichaddress elements require lists ofvalues.

When you enable validationon an address element, theapplication suggests alternativesduring address entry. Enablinga list of values requires the userto make a selection from a list.Both validation and lists of valuesare enforced in the UIs.

Your organization should:

• Enable list of valuesfor entering states inaddresses.

• Enable validation forstates because itsterritories are defined atthe state level.

Manage Geographies

Setting Up Geography Validationtopic in this chapter

Turn on Validation for AddressImport

The validation selection youmade affects entries made inthe application UI only. Youmust use the task ManageAdministrator Profile Values toset the profile option GeographyAddress Validation Enabled to

Manage Administrator ProfileValues

Setting Up Geography Validationtopic in this chapter



31


Yes to validate addresses youimport. You must also make sure thatthe address data you importmatches what the geographyreference data expects. Incase of data mismatch, add analternate geography data in theManage Geographies UI. Forexample, for the Terni provincein Italy, Nokia has a value ofTERNI and GBG | Loqate hasa value of TR. To resolve thisconflict, add TR as an alternateprovince name in the ManageGeographies UI.

Specifying the Geography Data Supplier: ProcedureIf you are importing geography data licensed by Oracle, and GBG | Loqate geography data exists for thecountry where you do business, then set the system profile option DaaS GBG | Loqate Data Import Enabled(ORA_HZ_ENABLE_DAAS_LOQATE) to Yes. By default, the system profile is set to No and the application imports Nokiadata. If you are doing business in multiple countries, and not all the countries are yet available from GBG | Loqate, then youcan download geography data from both suppliers by changing the value of this system profile, but you can download onlyone data set for each country.

To specify the geography data supplier:

1. Open the Manage Administrator Profile Values task from the implementation project or after searching for thetask by name in the Setup and Maintenance work area.

The Manage Administrator Profile Values page appears.2. In the Profile Option Code field located in the Search: Profile Option region, enter

ORA_HZ_ENABLE_DAAS_LOQATE.3. Click Search.4. With the profile option selected in the search results, select Yes from the Profile Value list to import GBG | Loqate

data. A setting of No imports Nokia data.5. Click Save and Close.

Importing Geography Reference DataUse this procedure to import geography reference data licensed by Oracle. If the country data you want to importis not available from the supplier specified using the system profile option DaaS GBG | Loqate Data Import Enabled(ORA_HZ_ENABLE_DAAS_LOQATE), then the Import Geography Data action is disabled.



32

Note: The geography data is provided by GBG | Loqate or Nokia and is third-party content. As per Oraclepolicy, this software and documentation may provide access to or information about content and services fromthird parties. Oracle and its affiliates are not responsible for and expressly disclaim all warranties of any kind withrespect to the third-party content and services. Oracle and its affiliates are not responsible for any loss, costs, ordamages incurred due to your access to or use of third-party content, products, or services.

To import geography data:

1. Sign is as a setup user having the role Master Data Management Applications Administrator.2. Open the Manage Geographies task directly from the implementation project or by searching for the task in the

Setup and Maintenance work area.The Manage Geographies page appears.

3. Enter either the country name in the Country Name field or the two-letter ISO code of the country in the CountryCode field.Examples of ISO country codes include US (United States) and AT (Austria).

4. Click Search.The Search Results display the country.

5. Select the country in the search results. Do not click the link.6. Select Import Geography Data from the Actions menu.7. Click OK to close the warning message.8. Click OK to close the confirmation message.

The import of larger countries may require several hours to complete. You can track the progress of the import process byselecting Scheduled Processes from the Navigator menu.

After the import is complete, you can search for the country again in the Manage Geographies page. Check marks nowappear in the Structure Defined and Hierarchy Defined columns indicating that the import completed successfully.

The following figure shows the Manage Geographies page with check marks on the Structure Defined and Hierarchy Definedcolumns indicating that the import has completed successfully.

Note: Report any issues with GBG | Loqate and Nokia data to Oracle Support who will contact the appropriateteam for correction. Alternatively, you can make manual changes to the geography data by using the ManageGeographies task in the Setup and Maintenance work area. If you decide to use geography data from anotherdata provider, then Oracle Support can delete the data and you can then load your data using File Import.



33

GBG | Loqate Geography Reference Data: ExplainedOracle Applications Cloud provides third-party GBG | Loqate master geography data for import. The following table lists thecountries for which the GBG | Loqate master geography data is available for import.

Country Name Country Code Default Language and LanguageCode

Additional Language Supportand Language Code

Australia

AU

English EN

N/A

Belgium

BE

Dutch/Flemish NL

French FR German DE

Brazil

BR

Portuguese PT

N/A

Canada

CA

English EN

French FR

France

FR

French FR

N/A

Germany

DE

German DE

N/A

Great Britain

GB

English EN

Welsh CY

Netherlands

NL

Dutch/Flemish NL

N/A

Portugal

PT

Portuguese PT

N/A

Spain

ES

Spanish ES

N/A



34

Country Name Country Code Default Language and LanguageCode

Additional Language Supportand Language Code

Sweden

SE

Swedish SV

N/A

Switzerland

CH

German DE

French FR Italian IT

United Arab Emirates

AE

Arabic AR

N/A

United States

US

English EN

N/A

Nokia Geography Reference Data: ExplainedOracle Applications Cloud provides third-party Nokia master geography data for import. The following table lists the countriesfor which the Nokia master geography data is available for import.

Country Name Country Code

Andorra

AD

Argentina

AR

Austria

AT

Belgium

BE

Brazil

BR

Bulgaria

BG

Canada

CA

Cayman Island

KY

Chile CL



35


Croatia

HR

Czech Republic

CZ

Denmark

DK

Dominican Republic

DO

Estonia

EE

Finland

FI

France

FR

Germany

DE

Greece

GR

Guadeloupe

GP

Hungary

HU

Iceland

IS

India

IN

Indonesia

ID

Ireland

IE

Isle of Man

IM

Israel

IL

Italy

IT

Jamaica

JM

Latvia

LV

Liechtenstein

LI

Lithuania LT



36


Luxembourg

LU

Malaysia

MY

Malta

MT

Martinique

MQ

Mexico

MX

Netherlands

NL

New Zealand

NZ

Norway

NO

Peru

PE

Poland

PL

Portugal

PT

Puerto Rico

PR

Reunion Island

RE

Romania

RO

Russian Federation (Russia)

RU

San Marino

SM

Singapore

SG

Slovakia

SK

Slovenia

SI

South Africa

ZA

Spain

ES

Swaziland SZ



37


Sweden

SE

Switzerland

CH

Taiwan

TW

Turkey

TR


AE

United Kingdom

GB

United States

US

Uruguay

UY

Holy See (Vatican City State)

VA

Importing Third Party Geography Data Using File BasedImportYou can import Oracle-licensed GBG | Loqate or Nokia data, shipped with the application, for those countries where the datais available. If the licensed data is not available or is already set up for a particular country, then the Import Geography Dataaction is disabled. In this case, you must license geography data from another supplier and import it from a file.

Importing Country Structures Using File-Based ImportA country structure is a hierarchical grouping of geography types for a country. For example, the geography structure for theUnited States has the geography type of State at the top, followed by the County, then the City, and finally the Postal Code.

You must import country structures before importing geographies. You can use the country structure to set up the following:

• The relationships between geographies within a country

• The types of geographies that you can define for a country

For more information about importing country structures, see the related links on importing country structures.

Importing Geographies Using File-Based ImportA geography is any region with a boundary around it, regardless of its size. It might be a state, a country, a city, a county, ora ward. You must create or import geographies before you can associate them with company defined zones and addresses.For more information about importing geographies, see the related links on importing geographies.



38

Related Topics• Importing Country Structures Using File-Based Import

• Country Structure Import, File-Based Data Import for Oracle Sales Cloud

• Importing Geographies

Setting Up Geocoding and Address CleansingGeocoding and Address Cleansing are additional features that you must set up separately. Geocoding makes it possibleto display customers in the vicinity of a mobile address. Address Cleansing makes it possible to validate postal addressesdown to the street level. Note that to use address cleansing, you require a separate license for the Address Verification CloudService.

You must set up Geocoding for those countries where you are using the Around Me functionality in Sales Cloud Mobile.Geocoding finds the latitude and longitude coordinates from geographic data such as street addresses or ZIP Codes.Once these coordinates are available, you can use the spatial services feature to identify points of interest, such ascustomer and contact addresses, in the vicinity. The application integrates the Geocoding feature with eLocation, whichis a Geocoding service provided by Oracle. For more information about eLocation, see: http://elocation.oracle.com/maps_oracle_dot_com_main.html.

Enabling GeocodingTo enable Geocoding, click the arrow mark under the Geocoding Defined column header and make sure that the arrow marktransforms into a tick mark.

The following is the figure of the Manage Geographies page with Geocoding Defined check box highlighted:

Once geocoding is enabled, you can schedule this feature to run at regular time intervals so that newly created or updatedlocations are selected and geocoded. To schedule the geocoding feature to run at regular intervals, complete these steps:

1. Navigate to the Scheduled Processes work area.2. Click Schedule New Process.3. Click the Name drop-down list and search for Populate Location Latitude and Longitude Information.4. Select the value form the search result and click OK.

http://docs.oracle.com/cloud/latest/common/OAFDI/OAFDI1504165.htm#OAFDI1504165

http://docs.oracle.com/cloud/latest/common/OEFBS/toc.htm

http://docs.oracle.com/cloud/latest/common/OAFDI/OAFDI1504168.htm#OAFDI1504168



39

5. Click OK in the Schedule new Process dialog box to confirm the name and description of the new process. ProcessDetails page appears.

6. Enter the parameters such as Country Code, Start Date, End Date, Regenerate Geocode and Batch Size.7. Click Process Option to set options such as Language, Territory, Currency, and Time Zone.8. Click OK to the Process Options page.9. Click Submit.

10. Click Close.

Enabling Address CleansingAddress Cleansing makes it possible to validate postal addresses down to the street level. Address cleansing validates,corrects, and standardizes address information that you enter in the application. Address cleansing, unlike geographyvalidation, validates both the geography attributes and the address line attributes.

Note: To use the address cleansing functionality, a separate license for the Address Verification Cloud Service isrequired.

You can specify the real-time address cleansing level for each country by selecting either of the following in the ValidationDefined option on the Manage Geographies page:

• None: Specifies no real time address cleansing.

• Optional: Enables address verification to cleanse address real time.

For more details on enabling address cleansing, see the chapter: Configuring Address Verification, Setting Up AddressCleansing and Address Verification, Defining Address Cleansing.

Setting Up Geography ValidationYou must set up geography validation for those geography elements that you plan to use in your sales territories. Setting upvalidation also helps users fill in missing address information, and validate addresses during entry. For example, you can haveusers select states or other address elements from lists to ensure accuracy during entry, and you can have the application fillin missing values. For example, when the user enters a Postal Code, the application can retrieve the city and state.

For each country, you must map the geography types to the address attributes. You need to verify the default mapping andupdate it if required when you define geography validation.

Our example organization wants its salespeople to use a list of values to enter the states in their addresses and it plans to setup territories at the state level. For these reasons, validation must be set up at the state level.

Define Geography ValidationPerform the following steps to define geography validation:

1. Open the Manage Geographies task from the implementation project or by searching for the task by name in theSetup and Maintenance work area.

The Manage Geographies page appears.2. Search for a country you imported using either its name or its two letter ISO code. For example, you can search by

entering either the country name United States or the two-letter ISO code US.3. Select the country from the Search Results area.4. Click the Go to Task button in the Validation Defined column. The Manage Geography Validation page appears.



40

5. In the Address Style region, ensure that the No Styles Format address style is selected. You define validation for theNo Styles Format address style so that the validations are performed for all addresses in the country.

Note: The setup of address styles for your application is done elsewhere, using the Manage AddressFormats task.

6. Select Enable List of Values in the Geography Mapping and Validation region to display the geography type as listof values during address entry in the classic and simplified UIs. For example, to have users select states from a list,select Enable List of Values for State.

Our example organization enables the list of values for State because it uses states for its sales territories and wantsto assure that they are always entered correctly.

7. Select Geography Validation for all the geography types that you plan to use in territories.

Our example organization plans to use set up geographies by state, so it selects Geography Validation for State.

You must enable geography validation for all geography levels above the level you are planning to use for territories.If the example organization decided to set up territories at the Postal Code level, it must select Geography Validationfor state, city, county, and Postal Code.

Note: If you do not select the validation for an address element, the application still suggests valuesto the user during address entry in the classic and simplified UIs, but it does not validate the addresselement.

8. Ensure that the mapping between Geography Type and Map to Attribute is valid in the Geography Mappingand Validation region and modify it if required. Oracle recommends that you use the following valid mapping for thecountries that GBG | Loqate supports:

Country Name Country Code Geography Type Map to Attribute


AE

◦ Country

◦ Emirate

◦ Municipality

◦ Area

◦ Country

◦ State

◦ City

◦ Additional AddressAttribute 2

Australia

AU

◦ Country

◦ State

◦ City

◦ Postcode

◦ Country

◦ State

◦ City

◦ Postal code

Belgium

BE

◦ Country

◦ Gewest

◦ Provincie

◦ Gemeente

◦ Postcode

◦ Country

◦ Additional addressattribute 1

◦ Province

◦ City

◦ Postal code

Brazil

BR

◦ Country ◦ Country



41


◦ Estado

◦ Municipio

◦ CEP

◦ State

◦ City

◦ Postal code

Canada

CA

◦ Country

◦ Province

◦ City

◦ Postal Code

◦ Country

◦ Province

◦ City

◦ Postal code

Switzerland

CH

◦ Country

◦ Kanton

◦ Bezirk

◦ Gemeinde

◦ PLZ

◦ Country

◦ State

◦ County

◦ City

◦ Postal code

Germany

DE

◦ Country

◦ Bundesland

◦ Bezirk

◦ Stadt

◦ PLZ

◦ Country

◦ State

◦ County

◦ City

◦ Postal code

Spain

ES

◦ Country

◦ Autonomia

◦ Provincia

◦ Municipio

◦ Codigo Postal

◦ Country


◦ Province

◦ City

◦ Postal code

France

FR

◦ Country

◦ Region

◦ Department

◦ Commune

◦ Settlement

◦ Postcode

◦ Country


◦ State

◦ City


◦ Postal code

Great Britain

GB

◦ Country

◦ County

◦ Posttown

◦ Postcode

◦ Country

◦ State

◦ City

◦ Postal code

Netherlands

NL

◦ Country ◦ Country



42


◦ Provincie

◦ Gemeente

◦ Settlement

◦ Postcode

◦ Province

◦ County

◦ City

◦ Postal code

Portugal

PT

◦ Country

◦ District

◦ Municipality

◦ Parish

◦ Postcode

◦ Country

◦ State

◦ County

◦ City

◦ Postal code

Sweden

SE

◦ Country

◦ Lan

◦ Kommun

◦ By

◦ Postnr

◦ Country

◦ State

◦ County

◦ City

◦ Postal code

United States

US

◦ Country

◦ State

◦ County

◦ City

◦ Zip Code

◦ Country

◦ State

◦ County

◦ City

◦ Postal code

9. Select the values from the Geography Validation Level for Country drop-down list to specify whether you want topermit the application to save addresses that are not considered valid. The following are the available values in theGeography Validation Level for Country drop-down list:

◦ No validation: The default value. Select to save incomplete or incorrect addresses and verify the address datalater by the Address Verification Cloud Service.

◦ Error: Select to verify address data against the master geography reference data. This value permits only validaddresses to be saved.

Our example organization wants to save all addresses including incomplete and invalid addresses, so it keeps theNo validation which is the default value.



43

The following figure shows the Manage Geography Validation page when the task is completed.


Turning on Validation for Address ImportBy default, the validation you specified is enforced for creating addresses in the UI only. You must set the profile optionGeography Address Validation Enabled to Yes for the validation to be enforced during import. Follow these steps to set theprofile option:

1. Open the Manage Administrator Profile Values task from the implementation project or by searching for it in theSetup and Maintenance work area. The Manage Administrator Profile Values page appears.

2. In the Profile Display Name field located in the Search: Profile Option region, enter Geography Address ValidationEnabled.

3. Click Search.4. With the profile option selected in the search results, select Yes from the Profile Value list.5. Click Save and Close.



44


Chapter 7Importing Accounts and Contacts Using Import Management

45

7 Importing Accounts and Contacts UsingImport Management

About Import Management

Importing Data: ProcedureUsing the Import Management option available from the Tools work area, you can import a wide range of business datafrom text files. Your import data can either create, update, or delete application records.

Use the steps outlined in this topic as a guide to importing data. The import options and other details differ by the type ofdata that you're importing. Before importing, you must understand how the data in your file maps to the attributes in OracleApplications Cloud and what values are expected in the import file.

Note: Do not submit duplicate import jobs for the same import object because they create duplicate objectrecords.

To help you get started, you can use the example import templates described in the related topics.

Importing Data from a FileYou must be signed in as an administrator or setup user to perform the import. To import data:

1. In the Tools work area, click the Import Management icon.2. On the Manage Imports page, click the Create Import Activity button. The Create Import Activity: Enter

Import Options page appears.3. Provide values for each field on the page as shown in the following table:

Field Description of the value

Name

Name of the import.

Object Object that you are importing.

If you cannot find your object in the drop-down list, then you can search and select the objectby clicking the Search link. In the Search and Select dialog box, enter the object name in theObject text box and click the Search button. Select your object from the result list and click OK.

You can also use the advanced search option by clicking the Advanced button. Here you cansearch based on various filter criteria such as object name, Attachment supported, creation date,and so on.

If the object you are importing is not listed then verify if you have the roles and privileges requiredto import the object.



46

Field Description of the value

Attachment Object To import an attachment for an existing object record in the database select the Attachments

object from the Object drop-down list. Next select the object from the Attachment Objectdrop-down list.

For more details on importing attachments, review the topic Importing Attachments: Procedure inthe related topics section.

File Name

Browse and select a text file in CSV format.

Note: If your source file has more than 50,000 records, then you must manually splitthe file into several smaller files with less than 50,000 records each. The file import pageonly allows 50, 000 records for each import job. Alternatively, you can use the OracleSales Cloud Data Loader Client, which can accept files with more than 50,000 records.See the My Oracle Support (support. oracle.com) document External Data Loader Client(document ID 2325249.1) for more information about this tool.

4. Optionally if you want to set additional import configurations, then click the Advanced Options section. Here youcan configure settings under Source File, Import Options, or Create Schedule sections.

a. In the Source File and Import Options regions, some of the options in the following table might be availabledepending on the object that you're importing:

Option Description

Import Mode You can specify whether you want to create and update records or update them only.

• Update and create records - a new record is created if a matching record is notfound. This is the default option.

• Create records - all the records in the file are new records which have to becreated. If there are any existing matching records, then they are marked as errors.

• Delete records - all the records in the file are deleted.

Notification email

The email of the individual who receives import processing notifications. The user submittingthe import receives an email notification automatically. If you want to have more than oneemail recipient, separate the email addresses with a semicolon.

Delimiter If your file doesn't use a comma to separate values, then select the correct delimiter in the

Delimiter drop-down list.

Decimal Separator

The decimal separator used in your import file.

Date Format

The format of the date fields in your file.

Time Stamp Format

The format of time fields in your file.

File Encoding

The format in which your source file has been encoded.

b. In the Create Schedule region, you can schedule the import to either run immediately or at a future date. Ifyou select a future date, then provide the date and time to start the import.



47

5. Click Next. The Create Import Activity: Map Fields page displays the first row of the data in your source file. Bydefault, the application tries to automatically map each of the source file columns to the appropriate target objectattribute. If some of the columns in your file could not be mapped, then drag the target attribute onto the AttributeName column under the Source File region.

6. You also have the option of selecting an appropriate mapping from the list of available mappings under the ImportMapping drop-down list. If you're reusing an import mapping, then both the source and target columns are alreadypopulated. The Source File region represents your import file.

You can choose not to import a column in your file by leaving the Attribute Name field blank.7. To validate the mapping of fields, click the Validate Data button. Validation process is triggered and displays any

mapping errors on the Mapping Validation screen. Additionally, the first 10 rows of the file are validated.8. Click Next. The Create Import Activity: Review and Submit page appears. On this page, review the import

activity configuration. If you had not run the prevalidation on the Map Fields page, then you get a notificationmessage to run the validation process.

9. Click the Validate Data button to run the validation. Validation errors, if any, are displayed on the Mapping Validationscreen. The data in unmapped columns are not imported. If you get warnings about unmapped columns, then youcan ignore these columns, and proceed to submit the import job.

10. Submit to activate the import.

Monitoring the Import StatusTo monitor the status of your import:

1. After you submit your import, you can view the status on the Manage Imports page that appears. It shows thefollowing infolets:

Infolet Heading Description

All Imports

Shows the active, completed, and unsuccessful imports.

Active Imports

Shows all the imports that are currently running.

My Completed Imports

Shows the imports that have completed.

Unsuccessful

Shows the unsuccessful imports.

2. Click the My Completed Imports tab to view the imports that have completed.3. Monitor the status of your import. A status of Completed or Completed with Errors indicates that the import has

completed. Alternatively, you can wait for the notification email. For more details on monitoring the status of import,see the topic Import Monitoring: Explained referenced in the related links section.

4. Click the import name link to see additional information about the import. You can generate the diagnostics and logfiles from the Action menu. Download the log files by clicking the download icon under the Import Attachmentssection.

Suppressing Business Events for the ObjectsWhile bulk loading data into Oracle Sales Cloud, business events on standard objects are triggered in the Create and Updateoperations. This may have an adverse impact on performance. You can suppress this behavior using the following profileoptions:

• ZCA_PUBLIC_BUSINESS_EVENTS: You can use this profile option to suppress the business events for Accounts,Activity, Asset, Contacts, Deal Registration, Leads, and Opportunity objects. This profile option has the default



48

value set to Y. Y indicates that all business events are enabled. When you set the profile option value to N, then thebusiness events are suppressed until the same profile option is set to Y once again.

• ZPM_ENABLE_PARTNER_EVENTS: You can use this profile option to suppress the business events for Partner,Partner Contact, and Partner Notes objects. This profile option has the default value set to N. However, the profileoption ZCA_PUBLIC_BUSINESS_EVENTS should be disabled to suppress events for any object. The profile optionZCA_PUBLIC_BUSINESS_EVENTS overrides ZPM_ENABLE_PARTNER_EVENTS.

Related Topics

• File-Based Import Monitoring: Explained

• Import Activity Field Mapping: Explained

• File-Based Import Mapping: Explained

Importing Attachments: ProcedureThis topic describes how to import attachments using the Import Management feature. You can import attachmentsassociated with any supported object.

The following objects support importing attachments:

• Activity

• Asset

• Lead

• Opportunity

The following are the file types supported for attachment files:

• CSV

• PDF

• PNG

• PPTX

• TIF

• TEXT

• XLSX

• XML

Importing AttachmentsYou can use the following steps to import attachments using Import Management:

1. Click Tools > Import Management.2. On the Manage Imports page, click the Create Import Activity button. The Create Import Activity: Enter

Import Options page appears.3. In the Name field, enter a name for your import. In the Object drop-down list, and select Attachment.4. In the Attachment Object drop-down list that appears, select the object associated with the attachment.5. Browse and select the ZIP file that contains the attachment files and the source data file with the object records

information for which you import the attachment.

https://fusionhelp.oracle.com/helpPortal/faces/AtkHelpPortalMain?TopicId=9DABCC981063D1C4E040D30A688104C1

https://fusionhelp.oracle.com/helpPortal/faces/AtkHelpPortalMain?TopicId=9CC9BA836F57554AE040D30A688133D4

https://fusionhelp.oracle.com/helpPortal/faces/AtkHelpPortalMain?TopicId=9CC9BA836F54554AE040D30A688133D4



49

6. The ZIP file must contain at least a file named Attachment.CSV, and optionally one or more attachment files. TheAttachment. CSV file has the format shown in the following table:

Pk1Value ObjectPuid FileName Url

300100111735265

Sales.txt

CDRM_L1011

www.Google.com

300100111735265

www.Yahoo.com

CDRM_L1212

file1.txt

Pk1Value and ObjectPuid column values uniquely identify an existing object record. FileName indicates the name ofattachment files. Url indicates the value of URL attachment to import.An attachment can only be associated with an existing record of the object. A single record can be associated withmultiple attachments by having multiple rows in the CSV file. There is no limit on the number of attachments that canbe imported in a single import job. However, the size of the attachment ZIP file cannot exceed 250 MB.

Note: A record in the CSV file cannot have values for both FileName and Url columns. You can passeither the Primary key or the PUID, but not both for an object record.

7. Click Next. On the Create Import Activity: Map Fields page, click the Apply button next to the Import Mappingdrop-down list to map the source and target attributes automatically.

8. Click Next to navigate to the Review and Submit page.

Review the import activity configuration and click Submit to activate the import. The Manage Imports page shows thestatus of the submitted import. The topic Importing Data: Procedure in the related topics section contains more details aboutthe import process.

Importing Your Data

Importing Your Account DataUse this topic to import account data into Oracle Applications Cloud. You can use the import functionality to create, update,or delete account records.

The account object has the following child objects:

• Address

• Classification

• Relationship

• Sales Team Member

To import account records, perform the following tasks:

1. Map your source data to Oracle Applications Cloud object attributes.



50

2. Create source Comma Separated Values (CSV) file for import.3. Create the import activity.4. Review the import results.

Mapping Your Source Data to Oracle Applications Cloud Object AttributesTo import your account data into Oracle Applications Cloud, you must populate a CSV file with your source data and mapthat source data to target object attributes in Oracle Applications Cloud.

You must do the following before creating the CSV file for data import:

• Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

• Ensure prerequisite steps are complete, such as understanding what attributes are required for importing yourobjects.

• Understand your options for uniquely identifying the records.

• Ensure parent records exist before importing child records.

• Identify the target object attributes that are required in the CSV file for a successful import.

Prerequisite Setup Tasks

You must set certain options for some attributes in the application before you can populate them. For example, if you areusing source system reference information to identify your account records, the source system of the Account object shouldbe enabled for parties in the Manage Trading Community Source Systems task.

Also, when importing a child record, ensure that its parent record exists in the database. For example, when importing theaddress of an account, ensure that its parent account exists in the database. If the parent record does not exist beforeimporting the child record, then the child record import fails.

Options for Uniquely Identifying the Records

To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the importprocess to uniquely identify the records. The file import process uses the attribute values to automatically map your sourcedata to the target object attributes in Oracle Applications Cloud.

The preferred options for uniquely identifying an object record are as follows:

• Public unique identifiers: If you're creating records, then you can provide a user-friendly public unique identifier(attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for whichyou have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you canuse the Number attribute to identify the record. For Account object, the attribute is PartyNumber. It appears as PartyNumber in the UI.

• Source system and source system reference value: If you're importing data from a legacy or external systemor are updating records for which you have previously provided source system reference data, then youcan provide the source system code that identifies the external system (attributes typically denoted with'SourceSystem') and source system reference value, a unique identifier within the external system (typicallydenoted with 'SourceSystemReferenceValue'). For Account object, these attributes are SourceSystem andSourceSystemReferenceValue. They appear as Party Source System and Party Source System Reference Value inthe UI respectively.

Required Attributes and Validations

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure thatyou provide valid values for the attributes. The following table lists the required attributes for importing new account records,required attributes for updating account records, prerequisite setup tasks for the attributes, and specific validations, if any, foraccount import:



51

Attribute Description Prerequisite SetupTasks or ImportValidations

Creating an AccountRecord

Updating an ExistingAccount Record

Deleting an ExistingAccount Record

SourceSystem

The coderepresenting thesource system forthe sales account.

Identify the sourcesystem or configuresource systemseither by using theManage TradingCommunity SourceSystem task, orby importing thesource systeminformation intoOracle ApplicationsCloud using theSource SystemReference importobject.

ConditionallyRequired

For uniquelyidentifying anaccount record,provide one of thefollowing referenceinformation:

• SourceSystemandSourceSystemReferenceValue

• PartyNumber




• PartyNumber




• PartyNumber

SourceSystemReferenceValue

The referencenumber or textrepresenting thesource systemunique ID for theparty (account orcontact) to whichthe sales profilebelongs.





• PartyNumber




• PartyNumber




• PartyNumber

PartyNumber

The public uniqueidentifier of theparty.

Identify the party IDand party numbervalue by exportingthe Party object.




OrganizationName

The name ofthe party of theOrganization partytype.

Identify theorganization nameof the resource bynavigating to theResource Directory.

Required



OwnerPartyNumber

The public uniqueidentifier of theresource who ownsand manages thesales account.

No prerequisitetasks.


Provide theaccount owner, byincluding one of thefollowing referenceinformation:

• OwnerPartyNumber• OwnerEmailAddress







52

Attribute Description Prerequisite SetupTasks or ImportValidations

Creating an AccountRecord

Updating an ExistingAccount Record

Deleting an ExistingAccount Record

OwnerEmailAddress

The email addressof the resource whoowns and managesthe sales account.

No prerequisitetasks.








You can view the Account object along with all its child objects and attributes in the Manage Import Objects page of theImport Objects tab. You can find attribute information like type, length, description, and so on, on this page.

Creating Source CSV File for ImportThe CSV file is provided as source to the file-based data import process. You must populate the CSV file with the data youwant to import into Oracle Applications Cloud.

You can either create a CSV file on your own or make use of templates available in preexisting mappings. To download atemplate, do the following:

1. In the Navigator, under Tools, click Import Management.2. Click the Import Objects tab to open the Import Object Details page.3. In the table, select the Account object row and click the Download icon.4. Save the Account_Templates ZIP file to a location on your desktop.

You must edit the Account.CSV file and provide valid values for the required attributes.

Creating the Import ActivityTo import data into Oracle Applications Cloud, you must create an import activity and provide the CSV file as a source to theactivity. You must be signed in as an administrator or a setup user to perform this task. To create an import activity do thefollowing:

1. In the Navigator, click Tools > Import Management.2. On the Manage Imports page, click Create Import Activity.3. On the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select

Account from the Object drop-down list.4. In File Name field, browse and upload the required CSV file, and click Next.5. On the Map Fields page, the source and target attributes are automatically mapped. If required, manually edit the

attribute mappings, and save the mapping file. Click Next.6. Click the Validate Data button to validate the mapping of the source file for unmapped columns and to check for

data format issues.7. On the Review and Submit page, click Submit.

Reviewing the Import ResultsYou can review the import results by checking for the import activity on the Manage Import Activity page. You must besigned in as an administrator or a setup user to perform this task. To check the status of the import activity, do as follows:

1. In the Navigator, click Tools > Import Management.



53

2. On the Manage Imports page, click the All Imports infotile. Search for the import activity that you created usingone of the search criteria, such as status, name, object, and so on.

3. Check the Status column for the import activity. The import is successful if the status displays as Completed.

Note: On this page, you can also view quickly the number and status of all active imports, completedimports, and unsuccessful imports that have been submitted.

Related Topics

• Managing Import Mappings

Importing Your Contact DataUse this topic to import contact data into Oracle Applications Cloud. You can use the import functionality to create, update,or delete contact records.

The contact object has the following child objects:

• Address

• Classification

• Relationship

• Sales Team Member

To import contact records, perform the following tasks:

1. Map your source data to Oracle Applications Cloud object attributes.2. Create source Comma Separated Values (CSV) file for import.3. Create the import activity.4. Review the import results.

Mapping Your Source Data to Oracle Applications Cloud Object AttributesTo import your contact data into Oracle Applications Cloud, you must populate a CSV file with your source data and map thatsource data to target object attributes in Oracle Applications Cloud.

You must do the following before creating the CSV file for data import:

• Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

• Ensure prerequisite steps are complete, such as understanding what attributes are required for importing yourobjects.

• Understand your options for uniquely identifying the records.

• Ensure parent records exist before importing child records.

• Identify the target object attributes that are required in the CSV file for a successful import.

Prerequisite Setup TasksYou must set certain options for some attributes in the application before you can populate them. For example, if you areusing source system reference information to identify your contact records, the source system of the Contact object shouldbe enabled for parties in the Manage Trading Community Source Systems task.

Also, when importing a child record, ensure that its parent record exists in the database.

https://fusionhelp.oracle.com/helpPortal/faces/AtkHelpPortalMain?TopicId=4D6E3DA1E689554BE05362C3F00A18E6



54

Options for Uniquely Identifying the RecordsTo import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the importprocess to uniquely identify the records. The file import process uses the attribute values to automatically map your sourcedata to the target object attributes in Oracle Applications Cloud.

The preferred options for uniquely identifying an object record are as follows:

• Public unique identifiers: If you are creating records, then you can provide a user-friendly public unique identifier(attributes denoted with Number and usually visible in the business object's UI). If you update a record for which youhave previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can usethe Number attribute to identify the record.

• Source system and source system reference value: If you are importing data from a legacy or external system or areupdating records for which you have previously provided source system reference data, then you can provide thesource system code that identifies the external system (attributes typically denoted with SourceSystem) and sourcesystem reference value, a unique identifier within the external system (typically denoted with SourceSystemReference).

Required Attributes and ValidationsTo import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure thatyou provide valid values for the attributes. The following table lists the required attributes for importing new contact records,required attributes for updating contact records, required attributes for deleting contact records, prerequisite setup tasks forthe attributes, and specific validations, if any, for contact import:

Attribute Description Prerequisite SetupTask or ImportValidations

Creating a ContactRecord

Updating an ExistingContact Record

Deleting an ExistingContact Record

SourceSystem

The coderepresenting thesource system forthe contact.


ConditionallyRequired Foruniquely identifyinga contact record,provide one of thefollowing referenceinformation:


• PartyNumber



• PartyNumber



• PartyNumber

SourceSystemReferenceValue

The referencenumber or textrepresenting thesource systemunique ID for thecontact.




• PartyNumber



• PartyNumber



• PartyNumber



55

Attribute Description Prerequisite SetupTask or ImportValidations

Creating a ContactRecord

Updating an ExistingContact Record

Deleting an ExistingContact Record

PartyNumber

The public uniqueidentifier of thecontact.

No prerequisitetasks




FirstName

First name of aperson party.


Required

Not required

Not required

LastName

Last name of aperson party.


Required

Not required

Not required

You can view the Contact object along with all its child objects and attributes in the Manage Import Objects page of theImport Management flow. You can find attribute information like type, length, description, and so on, on this page.

Creating Source CSV File for ImportThe CSV file is provided as source to the file-based data import process. You must populate the CSV file with the data youwant to import into Oracle Applications Cloud.

You can create a CSV file on your own or by using a predefined template. To download a preexisting template, do thefollowing:

1. In the Navigator, under Tools, click Import Management.2. Click the Import Objects tab to open the Manage Object Details page.3. Click the object name link under the Display Name column to navigate to the Manage Mapping page.4. If you don't have an existing mapping, then click the Create Import Mapping button to create a mapping.5. On the Edit Import Mapping page, map the required by dragging them from the Target Attributes section to the

Source File section. Save the mapping when you are done.6. Click the link in the Mapping Number column of the required mapping.

Note: You can filter the mappings using the Find drop-down list.

7. On the Edit Import Mapping page, select Download Template from the Actions drop-down list.8. Save the template CSV file to a location on your desktop.

You must edit the template CSV file and provide valid values for the required attributes. The following is an example of a CSVfile for the Contact object.

PartyNumberAddress1 Address2 City State FirstName LastName OwnerPartyNumberSourceSystemSourceSystemReferenceValueCountry

Contact_1823894

212HerringtonBoulevard

Suite 10

FosterCity

CA

Dennis

Peattie

Party_7231354

CSV

CON_TST_OSR1_001

US

Contact_6546546

VisionCorporationAddress1

VisionCorporationAddress2

Palo Alto

CA

Steve

Braun

Party_4657978

DNB

CON_TST_OSR1_741

US



56

Creating the Import ActivityTo import data into Oracle Applications Cloud, you must create an import activity and provide the CSV file as a source to theactivity. To create an import activity, do the following:

1. Sign in as a setup user.2. In the Navigator, under Tools, click Import Management.3. On the Manage Imports page, click Create Import Activity.4. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select

Contact from the Object drop-down list.5. In File Name, browse and upload the required CSV file, and click Next.6. In the Create Import Activity: Map Fields page edit the attribute mappings if required, and click Next.

Note: Click Validate Data to validate the mapping of the source file for unmapped columns and tocheck for data format issues.

7. In the Create Import Activity: Review and Submit page, click Submit.

Reviewing the Import ResultsYou can review the import results by checking for the import activity in the Manage Import Activity page. A file import activityis said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:

1. Sign in as a setup user.2. In the Navigator, under Tools, click Import Management.3. On the Manage Imports page, search for the import activity that you created using one of the search criteria, such

as status, name, object, and so on.4. Check the Status column for the import activity. The import is successful if the status displays as Completed. The

other valid values for the import activity status are: Queued for import, Preparing data for import, Importingdata, Completed with errors, and Unsuccessful.

Note: On this page, you can also view quickly the number and status of all active imports, completedimports, and unsuccessful imports that have been submitted.


Chapter 8Importing Accounts and Contact Using File-Based Import

57

8 Importing Accounts and Contact Using File-Based Import

Account and Contact ImportYou import accounts and contacts in separate files, first the accounts and then the contacts.

Read the About Importing Accounts and Contacts topic and perform the steps outlined in the following table to completeaccount and contact import. You can open the different import tasks directly from the Import Accounts and Contacts folder inthe implementation project. Alternatively, you can search for the tasks by name from the Setup and Maintenance work area.


Register the Source System ofYour Data

Register the application that isthe source of your import data.This one-time setup creates thecode that you enter along withthe different reference IDs in allof your import files. Oracle permits you to importdata from multiple systems, sothe reference IDs alone don'tguarantee uniqueness.

Manage Trading CommunitySource Systems

See the Registering the SourceSystem of Your Customer Datatopic in this chapter.

Export Party ID for the Users youhave Created (AccountOwnerID)

Export Party ID for the users youhave created. You must use theParty IDs (AccountOwnerID) toidentify the resource you want tobe the account owner for eachaccount you import. Account owners see the accountin the list of My Accounts andare automatically members ofthe account team with privilegesto add others.

Schedule Export Processes

See the Exporting AccountOwner Party IDs topic in thischapter.

Specify the IndustryClassification for Accounts

If you plan to import industryclassification codes andyou do not want to usethe codes in the defaultCUSTOMER_CATEGORY,then you must set thesystem profile optionMOT_INDUSTRY_CLASS_CATEGORYto your category type.

You can use any one of thefollowing industry classification

Manage ClassificationCategories Manage Administrator ProfileValues

See the Specifying the IndustryClassification for Accounts topicin this chapter.



58


categories which are supplied byOracle with your application:

• 1972 SIC• 1977 SIC• 1987 SIC• CUSTOMER_CATEGORY• NACE• NAF• NAICS_1997• NAICS_2002

You can review the availablecodes for each of thesecategories using the ManageClassification Categories task.

Download a Template forImporting Your Data

In the Manage File ImportMappings work area, searchfor Account Create and UpdatePredefined Mapping anddownload the template from thismapping. The steps to download thetemplate are the same as thoseyou used for downloading thetemplates for importing usersand the sales catalog productgroups.

Manage File Import Mappings.

See the Downloading Templatesfor Importing Accounts andContacts topic in this chapter.

Understand the Account ImportTemplate

Review the template and thevalues each column in your filerequires for import. For example,the address data must matchthe geography reference datayou imported earlier. The Nokiageography data requires you tospell out in capital letters bothUS cities and states. Populate the template with yourdata and save it as a .csv file.

This task is done in your importfile.

See the Understanding theAccount Import Template topicin this chapter.

Add Additional Columns forImporting Additional Accountand Contact Attributes asRequired

Optionally, add additionalcolumns to the import file.

This task is done in your importfile.

See the Researching AdditionalAccount and Contact Attributesfor Import topic in this chapter.

If required, edit the seededmapping7

If you added columns to your file,then you must copy the seededmapping and edit the copy tomap them.

Manage File Import Mappings

See the Creating a NewMapping for a Changed ImportTemplate topic in this chapter.

Create an Import Activity toImport the Account Data

Import the file by creating animport activity.

Manage File Import Activities

See the Importing the Accountsand Contacts Files topic in thischapter.



59


Use these Same Steps to ImportContacts

Import contacts using the samesteps. This time you should usethe template you download fromthe Contact Create and UpdatePredefined Mapping.

• Manage File ImportMappings

• Manage File ImportActivities

See the Understanding theContact Import Template topic inthis chapter.

About Importing Accounts and ContactsAlthough you can create a few test accounts and contacts in the user interface, you may want to import some of your existingcustomer data to test the customer data management features.

About the Import ProcessTo import your account and contact data, you must complete the following steps for each object:

1. Download a template.2. Populate the template with your data.3. Add any additional columns you may need. This requires some research on your part.4. If you added any columns, then you must edit the mapping that prompts the application which import attribute is

mapped to what application attribute.

You cannot edit the mapping supplied by Oracle, so you must create a copy and add the additional columns to themapping copy.

5. Import the file.

Note: While importing your account and contact data, using a template is not required. However, using onesaves your time. Not only does the template include many of the common attributes for import, but it comes withits own predefined mapping. If you do not use the template, then you must map each attribute in your file to thecorresponding attribute in the application yourself.

Importing your account and contact data is complex because customer data such as addresses and contact points arestored in different objects in the application. This means that, in addition to the data itself, you are adding reference IDs intoyour file so the application can relate the data you import. For example, to import accounts and their contacts, you first importthe accounts and then use their reference IDs to import their contacts. The reference information you add to each object inthe file also permits you to update the information later, if required.

Information You Are Importing for AccountsIn Oracle Applications Cloud, you use accounts to import basic information about the companies and organizations importantto your business. This information appears in the Account Profile page in the UI.

• Organization name and basic profile information such as the CEO name and year the organization was established

• Industry classification

• Address

• Phone



60

• Fax

• URL

There are two types of accounts:

• Customer

Use this type when importing accounts you have sold to in the past.

• Prospect

Use this type if you have qualified a company or organization as a potential customer.

In your import file, you must specify one of these two account types for each record.

Information You Are Importing for ContactsFor contacts, you are importing the basic information about the contact which appears on the Edit Contact page. Thisincludes the name, address, phone, and other contact and address information.

About Importing Addresses for Accounts and ContactsOracle Applications Cloud stores addresses and other information you import as separate objects. When you import anaddress, for example, the application creates a location containing the address information, and a site, which provides the linkbetween the location and the account or contact. If you are importing a contact at an existing account address, you can:

• Import the address once with the account and share that address with the contact. This is the equivalent of selectingthe Use account address option when creating the contact in the UI. To do this, you import the address with theaccount information and reference the address in the contact import file using the location ID you entered in the



61

account import file. You can reference the account address in your contact import file by including the location IDyou imported for the account.

• You import the same address once for the account, and a second time for the contact. Doing so creates a duplicateaddress (two locations) and requires you to update two addresses in the future if there are changes, but does nototherwise affect the performance of your application.



62

You reference the objects such as the organization and the location using reference IDs you include in your import files. Thefollowing figure explains how you reference the account and its address in your contact import file.

Each object is identified by a unique ID, called the Original System Reference (OSR).

• The account import file includes IDs relevant to address import:

◦ The organization ID (Org.1)

◦ The ID for the location created from the address (Location1). In the account import template, you can find thisID in the AddressLocationOrigSystemReference column.

◦ The site ID (Site1) The site represents the link between the organization and the location. You can havemultiple sites because a single organization can have many locations.

• The contact import file includes IDs for the following:

◦ The ID of the organization the contact belongs. You enter the organization ID you imported in the accountimport file (Org.1)

◦ The contact (Contact1)

◦ The ID of the organization's location.(Location1). You enter the value you imported for accounts in theAddressLocationOrigSystemReference column.

◦ The site (Site2) This ID represents the link between the contact and the location. You can have multiplelocations for a contact.

Registering the Source System of Your Customer DataUse this procedure to register the source of the customer data you are importing by creating a source system. You use thecode you enter in the source system in all of your import files to identify the source of your data.

1. While signed in as a setup user, open the Manage Trading Community Source Systems task from theimplementation project. Alternatively, you can search for the task by name in the Setup and Maintenance work area.

The Manage Trading Community Source Systems page appears.2. From the Actions menu in the Search Results region, click Create.

The Create Source System page appears.3. In the Code field, enter the code you will use in your import files. For example, enter CDMSS.4. Enter a name. For example, enter Customer Data Source System.5. Make sure that Spoke is selected in the Type list.6. Select Enable for Trading Community Members.



63


Exporting Account Owner Party IDsThis topic describes how you can export the Party IDs (AccountOwnerIDs) that you need for importing account owners.

Follow these steps to obtain the Party IDs for the resources you created. You enter these IDs into your import file to identifyaccount owners.

1. While signed in as a setup user, open the Schedule Export Processes task from the implementation project.Alternatively, you can search for the task by name in the Setup and Maintenance Work area.

The Overview page appears.2. From the Actions menu, select Create.

The Create Export Process Definition: Enter Basic Information page appears.3. Enter a name for your export.4. Click Next.

The Create Export Process Definition: Configure Export Objects page appears.5. From the Actions menu, select Create.

The Manage Export Objects window appears.6. Scroll down to Party, select it, and use the right-arrow key to move it to the Selected Objects list.7. Click Done.

The Create Export Process Definition: Configure Export Objects page appears.8. Click Next.

The Create Export Process Definition: Create Schedule page appears. The schedule is set to run immediately afteryou activate.

9. Click Next.

The Create Export Process Definition: Review page appears.10. Click Activate.

The Overview page appears.11. When the process completes, click the file name in the Exported Data File column in the Export: History section and

save it to your desktop.12. When you are ready to populate the AccountOwnerId values in your import file, then do the following:

a. Open the file in a spreadsheet program such as Open Office or Excel.b. Search for each resource by their full name or scroll to the Name column (Column CS). The PartyID column

is located next to the Name column (Column CR). If the party ID appears in scientific notation, then you mustformat the column to display as a number with zero decimal places.



64

Specifying the Industry Classification for AccountsUse the following procedure to specify which industry classification category you want to use for accounts. The classificationsfor the category you select appear in the list of values for the Industry field in the Account user interface. By default, the profileis set to CUSTOMER_CATEGORY.

1. While signed in as a setup user, open the Manage Administrator Profile Values task from the implementation project.Alternatively, you can search for the task by name in the Setup and Maintenance work area.

The Manage Administrator Profile Values page appears.2. In the Search: Profile Option region, Profile Option Code field, enter MOT_INDUSTRY_CLASS_CATEGORY3. Click Search.4. Select the classification category from the Profile Value list. The available values are:

◦ 1972 SIC

◦ 1977 SIC

◦ 1987 SIC

◦ CUSTOMER_CATEGORY

◦ NACE

◦ NAF

◦ NAICS_1997

◦ NAICS_2002


Downloading Templates for Importing Accounts andContactsThis topic describes how you can download two templates provided by Oracle that you can use to import basic informationabout accounts and contacts.

Complete the following steps to download the template for importing data into Oracle Applications Cloud using file import:

1. Sign in as a setup user and open the Manage File Import Mappings task from the implementation project.

Alternatively, setup and master data management application administrator users can search for the task by name inthe Setup and Maintenance work area.

The Manage File Import Mappings page appears.2. In the Search region, select the object you want to import from the Object list. For example:

◦ For importing accounts, select Account.

◦ For importing contacts, select Contact.

3. Select the predefined option.4. Click Search.



65

5. Select the appropriate mapping. For accounts, click the Account Create and Update predefined Mapping name link.

The Edit Import Mapping page appears.6. Click Download Template.7. Save the template to your desktop.

Understanding the Account Import TemplateThis topic provides an overview of a data file created from the Account Create and Update Predefined Mapping templateprovided by Oracle for importing accounts.

Account Create and Update Predefined Mapping DetailsYou can use the Account Create and Update Predefined Mapping template you downloaded to import basic informationabout the organizations you do business with.

Account Template StructureThe template file includes a header row with the names of the attributes you map. The columns are arranged in the sameorder as the mapping in Oracle Applications Cloud.

The following figure shows the template structure. About half the columns in the template are attributes the application usesto uniquely identify the data you import. These attributes (shaded in gray) are the following:

• Original System (OS)

The first column in the template, AccountOrigSystem, identifies the source of your import data. For each row inyour file, you enter the code you created when you registered the source of your import using the Manage TradingCommunity Source Systems task. This value is the same for each row in your file unless you are importing your datafrom multiple systems.

• Original System Reference (OSR) columns

In each record, you must enter a unique ID in each of the <Object Name> OrigSystemReference columns. The IDs canbe either existing IDs from your legacy application or you can generate the IDs within Excel.

The template includes additional IDs for objects that Oracle Applications Cloud creates behind the scenes as part ofthe customer model. For example, when you import an address, the address creates a location and a site. You canhave many addresses, locations, and sites for each customer.

You must supply unique IDs for all of these attributes and keep your import file on hand, in case you decide toupdate the account information later.

Account Import Template AttributesSuppose you are trying to import accounts and contacts for a fictitious company, Vision Corp. The following table explainsthe account import template. It lists the columns in the account import template and explains what values you can import.



66

Column Description Sample Value Value required for the VisionCorp. example?

AccountOrigSystem

Enter the code you createdwhen you registered the sourceof your import using the ManageTrading Community SourceSystems task. This value is samefor each row in your file. If you leave this column blank,then the application usesthe default value CSV andgenerates a unique ID for theOrigSystemReference.

VISION

No

AccountOrigSystemReference

Enter a unique identifier andgenerates a unique ID for theOrig system reference for theaccount, this can be an ID fromyour source system, or you cangenerate a unique ID in Excel.

Vision_ Account1

Required only when OrigSystemis passed.

AccountName

Enter the organization name.

Pinnacle Technologies

Yes. Always required for creatingthe organization record.

DUNSNumber

The unique number assignedto an organization by Dun andBradstreet.

180020919

No.

ClassCategory1 For each record, enter the name

of the classification categoryyou are using in your applicationto identify the industry for youraccounts.

This value must be the same forall records.

You can enter one of thefollowing classificationcategories:

• 1972 SIC• 1977 SIC• 1987 SIC• CUSTOMER_CATEGORY• NACE• NAF• NAICS_1997• NAICS_2002

As described in a related topic,this name you enter here mustmatch the classification categoryyou specify in the profile optionMOT_INDUSTRY_CLASS_CATEGORY,using the Manage Administrator

1987 SIC

Required for Vision Corp.because it wants to use SalesPredictor to recommendproducts and generate leads byindustry.



67


Profile Values task from theSetup and Maintenance workarea.

This profile option determineswhich list of classificationsappears in the Industry field foraccounts.

ClassCategory2

Enter the name of the secondclassification category you areusing in your application toidentify the industry for youraccounts.

No

ClassCode1

You must enter one of theclassification codes for theclassification category youspecified. You can obtain alist of the codes using thesame Manage ClassificationCategories, Setup andMaintenance task.

2752

Required if you specified aclassification category for therecord.

ClassCode2

Enter the second classificationcode for the classificationcategory you specified.

No.

AccountOwnerId Party ID of the resource you

want to list as the AccountOwner. You must obtain this IDfrom Oracle Applications Cloud.

Being an account owner meansthat you:

• See the account in the listof My Accounts

• Are automaticallyassigned as a member ofthe Account Team withprivileges to add others.

Account owners cannot beassigned or reassigned by salesterritories.

12789

Yes. If you leave this field blank, thenownership is assigned to theuser who is doing the import.

AccountType

Specifies if the account you areimporting is a customer or aprospect. Valid values are:ZCA_CUSTOMER andZCA_PROSPECT If you do not enter a value,the application automatically

ZCA_CUSTOMER

Yes. Vision Corp. is importingonly accounts of type customer,so the values is alwaysZCA_CUSTOMER.



68


supplies the value ofZCA_PROSPECT. You can change this defaultby setting the account profileAccount Type Default (ZCA_DEFAULT_ ACCOUNT_TYPE) toCustomer.

Address1

Enter the first line of the address.

600 4th Ave

No.

Address2

Enter the second line of theaddress, if any.

Suite 400

No.

Address3

Enter the third line of theaddress, if any.

Office 4B020

No.

City

Enter the city in the formatexpected by the geographyreference data you imported. The Nokia data for the UnitedStates expects the city names tobe spelled out all in capitals.

IRVINE

No.

State

Enter the state in the formatexpected by the geographyreference data you imported. The Nokia data for the UnitedStates expects the states to bespelled out all in capitals.

CALIFORNIA

Required for this use case. The Vision Corp. sales territoriesdescribed in this guide are setup based on state. If a state ismissing in your data, then therecord is assigned to the firstterritory up the territory hierarchythat does not specify a state.

County

Enter the county in the formatexpected by the geographyreference data you imported. The Nokia data for the UnitedStates expects the city names tobe spelled out all in capitals.

Orange

No.

Province

Enter the Province in the formatexpected by the geographyreference data you imported. The Nokia data for the UnitedStates expects the city names tobe spelled out all in capitals.

No.

Zip/PostalCode

Enter the postal code for theaccount's address.

19102

No.



69


CountryCode

Enter the two-letter country codefor the account address. You can view the list of countriesand their country codes usingthe Manage Geographies, Setupand Maintenance task.

US

Yes. If you are importing addressesin countries other than the US,you may have to add differentaddress columns to the importfile, depending on the format ofthat country's address.

SiteUseTyp

Enter the lookup code thatrepresents the purpose for theaddress association, a sell-toaddress or a bill-to address.

SELL_TO

N.

AddressLocationOrigSystemReference

Enter a unique identifier for theaddress location, this can be anID from your source system, oryou can generate a unique ID inExcel.

Account_ Address_ Location1

Yes.

AddressSiteOrigSystemReference

Enter a unique identifier for theaddress site, this can be an IDfrom your source system, oryou can generate a unique ID inExcel.

Account_ Address_Site1

Yes.

PhoneCountryCode

Enter the country code for thephone number.

1

No.

PhoneNumber

Enter the phone number withoutany delimiters or spaces.

No.

PhoneOrigSystemReference

Enter a unique identifier for thephone number. You can use an existing ID, oryou can generate the ID in Excel.

Account_Phone1

Required if you are importing aphone number.

URL

Enter the URL.

http: / /pinnacletechnologiescom

No.

UrlOrigSystemReference

Enter a unique identifier for theURL. You can use an existing ID, oryou can generate the ID in Excel.

Required if you are importing aURL.



70

Understanding the Contact Import TemplateThis topic provides an overview of a contact import data file prepared from the Contact Create and Update PredefinedMapping template provided by Oracle.

Contact Create and Update Predefined Mapping DetailsJust like the template you used to import accounts, the Contact Create and Update Predefined Mapping template includesa header row with columns that map to the attributes in the application. The columns are arranged in the same order as themapping in Oracle Applications Cloud. You can add additional attributes to the file by appending them after the last column.In case you add additional attributes, you must copy and modify the seeded mapping to create a modified mapping thatincludes these additional attributes.

Contact Import TemplateIn your import file, you must provide the contact's first and last names, and you must identify the account where the individualis a contact by entering the values you entered in the AccountOrigSystem and AccountOrigSystemReference columns of youraccount import file.

You must also supply the reference information for any additional information you import.

The following table lists the commonly used attributes of the contact import template in the order they are included in thetemplate.

Column Description Sample Value Value required for use case?

ContactOrigSystem

The code you create using theManage Trading CommunitySource Systems task. If you leave this column blank,then the application uses thedefault value CSV and generatesa unique ID for the Orig systemreference.

VISION

Default value.

ContactOrigSystemReference

A unique identifier for the record.This can be an existing ID, or youcan generate this ID in Excel.

Vision_ Contact1

Required only when Orig systemis passed.

Title

Contacts title such as Mr, Mrs,or Ms

Ms

No.

FirstName

Contact's first name.

Dennis

Yes.

LastName

Contact's last name.

Peattie

Yes.

Type

Enter Customer (ZCA_CUSTOMER) if you haveyou have sold to the contactin the past. Enter Prospect

ZCA_CUSTOMER

Yes. Vision Corp. is importingonly contacts of type customer,so the value is alwaysZCA_CUSTOMER.



71


(ZCA_ PROSPECT) if you havequalified a contact as a potentialcustomer.

OwnerId

Address1

The first line of the contact'saddress.

212 Herrington Boulevard

No.

Address2

The second line of the contact'saddress.

Suite 10

No.

Address3

The third line of the contact'saddress.

Office 2B020

No.

City

The city in the format expectedby the geography reference datayou imported. The Nokia data for the UnitedStates expects the city names tobe spelled out all in capitals.

FOSTER CITY

No.

State

The state in the same format asthat expected by the geographyreference data you imported. The Nokia data for the UnitedStates expects the states to bespelled out all in capitals.

CALIFORNIA

No.

County

Enter the county in the formatexpected by the geographyreference data you imported. The Nokia data for the UnitedStates expects the city names tobe spelled out all in capitals.

Province

Enter the province in the formatexpected by the geographyreference data you imported. The Nokia data for the UnitedStates expects the city names tobe spelled out all in capitals.

Zip/PostalCode

The postal code of the contact'saddress.

94356

No.

Country

The country code of thecontact's country.

US

No.



72


AddressLocationOrigSystemReference

A unique identifier for thelocation that is createdautomatically whenever youimport an address. You can use an existing ID, oryou can generate the ID in Excel.

Vision_ Contact_ Address1

Required if you are importingaddress information. To link the contact to theaddress you importedfor the organization, thenyou copy the ID youentered in the organizationAddressLocationOrigSystemReferencefield.

AddressSiteOrigSystemReference

A unique identifier for the sitethat is created automaticallywhenever you import anaddress. You can use an existing ID, oryou can generate the ID in Excel.

Required if you are importing anaddress.

WorkPhoneCountryCode

The country code.

1

No.

WorkPhoneNumber

The phone number without anydelimiters or spaces.

5551212

No.

WorkPhoneOrigSystemReference

A unique identifier for the phonenumber. You can use an existing ID, oryou can generate the ID in Excel.

Vision_ Contact1_ Phone1

Required if you are importing aphone number.

MobileCountryCode

The country code.

1

No

MobileNumber

The phone number without anydelimiters or spaces.

3335555

No

MobileOrigSystemReference

A unique identifier for the phonenumber. You can use an existing ID, oryou can generate the ID in Excel.

Vision_ Contact1_ Mobile1

Required if you are importing amobile phone number.

EmailAddress

Contact e-mail.

Dennis. [email protected]

EmailOrigSystemReference

A unique identifier for the e-mail. You can use an existing ID, oryou can generate the ID in Excel.

Vision_ Contact1_ Email1

Required if you are importing anE-Mail.

AccountOrigSystem

The source system code for theaccount.

VISION

Yes.

AccountOrigSystemReference

TheAccountOrigSystemReference

Vision_ Account1

Yes.



73


for the account associated withthe contact.

AccountId

Alternate ID that you canexport and use instead of theAccountOrigSystemReference.

Leave blank. You are usingAccountOrigSystemReference.

You can import additional attributes to a contact by appending attributes to the import file. For more information aboutappending additional attributes for import, see the topic Appending Additional Attributes for Import in this chapter.

Researching Additional Account and Contact Attributes forImportThis topic explains how you can obtain information about additional attributes to include in your import file for accounts andcontacts. To import an additional field you see in the UI, for example, you must first obtain the technical field name and thenfind out what values that field expects.

Finding the Technical Name of a UI FieldTo import fields in the UI, you must first find the technical name of the field using Application Composer using the followingsteps:

1. While signed in as a setup user, click the Application Composer link under the Tools heading in the Navigator.

The Application Composer page appears.2. Expand the Standard Objects for the Common application and select the Fields link for the object you want to

research.

The UI fields and their technical names are listed on the Standard tab. You can filter the fields by name.



74

The following figure shows the UI fields and their technical names listed on the Standard tab. You can filter the fieldsby name.

3. In addition to the technical name of the field, you must determine the import object the field belongs to. You can findthe import object by viewing an existing file import mapping and searching the lists of attributes for the most likelyobjects.

a. In the Setup and Maintenance work area, search for the Manage File Import Mappings task.b. Search for the predefined mappings for the Account or Contact object.c. Click the Account Create and Update Predefined Mapping or the Account Create and Update Seeded

Mapping link.d. On the Edit Import Mapping page, click Copy Mapping.e. In the Column Mapping region, look for an object with similar fields. The Academic Title field, for example, is a

property of the person, so this field most likely belongs to the PersonProfile object.f. Click the down arrow to the right of the Target Attribute to display the list of objects, and then click Search.

The Search and Select: Attribute window appears.g. Search for the attribute using the technical name, for example: PersonAcademicTitle, to verify the attribute

exists for the object you selected.h. Cancel out of the window and the Edit Import Mapping page when you are done as you do not want to

update the mapping.

Researching Available Account and Contact AttributesYou can research additional account and contact group attributes for import using the File Based Data Import for OracleSales Cloud guide available on Oracle Help Center (http://docs.oracle.com).

In the File Based Data Imports chapter, see the Account Import and Contact Import topics. These topics include links to filescontaining the information about the available attributes.

Related Topics

• File Based Data Import for Oracle Sales Cloud guide

https://docs.oracle.com/cloud/latest/common/OEFBS/



75

Creating a New Mapping for a Changed Import TemplateThis topic describes how you can add an additional contact field you want to import to the seeded Contact Create andUpdate Mapping provided by Oracle and how to import your data file with that additional field. This example shows how toupdate existing contact information, but you can use this method for importing new contacts as well.

If you have added additional columns to your import file, then you must also add them to the mapping you use during import.You do this by copying the existing mapping and then editing the copy. You select this new mapping when importing the file.

1. While signed in as a setup user, open the Manage File Import Mappings task from the implementation project.Alternately, search for the task by name In the Setup and Maintenance work area.

The Manage File Import Mappings page appears.2. Select Account from the Object list.3. Select the Seeded option.4. Click Search.5. Select the row with the mapping you want to copy. In this example, you select either Account Create and Update

Predefined Mapping or Contact Create and Update Predefined Mapping.6. From the Actions menu, select Copy Mapping.

The application creates a new mapping in the background. The default name starts with the words Copy of andends with today's date.

7. Deselect the Seeded option.8. Click Search again.

The application displays the copied mapping.9. Click the mapping name link.

The Edit Import Mapping page appears.10. Enter a new name in the Import Mapping field so your new mapping is easy to find when you import.11. Scroll down to the end of the Column Mappings and place your cursor in the last row. Make a note of the Sequence

number.12. For each additional attribute you have in your file:

a. Click Create (the green plus sign icon)

The application creates a new row.b. Enter the sequence number. This should be a number greater than the last row in the template.c. Enter the column header you are using in your file.d. Enter a sample value. This value is only for information.e. In the Target column, select the Object and the Attribute.




76

Importing the Accounts and Contacts FilesYou import the CSV files with your account and contact data by creating and activating an import activity. The process ofimporting these files is the same. The only difference is the import object and mapping you select. You must import the filewith account data before you import the contact data.

1. While signed in as a setup user, open the Manage File Import Activities task from the implementation project.Alternately, search for the task by name in the Setup and Maintenance work area.

The Manage Import Activities page appears.2. Click Create.

The Create Import Activity: Enter Import Options page appears.3. In the Name field, enter a name for your import activity.4. From the Objects list, select Account.5. In the Source File Upload From region, select Desktop.6. Click Browse and select your import file.7. The delimiter for the template import file is Comma separated, the default selection from the Data Type list.8. Select the Header row included option because the file includes a header.9. From the Import Mapping list, select a mapping. If you have not made any modifications to the Predefined mapping,

select Account Create and Update Seeded Mapping or Contact Create and Update Predefined Mapping.10. Click Next.

The Create Import Activity: Map Fields page appears.

The Map Fields region displays the mapping you selected.11. Click Next.

The Create Import Activity: Schedule page appears.12. Click Next.

The Create Import Activity: Review and Activate page appears.13. Click Activate.

You can monitor the progress of the import activity and view completion reports for both successful records and errors byselecting the import activity in the Manage File Import Activities page.

Troubleshooting Common Import ErrorsThe following table provides troubleshooting tips for common import errors. You can view the errors by downloading the errorlog from the import activity.

Error Description Troubleshooting Tips

A matching record of type RESOURCEcannot be found using the value of theattribute RESOURCE_ID that you provided.(MKT-285218) Cause: No record exists

The Party ID you used for the account ownerwas not valid.

Check the Party ID for the resource in the fileyou exported.



77

Error Description Troubleshooting Tips

with the specified user key value. Action:Verify that the record with the specified userkey exists. If it does not exist, then removethe record from the data file, or update therecord with a valid user key.

The combination of columns PARTY_ORIG_SYSTEM and PARTY_ ORIG_SYSTEM_ REFERENCE must be unique.

You included duplicateAccountOrigSystemReference orContactOrigSystemReference ID in the samefile.

Remove the duplicates.

An OSR value used in this batch alreadyexists in one of the parallel batches that iscurrently being processed.

You have more than one process trying toimport the same records.

Wait for a process to complete beforeinitiating another one.

HZ_ IMP_ PARTY_ NAME_ERROR - Youmust enter a party name.

When you are creating a new organization,you must enter the account name in theAccountName column.

You are most likely to see this error whenyou are trying to update existing accountor contact information. The original system(OS) and original system reference (OSR)information you entered does not resolveto any existing account or contact, so theapplication assumes you are trying to createa new one.

At least one of the required name fields inthe HZ_ IMP_ PARTIES_ T table is missing avalue.

When creating contacts, you must enter thefirst or last names, or both (FirstName andLastName columns).

Errors that start with: The process fails toload data into import interface tables. Cause:java. lang. Exception: StagingLoader. load()exception thrown in find VO.

You may not have checked the header rowincluded box, so the application treats theheader row as a regular data row.

Rerun the import with the header row optionchecked.

fails on the target @ ORACLE connectionORACLE_ FUSION. @ Caused By: java. sql.SQLSyntaxErrorException: ORA-01722:invalid number

Data type in your import file does not matchthe data type expected in the application.For example, a number cannot includecharacters such as - or /.

Check your import file data.

A matching record of type ContactEmailcannot be found using the value of theattribute for EmailType that you provided.(MKT-285218) Cause: No record exists withthe specified user key value. Action: Verifythat the record with the specified user keyexists.

The error appears when information aboutthe parent object you are importing doesnot exist for a child object. For example, Ifyou are importing a contact E-mail, then youmust include the OS and OSR for the contactin the same row of your file.

Verify that each row contains the account orcontact OS and OSR pairs.



78


Chapter 9Importing Accounts and Contacts Using Simplified View

Import Objects

79

9 Importing Accounts and Contacts UsingSimplified View Import Objects

Importing Data Using Simplified View Import Objects:OverviewFile-based data import using the simplified view import objects removes the step of complex manual mapping byautomatically mapping the source import file data to the target import objects and attributes.

You can import a wide range of data using file-based data import to create, update, or delete application records. Simplifiedview import objects are currently available for Accounts and Contacts.

The simplified view import objects let you import your account and contact data into Oracle Applications Cloud using filesin .zip file. You can use these objects to import all object-related data in the form of a .zip file. The .zip file includes data aboutthe business object and its child objects. If you use automatic import mapping, then the application automatically maps thesource file columns to the target objects and target attributes for the object being imported. You can avoid manually mappingthe attributes.

Importing Contacts Using the Contact - Simplified ViewImport Object: ProcedureYou can import contact data into Oracle Applications Cloud using the Contact-Simplified View import object. You can use theobject to create, update, or delete contact records.

The Contact-Simplified View object is hierarchical. The root of the hierarchy is the Contact-Simplified View object that includesbasic information about the contact. It contains the following child objects:

• Sales Cloud Address: Includes detailed location information for a contact. If the profile option codeZCA_ACCOUNT_ADDRESS_REQUIRED_ENABLED is set as Yes at site level, then you must provide addressinformation.

• Sales Cloud Classification: Includes classification information that is used to categorize a contact.

• Sales Cloud Relationship: Includes the relationship information of a contact with other entities, or parties.

• Sales Cloud Team Member: Includes the team member information of a contact.

• Sales Cloud Attachment: Includes the attachment information of a contact.

• Additional Name: Includes the additional names of a contact.

• Raw Phone Number: Includes the phone number information such as country code, area code, and so on.

To import contacts using the Contact-Simplified View import object, you must:

1. Create CSV files with the import data2. Create an import activity



Import Objects

80

Create CSV files with the import dataOracle Applications Cloud lets you import your contact data in CSV format. You can include contact and its child objects'information in CSV files, and import them as a ZIP file. You must include a CSV file each for contact and its child objects.

The columns in the CSV files indicate the attributes you can import for each object. To import records, your source file mustinclude the attributes that enable the import process to identify these records. The File Import process uses these columnnames to automatically map your source data to the attributes in Oracle Applications Cloud.

You must understand the following before populating the templates:

• Identifiers: Identifiers of a record let you reference the record when you want to update the record. OracleApplications Cloud generates an internal identifier for each new record. However, Oracle recommends that youprovide the origin system and origin system reference (OS/OSR) information when you are creating a record. TheOS/OSR information is used to update a record, as well as or to associate another record with it. For example, youcan use the OS/OSR information of a contact record to update the contact information, or to create a new addressfor the contact. If you are updating a child resource, then you must provide the identifier information of the child andits parent. For example, to update an address of a contact you must provide the identifier information of the contactand the address. You can also use a record's internal ID to refer to a record. A record's internal ID, or object key, istypically its row ID in the Oracle Applications Cloud database. The internal ID is a system-generated unique identifierwith an attribute name, such as PartyId, RelationshipId, or PartySiteId. However, to determine the internal ID youmust export the object from the Oracle Applications Cloud Database.

• Prerequisite Setup Tasks: Some attributes are dependent on other attributes or list of values for their values.Similarly, some attributes require that certain options in the application are set before you can populate them. Forexample, an origin system of a contact that you are importing should be enabled for parties in the Manage TradingCommunity Source Systems task.

• Parent Records: When importing a child record, ensure that its parent record exists in the database. For example,when importing the address of a contact, ensure that its parent contact exists in the database. You can import newparent and child records in the import activity. You must ensure that the new child record in the import file shouldrefer to the parent using its identifier. For example, you can import a new contact in the contact import CSV file anda new address in the address import CSV file. In this case, the address import file should include a reference to theparent record in the contact import file.

You must also be aware of the following to be able to successfully populate the import templates:

• Required attributes while importing new records

• Required attributes while updating records

• Prerequisite setup tasks for attributes, if any.

The following table lists the required attributes for importing the Contact object.

Required Attributes Description Prerequisite Setup Task Create Contact Update Contact

ObjectKey

The Oracle ApplicationsCloud record ID for theparty (account, contact,household, or legal entity)to which the personprofile belongs.

Identify the ObjectKeyvalue by exporting theParty object using theSetup and Maintenance,Manage Bulk DataExport, Schedule ExportProcesses task.

Not required. Conditionally required.

Provide referenceinformation to identifythe existing party. Thereference information canbe:

• ObjectKey (OracleSales Cloudrecord ID).



Import Objects

81


• SourceSystemandSourceSystemReferenceValue(source systemcode and sourcesystem referencevalues) providedwhen importingthe organizationprofile.

• PartyNumber(public uniqueidentifier for anorganizationprofile).

• A business keysuch as personname.

SourceSystem

The code representingthe external sourcesystem for the party(account, contact,household, or legal entity)to which the personprofile belongs.

Identify the sourcesystem or configuresource systems eitherby using the ManageTrading CommunitySource System task, orby importing the sourcesystem information intoOracle Sales Cloudusing the Source SystemReference import object.

Conditionally required.

Provide referenceinformation to createcontact. The referenceinformation can be:

• SourceSystemandSourceSystemReference.

• Party Number



• SourceSystemandSourceSystemReferenceprovided whenimporting thecontact.

• Party Number• ObjectKey

SourceSystemReference

The reference numberor text representing thesource system unique IDfor the party (account,contact, household, orlegal entity) to which theperson profile belongs.



Provide referenceinformation to createcontact. The referenceinformation can be:

• SourceSystemandSourceSystemReference.

• Party Number



• SourceSystemandSourceSystemReferenceprovided whenimporting thecontact.

• Party Number• ObjectKey

OwnerEmailAddress

The e-mail address ofthe resource that ownsand manages the salesaccount to which thecontact is associated.

Identify the party IDand party number ofthe owner by exportingthe Party object usingSetup and Maintenance,Manage Bulk Data

Conditionally required. Conditionally required.

By default, the userimporting the contact isdesignated as the owner.



Import Objects

82


Export, Schedule ExportProcesses task.

Specify an owner, byincluding one of followingreference information:

• OwnerEmailAddress• OwnerPartyId• OwnerPartyNumber

To specify a differentowner, include one ofthe following referenceinformation:


OwnerPartyId

The unique identifier of avalid employee resourcewho owns and managesthe sales account towhich the contact isassociated.

Identify the party IDand party number ofthe owner by exportingthe Party object usingSetup and Maintenance,Manage Bulk DataExport, Schedule ExportProcesses task.








OwnerPartyNumber

The party number of avalid employee resourcewho owns and managesthe sales account towhich the contact isassociated.

Identify the party IDand party number ofthe account owner byexporting the Partyobject using Setupand Maintenance,Manage Bulk DataExport, Schedule ExportProcesses task.








FirstName

The first name of a party.

No prerequisite tasks

Required.

Not required.

LastName

The last name of a party.

No prerequisite tasks

Required.

Not required.

The following table lists the attributes required to import Address object.

Attribute Description Prerequisite Setup Task Create Address Update Address

PartyId

The Oracle Sales Cloudinternal ID for the contactto which the addressbelongs.

Identify the party IDand party number valueby exporting the Partyobject using the Setupand Maintenance,Manage Bulk Data




Import Objects

83



Provide referenceinformation to identify thecontact:

• PartyId.• PartySourceSystem

andPartySourceSystemReferenceValueprovided in theSalesCloudContactCSV file.

• Party Number.




• Party Number.

PartyNumber

The public uniqueidentifier for the contactto which the addressbelongs.

Identify the party IDand party number valueby exporting the Partyobject using the Setupand Maintenance,Manage Bulk DataExport, Schedule ExportProcesses task.





• Party Number.





• Party Number.

PartySourceSystem

The code representingthe source system for thecontact.






• Party Number.





• Party Number.

PartySourceSystemReferenceValue

The reference numberor text representing thesource system unique IDfor the contact.












Import Objects

84


• Party Number. • Party Number.

Country

The country codecomponent of theaddress.

Identify valid countrycodes using the Setupand Maintenance,Manage Territories task.

Required.

Required.

LocationId

The unique ID for theexisting location recordin the Oracle Sales Clouddestination table.

Identify theLOCATION_ID for anexisting location byexporting the Locationobject using the Setupand Maintenance,Manage Bulk DataExport, Schedule ExportProcesses task.


Provide any of thefollowing referenceinformation to identify theaddress:

• LocationId.• SiteNumber.• AddressSourceSystem

andAddressSourceSystemReference.

AddressSourceSystem

The code representingthe source system for theaddress.



Provide the sourcesystem and sourcesystem reference valuesif you intend to importupdates to previouslyimported records fromthe same system.

• SiteNumber.• AddressSourceSystem






AddressSourceSystemReference

The reference numberor text representing thesource system unique IDfor the address.










Site Number

The public uniqueidentifier for the address.

Identify the addressnumber value byexporting the Partyobject using the Setupand Maintenance,Manage Bulk Data


Provide any of thefollowing reference



Import Objects

85



information to identify theaddress:



AddressType

The type of the address.You can define multipleaddress types for anaddress.

A list of valid values isdefined in the lookupPARTY_ SITE_ USE_CODE. Review andupdate the codesusing the Setup andMaintenance workarea, Manage StandardLookups task.

Required.

Not required.

The following table lists the attributes required for importing the Classification object for Contact.

Attribute Description Prerequisite Setup Task Create Classification Update Classification

PartyId

The Oracle Sales Cloudinternal ID for the contactto which the classificationbelongs.


Required.




• Party Number.

Required.




• Party Number.

PartyNumber

The public uniqueidentifier for the contactto which the classificationbelongs.


Required.




• Party Number.

Required.




• Party Number.

PartySourceSystem


Identify the sourcesystem or configuresource systems eitherby using the Manage

Required. Required.



Import Objects

86


Trading CommunitySource System task




• Party Number.




• Party Number.



Identify the sourcesystem or configuresource systems eitherby using the ManageTrading CommunitySource System task

Required.




• Party Number.

Required.




• Party Number.

SourceSystem

SourceSystem: Thecode representing thesource system for theclassification.


Required. Provide the sourcesystem and sourcesystem reference values.


Provide the referenceinformation to identify theclassification.

• ObjectKey.• SourceSystem

andSourceSystemReference.


SourceSystemReference:The reference numberor text representing thesource system unique IDfor the classification.


Required. Provide the sourcesystem and sourcesystem reference values.


Provide the referenceinformation to identify theclassification.

• ObjectKey.• SourceSystem

andSourceSystemReference.

ClassificationCode

The classificationcategory withinclassification category.

The classification andclassification codeshould be valid for theclassification category.Review the classificationsand classification codes,using the Manage

Required.

Required.



Import Objects

87


Classification Categories,Setup and Maintenancetask.

ClassificationCategory

The classification codewithin classificationcategory.

The classification andclassification codeshould be valid for theclassification category.Review the classificationsand classification codes,using the ManageClassification Categories,Setup and Maintenancetask.

Required.

Required.

The following table lists the attributes for Relationship object.

Attribute Description Prerequisite Setup Task Create Relationship Update Relationship

RelationshipId

The internal ID for therelationship.

Identify the relationshipID by exporting theParty object using theSetup and Maintenance,Manage Bulk DataExport, Schedule ExportProcesses task.


Provide referenceinformation to identify therelationship:

• RelationshipId.• RelationshipSourceSystem

andRelationshipSourceSystemReference.

RelationshipSourceSystem

A source system codethat identifies the originalsource system of therelationship between theobject and the subjectparties.


Required. Conditionally required.




RelationshipSourceSystemReference

A source systemreference that identifiesthe original referenceID of the relationshipbetween the object andthe subject parties in thesource system.






SubjectPartyId

The Oracle Sales Cloudinternal ID for the contact

Identify the party IDand party number valueby exporting the Party




Import Objects

88


to which the classificationbelongs.

object using the Setupand Maintenance,Manage Bulk DataExport, Schedule ExportProcesses task.


• SubjectPartyId• SubjectSourceSystem

andSubjectSourceSystemReferenceprovided in theSalesAccountCSV file.

• SubjectPartyNumber





SubjectPartyNumber













SubjectSourceSystem













SubjectSourceSystemReference













Import Objects

89


• SubjectPartyNumber • SubjectPartyNumber

RelationshipType

Describes the directionalconnection betweenthe object and subjectrelationship. For example,Employer of versesEmployee of.

You can view therelationship type andrelationship type codedefinition from the Setupand Maintenance,Manage RelationshipTypes task.

Required.

Not required.

RelationshipCode

Describes therelationship, such asContact or Membership.


Required.

Not required.

The following table lists the attributes required to import Team Member object for Contact.

Attribute Description Prerequisite Setup Task Add Team Member Update Team Member

PartyId

The Oracle Sales Cloudinternal ID for the contactto which the classificationbelongs.






• Party Number.




andPartySourceSystemReferenceValueprovided in theSalesAccountCSV file.

• Party Number.

PartyNumber







• Party Number.





• Party Number.

PartySourceSystem


Identify the sourcesystem or configuresource systems eitherby using the Manage




Import Objects

90


Trading CommunitySource System task




• Party Number.




• Party Number.








• Party Number.





• Party Number.

ResourceId

The Oracle Sales Cloudinternal ID for sales teammember.

Identify the resource IDand resource numbervalue by exporting theParty object using theSetup and Maintenance,Manage Bulk DataExport, Schedule ExportProcesses task.

Not Required. Conditionally required.

Provide referenceinformation to identify theresource team member:

• ResourceId• ResourcePartyNumber

ResourcePartyNumber

The public uniqueidentifier for the salesteam member.





Create Import ActivityYou use the Manage File Import Activities task to create import activities. It consists of a step by step guided process toassist you with creating an import activity for a given object.

1. Sign in as a setup user and navigate to the Setup and Maintenance work area.2. Search for and select the Manage File Import Activities task.3. On the Manage File Import Activities page, click the Create icon.



Import Objects

91

4. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select theContact-Simplified View object from the Object list.

5. Select ZIP file from the File Type list, check the Desktop option, and browse and upload the required ZIP file.6. To add attachments, under Attachments section, browse and upload your file. The attachment must be in ZIP

format.

Note: Ensure that you have the following columns and the required values in theSalesCloudContact.csv file:

Column Name Expected Value

ATTACHMENT_ FILE_NAME

The file name with extension. For example, Sales.jpg.

ATTACHMENT_ FILE_DESC

The description of the file.

ATTACHMENT_ FILE_TITLE

The title of the file.

ATTACHMENT_ CATEGORY_NAME

The category of the file. For example, MISC.

7. Click Next.8. In the Create Import Activity: Create Schedule page, select an appropriate scheduling option from the Schedule list.9. Click Next.

10. On the Create Import Activity: Review and Activate page, click Activate to activate the import activity immediately, orclick Save and Close if you want to use the import activity later.

Importing Accounts using the Account - Simplified ViewImport Object: ProcedureYou can import account data into Oracle Applications Cloud using the Account-Simplified View import object. You can usethe object to create, update, or delete account records.

The Account-Simplified View object is hierarchical. The root of the hierarchy is the Account-Simplified View object thatincludes basic information about the account. It contains the following child objects:

• Sales Cloud Address: Includes detailed location information for an account. If the profile option codeZCA_ACCOUNT_ADDRESS_REQUIRED_ENABLED is set as Yes at site level, then you must provide addressinformation.

• Sales Cloud Classification: Includes classification information that is used to categorize an account.

• Sales Cloud Relationship: Includes the relationship information of an account with other entities, or parties, such ascontacts, households, and so on.

• Sales Cloud Team Member: Includes the team member information of an account.

• Sales Cloud Attachment: Includes the attachment information of an account.

• Additional Name: Includes the additional names of an account.

• Raw Phone Number: Includes the phone number information such as country code, area code, and so on.



Import Objects

92

To import accounts using the Account-Simplified View import object, you must:

1. Create CSV files with the import data2. Create an import activity

Create CSV files with the import dataOracle Applications Cloud lets you import account data in CSV format. You can include account and its child objects'information in CSV files, and import them as a ZIP file. You must include a CSV file each for account and its child objects.

The columns in the CSV files indicate the attributes you can import for each object. To import records, your source file mustinclude the attributes that enable the import process to identify these records. The File Import process uses these columnnames to automatically map your source data to the attributes in Oracle Applications Cloud.

You must understand the following before populating the templates:

• Identifiers: Identifiers of a record let you reference the record when you want to update the record. Oracle SalesCloud generates an internal identifier for each new record. However, Oracle recommends that you provide the originsystem and origin system reference (OS/OSR) information when you are creating a record. The OS/OSR informationis used to update a record, as well as or to associate another record with it. For example, you can use the OS/OSRinformation of an account record to update the account information, or to create a new address for the account. Ifyou are updating a child resource, then you must provide the identifier information of the child and its parent. Forexample, to update an address of an account you must provide the identifier information of the account and theaddress. You can also use a record's internal ID to refer to a record. A record's internal ID, or object key, is typicallyits row ID in the Oracle Applications Cloud database. The internal ID is a system-generated unique identifier with anattribute name, such as PartyId, RelationshipId, or PartySiteId. However, to determine the internal ID you must exportthe object from the Oracle Sales Cloud Database.

• Prerequisite Setup Tasks: Some attributes are dependent on other attributes or list of values for their values.Similarly, some attributes require that certain options in the application are set before you can populate them. Forexample, an origin system of an account that you are importing should be enabled for parties in the Manage TradingCommunity Source Systems task.

• Parent Records: When importing a child record, ensure that its parent record exists in the database. For example,when importing the address of an account, ensure that its parent account exists in the database. You can importnew parent and child records in the import activity. You must ensure that the new child record in the import fileshould refer to the parent using its identifier. For example, you can import a new account in the account import CSVfile and a new address in the address import CSV file. In this case, the address import file should include a referenceto the parent record in the account import file.

You must also be aware of the following to successfully populate the import templates:

• Required attributes while importing new records

• Required attributes while updating records

• Prerequisite setup tasks for attributes, if any.

The following table lists the attributes required to import the Account object.

Required Attributes Description Prerequisite Setup Task Create Sales Account Update Sales Account

SourceSystem

The code representingthe source system for thesales account.

Identify the sourcesystem or configuresource systems eitherby using the ManageTrading CommunitySource System task, orby importing the source

Conditionally required Provide the sourcesystem and sourcesystem reference valuesif you intend to importupdates to previously

Conditionally required

Provide referenceinformation to identifythe existing party. The



Import Objects

93


system information intoOracle Sales Cloudusing the Source SystemReference import object.

imported records fromthe same system.

reference information canbe:

• SourceSystemandSourceSystemReferenceprovided whenimporting thesales account.

• Party Number


The reference numberor text representing thesource system uniqueID for the party (accountor contact) to which thesales profile belongs.


Conditionally required Provide the sourcesystem and sourcesystem reference valuesif you intend to importupdates to previouslyimported records fromthe same system.



• SourceSystemandSourceSystemReferenceprovided whenimporting thesales account.

• Party Number

OwnerEmailAddress

The e-mail address ofthe resource that ownsand manages the salesaccount.



Specify an accountowner, by including oneof following referenceinformation:

• Email Address ofthe account owner

• Party ID of theaccount owner inthe OwnerPartyIdcolumn.

• Party Numberof the accountowner in theOwnerPartyNumbercolumn.


By default, the userimporting the accountis designated as theaccount owner.

To specify a differentaccount owner, includeone of the followingreference information:




OwnerPartyId

The unique party ID ofthe resource assigned tomanage the sales profile.

Identify the party IDand party number ofthe account owner byexporting the Partyobject using Setupand Maintenance,Manage Bulk Data


Specify an accountowner, by including one


By default, the userimporting the accountis designated as theaccount owner.



Import Objects

94



of following referenceinformation:








OwnerPartyNumber

The unique party numberof the resource assignedto manage the salesprofile.


Conditionally requiredSpecify an accountowner, by including oneof following referenceinformation:




Conditionally requiredBy default, the userimporting the accountis designated as theaccount owner.





The following table lists the attributes required for importing the Address object for Accounts.


PartyId

The Oracle Sales Cloudinternal ID for theaccount to which theaddress belongs.


Required

Provide referenceinformation to identify theaccount:



Required






Import Objects

95



PartyNumber

The public uniqueidentifier for the accountto which the addressbelongs.


Required




• Party Number.

Required




• Party Number.

PartySourceSystem

The code representingthe source system for theaccount.


Required




• Party Number.

Required




• Party Number.


The reference numberor text representing thesource system unique IDfor the account.


Required




• Party Number.

Required




• Party Number.

Country

The country codecomponent of theaddress.

Identify valid countrycodes using the Setupand Maintenance,Manage Territories task.

Required

Required

AddressSourceSystem

The code representingthe source system for theaddress.

Identify the sourcesystem or configuresource systems eitherby using the ManageTrading Community


Provide the sourcesystem and source


Provide any of thefollowing reference



Import Objects

96


Source System task, orby importing the sourcesystem information intoOracle Sales Cloudusing the Source SystemReference import object.

system reference valuesif you intend to importupdates to previouslyimported records fromthe same system.

• Site Number.• AddressSourceSystem


information to identify theaddress:



AddressSourceSystemReference

The reference numberor text representing thesource system unique IDfor the address.










Site Number

The public uniqueidentifier for the address.

Identify the addressnumber value byexporting the Partyobject using the Setupand Maintenance,Manage Bulk DataExport, Schedule ExportProcesses task.

Not required Conditionally required




AddressType

The type of the address.You can define multipleaddress types for anaddress.

A list of valid values isdefined in the lookupPARTY_ SITE_ USE_CODE. Review andupdate the codesusing the Setup andMaintenance workarea, Manage StandardLookups task.

Required

Not Required

The following table lists the attributes required while importing Classification object for the Account.


PartyId

The Oracle Sales Cloudinternal ID for theaccount to which theclassification belongs.

Identify the party IDand party number valueby exporting the Partyobject using the Setupand Maintenance,

Required Required



Import Objects

97


Manage Bulk DataExport, Schedule ExportProcesses task.




• Party Number.




• Party Number.

PartyNumber

The public uniqueidentifier for the accountto which the classificationbelongs.


Required




• Party Number.

Required




• Party Number.

PartySourceSystem



Required




• Party Number.

Required




• Party Number.




Required




Required






Import Objects

98



SourceSystem

SourceSystem: Thecode representing thesource system for theclassification.



Required Provide the referenceinformation to identify theclassification.


SourceSystemReference:The reference numberor text representing thesource system unique IDfor the classification.



Required Provide the referenceinformation to identify theclassification.

ClassificationCode

The classificationcategory withinclassification category.


Required

Required

ClassificationCategory

The classification codewithin classificationcategory.


Required

Required

The following table lists the attributes required to import the Relationship object for the Account.


RelationshipId

The internal ID for therelationship.

Identify the relationshipID by exporting theParty object using theSetup and Maintenance,Manage Bulk Data

Conditionally required. If the source of yourdata is a third party orexternal system, and youintend to import updates

Required.



Import Objects

99



to previously importedrecords from the samesystem, provide theoriginal source systemand source systemreference values.




RelationshipSourceSystem

A source system codethat identifies the originalsource system of therelationship between theobject and the subjectparties.


Conditionally required. If the source of yourdata is a third party orexternal system, and youintend to import updatesto previously importedrecords from the samesystem, provide theoriginal source systemand source systemreference values.

Required.

RelationshipSourceSystemReference

A source systemreference that identifiesthe original referenceID of the relationshipbetween the object andthe subject parties in thesource system.


Conditionally required. If the source of yourdata is a third party orexternal system, and youintend to import updatesto previously importedrecords from the samesystem, provide theoriginal source systemand source systemreference values.

Required.

SubjectPartyId



Required





Required





SubjectPartyNumber



Required


• SubjectPartyId

Required


• SubjectPartyId



Import Objects

100


• SubjectSourceSystemandSubjectSourceSystemReferenceprovided in theSalesAccountCSV file.


• SubjectSourceSystemandSubjectSourceSystemReferenceprovided in theSalesAccountCSV file.


SubjectSourceSystem



Required





Required





SubjectSourceSystemReference



Required





Required





RelationshipType

Describes the directionalconnection betweenthe object and subjectrelationship. For example,Employer of versesEmployee of.


Required

Not required

RelationshipCode

Describes therelationship, such asContact or Membership.


Required

Not required

The following table lists the attributes required to import the Team Member object for the Account.



Import Objects

101


PartyId



Required




• Party Number.

Required




• Party Number.

PartyNumber



Required




• Party Number.

Required




• Party Number.

PartySourceSystem



Required




• Party Number.

Required




• Party Number.




Required



andPartySourceSystemReferenceValueprovided in the

Required



andPartySourceSystemReferenceValueprovided in the



Import Objects

102


SalesAccountCSV file.

• Party Number.

SalesAccountCSV file.

• Party Number.

ResourceId

The Oracle Sales Cloudinternal ID for sales teammember.


Required



Required



ResourcePartyNumber

The public uniqueidentifier for the salesteam member.


Required



Required



Create Import ActivityYou use the Manage File Import Activities task to create import activities. It consists of a step by step guided process toassist you with creating an import activity for a given object.

1. Sign in as a setup user and navigate to the Setup and Maintenance work area.2. Search for and select the Manage File Import Activities task.3. On the Manage File Import Activities page, click the Create icon.4. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select the

Account-Simplified View object from the Object list.5. Select ZIP file from the File Type list, check the Desktop option, and browse and upload the required ZIP file.6. To add attachments, under Attachments section, browse and upload your file. The attachment must be in ZIP

format.

Note: Ensure that you have the following columns and the required values in theSalesCloudAccount.csv file:

Column Name Expected Value

ATTACHMENT_ FILE_NAME

The file name with extension. For example, Sales.jpg.

ATTACHMENT_ FILE_DESC

The description of the file.

ATTACHMENT_ FILE_TITLE

The title of the file.

ATTACHMENT_ CATEGORY_NAME

The category of the file. For example, MISC.



Import Objects

103

7. Click Next.8. In the Create Import Activity: Create Schedule page, select an appropriate scheduling option from the Schedule list.9. Click Next.

10. On the Create Import Activity: Review and Activate page, click Activate to activate the import activity immediately, orclick Save and Close if you want to use the import activity later.



Import Objects

104


Chapter 10Configuring Profile Options

105

10 Configuring Profile Options

Customer Hub Profile Options Setup: OverviewProfile options are a set of preferences that you can use to centrally manage the user interface settings, data access andprocessing, and application action.

Customer Hub profile options let you view or change the address cleansing configuration, matching configuration, duplicateresolution request options, and various thresholds such as auto link, auto merge, and batch sizes. You can set these profileoption values only at the site level. You can configure profile options using the Manage Customer Hub Profile Options taskin the Setup and Maintenance work area. You need not change any profile options to use Customer Data Management.However, you should be familiar with them so that the correct configurations, actions, and thresholds are selected for eachcustomer. To find the list of Profile Options you can specify %ZCH% in the Manage Administrator Profile Values task.

The following table lists some important Customer Hub profile options, along with their names, descriptions and defaultvalues.

Profile Option Name Profile Option Definition Description Default Value

ZCH_ CLNS_ PROC_BT_SIZE

Data Cleansing Process BatchSize

The transaction batch size forthe data cleansing process. Setthis value based on availablesystem resources.

10000

ZCH_ DEDUP_ REQUEST_TYPE_OPTION

Resolution Request Type Default

The default request type for theduplicate resolution requests.

Merge

ZCH_ DI_ PROC_BT_SIZE

Duplicate Identification ProcessBatch Size

The transaction batch sizefor the duplicate identificationprocess. It's used to grouprecords in the batch and processeach group in a loop as aseparate transaction.

100

ZCH_ USER_ MERGE_REQUESTS

User Merge Requests

The processing options formerge requests. This optionapplies only for merge requestssubmitted from FUSE UI or EUMUI in Enter Merge Request setuptask.

Unspecified (NULL)

ZCH_ ENABLE_ SURVIVORSHIP

Survivorship Enabled

The option to enable survivorshiprules for duplicate resolution.

Yes

ZCH_ AUTO_ LINK_THRESHOLD

Auto Link Threshold

The threshold for auto link. Datastewards review link requestswith lower scores.

0



106

Profile Option Name Profile Option Definition Description Default Value

ZCH_ AUTO_ MERGE_THRESHOLD

Auto Merge Threshold

The threshold for auto merge.Data stewards review mergerequests with lower scores.

100

ZCH_ DI_ MERGEREQ_REC_SIZE

Duplicate Set Record Number

The maximum number ofrecords in a duplicate set thatcan be automatically convertedto duplicate resolution requests.

10

ZCM_ ACC_ EXACT_NAME_MATCH

Exact Account Name Match

This option controls the displayof duplicate accounts based onan exact name match when noduplicate accounts were foundfrom data quality configuration.

FALSE

ZCM_ CON_ EXACT_NAME_MATCH

Exact Contact Name Match

This option controls the displayof duplicate contacts based onan exact name match when noduplicate contacts were foundfrom data quality configuration.

FALSE

ZCM_ ACC_ DUP_NOTIFICATION

Duplicate Account Notification

This option controls whether theUI that shows notifications forduplicate accounts should beenabled or not. This option is available only if youhave Oracle Fusion Data Quality.

TRUE

ZCM_ CON_ DUP_NOTIFICATION

Duplicate Contact Notification

This option controls whether theUI that shows notifications forduplicate contacts should beenabled or not. This option is available only if youhave Oracle Fusion Data Quality.

TRUE

You must consider the following point while setting the values of the Customer Hub profile options:

• The profile option User Merge Requests is set to Unspecified (NULL) by default. You can set the following values forthis profile option:

◦ Allow Processing Without Approval: Merge requests are processed immediately without approval by thedata steward.

◦ Process Subject to Approval: Merge requests are reviewed by the data steward, who can decide toapprove or not.

◦ Unspecified: Merge requests are processed immediately without data steward approval. This indicates thatthe Customer Hub is not configured. The option is enabled only if the user has the Submit Trading CommunityMerge Request and Enter Trading Community Merge Request privileges.

• Data stewards must review merge requests initiated from the Simplified UI, Enter Merge Request setup task,Automerge web service, or the Duplicate Resolution Request web service. Data stewards can review mergerequests only if the profile option User Merge Requests is set to Process Subject to Approval, else the mergerequests returns an error.



107

• Auto Link Threshold is set to 0 by default, which means auto link never occurs automatically. Maximum auto mergethreshold is 100, which means unless there is a 100 percent match, there is no auto merge. You need to change thethreshold based on customer implementation.

Managing Customer Hub Profile OptionsThis procedure describes how to set up customer hub profile options.

You can configure these profile options by completing the following steps:

1. Navigate to Setup and Maintenance work area.2. Search for and go to the Manage Customer Hub Profile Options task.3. Select the profile option that you want to configure on the Manage Customer Hub Profile Options page.4. Select the appropriate profile option value, in the Profile Values area of the page.5. Click Save and Close.



108


Chapter 11Configuring Address Verification

109

11 Configuring Address Verification

Address Verification: Setup OverviewAddress cleansing is a process that corrects, parses, and completes and verify address data, based on postal requirements.For example, if you enter postal code, city, and country, then address cleansing may return a value for state. Likewise, if youenter city, state, and country, then address cleansing supplies a postal code value. In addition, you can validate the addressdata against the customer's master geography data, ensuring that the data entered is consistent with reference data. Thisaddress cleansing service is offered real-time, during the creation or edit of account, contact, or household, in batch modein the CDM work area, in file import, as well as any other service creating address data in the database. Address verificationis the process to verify that the address data entered for an account, contact, or household is a confirmed postal address.This includes the first line of the address, which typically includes a premise or building number and street name. Note that foraddress cleansing and verification you require a separate license for the Address Verification Cloud Service.

The following table lists the configurations that you must complete to enable address cleansing and verification. All the tasksare available in the Setup and Maintenance work area.


Manage Server Configurationsfor Cleansing

Enable the EDQ Real-time andBatch Basic Cleanse Serverconfiguration by selecting thecheck box against it. Ensure thatthe Server Parameter Values(Server Address, Server Port,and DaaS Cleansing Server URL)are complete.

Manage Server Configurations

For more informationabout managing EDQserver configurations, seeImplementing Customer DataManagement, Define DataQuality, Enterprise Data QualityServer Configurations: Explained.

Configure the AddressVerification Cloud Service

Subscribe to the OracleSocial Data and Insight CloudService and Oracle AddressVerification Cloud Service. Setthe Profile Value for theDAAS_PRODUCTION_ MODE profileoption to NO to configureApplications Cloud to DataCloud Integration.

• Manage Sales Cloud toData Cloud Integration

• Manage AdministratorProfile Values

Manage Enterprise Data QualityCleansing Configurations

You can use either thepredefined cleansingconfiguration shipped ready-to-use, or duplicate and editthese configurations to meetyour cleansing requirements.You can duplicate an availableconfiguration to modify itaccording to your geography,address, and cleansingrequirements.

Manage Enterprise Data QualityCleansing Configurations

For more information aboutmanaging EDQ cleansingconfigurations, see ImplementingCustomer Data Management,Define Data Quality, EnterpriseData Quality CleansingConfigurations: Explained.



110


Note: You must save aduplicated configurationbefore you edit it.

Set Up Address Cleansing andAddress Verification

Enable Address Verification forthe countries in which you dobusiness.

Manage Geographies, ValidationDefined

Managing Server Configurations for CleansingThis topic explains how to manage server configurations for cleansing.

You can enable the Server Configuration for cleansing by completing the following steps:

1. In the Setup and Maintenance work area, search for the Manage Server Configurations task by name and click Go.2. Select the EDQ Real-time and Batch Basic Cleanse Server option.3. Ensure that the Server Parameter Values (Server Address, Server Port, and DaaS Cleansing Server URL) are

complete.4. Click Save and Close.

For more information about managing EDQ server configurations, see Implementing Customer Data Management, DefineData Quality, Enterprise Data Quality Server Configurations: Explained.

Configuring the Address Verification Cloud ServiceThe address verification processes use country-specific postal address data provided in Enterprise Data Quality and DataCloud. For address verification you require a separate license for the Address Verification Cloud Service.

Configuring the Address Verification Cloud Service requires the following steps:

1. Creating a DaaS user and assigning a role.2. Configuring the Manage Sales Cloud to Data Cloud Integration task in Sales Cloud.3. Configuring Manage Administrator Profile Values task in Sales Cloud.

Creating a DaaS User and Assigning a RoleHere are the key steps to create a DaaS user and to assign Data Service Client API AppID role:

1. Subscribe to Oracle Social Data And Insight Cloud Service or request a trial account:

a. Log on to the My Services application at http://cloud.oracle.com.b. Navigate to Data Center where the service is located and request a trial or purchase a subscription.

For more details, see Subscribing to an Oracle Cloud Service Trial, Getting Started with Oracle Cloud, in theRelated Links section of this topic.



111

Note: Oracle Social Data and Insight Cloud Service and Oracle Address Verification CloudService offer a combined trial subscription; that is, when you order a trial for one service, youalso get the other. Each service must be purchased separately, but they can be part of the samesubscription order. For more information on subscriptions, see Understanding Subscriptions andFAQ -Subscriptions.

2. Activate your account:

a. Open the welcome e-mail you received from Oracle Cloud.b. Click on the Activate My Trial button.

When the activation of your trial subscription to an Oracle Cloud service is complete, you will get a post-activatione-mail from Oracle Cloud. This e-mail contains the sign-in credentials, My Services URL, and Identity domaininformation.

Tip: You can see the DaaS subscription URL under the My Account Administration Details section ofthe e-mail.

3. Reset your password:

a. Click the My Service URL.b. Log in to the My Services Dashboard using the temporary password.c. Reset your password when you are prompted.

When you sign in successfully, the My Services Dashboard page displays a list of your activated services and theREST service endpoint URLs for both Address Verification API, Company and Contact Data API.

4. Set up DaaS by creating a user and assigning the Data Service Client API AppID role to the new user.

a. Navigate to My Services Dashboard.b. Click the Users tab on the My Services Users page. The Add User page appears.c. Enter your credentials.d. Expand the Advanced Roles section and add the role Data Service Client API AppID.e. Click Add to assign this role to the user.

Configuring Customer Data Management Cloud to Data Cloud IntegrationAfter the DaaS user is setup, navigate to Sales Cloud for adding DaaS URL and credentials. The following are the steps toconfigure sales Cloud to Data Cloud Integration:

1. Navigate to Setup and Maintenance.2. Search for and go to the Manage Sales Cloud to Data Cloud Integration task.3. Enter the following information on the Manage Sales Cloud to Data Cloud Integration page:

◦ URL of your DaaS instance: This service instance URL is available in the post-activation e-mail on the TrialDetails section.

◦ Select oracle/wss_username_token_over_ssl_client_policy as Security Policy.

◦ Enter the DaaS user name and password you created in DaaS setup.




112

Requesting the Welcome E-mail to be ResentSetup steps for this service are sent through a welcome e-mail to the customer when the license is purchased. Detailedsteps for setting up Address Verification, including how to obtain DaaS Cleansing Server URL, can be found in Using OracleAddress Verification Cloud Service in the Help Center. If the DaaS Cleansing Server URL is missing and the customeradministrator has already activated the service, then the customer administrator can request resend of the Welcome e-mailby going to http://cloud.oracle.com > My Account (see the following figure).

The following figure highlights the Resend Welcome E-mail button on the My Accounts page.

However, if the customer administrator did not receive a welcome e-mail with links to activate the service, then the customerwill have to log a service request to have Oracle Support resend the welcome e-mail so that the customer administratorcan activate the service. Instructions on how to log a service request and the Customer Support Identifier associated to theservice request are described in the FAQ section of Getting Started with Oracle Cloud in the Help Center.

Managing Administrator Profile ValuesComplete the following steps to manage administrator profile values:

1. Navigate to Setup and Maintenance.2. Search for and go to the Manage Administrator Profile Values task.3. Enter DAAS_PRODUCTION_MODE as the Profile Option Code on the Manage Administrator Profile Values page.4. Click Search. The specified Profile Option appears as the search result.5. Make sure that theProfile Level is Site and the Profile Value is set to No.

Note: Do not set the Profile Level Site value to Yes. The only supported value today is No.


The integration between Data as a Service and Oracle Customer Data Management Cloud is now complete.

You find more information about the DaaS Address Verification in the Using Oracle Address Verification Cloud Service guidein the Related Links Sections.

Related Topics• Subscribing to an Oracle Cloud Service Trial

• Using Oracle Address Verification Cloud Service

• Oracle Enterprise Data Quality Customer Data Services Pack documentation

Managing Enterprise Data Quality Cleansing ConfigurationsEnterprise Data Quality configuration provides the mapping between the Enterprise Data Quality address cleansing attributesand the Customer Data Management Cloud Service address attributes.

http://docs.oracle.com/en/cloud/get-started/subscriptions-cloud/csgsg/subscribing-oracle-cloud-servicetrial.html

http://docs.oracle.com/en/cloud/saas/address-verify-cloud/csads/toc.htm

http://docs.oracle.com/cd/E48549_01/doc.11117/e40733/toc.htm#BABEFJGA



113

As part of managing Enterprise Data Quality (EDQ) cleansing configurations you have the following options:

• Use the predefined cleansing configurations shipped ready-to-use with the application.

• Adapt the predefined cleansing configurations to your address cleansing requirements by duplicating and editingthem.

Copying a Predefined Enterprise Data Quality Cleansing ConfigurationTo copy or make a duplicate of a predefined Enterprise Data Quality cleansing configuration, complete these steps:

1. Navigate to the Setup and Maintenance work area.2. Search for and go to the Manage Enterprise Data Quality Cleansing Configurations Task.3. Select the Address Cleansing configuration, and click Duplicate.4. Enter a name in the Name field.5. Click Save.

Adapting a Copy of the Predefined Enterprise Data Quality CleansingConfigurationTo edit a copy of the predefined Enterprise Data Quality cleansing configuration to your cleansing requirements, completethese steps:

Note: You cannot edit a predefined Enterprise Data Quality configuration. You can only make a copy of it andedit it by following this procedure.

1. Sign in as a setup user and navigate to the Setup and Maintenance work area.2. Search for and go to the Manage Enterprise Data Quality Cleansing Configurations task.3. Select a copy of the Address Cleansing configuration that you created earlier and click Edit. The Edit EDQ Cleansing

configuration page appears.4. Select Usage as Both to ensure that Address Cleansing is available in the UI when creating or editing Accounts or

Contacts, as well as for API.Note that the Usage option is set to Both, which indicates that the configuration is for both real-time and batchmatching.

5. Select the Active check box to activate the copy of the address cleansing configuration.By default, the predefined configurations are set to active. If there are copies of the predefined configurations, thenyou can set any of them to active by selecting the Active check box.

Note: You can activate only one configuration at a time. You must rebuild the keys when you activatea configuration.

6. Click Yes in the warning dialog box to activate this configuration.7. In the Cleansing Attributes Mapping section, select an attribute in the Address column, enter a corresponding

attribute in the Attributes column, and then map it with the corresponding attributes in the Attributes column tocreate an attribute mapping.For more information about mapping cleansing attributes, see Mapping Address Cleansing Attributes.

8. In the Cleansing Configuration Parameters section, perform the following tasks:a. In the Default Country drop-down list, select the relevant country name.b. In the Output Casing drop-down list, select Upper Case to print the address in upper case.



114

c. In the Minimum Verification Level drop-down list, select 3-Verified to Thoroughfare Level.d. In the Minimum Verification Score drop-down list, select 80.e. Select the Correct Partially Verified Addresses check box.f. Select the Correct Ambiguous Addresses check box.

For more information, see Configuring Cleansing Configuration Parameters.9. Click Save to save your changes.

10. Review Configuration Results.

For more information, see Reviewing Matching Configuration Results.11. Click Save and Close.

Mapping Address Cleansing AttributesCustomer Data Management Cloud Service provides the following attributes for address cleansing:

• Input Address Attribute: The attribute used to describe the input address from the Customer Data ManagementCloud service.

• Output Address Attribute: The attribute used to describe the output address to Customer Data Management Cloudservice after the address cleansing process is complete.

• EDQ Attribute: The Enterprise Data Quality attribute that is used for cleansing.

You can determine which input address attribute you want to map to the EDQ attribute for address cleansing. An EDQattribute is used to describe a distinct item of information that relates to a record. For example, a City attribute might describethe city details of a Customer record. Once the mapping is established, the input address is validated and verified. You canmap the cleansed address described in the EDQ attribute to the corresponding output address attribute.

Defining Cleansing Configuration ParametersCleansing configuration parameters are system-level parameters that control aspects of the data quality cleansing services.An EDQ cleansing configuration includes both real-time and batch cleansing configuration parameters.

These parameters control real-time and batch address cleansing, standardization, and validation operations for a subset or allof the address records in the database, or as part of a data import process. The following table describes theses parametersand provides the supported parameter values where applicable.

Parameter Description Parameter Value

Default Country

Used to specify the country to cleanse theaddress, if no identifiable country can befound in an input address.

• Possible Values: Names of differentcountries

• Default Value: United States

Output Casing

Used to specify the letter case for an outputaddress.

• Possible Values: Upper case, Lowercase, Mixed case.

• Default Value: Mixed

Minimum Verification Level

Used to specify the level of verificationto which the input data matches theavailable reference data during theverification process. Ranges from Verifiedto Administrative Area Level to Verified toDelivery Point, or Postbox level.

• Possible Values: Between 1 and 5.• Default Value: 3.

Note: The higher the value, themore precise is the address. Fora description of what each level



115


means, see Section "Notes onVerification Levels".

Minimum Verification Score

Used to specify the similarity between theinput address and closest reference datamatch as a percentage between 0 (no match)and 100 (perfect match).

• Possible Values: Between 0 and 100.• Default Value: 90

Correct Partially Verified Addresses

Determines if you want to correct theaddresses that you entered.

• Possible Values: Yes/No• Default Value: No

Correct Ambiguous Addresses

Determines if you want to correct theaddress that you entered if it is unclear andresolve it to the correct address.

• Possible Values: Yes/No• Default Value: No

Processing Mode

Use Verify mode to see the verifiedaddresses. The Address Verification usagecounter increases when you use the Verifymode.

• Possible Values: Verify• Default Value: Verify

Notes on Verification LevelsThe verification level is used to specify the level of verification to which the input data matches the available reference dataduring the verification process. It is output as the second character of the Accuracy Code returned by the EDQ AddressVerification processor. The 'post-processed' verification level is used (not the 'pre-processed' level); that is, the verificationlevel achieved after EDQ Address Verification applies standardization and parsing to the input address.

The following table lists the possible verification levels. The maximum verification level that it is possible to reach variesby country. For information on the maximum level in each country, see the Oracle EDQ Portal website at: http://www.loqate.com/oracle

Verification Level Description

1

Verified to Administrative Area (State, Region or County) level

2

Verified to Locality (City or Town) level

3

Verified to Thoroughfare (Street) level

4

Verified to Premise (Building Number) level

5

Verified to Delivery Point (Sub-Building Number) level



116

Reviewing Configuration ResultsThe Review Configuration Results option lets you check if the address attributes entered for cleansing in the Edit EDQCleansing Configuration page return the expected cleansed address. You can also test the results of one or more of thefollowing cleansing configuration parameters:

• Minimum Verification Level: Returns records based on the minimum verification level.

• Minimum Verification Score: Returns records based on the minimum verification score.

• Processing Mode: Use Search mode to search for valid addresses from Address.

• Verification Cloud Service. If you use Verify mode, the Address Verification usage counter increases.

You can review configuration results by completing the following steps:

1. Click the Review Configuration Results button on the Edit EDQ Cleansing Configuration page.

Clicking the Review Configurations Result button verifies your connection with the DaaS server. Select the processmode as Search to see multiple address results and Verify to see the verified address.

2. Enter values for the Cleansing Configuration parameters as required.3. Enter some sample address data into Review Configuration Results page:

a. Address 1: 100 Oracle Parkwayb. State: CAc. Country: Redwood City

4. Click Find to verify whether the cleansed address record meets your expectations.



117

The following figure shows the Review Configurations Results page.

For more information about address cleansing configuration template, see Implementing Customer Data Management, DefineData Quality, Managing Enterprise Data Quality Cleansing Configurations: Procedures.



118

Setting Up Address Cleansing and Address ValidationThis topic describes the procedure for setting up address cleansing and address Verification. It also describes how to turn onvalidation for address import.

Defining Address CleansingUse the following steps to define address cleansing for the countries in which you do business.

1. Navigate to the Setup and Maintenance work area.2. Search for and go to the Manage Geographies task. The Manage Geographies page appears.3. Search for a country for which you want to enable Address Validation using either by name or by its two letter ISO

code. For example, you can search by entering either the country name United States or the two letter ISO code US,and clicking Search.

4. Select the country in the Search Results area.5. Click the Go to Task button in the Address Cleansing Defined column to enable the Verify Address button for

account, contact or household on the simplified UI.

6. In Address Cleansing Level dialog box, set the Real-Time Address Cleansing Level to Optional to enable the optionto cleanse addresses. If the level is set to None, it specifies no real-time address cleansing.


Defining Address ValidationUse the following steps to define address verification for the countries in which you do business.

1. Navigate to the Setup and Maintenance work area.2. Search for and go to the Manage Geographies task. The Manage Geographies page appears.3. Search for a country for which you want to enable Address Validation using either its name or its two letter ISO code.

For example, you can search by entering either the country name United States or the two letter ISO code US, andclicking Search.

4. Select the country in the Search Results area.5. Click the check box in the Validation Defined column to enable or disable address validation for each country. The

Manage Geography Validation page appears.



119

The following figure shows the Manage Geography Validation page.

6. In the Address Style region, ensure that the No Styles Format address style is selected. You define validation for theNo Styles Format address style so that the validations are performed for all addresses in the country.

The setup of address styles for your application is done elsewhere, using the Manage Address Formats task. Theformat of addresses for Accounts and Contacts on the Create and Edit pages in Simplified UI and may not mapperfectly to master geography structure.

7. Deselect Enable List of Values option in the Geography Mapping and Validation region to avoid Address VerificationCloud Service data conflicts with master reference geography data. By deselecting this option you can avoid any UIlevel validation against master geographies while adding address.



120

Note: The Enable List of Values option is used to display the geography type as list of values duringaddress entry in the classic and simplified UIs. For example, to have users select states from a list,select Enable List of Values for State. You must enable the list of values for State if you use states foryour sales territories and want to assure that they are always entered correctly.

If Address Verification Cloud Service is used, the check boxes for Enable List of Values should be deselected toavoid data conflicts with master geography data. Tax Validation and Geography Validation are used for tax validationand territory management respectively.

8. Select Geography Validation Level for Country as No validation to verify address data by Address Verification CloudService.

Tip: If the Select Geography Validation Level for Country is set to Control as: Error, it means that youwant to verify address data against the master geography reference data.


For more information about setting up Master Reference Geographies and Address Cleansing, see the MOS document BestPractices for Setting up Master Reference Geographies, in the Related Links section of this topic.

Turning on Validation for Address ImportBy default, the validation you specified is enforced for creating addresses in the UI. You must set the profile option GeographyAddress Validation Enabled to Yes for the validation to be enforced during import. Follow these steps to set the profile option:

1. Navigate to the Setup and Maintenance work area.2. Search for and go to the Manage Administrator Profile Values task.

The Manage Administrator Profile Values page appears.3. In the Profile Display Name field located in the Search: Profile Option region, enter Geography Address Validation

Enabled.4. Click Search.5. With the profile option selected in the search results, select Yes from the Profile Value list.6. Click Save and Close.

Related Topics

• Managing Geography Mismatches

Enabling Search Mode for Address Verification CloudServiceThe Address Verification Cloud Service comes with two processing modes, Verify and Search. You can use this functionalityto verify an address in real-time while entering information on the Create Accounts or the Create Contacts page.

Out of the box, only the Verify mode is available to customers. When the Verify mode is enabled and you do real-time addressverification on the Create or Edit Accounts or Contacts page, the service returns a single verified address that matches theaddress information you entered on the page.

https://fusionhelp.oracle.com/helpPortal/faces/AtkHelpPortalMain?TopicId=413E6ADD908235EDE05362C3F00A836D



121

The search mode is available only to the Oracle Data Cloud Address Verification Unlimited License customers from Release11 Patch Bundle 15. When the Search mode is enabled and you do real-time address verification on the Create or EditAccounts or Contacts page, the service returns a list of the suggested verified addresses that match the address informationyou entered. You can then select the appropriate address from the list. You must create a new profile option and configurethe address verification process mode to enable search mode. This topic describes how Oracle Data Cloud AddressVerification Unlimited License customers can enable the DaaS Address Verification Search Mode.

Create New Profile Option for Enabling Search ModePerform the following steps to create a new profile option that you require to enable search mode.

1. Sign in as a setup user such as, Sales Administrator, Master Data Management Application Administrator, orApplication Implementation Consultant.

2. Navigate to Setup and Maintenance > Manage Applications Core Profile Options task.3. Click New from Actions. The Create Profile Option page appears.4. Enter the following information in the Create Profile Option page:

◦ Profile Option code: ORA_ZCQ_AV_UNLIMITED_LIC

◦ Profile Display Name: ORA_ZCQ_AV_UNLIMITED_LIC

◦ Application: Trading Community Data Quality

◦ Module: Application Common

◦ Provide appropriate Description

◦ Provide appropriate Start Date and End Date.

5. Click Save and Close.Now you can see the new profile option in the Manage Applications Core Profile Options page.

6. Select the SiteEnabled and Updatable check boxes in the Profile Options Levels section.7. Click Save and Close.8. Navigate to the Manage Applications Core Administrator Profile Values task.9. Search for the Profile Option Code ORA_ZCQ_AV_UNLIMITED_LIC.

10. Click New under the ORA_ZCQ_AV_UNLIMITED_LIC: Profile Values section.11. Select Site as the profile level and Y as the profile value.12. Click Save and Close.

Configure Address Verification Processing ModeYou can configure the address verification process mode by performing the following tasks:

1. Navigate to the Setup and Maintenance work area > > Manage Enterprise Data Quality CleansingConfigurations task.

2. Click Address Cleansing.The Edit EDQ Cleansing Configuration: Address Cleansing page appears.

3. Select Search from the Processing Mode drop down list in the Cleansing Configuration Parameters section.

Note: You can select either Verify or Search mode form the Processing Mode drop down listaccording to your requirements. Select Verify mode if you want only one verified address to be returnedwhile verifying an address on the Create Accounts or Create Contacts page. Select Search mode toget a list of the suggested verified addresses that match the address you entered so that you canselect the appropriate address from the list.



122


Verify Search Mode on Account or Contact Creation PageYou can verify the functionality of the Search mode while creating a new account or contact. Perform the following steps toverify an address in the search mode while creating a new account:

1. Navigate to Accounts work area.2. Click Create Account.3. Enter Address Line 1, City, and State of the account that you want to create on the Create Accounts page.4. Click Verify Address.

Note: If you click Verify Address after populating all the fields in the Address section of the CreateAddress page, you will get only one verified address with the complete match.

5. Select the correct address by clicking Select for the appropriate address from the list of suggested verifiedaddresses.

6. Click OK.

When you click OK the selected address gets populated in the Address section of the Create Account page.7. Enter account details on the Create Account page.8. Click Save and Close.


Chapter 12Configuring Duplicate Identification

123

12 Configuring Duplicate Identification

Duplicate Identification: Setup OverviewDuplicate identification is a process that identifies potential duplicate records for account, contact, and address. You can usethis process to identify duplicates in the following situations:

• Identify potential duplicate account, contact, and address records in real-time when its salespersons create acustomer record. This prevents the entry of duplicate records.

• Identify potential duplicates in batch mode for records already in the database or within the batch file itself.

• Identify duplicates during import of customer data for records already in the database.

Duplicate identification uses the Enterprise Data Quality (EDQ) service. You require a separate license for the Data QualityCloud Service.

You can enable Duplicate Identification by configuring the following tasks in Setup and Maintenance:



Enable the check box for EDQReal-time and Batch MatchServer configuration. Ensure thatthe Server Parameter Values(Server Address and Server Port)are complete.


For more informationabout managing EDQserver configurations, seeImplementing Customer DataManagement, Define DataQuality, Enterprise Data QualityServer Configurations: Explained.

Manage Enterprise Data QualityMatching

You can use either thepredefined matchingconfiguration shipped ready-to-use, or copy and edit theseconfigurations to meet yourmatching requirements.

Manage Enterprise Data QualityMatching Configurations

For more information aboutmanaging EDQ matchingconfigurations, see ImplementingCustomer Data Management,Define Data Quality, EnterpriseData Quality MatchingConfigurations: Explained.

Managing Server ConfigurationsYou can enable the server configuration for matching by completing the following steps:

1. Navigate to the Setup and Maintenance work area.2. Search for and go to the Manage Server Configurations task.3. Select the EDQ Real-time and Batch Basic Match Server configuration to enable it.4. Ensure that the Server Parameter Values (Server Address and Server Port) are complete.5. Click Save and Close.

For more information about managing EDQ server configurations, see Implementing Customer Data Management, DefineData Quality, Enterprise Data Quality Server Configurations: Explained.



124

Managing Enterprise Data Quality Matching ConfigurationsTo identify duplicate records, you need one matching configuration per object: Account, Contact, and Address. You caneither use the predefined matching configuration shipped ready-to-use, or copy and edit these configurations to meet yourmatching requirements. The ready-to-use configurations are read-only. There can be only one active matching configurationper object.

Copying a Predefined Enterprise Data Quality Matching ConfigurationTo copy or make a duplicate of a predefined Enterprise Data Quality matching configuration complete the following steps.This example demonstrates the procedure for duplicating the matching configuration for the account object.

1. Navigate to the Setup and Maintenance work area.2. Search for and go to the Manage Enterprise Data Quality Matching Configurations task.3. Select the Account Duplicate Identification match configuration, and click Duplicate.4. Click Yes in response to the warning message.5. Click Save to save the copy of the predefined configuration. When saved you can rename the configuration

appropriately.6. Repeat steps 2 to 4 to create copies of the predefined match configuration for the Contact Duplicate Identification or

Address Duplicate Identification.

Adapting a Copy of the Predefined Enterprise Data Quality MatchingConfigurationTo edit a copy of the predefined Enterprise Data Quality matching configuration, for example to edit the matchingconfiguration for the account object, complete the following steps:

Note: To edit the predefined Enterprise Data Quality configurations, you must make a copy of it. You cannotedit the predefined configurations.

1. Navigate to the Setup and Maintenance work area.2. Search for and go to Manage Enterprise Data Quality Matching Configurations task.3. Select the copy of Account Duplicate Identification match configuration that you created in "Copying a Predefined

Enterprise Data Quality Matching Configuration" section.4. Click Edit.5. Rename the configuration if required.6. Select the Active check box to activate the new configuration.

Note: By default, the predefined configurations are set to active. If there are one or more copies of thepredefined configurations, then you can activate any of them by selecting the Active check box. Onlyone configuration can be activated at a time. Make sure that the Usage option is set to Both, whichindicates that the configuration is for both for real-time and batch matching.

7. Click Yes in response to the warning message to set this configuration as active.8. In the Match Attributes section, you can edit the mapping between EDQ Match Identifier and attributes as follows:

a. Select a row and click the attribute drop-down list arrow of the selected row.b. Select the relevant attribute from the list.



125

c. If the list does not display the attribute that you want to map, then click Search in the drop-down list to searchfor the attribute.

d. Select the relevant option and click OK.9. For more information about mapping matching attributes, see Mapping Matching Attributes. You can set the real-

time and batch key generation options and matching configuration parameters as follows:

a. Select Typical in the Cluster Key Level drop-down list of the Key Generation Options section.b. In the Score Threshold field, enter 85.c. In the Match Results Display Threshold field, enter 20.

Note: The Match Results Display Threshold option is not available for Batch. For more information, seeConfiguring Matching Configuration Parameters.

10. Click Save.11. Click Review Configuration Results. For more information, see Reviewing Configuration Results.12. Click Save and Close.

Mapping Matching AttributesMatch attributes, such as name, country, and postal code are used for real-time and batch matching of the account,contact, and address records. You map the attributes in Customer Data Management application with the correspondingEnterprise Data Quality (EDQ) attributes to create an attribute mapping. For example, for account matching, map the EDQAttribute, name, to the Account Attribute, OrganizationName. When you map the attributes in the CDM application with thecorresponding EDQ attributes, you create a matching configuration setting for identifying duplicate entries. These settings arestored as matching keys in CDM.

You can use two types of EDQ Match Identifiers to include or exclude records from matching.

• Unique Identifier: Records that have the same Unique Identifiers always match, regardless of all other data.

• Elimination Identifier: Records that have different Elimination Identifiers never match.

Examples of attributes that could be used for Unique Identifier or Elimination Identifier are Social Security Number for contactor D-U-N-S number for account. You can use up to 3 Unique Identifier and 3 Elimination Identifier attributes in your matchingconfiguration.

Note: When you change the attribute mappings you must regenerate matching key values for the new orupdated accounts, contacts, and addresses.

Matching configuration parameters are system-level parameters that control aspects of the data quality matching services. AnEnterprise Data Quality (EDQ) matching configuration includes both real-time and batch matching configuration parameters.

The following table describes the real-time and batch configuration parameters and provides the supported parameter valueswhere applicable.


Cluster Key Level

Returns records based on the cluster keylevel.

• Possible Values: Limited (loosematching), Typical or Exhaustive (tightmatching).



126


• Default Value: Typical (recommended)

Score Threshold

Specifies the score above which the matchedrecords are returned by the matching service.Records equal to or greater than the scoreare considered as matches and the recordswith scores less than the threshold arerejected.


Match Results Display Threshold

Controls the number of matched recordsthat are returned by the real-time matching.Note: This match configuration parameter isenabled only for real-time matching.


Review Matching Configuration ResultsThe Review Configuration Results option allows you to evaluate if the attributes and parameters entered for matching inthe Edit EDQ Matching Configuration page return the expected results. You can also test the results of one or more of thefollowing matching configuration parameters:

• Cluster Key Level

• Score Threshold

• Maximum Candidates

• Match Results Display Threshold

You can review the configuration results of the Contact Duplicate Identification matching configuration by completing thefollowing steps:

1. Click the Review Configuration Results button on the Edit EDQ Matching Configuration page.2. Enter values for the Matching Configuration parameters as required.3. Enter some sample data into Review Configuration Results UI page as follows:

Match Configuration Parameters

◦ Cluster Key Level: Exhaustive

◦ Score Threshold: 50

◦ Maximum Candidate: 99

◦ Match Results Display Threshold: 20

Match Attributes

◦ PersonFirstName: Lisa

◦ PersonLastName: Jones

◦ Address1: 300 Oracle Pkwy

4. Click Find to verify whether the records returned as potential duplicates meet your expectations.

For more information about managing EDQ server configurations, see Implementing Customer Data Management, DefineData Quality, Enterprise Data Quality Matching Configurations: Explained.



127

Managing Key Generation: ExplainedThe EDQ matching process for real-time and batch matching makes use of the EDQ Cluster Key Generation service andthe EDQ matching service for duplicate identification. Successful key generation is critical to duplicate identification. Keygeneration identifies similar parties and assigns a key to each. When a matching configuration is made active, the applicationpasses a set of keys (subset of parties) to the EDQ matching service to process for duplicate identification.

The EDQ Cluster Key Generation service must be run whenever a record is added or updated in the application. This servicegenerates keys for records added as well as for the records that are updated in the application. If keys are not generated,duplicate identification fails.

Scheduling Key GenerationYou can schedule incremental key generation for an active matching configuration using the schedule key generation optionon the Edit Matching Configuration page. This generates keys for records that do not have a key or if the key time stampis older than that of the records. You must incrementally generate matching key values for the new or updated accounts,contacts, and addresses.

Rebuilding KeysYou must rebuild keys before activating a new configuration. You must rebuild keys if you change match configurationmappings or if you think that the keys are no longer valid because of updates to the records. You can regenerate matchingkey values using the Rebuild Keys option in the Edit Matching Configuration page.

Specifying Real-time and Batch Key Generation OptionsYou can specify different key generation options for batch matching and real-time matching. Take for example the clusterkey level parameter that has the values, limited, typical, or exhaustive. It is possible to select one value of this parameter, saylimited, for batch matching and another, say exhaustive, for real-time matching, depending on how tightly you want the dataquality engine to match records.

Reviewing Key Generations StatusYou can search for key generation jobs and review the status of each key generation job on the Manage Key Generationpage. The following table describes the various possible key generation statuses for a matching configuration.

Key Generation Status Description

Pending

Key generation for the configuration is required.

Processing

Key generation for the configuration is in progress.

Review Required

Key generation for this configuration needs review.

Ready

Key generation for this configuration is complete.



128

Selecting Sources of Match Rules and Scoring: Points toConsiderThe Customer Data Quality application comes with two options for match rules and scoring, predefined match rules (EDQmatch rules) and custom match rules (Customer Data Management match rules). You can use a drop-down button onthe Enterprise Data Quality Matching Configuration page to select the match rules and scoring option best suited for yourbusiness requirements.

The predefined EDQ match rules include a single, view-only matching rule for each object such as account, contact, andaddress. These match rules cannot be edited, scores cannot be changed, and no new rules can be added.

In case the predefined match rules are not suitable for your business requirements, you should enable custom match rulesand scoring. You should be able to turn on custom scoring by selecting Custom from the Scoring Type drop-down list on theManage Enterprise Data Quality Matching Configurations UI page. You can use this functionality to create your own matchrules and scores.

Managing Custom Match Rules and Scoring: ExplainedThis topic describes how to enable the custom match rules and scoring functionality.

Use the following procedure to enable custom match rules for account and contact. Note that custom match rules areavailable only for account and contact.

1. Navigate to: Setup and Maintenance > Customer Data Management offering > Setup >Data Quality functional area >Define Data Quality > Manage Enterprise Data Quality Matching Configuration.

2. Drill down on the predefined or the user-defined matching configuration, on the Manage Enterprise Data QualityMatching Configurations UI page, for which you want to enable or disable custom match rules and scoring.

3. Select Custom from the Scoring Type drop-down list on the Edit Match Configuration page.4. Click Save or Save and Close

Creating Custom Match Rules: ProcedureYou can use the custom match rule and scoring functionality to create your own match rules and scores based on yourbusiness requirements.

Use the following procedure to create custom match rules.

1. Navigate to: Setup and Maintenance > Customer Data Management offering > Setup > Data Quality functional area> Define Data Quality> Manage Enterprise Data Quality Matching Configurations.

2. Drill down on the predefined or the user-defined matching configuration, on the Manage Enterprise Data QualityMatching Configurations UI page, for which you want to create or update predefined rules.

3. Click Manage Match Rules on the Edit Match configuration page.4. On the Manage Match Rules page click New. Alternatively, you can click Duplicate to create a new rule based on an

existing predefined or user-defined match rule.



129

5. Enter the following valued for the for the newly created or copied match rule:

◦ Rule Name: The name of the new rule.

◦ Match Rule Score: The score that you assign to the rule. The value must be between 1 and 100.

◦ Rule Attribute: The standard or predefined attributes that must be used in the custom match rules. Ensurethat the syntax and spelling are exact.

6. Click Save or Save and Close.



130


Chapter 13Configuring Duplicate Resolution

131

13 Configuring Duplicate Resolution

Duplicate Resolution: Setup OverviewDuplicate resolution is a set of processes used, after duplicate records are identified, to consolidate those records. The twopossible outcomes to duplicate resolution: merged records or linked records.

Consistent application of complicated logic is required to identify the duplicate records and merge them. However, thereare tools and rules that you can use to determine whether to merge records or not. These rules can also help determinethe record that should be kept as the golden master (the surviving record) and the record that should be deleted (the victimrecord).

You can enable duplicate resolution by configuring the tasks listed in the following table. Note that to access these tasks,you must sign in as an implementation user who has the role Master Data Management Application Administrator assigned.MDM_Admin_V1 is such a predefined user shipped out of the box with the application.


Manage Source SystemConfidence

Source system confidence levelsor scores are used as criteria insurvivorship rules for:

• Comparing the reliabilityof information fromdifferent source systems.

• Preserving the data fromthe most reliable source inthe master record duringmerge operations.

You can set the sourceconfidence score per sourcesystem for attributes in theOrganization (Account) andPerson (Contact) objects.

Manage Source SystemConfidence

For more information aboutmanaging source systemconfidence, see ImplementingCustomer Data Management,Define Customer HubConfiguration, Source SystemConfidence.

Manage Survivorship Rules

Survivorship rules determine themaster or surviving customerrecord and its attributes duringthe merge operations forduplicate resolution. Ensurethat the ZCH_ ENABLE_SURVIVORSHIP profile option isset to Yes.



For more information aboutsurvivorship rules, seeImplementing CustomerData Management, DefineCustomer Hub Configuration,Define Survivorship, ManageSurvivorship Rules.

Manage Agreement Rules

Agreement rules determinewhether a merge request shouldbe vetoed by the applicationor not. Merge requests thatviolate agreement rules do notcomplete successfully.

Manage Agreement Rules

For more information aboutagreement rules, seeImplementing Customer DataManagement, Define CustomerHub Configuration, AgreementRules.



132


Run Request Dispatch Job

Run this process to manage andmonitor resolution requests inpending or submitted statuses.

Run Request Dispatch Job

For more information, seeImplementing Customer DataManagement, Define CustomerHub Configuration, Run RequestDispatch Job.

Managing Source System ConfidenceSource system confidence is used to determine the relative reliability of a particular account or contact attribute (standardor custom) from a particular source system. This allows the preservation of data from the most reliable source in themaster record during the merge operation. Each attribute is given its own source system confidence score. Source systemconfidence levels range from 0 to 100, and are set by default to 0. When all source system confidence levels are set to 0, allconflicts are listed for the Master Data Management Applications Administrator. The Master Data Management ApplicationsAdministrator reviews the list and decides the source system attributes that must be included into the master record.

You can define source system confidence using the following procedure:

1. Navigate to the Setup and Maintenance work area2. Search for and go to the Manage Source System Confidence task. The Manage Source System Confidence page

appears.3. From the Actions menu, click New. The Define Source System Confidence Page appears.4. Click Object Type drop-down list and select an object type.5. Select and move the attributes for which you want to set the source system confidence scores from the Available

Attributes list to the Selected Attributes list.6. Select a source system code from the Source System Code drop-down list.7. Enter a value in the Source Confidence field. The value of the source system confidence can range from 0 to 100.8. Click New to define the source confidence score for the selected attributes for different systems.9. Click Save and Close after defining source system confidence score. All attributes, their source system, and

confidence scores are visible in the Manage Source System Confidence UI page.

Managing Survivorship RulesSurvivorship rules create the best version of a record from multiple source systems, based on business rules. These businessrules use Source System Confidence scores as well as other criteria to determine the attributes that should be retained duringmerge operations.

You can enable Survivorship Rules by configuring the following tasks in Setup and Maintenance:

• Manage Survivorship Rules

• Manage Customer Hub Profile Options

The two types of survivorship rules that are used together to define the best version of a surviving record are as follows:

• Set master record: Defines the criteria for selecting the master record at the record level.

• Set attribute value: Defines the criteria for selecting the best attribute values at the attribute level.



133

Six predefined set attribute value rules are provided ready-to-use with the application:

• Least Recently Updated Organization Attribute (History Wins): This rule selects the organization attributes thathave the oldest updated date.

• Most Recently Updated Organization Attribute (Recent Wins): This rule selects the organization attributes thathave the most recent updated date.

• Highest Source Confidence Level Wins for Organization: This rule selects the organization attribute values thathave the highest source confidence.

• Least Recently Updated Person Attribute (History Wins): This rule selects the person attributes that have theoldest updated date..

• Most Recently Updated Person Attribute (Recent Wins): This rule selects the person attributes that have themost recent updated date.

• Highest Source Confidence Level Wins for Person: This rule selects the person attribute values that have thehighest source confidence.

In addition, you can use predefined templates to create new Set Attribute Value rules.

You must consider the following point while defining survivorship rules:

• Edits or changes made to the survivorship rules in an active sandbox will not be saved.

• After creating or editing a survivorship rule, the Submit button must be selected in order for the changes to be saved.

• Survivorship rules are stored in the rules dictionary XML file. The dictionary can be exported and imported throughthe Export Survivorship Rules Dictionary web service and the Import Survivorship Rules Dictionary web service.

Defining Survivorship RulesThis example demonstrates how to create a survivorship rule. Survivorship rules enable intelligent creation of the best versionrecord, especially from multiple source systems, by specifying criteria for selecting the record to be retained during a mergeoperation.

Use the UI available from the Manage Survivorship Rules task in Setup and Maintenance to create a survivorship rule and tospecify the criteria for selecting the master record.

Create Survivorship RuleFollowing are the steps to create survivorship rules:

1. Navigate to the Manage Survivorship Rules task.2. Click add.3. Enter the sample information provided in the following table on the Create Survivorship Rule page.

Field Value

Rule Name

PickPersonMasterRule

Description

Select the master person record based on original source system of the record.



134

Field Value

Rule Type

Set master record

Note: Note: You can create the following two types of survivorship rules: Set MasterRecord and Set Attribute Value. You can use predefined templates to create the SetAttribute Value rules.

Object Type

Person

Note: You can create a survivorship rule for the following two types of party records:Person and Organization.

4. Click Apply. The Define Survivorship Rules: Select Master Record page appears.

Specify Criteria for Selecting the Master RecordThe following are the steps to specify criteria for selecting master record:

1. Navigate to the Define Survivorship Rules: Select Master Record page.2. Enter the information provided in the following table as IF/THEN rules condition in the Define Survivorship Rules:

Select Master Record page.

Rule Condition Value

IF Condition IF PersonParty is a TCHFactTypeDictionary.PersonPartyVO

and there is a case where {OrigSourceSystem} != null and OrigSourceSystem.OwnerTableId == PersonParty.PartyId and OrigSourceSystem.OrigSystem == "GSI"}

THEN Condition THEN Assert new Result (name:"masterId", value:"PersonParty.PartyId)

Note the following specification in the Define Survivorship Rules: Select Master Record page.

◦ Click the + icon to add additional patterns to include additional conditions

◦ Click the Surround with Parenthesis option to add more features to the conditions

◦ Select the + Simple Test option to add additional clauses



135

The following figure shows the Define Survivorship Rules: Select Master Record page with the Surround iconhighlighted.

3. Click the Advanced Settings button to verify the effective date of the rule that you are going to create.

The following figure shows Advanced Settings icon on the Define Survivorship Rule: Select Master Record page.

4. Select an effective date, as appropriate. The default effective date is Always. You can select an Effective From orEffective To date, or you can select an Effective Date range.

5. Select a priority for the rule, as appropriate.

The default priority of the Survivorship rules is Medium. These rules get executed in the order of their priority.6. Ensure that the Rules Active option is selected.



136

The following figure shows how the survivorship rule looks like when fully defined. The details include the rule nameand the IF and THEN conditions for determining the master.

7. Click Save and Close. You can view the newly created rule in the Manage Survivorship Rules page by searching forit.

8. Click Submit.

Tip: To activate the rule you must click Submit. You may have selected the Active mode, but that willnot activate a rule unless submitted.

Related Topics• Implementing Customer Data Management: Define Survivorship

• MOS document: Define Survivorship Rules

Defining Set Master Record RulesThis procedure demonstrates how to create a survivorship rule of the type Set Master Record. You can determinesurvivorship at the record level using the set master record rule type. Set master rules are used in party merge to set a singlerecord as the master record.

http://docs.oracle.com/cloud/latest/salescs_gs/OACDM/OACDM1010615.htm#OACDM1010575

https://support.oracle.com/epmos/faces/DocumentDisplay?id=2113358.1



137

Defining Set Master Record RulesThe input to the survivorship rule is given in the IF clause. In a set master rule, the input is a set of party records. The THENclause contains the output that determines the master record. In the Set Master Record rule, the output is a result object thatcontains a specific Party ID. If multiple records with different Party IDs are returned, then it results in a conflict error. To createSet Master rules, you may perform the following steps:

To create Set Master rules, you perform the following steps:

1. Navigate to the Manage Survivorship Rules task.2. Click Add. The Create Survivorship Rule page appears.3. Enter the information provided in the following table on the Create Survivorship Rule page.

Field Value

Rule Name

PickOrganizationMasterRule

Description

Select the master organization record based on the specified criteria for setting the master record.

Rule Type

Set master record

Object Type

Organization

4. Click Apply. You are taken to the Define Survivorship Rules: Select Master Record page.

In the Define Survivorship Rules: Select Master Record page, you specify criteria for picking the master record. The criteriathat you define in this page determine the output of the rule.

The following topics contains three worked examples that show different ways of defining criteria in the Define SurvivorshipRules: Select Master Record page to set a master records:

• Set the Record with Oldest Creation Date as Master

• Set the Record with D-U-N-S Number and Smallest Party ID as Master

• Set the Record with D-U-N-S Number and Highest Number of Party Site as Master

Set the Record with the Oldest Creation Date as MasterThis rule has a single condition to set a record that has the oldest creation date as the master.

1. Navigate to the Define Survivorship Rules: Select Master Record page.2. Enter the information provided in the following table as IF/THEN rules condition in the Define Survivorship Rule:

Select Master Record page.


IF Condition IF master is an HZ_PERSON_FactType.PersonPartyVO

and there is no case where {nonmaster == HZ_PERSON_FactType.PersonPartyVO and master.PartyId isn't nonmaster.PartyId and master.creationDate is more than nonmaster.CreationDate}

THEN ConditionTHEN Assert new Result (name:"masterId", value:" master.PartyId)



138


The following figure displays the Define Survivorship Rules: Select Master Record page with completely filled IF and THENrules conditions for setting a record that has the oldest creation date as the master.

Set the Record with D-U-N-S Number and Smallest Party ID as MasterThis rule identifies and returns the master record based on the following three conditions in the order of priority listed:

1. Pick master that has D-U-N-S Number.2. If more than one record has D-U-N-S Number, pick one based on the smallest Party ID.3. If no record has D-U-N-S Number, pick one based on the smallest Party ID.

The following are the use cases for a set master record rule to pick the master based on the D-U-N-S number and thesmallest Party ID.

Use Case 1

In this case, there are two records with D-U-N-S number. Therefore, the record with the smaller party ID is picked as themaster record. The following table contains the sample record information for this use case.



139

Record Name Party ID D-U-N-S Number Master

Record 1

11

998837472

Yes

Record 2

12

null

No

Record 3

13

984939234

No

The following table lists the IF and THEN rules condition values that you must enter on the Define Survivorship Rules: SelectMaster Record page for this use case.


IF Condition Pick D-U-N-S number{IF master is an

HZ_PERSON_FactType.OrganizationPartyVOmaster.DUNsNumberC isn't null}masterPartyID is the minimum of masterPartyIDwhere{master= HZ_PERSON_FactType.OrganizationPartyVO andmaster.DUNsNumberC isn't null}

THEN Condition THEN

Assert new Result (name:"masterId", value:" master.PartyId)



140

The following figure shows the Define Survivorship Rules: Select Master Record page with IF and THEN rules conditions forpicking the record with D-U-N-S number and minimum party ID as master.

Use Case 2

In this case, there is no record with D-U-N-S number. Therefore, the record with smallest party ID is picked as the masterrecord. The following table lists the sample record information for this use case.

Record Name Party ID D-U-N-S Number Master

Record 1

21

null

Yes

Record 2

22

null

No

Record 3

23

null

No



141

The following table lists the IF and THEN rules condition values that you must enter on the Define Survivorship Rules: SelectMaster Record page for this use case.


IF Condition Pick D-U-N-S number

{IF master is an HZ_PERSON_FactType.OrganizationPartyVOmaster.DUNsNumberC isn't null}and masterPartyID is the minimum of masterPartyIDwhere{master= HZ_PERSON_FactType.OrganizationPartyVO andmaster.DUNsNumberC isn't null}

THEN Condition THEN

Assert new Result (name:"masterId", value:" master.PartyId)

The following figure displays the Define Survivorship Rules: Select Master Record page with completely filled IF and THENrules conditions to set the record that has the smallest party ID as the master when no record with D-U-N-S number is found.

In this example, you have created two set master rules for Organization. First rule is for the cases where the input recordshave at least one record with D-U-N-S number. The second is for the case where no records have D-U-N-S Number.

Note: You can activate more than one survivorship rule at a time. When you activate multiple rules, make surethat the rules are not conflicting and the conditions in the rule are set according to the priority.



142

Set the Record with D-U-N-S Number and Highest Number of Party Sites asMasterThis rule identifies and returns the master record based on the following three conditions in the order of priority listed:

1. Pick master that has D-U-N-S Number.2. Pick master that has more party sites.3. Pick master that has the smallest Party ID.

The following are two use cases for creating a set master rule to select the master record based on D-U-N-S number,number of party sites, and party ID:

Use Case 1

In this case, there are three records with D-U-N-S number and two records with highest number of party sites. Among thosetwo records, the one with the lower value for party ID is selected as master. The following table contains the sample recordinformation for this use case.

Record Name Party ID Number of Party Sites D-U-N-S Number Master

Record 1

11

3

198837472

Yes

Record 2

12

3

489203901

No

Record 3

13

2

384792392

No

Record 4

14

1

null

No

Use Case 2

In this case, there are no records with D-U-N-S number. So, among the two records with higher number of party sites, therecord with the smaller party ID is picked as the master record. The following table contains the sample record information forthis use case.

Record Name Party ID Number of Party Sites D-U-N-S Number Master

Record 1

21

1

null

No

Record 2

22

2

null

Yes

Record 3

23

3

null

No

To create a master record with D-U-N-S number, number of party sites, and party ID, you add one more condition to theprevious example where you set a master record with D-U-N-S number. Adding a condition to the previous example makesthe rules complicated and cumbersome. Instead, you can create a simple rule for each condition to narrow down the list ofpotential master records and create another simple rule in the end to pick one record from the remaining potential masterrecords.



143

Note: You can activate more than one survivorship rule at a time. When you activate multiple rules, make surethat the rules are not conflicting and the conditions in the rule are set according to the priority.

The following figure displays the Survivorship Rules: Select Master Record page with the IF and THEN rules condition valuesfor creating a set master rule to set the record that has D-U-N-S Number as master. The priority of the rule is set as highest.The details of the conditions are as follows:

Priority: Highest

IF condition: If number of non-null DUNS records is the count where {master is aHZ_ORGANIZATION_FactType.OrganizationPartyVO and master.DUNSNumberC isn't null} and number of non-null DUNS

records more than 0 and master is a HZ_ORGANIZATION_FactType.OrganizationPartyVO and master.DUNSNumberC is null

THEN condition: Then retract master



144

Now, you set the conditions to set the record with the maximum number of party sites as the master.

The following figure shows the Survivorship Rules: Select Master Record page with the IF and THEN condition values to setthe record with the maximum number of party sites as the master from the remaining potential records. The priority of the ruleis set as higher. The details of the conditions are as follows.

Priority: Higher

IF condition: If maximum party site number is the maximum of master.PartySite.size() where {master is aHZ_ORGANIZATION_FactType.OrganizationPartyVO} and master is a HZ_ORGANIZATION_FactType.OrganizationPartyVO and

master.PartySite.size() isn't maximum party site number

THEN condition: Then retract master

When the records are screened with two previous conditions, you create a third condition to screen all remaining potentialrecords with the smallest party ID.

The following figure shows the Survivorship Rules: Select Master Record page with the IF and THEN condition values forcreating a set master rule to set the record with the smallest party ID as the master. The priority of the rule is set as medium.The details of the conditions are as follows.

Priority: Medium

IF condition: If masterPartyId is the minimum of master.PartyId where {master is aHZ_ORGANIZATION_FactType.OrganizationPartyVO}



145

THEN condition: Assert new Result(name: "masterId",value:masterPartyId)

In this example, the rules are created to narrow down the list of potential master records. When you activate more than onerule at a time you should set the conditions for the rule according to the priority to narrow down the list of potential masterrecords. In this example Eliminate Null D-U-N-S Number rule is executed first to select records with D-U-N-S Number. Selectthe Most Address rule is executed next to find the master record with most number of party sites among the potential masterrecords having D-U-N-S Number. Finally, Select Minimum Party ID rule is executed at the end to pick the minimum party IDfrom the remaining party records.

Defining Set Attribute Value RulesThis example demonstrates how to create a survivorship rule of the type Set Attribute Value. You can determine survivorshipat the attribute level using the set attribute value survivorship rule type. Set attribute value rules are used in party merge todetermine which attribute value should come from which record.

The input to the survivorship rule is given in the IF clause. In a set attribute value rule, the inputs are the party records andtheir source information. The source information contains information about all attributes for each record in the database. Ifyou are creating rules that use the Source information VO, you define it in the Define Source Systems Confidence page of theManage Source System Confidence task. You must map each attribute to its source system and given a Source Confidencescore on a scale of 1 to 100.



146

The following table lists the attributes in the source information VO to create a set attribute value rule.

Attribute Name Description

RecordId

The record ID of a specific attribute.

AttributeName

The name of the attribute.

Source

The source system from where the attribute is updated.

SourceConfidenceLevel

The source confidence level assigned to the source system.

SourceUpdateDate

The date when the attribute was last updated.

The THEN clause determines the output object that picks the survivor record. In this case, setAttribute function creates theoutput object. To create Set Attribute Value rules, you perform the following steps:

1. Navigate to the Manage Survivorship Rules task.2. Click Add. The Create Survivorship Rule page appears.

Tip: You can select attributes from the available attributes in the Create Survivorship Rule page. It pre-populates the rule template with the selected attributes. It is not mandatory to set attributes from theavailable attribute.

3. Enter the sample information provided in the following table on the Create Survivorship Rule page.

Field Value

Rule Name

PickAttributeValueRule

Description

Select the survivor value for a specific attribute based on specified survivor selection criteria.

Select the survivor value for a specificattribute based on specified survivorselection criteria.

Set attribute value

Object Type

Organization

Template

Select the Attribute Based template to select the surviving value based on the characteristic ofthe attributes. For example, you need an Attribute Based template to pick an attribute with thehighest or lowest value such as a party number, or salary, or the earliest incorporated year. Selectthe Source Confidence Based template to select the surviving value based on the confidence inthe source information.

4. Select attributes from the available attributes to pre-populate the rules template. In case you want to use thepredefined set attribute rules, do not select any attributes.

5. Click Apply. You are taken to the Define Survivorship Rules: Select Attribute Value page.



147

In the Define Survivorship Rules: Select Attribute Value page, you specify criteria for selecting the survivor attribute value. Thecriteria that you define in this page determine the feature of the rule. You also have the option of using one of the followingthree predefined templates:

• Highest Source Confidence Level Wins for Organization (or Person): Use this rule to select the attribute values withthe highest source confidence level.

• Most recently updated Organization (or person) attribute: Use this rule to select the attribute values with the mostrecently updated date.

• Least recently updated Organization (or person) attribute: Use this rule to select the attribute values with the oldestupdated date.

The following sections of this topic contain three worked examples that show different ways of manually setting survivorattribute values in the Define Survivorship Rules: Select Attribute Value page. They are as follows:

• Set the Values with the Earliest Update Date as the Surviving Attribute Values

• Set the Value with the Highest Source Confidence Level as the Surviving Attribute Value for D-U-N-S Number

• Set the Values with the Earliest Incorporated Year as the Surviving Attribute Values

Set the Values with the Earliest Update Date as Surviving Attribute ValuesThis rule has a single condition to set all the surviving attribute values based on the earliest update date. The following is a usecase for a set attribute rule to select the values with the earliest update date as surviving attribute values:

Use Case 1

Party Record

The following table contains information for party records.

Record Name Party ID Party Name D-U-N-S Number

Record 1

1

Oracle Corp

198837472

Record 2

2

Oracle USA Corp

489203901

Record 3

3

Oracle

null

Source Information

The following table contains information for source information records.

Record ID Attribute Name Source Source Confidence Level Source Update Date

1

Party Name

FUSION

95

1/5/2016

2

Party Name

FUSION

95

1/5/2010

3

Party Name

SIEBEL

90

1/5/2000

1 D-U-N-S Number DNB 100 2/5/1990



148


2

D-U-N-S Number

FUSION

95

1/5/2016

In this case:

• The D-U-N-S number attribute value from the record with ID 1 is selected as survivor because the source informationindicates that it has the earliest source update date.

• The Party Name attribute value from the record with the ID 3 is selected as survivor because the source informationindicates that it has the earliest source update date.

Populate the Define Survivorship Rules: Select Attribute Values page with the IF and THEN rules condition values provided inthe following table.


IF Condition IF picked attribute is a AttributeSourceInfoVO

and there is no case where {Other Attribute == AttributeSourceInfoVO andthere is no case whereOther Attribute is a AttributeSourceInfoVOPicked Attribute.Attributename is OtherAttributename andPickedAttribute.RecordId isn't Other Attribute.recordId andPicked Attribute.SourceUpdateDate more than OtherAttribute.SourceUpdateDate}

THEN Condition THEN

call setAttribute (picked attribute.Attributename, Picked Attribute.RecordId)

The following figure displays the Define Survivorship Rules: Select Attribute Values page with the IF and THEN rulesconditions to create the set attribute value rule that selects the values with the earliest source update date as the survivingattribute value. The figure provides the following details.

Name of the rule: History Wins

IF condition: If picked attribute is a AttributeSourceInfoVO and there is no case where {Other Attributeis AttributeSourceInfoVO and Picked Attribute.AttributeName is Other Attribute.AttributeName and

PickedAttribute.RecordId isn't Other Attribute.RecordId and Picked Attribute.SourceUpdateDate more than Other

Attribute.SourceUpdateDate}



149

THEN condition: Then call setAttribute (Picked Attribute.AttributeName, Picked Attribute.RecordId)

Set the Value with the Highest Source System Confidence Level as theSurviving Attribute Value for D-U-N-S NumberThis rule has a single condition to select the D-U-N-S number value with the highest source confidence level as the survivingattribute value for the D-U-N-S number attribute. The following is a use case for a set attribute rule to select the D-U-N-Snumber value with the highest source confidence level as the surviving attribute value:

Use Case

Party Record



Record 1 1 Oracle Corp 198837472



150


Record 2

2

Oracle USA Corp

489203901

Record 3

3

Oracle

null

In this case, the party record contains three records with the attribute Party Name and two records with D-U-N-S number.These attributes are picked to create the source information. The source information table defined using the attributes fromthis party record table is as follows:

Source Information

The following table contains information for source information records.


1

Party Name

FUSION

95

1/5/2016

2

Party Name

FUSION

95

1/5/2010

3

Party Name

SIEBEL

90

1/5/2000

1

D-U-N-S Number

DNB

100

2/5/1990

2

D-U-N-S Number

FUSION

95

1/5/2016

In this case, the D-U-N-S attribute value for the record with ID 1 is selected as survivor because the source informationindicates that it has the highest source confidence level among all records that have the D-U-N-S Number attribute.

The following figure displays Define Survivorship Rules: Select Attribute Values page with the IF and THEN rules conditionvalues to set the attribute value with the highest source system confidence level as the survivor. The figure provides thefollowing details.

Name of the rule: Highest Source Confidence Level

IF condition: If picked attribute is a AttributeSourceInfoVO andPicked Attribute.ArrtibuteName isEnquireDUNSNumberC and there is no case where {Other Attribute is a AttributeSourceInfoVO and Picked

Attribute.AttributeName is Other Attribute.AttributeName and Picked Attribute.RecordId isn't Other

Attribute.RecordId and Picked Attribute.SourceConfidenceLevel is less than OtherAttribute.SourceConfidenceLevel}



151

THEN condition: Then call setAttribute (Picked attribute.AttributeName, Picked Attribute.RecordId)

Set the Values with the Earliest Incorporated Year as the Surviving AttributeValuesThis rule has a single condition to select values with the earliest incorporated year as the surviving attribute values. Thefollowing is a use case for creating such a set attribute value rule:

Use Case 1

Party Record


Record Name Party ID Party Name Incorporated Year

Record 1

1

Oracle Corp

1980

Record 2

2

Oracle USA Corp

1990

Record 3

3

Oracle

2000



152

In this case, the party record table contains three records with the attributes Party Name, Party ID, and Incorporated Year.The attribute values for the record with the earliest incorporated year are picked as survivor attribute values.

The following figure displays Define Survivorship Rules: Select Attribute Values page with the IF and THEN rules conditionvalues to set the attribute with the earliest incorporated year as the survivor. The figure provides the following details.

Name of the rule: Selecting the Earliest Incorporated Year

IF condition: If for each case where org is a OrganizationDVO and org.IncorpYear isn't null and there is no casewhere another org is a OrganizationDVO and org.PartyId is not another org.PartyId and another org.IncorpYear

isn't null and org.IncorpYear.intvalue() is more than another org.incorpyear.intValue()

THEN condition: Then call setAttribute ("IncorpYear", org.PartyId)



153

Managing Agreement RulesAn agreement rule is a collection of patterns and conditions that are defined to determine whether a merge request shouldbe vetoed by the application or not. Merge requests that violate these rules are either automatically rejected or end in error.An example of an Agreement Rule is CUST_CONTACT_DIFF_RESOURCE_ORG_VETO, which prevents two partner-ownedcontacts belonging to different resource organizations from being merged.

Agreement rules let you check a merge request for any veto conditions that can prevent a merge from occurring. Theserules save resources and time by obviating the task of reviewing merge requests to prevent undesired merges from beingprocessed. Besides, agreement rules prompt you to consider alternative duplicate resolution mechanism such as linking.Note that Agreement Rules cannot be set up in sandbox mode. Agreement rule can be of the following two types:

• Predefined: These are shipped out of the box with the application and are available in the predefined AgreementRules Dictionary shipped with the application.

• User-defined: You can create your own Agreement Rules using the Manage Agreement Rules setup andmaintenance task.

To know more about the two types of agreement rules see the Agreement Rules: Explained topic in the related links.

Related Topics

• Agreement Rules: Explained

Defining Agreement RulesThis example demonstrates how to create user-defined agreement rules that you can use to prevent a merge request frombeing processed.

Agreement rules are collections of patterns and conditions that are defined to determine whether a merge request should bevetoed by the application or not. Perform the following tasks to define agreement rules:

• Review and refresh terms in the predefined agreement rules dictionary shipped out of the box

• Add a new agreement rule

For more information on agreement rules, see Oracle Fusion Middleware User's Guide for Oracle Business Rules on OracleTechnology Network at http://www.oracle.com/technetwork.

Review and Refresh Terms in the Predefined Agreement RulesDictionaryThe Customer Hub application is shipped with a predefined agreement rules dictionary that contains all the predefinedAgreement Rules shipped out of the box with the application. Before using this dictionary to define custom agreement rules,you must review whether the agreement rule terms and term attributes existing in the predefined agreement rules dictionaryare sufficient to define custom agreement rules needed to meet your business requirements. If required, refresh terms toimport the latest terms, term attributes, and related metadata, for example, fact types such as entities and objects. Refreshing




154

the dictionary helps you pull in all the newly added custom attributes for accounts and contacts. Use the following steps toreview and refresh the agreement rules dictionary:

1. Navigate to the Setup and Maintenance work Navigate to: Setup and Maintenance > Customer Data Managementoffering > Setup > Customer Hub functional area > Manage Agreement Rules task.

2. Review whether the agreement rule terms and term attributes existing in the predefined agreement rules dictionaryare sufficient to define custom agreement rules needed to meet your business requirements.

3. Click Refresh Terms to import the latest terms, term attributes, and related metadata.4. Click OK in response to the confirmation message.

Add a New Agreement RuleAfter reviewing and refreshing the Agreement Rules Dictionary using the earlier steps, perform the following steps to create anew custom agreement rule:

1. Click Next to navigate to the Manage Agreement Rules: Define Rules page.2. Click Add form the Actions menu to add a new rule.3. Enter a rule name.4. Click Define Rule.5. Enter the reason for creating the agreement rule in the Justification Reason.6. Click Add form the Actions menu to create a new pattern.7. Complete the fields in the new pattern field using the sample information provided in the following table. Use the

default values except where indicated. Note that the relation is always AND between patterns and cannot be edited.You must include the Dictionary Terms OrganizationPartyVO and PersonPartyVO, with defined MergeType, into theDefine Patterns column. These patterns determines the master and nonmaster records.

Pattern Dictionary Term Term Alias Relation

for each case where

PersonPartyVO

Person

AND

for each case where

OrganizationPartyVO

NonmasterParty

AND

there is a case where

PartyUsageAssignmentVO

PartyUsageAssignment

AND

8. Navigate to the Conditions table.9. Click Add from Actions to add a new condition and complete the fields using the sample information provided in the

following table. Use the default values except where indicated.

Term Attribute Operator Value Relation

Person. PartyNumber

is not

1234

AND

NonmasterParty. MergeType

=

Nonmaster

AND

UsageAssignment.PartyUsageCode

=

HR_APPLICANT

AND

10. Click Save or Save and Close.11. Click Submit.



155

Related Topics

• Agreement Rules: Explained

Running the Request Dispatch JobThe Dispatch Job processes duplicate resolution requests in Pending or Submitted status. Run this process to manage andmonitor resolution requests. Running the Dispatch Process You can run this job in two modes:

• On demand. Complete the following steps to run the job on an ad-hoc basis:

a. Navigate to Run Request Dispatch Job taskb. Click Submit

• Per a specific schedule. Do the following steps to set up a recurring job:

a. Navigate to Run Request Dispatch Job task.b. Click Advanced on the Run Request Dispatch Job task.c. Click Schedule tab and select the Using a Schedule radio button.d. Select the frequency you want and click Submit.

Reviewing the Status of the ProcessTo see the list of dispatch jobs, and their statuses:

1. Go to the Tools section on the Navigator.2. Click the Scheduled Processes link under Tools.3. View the status of the Schedule Duplicate Resolution Requests process.

High Volume Batch Deduplication: Best Practices andGuidelineBatch deduplication of account or contact records in Customer Data Management (CDM) Cloud Service consists of thefollowing two steps:

• Duplicate Identification: This step includes the identification of duplicate records by submitting a DuplicateIdentification Batch job.

You can define and submit this job from the Duplicate Identification page.

• Duplicate Resolution: This step includes the resolution of the duplicates, typically by merging each set of duplicaterecords.

You can resolve the duplicates either automatically by submitting the Duplicate Identification Batch job (calledAutomerge) or manually by submitting records in bulk from the Duplicate Identification Batch results review page.

For more details on these steps and for configuration of Automerge, see Merge Requests, Implementing Customer DataManagement.




156

Both of these jobs are data-intensive operations that can read or update millions of rows of data in various Oracle ApplicationCloud tables. This document is intended to provide the guidelines and best practices for planning the data-sets, andapplying appropriate configurations to achieve optimal throughput for high volume deduplication in CDM Cloud Service.Each customer's data set is unique. The time required to process a duplicate identification batch varies on the data shape.Approximately 15,000 to 20,000 records per batch take 3 to 4 hours to process.

Best Practices and GuidelinesCustomer Data Management merge is a data-intensive process that scans and updates a large number of tables in OracleApplications Cloud, to correctly merge two or more Accounts or Contacts.

This section describes how you can use the following profile options to optimize the merge process:

• Scope of Merge Process (ORA_ZCH_MERGE_SCOPE_LOOKUP): You can use this profile option to define thescope of the merge process.

• Master Record Selection Method (ORA_ZCH_SETMASTER_LOOKUP): You can use this profile option to specifythe method for selecting the master record in a merge request.

• Create Automerge with Review (ORA_ZCH_AUTOMERGE_REVIEW): You can use the profile option to select anappropriate processing option for Automerge.

• Maximum Number of Concurrent Merge Jobs (ORA_ZCH_MERGE_MAX_REQUEST_LIMIT): Specify themaximum number of merge jobs to be processed at a time. If you do not set the maximum limit, all merge jobs aresubmitted for concurrent processing.

You can set these profile options from the Manage Customer Hub Profile Options Setup and Maintenance task.

Defining the Scope of the Merge ProcessWhen you merge two or more records, the application scans hundreds of transactional and reference tables acrossall modules in the Oracle Applications Cloud such as, Core CDM, CRM, Financials, and Manufacturing. This canmake merge a data-intensive and time consuming process. However, you can use the Scope of Merge Process(ORA_ZCH_MERGE_SCOPE_LOOKUP) profile option to define and limit the scope of merge process in an implementationso that the application scans only the necessary business areas. This optimizes the size of the merge memory and executionprofile.

The following options are supported by the Scope of Merge Process profile option:

• All Functional Areas (ALL): This is the default option and scans across all areas of Oracle Applications Cloud. Youuse this option when there is a global implementation running various modules of Oracle Applications Cloud such as,Core CDM, CRM, Financials, and Manufacturing.

• All Customer Relationship Management Related Areas (CRM): This option limits the scope of the process to handleall the CRM entities such as, Opportunities, and Leads, core Customer Data, Common Entities such as, Notes,and Activities, and Custom Objects. You use this option when there is a CRM implementation along with the use ofCustomer Data Management functionality.

• Customer Data Management Specific Areas (CDM): This option limits the scope of the process to core CustomerData, Common Entities such as Notes and Activities, and Custom Objects. You use this option during the initialcustomer data consolidation and to achieve best performance for Customer Data management, implementations.

Note: The profile option settings can be changed at any time, if additional modules are turned on the instance.For instance, the CDM option might be used during initial consolidation and cleanup of customer data and thenchanged to CRM or ALL options if other modules are implemented later.



157

Defining the Master Record Selection MethodThe performance of the merge process also depends on the method used to select the master record. You can use theMaster Record Selection Method (ORA_ZCH_SETMASTER_LOOKUP) profile option to specify an appropriate option forselecting the master party automatically during merge. The following options are supported by the Master Record SelectionMethod profile option:

• Select master record using survivorship rule (RULE): This is set as the default master selection option. This optionselects the master record based on the Set Master rules defined in the Manage Survivorship task. These rules areapplied using the Oracle Business Rules component. You use this option when there are complex business rulesrequired to pick the master.

• Select the oldest record as master (OLDEST): This option selects the party with the earliest creation date as themaster.

• Select the newest record as master (NEWEST): This option selects the party with the newest creation date as themaster.

• Select master based on duplicate identification results (ANY) - This option randomly selects one of the parties in theset as a master.

Configuring Automerge ActionAutomerge is the process of automatically merging identified duplicate sets that exceed the automerge threshold. Theprocess is initiated by creating a duplicate identification batch with the Create Merge Request option. You can use theCreate Automerge with Review (ORA_ZCH_AUTOMERGE_REVIEW) profile option that has Yes and No values to select anappropriate processing option for Automerge:

• Create merge requests only for duplicate sets exceeding the automerge threshold: To enable this processing option,select No as the value for the Create Automerge with Review (ORA_ZCH_AUTOMERGE_REVIEW) profile option. Ifyou select this option, the application processes duplicate sets as follows:

◦ The application preprocesses the duplicate sets exceeding the automerge threshold and merges them into asingle job. This option is ideal for processing high volumes of merge requests when the duplicate sets requireno review or any further action.

◦ Duplicate sets not exceeding the automerge threshold remain in Not Reviewed status in the DuplicateIdentification page, from where they can be manually converted to merge requests, or rejected, if needed.

• Create Merge Requests for all duplicate sets: To enable this processing option, select Yes as the value for the CreateAutomerge with Review (ORA_ZCH_AUTOMERGE_REVIEW) profile option. If you select this option, merge requestsare created for all duplicate sets. All requests are first pre-processed. Then they are either merged (if they exceedthe automerge threshold), or put in "New" status (so that they can be reviewed) if they don't exceed automergethreshold.

Controlling the Concurrency of Merge ProcessesEach merge request executes as a single batch process in the Enterprise Service Scheduler (ESS). The number of mergerequests executing concurrently is limited by the number of batches being concurrently processed. Therefore, if thereare other ESS processes competing for threads when there are a large number of merge requests queued up, then thescheduling of those jobs could get delayed.

During initial consolidation of customer data, it's advantageous to use the maximum available threads. However, in steadystate when there are other processes running in the system, it may be necessary to limit and control the number ofconcurrent merge ESS jobs.



158

To achieve this, set the following profile option to an appropriate value:

• Profile Option Name: Maximum Number of Concurrent Merge Jobs

• Profile Option Code: ORA_ZCH_MERGE_MAX_REQUEST_LIMIT

◦ When the profile option value is left blank or when no value is defined, the ESS will allocate merge requestsaccording to the threads available. This is recommended during initial high volume data processing.

◦ After initial data load, set the profile option value to ten or lower if other processes such as Web services orother ESS jobs are running.

Initial Data Consolidation and CleanupIf during initial data consolidation the data is expected to have a large percentage of duplicates, then it is recommendedto decompose the data sets for duplicate identification into smaller chunks of data. Chunk refers to the number of recordsdefined by the selection criteria when submitting a duplicate identification batch. This enables the duplicate identification andresolution process to be robust, reliable, and manageable.

The recommended size of a chunk depends on the number of duplicates expected to be identified. Approximately, you canset the selection criteria for duplicate identification such that, each batch produces not more than 50,000 duplicate sets. Theselection criteria for defining a duplicate identification batch can be based on some functional decomposition criteria. Forexample, the selection criteria can be based on the State or the starting alphabet of the name.

Purging Duplicate Resolution Data: ExplainedLegacy duplicate resolution data, such as resolution logs and legacy duplicate resolution batches and requests can clutter theduplicate resolution work area as well as affect the performance of the application. Use the Purge Duplicate Resolution Datascheduled process to purge the duplicate resolution data, such as resolution logs and to delete duplicate resolution batchesand requests. You can schedule this process from the Scheduled Processes work area. You can navigate to this work areaas follows: Navigator > Tools > Scheduled Processes.

This scheduled process lets you purge duplicate resolution data based on status and date range. You can specify the statusof the duplicate resolution requests to be purged, such as duplicate resolution requests in Completed, Error, or Rejectedstatus. You can also specify a date range by specifying the start and an end date to select duplicate resolution requests to bepurged. For more information, see: Submitting Scheduled Processes and Process Sets: Procedure

Related Topics

• Submitting Scheduled Processes and Process Sets: Procedure

• Process Sets: Explained

• Managing Scheduled Processes That You Submitted: Points to Consider

https://fusionhelp.oracle.com/helpPortal/faces/AtkHelpPortalMain?TopicId=04C7C6F4C65C6FAFE05362C3F00ABFC4

https://fusionhelp.oracle.com/helpPortal/faces/AtkHelpPortalMain?TopicId=96D9675F3D49C07DE040D30A68813CF9

https://fusionhelp.oracle.com/helpPortal/faces/AtkHelpPortalMain?TopicId=E4DD63537E8A087AE040D30A68816744


Chapter 14Configuring Data Enrichment

159

14 Configuring Data Enrichment

Configuring Social Data and Insight Cloud Service for DataEnrichment and Address Verification: OverviewYou can use the Oracle Social Data and Insight Cloud service, also known as, Data as a Service (DaaS), to enrich youraccount and account contact (B2B contact) data in Oracle Cloud applications. This cloud service uses Dun and Bradstreet(D&B) data for more than 200 countries as the primary source for enrichment. Data enrichment improves the quality of yourexisting account or account contact data, address information, and also enriches the data with additional information. Usingthis cloud service, salesperson can enrich accounts and account contacts in real-time and administrators and data stewardscan enrich data in bulk.

You can enrich account and account contact data in bulk using either batch data enrichment in the Data Enrichment workarea, or manually using bulk import and export templates. You can also use real-time data enrichment to enrich a small setof data in real time on the Accounts and Contacts pages. Additionally, you can also download enriched account and contactdata from the Oracle Social Data and Insight Cloud service.

Configuring Batch Data EnrichmentThe batch data enrichment option lets you enrich data in bulk by creating and submitting batch-processing jobs in the DataEnrichment work area. Configuring this enrichment process flow requires the completion of the following set-up steps:

1. Create a DAAS user and assign appropriate privileges. For more information, see: Creating a DaaS User andAssigning Role: Procedure.

2. Configure Sales Cloud to Data Cloud integration. For more information, see: Configuring Sales Cloud to Data CloudIntegration: Procedure.

Configuring Manual Data EnrichmentIf you require custom attributes for social data enrichment, then you must create a manual enrichment job. The manualenrichment option lets you use custom import mappings to import the enriched records back. The following are the steps toperform manual data enrichment:

1. Export data from Sales Cloud to a CSV file2. Enrich the data using Oracle Social Data and Insight Cloud service3. Download the enriched data file from Oracle Social Data and Insight Cloud service4. Import the enriched data file into Oracle Sales Cloud

The application comes with preconfigured mappings to import account data or account contact data from Data as a Service(DaaS). However, if you require custom attributes for social data enrichment, as a part of configuring this enrichment processflow you must create custom import mappings to import the enriched records back.



160

Configuring Real Time Data EnrichmentThe real time enrichment option lets you enrich data one-record at a time during the create account or contact flow. It alsolets you enrich up to five existing records on the Accounts or Contacts simplified UI. Configuring this enrichment process flowrequires the completion the following set-up steps:

1. Create a DAAS user and assign appropriate privileges. For more information, see: Creating a DaaS User andAssigning Role: Procedure.

2. Set up real-time data enrichment preferences. For more information, see: Managing Social Data and Insight CloudAttribute Mapping and Preferences: Procedure.

3. Set up administrator profile options. For more information, see: Managing Social Data and Insight Cloud AttributeMapping and Preferences: Procedure.

4. Configure Sales Cloud and Data Cloud integration. For more information, see: Configuring Sales Cloud to DataCloud Integration: Procedure.

The following figure illustrates all the available data enrichment process flows:

For more information, see the Using Oracle Social Data and Insight Cloud Service guide.

Related Topics

• Managing Real Time Data Enrichment Mapping and Preferences: Procedure

https://fusionhelp.oracle.com/helpPortal/faces/AtkHelpPortalMain?TopicId=07CB56D56E3F2477E05362C3F00AFC15



161

Creating a DaaS User and Assigning Role: ProcedureHere are the key steps to create a DaaS user and to assign Data Service Client API AppID role:

1. Subscribe to DaaS for Sales (Social Data and Insight) or request a trial account:

a. Log on to the My Services application at http://cloud.oracle.com.b. Navigate to Data Center where the service is located and request a trial or purchase a subscription to Data as

a Service (DaaS).

For more details, see Subscribing to an Oracle Cloud Service Trial in the Getting Started with Oracle Cloud.

Oracle Social Data and Insight Cloud Service and Oracle Address Verification Cloud Service offer a combinedtrial subscription. When you order a trial for one service, you also get the other. Each service must be purchasedseparately, but they can be part of the same subscription order. For more information about subscriptions, seeUnderstanding Subscriptions and FAQ Subscriptions.

When you request a trial subscription, you receive a welcome e-mail. An activation e-mail contains the ActivateMy Trial button along with service details. Service details consist of information such as name of the data center,subscription details, and identity domain.

2. Activate your account:

a. Open the welcome e-mail you received from Oracle Cloud.b. Click the Activate My Trial button.

When the activation of your trial subscription to an Oracle Cloud service is complete, you get a post activation e-mailfrom Oracle Cloud. This e-mail contains the sign-in credentials, My Services URL, and Identity domain information.

Tip: You can see the DaaS subscription URL under the My Account Administration Details section ofthe e-mail.

3. Reset your password:

a. Click the My Service URLb. Log on to the My Services Dashboard using the temporary password.c. Reset your password when you are prompted.

When you sign in successfully, the My Services Dashboard page displays a list of your activated services and theREST service endpoint URLs for both Address Verification API and Company and Contact Data API.

4. Set up DaaS by creating a user and assigning the Data Service Client API AppID role to the new user.

a. Navigate to My Services Dashboard.b. Click the Users tab on the My Services Users page. Add User page appears.c. Enter your credentials.d. Expand the Advanced Roles section and add the role Data Service Client API AppID.e. Click Add to assign this role to the user.



162

Configuring Integration to Data Cloud: ProcedureYou can configure the Sales Cloud to the Data Cloud Integration after you set up the DaaS user. To configure the Sales Cloudto the Data Cloud Integration you navigate to Sales Cloud for adding DaaS URL and credentials. The following are the stepsto configure sales Cloud to Data Cloud Integration:

1. Navigate to Setup and Maintenance.2. Enter Manage Sales Cloud to Data Cloud Integration in the task search box.3. Click Search.4. Navigate to Manage Sales Cloud to Data Cloud Integration page.5. Enter the following information:

a. URL of your DaaS instance - This service instance URL is available in the post-activation email and on the MyServices application.

b. Select oracle/wss_username_token_over_ssl_client_policy as Security Policy.c. Enter the DaaS user name and password you created in DaaS setup.



Chapter 15Configuring Automerge

163

15 Configuring Automerge

Automerge: Setup OverviewThe automerge functionality merges duplicate records without any approval or intervention from the data steward. Automaticprocessing of merge requests is critical when processing large volumes of customer data because automerge can expeditethe resolution of duplicate records without manual review. Note that during automerge, the child entities of the duplicaterecords, such as contact points, relationships, classifications, and cross references, become the child entities of the masterrecord. For more information about automerge, see Using Customer Data Management, Managing Customer Data Quality,Resolve Duplicate Customer Information, Automerge: Explained.

Enabling Automerge involves several implementation steps that you have probably already completed while setting upduplicate identification and duplicate resolution. However, review the following list ensure these setups are indeed complete.

You can enable automerge by configuring the task listed in the following table in the Setup and Maintenance work area:



Set up the following profileoptions appropriately:

• Auto Merge Threshold(ZCH_AUTO_MERGE_THRESHOLD)

• Record Size Limitof Duplicate Set(ZCH_DI_MERGEREQ_REC_SIZE)

• Survivorship Enabled(ZCH_ENABLE_SURVIVORSHIP)


For more information see,Getting Started with YourCustomer Data ManagementImplementation, ConfiguringProfile Options.

Define Survivorship

Survivorship rules determinethe master or surviving recordand its attributes during themerge operations for duplicateresolution. Ensure that the ZCH_ENABLE_ SURVIVORSHIPprofile option is set to Yes.



For more information see,Getting Started with YourCustomer Data ManagementImplementation, ManagingSurvivorship Rules.

Manage Server Configuration

Enable the check box for EDQReal-time and Batch MatchServer configuration. Ensure thatthe Server Parameter Values(Server Address and Server Port)are complete.

Manage Server Configuration

For more information see,Getting Started with YourCustomer Data ManagementImplementation, Manage ServerConfiguration.

Manage Enterprise Data QualityMatching Configuration

Create an active MatchConfiguration in ManageEnterprise Data Quality MatchingConfigurations task or use apredefined Match Configuration.Rebuild the keys if necessary.

Manage Enterprise Data QualityMatching Configurations

For more information see,Getting Started with YourCustomer Data ManagementImplementation, ManagingEnterprise Data Quality MatchingConfigurations.



164


Create an appropriate duplicateresolution request

Create a duplicate identificationbatch and select Create MergeRequest as the AutomaticProcessing Option.

N/A For more information, see:

• Using Customer DataManagement, ManagingCustomer Data Quality,Identify DuplicateCustomer Information,Creating DuplicateIdentification Batches:Points to Consider

• Using Customer DataManagement, ManagingCustomer Data Quality,Resolve DuplicateCustomer Information,Creating DuplicateResolution Request:Explained.

Understanding How Records are Selected for AutomergeRecords are selected for automerge based on the following criteria:

• Match threshold: The match threshold is defined in the Match Configuration and determines whether a record isincluded in a duplicate set or not.

• Merge threshold: The merge threshold is defined by the ZCH_AUTO_MERGE_THRESHOLD profile option anddetermines whether the merge request for a duplicate set is processed automatically or if it must be reviewedmanually.

The three possible outcomes for each record with regard to duplicate identification and merging are as follows:

• Low score below match threshold: The record is not included in duplicate set and in the merge request for thatduplicate set.

• Medium score above match threshold and below merge threshold: The record is included in duplicate set but mergerequest for that duplicate set must be reviewed manually.

• High score above match threshold and above merge threshold: The record is included in duplicate set and mergerequest is processed automatically.

The score for all the records in a duplicate set must be above the merge threshold for automated processing. If one record inthe duplicate set is below merge threshold, and the other records are above the merge threshold, the merge request must bereviewed manually.

Note: When you merge two or more records with exactly same children information under phone, email, oraddress the children information is merged and rolled up to the survivor record.



165

Implementing AutomergeThis topic describes how to set up automerge, run the automerge process, and troubleshoot automerge issues.

Automatic processing of merge requests is critical when processing large volumes of customer data. Automerge can expeditethe resolution of duplicate records without any manual review or approval from the data steward.

Enabling AutomergeEnabling Automerge involves several implementation steps that must be completed by an implementor using the followingSetup and Maintenance tasks:

• Manage Customer Hub Profile Options: Navigate to this task through the Setup and Maintenance work area toperform the following implementation steps:

◦ Set Auto Merge Threshold profile option (ZCH_AUTO_MERGE_THRESHOLD) to the required value. Thisprofile option specifies the threshold for auto merge. Merge requests with lower scores need data steward'sreview. An exact match is 100.

◦ Review the Record Size Limit of Duplicate Set (ZCH_DI_MERGEREQ_REC_SIZE). This profile optiondetermines the maximum number of records in the duplicate set that can be merged automatically. By default,the value is set to 10 records.

◦ Set the Survivorship Enabled profile option (ZCH_ENABLE_SURVIVORSHIP) to Yes. This profile optionenables the survivorship rules to select the master record and retain the attributes during a merge or updateoperation.

• Define Survivorship: Navigate to this task through the Setup and Maintenance work area to create Set Mastersurvivorship rules or to activate the predefined rules. Set Master survivorship rules are used to choose the masterrecord for merge requests created from the duplicate identification batch.

If there are no active Set Master rules or if the Set Master rules did not trigger, then the merge request must bereviewed manually. Even if the ZCH_AUTO_MERGE_THRESHOLD profile option is set, the score for all records isabove the threshold value, and the number of records is below the record size limit you must activate Set Masterrules to complete the automerge without manual review.

Note: You can use the Set Attribute rules with Set Master rules to determine the Golden Master record.For automerge, Set Master rule is required.

• Define Data Quality: Navigate to this task through the Setup and Maintenance work area to perform the followingimplementation steps:

◦ Create an active Match Configuration in Manage Enterprise Data Quality Matching Configurations task or usea predefined Match Configuration. Rebuild the keys if necessary.

◦ Enable EDQ Real Time and Batch Basic Match Server in Manage Server Configurations task.

Running AutomergeRunning automerge involves the following two steps:

1. Create a duplicate identification batch and select Create Merge Request as the Automatic Processing Option.



166

2. Run the task Run Request Dispatch Job to disposition the duplicate resolution sets.

The Dispatch Job processes any resolution request in Pending or Submitted status. You can run this job in two modes:

• On demand. Do the following steps to set up a recurring job:

a. Navigate to the Run Request Dispatch Job task through the Setup and Maintenance work area.b. Click Submit.

• Per a specific schedule: Do the following steps to set up a recurring job:

a. Navigate to Run Request Dispatch Job task.b. Click Advanced.c. Click Schedule tab and select the Using a Schedule radio button.d. Select a required frequency and click Submit.

To see the list of dispatch jobs, and their statuses:

1. Go to the Tools section on the Navigator2. Click the Scheduled Processes link under Tools.3. View the status of the Schedule Duplicate Resolution Requests process.

Troubleshooting Automerge IssuesAfter you create your Duplicate Identification Batch, drill down into the completed batch to see the results. If duplicate setshave been found, and automerge is enabled, resolution requests are automatically submitted for merging.

If the resolution request was not submitted automatically, you can drill down to the duplicate set and compare the score foreach record with the threshold in the ZCH_AUTO_MERGE_THRESHOLD profile option and the number of records with thelimit in the ZCH_DI_MERGEREQ_REC_SIZE profile option. If all scores are above the threshold and the number of records isbelow the limit, verify that Set Master rules are active and triggered to choose a master for the records in the duplicate set,and that ZCH_ENABLE_SURVIVORSHIP is set to yes.


Chapter 16Integrating Customer Data Management with Other Cloud

Services

167

16 Integrating Customer Data Managementwith Other Cloud Services

Customer Data Management Cloud IntegrationApproaches: ExplainedYou can integrate Customer Data Management Cloud with other cloud services using REST APIs and SOAP APIs to provideaddress cleansing, duplicate identification, and duplicate resolution capabilities. Alternatively you can use the IntegrationCloud Service to develop work flows to integrate Customer Data Management with other cloud based or on-premiseapplications.

Customer Data Management Cloud Integration Using REST APIsOracle Customer Data Management the (CDM) Cloud provides multiple public REST APIs that can be used to access datastored in the CDM Cloud and construct integrations to other systems. The APIs include resources to Get, Post (create),Patch (update), and Delete organizations (accounts) and persons (contacts). Also there are resources to identify and createresolution request for duplicate parties.

For more information on public REST APIs, see REST API for Oracle Sales Cloud in the Related Topics section.

Customer Data Management Cloud Integration Using SOAP APIsOracle Customer Data Management (CDM) Cloud provides SOAP services to create and update organizations (accounts) andpersons (contacts). You can also use these services to identify and resolve duplicate parties.

For more information on SOAP APIs, see SOAP Web Services for Sales Cloud in the Related Topics section.

Customer Data Management Cloud Integration with Import and ExportOracle Customer Data Management (CDM) Cloud lets you use File-Based Data Import and Export, Bulk Export, and DataImport to import and export application data using text or XML files. You can also use import to create or update records inOracle Customer Data Management Cloud.

You can configure the import process to:

• Define deduplication within the data being loaded.

• Define deduplication of the data being loaded against the records that exist in the database.

You can also select a matching configuration to identify duplicates and specify the action to perform on the duplicate recordsduring the import process.

For more information on File-Based Data Import and Export, see Understanding File-Based Data Import and Export in theRelated Topics section.



Services

168

Customer Data Management Cloud Integration Using the Integration CloudServiceYou can use the Integration Cloud Service to leverage predefined integrations between Customer Data Management Cloud,other cloud services, and on premise applications. For example, you can integrate Oracle Sale Cloud and Oracle ServiceCloud with Customer Data Management Cloud to provide the duplicate resolution capability. Using this capability, you canmerge an Oracle Sales Cloud account (organization) or contact (person) with an Oracle Service Cloud account (organization)or contact (person).

For more information on the Integration Cloud Service, see Oracle Integration Cloud Service in the Related Topics section.

Customer Data Management Integrations for Accounts (Organization) andContacts (Persons)The following table shows the possible integrations options for Oracle Customer Data Management Cloud:

CDMProcess(Batch Job)

SOAPService

RESTService

Data Import(for accountReceivablesonly)

File-BasedData Import

File-BasedData Import(SimplifiedView)

File-BasedData Export

ICS Events Comments

AddressCleansing

No

AddressCleansing isavailable bythe RESTservice fromAddressVerificationCloudServiceonly.

Yes

No

No

Yes (BatchSummaryonly). Doesnot includechild objectsuch asduplicateaddress andrelationships.

No

File Exportis onlyavailablefromCustomerDataManagementwork area.

DuplicateIdentification

No

No

Yes

Yes

No

Yes (BatchSummaryonly). Doesnot includechild objectsuch asduplicateaddress andrelationships.

No

File Exportis onlyavailablefromCustomerDataManagementwork area.

DuplicateResolutionandMerging

Yes. SOAPservice cancreate newresolutionrequestsand queryexistingresolutionrequestsbut cannotupdate theexistingrequests.

Yes. Restservice cancreate newresolutionrequestand queryexistingresolutionrequestsbut cannotupdate theexistingrequests.

Yes

No

No

Yes. Doesnot includechild objectsuch asduplicateaddress andrelationships.

Yes. PublicResolutionRequestUpdated.

Bulk Exportcan be usedfor duplicateparty detailsin theDuplicateResolution.See,ImplementingCDM in theRelatedTopicssection.



Services

169

CDMProcess(Batch Job)

SOAPService

RESTService

Data Import(for accountReceivablesonly)

File-BasedData Import

File-BasedData Import(SimplifiedView)

File-BasedData Export

ICS Events Comments

DataEnrichment

No

Dataenrichmentis availableby RESTservicefrom OracleSocial Dataand InsightCloudServiceonly.

No

No

No

Yes

No

Related Topics

• REST API for Oracle Sales Cloud

• SOAP Web Services for Sales Cloud

• Understanding File-Based Data Import and Export

• Oracle Integration Cloud Service

• Implementing CDM

Merge Operation Process During Integration Cloud ServiceBased Integration: ExplainedOracle Customer Data Management (CDM) Cloud acts as the customer master during Integration Cloud Service basedintegration between different cloud services (also known as spoke systems). You can use CDM Cloud to cleanse,consolidate, and share customer data across integrated cloud services, such as Oracle Sales Cloud and Oracle Servicecloud. This topic explains how the duplicate resolution capability of the Customer Data Management Cloud merges recordsacross integrated cloud services, for example, how it merges an Oracle Sales Cloud account or contact with an OracleService Cloud account or contact.

Merge Operation Process for Point to Point IntegrationIn this integration scenario, the Customer Data Management Cloud provides the duplicate resolution capability to a singlespoke system.

http://docs.oracle.com/cloud/latest/salescs_gs/FAAPS/index.html

http://docs.oracle.com/cloud/latest/salescs_gs/OESWS/toc.htm

https://docs.oracle.com/en/cloud/saas/applications-common/r13-update17d/oafdi/toc.htm

https://docs.oracle.com/en/cloud/paas/integration-cloud-service/index.html

https://docs.oracle.com/en/cloud/saas/customer-data-management/r13-update17d/faicd/manage-bulk-data-export.html#FAICD291412



Services

170

The following diagram shows the before merge status of two contacts, Contact A and Contact B, of an account from Spoke1.

Contact AFirst Name = JohnMiddle Name = D.


ActiveActive

Contact BFirst Name = John

Middle Name = David


Middle Name = David

Active Active

Original System Reference A300012345634567862

Original System Reference B300012987489378234

External Reference A300012345634567862

External Reference B300012987489378234

CDM Spoke 1

The following diagram illustrates how the two contacts, A and B, of the account from Spoke 1 are being merged in CDMCloud and how the Contact A emerges as the survivor and the Contact B becomes the victim.



Services

171



Integration for Contact A stays intact

ActiveActive


Middle Name = David


Middle Name = DavidIntegration should delete Contact B

Inactive Active

Original System Reference A

300012345634567862

Original System Reference B

300012987489378234



CDM Spoke 1

Spoke 1 Identification for Contact B

The following diagram shows the after merge status of two contacts, A and B, of the account. Note that in Spoke 1 onlyContact A has survived and remained active after the merge.



Services

172



Integration for Contact A stays intact

ActiveActive


Middle Name = David

Inactive

Original System Reference A300012345634567862

Original System Reference B300012987489378234


CDM Spoke1

Merge Operation Process for Publish and Subscribe IntegrationIn this integration scenario, the Customer Data Management Cloud provides the duplicate resolution capability to two or moreintegrated cloud services or spoke systems. Duplicate data from spoke systems is consolidated in the CDM cloud and themastered data is published to the subscribing spoke systems.



Services

173

The following diagram shows the before merge status of two contacts, A and B, of an account that exists both in Spoke 1and Spoke 2.

Contact AFirst Name = JohnMiddle Name = D.Last Name = Doe


ActiveActive


Middle Name = DavidLast Name = Doe



Active Active


300012345634567862


300012987489378234



CDM Spoke 1






Active

Active Spoke 2

The following diagram shows the after merge status of two contacts, A and B, of the account.



Services

174



ActiveActive





InactiveDeleted


300012345634567862


300012987489378234



CDM

Spoke 1






Active

DeletedSpoke 2

Take note of the following:

• Data about Contacts A and B comes in the Customer Data Management cloud from both the spoke systems.

• The merge is taking place in the Customer Data Management cloud and any owned objects by the victims aremoved (re-parented) to survivor record in CDM.

• The mastered data is published to both the spoke systems and, consequently, Contact B is deleted from both thespoke systems.

oracle · 2018-07-11 · nokia geography reference data: ... oracle customers that have purchased...

Documents