Oracle. Customer Data Management Cloud Getting Started with Your Customer Data Management Implementation. Release 13 (update 17D)

Transcription

1 Oracle Customer Data Management Cloud Getting Started with Your Customer Data Management Release 13 (update 17D)

2 Release 13 (update 17D) Part Number E Copyright , Oracle /or its affiliates. All rights reserved. Author: Jesna Narayanan Contributor: Tracie Felker, Virinder Kaur, Ashwini Malthankar, Nakishore Palasala, Parth Shah, Abhishek Sura, Vijay Tiwary, Jiri Weiss, This software related documentation are provided under a license agreement containing restrictions on use disclosure are protected by intellectual 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, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice is not warranted to be error-free. If you find any errors, please report them to us 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 the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, / or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, /or documentation, shall be subject to license terms license restrictions applicable 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 in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, other measures to ensure its safe use. Oracle Corporation its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle Java are registered trademarks of Oracle /or its affiliates. Other names may be trademarks of their respective owners. Intel Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware documentation may provide access to or information about content, products, services from third parties. Oracle Corporation its affiliates are not responsible for expressly disclaim all warranties of any kind with respect to third-party content, products, services unless otherwise set forth in an applicable agreement between you Oracle. Oracle Corporation its affiliates will not be responsible for any loss, 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 agreement between you Oracle. The business names used in this documentation are fictitious, are not intended to identify any real companies currently or previously in existence. Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit pls/topic/lookup?ctx=acc&id=info or visit if you are hearing impaired.

3 Contents Preface 1 i About this Guide Purpose Scope Audience How to Use This Guide... 1 What You Will Be Able to Do After Completing the Setups in This Guide Signing In Performing Preliminary Setup Tasks Preliminary Setup Tasks: Overview Signing In for the First Time Familiarizing Yourself with Useful Toolbar Icons Accessing Setup Tasks Enabling the Customer Data Management Offering for... 5 Verifying the Need for Additional Licenses Enabling Quick Access to Setup Tasks Setup Task Overview 9 Prerequisites for Setting Up the Customer Data Management Cloud Service... 9 Setup Tasks Completed for You in Service Setup Task Summary Creating Setup Users Setup Users Creation About Creating Setup Users Creating a Job for Provisioning Setup Users Creating the Provisioning Rule for Setup Users Creating Setup Users Designating a Single User to Receive All Credential s Granting the Initial User the Same Privileges as Other Setup Users Resetting User Passwords... 24

4 5 Creating Customer Data Management Application Users Application Users Creation: Overview Creating Customer Data Management Application Users Setting Up Geography Data Geography Setup: Overview Importing Nokia Geography Reference Data Countries Available for Import of Nokia Geography Reference Data Importing Third Party Geography Data Using File Based Import Setting Up Geocoding Address Cleansing Setting Up Geography Validation Turning on Validation for Address Import Importing Accounts Contacts Account Contact Import About Importing Accounts Contacts About Importing Addresses for Accounts Contacts Exporting Account Owner Party IDs Specifying the Industry Classification for Accounts Downloading Templates for Importing Accounts Contacts Understing the Account Import Template Understing the Contact Import Template Researching Additional Account Contact Attributes for Import Creating a New Mapping for a Changed Import Template Importing the Accounts Contacts Files Troubleshooting Common Import Errors Importing Accounts Contacts Using Simplified View Import Objects Importing Data Using Simplified View Import Objects: Overview Importing Contacts Using the Contact - Simplified View Import Object: Procedure Importing Accounts using the Account - Simplified View Import Object: Procedure Configuring Profile Options 85 Customer Hub Profile Options Setup: Overview Managing Customer Hub Profile Options

5 10 Configuring Address Verification Address Verification: Setup Overview Managing Server Configurations for Cleansing Configuring the Address Verification Cloud Service Managing Enterprise Data Quality Cleansing Configurations Setting Up Address Cleansing Address Validation Enabling Search Mode for Address Verification Cloud Service 11 Configuring Duplicate Identification Duplicate Identification: Setup Overview Managing Server Configurations Managing Enterprise Data Quality Matching Configurations Mapping Matching Attributes Managing Key Generation: Explained Selecting Sources of Match Rules Scoring: Points to Consider Managing Custom Match Rules Scoring: Explained Creating Custom Match Rules: Procedure Configuring Duplicate Resolution 111 Duplicate Resolution: Setup Overview Managing Source System Confidence Managing Survivorship Rules Defining Survivorship Rules Defining Set Master Record Rules Defining Set Attribute Value Rules Managing Agreement Rules Defining Agreement Rules Running the Request Dispatch Job High Volume Batch Deduplication: Best Practices Guideline Configuring Automerge Automerge: Setup Overview Understing How Records are Selected for Automerge Implementing Automerge

6

7 Preface Preface This preface introduces information sources that can help you use the application. Oracle Applications Help Use the help icon to access Oracle Applications Help in the application. If you don't see any help icons on your page, click the Show Help icon in the global header. Not all pages have help icons. You can also access Oracle Applications Help at Using Applications Help Watch: This video tutorial shows you how to find help use help features. Additional Resources Community: Use Oracle Applications Customer Connect to get information from experts at Oracle, the partner community, other users. Guides Videos: Go to the Oracle Help Center to find guides videos. Training: Take courses on Oracle Cloud from Oracle University. Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at Oracle Accessibility Program. Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit or visit ctx=acc&id=trs if you are hearing impaired. Comments Suggestions Please give us feedback about Oracle Applications Help guides! You can send to: i

8 Preface ii

9 1 Chapter 1 About this Guide About this Guide Purpose Scope This guide describes how to get started with the implementation of Customer Data Management cloud service capabilities such as duplicate identification, duplicate resolution, address verification, data enrichment. This guide uses the default settings provided by Oracle does not provide detailed explanations of all available features. This document supplements stard product documentation, which you are encouraged to review. To find documentation other learning resources, such as guides, white papers, videos, visit the Help Center for Oracle Customer Data Management Cloud. Related Topics Audience This document is for Oracle customers (System Integrators, Sales Consultants) Support involved in implementation of the Customer Data Management Cloud Service. The tips techniques detailed in this document may not be suitable for an onpremise deployment. How to Use This Guide Here'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 underst the setups the chapter covers. Use the Setup Overview as a guide to the setups you must perform. The remaining topics in the chapter provide the step-by-step details of how to perform each of those setups. Refer to other guides for full explanation of the different features options. What You Will Be Able to Do After Completing the Setups in This Guide After completing the setups in this guide, you should be able to: Identify duplicates: Identify potential duplicate account, contact, address records in real time when your application users create a customer record, thus preventing entry of duplicate records. 1

10 Chapter 1 About this Guide Identify potential duplicates using batch processing for records already in the database or potential duplicates of 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 verify that the address is an actual postal address. Enrich Data: Enrich account contact data to ensure it's comprehensive 2

11 Chapter 2 Signing In Performing Preliminary Setup Tasks 2 Signing In Performing Preliminary Setup Tasks Preliminary Setup Tasks: Overview Before you start implementing your Customer Data Management application according to the instructions in this guide, you must complete the preliminary tasks listed in the following table. Step Description Where to Get More Details Complete the Service Administrator Action List Complete the actions listed in the Service Administrator Action List provided by Oracle See Signing In for the First Time topic in this chapter. Enable the Customer Data Management offering for implementation Enable the Customer Data Management offering for implementation in the Setup Maintenance work area. See the Enabling the Customer Data Management Offering for topic in this chapter. Ascertain that you have the required licenses Verify that you have all the additional licenses required for your implementation of the Customer Data Management capabilities. See the Verifying the Need for Additional Licenses topic in this chapter. Install the CDM Project Install the CDM implementation project into your environment to speed up your access to the implementation tasks. See the Enabling Quick Access to Setup Tasks topic in this chapter. You can download the implementation project from support. oracle.com upload it into your environment. Signing In for the First Time As part of your Oracle Sales Cloud Service, you are provisioned two Customer Data Management Cloud environments, production test. When your test environment is ready, Oracle sends a Welcome to the person designated as the Service, Account, Identity Domain administrator when you signed up with the. The Welcome to the administrator for the contains all the details about your test production environments, login credentials, an Action List. Before you sign in for the first time, read the environment access , complete the tasks in the Service Administrator Action List, familiarize yourself with the different user interfaces basic navigation. Related Topics Service Administrator Action List 3

12 Chapter 2 Signing In Performing Preliminary Setup Tasks Familiarizing Yourself with Useful Toolbar Icons The topic lists the most useful tool bar icons in the applications home page. The following figure lists the tool bar icons 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 Recent Items Marks a page as favorite provides access 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, opens the Settings Actions menu. From the menu, you can sign out, personalize the UI, access help, navigate to the Setup Maintenance work area. Accessing Setup Tasks You perform setup tasks in the Setup Maintenance work area in other work areas of the application. This topic explains the different ways of accessing these setup tasks. Speeding Up Access to Setup Tasks Using the Project You gain faster access to the setup tasks covered in the Getting Started with Your Oracle Customer Data Management Cloud guide by downloading installing an implementation project provided by Oracle. The implementation project complements the structure of this guide provides a direct link to each core setup task. 4

13 Chapter 2 Signing In Performing Preliminary Setup Tasks If you do not use the implementation project, then you must navigate to each individual task separately. Depending on the task, you must either search for the task by name in the Setup Maintenance work area or navigate to a different work area using the Navigator. Searching for Setup Tasks in the Setup Maintenance Work Area You can also search for individual tasks by name in the Setup Maintenance work area. Use the percent sign (%) to represent missing letters or words. For example, to find the Manage HCM Role Provisioning Rules task, you can search for manage HCM % rules. The searches are not case-sensitive. Navigating to Other Work Areas for Setup When 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 permissions assigned to each user, rather than on the features you have purchased. Because a setup user has a broad range of permissions, not all of the selections are applicable to your setup. Aside from the Setup Maintenance work area, you use only a small number of the available work areas accessible from the Navigator menu. The most important of these include: My Team Manage Users Use this work area for creating managing individual users in the UI. The Manage Users task in the Setup Maintenance work area opens the same work area. Tools Scheduled Processes Use this work area for scheduling monitoring background processes. The Scheduled Processes work area is not available when you first sign in as the initial user. You must grant yourself the additional privileges as described in this guide. Application Composer Use Application Composer to configure enhance your application. Customer Data Management Use the different work areas under this heading for functional setup to create data used to test your Customer Data Management application. Note: The Customer Data Management Cloud Service uses File-Based Data Import. The Data Import functionality that lets you import data in bulk is available only for an on-premise implementation. 5

14 Chapter 2 Signing In Performing Preliminary Setup Tasks Enabling the Customer Data Management Offering for Before you start work, you must enable the functional areas of the Customer Data Management Cloud that you are going to use for implementation. Enabling the different areas makes it possible for you to track the progress of your implementation from within the Setup Maintenance work area, in some cases, even turn on applicable features UI regions. You can enable only the functional areas you are implementing now, if required, add more later on. To enable the functional areas: 1. Navigate to the Setup 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 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 Data Quality, Define Customer Hub Configuration, Customer Data Management Business Intelligence Analytics. 5. Click Actions select Go to Offerings. You are returned to the Setup Maintenance page. Verifying the Need for Additional Licenses You 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 Oracle Sales Cloud license provides you access to the following customer data management functionality: Customer Data Management Dashboard Data Steward Productivity Tools File-Based Import Data Import Manual Merge Auto-Merging Survivorship Agreement Rules Audit Reporting Link Relate Account Hierarchy Management To make use of the all the capabilities of the Customer Data Management Cloud Service, you require the following additional licenses: Oracle Fusion Data Quality Cloud Service: This service enables you to identify potential duplicates records in the database or potential duplicates of the records in the database within an import batch. You can use this service for both real-time batch duplicate identification. Note that a stalone customer of the Customer Data Management Cloud Service must purchase the Oracle Fusion Data Quality Cloud Service because both the cloud services are sold together. 6

15 Chapter 2 Signing In Performing Preliminary Setup Tasks Address Verification Cloud Service: This service enables you to cleanse an address to conform to postal requirements verify that the address is an actual postal address. Oracle Social Data Insight Cloud Service: This service enables you to enrich account contact data to ensure it is comprehensive. Enabling Quick Access to Setup Tasks The : Getting Started with Your guide describes how to speed up your initial setup using an implementation project supplied by Oracle. The implementation project serves as a launch pad for many of the setup tasks covered in this guide, so you don't have to search for individual setup tasks or navigate to work areas, including the scheduled processes. Downloading the Project to Your Desktop Download the implementation project to your desktop from the : Getting Started with Your : Project (Doc ID ) available on support.oracle.com. There are two variations of the implementation project that you download depending on how much functionality you want to set up: Quick Setup Basic Customer Data Management: Use this implementation project for setting up the customer data management functionality shipped with Oracle Sales Cloud: Customer Data Management Dashboard Data Steward Productivity Tools File-Based Import Data Import Manual Merge Auto-Merge Survivorship Agreement Rules Audit Reporting Quick Setup Customer Data Management Cloud Service: Use this implementation project to set up all the capabilities 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 records already in the database or potential duplicates of the records in the database within an import batch. You can use this service for both real-time batch duplicate identification. Address Verification Cloud Service: This service enables you to cleanse an address to confirm to postal requirements verify that the address is an actual postal address. Oracle Social Data Insight Cloud Service: This service enables you to enrich account contact data to ensure it is comprehensive. The Getting Started with Your guide covers the tasks in both variations. Installing the Project You Downloaded Install the implementation project by uploading the configuration package file using these steps: 1. Navigate to the Setup Maintenance work area. 7

16 2. Click the Tasks menu icon. 3. Click the Manage Configuration Packages link. Chapter 2 Signing In Performing Preliminary Setup Tasks The Manage Configuration Packages page appears. 4. Click Upload. The Upload Configuration Package page appears. 5. Click Browse 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 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 Maintenance work area page. 10. Click Projects. The Projects page appears listing your project. 11. Click the name link to open the implementation project. Using the Project As a Launchpad for Your Tasks Follow these steps to use the implementation project as the launchpad for your implementation tasks. 1. Navigate to the Setup Maintenance work area by clicking the icon on the springboard. The Setup Maintenance page appears. 2. Click Projects. The 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 Tasks region. 4. Click a folder to open it 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. 8

17 3 Chapter 3 Setup Task Overview Setup Task Overview Prerequisites for Setting Up the Customer Data Management Cloud Service The prerequisites for setting up the Customer Data Management Cloud Service can be broadly grouped into two categories, prerequisite implementation decisions additional licenses. Prerequisite Decisions You have the following two options for setting up the Customer Data Management Cloud Service: Stalone : You want to use Service individually or along with a non-oracle cloud services. The guide describes all the setup steps required for a stalone implementation of the Oracle Customer Data Management Cloud Service. However, to use the Customer Data Management Cloud Service with a non-oracle cloud service, you will have to set up that non-oracle cloud service separately. Add-on : You want to use the Service with another Oracle cloud service, such as Sales Cloud. Details for this implementation option can be found in the respective Getting Started guide for your other Oracle cloud service. For example, if you want to use Customer Data Management Cloud Service with Sales Cloud you should see Getting Started with Your Sales Cloud in the Help Center. Note that the implementation tasks may vary slightly depending on the implementation option that you select. Prerequisite Additional Licenses Customer Data Management is shipped free of cost with some Oracle Cloud Services such as Oracle Sales Cloud. An Oracle Sales Cloud license provides you access to the following customer data management functionality: Customer Data Management Dashboard Data Steward Productivity Tools File-Based Import Data Import Manual Merge Auto-Merging Survivorship Agreement Rules Audit Reporting However, to make use of the all the capabilities of the Customer Data Management cloud service, you require the following additional licenses: Oracle Fusion Data Quality Cloud Service: This service enables you to identify potential duplicates records already in the database or potential duplicates of the records in the database within an import batch. You can use this service for both real-time batch duplicate identification. Address Verification Cloud Service: This service enables you to cleanse an address to confirm to postal requirements verify that the address is an actual postal address. 9

18 Chapter 3 Setup Task Overview Oracle Social Data Insight Cloud Service: This service enables you to enrich account contact data to ensure it is comprehensive. Note that a stalone customer of the Customer Data Management Cloud Service must also purchase the Oracle Fusion Data Quality Cloud Service, because these two cloud services are always sold together. Setup Tasks Completed for You in Oracle Customer Data Management Cloud Service Setup Tasks Completed for You in When Oracle provisions a Customer Data Management Cloud Service environment, we generally set up some basic information about your company that you provide while signing up for the service. This initial setup includes company name, corporate address, legal entity, business unit, corporate currency, the creation of an initial user. You can verify the values using the tasks provided in this topic. You can reach the tasks directly from the implementation project provided by Oracle, or by searching for the tasks in the Setup Maintenance work area. Note that if you are setting up Service together with another cloud service such as Oracle Global Human Resources Cloud, Oracle Procurement Cloud, Oracle Financials Cloud, then Oracle does not complete any of these tasks in your environment. In such shared Global Single Instance (GSI) environments, you must set up enterprise structures, such as legal entity business unit, in the other cloud services according to the instructions provided in 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 cloud service. What Oracle Enters for You Description Setup Task Name Your company name Access this task to view the Oracle entered company name based on the information you provided. Manage Enterprise HCM Information Your corporate address This is the address you provided. As a best practice, use the same legal corporate address used for tax information. To review edit the address, you must search for the address first by the country where it is located. If you do make any changes, then you must remember to click Save Close for 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 this task. In the Create User UI, the legal entity is called the Legal Employer. Manage Legal Entity HCM Information The legal entity name Oracle enters for you is your enterprise name followed by the suffix 10

19 Chapter 3 What Oracle Enters for You Setup Task Overview Description Setup Task Name LE. Follow these steps to verify the legal entity name: 1. On the Manage Legal Entity HCM Information page, click Advanced to access the Advanced Search page. 2. In the Legal Entity Name field, change the Start with operator to Contains enter LE as the search parameter. 3. Click Search. Creates a business unit sets the business unit as the default. Oracle creates one business unit for creating your employee users. The business unit name is your enterprise name followed by the suffix BU. Oracle then sets the profile option HZ_ DEFAULT_ BU_CRM to that business unit. Manage Common CRM Business Unit Profile Options In addition, Oracle creates one user for you. This is the initial user you received in the welcome . The initial user is provisioned with the following job roles: Application Consultant IT Security Manager Application Diagnostic Administrator The initial user can create other users, change security settings, perform many, but not all, implementation tasks. The user is not provisioned with all the security permissions required to complete the setups in this guide, but has the ability to assign these roles to herself to others. For example, the initial user does not have the permission to set up search run monitor scheduled processes. Setup Task Summary The following table summarizes the setups covered by this guide 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 in the project, you must navigate to specific work areas or tasks described in the following table. Step Setup Description Create Setup Users Grant yourself the additional privileges that you need to complete the setups in this guide create any additional users to help you with setup. Task Names Manage Job Manage HCM Role Provisioning Rules Manage Users Project Folder Create Setup Users Setup users are not part of your resource organization. They can be systems integrators you hired for the implementation, for example. Create Application Users Create a few application users to test your setups. You need to Manage Users Create Customer Data Management Application Users 11

20 Chapter 3 Step Setup Description Setup Task Overview Task Names Project Folder ensure that the provisioning rules you created work as intended. Import Geographies Import geography reference data for the countries where you do business set up validation for required address elements. This step is required to validate addresses. Manage Geographies Manage Administrator Profile Values Set Up Geography Data Manage Trading Community Source Systems Schedule Export Process Manage Administrator Profile Values Manage File Import Mappings Manage File Import Activities Import Accounts Contacts You must enforce validation for addresses you import, by setting the profile option Geography Address Validation Enabled to Yes using the Manage Administrator Profile Values task. Importing Account, Contact, other Customer information Get ready to import accounts contacts by: Registering the application that's the source of your account contacts data Exporting the Party IDs of the sales resources you created earlier Specifying which industry classification category you are using by setting the profile option MOT_INDUSTRY_CLASS_CATEGORY. Import your accounts contacts from a file using templates you can download modify. Configure Profile Options Configure Address Verification Review update profile options to optimize the implementation of the Customer Data Management Cloud Service according to your business requirements. This step includes address cleansing address verification setup. Address cleansing is a process that corrects, parses, completes address data based on postal requirements. Manage Customer Hub Profile Options Address verification requires a separate license for the Address Verification Cloud Service. This service enables you to cleanse an address to conform to postal Manage Server Configurations Manage Enterprise Data Quality Cleansing Configurations Manage Sales Cloud to Data Cloud Integration Manage Administrator Profile Values Manage Geographies Define Customer Hub Configuration Define Data Quality 12

21 Chapter 3 Step Setup Description Setup Task Overview Task Names Project Folder requirements verify that the address is an actual postal address. You can set up address verification by: Configure Duplicate Identification Enabling the server configurations for cleansing Configuring the address verification cloud service Managing enterprise data quality cleansing configurations Defining address cleansing address verification Complete this set up to identify duplicates in the following situations: Identify potential duplicate account, contact, address records in real-time when your application users create a customer 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. Manage Server Configurations Manage Enterprise Data Quality Matching Configurations Define Customer Hub Configuration Duplicate identification uses the Enterprise Data Quality (EDQ) service. You require a separate license for the Data Quality Cloud Service. You can set up duplicate identification by: Enabling the server configurations for matching 13

22 Chapter 3 Step Setup Description Configure Duplicate Resolution Configure Auto Merge Task Names Project Folder Setting up Enterprise Data Quality matching configurations Complete the following set up to consolidate duplicates by merging or linking them: Setup Task Overview Defining source system confidence Creating appropriate survivorship merge agreement rules Set up the automerge functionality to merge duplicate records through automated processing without any approval or intervention from the data steward. Manage Source System Confidence Manage Survivorship Rules Manage Customer Hub Profile Options Manage Agreement Rules Run Request Dispatch Job Manage Customer Hub Profile Options Define Survivorship Define Data Quality Define Customer Hub Configuration Define Customer Hub Configuration Define Data Quality Note that the implementation steps may vary slightly depending on the implementation option that you select, stalone implementation 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 14

23 Chapter 4 4 Creating Setup Users Creating Setup Users Setup Users Creation The initial user created for you by Oracle is configured to perform the security tasks, which include the creation of other users the granting of additional privileges. After you have signed in for the first time, you are ready to provide yourself with additional privileges to create other users who will help you with application setup. This chapter assumes that the users doing the setup are not resources who are part of the resource organization. However, there is nothing stopping you from providing 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 conceptual overview of creating setup users. Detailed steps are provided in procedures in this chapter. You can access all tasks from the Create Setup Users folder in your implementation project. Step Description Task Name Where to Get More Details Create a job for Provisioning Setup Users Create a job, Customer Data Management Administrator, which you can later assign to all users who are performing setup are not part of your resource organization. Manage Job See Creating a Job for Provisioning Setup Users topic in this chapter. Manage HCM Role Provisioning Rules See Creating the Provisioning Rule for Setup Users topic in this chapter. Manage Users See Creating Setup Users topic in this chapter. What you name the job doesn't matter. You use the job only as a condition in the rule to provision setup users with the permissions they require to complete all setups. Create a rule to provision roles to that job Create a role provisioning rule that automatically provisions the following job roles to all users with the Customer Data Management Administrator job: Create setup users associate the job roles to them. Application Consultant IT Security Manager Application Diagnostic Administrator Master Data Management Application Administrator Create each setup user as a user of type employee with the Customer Data Management Administrator job associate the job roles to them. 15

24 Chapter 4 Creating Setup Users Step Description Task Name Where to Get More Details Grant the Initial User the Same Privileges as Other Setup Users Grant yourself, the initial user, the same additional privileges the other setup users have by editing the initial user profile. Manage Users See Granting the Initial User the Same Privileges as Other Setup Users topic in this chapter. About Creating Setup Users Although the initial user can perform many of the setup tasks in this guide, this user cannot perform all of them without additional privileges. For example, the initial user cannot run scheduled processes, including the geography import task indexing for searches. About Security the Initial Setup Tasks Oracle follows the industry stard Role Based Access Control approach to security. In Oracle Applications Cloud, the privileges 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 as reviewing sales team performance approving forecasts. The Employee abstract role adds the ability to access reports manage personal profile information. The Resource abstract role makes it possible for a user to be assigned as a sales resource to accounts opportunities. To perform the initial setup tasks mentioned in this guide, you must provision users with all the job roles granted to the initial user. These job roles are: Application 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 data. In addition, you may also provision them with: Employee (abstract role) Provides access to BI reports the ability to run 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) 16

25 Chapter 4 Creating Setup Users Performs customer data management activities including data import, cleansing, duplicate identification, duplicate resolution. In addition, the Customer Data Steward can perform the following few tasks in the Setup Maintenance 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 has additional privileges including assigning requests. In addition, the Customer Data Steward can perform the following few tasks in the Setup 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 as well. In, you provision job roles abstract roles to users using role provisioning rules. If users meet the conditions of the rule, the application provisions them with the job roles abstract roles that you want to 17

26 Chapter 4 Creating Setup Users assign to the user. The following figure shows how the role provisioning rule conditions must be met to provision the job roles abstract roles. User Role Provisioning Rule Condition 1 Condition 2... Abstract Role Job Role1 Job Role 2 The role provisioning rules you use to provision customer data management application users the initial setup users have different conditions. Provisioning Customer Data Management Application Users You provision job roles to customer data management users, including data steward managers customer data steward based on the role the user plays in the resource organization. This resource role is the job title which appears under the user name in the Resource Directory. 18

27 Chapter 4 Creating Setup Users The following figure shows resource directory page with the resource role appearing as job tittle under the user name highlighted with the callout 1. 1 Special Provisioning Rule for Setup Users Because users doing the initial setup aren't part of your company's resource organization, you don't want them to be a part of the resource hierarchy you don't want them to appear in the Resource Directory. For these reasons, you do not create setup users as resources, 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 as the condition. You create a Customer Data Management Administrator job, a field not normally used in Oracle Customer Data Management Cloud, provision the setup user with job roles based on this job. Customer Data Management Administrator 19

28 Chapter 4 Creating Setup Users job contains roles such as Application Consultant, Application Diagnostic Administrator, It Security Manager, Sales Analysis, Customer Data Management Administrator. The following figure illustrates the two provisioning rules used to provision the Customer Data Management administrator job role employee role to the setup user. The employee role provisioning rule is already set up for you by Oracle unless you are implementing your application in a Global Single Instance environment. In GSI environments, you must set up all provisioning rules yourself. What Happens When You Create Users When you create users, : Creates accounts, user names, temporary passwords Provisions the job roles abstract roles the users require to carry out their jobs Sends users an with their sign-in credentials Tip: System notification s, including the initial with sign-in information, do not include the URL for accessing. You must provide this URL to users separately. 20

29 Chapter 4 Creating Setup Users Creating a Job for Provisioning Setup Users Use this procedure to create a job that you can use to assign setup users with implementation privileges. You use this job as a condition in the provisioning rule you create 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 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 Maintenance work area. To open the task from the implementation project: a. Navigate to the Setup Maintenance work area by clicking the Setup Maintenance icon on the springboard. The springboard is the page you see when you first sign in. b. Click Projects. c. In the Search Results region on the 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, 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 been created. Creating the Provisioning Rule for Setup Users Use this procedure to create the provisioning rule which automatically provisions users assigned the Customer Data Management 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 open the Manage HCM Role Provisioning Rules task from the implementation project. Alternatively, you can search for the task by name in the Setup Maintenance work area. The Manage Role Mappings page appears. 2. Click Create. The Create Role Mapping page appears. 21

30 Chapter 4 Creating Setup Users 3. In the Mapping Name field, enter Customer Data Management Administrator, or another name that will help you identify this mapping in the future. 4. In the Conditions region, select Customer Data Management Administrator, the job you created earlier, from the Job list. If the job does not appear in the list, click Search 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 select each of the following job roles: Application 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 Close. Creating Setup Users After 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 task in the implementation project. Alternatively, you can click the Manage Users link under the My Team heading in the Navigator. The Manage Users page appears. 2. Click Create. The Create User page appears. 3. Enter the user's name a unique in the Personal Details region. The application automatically sends the initial sign-in credentials to this 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 name for you. By default, the application uses the as the user name. 5. In the User Notification Preferences region, select the Send user name password option. The option to send the user name password through is available only before you save the user record for the first time. You do not see the User Notification Preferences region 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 user you must reset the user password manually using the procedure described in the Resetting User Passwords topic. 6. In the Employment Information region, enter the following: Select Employee from the Person Type list. 22

31 Chapter 4 Creating Setup Users From the Legal Employer list, select the only value available, the legal employer Oracle created for you using the information you provided when you signed up with. From the Business Unit list, select the only value available, the business unit created for you when you signed up. From the Job list, select Customer Data Management Administrator, the job you just created. If the job is not 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 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 run periodically. You can view the status of the request any time you edit this user. When the process is complete, the roles appear in the Current Roles region. 8. Click Save Close. If you have not selected the Send user name password option, then you must reset the password using the procedure described in the Resetting User Passwords topic. Tip: The with the user name password does not include the URL of your application. You must provide the URL to users separately. Designating a Single User to Receive All Credential s You can redirect the s with user credentials temporary passwords to a single user. For example, you may want to send all of the credential s to one of the setup users, so that you can sign in as different sales users test your setups. Note: The application sends the s with initial passwords only once. If you send the initial s to one of the setup users, then you must forward the credentials to the real user, if required. To redirect the credential s to a single user: 1. While signed in as a setup user, open the task Manage Enterprise HCM Information from the implementation project. Alternately, search for the task by name in the Setup Maintenance work area. The Enterprise page appears. 2. Click Edit on the Enterprise page, select Correct. The Edit Enterprise page appears. 3. In the User Role Provisioning Information region, select Yes from the Send User Name Password list enter the of the user to receive the credential s in the Alternate Contact Address field. 4. Make sure the Send User Name Password option is set to Yes. 5. Click Submit. 23

32 6. Close the warning by clicking Yes. 7. Click Done. Chapter 4 Creating Setup Users The user you specified continues to receive all credentials s until you clear the Alternate Contact Address field. Granting the Initial User the Same Privileges as Other Setup Users Use 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 task in the implementation project. You can also click the Manage Users link under the My Team heading in the Navigator. The Manage Users page appears. 2. Enter the first name of the initial user in the Keywords field 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 Search 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 run periodically. You can view the status of the request any time you edit this user. When the process is complete, the roles appear in the Current Roles region. 6. Click Save Close. If you are signed in as the initial user, you must sign in again for the new privileges to take effect. Resetting User Passwords Use the Users tab in the Security Console work area to reset user passwords. You can have the application send out an notification with the URL the users can use to create the password themselves, or you can create passwords of your own choosing. If you are creating users for testing, then entering your own password using the manual option makes it possible 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 then to the Security Console work area. 24

33 Chapter 4 Creating Setup Users You can close any warnings regarding the scheduling of the Import Users 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 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 to users with a URL that they can use to create their own passwords 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 option b. Enter the new password twice. 7. Click Reset Password. If you selected the Automatically generate password option, then the application sends out the enabling the user to change the password sign in. No notification is sent if you selected the manual option. 25

34 Chapter 4 Creating Setup Users 26

35 Chapter 5 Creating Customer Data Management Application Users 5 Creating Customer Data Management Application Users Application Users Creation: Overview Customer 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 from the Manage Users work area. Step Description Task Name Where to Get More Details Create Data Steward Managers Create one or more Data Steward Managers depending on your business requirements. Manage Users The Creating Customer Data Management Application Users topic. Create Customer Data Stewards Create one or more Customer Data Stewards depending on your business requirements. Manage Users The Creating Customer Data Management Application Users topic. Creating Customer Data Management Application Users Use 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 open this task by clicking Manage Users under the My Team heading in the Navigator, or you can search for the task by name in the Setup Maintenance work area. 2. On the Manage Users page, click Create. The Create User page appears. 3. Enter the user's first last names a unique address in the Personal Details region. The application normally sends the initial sign-in credentials to this when you save the record. If you earlier specified an alternate in the Enterprise page, the mail is sent to the alternate address instead. If you do want the to be sent to the user, you must remove that alternate address from the Enterprise page. 4. The application automatically fills the current date in the Hire Date field uses that date as the start date for the resource. 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, the application uses the as the user name. 27

36 Chapter 5 Creating Customer Data Management Application Users 6. In the User Notification region, leave the Send User Name Password option selected if you want the credentials 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 you provided when you signed up with. There should be only one value available: 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 only one 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 not correspond 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 abstract roles according to the role provisioning rules. 10. Click Save Close. The application creates the user. Unless you deselected the Send User Name Password option, the application also sends the with the user name password. 28

37 Chapter 6 6 Setting Up Geography Data Setting Up Geography Data Geography Setup: Overview You must import set up reference geography data for the countries where you do business if you are setting up sales territories using geography as one of your dimensions or if you want to validate address entry. Alternatively, you can verify address data by the Address Verification Cloud Service. However, note that you require a separate license for the Address Verification Cloud Service. Suppose your organization is doing both. Further suppose that it plans to set up sales territories based on states in the US, so it must import geography data for the US. Also, your organization wants its salespeople to use a list of values to enter the states in their addresses. The state in the address must be validated because invalid entries would cause 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 to set up territories at the Postal Code level, then it should set up validation for state, city, county, Postal Code. The following table lists the tasks you must complete to setup geography. You can access all tasks for this setup from the Setup Geography Data folder in your implementation project. Step Description Task Name Where to Get More Details Import Geography Data Import geography data for the countries where you do business. You can import Oracle-licensed Nokia data for those countries where the data is available. This includes the US, used in our example organization, a growing list of other countries. Manage Geographies Importing Nokia Geography Reference Data Countries Available for Import of Nokia Geography Reference Data topics in this chapter Manage Geographies Setting Up Geography Validation topic in this chapter If the licensed Nokia data is not available for a particular country, then the Import Nokia Data action is disabled. In this case, you must license geography data from another supplier import it from a file. For more information about importing third party geography data, see the Importing Geographies chapter of the Oracle Sales Cloud FileBased Data Import Guide available on docs. oracle.com. Set up Geography Validation For the countries you imported, enable validation down to address level required for your territories specify which address elements require lists of values. When you enable validation on an address element, the application suggests alternatives 29

38 Chapter 6 Step Description Setting Up Geography Data Task Name Where to Get More Details Manage Administrator Profile Values Setting Up Geography Validation topic in this chapter during address entry. Enabling a list of values requires the user to make a selection from a list. Both validation lists of values are enforced in the UIs. Your organization should: Turn on Validation for Address Import Enable list of values for entering states in addresses. Enable validation for states because its territories are defined at the state level. The validation selection you made affects entries made in the application UI only. You must use the task Manage Administrator Profile Values to set the profile option Geography Address Validation Enabled to Yes to validate addresses you import. You must also make sure that the address data you import matches what the geography reference data expects. The Nokia geography reference data requires the states in the US to be spelled out capitalized, for example. This means that California addresses you import must be CALIFORNIA, not California, or CA. Importing Nokia Geography Reference Data Use this procedure to import Nokia geography reference data licensed by Oracle. If the country data you want to import is not available, then the Import Nokia Data action is disabled. Note that the geography data is provided by Nokia is third-party content. As per Oracle policy, this software documentation may provide access to or information about content services from third parties. Oracle its affiliates are not responsible for expressly disclaim all warranties of any kind with respect to the third-party content services. Oracle its affiliates are not responsible for any loss, costs, or damages incurred due to your access to or use of thirdparty content, products, or services. To import Nokia 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 Maintenance work area. 3. Click the task name link in the search results. The Manage Geographies page appears. 30

39 Chapter 6 Setting Up Geography Data 4. Enter either the country name or the two-letter ISO code (for example, US for the United States or AT for Austria). 5. Click Search. The Search Results display the country. 6. Select the country in the search results. 7. Select Import Nokia Data from the Actions menu. 8. Click OK to close the warning message. 9. 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 by selecting 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 now appear in the Structure Defined Hierarchy Defined columns indicating that the import completed successfully. The following figure shows the Manage Geographies page with check marks on the Structure Defined Hierarchy Defined columns indicating that the import has completed successfully. Countries Available for Import of Nokia Geography Reference Data Nokia geography reference data is available for import for the countries listed in the following table. Country Name Country Code Andorra AD Argentina AR Austria AT Belgium BE Brazil BR 31

40 Country Name Country Code Bulgaria BG Canada CA Cayman Isl KY Chile CL Croatia HR Czech Republic CZ Denmark DK Dominican Republic DO Estonia EE Finl FI France FR Germany DE Greece GR Guadeloupe GP Holy See (Vatican City State) VA Hungary HU Icel IS India IN Indonesia ID Irel IR Isle Of Man IM Israel IL Chapter 6 Setting Up Geography Data 32

41 Country Name Country Code Italy IT Jamaica JM Latvia LV Liechtenstein LI Lithuania LT Luxembourg LU Malaysia MY Malta MT Martinique MQ Mexico MX Netherls NL New Zeal NZ Norway NO Peru PE Pol PL Portugal PT Puerto Rico PR Reunion Isl RE Romania RO Russian Federation (Russia) RU San Marino SM Singapore SG Chapter 6 Setting Up Geography Data 33

42 Country Name Country Code Slovakia SK Slovenia SI South Africa ZA Spain ES Swazil SZ Sweden SE Switzerl CH Taiwan TW Turkey TR United Arab Emirates AE United Kingdom GB United States US Uruguay UY Chapter 6 Setting Up Geography Data Importing Third Party Geography Data Using File Based Import You can import Oracle-licensed Nokia data, shipped with the application, for those countries where the data is available. If the licensed Nokia data is not available for a particular country, then the Import Nokia Data action is disabled. In this case, you must license geography data from another supplier import it from a file. Importing Country Structures Using File-Based Import A country structure is a hierarchical grouping of geography types for a country. For example, the geography structure for the United States has the geography type of State at the top, followed by the County, then the City, 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 34

43 Chapter 6 Setting Up Geography Data For more information about importing country structures, see the related links on importing country structures. Importing Geographies Using File-Based Import A geography is any region with a boundary around it, regardless of its size. It might be a state, a country, a city, a county, or a ward. You must create or import geographies before you can associate them with company defined zones addresses. For more information about importing geographies, see the related links on importing geographies. 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 Address Cleansing Geocoding Address Cleansing are additional features that you must set up separately. Geocoding makes it possible to display customers in the vicinity of a mobile address. Address Cleansing makes it possible to validate postal addresses down to the street level. Note that to use address cleansing, you require a separate license for the Address Verification Cloud Service. You must set up Geocoding for those countries where you are using the Around Me functionality in Sales Cloud Mobile. Geocoding finds the latitude 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 as customer contact addresses, in the vicinity. The application integrates the Geocoding feature with elocation, which is a Geocoding service provided by Oracle. For more information about elocation, see: maps_oracle_dot_com_main.html. Enabling Geocoding To enable Geocoding, click the arrow mark under the Geocoding Defined column header make sure that the arrow mark transforms into a tick mark. 35

44 Chapter 6 Setting Up Geography Data 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 updated locations are selected geocoded. To schedule the geocoding feature to run at regular intervals, complete these steps: Navigate to the Scheduled Processes work area. Click Schedule New Process. Click the Name drop-down list search for Populate Location Latitude Longitude Information. Select the value form the search result click OK. Click OK in the Schedule new Process dialog box to confirm the name description of the new process. Process Details page appears. Enter the parameters such as Country Code, Start Date, End Date, Regenerate Geocode Batch Size. Click Process Option to set options such as Language, Territory, Currency, Time Zone. Click OK to the Process Options page. Click Submit. Click Close. Enabling Address Cleansing Address Cleansing makes it possible to validate postal addresses down to the street level. Address cleansing validates, corrects, stardizes address information that you enter in the application. Address cleansing, unlike geography validation, validates both the geography attributes the address line attributes. Note: To use the address cleansing functionality, a separate license for the Address Verification Cloud Service is required. You can specify the real-time address cleansing level for each country by selecting either of the following in the Validation Defined 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 Address Cleansing Address Verification, Defining Address Cleansing. 36

45 Chapter 6 Setting Up Geography Data Setting Up Geography Validation You must set up geography validation for those geography elements that you plan to use in your sales territories. Setting up validation also helps users fill in missing address information, validate addresses during entry. For example, you can have users select states or other address elements from lists to ensure accuracy during entry, you can have the application fill in missing values. For example, when the user enters a Postal Code, the application can retrieve the city state. Our example organization wants its salespeople to use a list of values to enter the states in their addresses it plans to set up territories at the state level. For these reasons, validation must be set up at the state level. Define Geography Validation Perform 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 the Setup 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. 5. In the Address Style region, ensure that the No Styles Format address style is selected. You define validation for the No 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 Address Formats task. 6. Select Enable List of Values in the Geography Mapping Validation region to display the geography type as list of values during address entry in the classic 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 wants to 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 Validation for state, city, county, Postal Code. Note: If you do not select the validation for an address element, the application still suggests values to the user during address entry in the classic simplified UIs, but it does not validate the address element. 37

46 Chapter 6 Setting Up Geography Data 8. Select the values from the Geography Validation Level for Country drop-down list to specify whether you want to permit the application to save addresses that are not considered valid. The following are the available values in the Geography Validation Level for Country drop-down list: No validation: The default value. Select to save incomplete or incorrect addresses verify the address data later by the Address Verification Cloud Service. Error: Select to verify address data against the master geography reference data. This value permits only valid addresses to be saved. Our example organization wants to save all addresses including incomplete invalid addresses, so it keeps the No validation which is the default value. Our example organization wants to save all addresses including incomplete invalid addresses, so it keeps the No validation which is the default value. 38

47 Chapter 6 Setting Up Geography Data The following figure shows the Manage Geography Validation page when the task is completed. 9. Click Save Close. 39

48 Chapter 6 Setting Up Geography Data Turning on Validation for Address Import By default, the validation you specified is enforced for creating addresses in the UI only. You must set the profile option Geography Address Validation Enabled to Yes for the validation to be enforced during import. Follow these steps to set the profile option: 1. Open the Manage Administrator Profile Values task from the implementation project or by searching for it in the Setup 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 Validation Enabled. 3. Click Search. 4. With the profile option selected in the search results, select Yes from the Profile Value list. 5. Click Save Close. 40

49 Chapter 7 7 Importing Accounts Contacts Importing Accounts Contacts Account Contact Import You import accounts contacts in separate files, first the accounts then the contacts. Read the About Importing Accounts Contacts topic perform the steps outlined in the following table to complete account contact import. You can open the different import tasks directly from the Import Accounts Contacts folder in the implementation project. Alternatively, you can search for the tasks by name from the Setup Maintenance work area. Step Description Task Name Where to Get More Details Register the Source System of Your Data Register the application that is the source of your import data. This one-time setup creates the code that you enter along with the different reference IDs in all of your import files. Manage Trading Community Source Systems See the Registering the Source System of Your Customer Data topic in this chapter. Schedule Export Processes See the Exporting Account Owner Party IDs topic in this chapter. Oracle permits you to import data from multiple systems, so the reference IDs alone don't guarantee uniqueness. Export Party ID for the Users you have Created (AccountOwnerID) Export Party ID for the users you have created. You must use the Party IDs (AccountOwnerID) to identify the resource you want to be the account owner for each account you import. Account owners see the account in the list of My Accounts are automatically members of the account team with privileges to add others. Specify the Industry Classification for Accounts Manage Classification If you plan to import industry Categories classification codes you do not want to use Manage Administrator Profile the codes in the default Values CUSTOMER_CATEGORY, then you must set the system profile option MOT_INDUSTRY_CLASS_CATEGORY to your category type. See the Specifying the Industry Classification for Accounts topic in this chapter. You can use any one of the following industry classification categories which are supplied by Oracle with your application: 1972 SIC 1977 SIC 41

50 Chapter 7 Step Description Importing Accounts Contacts Task Name Where to Get More Details Manage File Import Mappings. See the Downloading Templates for Importing Accounts Contacts topic in this chapter. This task is done in your import file. See the Understing the Account Import Template topic in this chapter SIC CUSTOMER_CATEGORY NACE NAF NAICS_1997 NAICS_2002 You can review the available codes for each of these categories using the Manage Classification Categories task. Download a Template for Importing Your Data In the Manage File Import Mappings work area, search for Account Create Update Predefined Mapping download the template from this mapping. The steps to download the template are the same as those you used for downloading the templates for importing users the sales catalog product groups. Underst the Account Import Template Review the template the values each column in your file requires for import. For example, the address data must match the geography reference data you imported earlier. The Nokia geography data requires you to spell out in capital letters both US cities states. Populate the template with your data save it as a.csv file. Add Additional Columns for Importing Additional Account Contact Attributes as Required Optionally, add additional columns to the import file. This task is done in your import file. See the Researching Additional Account Contact Attributes for Import topic in this chapter. If required, edit the seeded mapping7 If you added columns to your file, then you must copy the seeded mapping edit the copy to map them. Manage File Import Mappings See the Creating a New Mapping for a Changed Import Template topic in this chapter. Create an Import Activity to Import the Account Data Import the file by creating an import activity. Manage File Import Activities See the Importing the Accounts Contacts Files topic in this chapter. Use these Same Steps to Import Contacts Import contacts using the same steps. This time you should use the template you download from the Contact Create Update Predefined Mapping. Manage File Import Mappings Manage File Import Activities See the Understing the Contact Import Template topic in this chapter. 42

51 Chapter 7 Step Description Importing Accounts Contacts Task Name Where to Get More Details About Importing Accounts Contacts Although you can create a few test accounts contacts in the user interface, you may want to import some of your existing customer data to test the customer data management features. About the Import Process To import your account contact data, you must complete the following steps for each object: Download a template. Populate the template with your data. Add any additional columns you may need. This requires some research on your part. 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 add the additional columns to the mapping copy. 5. Import the file. Note: While importing your account contact data, using a template is not required. However, using one saves your time. Not only does the template include many of the common attributes for import, but it comes with its own predefined mapping. If you do not use the template, then you must map each attribute in your file to the corresponding attribute in the application yourself. Importing your account contact data is complex because customer data such as addresses contact points are stored in different objects in the application. This means that, in addition to the data itself, you are adding reference IDs into your file so the application can relate the data you import. For example, to import accounts their contacts, you first import the accounts then use their reference IDs to import their contacts. The reference information you add to each object in the file also permits you to update the information later, if required. Information You Are Importing for Accounts In Oracle Applications Cloud, you use accounts to import basic information about the companies organizations important to your business. This information appears in the Account Profile page in the UI. Organization name basic profile information such as the CEO name year the organization was established Industry classification Address Phone Fax URL There are two types of accounts: Customer 43

52 Use this type when importing accounts you have sold to in the past. Chapter 7 Importing Accounts Contacts 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 Contacts For contacts, you are importing the basic information about the contact which appears on the Edit Contact page. This includes the name, address, phone, other contact address information. About Importing Addresses for Accounts Contacts Oracle Applications Cloud stores addresses other information you import as separate objects. When you import an address, for example, the application creates a location containing the address information, a site, which provides the link between the location the account or contact. If you are importing a contact at an existing account address, you can: Import the address once with the account share that address with the contact. This is the equivalent of selecting the Use account address option when creating the contact in the UI. To do this, you import the address with the account information reference the address in the contact import file using the location ID you entered in the account import file. You can reference the account address in your contact import file by including the location ID you imported for the account. 44

53 Chapter 7 Importing Accounts Contacts You import the same address once for the account, a second time for the contact. Doing so creates a duplicate address (two locations) requires you to update two addresses in the future if there are changes, but does not otherwise affect the performance of your application. You reference the objects such as the organization the location using reference IDs you include in your import files. The following figure explains how you reference the account 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 this ID in the AddressLocationOrigSystemReference column. The site ID (Site1) The site represents the link between the organization the location. You can have multiple 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 account import file (Org.1) The contact (Contact1) The ID of the organization's location.(location1). You enter the value you imported for accounts in the AddressLocationOrigSystemReference column. 45

54 Chapter 7 Importing Accounts Contacts The site (Site2) This ID represents the link between the contact the location. You can have multiple locations for a contact. Registering the Source System of Your Customer Data Use this procedure to register the source of the customer data you are importing by creating a source system. You use the code 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 the implementation project. Alternatively, you can search for the task by name in the Setup 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. In the Code field, enter the code you will use in your import files. For example, enter CDMSS. Enter a name. For example, enter Customer Data Source System. Make sure that Spoke is selected in the Type list. Select Enable for Trading Community Members. Click Save Close. Exporting Account Owner Party IDs This 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 identify account 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 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. 46

55 The Create Export Process Definition: Configure Export Objects page appears. 5. From the Actions menu, select Create. Chapter 7 Importing Accounts Contacts The Manage Export Objects window appears. 6. Scroll down to Party, select it, 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 after you 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 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 must format the column to display as a number with zero decimal places. Specifying the Industry Classification for Accounts Use the following procedure to specify which industry classification category you want to use for accounts. The classifications for the category you select appear in the list of values for the Industry field in the Account user interface. By default, the profile is 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 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_CATEGORY 3. 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_

56 NAICS_2002 Chapter 7 Importing Accounts Contacts 5. Click Save Close. Downloading Templates for Importing Accounts Contacts This topic describes how you can download two templates provided by Oracle that you can use to import basic information about accounts 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 open the Manage File Import Mappings task from the implementation project. Alternatively, setup master data management application administrator users can search for the task by name in the Setup 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. 5. Select the appropriate mapping. For accounts, click the Account Create Update predefined Mapping name link. The Edit Import Mapping page appears. 6. Click Download Template. 7. Save the template to your desktop. Understing the Account Import Template This topic provides an overview of a data file created from the Account Create Update Predefined Mapping template provided by Oracle for importing accounts. Account Create Update Predefined Mapping Details You can use the Account Create Update Predefined Mapping template you downloaded to import basic information about the organizations you do business with. Account Template Structure The template file includes a header row with the names of the attributes you map. The columns are arranged in the same order 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 uses to uniquely identify the data you import. These attributes (shaded in gray) are the following: Original System (OS) 48

57 Chapter 7 Importing Accounts Contacts The first column in the template, AccountOrigSystem, identifies the source of your import data. For each row in your file, you enter the code you created when you registered the source of your import using the Manage Trading Community Source Systems task. This value is the same for each row in your file unless you are importing your data from 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 can be 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 of the customer model. For example, when you import an address, the address creates a location a site. You can have many addresses, locations, sites for each customer. You must supply unique IDs for all of these attributes keep your import file on h, in case you decide to update the account information later. Account Import Template Attributes Suppose you are trying to import accounts contacts for a fictitious company, Vision Corp. The following table explains the account import template. It lists the columns in the account import template explains what values you can import. Column Description Sample Value Value required for the Vision Corp. example? AccountOrigSystem Enter the code you created when you registered the source of your import using the Manage Trading Community Source Systems task. This value is same for each row in your file. VISION No If you leave this column blank, then the application uses the default value CSV generates a unique ID for the OrigSystemReference. AccountOrigSystemReference Enter a unique identifier generates a unique ID for the Orig system reference for the account, this can be an ID from your source system, or you can generate a unique ID in Excel. Vision_ Account1 Required only when OrigSystem is passed. AccountName Enter the organization name. Pinnacle Technologies Yes. Always required for creating the organization record. DUNSNumber The unique number assigned to an organization by Dun Bradstreet No SIC Required for Vision Corp. because it wants to use Sales Predictor to recommend ClassCategory1 For each record, enter the name of the classification category you are using in your application 49

58 Chapter 7 Column Description Importing Accounts Contacts Sample Value to identify the industry for your accounts. Value required for the Vision Corp. example? products generate leads by industry. This value must be the same for all records. You can enter one of the following classification categories: 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 must match the classification category you specify in the profile option MOT_INDUSTRY_CLASS_CATEGORY, using the Manage Administrator Profile Values task from the Setup Maintenance work area. This profile option determines which list of classifications appears in the Industry field for accounts. ClassCategory2 Enter the name of the second classification category you are using in your application to identify the industry for your accounts. ClassCode1 You must enter one of the classification codes for the classification category you specified. You can obtain a list of the codes using the same Manage Classification Categories, Setup Maintenance task. ClassCode2 Enter the second classification code for the classification category you specified. AccountOwnerId Party ID of the resource you want to list as the Account No 2752 Required if you specified a classification category for the record. No Yes. 50

59 Chapter 7 Column Description Importing Accounts Contacts Sample Value Owner. You must obtain this ID from Oracle Applications Cloud. Value required for the Vision Corp. example? If you leave this field blank, then ownership is assigned to the user who is doing the import. Being an account owner means that you: See the account in the list of My Accounts Are automatically assigned as a member of the Account Team with privileges to add others. Account owners cannot be assigned or reassigned by sales territories. AccountType Specifies if the account you are importing is a customer or a prospect. ZCA_CUSTOMER Yes. Vision Corp. is importing only accounts of type customer, so the values is always ZCA_CUSTOMER. Valid values are: ZCA_CUSTOMER ZCA_PROSPECT If you do not enter a value, the application automatically supplies the value of ZCA_PROSPECT. You can change this default by setting the account profile Account Type Default (ZCA_ DEFAULT_ ACCOUNT_TYPE) to Customer. Address1 Enter the first line of the address th Ave No. Address2 Enter the second line of the address, if any. Suite 400 No. Address3 Enter the third line of the address, if any. Office 4B020 No. City Enter the city in the format expected by the geography reference data you imported. IRVINE No. CALIFORNIA Required for this use case. The Nokia data for the United States expects the city names to be spelled out all in capitals. State Enter the state in the format expected by the geography reference data you imported. The Vision Corp. sales territories described in this guide are set up based on state. If a state is 51

60 Chapter 7 Column Description Importing Accounts Contacts Sample Value The Nokia data for the United States expects the states to be spelled out all in capitals. County Enter the county in the format expected by the geography reference data you imported. Value required for the Vision Corp. example? missing in your data, then the record is assigned to the first territory up the territory hierarchy that does not specify a state. Orange No. The Nokia data for the United States expects the city names to be spelled out all in capitals. Province Enter the Province in the format expected by the geography reference data you imported. No. The Nokia data for the United States expects the city names to be spelled out all in capitals. Zip/PostalCode Enter the postal code for the account's address No. CountryCode Enter the two-letter country code for the account address. US Yes. If you are importing addresses in countries other than the US, you may have to add different address columns to the import file, depending on the format of that country's address. You can view the list of countries their country codes using the Manage Geographies, Setup Maintenance task. SiteUseTyp Enter the lookup code that represents the purpose for the address association, a sell-to address or a bill-to address. SELL_TO N. AddressLocationOrigSystemReference Enter a unique identifier for the address location, this can be an ID from your source system, or you can generate a unique ID in Excel. Account_ Address_ Location1 Yes. AddressSiteOrigSystemReference Enter a unique identifier for the address site, this can be an ID from your source system, or you can generate a unique ID in Excel. Account_ Address_Site1 Yes. PhoneCountryCode Enter the country code for the phone number. 1 No. PhoneNumber Enter the phone number without any delimiters or spaces. No. 52

61 Chapter 7 Importing Accounts Contacts Column Description Sample Value Value required for the Vision Corp. example? PhoneOrigSystemReference Enter a unique identifier for the phone number. Account_Phone1 Required if you are importing a phone number. http: / / pinnacletechnologiescom No. You can use an existing ID, or you can generate the ID in Excel. URL Enter the URL. UrlOrigSystemReference Enter a unique identifier for the URL. Required if you are importing a URL. You can use an existing ID, or you can generate the ID in Excel. Understing the Contact Import Template This topic provides an overview of a contact import data file prepared from the Contact Create Update Predefined Mapping template provided by Oracle. Contact Create Update Predefined Mapping Details Just like the template you used to import accounts, the Contact Create Update Predefined Mapping template includes a header row with columns that map to the attributes in the application. The columns are arranged in the same order as the mapping 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 modify the seeded mapping to create a modified mapping that includes these additional attributes. Contact Import Template In your import file, you must provide the contact's first last names, you must identify the account where the individual is a contact by entering the values you entered in the AccountOrigSystem AccountOrigSystemReference columns of your account 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 the template. Column Description Sample Value Value required for use case? ContactOrigSystem The code you create using the Manage Trading Community Source Systems task. VISION Default value. If you leave this column blank, then the application uses the 53

62 Chapter 7 Column Description Importing Accounts Contacts Sample Value Value required for use case? default value CSV generates a unique ID for the Orig system reference. ContactOrigSystemReference A unique identifier for the record. This can be an existing ID, or you can generate this ID in Excel. Vision_ Contact1 Required only when Orig system is 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 have you have sold to the contact in the past. Enter Prospect (ZCA_ PROSPECT) if you have qualified a contact as a potential customer. ZCA_CUSTOMER Yes. Vision Corp. is importing only contacts of type customer, so the value is always ZCA_CUSTOMER. Address1 The first line of the contact's address. 212 Herrington Boulevard No. Address2 The second line of the contact's address. Suite 10 No. Address3 The third line of the contact's address. Office 2B020 No. City The city in the format expected by the geography reference data you imported. FOSTER CITY No. CALIFORNIA No. OwnerId The Nokia data for the United States expects the city names to be spelled out all in capitals. State The state in the same format as that expected by the geography reference data you imported. The Nokia data for the United States expects the states to be spelled out all in capitals. County Enter the county in the format expected by the geography reference data you imported. 54

63 Chapter 7 Column Description Importing Accounts Contacts Sample Value Value required for use case? The Nokia data for the United States expects the city names to be spelled out all in capitals. Province Enter the province in the format expected by the geography reference data you imported. The Nokia data for the United States expects the city names to be spelled out all in capitals. Zip/PostalCode The postal code of the contact's address No. Country The country code of the contact's country. US No. Vision_ Contact_ Address1 Required if you are importing address information. AddressLocationOrigSystemReference A unique identifier for the location that is created automatically whenever you import an address. To link the contact to the address you imported for the organization, then you copy the ID you entered in the organization AddressLocationOrigSystemReference field. You can use an existing ID, or you can generate the ID in Excel. AddressSiteOrigSystemReference A unique identifier for the site that is created automatically whenever you import an address. Required if you are importing an address. You can use an existing ID, or you can generate the ID in Excel. WorkPhoneCountryCode The country code. 1 No. WorkPhoneNumber The phone number without any delimiters or spaces No. WorkPhoneOrigSystemReference A unique identifier for the phone number. Vision_ Contact1_ Phone1 Required if you are importing a phone number. You can use an existing ID, or you can generate the ID in Excel. MobileCountryCode The country code. 1 No MobileNumber The phone number without any delimiters or spaces No 55

64 Chapter 7 Importing Accounts Contacts Column Description Sample Value Value required for use case? MobileOrigSystemReference A unique identifier for the phone number. Vision_ Contact1_ Mobile1 Required if you are importing a mobile phone number. You can use an existing ID, or you can generate the ID in Excel. Address Contact . Dennis. Peattie@usvisioncorp. com OrigSystemReference A unique identifier for the . Vision_ Contact1_ 1 Required if you are importing an . You can use an existing ID, or you can generate the ID in Excel. AccountOrigSystem The source system code for the account. VISION Yes. AccountOrigSystemReference The AccountOrigSystemReference for the account associated with the contact. Vision_ Account1 Yes. AccountId Alternate ID that you can export use instead of the AccountOrigSystemReference. Leave blank. You are using AccountOrigSystemReference. You can import additional attributes to a contact by appending attributes to the import file. For more information about appending additional attributes for import, see the topic Appending Additional Attributes for Import in this chapter. Researching Additional Account Contact Attributes for Import This topic explains how you can obtain information about additional attributes to include in your import file for accounts contacts. To import an additional field you see in the UI, for example, you must first obtain the technical field name then find out what values that field expects. Finding the Technical Name of a UI Field To import fields in the UI, you must first find the technical name of the field using Application Composer using the following steps: 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. Exp the Stard Objects for the Common application select the Fields link for the object you want to research. The UI fields their technical names are listed on the Stard tab. You can filter the fields by name. 56

65 Chapter 7 Importing Accounts Contacts The following figure shows the UI fields their technical names listed on the Stard tab. You can filter the fields by name. 3. In addition to the technical name of the field, you must determine the import object the field belongs to. You can find the import object by viewing an existing file import mapping searching the lists of attributes for the most likely objects. a. In the Setup 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 Update Predefined Mapping or the Account Create 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, then click Search. The Search 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 the Edit Import Mapping page when you are done as you do not want to update the mapping. Researching Available Account Contact Attributes You can research additional account contact group attributes for import using the File Based Data Import for Oracle Sales Cloud guide available on Oracle Help Center ( In the File Based Data Imports chapter, see the Account Import Contact Import topics. These topics include links to files containing the information about the available attributes. Related Topics File Based Data Import for Oracle Sales Cloud guide 57

66 Chapter 7 Importing Accounts Contacts Creating a New Mapping for a Changed Import Template This topic describes how you can add an additional contact field you want to import to the seeded Contact Create Update Mapping provided by Oracle how to import your data file with that additional field. This example shows how to update 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 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 Maintenance work area The Manage File Import Mappings page appears. Select Account from the Object list. Select the Seeded option. Click Search. Select the row with the mapping you want to copy. In this example, you select either Account Create Update Predefined Mapping or Contact Create Update Predefined Mapping. 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 ends 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 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 the Attribute. 13. Click Save Close. 58

67 Chapter 7 Importing Accounts Contacts Importing the Accounts Contacts Files You import the CSV files with your account contact data by creating activating an import activity. The process of importing these files is the same. The only difference is the import object mapping you select. You must import the file with 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 Maintenance work area. The Manage Import Activities page appears. 2. Click Create. The Create Import Activity: Enter Import Options page appears. In the Name field, enter a name for your import activity. From the Objects list, select Account. In the Source File Upload From region, select Desktop. Click Browse select your import file. The delimiter for the template import file is Comma separated, the default selection from the Data Type list. Select the Header row included option because the file includes a header. From the Import Mapping list, select a mapping. If you have not made any modifications to the Predefined mapping, select Account Create Update Seeded Mapping or Contact Create 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 Activate page appears. 13. Click Activate. You can monitor the progress of the import activity view completion reports for both successful records errors by selecting the import activity in the Manage File Import Activities page. Troubleshooting Common Import Errors The following table provides troubleshooting tips for common import errors. You can view the errors by downloading the error log from the import activity. Error Description Troubleshooting Tips A matching record of type RESOURCE cannot be found using the value of the attribute RESOURCE_ID that you provided. (MKT ) Cause: No record exists The Party ID you used for the account owner was not valid. Check the Party ID for the resource in the file you exported. 59

68 Error Chapter 7 Importing Accounts Contacts Description Troubleshooting Tips The combination of columns PARTY_ ORIG_SYSTEM PARTY_ ORIG_ SYSTEM_ REFERENCE must be unique. You included duplicate AccountOrigSystemReference or ContactOrigSystemReference ID in the same file. Remove the duplicates. An OSR value used in this batch already exists in one of the parallel batches that is currently being processed. You have more than one process trying to import the same records. Wait for a process to complete before initiating another one. HZ_ IMP_ PARTY_ NAME_ERROR - You must enter a party name. When you are creating a new organization, you must enter the account name in the AccountName column. You are most likely to see this error when you are trying to update existing account or contact information. The original system (OS) original system reference (OSR) information you entered does not resolve to any existing account or contact, so the application assumes you are trying to create a new one. At least one of the required name fields in the HZ_ IMP_ PARTIES_ T table is missing a value. When creating contacts, you must enter the first or last names, or both (FirstName LastName columns). Errors that start with: The process fails to load data into import interface tables. Cause: java. lang. Exception: StagingLoader. load() exception thrown in find VO. You may not have checked the header row included box, so the application treats the header row as a regular data row. Rerun the import with the header row option checked. fails on the ORACLE connection ORACLE_ Caused By: java. sql. SQLSyntaxErrorException: ORA-01722: invalid number Data type in your import file does not match the data type expected in the application. For example, a number cannot include characters such as - or /. Check your import file data. A matching record of type Contact cannot be found using the value of the attribute for Type that you provided. (MKT ) Cause: No record exists with the specified user key value. Action: Verify that the record with the specified user key exists. The error appears when information about the parent object you are importing does not exist for a child object. For example, If you are importing a contact , then you must include the OS OSR for the contact in the same row of your file. Verify that each row contains the account or contact OS OSR pairs. with the specified user key value. Action: Verify that the record with the specified user key exists. If it does not exist, then remove the record from the data file, or update the record with a valid user key. 60

69 Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects 8 Importing Accounts Contacts Using Simplified View Import Objects Importing Data Using Simplified View Import Objects: Overview File-based data import using the simplified view import objects removes the step of complex manual mapping by automatically mapping the source import file data to the target import objects attributes. You can import a wide range of data using file-based data import to create, update, or delete application records. Simplified view import objects are currently available for Accounts Contacts. The simplified view import objects let you import your account contact data into Oracle Applications Cloud using files in.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 about the business object its child objects. If you use automatic import mapping, then the application automatically maps the source file columns to the target objects target attributes for the object being imported. You can avoid manually mapping the attributes. Importing Contacts Using the Contact - Simplified View Import Object: Procedure You can import contact data into Oracle Applications Cloud using the Contact-Simplified View import object. You can use the object 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 includes basic information about the contact. It contains the following child objects: Sales Cloud Address: Includes detailed location information for a contact. If the profile option code ZCA_ACCOUNT_ADDRESS_REQUIRED_ENABLED is set as Yes at site level, then you must provide address information. 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. To import contacts using the Contact-Simplified View import object, you must: 1. Create CSV files with the import data 2. Create an import activity Create CSV files with the import data Oracle Applications Cloud lets you import your contact data in CSV format. You can include contact its child objects' information in CSV files, import them as a ZIP file. You must include a CSV file each for contact its child objects. 61

70 Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects The columns in the CSV files indicate the attributes you can import for each object. To import records, your source file must include the attributes that enable the import process to identify these records. The File Import process uses these column names to automatically map your source data to the attributes in Oracle Applications Cloud. You must underst the following before populating the templates: Identifiers: Identifiers of a record let you reference the record when you want to update the record. Oracle Applications Cloud generates an internal identifier for each new record. However, it is recommended that you provide the origin system origin system reference (OS/OSR) information when you are creating a record. The OS/OSR information is used to update a record, as well as or to associate another record with it. For example, you can use the OS/OSR information of a contact record to update the contact information, or to create a new address for the contact. If you are updating a child resource, then you must provide the identifier information of the child its parent. For example, to update an address of a contact you must provide the identifier information of the contact the address. You can also use a record's internal ID to refer to a record. A record's internal ID, or object key, is typically its row ID in the Oracle Applications Cloud database. The internal ID is a system-generated unique identifier with an attribute name, such as PartyId, RelationshipId, or PartySiteId. However, to determine the internal ID you must 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. For example, an origin system of an contact that you are importing should be enabled for parties in the Manage Trading Community 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 contact, ensure that its parent contact exists in the database. You can import new parent child records in the import activity. You must ensure that the new child record in the import file should refer to the parent using its identifier. For example, you can import a new contact in the contact import CSV file a new address in the address import CSV file. In this case, the address import file should include a reference to the parent 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 ObjectKey The Oracle Applications Cloud record ID for the party (account, contact, household, or legal entity) to which the person profile belongs. Identify the ObjectKey value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Not required. Update Contact Conditionally required. information to identify the existing party. The reference information can be:: ObjectKey (Oracle Sales Cloud record ID). SourceSystem SourceSystemReferenceValue (source system code source system reference 62

71 Required Attributes Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Contact Update Contact SourceSystem The code representing the external source system for the party (account, contact, household, or legal entity) to which the person profile belongs. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Conditionally required. Conditionally required. information to create new contact. The reference information can be: information to identify the existing party. The reference information can be: SourceSystem SourceSystemReference. Party Number SourceSystemReference The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the person profile belongs. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Conditionally required. information to create new contact. The reference information can be: information to identify the existing party. The reference information can be: SourceSystem SourceSystemReference. Party Number The address of the resource that owns manages the sales account to which the contact is associated. Identify the party ID party number of the owner by exporting the Party object using Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. SourceSystem SourceSystemReference provided when importing the contact. Party Number ObjectKey Conditionally required. Owner Address values) provided when importing the organization profile. PartyNumber (public unique identifier for an organization profile). A business key such as person name. SourceSystem SourceSystemReference provided when importing the contact. Party Number ObjectKey Conditionally required. Conditionally required. Specify an owner, by including one of following reference information: By default, the user importing the contact is designated as the owner. Owner Address OwnerPartyId OwnerPartyNumber To specify a different owner, include one of 63

72 Required Attributes Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Contact Update Contact the following reference information: OwnerPartyId The unique identifier of a valid employee resource who owns manages the sales account to which the contact is associated. Identify the party ID party number of the owner by exporting the Party object using Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Conditionally required. Conditionally required. Specify an owner, by including one of following reference information: By default, the user importing the contact is designated as the owner. Owner Address OwnerPartyId OwnerPartyNumber To specify a different owner, include one of the following reference information: OwnerPartyNumber The party number of a valid employee resource who owns manages the sales account to which the contact is associated. Identify the party ID party number of the account owner by exporting the Party object using Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Owner Address OwnerPartyId OwnerPartyNumber Owner Address OwnerPartyId OwnerPartyNumber Conditionally required. Conditionally required. Specify an owner, by including one of following reference information: By default, the user importing the contact is designated as the owner. Owner Address OwnerPartyId OwnerPartyNumber To specify a different owner, include one of the following reference information: Owner Address OwnerPartyId OwnerPartyNumber 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. Create Address Update Address Conditionally required. Conditionally required. contact: contact: The following table lists the attributes required to import Address object. Attribute Description Prerequisite Setup Task PartyId The Oracle Sales Cloud internal ID for the contact to which the address belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. PartyId. PartyId. 64

73 Attribute Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Address PartyNumber The public unique identifier for the contact to which the address belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Conditionally required. Conditionally required. contact: contact: PartySourceSystem The code representing the source system for the contact. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Conditionally required. contact: contact: The country code component of the address. Identify valid country codes using the Setup Maintenance, Manage Territories task. PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesCloudContact SalesCloudContact CSV file. CSV file. Party Number. Party Number. Conditionally required. Conditionally required. contact: contact: Country PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesCloudContact SalesCloudContact CSV file. CSV file. Party Number. Party Number. Conditionally required. PartySourceSystemReferenceValue The reference number or text representing the source system unique ID for the contact. Update Address PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesCloudContact SalesCloudContact CSV file. CSV file. Party Number. Party Number. PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesCloudContact SalesCloudContact CSV file. CSV file. Party Number. Party Number. Required. Required. 65

74 Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Attribute Description Prerequisite Setup Task Create Address LocationId The unique ID for the existing location record in the Oracle Sales Cloud destination table. Identify the LOCATION_ID for an existing location by exporting the Location object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Not required. AddressSourceSystem The code representing the source system for the address. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. The public unique identifier for the address. Identify the address number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. LocationId. SiteNumber. AddressSourceSystem AddressSourceSystemReference Conditionally required. Conditionally required. Provide the source system source system reference values if you intend to import updates to previously imported records from the same system. Provide any of the following reference address: LocationId. SiteNumber. AddressSourceSystem AddressSourceSystemReference SiteNumber. AddressSourceSystem AddressSourceSystemReference. Conditionally required. Conditionally required. Provide the source system source system reference values if you intend to import updates to previously imported records from the same system. Provide any of the following reference address: Site Number Conditionally required. Provide any of the following reference address: AddressSourceSystemReference The reference number or text representing the source system unique ID for the address. Update Address LocationId. SiteNumber. AddressSourceSystem AddressSourceSystemReference SiteNumber. AddressSourceSystem AddressSourceSystemReference. Not required. Conditionally required. Provide any of the following reference address: SiteNumber. AddressSourceSystem AddressSourceSystemReference 66

75 Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Attribute Description Prerequisite Setup Task Create Address Update Address AddressType The type of the address. You can define multiple address types for an address. A list of valid values is defined in the lookup PARTY_ SITE_ USE_ CODE. Review update the codes using the Setup Maintenance work area, Manage Stard Lookups task. Required. Not required. The following table lists the attributes required for importing the Classification object for Contact. Attribute Description Prerequisite Setup Task PartyId The Oracle Sales Cloud internal ID for the contact to which the classification belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Create Classification Update Classification Required. Required. contact: contact: PartyNumber The public unique identifier for the contact to which the classification belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Required. Required. contact: contact: PartySourceSystem The code representing the source system for the contact. Identify the source system or configure source systems either by using the Manage Trading Community Source System task PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesCloudContact SalesCloudContact CSV file. CSV file. Party Number. Party Number. PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesCloudContact SalesCloudContact CSV file. CSV file. Party Number. Party Number. Required. Required. contact: contact: PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the 67

76 Attribute Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Classification PartySourceSystemReferenceValue The reference number or text representing the source system unique ID for the contact. Identify the source system or configure source systems either by using the Manage Trading Community Source System task SourceSystemReference SourceSystemReference: The reference number or text representing the source system unique ID for the classification. SalesCloudContact CSV file. Party Number. Required. contact: contact: SourceSystem: The code representing the source system for the classification. Update Classification Required. SourceSystem SalesCloudContact CSV file. Party Number. PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesCloudContact SalesCloudContact CSV file. CSV file. Party Number. Party Number. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Required. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Required. Provide the source system source system reference values. Conditionally required. Provide the reference classification. Provide the source system source system reference values. ObjectKey. SourceSystem SourceSystemReference. Conditionally required. Provide the reference classification. ObjectKey. SourceSystem SourceSystemReference. ClassificationCode The classification category within classification category. The classification classification code should be valid for the classification category. Review the classifications classification codes, using the Manage Classification Categories, Setup Maintenance task. Required. Required. ClassificationCategory The classification code within classification category. The classification classification code should be valid for the classification category. Review the classifications Required. Required. 68

77 Attribute Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Classification Update Classification Update Relationship classification codes, using the Manage Classification Categories, Setup Maintenance task. The following table lists the attributes for Relationship object. Attribute Description Prerequisite Setup Task Create Relationship RelationshipId The internal ID for the relationship. Identify the relationship ID by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Not required. Conditionally required. relationship: RelationshipSourceSystem A source system code that identifies the original source system of the relationship between the object the subject parties. Identify the source system or configure source systems either by using the Manage Trading Community Source System task Required. Conditionally required. relationship: RelationshipSourceSystemReference A source system reference that identifies the original reference ID of the relationship between the object the subject parties in the source system. Identify the source system or configure source systems either by using the Manage Trading Community Source System task Required. The Oracle Sales Cloud internal ID for the contact to which the classification belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. RelationshipId. RelationshipSourceSystem RelationshipSourceSystemRefere Conditionally required. relationship: SubjectPartyId RelationshipId. RelationshipSourceSystem RelationshipSourceSystemRefere RelationshipId. RelationshipSourceSystem RelationshipSourceSystemRefere Conditionally required. Conditionally required. contact: contact: SubjectPartyId SubjectPartyId SubjectSourceSystem SubjectSourceSystem SubjectSourceSystemReference SubjectSourceSystemReference provided in the provided in the 69

78 Attribute Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Relationship SubjectPartyNumber The public unique identifier for the contact to which the classification belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. The code representing the source system for the contact. Identify the source system or configure source systems either by using the Manage Trading Community Source System task contact: contact: Conditionally required. contact: contact: Conditionally required. contact: contact: Describes the directional connection between the object subject relationship. For example, Employer of verses Employee of. You can view the relationship type relationship type code definition from the Setup Maintenance, Manage Relationship Types task. SubjectPartyId SubjectPartyId SubjectSourceSystem SubjectSourceSystem SubjectSourceSystemReference SubjectSourceSystemReference provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. SubjectPartyNumber SubjectPartyNumber Conditionally required. RelationshipType SubjectPartyId SubjectPartyId SubjectSourceSystem SubjectSourceSystem SubjectSourceSystemReference SubjectSourceSystemReference provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. SubjectPartyNumber SubjectPartyNumber Conditionally required. Identify the source system or configure source systems either by using the Manage Trading Community Source System task SalesAccount CSV file. SubjectPartyNumber Conditionally required. SubjectSourceSystemReference The reference number or text representing the source system unique ID for the contact. Update Relationship Conditionally required. SubjectSourceSystem SalesAccount CSV file. SubjectPartyNumber SubjectPartyId SubjectPartyId SubjectSourceSystem SubjectSourceSystem SubjectSourceSystemReference SubjectSourceSystemReference provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. SubjectPartyNumber SubjectPartyNumber Required. Not required. 70

79 Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Attribute Description Prerequisite Setup Task Create Relationship Update Relationship RelationshipCode Describes the relationship, such as Contact or Membership. You can view the relationship type relationship type code definition from the Setup Maintenance, Manage Relationship Types task. Required. Not required. The following table lists the attributes required to import Team Member object for Contact. Attribute Description Prerequisite Setup Task PartyId The Oracle Sales Cloud internal ID for the contact to which the classification belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Add Team Member Update Team Member Conditionally required. Conditionally required. contact: contact: PartyNumber The public unique identifier for the contact to which the classification belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Conditionally required. Conditionally required. contact: contact: PartySourceSystem The code representing the source system for the contact. Identify the source system or configure source systems either by using the Manage Trading Community Source System task PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesCloudContact SalesAccount CSV file. CSV file. Party Number. Party Number. PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Conditionally required. Conditionally required. contact: contact: PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. 71

80 Attribute Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Add Team Member PartySourceSystemReferenceValue The reference number or text representing the source system unique ID for the contact. Identify the source system or configure source systems either by using the Manage Trading Community Source System task ResourcePartyNumber The public unique identifier for the sales team member. Party Number. Conditionally required. contact: contact: The Oracle Sales Cloud internal ID for sales team member. Update Team Member Conditionally required. ResourceId Party Number. PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Identify the resource ID resource number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Not Required. Identify the resource ID resource number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Required. Conditionally required. resource team member: ResourceId ResourcePartyNumber Conditionally required. resource team member: ResourceId ResourcePartyNumber Create Import Activity You use the Manage File Import Activities task to create import activities. It consists of a step by step guided process to assist you with creating an import activity for a given object Log in as a setup user navigate to the Setup Maintenance work area. Search for select the Manage File Import Activities task. On the Manage File Import Activities page, click the Create icon. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, select the Contact-Simplified View object from the Object list. 5. Select ZIP file from the File Type list, check the Desktop option, browse upload the required ZIP file. 6. To add attachments, under Attachments section, browse upload your file. The attachment must be in ZIP format. Note: Ensure that you have the following columns the required values in the SalesCloudContact.csv file: 72

81 Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects 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. Click Next. In the Create Import Activity: Create Schedule page, select an appropriate scheduling option from the Schedule list. Click Next. On the Create Import Activity: Review Activate page, click Activate to activate the import activity immediately, or click Save Close if you want to use the import activity later. Importing Accounts using the Account - Simplified View Import Object: Procedure You can import account data into Oracle Applications Cloud using the Account-Simplified View import object. You can use the 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 that includes 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 code ZCA_ACCOUNT_ADDRESS_REQUIRED_ENABLED is set as Yes at site level, then you must provide address information. 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 as contacts, households, so on. Sales Cloud Team Member: Includes the team member information of an account. Sales Cloud Attachment: Includes the attachment information of an account. To import accounts using the Account-Simplified View import object, you must: 1. Create CSV files with the import data 2. Create an import activity Create CSV files with the import data Oracle Applications Cloud lets you import account data in CSV format. You can include account its child objects' information in CSV files, import them as a ZIP file. You must include a CSV file each for account its child objects. The columns in the CSV files indicate the attributes you can import for each object. To import records, your source file must include the attributes that enable the import process to identify these records. The File Import process uses these column names to automatically map your source data to the attributes in Oracle Applications Cloud. 73

82 Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects You must underst the following before populating the templates: Identifiers: Identifiers of a record let you reference the record when you want to update the record. Oracle Sales Cloud generates an internal identifier for each new record. However, it is recommended that you provide the origin system origin system reference (OS/OSR) information when you are creating a record. The OS/OSR information is used to update a record, as well as or to associate another record with it. For example, you can use the OS/OSR information of an account record to update the account information, or to create a new address for the account. If you are updating a child resource, then you must provide the identifier information of the child its parent. For example, to update an address of an account you must provide the identifier information of the account the address. You can also use a record's internal ID to refer to a record. A record's internal ID, or object key, is typically its row ID in the Oracle Applications Cloud database. The internal ID is a system-generated unique identifier with an attribute name, such as PartyId, RelationshipId, or PartySiteId. However, to determine the internal ID you must export the 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. For example, an origin system of an account that you are importing should be enabled for parties in the Manage Trading Community 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 import new parent child records in the import activity. You must ensure that the new child record in the import file should refer to the parent using its identifier. For example, you can import a new account in the account import CSV file a new address in the address import CSV file. In this case, the address import file should include a reference to the parent record in the account 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 attributes required to import the Account object. Required Attributes Description Prerequisite Setup Task Create Sales Account SourceSystem The code representing the source system for the sales account. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Conditionally required Provide the source system source system reference values if you intend to import updates to previously imported records from the same system. Update Sales Account Conditionally required information to identify the existing party. The reference information can be: SourceSystemReference The reference number or text representing the source system unique ID for the party (account Identify the source system or configure source systems either by using the Manage Trading Community Conditionally required Provide the source system source system reference values SourceSystem SourceSystemReference provided when importing the sales account. Party Number Conditionally required information to identify 74

83 Required Attributes Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Description Prerequisite Setup Task Create Sales Account Update Sales Account or contact) to which the sales profile belongs. Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. if you intend to import updates to previously imported records from the same system. the existing party. The reference information can be: Owner Address The address of the resource that owns manages the sales account. Identify the party ID party number of the account owner by exporting the Party object using Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Conditionally required Conditionally required Specify an account owner, by including one of following reference information: By default, the user importing the account is designated as the account owner. Address of the account owner Party ID of the account owner in the OwnerPartyId column. Party Number of the account owner in the OwnerPartyNumber column. To specify a different account owner, include one of the following reference information: OwnerPartyId The unique party ID of the resource assigned to manage the sales profile. Identify the party ID party number of the account owner by exporting the Party object using Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. SourceSystem SourceSystemReference provided when importing the sales account. Party Number Address of the account owner Party ID of the account owner in the OwnerPartyId column. Party Number of the account owner in the OwnerPartyNumber column. Conditionally required Conditionally required Specify an account owner, by including one of following reference information: By default, the user importing the account is designated as the account owner. Address of the account owner Party ID of the account owner in the OwnerPartyId column. Party Number of the account owner in the OwnerPartyNumber column. To specify a different account owner, include one of the following reference information: Address of the account owner Party ID of the account owner in the OwnerPartyId column. Party Number of the account owner in the 75

84 Required Attributes Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Sales Account Update Sales Account OwnerPartyNumber column. OwnerPartyNumber The unique party number of the resource assigned to manage the sales profile. Identify the party ID party number of the account owner by exporting the Party object using Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Conditionally required Specify an account owner, by including one of following reference information: Address of the account owner Party ID of the account owner in the OwnerPartyId column. Party Number of the account owner in the OwnerPartyNumber column. Conditionally required By default, the user importing the account is designated as the account owner. To specify a different account owner, include one of the following reference information: Address of the account owner Party ID of the account owner in the OwnerPartyId column. Party Number of the account owner in the OwnerPartyNumber column. The following table lists the attributes required for importing the Address object for Accounts. Attribute Description Prerequisite Setup Task PartyId The Oracle Sales Cloud internal ID for the account to which the address belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Create Address Update Address Required Required account: account: PartyNumber The public unique identifier for the account to which the address belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Required Required account: account: PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the 76

85 Attribute Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Address PartySourceSystem The code representing the source system for the account. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. The country code component of the address. Identify valid country codes using the Setup Maintenance, Manage Territories task. AddressSourceSystem The code representing the source system for the address. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. account: account: Identify the source system or configure source systems either PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Required Required account: account: PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Required Required Conditionally required Conditionally required Provide the source system source system reference values if you intend to import updates to previously imported records from the same system. Provide any of the following reference address: AddressSourceSystemReference The reference number or text representing the SalesAccount CSV file. Party Number. Required Country Update Address Required PartySourceSystemReferenceValue The reference number or text representing the source system unique ID for the account. SalesAccount CSV file. Party Number. Site Number. AddressSourceSystem AddressSourceSystemReference Site Number. AddressSourceSystem AddressSourceSystemReference. Conditionally required Conditionally required 77

86 Attribute Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Description Prerequisite Setup Task Create Address Update Address source system unique ID for the address. by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Provide the source system source system reference values if you intend to import updates to previously imported records from the same system. Provide any of the following reference address: Site Number The public unique identifier for the address. Identify the address number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Site Number. AddressSourceSystem AddressSourceSystemReference. Not required Conditionally required Provide any of the following reference address: AddressType The type of the address. You can define multiple address types for an address. A list of valid values is defined in the lookup PARTY_ SITE_ USE_ CODE. Review update the codes using the Setup Maintenance work area, Manage Stard Lookups task. Site Number. AddressSourceSystem AddressSourceSystemReference Required Site Number. AddressSourceSystem AddressSourceSystemReference Not Required The following table lists the attributes required while importing Classification object for the Account. Attribute Description Prerequisite Setup Task PartyId The Oracle Sales Cloud internal ID for the account to which the classification belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Create Classification Update Classification Required Required account: account: PartyNumber The public unique identifier for the account Identify the party ID party number value PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Required Required 78

87 Attribute Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Description Prerequisite Setup Task to which the classification belongs. by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Create Classification Update Classification account: account: PartySourceSystem The code representing the source system for the sales account. Identify the source system or configure source systems either by using the Manage Trading Community Source System task Required Required account: account: PartySourceSystemReferenceValue The reference number or text representing the source system unique ID for the account. Identify the source system or configure source systems either by using the Manage Trading Community Source System task Required account: account: SourceSystemReference PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Required SourceSystem PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. SourceSystem: The code representing the source system for the classification. Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Conditionally required Required Provide the source system source system reference values if you intend to import updates to previously imported records from the same system. Provide the reference classification. SourceSystemReference: The reference number or text representing the Identify the source system or configure source systems either Conditionally required Required 79

88 Attribute Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Description Prerequisite Setup Task Create Classification Update Classification source system unique ID for the classification. by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Sales Cloud using the Source System Reference import object. Provide the source system source system reference values if you intend to import updates to previously imported records from the same system. Provide the reference classification. ClassificationCode The classification category within classification category. The classification classification code should be valid for the classification category. Review the classifications classification codes, using the Manage Classification Categories, Setup Maintenance task. Required Required ClassificationCategory The classification code within classification category. The classification classification code should be valid for the classification category. Review the classifications classification codes, using the Manage Classification Categories, Setup Maintenance task. Required Required The following table lists the attributes required to import the Relationship object for the Account. Attribute Description Prerequisite Setup Task Create Relationship RelationshipId The internal ID for the relationship. Identify the relationship ID by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Conditionally required. RelationshipSourceSystem A source system code that identifies the original source system of the relationship between the object the subject parties. Identify the source system or configure source systems either by using the Manage Trading Community Source System task If the source of your data is a third party or external system, you intend to import updates to previously imported records from the same system, provide the original source system source system reference values. Conditionally required. Update Relationship Required. account: RelationshipId. RelationshipSourceSystem RelationshipSourceSystemRefere Required. If the source of your data is a third party or external system, you intend to import updates to previously imported records from the same system, provide the original source system 80

89 Attribute Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Relationship Update Relationship source system reference values. RelationshipSourceSystemReference A source system reference that identifies the original reference ID of the relationship between the object the subject parties in the source system. Identify the source system or configure source systems either by using the Manage Trading Community Source System task SubjectPartyId Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. The Oracle Sales Cloud internal ID for the account to which the classification belongs. Conditionally required. If the source of your data is a third party or external system, you intend to import updates to previously imported records from the same system, provide the original source system source system reference values. Required Required account: account: SubjectPartyNumber The public unique identifier for the account to which the classification belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. The code representing the source system for the sales account. Identify the source system or configure source systems either by using the Manage Trading Community Source System task SubjectPartyId SubjectPartyId SubjectSourceSystem SubjectSourceSystem SubjectSourceSystemReference SubjectSourceSystemReference provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. SubjectPartyNumber SubjectPartyNumber Required Required account: account: SubjectSourceSystem Required. SubjectPartyId SubjectPartyId SubjectSourceSystem SubjectSourceSystem SubjectSourceSystemReference SubjectSourceSystemReference provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. SubjectPartyNumber SubjectPartyNumber Required Required account: account: SubjectPartyId SubjectPartyId SubjectSourceSystem SubjectSourceSystem SubjectSourceSystemReference SubjectSourceSystemReference provided in the provided in the 81

90 Attribute Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Create Relationship SubjectSourceSystemReference The reference number or text representing the source system unique ID for the account. Identify the source system or configure source systems either by using the Manage Trading Community Source System task SalesAccount CSV file. SubjectPartyNumber Update Relationship SalesAccount CSV file. SubjectPartyNumber Required Required account: account: SubjectPartyId SubjectPartyId SubjectSourceSystem SubjectSourceSystem SubjectSourceSystemReference SubjectSourceSystemReference provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. SubjectPartyNumber SubjectPartyNumber RelationshipType Describes the directional connection between the object subject relationship. For example, Employer of verses Employee of. You can view the relationship type relationship type code definition from the Setup Maintenance, Manage Relationship Types task. Required Not required RelationshipCode Describes the relationship, such as Contact or Membership. You can view the relationship type relationship type code definition from the Setup Maintenance, Manage Relationship Types task. Required Not required The following table lists the attributes required to import the Team Member object for the Account. Attribute Description Prerequisite Setup Task PartyId The Oracle Sales Cloud internal ID for the account to which the classification belongs. Identify the party ID party number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Add Team Member Update Team Member Required Required account: account: PartyNumber The public unique identifier for the account Identify the party ID party number value PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Required Required 82

91 Attribute Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Description Prerequisite Setup Task to which the classification belongs. by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Add Team Member Update Team Member account: account: PartySourceSystem The code representing the source system for the sales account. Identify the source system or configure source systems either by using the Manage Trading Community Source System task Required Required account: account: PartySourceSystemReferenceValue The reference number or text representing the source system unique ID for the account. Identify the source system or configure source systems either by using the Manage Trading Community Source System task Required account: account: ResourcePartyNumber The Oracle Sales Cloud internal ID for sales team member. The public unique identifier for the sales team member. Identify the resource ID resource number value by exporting the Party object using the Setup Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Identify the resource ID resource number value by exporting the Party object using the Setup Maintenance, PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Required ResourceId PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. PartyId. PartyId. PartySourceSystem PartySourceSystem PartySourceSystemReferenceValue PartySourceSystemReferenceVal provided in the provided in the SalesAccount SalesAccount CSV file. CSV file. Party Number. Party Number. Required Required resource team member: resource team member: ResourceId ResourcePartyNumber Required ResourceId ResourcePartyNumber Required 83

92 Attribute Description Chapter 8 Importing Accounts Contacts Using Simplified View Import Objects Prerequisite Setup Task Manage Bulk Data Export, Schedule Export Processes task. Add Team Member Update Team Member resource team member: resource team member: ResourceId ResourcePartyNumber ResourceId ResourcePartyNumber Create Import Activity You use the Manage File Import Activities task to create import activities. It consists of a step by step guided process to assist you with creating an import activity for a given object Log in as a setup user navigate to the Setup Maintenance work area. Search for select the Manage File Import Activities task. On the Manage File Import Activities page, click the Create icon. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, select the Account-Simplified View object from the Object list. 5. Select ZIP file from the File Type list, check the Desktop option, browse upload the required ZIP file. 6. To add attachments, under Attachments section, browse upload your file. The attachment must be in ZIP format. Note: Ensure that you have the following columns the required values in the SalesCloudAccount.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. Click Next. In the Create Import Activity: Create Schedule page, select an appropriate scheduling option from the Schedule list. Click Next. On the Create Import Activity: Review Activate page, click Activate to activate the import activity immediately, or click Save Close if you want to use the import activity later. 84

93 Chapter 9 9 Configuring Profile Options Configuring Profile Options Customer Hub Profile Options Setup: Overview Profile options are a set of preferences that you can use to centrally manage the user interface settings, data access processing, application action. Customer Hub profile options let you view or change the address cleansing configuration, matching configuration, duplicate resolution request options, various thresholds such as auto link, auto merge, batch sizes. You can set these profile option values only at the site level. You can configure profile options using the Manage Customer Hub Profile Options task in the Setup 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, thresholds are selected for each customer. 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 default values. Profile Option Name Profile Option Definition Description Default Value ZCH_ CLNS_ PROC_BT_SIZE Data Cleansing Process Batch Size The transaction batch size for the data cleansing process. Set this value based on available system resources ZCH_ DEDUP_ REQUEST_ TYPE_OPTION Resolution Request Type Default The default request type for the duplicate resolution requests. Merge ZCH_ DI_ PROC_BT_SIZE Duplicate Identification Process Batch Size The transaction batch size for the duplicate identification process. It's used to group records in the batch process each group in a loop as a separate transaction. 100 ZCH_ USER_ MERGE_ REQUESTS User Merge Requests The processing options for merge requests. This option applies only for merge requests submitted from FUSE UI or EUM UI in Enter Merge Request setup task. Unspecified (NULL) ZCH_ ENABLE_ SURVIVORSHIP Survivorship Enabled The option to enable survivorship rules for duplicate resolution. Yes ZCH_ AUTO_ LINK_ THRESHOLD Auto Link Threshold The threshold for auto link. Data stewards review link requests with lower scores. 0 85

94 Chapter 9 Configuring Profile Options Profile Option Name Profile Option Definition Description Default Value ZCH_ AUTO_ MERGE_ THRESHOLD Auto Merge Threshold The threshold for auto merge. Data stewards review merge requests with lower scores. 100 ZCH_ DI_ MERGEREQ_ REC_SIZE Duplicate Set Record Number The maximum number of records in a duplicate set that can be automatically converted to duplicate resolution requests. 10 ZCM_ ACC_ EXACT_ NAME_MATCH Exact Account Name Match This option controls the display of duplicate accounts based on an exact name match when no duplicate accounts were found from data quality configuration. FALSE ZCM_ CON_ EXACT_ NAME_MATCH Exact Contact Name Match This option controls the display of duplicate contacts based on an exact name match when no duplicate contacts were found from data quality configuration. FALSE ZCM_ ACC_ DUP_ NOTIFICATION Duplicate Account Notification This option controls whether the UI that shows notifications for duplicate accounts should be enabled or not. TRUE This option is available only if you have Oracle Fusion Data Quality. ZCM_ CON_ DUP_ NOTIFICATION Duplicate Contact Notification This option controls whether the UI that shows notifications for duplicate contacts should be enabled or not. TRUE This option is available only if you have Oracle Fusion Data Quality. 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 for this profile option: Allow Processing Without Approval: Merge requests are processed immediately without approval by the data steward. Process Subject to Approval: Merge requests are reviewed by the data steward, who can decide to approve or not. Unspecified: Merge requests are processed immediately without data steward approval. This indicates that the Customer Hub is not configured. The option is enabled only if the user has the Submit Trading Community Merge Request 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 merge requests only if the profile option User Merge Requests is set to Process Subject to Approval, else the merge requests returns an error. 86

95 Chapter 9 Configuring Profile Options Auto Link Threshold is set to 0 by default, which means auto link never occurs automatically. Maximum auto merge threshold is 100, which means unless there is a 100 percent match, there is no auto merge. You need to change the threshold based on customer implementation. Managing Customer Hub Profile Options This procedure describes how to set up customer hub profile options. You can configure these profile options by completing the following steps: Navigate to Setup Maintenance work area. Search for go to the Manage Customer Hub Profile Options task. Select the profile option that you want to configure on the Manage Customer Hub Profile Options page. Select the appropriate profile option value, in the Profile Values area of the page. Click Save Close. 87

96 Chapter 9 Configuring Profile Options 88

97 Chapter Configuring Address Verification Configuring Address Verification Address Verification: Setup Overview Address cleansing is a process that corrects, parses, completes verify address data, based on postal requirements. For example, if you enter postal code, city, country, then address cleansing may return a value for state. Likewise, if you enter city, state, country, then address cleansing supplies a postal code value. In addition, you can validate the address data against the customer's master geography data, ensuring that the data entered is consistent with reference data. This address cleansing service is offered real-time, during the creation or edit of account, contact, or household, in batch mode in the CDM work area, in file import, as well as any other service creating address data in the database. Address verification is 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 street name. Note that for address cleansing 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 verification. All the tasks are available in the Setup Maintenance work area. Step Description Task Name Where to Get More Details Manage Server Configurations for Cleansing Enable the EDQ Real-time Batch Basic Cleanse Server configuration by selecting the check box against it. Ensure that the Server Parameter Values (Server Address, Server Port, DaaS Cleansing Server URL) are complete. Manage Server Configurations For more information about managing EDQ server configurations, see Implementing Customer Data Management, Define Data Quality, Enterprise Data Quality Server Configurations: Explained. Configure the Address Verification Cloud Service Subscribe to the Oracle Social Data Insight Cloud Service Oracle Address Verification Cloud Service. Set the Profile Value for thedaas_ PRODUCTION_ MODE profile option to NO to configure Applications Cloud to Data Cloud Integration. Manage Enterprise Data Quality Cleansing Configurations You can use either the predefined cleansing configuration shipped readyto-use, or duplicate edit these configurations to meet your cleansing requirements. You can duplicate an available configuration to modify it according to your geography, address, cleansing requirements. Manage Sales Cloud to Data Cloud Integration Manage Administrator Profile Values Manage Enterprise Data Quality Cleansing Configurations For more information about managing EDQ cleansing configurations, see Implementing Customer Data Management, Define Data Quality, Enterprise Data Quality Cleansing Configurations: Explained. 89

98 Chapter 10 Step Description Configuring Address Verification Task Name Where to Get More Details Note: You must save a duplicated configuration before you edit it. Set Up Address Cleansing Address Verification Enable Address Verification for the countries in which you do business. Manage Geographies, Validation Defined Managing Server Configurations for Cleansing This 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 Maintenance work area, search for the Manage Server Configurations task by name click Go. 2. Select the EDQ Real-time Batch Basic Cleanse Server option. 3. Ensure that the Server Parameter Values (Server Address, Server Port, DaaS Cleansing Server URL) are complete. 4. Click Save Close. For more information about managing EDQ server configurations, see Implementing Customer Data Management, Define Data Quality, Enterprise Data Quality Server Configurations: Explained. Configuring the Address Verification Cloud Service The address verification processes use country-specific postal address data provided in Enterprise Data Quality Data Cloud. 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 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 Assigning a Role Here are the key steps to create a DaaS user 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 b. Navigate to Data Center where the service is located request a trial or purchase a subscription. For more details, see Subscribing to an Oracle Cloud Service Trial, Getting Started with Oracle Cloud, in the Related Links section of this topic. 90

99 Chapter 10 Configuring Address Verification Note: Oracle Social Data Insight Cloud Service Oracle Address Verification Cloud Service offer a combined trial subscription; that is, when you order a trial for one service, you also get the other. Each service must be purchased separately, but they can be part of the same subscription order. For more information on subscriptions, see Understing Subscriptions FAQ -Subscriptions. 2. Activate your account: a. Open the welcome 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-activation from Oracle Cloud. This contains the sign-in credentials, My Services URL, Identity domain information. Tip: You can see the DaaS subscription URL under the My Account Administration Details section of the 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 the REST service endpoint URLs for both Address Verification API, Company Contact Data API. 4. Set up DaaS by creating a user assigning the Data Service Client API AppID role to the new user. a. b. c. d. e. Navigate to My Services Dashboard. Click the Users tab on the My Services Users page. The Add User page appears. Enter your credentials. Exp the Advanced Roles section add the role Data Service Client API AppID. Click Add to assign this role to the user. Configuring Customer Data Management Cloud to Data Cloud Integration After the DaaS user is setup, navigate to Sales Cloud for adding DaaS URL credentials. The following are the steps to configure sales Cloud to Data Cloud Integration: 1. Navigate to Setup Maintenance. 2. Search for 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 on the Trial Details section. Select oracle/wss_username_token_over_ssl_client_policy as Security Policy. Enter the DaaS user name password you created in DaaS setup. 4. Click Save Close. 91

100 Chapter 10 Configuring Address Verification Requesting the Welcome to be Resent Setup steps for this service are sent through a welcome to the customer when the license is purchased. Detailed steps for setting up Address Verification, including how to obtain DaaS Cleansing Server URL, can be found in Using Oracle Address Verification Cloud Service in the Help Center. If the DaaS Cleansing Server URL is missing the customer administrator has already activated the service, then the customer administrator can request resend of the Welcome by going to > My Account (see the following figure). The following figure highlights the Resend Welcome button on the My Accounts page. However, if the customer administrator did not receive a welcome with links to activate the service, then the customer will have to log a service request to have Oracle Support resend the welcome so that the customer administrator can activate the service. Instructions on how to log a service request the Customer Support Identifier associated to the service request are described in the FAQ section of Getting Started with Oracle Cloud in the Help Center. Managing Administrator Profile Values Complete the following steps to manage administrator profile values: Navigate to Setup Maintenance. Search for go to the Manage Administrator Profile Values task. Enter DAAS_PRODUCTION_MODE as the Profile Option Code on the Manage Administrator Profile Values page. Click Search. The specified Profile Option appears as the search result. Make sure that theprofile Level is Site 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. 6. Click Save Close. The integration between Data as a Service is now complete. You find more information about the DaaS Address Verification in the Using Oracle Address Verification Cloud Service guide in 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 Configurations Enterprise Data Quality configuration provides the mapping between the Enterprise Data Quality address cleansing attributes the Customer Data Management Cloud Service address attributes. 92

101 Chapter 10 Configuring Address Verification 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 editing them. Copying a Predefined Enterprise Data Quality Cleansing Configuration To copy or make a duplicate of a predefined Enterprise Data Quality cleansing configuration, complete these steps: Navigate to the Setup Maintenance work area. Search for go to the Manage Enterprise Data Quality Cleansing Configurations Task. Select the Address Cleansing configuration, click Duplicate. Enter a name in the Name field. Click Save. Adapting a Copy of the Predefined Enterprise Data Quality Cleansing Configuration To edit a copy of the predefined Enterprise Data Quality cleansing configuration to your cleansing requirements, complete these steps: Note: You cannot edit a predefined Enterprise Data Quality configuration. You can only make a copy of it edit it by following this procedure. 1. Sign in as a setup user navigate to the Setup Maintenance work area. 2. Search for go to the Manage Enterprise Data Quality Cleansing Configurations task. 3. Select a copy of the Address Cleansing configuration that you created earlier 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 batch matching. 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, then you 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 activate a 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, then map it with the corresponding attributes in the Attributes column to create 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. 93

102 Chapter 10 Configuring Address Verification 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 Close. Mapping Address Cleansing Attributes Customer 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 Management Cloud service. Output Address Attribute: The attribute used to describe the output address to Customer Data Management Cloud service 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 EDQ attribute is used to describe a distinct item of information that relates to a record. For example, a City attribute might describe the city details of a Customer record. Once the mapping is established, the input address is validated verified. You can map the cleansed address described in the EDQ attribute to the corresponding output address attribute. Defining Cleansing Configuration Parameters Cleansing configuration parameters are system-level parameters that control aspects of the data quality cleansing services. An EDQ cleansing configuration includes both real-time batch cleansing configuration parameters. These parameters control real-time batch address cleansing, stardization, validation operations for a subset or all of the address records in the database, or as part of a data import process. The following table describes theses parameters provides the supported parameter values where applicable. Parameter Description Default Country Used to specify the country to cleanse the address, if no identifiable country can be found in an input address. Used to specify the letter case for an output address. Output Casing Minimum Verification Level Used to specify the level of verification to which the input data matches the available reference data during the verification process. Ranges from Verified to Administrative Area Level to Verified to Delivery Point, or Postbox level. Parameter Value Possible Values: Names of different countries Default Value: United States Possible Values: Upper case, Lower case, Mixed case. Default Value: Mixed Possible Values: Between 1 5. Default Value: 3. Note: The higher the value, the more precise is the address. For a description of what each level 94

103 Chapter 10 Parameter Description Configuring Address Verification Parameter Value means, see Section "Notes on Verification Levels". Minimum Verification Score Used to specify the similarity between the input address closest reference data match as a percentage between 0 (no match) 100 (perfect match). Possible Values: Between Default Value: 90 Correct Partially Verified Addresses Determines if you want to correct the addresses that you entered. Possible Values: Yes/No Default Value: No Correct Ambiguous Addresses Determines if you want to correct the address that you entered if it is unclear resolve it to the correct address. Possible Values: Yes/No Default Value: No Processing Mode Use Verify mode to see the verified addresses. The Address Verification usage counter increases when you use the Verify mode. Possible Values: Verify Default Value: Verify Notes on Verification Levels The verification level is used to specify the level of verification to which the input data matches the available reference data during the verification process. It is output as the second character of the Accuracy Code returned by the EDQ Address Verification processor. The 'post-processed' verification level is used (not the 'pre-processed' level); that is, the verification level achieved after EDQ Address Verification applies stardization parsing to the input address. The following table lists the possible verification levels. The maximum verification level that it is possible to reach varies by country. For information on the maximum level in each country, see the Oracle EDQ Portal website at: 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 95

104 Chapter 10 Configuring Address Verification Reviewing Configuration Results The Review Configuration Results option lets you check if the address attributes entered for cleansing in the Edit EDQ Cleansing Configuration page return the expected cleansed address. You can also test the results of one or more of the following 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 process mode as Search to see multiple address results 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 Parkway b. State: CA c. Country: Redwood City 4. Click Find to verify whether the cleansed address record meets your expectations. 96

105 The following figure shows the Review Configurations Results page. Chapter 10 Configuring Address Verification For more information about address cleansing configuration template, see Implementing Customer Data Management, Define Data Quality, Managing Enterprise Data Quality Cleansing Configurations: Procedures. 97

106 Chapter 10 Configuring Address Verification Setting Up Address Cleansing Address Validation This topic describes the procedure for setting up address cleansing address Verification. It also describes how to turn on validation for address import. Defining Address Cleansing Use the following steps to define address cleansing for the countries in which you do business. 1. Navigate to the Setup Maintenance work area. 2. Search for 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, 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 option to cleanse addresses. If the level is set to None, it specifies no real-time address cleansing. 7. Click Save Close. Defining Address Validation Use the following steps to define address verification for the countries in which you do business. 1. Navigate to the Setup Maintenance work area. 2. Search for 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, clicking 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. 98

107 The following figure shows the Manage Geography Validation page. Chapter 10 Configuring Address Verification 6. In the Address Style region, ensure that the No Styles Format address style is selected. You define validation for the No 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. The format of addresses for Accounts Contacts on the Create Edit pages in Simplified UI may not map perfectly to master geography structure. 7. Deselect Enable List of Values option in the Geography Mapping Validation region to avoid Address Verification Cloud Service data conflicts with master reference geography data. By deselecting this option you can avoid any UI level validation against master geographies while adding address. 99