Oracle Sales Cloud Using Customer Data Management. Release 8

Transcription

1 Oracle Sales Cloud Using Customer Data Management Release 8 April 2014

2 Oracle Sales Cloud Using Customer Data Management Part Number E Copyright , Oracle and/or its affiliates. All rights reserved. Authors: Rakesh Chaudhary, Abhishek Sura, Vijay Tiwary, Jacqueline Wood This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and 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 and 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, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and 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, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and 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 and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and 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. For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at Oracle customers have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired.

3 Contents 1 Import Customer Information Using File-Based Import Overview of File-Based Import Importing Consumers Using File-Based Import Importing Contacts Using File-Based Import Importing Country Structures Using File-Based Import Importing Customer Hierarchies Using File-Based Import Importing Customers Using File-Based Import Importing Employee Resources Using File-Based Import Importing Geographies Using File-Based Import Importing Group Customers Using File-Based Import Importing Legal Entities Using File-Based Import Importing Resource Teams Using File-Based Import Import Customer Information Using Data Import Overview of Data Import Enter Import Process Information FAQs for Enter Import Process Information FAQs for View Error Reports and Output Files FAQs for Purge Batch Conduct What-If Analysis and Submit FAQs for View Batch Detail and Statistics Enriching Sales Cloud Data Using Oracle Social Data and Insight Cloud Service Enriching Account and Account Contact Data: Explained Importing New Records into Oracle Sales Cloud from Oracle Social Data and Insight Cloud Service: Explained Manage Customer Data Quality Overview of Data Quality Management Cleanse Customer Information Enter Data Cleansing Batch Information and Submit FAQs for Cleanse Customer Information Identify Duplicate Customer Information View Nonduplicate Mapping FAQs for Assign Duplicate Identification Batch Enter Duplicate Resolution Request Resolve Duplicate Customer Information

4 5 Analyze Customer Data Quality Analyze Data Quality FAQs for Analyze Data Quality Manage Party Information Manage Party Information Manage Hierarchy Information Manage Hierarchy Information FAQs for Manage Hierarchy Information Manage Enterprise Resource Information Manage Resource Information FAQs for Manage Resource Information Manage Resource Organization Information FAQs for Manage Resource Organization Information Manage Resource Team Information FAQs for Manage Resource Team Information View Audit Histories Audit History: Explained Audit Event Types: Explained

5 Preface This Preface introduces the guides, online help, and other information sources available to help you more effectively use Oracle Fusion Applications. Oracle Fusion Applications Help You can access Oracle Fusion Applications Help for the current page, section, activity, or task by clicking the help icon. The following figure depicts the help icon. Note If you don't see any help icons on your page, then click the Show Help icon button in the global area. However, not all pages have help icons. You can add custom help files to replace or supplement the provided content. Each release update includes new help content to ensure you have access to the latest information. Patching does not affect your custom help content. Oracle Fusion Applications Guides Oracle Fusion Applications guides are a structured collection of the help topics, examples, and FAQs from the help system packaged for easy download and offline reference, and sequenced to facilitate learning. To access the guides, go to any page in Oracle Fusion Applications Help and select Documentation Library from the Navigator menu. Guides are designed for specific audiences: User Guides address the tasks in one or more business processes. They are intended for users who perform these tasks, and managers looking for an overview of the business processes. They are organized by the business process activities and tasks. Implementation Guides address the tasks required to set up an offering, or selected features of an offering. They are intended for implementors. They are organized to follow the task list sequence of the offerings, as displayed within the Setup and Maintenance work area provided by Oracle Fusion Functional Setup Manager. Concept Guides explain the key concepts and decisions for a specific area of functionality. They are intended for decision makers, such as chief

6 financial officers, financial analysts, and implementation consultants. They are organized by the logical flow of features and functions. Security Reference Manuals describe the predefined data that is included in the security reference implementation for one offering. They are intended for implementors, security administrators, and auditors. They are organized by role. These guides cover specific business processes and offerings. Common areas are addressed in the guides listed in the following table. Guide Intended Audience Purpose Common User Guide All users Explains tasks performed by most users. Common Implementation Guide Implementors Explains tasks within the Define Common Applications Configuration task list, which is included in all offerings. Functional Setup Manager User Guide Technical Guides Implementors System administrators, application developers, and technical members of implementation teams Explains how to use Oracle Fusion Functional Setup Manager to plan, manage, and track your implementation projects, migrate setup data, and validate implementations. Explain how to install, patch, administer, and customize Oracle Fusion Applications. Note Limited content applicable to Oracle Cloud implementations. For other guides, go to Oracle Technology Network at technetwork/indexes/documentation. Other Information Sources My Oracle Support Oracle customers have access to electronic support through My Oracle Support. For information, visit ctx=acc&id=info or visit ctx=acc&id=trs if you are hearing impaired. Use the My Oracle Support Knowledge Browser to find documents for a product area. You can search for release-specific information, such as patches, alerts, white papers, and troubleshooting tips. Other services include health checks, guided lifecycle advice, and direct contact with industry experts through the My Oracle Support Community.

7 Oracle Enterprise Repository for Oracle Fusion Applications Oracle Enterprise Repository for Oracle Fusion Applications provides details on service-oriented architecture assets to help you manage the lifecycle of your software from planning through implementation, testing, production, and changes. In Oracle Fusion Applications, you can use Oracle Enterprise Repository at for: Technical information about integrating with other applications, including services, operations, composites, events, and integration tables. The classification scheme shows the scenarios in which you use the assets, and includes diagrams, schematics, and links to other technical documentation. Other technical information such as reusable components, policies, architecture diagrams, and topology diagrams. Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at accessibility/index.html. Comments and Suggestions Your comments are important to us. We encourage you to send us feedback about Oracle Fusion Applications Help and guides. Please send your suggestions to You can use Send Feedback to Oracle from the Settings and Actions menu in Oracle Fusion Applications Help.

8

9 1 Import Customer Information Using File- Based Import Overview of File-Based Import File-Based Data Import: How It Works The Define File-Based Data Import group of tasks relies on integration with different Oracle Sales Cloud and architecture components, such as interface tables and application base tables. This topic provides an overview of these components to help you understand the import process and the different import activity statuses. The following figure provides an overview of the major application components used when you import data from a file. These components include Import object Import mapping Import activity File repository Application Composer Interface tables Oracle Sales Cloud base tables Import Customer Information Using File-Based Import 1-1

10 Import Objects, Import Mapping, and Import Activity The import objects you select when you create an import activity are provided by Oracle. They are managed using the Manage File Import Objects task. When you create an import activity, you must specify a mapping of the fields in your file to the attributes of the import object. You can create the mapping while creating an import activity or separately using the Manage File Import Mappings task. The mapping is stored and managed as a separate object. File Repository The text or XML data file you upload for import is stored in a file repository so that it is available for import processing when you schedule an import activity. Any attachments you upload are stored in the same repository. Application Composer and Custom Extensions When you create additional attributes for import using Application Composer, these extensions are stored in a separate repository and are available when you create your mapping. Interface Tables The import activity populates the application interface tables with your data. This is an intermediate holding area for your data that permits you to correct any import errors. Oracle Sales Cloud data is not changed at this point. 1-2 Oracle Sales Cloud Using Customer Data Management

11 Oracle Sales Cloud Base Tables The import activity loads your data into Oracle Sales Cloud base tables to complete the import. Import Activity Source File Options: Explained The Import Activity consists of a step by step guided process to assist you with creating an import activity for a given object. This topic describes the source file options defined in the Import Activity that are used by the import process to locate and parse the source file data. Source File Data Enter attribute details pertaining to the source file as follows: Option File Type Data Type, Delimiter, and Header Row Included Import Mapping Description Source file must be either Text or XML. A Text file type can further be defined based on how the data is delimited and if the source file is expected to include a row of headings for each column. Displays a list of predefined mappings for the object selected for this import activity. The selected mapping will be used as the basis for mapping your source file in the next Import Activity step. Source File Location The following outlines the options that are available to you when locating your source file for import. Import Customer Information Using File-Based Import 1-3

12 Option File Selection Description Select from the following file selections: Specific file Enables you to upload a specific source file from a local file system, such as your desktop, a URL address, or from a network path. A file name is required for this option. Most recent file Enables you to schedule repeating import activities without having to select a new file every time. This selection is only available when you select Network from the Upload From options. Upload From You need to copy the new file to the specified network path for repeating import activities. You do not need to enter a file name for this option and can only upload your source file from a network path. The asterisk wildcard is supported for multiple characters. The question mark wildcard is supported for a single character. You can upload the source file from three locations: Desktop URL Network If you select Desktop, a File Name field with an associated Update button is displayed. Click Update and browse to search for and select the file you want to upload. If you select URL, enter the address location as in the following example format: If you select Network, enter the file name path as in the following example format: \ComputerName \SharedFolder\Resource\ Note If you selected the Specific File as your file selection option, then you will have to include the file name for both URL and Network file path locations. 1-4 Oracle Sales Cloud Using Customer Data Management

13 Importing Attachments Using File-Based Data Import This topic describes how to include attachments when you use the Manage File Import Activities task. 1. Make sure the Manage File Import Activities task can attach a file to the business object. You can import attachments only for the following business objects:. Asset Interaction Lead Opportunity Partner Task 2. Add one or more of the following columns to the source file that you are importing. The ATTACHMENT_FILE _NAME header is the only required header. All other headers are optional. The Manage File Import Activities task reserves these header names for their described usage. You must not use them for any other purpose. Column Header ATTACHMENT_FILE _NAME ATTACHMENT_FILE _DESC ATTACHMENT_FILE _TITLE ATTACHMENT_CATEGORY _NAME Description Specify a file name. The ZIP file must include this file name. Describe the file. Enter the file title. If you do not specify a file title, then the Manage File Import Activities task uses the file name as the title. Specify the attachment category. For example, you can categorize attachments for an expense report as a receipt, scanned invoice image, and so on. This categorization allows the user to chose the attachment from a list, such as a list of receipts. For more information, see the link to What's an attachment category? at the end of this topic. 3. In each row, enter the name of the attachment file that the Manage File Import Activities task must attach to the record. Import Customer Information Using File-Based Import 1-5

14 In the following example, you enter file_1.doc as the attachment file for Lead 1. LeadName StatusCD Score ATTACHMENT _FILE _NAME Lead 1 QUALIFIED 7 file_1.doc Lead 2 QUALIFIED 8 file_2.doc Lead 3 QUALIFIED 3 file_3.doc Lead 4 QUALIFIED 7 file_4.doc Note the following: To specify the same attachment file for more than one record, enter the same file name for each record in the ATTACHMENT _FILE _NAME column. For example, you can specify file_1.doc for Lead 1 and for Lead 2. You can specify multiple attachments for leads and tasks. You cannot specify multiple attachments for any other type of business object. For example, you can include only one attachment for an asset, but you can include more than one attachment for a task. To specify more than one attachment for the same record, you add one ATTACHMENT _FILE _NAME column for each attachment. Lead 1 and Lead 3 in the following example each include three attachments, so this example includes three ATTACHMENT _FILE _NAME columns: LeadName StatusCD ATTACHMENT ATTACHMENT ATTACHMENT _FILE _NAME _FILE _NAME _FILE _NAME Lead 1 QUALIFIED file_1.doc file_2.doc file_3.doc Lead 2 QUALIFIED file_4.doc Lead 3 QUALIFIED file_5.doc file_6.doc file_7.doc Lead 4 QUALIFIED If you specify more than one attachment for the same record, and if you add any of the optional attachment columns, then you must repeat all the columns in the same order for each attachment file. 4. Create a ZIP file that includes the files that you must attach. For example, create a file named myfiles.zip that includes the following files: file_1.doc file_2.doc file_3.doc 1-6 Oracle Sales Cloud Using Customer Data Management

15 file_4.doc You can also use a JAR file. You can organize these files in folders and subfolders, at your discretion. 5. Log into your Oracle Sales Cloud application. 6. Navigate to the Setup and Maintenance screen, and then search for the Manage File Import Activities task. 7. In the Search Results list, click Go to Task. 8. In the Overview list, click Create. 9. In the Create Import Activity : Enter Import Options screen, choose an object in the Object field that supports attachments. Examine the step earlier in this procedure to identify the objects that support attachments. 10. In the Attachments section, click Browse, and then locate your ZIP file. Note the following: You can upload only one ZIP file. You cannot add more attachments after you upload the ZIP file. 11. Finish the remaining fields and screens in the Manage File Import Objects task. The Manage File Import Activities task recognizes the reserved column header names, so you do not need to map them in the Create Import Activity: Map Fields screen. For more information about finishing this task, see the Related Links section at the end of this topic. Import Activity Import Options: Explained This topic describes the import options available while creating import activities. Source File Data Transformation The following options are used to identify the formatting of source file data so the data can be correctly interpreted and transformed by the import process: Option Decimal Separator Date Format Time Stamp Format File Encoding Description The format of the fractional portion of numerical values in columns mapped to attributes with a decimal attribute type. The format for values in columns mapped to attributes with a date attribute type. The format for values in columns mapped to attributes with a time stamp attribute type. The overall encoding of the characters within the file. Import Customer Information Using File-Based Import 1-7

16 Interface to Target Import Options Depending on the object you are importing and the application modules you have implemented, you can select one or more of these options. Option Import Mode Description For importing leads and employee resources only, you have the option of specifying if you want to create and update records or update only. If you select update, then any new records will be ignored by the import process. Allowable Error Count For all other import objects, both create and update are available. An error count above the threshold will stop the import process for all records. If the error count is below the threshold, records without errors are imported. In either case, records with errors will be reported in the Error and Exception files. Validation errors include: Missing required values Values that exceed the attribute length Invalid identifiers and lookup codes Duplicates to existing records in the destination tables based on the combination of attributes selected for duplicate validation in the predefined Import Mapping Notification Duplicates found using matching configurations for Customer Data Management objects do not contribute to the error count. The of the intended recipient of import processing notifications. 1-8 Oracle Sales Cloud Using Customer Data Management

17 Customer Data Management Duplicates Using this option, which is available only if you have licensed the data quality functionality, you can select different options for handling duplicates when you are importing customers, consumers, and legal entities either alone or as part of another object. The duplicates are determined using the following matching configurations: Batch Location Basic Duplicate Identification Batch Person Basic Duplicate Identification Batch Organization Basic Duplicate Identification You can select from one of the following: Do Not Import Duplicate Records If the main object of the Import Activity is a consumer, customer, or a legal entity object, rows that are matched to existing records will not be imported. These duplicates records are reported in the Exception and Error reports. If the Customer Data Management objects are components of another object and one or more matches are found, the existing duplicate records are evaluated to determine the most recent record. The most recent record will be associated with the main object being imported. For example, when importing a marketing response object, the consumer object is also a component of the marketing response. If the consumer is matched to an existing record, the consumer in the interface tables is not imported. However, the marketing response object will import and the most recent existing consumer record will be associated to the marketing response. Import Duplicate Records The Customer Data Management objects will be imported even if matched records exist. Import Duplicate Records and Create Resolution Request The Customer Data Management objects will be imported even if matched records exist. In addition, a duplicate resolution request is created and displayed in the Customer Data Management, Duplicate Resolution work area. Import Customer Information Using File-Based Import 1-9

18 Duplicate Look Back Days This option applies only to the Lead import object. Only existing leads created within the period determined by the look back days value are evaluated for duplicates based on the attributes selected for duplicate validation in the predefined import mapping. If a duplicate is found, the lead will not be imported and the duplicate record will be reported on the Exception report. Duplicate leads are included in the calculation of the allowable error count threshold. Import Activity Field Mapping: Explained After entering your import options, the second step of the import activity process is to map fields in the source file to the corresponding target attributes. This topic explains: Map Fields Saving the Import Mapping Constant Values Map Fields The Map Fields section can be subdivided into source file columns and target attribute columns. The source column header value is derived from one of the following: Predefined mapping, if one is selected The source file, if the Header Row Included option is selected in the first step of the Import Activity definition (for Text file type only) Generic values of Column A, Column B, and so on, if the Header Row Included option is not selected (for Text file type only) XML tagging structure (for XML file type only) The following table outlines the source columns: Source Column Column Header Example Value Ignore Description Represents the column header for Text file types and the tagging structure for XML file types. Values are derived from the first source file saved with the predefined mapping. If you did not select a predefined mapping, the example values are taken from the first data row in the source file selected in the first step of the Import Activity definition. Select this option if you do not want to import the source file data in that column. The following table outlines the target columns: Target Column Object Attribute Description The group of import objects that represent the components of the business object being imported. The attribute name that represents the corresponding interface table column for the object Oracle Sales Cloud Using Customer Data Management

19 Saving the Import Mapping The mapping between source file information and target attributes is saved as a reusable mapping when the Import Activity is saved, using the import activity name and date to derive a mapping name. If you selected a predefined mapping, modifications made in the Import Activity to an unlocked mapping will update and save to the predefined mapping. If the predefined mapping is locked, a modified mapping will be saved as a new mapping. To specify a mapping name for new mappings, select the Save As option from the Map Fields Actions menu. Constant Values Constant values provide a way to specify a value for a target attribute that all imported objects will inherit. For example, if a source file does not contain a column for business unit and all of the objects in the file belong to the same business unit, enter a constant value for the object and business unit attribute. File Import Activity Statuses: Explained This topic explains the meaning of the different import activity statuses when you import data from a file using the Manage File Import Activities task. The following table lists and describes the import activity statuses. Status No status displayed for the activity New Scheduled Interface table upload in progress Base table upload in progress Completed Completed with errors Description The new import activity definition is not complete. The import activity definition is complete, but the activity is not yet scheduled to run. The import activity definition is complete and scheduled to run later. The data file is being loaded into the interface tables. The data file is being loaded from the interface tables into the application tables. All records were processed and loaded into the application tables. The import activity found errors in the data file that you must correct. You can view details about the errors by clicking the status link. File-Based Import Monitoring: Explained You can monitor all file import activities that are currently scheduled to run, have completed successfully, or failed with errors. For each import activity, you can view the details pertaining to each underlying process and make necessary updates for any failed records to import again. You can view the list of import activities from the Manage Import Activities page. Select the import activity that you want to monitor by clicking on the hyperlink in the corresponding Status column. The View Import Status results page is displayed which contains the following sections: Import Customer Information Using File-Based Import 1-11

20 Files Processed Import Processes Files Processed The Files Processed section displays a row for each source file that is processed. The import processing details are summarized and displayed for each source file and include the following: File Processing Summary Information Records Read From File Format Errors Load Errors Successfully Loaded Attachments Description The number of records read from the source file. The number of errors found when processing data to insert into the interface tables from the source file, Import Activity constants, and Import Object value default values. View the error details in the Exception and Error files attached to the process. The number of errors found when importing data from the interface tables to the destination application tables. View the error details in the Exception and Error files attached to the process. The number of import objects imported to the application destination tables. If the import object is made up of multiple components, each component is counted as successfully loaded. Consequently the Successfully Loaded count may be larger than the Records Read From File count. View the successful record details in the Log file attached to the process. Once an Import Activity process has completed, processing reports are included in the Attachments column. The Log file includes the records that were successfully imported plus the unique destination application table identifiers for the objects. The Exception file includes the records that were not imported plus a reference to one of the errors for each record that failed. The Error file includes all the errors for each record that failed validation. Import Processes From the Import Processes section, you can view details pertaining to each process involved in importing the objects in the source file. A listing of brief messages provides information on processing steps within each underlying process. Importing Consumers Using File-Based Import Importing Consumers Using File-Based Import: Explained This topic explains how to prepare and import consumer data from an external data source into Oracle Sales Cloud, using the File-Based Data Import feature. A consumer is a person who intends to purchase goods and services. Within Oracle Sales Cloud, a person with a selling relationship is referred to as a consumer. A 1-12 Oracle Sales Cloud Using Customer Data Management

21 consumer import object allows you to import all information about a consumer, such as the consumer profile, consumer address information, consumer contact point information, and consumer contact preference information. You must consider the following questions before importing consumer information: How does your legacy or source system represent the consumer information compared to how Oracle Sales Cloud represents the same data? Do you have to configure values in Oracle Sales Cloud to map them to your existing data values? Do you have to customize Oracle Sales Cloud to capture attributes that are critical to the way you do business? What import features are available for importing your business object? How do I verify my imported data? Comparing Business Object Structures You must understand how your consumer data corresponds with the data in Oracle Sales Cloud to be able to map your legacy data to the data needed by Oracle Sales Cloud. First, you must understand how Oracle Sales Cloud represents the structure of the data for a consumer. The consumer import object structure is hierarchical. The root of the hierarchy is the consumer profile, which must exist before you can import lower-level entities, such as , sell-to address, sales account profile, and fax. These child entities can have other entities as their child entities. This hierarchical structure supports one-to-many relationships between the components that make up the consumer. The following figure shows the consumer and its child entities. The person profile contains basic information about the consumer, such as the first name, last name, and party usage. For each consumer, you can have other information, such as sell-to addresses, phone details, and sales account profile. Note All entities referring to contact information, such as primary phone or , include a child entity that captures the contact preference. For example, the Primary Phone Contact Preference entity captures the contact preference of the consumer for the contact method primary phone. Comparing Business Object Data Each import object is a collection of attributes that helps to map your data to the Oracle Sales Cloud data and to support one-to-many relationships between the structural components that make up the consumer. Import Customer Information Using File-Based Import 1-13

22 A good understanding of the import objects and attribute details is critical to preparing your import data. The attribute details are available for your reference in the Oracle Enterprise Repository. The reference guide files contain descriptions, default values, and validations for each of the attributes. The validation information includes the navigation to the task where you can define values in Oracle Sales Cloud. For example, if you have values in your data that correspond to a choice list, then the validation information for that attribute provides the task name in the Setup and Maintenance work area where you can define your values. Extensible Attributes If you have to extend the import object to import your legacy or source data, then you must use Application Composer to design your object model extensions and to generate the required artifacts to register your extensions and make them available for importing. The corresponding import object is updated with the extensible attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes. Importing Consumers Using File-Based Data Import For the consumers business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks required to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. When creating a consumer, you use the Consumer import object. An import activity defines the instructions for processing the import data, including the source file, import mapping from the source file to the object and attribute, and the import schedule. When importing consumer information, you first import the basic person profile information and then the child entities for the consumer. When importing child entities, you must provide the parent reference information for all parent levels for the entity. You must provide the PartyOrigSystem and PartyOrigSystemReference of the consumer when importing contacts for the consumer. PartyOrigSystem is the source system code that identifies the source of the information being imported. PartyOrigSystemReference is unique for each row of data within a single import, and is a combination of PartyOrigSystem and a unique reference. For example, you first import basic profile details, such as first name, last name, party type, and party usage. You then import other information, such as additional names, , sell-to address, and primary phone for the consumer. Verifying Your Imported Data You can view the list of import activities from the Manage Import Activities page. You can verify your imported data by clicking the Status column for your import activity. Alternatively, you can also navigate to the Customer Center work area to view the consumer information that you have imported Oracle Sales Cloud Using Customer Data Management

23 Consumer Import Objects: How They Work Together The Consumer import object allows you to import consumers, their detailed information, and contacts related to the consumer. This topic describes the Consumer import object and introduces the following: Target import object concepts Target objects for the Consumer import object Target import object attribute Target object attribute reference guide files Consumer Target Import Object Concepts The Consumer import object imports consumer information, and is split into separate target import objects for organizing the individual attributes of the different aspects of the consumer. To map the source data in your import file to the target attributes in Oracle Sales Cloud, you must understand how the target objects are related and what attributes are included in each target object. The target import objects included in the Consumer import object are grouped into information about the consumer. The person profile is the target import object containing attributes to import information about the consumer. When updating an existing consumer with additional information, you must provide the parent reference information for the existing consumer. To update the information for an existing consumer or to create a consumer record, you can import consumer profile information, addresses, and contact points, such as phone and fax number. The following target import objects are for creating and updating the corresponding consumer information: PersonProfile, PrimaryPhone, Fax, Mobile, Classification, AdditionalIdentifier, AdditionalName, , SellToAddress, and SalesAccountProfile. Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Sales Cloud Applications attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference files contain descriptions, logic used to choose default values, and validation information for each of the Oracle Sales Cloud Applications attributes. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target import object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Note If any of the attributes that you want to import do not have an equivalent target object attribute, then review the Application Composer Extensibility features for the consumer. Import Customer Information Using File-Based Import 1-15

24 Target Import Objects Attributes Resources To access the reference guide files for the consumer target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository for Oracle Sales Cloud Applications ( The following table lists the reference guide files that are available from the Documentation tab for the Consumer File-Based Data Import asset. Target Import Object Description Reference Guide File Names PersonProfile Includes detailed person information such as person name, relationship type, gender, and marital status. PersonFirstName, PersonLastName, DateOfBirth, PersonAcademicTitle, and PlaceOfBirth. HZ_IMP_PARTIES_T_Reference SellToAddress PartyId, PartyOrigSystem, PartyOrigSystemReference, RelOrigSystem, RelOrigSystemReference, and RelationshipId. Includes consumer addresses and party sites information. If party site usage of an address is not defined, then the import process sets it to Sell-To. In case there are multiple addresses without party site usage information, then the import process designates one of the addresses as the Sell-To address. Sample attributes include Address1, Address2, City, Country, County, State, and PostalCode. Reference attributes for location: LocationOrigSystem, LocationOrigSystemReference, and LocationId1. Reference attributes for party sites: SiteOrigSystem and SiteOrigSystemReference, and PartysiteId1. Reference attributes for party site use: SiteuseOrigSystem, SiteuseOrigSystemRef, and PartySiteUseId. HZ_IMP_PARTYSITES_T_ Reference 1-16 Oracle Sales Cloud Using Customer Data Management

25 PrimaryPhone Mobile Fax Indicates the primary phone number of the consumer. If the consumer has multiple phone numbers, one of the phone numbers is designated as the primary phone number. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. CpOrigSystem and CpOrigSystemReference. Indicates the mobile phone number of the consumer. PhoneAreaCode, PhoneCountryCode, and PhoneNumber. CpOrigSystem and CpOrigSystemReference. Indicates the fax number of the consumer. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. CpOrigSystem and CpOrigSystemReference. Indicates the of the consumer. ContactPointPurpose, Address, and StartDate. CpOrigSystem and CpOrigSystemReference HZ_IMP_CONTACTPTS_T_ Reference HZ_IMP_CONTACTPTS_T_ Reference HZ_IMP_CONTACTPTS_T_ Reference HZ_IMP_CONTACTPTS_T_ Reference Import Customer Information Using File-Based Import 1-17

26 InstantMessenger Indicates the instant messenger or social networking information of a consumer. HZ_IMP_CONTACTPTS_T_ Reference SalesAccountProfile AdditionalName ContactPointPurpose, EndDate, InstantMessagingAddress, and InstantMessengerType. CpOrigSystem and CpOrigSystemReference. Includes detailed information about a consumer sales account. A sales account is a specific sellto entity within a given consumer. A consumer can have multiple sales accounts and sales account profiles. AccountDirectorId, CreationDate, NamedAccountFlag, and AssgnExceptionFlag. OwnerOrigSystem and OwnerOrigSystemReference. Indicates alternative name of a consumer. NameId, PersonFirstName, PersonLastName, and PersonTitle. ZCA_IMP_SALES_ACCOUNTS_ Reference HZ_IMP_ADDTNLPARTYNAMES_T_ Reference Classification AdditionalNameOrigSystem and AdditionalNameOrigSystemReference. Incudes classification information for a consumer. Classification allows you to categorize entities such as parties, projects, tasks, and orders as hierarchies. HZ_IMP_CLASSIFICS_T_ Reference ClassificationCode, ClassificationCategory, PrimaryFlag, and Rank. Reference Attributes: ClassificationOrigSystem and ClassificationOrigSystemReference Oracle Sales Cloud Using Customer Data Management

27 AdditionalIdentifier Includes detailed information about an additional identifier for a consumer. IdentifierValue, IdentifierType, Country, and IssuingAuthorityName. HZ_IMP_ADDTNLPARTYIDS_T_ Reference Relationship IdentifierValue, AdditionaldentifierOrigSystem and AdditionalldentifierOrigSystemReference. Includes information about a relationship between the consumer and another entity, such as an organization or a person. HZ_IMP_RELSHIPS_T_ Reference PrimaryPhoneContactPreference MobileContactPreference RelationshipCode, RelationshipType, and DependentFlag. RelationshipID, RelOrigSystem and RelOrigSystemReference. Indicates the consumer's preference about being contacted through phone. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. Reference Attributes: CpOrigSystem and CpOrigSystemReference. Indicates the consumer's preference about being contacted through mobile phone. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. Reference Attributes: CpOrigSystem and CpOrigSystemReference. HZ_IMP_CONTACTPREFS_ Reference HZ_IMP_CONTACTPREFS_ Reference Import Customer Information Using File-Based Import 1-19

28 FaxContactPreference ContactPreference Indicates the consumer's preference about being contacted through fax. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode, Reference Attributes: CpOrigSystem and CpOrigSystemReference. Indicates the consumer's preference about being contacted through mobile phone. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. Reference Attributes: CpOrigSystem and CpOrigSystemReference. HZ_IMP_CONTACTPREFS_ Reference HZ_IMP_CONTACTPREFS_ Reference Importing Contacts Using File-Based Import Importing Contacts Using File-Based Import: Explained This topic explains how to prepare and import contact data from an external data source into Oracle Sales Cloud using the File-Based Data Import feature. A contact is a person party related to a customer, and the contact object contains information that identifies the contact and offers the contact points of the contact. Contact points can be geographical addresses, phone numbers, IDs, URLs, messenger IDs, and so on. The contact object also contains contact preference information for the contact. You must create or import contacts before you can associate them with customer objects. You must consider the following questions before importing contact information: How does your legacy system or source system represent the contact compared to how Oracle Sales Cloud represents the same data? Do you have to configure values in Oracle Sales Cloud to map to your data values? Do you have to customize the Oracle Sales Cloud object model to capture additional attributes that are critical to the way you do business? What import features are available for importing your business object? How do you verify your imported data? Comparing Business Object Structures You must understand how your contact data corresponds with the data in Oracle Sales Cloud, in order to be able to map your legacy data to the data needed 1-20 Oracle Sales Cloud Using Customer Data Management

29 by Oracle Sales Cloud. First, you must understand how Oracle Sales Cloud represents the structure of the data for a contact. In Oracle Sales Cloud, one table stores the contact information and another table optionally stores contact point details for that contact. A contact point is an identified means to contact a party. Contact points can be phone numbers, IDs, Web site addresses, or instant messenger IDs. The following figure shows the contact object and its child entities. The contact profile contains basic information about the contact, such as the contact name, party type, and party usage. For each contact, you can assign classifications, phone details, and additional names. If the contact is a consumer, then the contact relationship of the consumer includes other child entities that capture information about the consumer contact, such as contact job, contact phone, contact address, and contact . Note All contact-related entities, such phone or , include a child entity that captures the contact preference. For example, the Phone Contact Preference entity captures the contact preference of the consumer for the contact method phone. Import Objects for the Contact To facilitate the import of contacts, Oracle Sales Cloud incorporates the structure of the contact business object into import objects. The import object for contacts is Contact. Import Customer Information Using File-Based Import 1-21

30 Comparing Business Object Data Each import object is a collection of attributes that helps to map your data to the Oracle sales Cloud data and to support one-to-many relationships between the structural components that make up the contact. A good understanding of the attribute details of the import objects is critical to preparing your import data. The reference guide files contain descriptions, logic used to choose default values, and validation information for each import object attribute. The validation information includes the navigation to the task where you can define values. For example, if you have values in your data that correlate to a choice list in Oracle Sales Cloud, then the validation information for that attribute provides the task name in the Setup and Maintenance work area where you can define your values. For additional information, including a list of reference guide file names and locations that you need to complete this task, see the following table. Import Object Contact Related Import Object Topic Contact Import Objects: How They Work Together Hint: You can use the keyword importing contacts to search for related topics in Oracle Sales Cloud help. Extensible Attributes If you need to extend an import object to import your legacy or source data, you must use Application Composer to design your object model extensions and to generate the required artifacts to register your extensions and make them available for importing. The corresponding import object is updated with the extensible attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes. Importing Contacts Using File-Based Data Import For the Contact business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. When creating a new contact, you import the Contact object. You must be assigned the Master Data Management Administrator job role to access and submit the import activities for contacts. Verifying Your Imported Data Use the File-Based Import activity reports to verify imported data. You can also access the customer center work area to view the contact information that you have imported Oracle Sales Cloud Using Customer Data Management

31 Contact Import Objects: How They Work Together You can import all your contact information using the Contact import object. This topic describes this import object and introduces the following Target import object concepts Target objects for the Contact import object Target import object attributes Target import object attribute reference guide files Target Import Object Concepts The Contact import object is used to import a contact's profile information, such as first name, last name, address, and so on, and contact point information, such as phone numbers, fax, IDs, and so on. The Contact import object is split into separate target import objects for organizing the individual attributes of the different aspects of the contact's profile and contact points. To map the source data in your import file to the target attributes in Oracle Sales Cloud, you must understand how the target objects are related and what attributes are included in each target object. Contact Target Import Objects The target import objects included in the Contact import are grouped into information about the contact and the contact's relationship with other parties. The contact profile is the target import object containing attributes to import information about the contact. You can have multiple contact relationships associated with a contact. There are multiple target import objects that include attributes to import contacts and their related information. When updating an existing contact, you must provide the parent reference information of the existing contact. When importing contact profile or contact point information for a contact, you must provide relationship reference information in addition to the parent reference. You must provide this information because a contact can have multiple relationships with an organization, such as employee or board member. When importing information about a contact, you must refer to the specific relationship that you want to import information for. For example, you must specify whether you want to import information for John Smith the employee or John Smith the board member. If you do not include the reference information for a contact relationship, then the import process creates a new relationship. To update the information for an existing contact or to create a contact record, you can import contact profile information, addresses, and contact points. The following target import objects are for creating and updating contact information: PersonProfile, Fax, PrimaryPhone, Url, SalesAccountProfile, Classification, AdditionalName, Relationship, and AdditionalIdentifier. To update or create a contact point, use the following target import objects: ContactRelationship, ContactJob, ContactAddress, Contact , ContactPhone, ContactMobile, ContactInstantMessenger, and ContactFax. All contact-pointrelated entities, such as phone or , include a child entity that captures the contact preference. For example, the ContactPhoneContactPreference entity captures the contact preference of the primary phone contact method. Import Customer Information Using File-Based Import 1-23

32 Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and the Oracle sales Cloud attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference files contain descriptions, logic used to choose default values, and validation information for each attribute. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Note If any of the attributes that you want to import do not have an equivalent for the target object attribute, then review the Application Composer Extensibility features for the object. Target Import Objects Attributes Resources To access the reference guide files for target import objects, see the File- Based Data Import assets in Oracle Enterprise Repository ( fusionappsoer.oracle.com). The following table lists the reference guide files that are available from the Documentation tab for the Contact File-Based Data Import asset. Target Import Object Description Reference Guide File Names PersonProfile Includes information that identifies a contact. PersonFirstName, PersonLastName, DateOfBirth, gender, HouseholdIncome, and PlaceOfBirth HZ_IMP_PARTIES_T_Reference Fax PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the fax number of the contact. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_CONTACTPTS_T_Reference 1-24 Oracle Sales Cloud Using Customer Data Management

33 FaxContactPreference Phone PhoneContactPreference Indicates the contact's preferences about being contacted through Fax. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the phone number of the contact. If the contact has multiple phone numbers, then the first phone number is designated as the primary phone number. The attributes of PrimaryPhone, Fax, and URL are the same. However, the value of the attribute ContactPointType is different for each of these contact point related entities. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the contact's preferences about being contacted by phone. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the of the contact. ContactPointPurpose, Address, and StartDate. PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_CONTACTPREFS_Reference HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_CONTACTPREFS_Reference HZ_IMP_CONTACTPTS_T_Reference Import Customer Information Using File-Based Import 1-25

34 ContactPreference InstantMessenger Mobile MobileContactPreference Indicates the contact's contact preferences about being contacted through . ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the instant messenger information of a contact. ContactPointPurpose, EndDate, InstantMessagingAddress, and InstantMessengerType. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the mobile number of a contact. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, PhoneNumber, and PrimaryFlag. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the contact's preferences about being contacted through mobile phone. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_CONTACTPREFS_Reference HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_CONTACTPREFS_Reference 1-26 Oracle Sales Cloud Using Customer Data Management

35 Classification Address AddressContactPreference AdditionalName Includes classification information for a contact. Classification allows you to categorize entities, such as parties, projects, tasks, and orders as hierarchies. ClassificationCode, ClassificationCategory, PrimaryFlag, and Rank. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the address of a contact. If the contact has multiple addresses, then the first address is designated as the primary address. Address1, Address2, City, Country, County, State, and PostalCode. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the contact's preferences about being contacted at the primary address. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the alternative name of a contact. Additional Name, Additional Name Type, and GlobalPreferredNameFlag. PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_CLASSIFICS_T_Reference HZ_IMP_PARTYSITES_T_Reference HZ_IMP_CONTACTPREFS_Reference HZ_IMP_ADDTNLPARTYNAMES_T_Reference Import Customer Information Using File-Based Import 1-27

36 AdditionalIdentifier ContactRelationship Contact Contact ContactPreference Includes the basic information about an additional identifier for the contact. IdentifierValue, IdentifierType, Country, and IssuingAuthorityName. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Includes information about a relationship between the contact and other parties. RelationshipCode, RelationshipType, and DependentFlag. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the contact point of the contact. ContactPointPurpose, Address, and StartDate. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the contact's preferences about being contacted through the contact point. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_ADDTNLPARTYIDS_T_Reference HZ_IMP_RELSHIPS_T_Reference HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_CONTACTPREFS_Reference 1-28 Oracle Sales Cloud Using Customer Data Management

37 ContactFax ContactFaxContactPreference ContactInstantMessenger ContactMobile Indicates the number of the fax contact point of the contact. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, and PhoneExtension. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the contact's preference about being contacted through the fax contact point. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode PartyOrigSystem, PartyOrigSystemReference, and PartyId. Captures information about a contact's instant messenger contact point. ContactPointPurpose, EndDate, InstantMessagingAddress, and InstantMessengerType. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the number of a contact's mobile contact point. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, PhoneNumber, and PrimaryFlag. PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_CONTACTPREFS_Reference HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_CONTACTPTS_T_Reference Import Customer Information Using File-Based Import 1-29

38 ContactMobileContactPreference ContactPhone ContactPhoneContactPreference Indicates the contact's preferences about being contacted through the mobile phone contact point. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the number of the contact's phone contact point. If the contact has multiple phone numbers, then the first phone number is designated as the primary phone number. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, PhoneNumber, and PrimaryFlag. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the contact's preferences about being contacted through the phone contact point. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_CONTACTPREFS_Reference HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_CONTACTPREFS_Reference 1-30 Oracle Sales Cloud Using Customer Data Management

39 ContactAddress ContactAddressContactPreference ContactJob Indicates the address of a contact's address contact point. If the contact has multiple addresses, then the first address is designated as the primary address. Address1, Address2, City, Country, County, State, and PostalCode. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the contact's preferences about being contacted at the address contact point. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode PartyOrigSystem, PartyOrigSystemReference, and PartyId. Includes the job information of a contact. Comments, ContactNumber, Department, DepartmentCode, JobTitle, and JobTitleCode. PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_PARTYSITES_T_Reference HZ_IMP_CONTACTPREFS_Reference HZ_IMP_CONTACTS_T_Reference Importing Country Structures Using File-Based Import Importing Country Structures Using File-Based Import: Explained This topic explains how to prepare and import country structure data from an external data source into Oracle Sales Cloud using the File-Based Data Import feature. 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, and finally the Postal Code. You can use the country structure to set up the following: Import Customer Information Using File-Based Import 1-31

40 The relationships between geographies within a country The types of geographies that you can define for a country Consider the following questions when importing your data: How does your legacy system or source system represent the country structure compared to how Oracle Sales Cloud represents the same data? Do you have to configure values in Oracle Sales Cloud to map to your data values? Do you have to customize Oracle Sales Cloud to capture additional attributes that are critical to the way you do business? What import features are available for importing your business object? How do you verify your imported data? Comparing Business Object Structures You must understand how your country structure data corresponds with the data in Oracle Sales Cloud in order to be able to map your legacy data to the data needed by Oracle Sales Cloud. First, you must understand how Oracle Sales Cloud represents the structure of the data for a country structure. You must import a separate country structure import object for each country. Each of these import objects must contain the geography types that are used in the country's structure, organized in a hierarchy using geography level numbers. For example, if you are importing the country structure of Australia, the country structure could be the following: 1: Country, 2: State, 3: County, 4: Town, 5: ZIP. Import Objects for the Country Structure To facilitate the import of country structures, Oracle Sales Cloud incorporates the structure of the country structure into import objects. The import object for country structures is GeoStructureLevel. Comparing Business Object Data Each import object is a collection of attributes that helps to map your data to the Oracle Sales Cloud data and to support one-to-many relationships between the structural components that make up the country structure. A good understanding of the attribute details of the import objects is critical to preparing your import data. For information about the Oracle Sales Cloud attributes, see the Oracle Enterprise Repository. The reference files contain descriptions, logic used to choose default values, and validation information for each of the Oracle Sales Cloud attributes. The validation information includes the navigation to the task where you can define values in Oracle Sales Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Sales Cloud, then the validation information for that attribute provides the task name in the Setup and Maintenance work area where you can define your values. For additional information, including a list of reference file names and locations that you need to complete this task, see the following table. Import Object Country Structure Related Import Object Topic Country Structure Import Objects: How They Work Together 1-32 Oracle Sales Cloud Using Customer Data Management

41 Extensible Attributes If you need to extend the Oracle Sales Cloud object to import your legacy or source data, you must use Application Composer to design your object model extensions and to generate the required artifacts to register your extensions and make them available for importing. The corresponding import object is updated with the extensible attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes. Importing Country Structures Using File-Based Data Import For the country structure business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. When creating a new country structure, you import the Country Structure object. You must be assigned the Master Data Management Administrator job role to access and submit the import activities for country structures. Verifying Your Imported Data You can view the list of import activities from the Manage Import Activities page. You can verify your imported data by clicking the Status column for your import activity. Country Structure Import Objects: How They Work Together This topic describes the Country Structure import object. You use the Country Structure import object when you submit a file-based import activity to import your country structure information. This topic introduces the following: Target import object concepts Target objects for the Country Structure import object Target import object attributes Target object attribute reference guide files Target Import Object Concepts The Country Structure import object is used to import a country structure hierarchy, including details, such as geography type, geography type name, parent geography type, geography level numbers, and so on. To map the source data in your import file to the target attributes in Oracle Sales Cloud, you must understand how the target objects are related and what attributes are included in each target object. Import Customer Information Using File-Based Import 1-33

42 Country Structure Target Import Objects The Country Structure import object contains one target import object that organizes the individual attributes of the different aspects of the geography structure. When updating an existing country structure, you must provide the parent reference information of the existing country structure. This reference information connects the imported geography structure to the existing one. Use the ImpGeoStructureLevel target import object to create and update country structure information. Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference guide file includes attribute descriptions, default values, and validations performed by the import process. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Note If any of the attributes you want to import does not have an equivalent target object attribute, then review the Application Composer extensibility features for country structures. Target Import Objects Attributes Resources To access the reference guide files for the country code's target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository ( fusionappsoer.oracle.com). For detailed information on importing geographies using file-based import, refer to Document No , Importing Master Reference Geography Data, on the Oracle Support site. The following table lists the reference guide files that are available from the Documentation tab for the Country Code File-Based Data Import asset. Target Import Object Description Reference Guide File Names ImpGeoStructureLevel Contains information that specifies a country's geography structure. GeographyType, GeographyTypeName, LevelNumber, and ParentGeographyType. Reference attribute: CountryCode HZ_IMP_GEO_STRUCTURE _LEVELS_Reference 1-34 Oracle Sales Cloud Using Customer Data Management

43 Importing Customer Hierarchies Using File-Based Import Importing Customer Hierarchy Using File-Based Import: Explained This topic describes how to import a customer hierarchy and customer hierarchy members. A customer hierarchy captures the hierarchical relationships that a customer has with other customers. A customer hierarchy consists of hierarchy members. A customer hierarchy can be used to process payments from one customer and apply them to another customer in the same hierarchy. It can also be used to create the revenue roll-up report that rolls up revenue numbers from opportunities for all customers in a hierarchy. You must consider the following questions before importing customer hierarchy information: Are all members of the customer hierarchy in Oracle Fusion Applications? Do I have to import additional hierarchy members to complete the hierarchy? How does your legacy system or source system represent the customer hierarchy compared to how Oracle Fusion Applications represent the same data? Do you have to configure values in Oracle Fusion Applications to map your existing data values to the Customer import object? Do you have to customize Oracle Fusion Applications to capture additional attributes that are critical to the way you do business? What import features are available for importing your business object? How do I verify my imported data? To import a customer hierarchy, you must: 1. Import customers who must be a part of the hierarchy. 2. Import a hierarchy definition that includes the hierarchy structure and the root node. 3. Import members from the existing customers into the hierarchy. Comparing Business Object Structures Before you can import your legacy or source system customer hierarchy data, you must first analyze the data and see how it corresponds to the customer object structure of Oracle Fusion Applications. You must understand how Oracle Fusion Applications represent the structure of the data for a customer hierarchy. The Oracle Fusion Applications customer hierarchy object structure is hierarchical. At the top level is the customer hierarchy, which must exist before you can import customer hierarchy members. The customer hierarchy and customer hierarchy member contain information about the customer hierarchy Import Customer Information Using File-Based Import 1-35

44 and customer hierarchy nodes, such as the hierarchy type, hierarchy code, hierarchy name, and hierarchy version. Comparing Business Object Data After you understand the structure of the data, then compare the detailed attribute values of your data with the Oracle Fusion Applications data. Each import object is a collection of attributes organized to assist you when mapping your data to the Oracle Fusion Applications data and to support one-to-many relationships between the structural components that make up the customer hierarchy. A good understanding of the import objects and attribute details is critical to preparing your import data. Oracle Fusion Applications attribute details are available for your reference in the Oracle Enterprise Repository. The reference guide files contain descriptions, default values, and validations for each of the Oracle Fusion Applications attributes. The validation information includes the navigation to the task where you can define values in Oracle Fusion Applications. For example, if you have values in your data that correspond to a choice list in Oracle Fusion Applications, then the validation information for that attribute will provide the task name in the Setup and Maintenance work area where you can define your values. Extensible Attributes If you want to extend the Oracle Fusion Applications import object to import your legacy or source data, then you must use Application Composer to design your object model extensions and to generate the required artifacts to register your extensions and make them available for importing. The corresponding import object is updated with the extensible attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes. Importing Customer Hierarchy Using File-Based Data Import For the customer hierarchy business object, you must use the File-Based Data Import feature. You prepare XML or text source data files, such as CSV, in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks required to configure the import objects, to create source file mappings, and to schedule the import activities. You submit file-based import activities for each import object. An import activity defines the instructions for processing import data, including the source file, import mapping from the source file to the Oracle Fusion Applications object and attribute, and the import schedule. When importing customer hierarchy information, you first import the customer hierarchy information and then the customer hierarchy members for the 1-36 Oracle Sales Cloud Using Customer Data Management

45 customer hierarchy. When importing customer hierarchy members, you must provide the parent reference information that refers to the customer hierarchy of the member. Verifying Your Imported Data Oracle Fusion Applications provide File-Based Import activity reports, which can be used to verify imported data. You can view the list of import activities from the Manage Import Activities page. You can verify the status of the import activity by clicking the Status column for your import activity. Alternatively, you can also navigate to the Manage Hierarchies task from Setup and Maintenance to view the customer hierarchy information that you have imported. Customer Hierarchy Import Objects: How They Work Together The Customer Hierarchy import object imports customer hierarchy and customer hierarchy members. This topic describes the Customer Hierarchy object and introduces the following: Target import object concepts Target objects for the Customer Hierarchy import object Target import object attributes Target import object attribute reference guide files for evaluating and mapping source file data Customer Hierarchy Target Import Objects Concepts The Customer Hierarchy import object imports customer hierarchy and customer hierarchy members. The Customer Hierarchy and Customer Hierarchy Members import objects are split into separate target import objects for organizing the individual attributes for the different aspects of the customer hierarchy. To map the source data in your import file to the target attributes in Oracle Sales Cloud, you must understand how the target objects are related and what attributes are included in each target object. Target Import Objects The target import objects in the customer hierarchy import object are grouped into information about the customer hierarchy and information about the customer hierarchy members. The CustomerHierarchy is the target import object containing attributes to import information about the customer hierarchy, and the CustomerHierarchyMember is the target import object containing attributes to import information about the customer hierarchy members. You can have multiple hierarchy members associated with a customer hierarchy. To import a customer hierarchy, you must do the following: 1. Import customers who must be part of the hierarchy. 2. Import the customer hierarchy definition that includes the hierarchy structure and the root node. Import Customer Information Using File-Based Import 1-37

46 3. Import existing customers as customer hierarchy members into the hierarchy. Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference files contain descriptions, logic used to choose default values, and validation information for each of the attributes. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Note If any of the attributes that you want to import do not have an equivalent target object attribute, then review the Application Composer Extensibility features for the customer hierarchy. Target Import Objects Attributes Resources To access the reference guide files for the customer hierarchy target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository ( The following table lists the reference guide files that are available from the Documentation tab for the Customer Hierarchy File-Based Data Import asset. Target Import Object Description Reference Guide File Names CustomerHierarchy Customer hierarchy definition and root node of the customer hierarchy HZ_IMP_HIERARCHIES_T _Reference CustomerHierarchyMember Customer hierarchy members HZ_IMP_HIERARCHY_NODES_ Reference Importing Customers Using File-Based Import Importing Customers Using File-Based Import: Explained This topic explains how to prepare and import customer data from an external data source into Oracle Sales Cloud using the File-Based Data Import feature Oracle Sales Cloud Using Customer Data Management

47 A customer is an entity with whom you have a selling relationship. Oracle Sales Cloud refers to sales account and sales prospects collectively as a Customer. A customer business object allows you to capture all information about a customer, such as the customer profile, customer contact relationships information, and customer contact points. A sales account is a specific sell-to entity within a given customer. You can create leads and opportunities for sales accounts. An entity with a sales account can be one of the following: Sales Prospect: A prospective entity or person who does not have a sell-to address. This entity is used to define leads. Customer: A sales account or sales prospects. Legal Entity: A legal entity is a party that can enter into legal contracts or a business relationship. It can be sued if it fails to meet contractual obligations. You can use the Customer import object to import sales accounts or sales prospects of the type organization. You can use the Group Customer import object to import customers of the type group, and the Consumer import object to import customers of the type person. You must consider the following questions when importing your data: Did you identify the records that should be imported as sales prospects, and the records that should be imported as sales accounts? How does your legacy or source system represent the customer information compared to how Oracle Sales Cloud represents the same data? Do you have to configure values in Oracle Sales Cloud to map your existing data values to the Customer import object? Do you have to customize Oracle Sales Cloud to capture attributes that are critical to the way you do business? What import features are available for importing your business object? How do I verify my imported data? Comparing Business Object Structures Before you can import your customer data from the legacy or source system, you must first analyze the data and see how it corresponds to the customer object structure of Oracle Sales Cloud. You must understand how Oracle Sales Cloud represents the structure of the data for a customer. The Customer import object structure is hierarchical. The root of the hierarchy is the organization profile, which must exist before you can import lower-level components, such as classifications, contacts, and sales account profiles. These child entities can have other entities as their child entities. This hierarchical structure supports one-to-many relationships between the components that make up the customer. The following figure shows the customer object and its child entities. Import Customer Information Using File-Based Import 1-39

48 The organization profile contains basic information about the customer, such as the customer name and party usage. For each customer, you can assign classifications, contacts, sell to addresses, phone details, and additional names. The contact of the customer, in turn, includes other child entities that capture information about the contact, such as contact job, contact primary phone, contact primary address, and contact . Note All contact entities, such as primary phone or , include a child entity that captures the contact preference. For example, the Primary Phone Contact Preference entity captures the contact preference of the customer for the contact method primary phone. Comparing Business Object Data After you understand the structure of the data, the next step is to compare the detailed attribute values of your data with the Oracle Sales Cloud data. Each import object is a collection of attributes organized to assist you when mapping your data to the Oracle Sales Cloud data and to support one-to-many relationships between the structural components that make up the customer. A good understanding of the import objects and attribute details is critical to preparing your import data. The reference guide files contain descriptions, default values, and validations for each of the attributes. The validation information includes the navigation to the task where you can define values in Oracle Sales Cloud. For example, if you have values in your data that correspond to a choice list, then the validation information for that attribute provides the task name in the Setup and Maintenance work area where you can define your values. Extensible Attributes To extend an object to import your legacy or source data, you must use Application Composer to design your object model extensions and to generate the required artifacts to register your extensions and make them available for importing. The corresponding import object is updated with the extensible 1-40 Oracle Sales Cloud Using Customer Data Management

49 attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes. Importing Customers Using File-Based Data Import For the customer business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Import Setup and Maintenance task list includes the tasks required to configure the import objects, to create source file mappings, and to schedule the import activities. You submit file-based import activities for each import object. An import activity defines the instructions for processing import data including the source file, import data mapping from the source file to the import object and attribute, and the import schedule. When importing customer information, you first import the basic customer profile information, followed by the child entities for the customer. When importing child entities, you must provide the parent reference information for all parent levels for the entity. For example, you first import basic profile details, such as customer name, party type, and party usage. You then import contacts and contact information, such as phone, address, contact points, and fax for the customer. You must provide the PartyOrigSystem and PartyOrigSystemReference of the customer when importing contacts for the customer. PartyOrigSystem is the source system code that identifies the source of the information being imported. PartyOrigSystemReference is unique for each row of data within a single import, and is a combination of PartyOrigSystem and a unique reference. When importing contact information for a customer, you must provide the relationship reference information. This information is required because a contact can have multiple relationships with a customer. Verifying Your Imported Data You can view the list of import activities from the Manage Import Activities page. You can verify your imported data by clicking the Status column for your import activity. Alternatively, you can also navigate to the Customer Center work area to view the customer information that you have imported. Customer Import Objects: How They Work Together The Customer import object allows you to import customers, their detailed information, and contacts related to the customer. This topic describes the Customer import object. It introduces the following: Target import object concepts Target objects for the Customer import object Target import object attribute Target import object attribute reference guide files for evaluating and mapping source file data Import Customer Information Using File-Based Import 1-41

50 Customer Target Import Object Concepts The Customer import object imports customer information and contacts related to customer. The Customer import object is split into separate target import objects for organizing the individual attributes for the different aspects of the customer and customer contact. Before you import customer information, you must understand how the target objects are related and what attributes are included in each object. This understanding helps you create the appropriate mapping between the source data in your import file and the target attributes. The target import objects included in the Customer import object are grouped into information about the customer and the customer contact. The organization profile is the target import object containing attributes to import information about the customer. You can have multiple contacts associated with a customer. The Customer import object has multiple target import objects that include attributes to import customer contacts and their related information. When updating an existing customer with additional information, you must provide the parent reference information for the existing customer. When importing customer contacts or contact information for a customer, you must provide relationship reference information in addition to the parent reference. This information is required because a contact can have multiple relationships with an organization, such as an employee or board member. When importing information about a contact you must refer to the specific relationship that you want to import information for. For example, you might want to import information for John Smith the employee or John Smith the board member. If you do not include the reference information for a customer-contact relationship, then the import process creates a relationship. To update the information for an existing customer or to create a customer record, you can import customer profile information, addresses, and contact points, such as a phone and fax. The following target import objects are for creating and updating the corresponding customer information: OrganizationProfile, Fax, Address, PrimaryPhone, Url, SalesAccountProfile, Classification, AdditionalName, Relationship, SellToAddress, and AdditionalIdentifier. To update or to create a customer contact, use the following target import objects: ContactPersonProfile, ContactJob, ContactPrimaryAddress, Contact , ContactPrimaryPhone, ContactMobile, ContactInstantMessenger, and ContactFax. All contact-related entities, such as primary phone or , include a child entity that captures the contact preference. For example, the Primary Phone Contact Preference entity captures the contact preference of the legal entity for the contact method primary phone. Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference guide file includes attribute descriptions, default values, and validations performed by the import process. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can 1-42 Oracle Sales Cloud Using Customer Data Management

51 predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Note If any of the attributes you want to import do not have an equivalent target object attribute, then review the Application Composer Extensibility features for the customer. Target Import Objects Attributes Resources To access the reference guide files for the customer target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository ( fusionappsoer.oracle.com). The following table lists the reference guide files that are available from the Documentation tab for the Customer File-Based Data Import asset. Target Import Object Description Reference Guide File Names OrganizationProfile Includes detailed customer information, such as, organization name and organization type. OrganizationSize, UniqueNameAlias, CeoName, and CertificationLevel. HZ_IMP_PARTIES_T_Reference PrimaryPhone Address PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the primary phone number of the customer. If the customer has multiple phone numbers, one of the phone numbers is designated as the primary phone number. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. CpOrigSystem and CpOrigSystemReference. Includes the address information for a customer, such as, address, city, and country. Address1, City, Country, and LocationId LocationOrigSystem and LocationOrigSystem Reference HZ_IMP_CONTACTPTS_T_ Reference HZ_IMP_LOCATIONS_T_Reference Import Customer Information Using File-Based Import 1-43

52 Classification Includes classification information for a customer. Classification allows you to categorize entities such as parties, projects, tasks, and orders as hierarchies. ClassificationCode, ClassificationCategory, PrimaryFlag, and Rank. HZ_IMP_CLASSIFICS_T_Reference AdditionalName ClassificationOrigSystem and ClassificationOrigSystemReference. Indicates alternative name of a customer. HZ_IMP_ADDTNLPARTYNAMES_ T_Reference Additional Name, Additional Name Type, and GlobalPreferredNameFlag. Fax AdditionalNameOrigSystem and AdditionalNameOrigSystemReference. Indicates the fax of the customer. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. HZ_IMP_CONTACTPTS_T _Reference FaxContactPreference Url CpOrigSystem and CpOrigSystemReference. Indicates the customer preference about being contacted through Fax. PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Indicates the Url of the customer organization. ContactPointType, PrimaryFlag, Url, and WebType. CpOrigSystem and CpOrigSystemReference. HZ_IMP_CONTACTPREFS_ Reference HZ_IMP_CONTACTPTS_T_ Reference 1-44 Oracle Sales Cloud Using Customer Data Management

53 SalesAccountProfile SellToAddress AdditionalIdentifier Includes detailed information about a customer sales account. A sales account is a specific sellto entity within a given customer. A customer can have multiple sales accounts and sales account profiles. AccountDirectorId, NamedAccountFlag, and AssgnExceptionFlag. OwnerOrigSystem and OwnerOrigSystemReference. Includes customer addresses and party sites information. If party site usage of an address is not defined, then the import process sets it to Sell-To. If there are multiple addresses without party site usage information, then the import process designates one of the addresses as the Sell-To address. Address1, Address2, City, Country, County, and State. Reference attributes for location: LocationOrigSystem, LocationOrigSystemReference, and LocationId1. Reference attributes for party sites: SiteOrigSystem, SiteOrigSystemReference, and PartysiteId1. Reference attributes for party site use: SiteuseOrigSystem, SiteuseOrigSystemRef, and PartySiteUseId. Includes detailed information about an additional identifier for the customer. IdentifierValue, IdentifierType, Country, and IssuingAuthorityName. ZCA_IMP_SALES_ACCOUNTS _Reference HZ_IMP_PARTYSITES_T_ Reference HZ_IMP_ADDTNLPARTYIDS_T _Reference IdentifierValue, AdditionaldentifierOrigSystem, and AdditionalldentifierOrigSystemReference. Import Customer Information Using File-Based Import 1-45

54 Relationship ContactPersonProfile ContactAdditionalName Includes information about a relationship between the customer and another entity, such as an organization or a person. You must enter a relationship code in the RelationshipCode column, when creating a relationship. RelationshipCode, RelationshipType, and DependentFlag. RelationshipID, RelOrigSystem and RelOrigSystemReference. Includes detailed information, such as, person name, relationship type, and marital status, of a customer contact. Gender, MaritalStatus, PartyType, PartyUsageCode, PersonFirstName, and PersonLastName. PartyID, PartyOrigSystem, PartyOrigSystemReference, RelOrigSystem, RelOrigSystemReference, and RelationshipId. Indicates alternative name of a customer contact. NameId, PersonFirstName, PersonLastName, and PersonTitle. HZ_IMP_RELSHIPS_T_Reference HZ_IMP_RELSHIPS_T_Reference HZ_IMP_ADDTNLPARTYNAMES_T _Reference Contact AdditionalNameOrigSystem and AdditionalNameOrigSystemReference. Indicates the of the customer contact. HZ_IMP_CONTACTPTS_T_ Reference ContactPointPurpose, Address, and StartDate. CpOrigSystem and CpOrigSystemReference Oracle Sales Cloud Using Customer Data Management

55 ContactInstantMessenger Indicates the instant messenger or social networking information of a customer contact. HZ_IMP_CONTACTPTS_T_ Reference ContactPrimaryAddress ContactFax ContactJob ContactPointPurpose, EndDate, InstantMessagingAddress, and InstantMessengerType. CpOrigSystem and CpOrigSystemReference. Indicates the primary address of a customer contact. If the contact has multiple addresses, one of the addresses is designated as the primary address. Address1, Address2, City, Country, County, and State. Reference attributes for loaction: LocationOrigSystem, LocationOrigSystemReference, and LocationId1. Reference attributes or party sites: SiteOrigSystem, SiteOrigSystemReference, and PartysiteId1. Indicates the fax of the customer contact. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, and PhoneExtension. CpOrigSystem and CpOrigSystemReference. Includes job information of a customer contact. Comments, ContactNumber, Department, DepartmentCode, and JobTitleCode. RelationshipID, RelOrigSystem and RelOrigSystemReference HZ_IMP_PARTYSITES_T _Reference HZ_IMP_CONTACTPTS_T_ Reference HZ_IMP_CONTACTS_T_Reference Import Customer Information Using File-Based Import 1-47

56 ContactMobile ContactPrimaryPhone PrimaryPhoneContactPreference Contact ContactPreference Indicates the mobile number of a customer contact. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, PhoneNumber, and PrimaryFlag. CpOrigSystem and CpOrigSystemReference. Indicates the primary phone number of the customer contact. If the customer has multiple phone numbers, one of the phone numbers is designated as the primary phone number. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, PhoneNumber, and PrimaryFlag. CpOrigSystem and CpOrigSystemReference. Indicates the customer contact preference about being contacted through phone. PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Indicates the customer contact preference about being contacted through . PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. HZ_IMP_CONTACTPTS_T_ Reference HZ_IMP_CONTACTPTS_T _Reference HZ_IMP_CONTACTPREFS _Reference HZ_IMP_CONTACTPREFS_ Reference 1-48 Oracle Sales Cloud Using Customer Data Management

57 ContactFaxContactPreference ContactMobileContactPreference Indicates the customer contact preference about being contacted through Fax. PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Indicates the customer contact preference about being contacted through mobile phone. PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. HZ_IMP_CONTACTPREFS_ Reference HZ_IMP_CONTACTPREFS_ Reference CpOrigSystem and CpOrigSystemReference. ContactPrimaryAddressContactPreference Indicates the customer contact preference about being contacted at the primary address. HZ_IMP_CONTACTPREFS _Reference PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. ContactPrimaryPhoneContactPreference Indicates the customer contact preference about being contacted through the primary phone number. HZ_IMP_CONTACTPREFS _Reference PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Import Customer Information Using File-Based Import 1-49

58 Importing Employee Resources Using File-Based Import Importing Employee Resources Using File-Based Import: Explained This topic explains how to prepare and import employee resource data from an external data source into Oracle sales Cloud using the File-Based Data Import feature. Employee resources are employees within the deploying company who can be assigned work objects. You must create or import employee resources before you can associate them with resource organizations, resource teams, or work objects. You enter your employee resource information using the Setup and Maintenance work area, Manage Resources task, or you can import data to create new or update existing employee resources. Consider the following questions when importing your data: How does your legacy system or source system represent the employee resource compared to how Oracle Sales Cloud represent the same data? Do you have to configure values in Oracle Sales Cloud to map to your data values? Do you have to customize Oracle Sales Cloud to capture additional attributes that are critical to the way you do business? What import features are available for importing your business object? How do you verify your imported data? Comparing Business Object Structures You must understand how your employee resource data corresponds with the data in Oracle Sales Cloud in order to be able to map your legacy data to the data needed by Oracle Sales Cloud. First, you must understand how Oracle Sales Cloud represent the structure of the data for an employee resource. In Oracle Sales Cloud, one table stores the employee resource definition and other tables optionally store profile details for that employee resource. Profile details for a resource include information about an employee resource's organization and team memberships. The following figure illustrates the structure of the Employee Resource object Oracle Sales Cloud Using Customer Data Management

59 The worker profile contains basic information about the employee resource, such as the employee resource's primary address and resource profile details. Import Objects for the Employee Resource To facilitate the import of employee resources, Oracle Sales Cloud incorporate the structure of the employee resource into import objects. The import object for the employee resource is Employee Resource. Comparing Business Object Data Each import object is a collection of attributes that helps to map your data to the Oracle Sales Cloud data and to support one-to-many relationships between the structural components that make up the employee resource. A good understanding of the attribute details of the import objects is critical to preparing your import data. The reference guide files contain descriptions, logic used to choose default values, and validation information for each import object attribute. The validation information includes the navigation to the task where you can define values in Oracle Sales Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Sales Cloud, then the validation information for that attribute provides the task name in the Setup and Maintenance work area where you can define your values. For additional information, including a list of reference guide file names and locations that you need to complete this task, see the following table. Import Object Employee Resource Related Import Object Topic Employee Resource Import Objects: How They Work Together Hint: You can use the keyword importing employee resources to search for related topics in Oracle Sales Cloud help. Extensible Attributes If you need to extend the Oracle Sales Cloud object to import your legacy or source data, you must use Application Composer to design your object model extensions and to generate the required artifacts to register your extensions and make them available for importing. The corresponding import object is updated with the extensible attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes. Importing Employee Resources Using File-Based Data Import For the employee resource business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the import objects to create source-file mappings and to schedule the import activities. You submit file-based import activities Import Customer Information Using File-Based Import 1-51

60 for each import object. When creating a new employee resource, you import the Employee Resource import object. You must be assigned the Master Data Management Administrator job role to access and submit the import activities for employee resources. Verifying Your Imported Data Oracle Sales Cloud provide File-Based Import activity reports, which can be used to verify imported data. Users with either the Master Data Management Administrator job role can also navigate to the Manage Resources work area to view the imported employee resources. Employee Resource Import Objects: How They Work Together Employee resources are employees to whom you can assign work objects, for example, service agents, sales managers, and so on. You can import all your employee resource information using the Employee Resource import object. This topic describes this import object. This topic introduces the following: Target import object concepts Target objects for the Employee Resource import object Target import object attributes Target import object attribute reference guide files Target Import Object Concepts The Employee Resource import object is used to import an employee resource's worker profile information, such as first name, last name, address, and so on, and the employee resource's resource profile information, such as resource organization and resource team memberships. To map the source data in your import file to the target attributes in Oracle Sales Cloud, you must understand how the target objects are related and what attributes are included in each target object. Employee Resource Target Import Objects The target import objects included in the Employee Resource import object are grouped into information about the employee resource's profile and the employee resource's address information. The Worker profile is the target import object containing attributes to import information about the employee resource. When updating an existing employee resource, you must provide the parent reference information of the existing employee resource. When importing an employee resource's resource team information, you must provide relationship reference information in addition to the parent reference, because an employee resource can belong to more than one team simultaneously. To update the information for an existing employee resource or to create an employee resource record, you can import employee resource profile information and addresses. The following target import objects are for creating and updating employee resource information: WorkerProfile, ResourceProfile, and PrimaryAddress Oracle Sales Cloud Using Customer Data Management

61 To update or create an employee resource's resource profile, use the following target import objects: ResourceOrganizationMembership and ResourceTeamMembership. Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference guide files contain descriptions, logic used to choose default values, and validation information for each import object attribute. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Note If any of the attributes you want to import do not have an equivalent target object attribute, then review the Application Composer Extensibility features for the object. Target Import Objects Attributes Resources To access the reference guide files for the employee resource's target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository ( The following table lists the reference guide files that are available from the Documentation tab for the Employee Resource File-Based Data Import asset. Target Import Object Description Reference Guide File Names WorkerProfile Contains information that identifies an employee. ResourceProfile and PrimaryAddress. HRC_LOADER_BATCH_LINES _Reference ResourceProfile PartyOrigSystem, PartyOrigSystemReference, and PartyId. Contains information about a resource. PartyId, FirstName, LastName, Department, and JobCode. PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_RESOURCES_Reference Import Customer Information Using File-Based Import 1-53

62 PrimaryAddress Indicates the address of a resource. If the resource has multiple addresses, then the first address is designated as the primary address. Address1, Address2, City, Country, County, State, and PostalCode. HZ_IMP_PARTYSITES_T_Reference PartyOrigSystem, PartyOrigSystemReference, and PartyId. ResourceOrganizationMembership Contains the employee resource's resource organization membership information. RequestId, PartyId, ParentOrganizationName, OrganizationId, OrganizationName, and OrganizationUsage. HZ_IMP_GROUP_MEMBERS _Reference ResourceTeamMembership PartyOrigSystem, PartyOrigSystemReference, and PartyId. Contains the employee resource's resource team membership information. RequestId, TeamMemberId, TeamId, and TeamNumber. PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_TEAM_MEMBERS_ Reference Importing Geographies Using File-Based Import Importing Geographies Using File-Based Import: Explained This topic describes the tasks you must perform to import geography information. 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 custom zones and addresses. Consider the following questions when importing your data: 1-54 Oracle Sales Cloud Using Customer Data Management

63 How does your legacy system or source system represent the geography compared to how Oracle Sales Cloud represents the same data? Do you have to configure values in Oracle Sales Cloud to map to your data values? What import features are available for importing your business object? How do you verify your imported data? Comparing Business Object Structures You must understand how your geography data corresponds with the data in Oracle Sales Cloud in order to be able to map your legacy data to the data needed by Oracle Sales Cloud. First, you must understand how Oracle Sales Cloud represents the structure of the data for a geography. You must import a separate country structure import object for each country. Each of these import objects must contain the geography types that are used in the country's structure, organized in a hierarchy using geography level numbers. For example, if you are importing the country structure of Australia, the country structure could be the following: 1: Country, 2: State, 3: County, 4: Town, 5: ZIP. Import Objects for the Geography To facilitate the import of geographies, Oracle Sales Cloud incorporates the structure of the geography into import objects. The import object for the geography is ImpGeography. Comparing Business Object Data Each import object is a collection of attributes that helps to map your data to the Oracle Sales Cloud data and to support one-to-many relationships between the structural components that make up the geography. A good understanding of the attribute details of the import objects is critical to preparing your import data. For information about the Oracle Sales Cloud attributes, see the Oracle Enterprise Repository. The reference guide files contain descriptions, logic used to choose default values, and validation information for each import object attribute. The validation information includes the navigation to the task where you can define values in Oracle Sales Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Sales Cloud, then the validation information for that attribute provides the task name in the Setup and Maintenance work area where you can define your values. For additional information, including a list of reference file names and locations that you need to complete this task, see the following table. Import Object ImpGeography Related Import Object Topic Geography Import Objects: How They Work Together Hint: You can use the keyword importing geographies to search for related topics in Help. Extensible Attributes Oracle Sales Cloud does not support extensible attributes for geographies. You can only import data for attributes provided by Oracle Sales Cloud. Import Customer Information Using File-Based Import 1-55

64 Importing Geographies Using File-Based Data Import For the geography business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. When creating a new geography, you import the Geography object. You must be assigned the Master Data Management Administrator job role to access and submit the import activities for geographies. When importing geography information, you must provide the parent reference information for all parent levels for the entity. Verifying Your Imported Data Oracle Sales Cloud provides File-Based Import activity reports, which can be used to verify imported data. Users with the Master Data Management Administrator job role can also navigate to the Manage Geographies work area to view the imported geographies. Geography Import Objects: How They Work Together This topic describes the Geography import object. You use the Geography import object to import geography information. This topic introduces the following: Target import object concepts Target objects for the Geography import object Target import object attributes Target import object attribute reference guide files Target Import Object Concepts The Geography import object is used to import geography hierarchy information to create or update the geography data of a country. To map the source data in your import file to the target attributes in Oracle Sales Cloud, you must understand how the target objects are related and what attributes are included in each target object. Geography Target Import Objects The target import objects in the Geography import object contain information about the geography hierarchy. When updating an existing geography, you must provide the parent reference information of the existing geography, which connects the geography to the country of which it is a part. Use the ImpGeography target import object to create and update geography information. Note Before you import geography data for a country, you must define the country's geography structure Oracle Sales Cloud Using Customer Data Management

65 Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference guide file includes attribute descriptions, default values, and validations performed by the import process. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Target Import Objects Attributes Resources To access the reference guide files for the geography's target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository ( fusionappsoer.oracle.com). For detailed information on importing geographies using file-based import, refer to Document No , Importing Master Reference Geography Data, on the Oracle Support site. The following table lists the reference guide files that are available from the Documentation tab for the Geography File-Based Data Import asset. Target Import Object Description Attribute Reference Guide File Names ImpGeography Contains information that captures a country's geography hierarchy details. CountryCode, GeoDataProvider, GeographyType, PrimaryGeographyCode, PrimaryGeographyCodeType, and PrimaryGeographyName. Reference attribute: CountryCode HZ_IMP_GEOGRAPHIES_T _Reference Importing Group Customers Using File-Based Import Importing Group Customers Using File-Based Import: Explained This topic explains how to prepare and import group customer data from an external data source into Oracle Sales Cloud, using the File-Based Data Import feature. Import Customer Information Using File-Based Import 1-57

66 A group customer is a party consisting of a collection of persons and organizations. A group, similar to a person or organization, can enter into a business relationship with other parties and can be assigned to opportunities and leads. A group can have members of party type person or organization. You can maintain group customers information in Oracle Sales Cloud to create leads and opportunities for a group, or capture information about a group to know them better. However, maintaining this information may not let you assign all sales and marketing activities to a group. You must consider the following questions before importing group customer information: How does your legacy or source system represent the group customer information compared to how Oracle Sales Cloud represents the same data? Do you have to configure values in Oracle Sales Cloud to map your existing data values to the Group Customer import object? Do you have to customize Oracle Sales Cloud to capture additional attributes that are critical to the way you do business? What import features are available for importing your business object? How do I verify my imported data? Comparing Business Object Structures You must understand how your group customer data corresponds with the data in Oracle Sales Cloud to be able to map your legacy data to the data needed by Oracle Sales Cloud. First, you must understand how Oracle Sales Cloud represents the structure of the data for a group customer. The group customer import object structure is hierarchical. At the top level is the group profile, which must exist before you can import lower-level components, such as classifications, additional names, additional identifier, and members. These child entities can have other entities as their child entities. This hierarchical structure supports one-to-many relationships between the components that make up the group customer. The following figure shows the group customer import object and its child entities. The group customer profile contains basic information about the group customer, such as the group name, group type, and the group-party usage. For each group customer, you can assign classifications, members, relationships, additional identifier, and additional names. Note 1-58 Oracle Sales Cloud Using Customer Data Management

67 All entities referring to contact information, such as primary phone or , include a child entity that captures the contact preference. For example, the Phone Contact Preference entity captures the contact preference of the group for the phone contact method. Comparing Business Object Data Each import object is a collection of attributes that helps to map your data to the Oracle Sales Cloud data and to support one-to-many relationships between the structural components that make up the group customer. A good understanding of the import objects and attribute details is critical to preparing your import data. The attribute details are available for your reference in the Oracle Enterprise Repository. The reference guide files contain descriptions, default values, and validations for each of the attributes. The validation information includes the navigation to the task where you can define values in Oracle Sales Cloud. For example, if you have values in your data that correspond to a choice list, then the validation information for that attribute will provide the task name in the Setup and Maintenance work area where you can define your values. Extensible Attributes If you want to extend the object data to import your legacy or source data, then you must use Application Composer to design your object model extensions and to generate the required artifacts to register your extensions and make them available for importing. The corresponding import object is updated with the extensible attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes. Importing Group Customers Using File-Based Data Import For the group customer business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks that are required to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. An import activity defines the instructions for processing import data, including the source file, import mapping from the source file to the object and attribute, and the import schedule. When importing group customer information, you must first import the basic group customer profile information, followed by the child entities for the group customer. When importing child entities, you must provide the parent reference information for all parent levels for the entity. You must provide the PartyOrigSystem and PartyOrigSystemReference of the group customer when importing contacts for the group customer. PartyOrigSystem is the source system code that identifies the source of the information being imported. PartyOrigSystemReference is unique for each row of data within a single import, and is a combination of PartyOrigSystem and a unique reference. For example, Import Customer Information Using File-Based Import 1-59

68 you first import basic profile details, such as first name, last name, party type, and party usage. You then import contact information, such as phone, address, contact points, and fax for the group customer. Verifying Your Imported Data Oracle Sales Cloud provide File-Based Import activity reports, which you can use to verify imported data. You can view the list of import activities from the Manage Import Activities page. You can verify the status of the import activity by clicking the Status column for your import activity. Alternatively, you can also navigate to the Party Center work area to view the customer information that you have imported. Group Customer Import Objects: How They Work Together The Group Customer import object allows you to import group customers, their basic information, and members of the group. This topic describes the Group Customer import object and introduces the following: Target import object concepts Target objects for the Group Customer import object Target import object attributes Target import object attribute reference guide files for evaluating and mapping source file data Group Customer Target Import Objects Concepts The Group Customer import object imports group customers and its members. The Group Customer import object is split into separate target import objects for organizing the individual attributes for the different aspects of the group customer. To map the source data in your import file to the target attributes in Oracle Sales Cloud, you must understand how the target objects are related and what attributes are included in each target object. Group Customer Target Import Objects The target import objects in the Group Customer import object are grouped into information about the group customer and information about the member. The group profile is the target import object containing attributes to import information about the group customer. You can have multiple members associated with a group customer. You can assign only an organization or a person as a member of a group. You cannot assign a group as a member of another group. When updating an existing group customer with additional information, you must provide the parent reference information for the existing group customer. When importing contacts or contact information for a group customer, you must provide relationship reference information in addition to the parent reference. When importing information about a member, you must refer to the specific relationship that you want to import information for. For example, you might want to import information for John Smith the employee or John Smith the board member. If you do not include the reference information for a relationship, then the import process will create a relationship. To update the information for an existing group customer or to create a group customer record, you can import group customer profile information, addresses, 1-60 Oracle Sales Cloud Using Customer Data Management

69 and contact points, such as phone and fax. The following target import objects are for creating and updating the group customer information: GroupProfile, Fax, Mobile, Phone, , InstantMessenger, Relationship, Member, Address, Classification, AdditionalName, and AdditionalIdentifier. All contact-related entities, such phone or , include a child entity that captures the contact preference. For example, the Phone Contact Preference entity captures the contact preference of the group customer for the contact method primary phone. Additionally, the Address import object for a group customer includes another child entity, AddressPurpose, that captures the purpose of the current group customer address. Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference guide file includes attribute descriptions, default values, and validations performed by the import process. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Note If any of the attributes you want to import do not have an equivalent target object attribute, then review the Application Composer Extensibility features for the group customer. Target Import Objects Attributes Resources To access the reference guide files for the group customer target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository ( fusionappsoer.oracle.com). The following table lists the reference guide files that are available from the Documentation tab for the Group Customer File-Based Data Import asset. Target Import Object Description Reference Guide File Names GroupProfile Includes detailed group customer information, such as, group name and group type. The default party usage for a group customer is SALES_PROSPECT. AnnualIncome, NumOfDependents, MedianAge, and CertificationLevel. PartyOrigSystem, PartyOrigSystemReference, and PartyId. HZ_IMP_PARTIES_T_Reference Import Customer Information Using File-Based Import 1-61

70 Relationship Member Classification Includes information about the relationship between the group customer and the group member. You must enter a relationship code in the RelationshipCode column, when creating a relationship. RelationshipCode and RelationshipType. RelOrigSystem RelationshipID, and RelOrigSystemReference. Includes information about the group customer member. ObjectKey and SubjectId. RelOrigSystem RelationshipID, and RelOrigSystemReference. Includes classification information for a group customer. Classification allows you to categorize entities such as parties, projects, tasks, and orders as hierarchies. ClassificationCode, ClassificationCategory, PrimaryFlag, and Rank. HZ_IMP_RELSHIPS_T HZ_IMP_RELSHIPS_T HZ_IMP_CLASSIFICS_T AdditionalIdentifier Reference Attributes: ClassificationOrigSystem and ClassificationOrigSystemReference. Includes detailed information about an additional identifier for the group customer. HZ_IMP_ADDTNLPARTYID_T IdentifierValue, IdentifierType, Country, and IssuingAuthorityName. IdentifierValue, AdditionaldentifierOrigSystem, and AdditionalldentifierOrigSystemReference Oracle Sales Cloud Using Customer Data Management

71 AdditionalName Indicates alternative name of a group customer. Additional Name, Additional Name Type, and GlobalPreferredNameFlag. HZ_IMP_ADDTNLPARTYNAMES _T Url Reference Attributes: AdditionalNameOrigSystem and AdditionalNameOrigSystemReference. Indicates the Url of the group customer. HZ_IMP_CONTACTPTS_T_ Reference ContactPointType, PrimaryFlag, Url, and WebType. InstantMessenger CpOrigSystem and CpOrigSystemReference Indicates the instant messenger or social networking information of a customer contact. HZ_IMP_CONTACTPTS_T _Reference Fax FaxContactPreference ContactPointPurpose, EndDate, InstantMessagingAddress, and InstantMessengerType. CpOrigSystem, CpOrigSystemReference, and Objectkey. Indicates the fax of the group customer. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. CpOrigSystem and CpOrigSystemReference. Indicates the group customer preference about being contacted through fax. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. HZ_IMP_CONTACTPTS_T _Reference HZ_IMP_CONTACTPREFS _Reference Import Customer Information Using File-Based Import 1-63

72 Mobile MobileContactPreference Phone PrimaryPhoneContactPreference Indicates the mobile number of group customer. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, PhoneNumber, and PrimaryFlag. CpOrigSystem and CpOrigSystemReference. Indicates the group customer's preference about being contacted through mobile phone. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Indicates the primary phone number of the group customer. If the group has multiple phone numbers, one of the phone numbers is designated as the primary phone number. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. CpOrigSystem and CpOrigSystemReference. Indicates the group customer's preference about being contacted through phone. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. HZ_IMP_CONTACTPTS_T_ Reference HZ_IMP_CONTACTPREFS_ Reference HZ_IMP_CONTACTPTS_T_ Reference HZ_IMP_CONTACTPREFS_ Reference 1-64 Oracle Sales Cloud Using Customer Data Management

73 ContactPreference Address AddressContactPreference Indicates the of the group customer. ContactPointPurpose, Address, and StartDate. CpOrigSystem and CpOrigSystemReference. Indicates the group customer's preference about being contacted through . ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Indicates the address of a group customer. If the group has multiple addresses, one of the addresses is designated as the primary address. Address1, Address2, City, Country, County, State, and PostalCode. Reference attributes for location: LocationOrigSystem, LocationOrigSystemReference, and LocationId1. Reference attributes or party sites: SiteOrigSystem, SiteOrigSystemReference, and PartysiteId1. Indicates the group customer's preference about being contacted at the primary address. ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem, CpOrigSystemReference. HZ_IMP_CONTACTPTS_T_ Reference HZ_IMP_CONTACTPREFS _Reference HZ_IMP_LOCATIONS_T, HZ_IMP_PARTYSITES_T HZ_IMP_CONTACTPREFS _Reference Import Customer Information Using File-Based Import 1-65

74 AddressPurpose Indicates the purpose of a group customer's address. SiteUseType, EndDate, and StartDate. SiteOrigSystem and SiteOrigSystemReference. HZ_IMP_PARTYSITEUSES_T Importing Legal Entities Using File-Based Import Importing Legal Entities Using File-Based Import: Explained This topic explains how to prepare and import legal entities from an external data source into Oracle Sales Cloud using the File-Based Data Import feature. A legal entity is a recognized party with rights and responsibilities that is established by legislation. You create a legal entity for each registered company or other entity recognized in law for which you want to record assets, liabilities, expenses and income, pay transaction taxes, or perform intercompany trading. Within Oracle Sales Cloud, a legal entity is a representation of the legal unit of a customer. You must consider the following questions before importing legal entity information: How does your legacy or source system structure represent the legal entity information compared to how Oracle Sales Cloud represent the same data? How do your legacy or source system legal entities relate to business units, divisions, ledgers, balancing segments, consolidation rules, intercompany transactions, and payroll reporting? Do you have to configure values in Oracle Sales Cloud to map to your existing data values to the Legal Entity import object? Do you have to customize Oracle Sales Cloud to capture additional attributes that are critical to the way you do business? What import features are available for importing your business object? How do I verify my imported data? Comparing Business Object Structures Before you can import your legacy or source system legal entity data, you must first analyze the data and see how it corresponds with the legal entity object structure of Oracle Sales Cloud. You must understand how Oracle Sales Cloud represents the structure of the data for a legal entity. The legal entity structure of Oracle Sales Cloud is hierarchical. The organization profile is at the root level of the legal entity. The organization profile must exist before you can import lower-level components, such as , classification, additional name, primary address, and fax. These child entities can have other entities as their child entities. This hierarchical structure supports one-to-many relationships between the components that make up the legal entity. The following figure shows the legal entity and its child entities Oracle Sales Cloud Using Customer Data Management

75 The organization profile contains basic information about the legal entity, such as the legal entity name and party usage. For each legal entity, you can assign classifications, contacts, phone details, and additional names. The contact of the legal entity, in turn, includes other child entities that capture information about the contact, such as contact job, contact primary phone, contact primary address, and contact . Note All contact-related entities, such as primary phone or , include a child entity that captures the contact preference. For example, the Primary Phone Contact Preference entity captures the contact preference of the legal entity for the contact method primary phone. Comparing Business Object Data After you understand the structure of the data, then compare the detailed attribute values of your data with the Oracle Sales Cloud data. Each import object is a collection of attributes organized to help you when mapping your data to the Oracle Sales Cloud data and to support one-to-many relationships between the structural components that make up a legal entity. A good understanding of the import objects and attribute details is critical to preparing your import data. The attribute details are available for your reference in the Oracle Enterprise Repository. The reference guide files contain descriptions, default values, and validation for each of the attributes. The validation information includes the navigation to the task where you can define values in Oracle Sales Cloud. For example, if you have values in your data that correspond to a choice list, then the validation information for that attribute provides the task name in the Setup and Maintenance work area where you can define your values. Extensible Attributes If you have to extend the import object to import your legacy or source data, you must use Application Composer to design your object model extensions and to generate the required artifacts to register your extensions and make them available for importing. The corresponding import object is updated with the Import Customer Information Using File-Based Import 1-67

76 extensible attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes. Importing Legal Entities Using File-Based Data Import For the legal entity business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File- Based Data Import Setup and Maintenance task list includes the tasks required to configure the import objects, create source file mappings, and schedule the import activities. You submit file-based import activities for each import object. An import activity defines the instructions for processing the import data, including the source file, import mapping from the source file to the object and attribute, and the import schedule. When importing legal entity information, you first import the basic legal entity profile information and then the child entities for the legal entity. When importing child entities, you must provide the parent reference information for all parent levels for the entity. You must provide the PartyOrigSystem and PartyOrigSystemReference of the legal entity when importing contacts for the legal entity. PartyOrigSystem is the source system code that identifies the source of the information being imported. PartyOrigSystemReference is unique for each row of data within a single import, and is a combination of PartyOrigSystem and a unique reference. For example, you first import basic profile details, such as first name, last name, party type, and party usage. You then import contacts and contact information, such as phone, address, contact points, and fax for the legal entity. Note When importing contact information for a legal entity, you must provide the relationship reference information. This information is required because a contact can have multiple relationships with a legal entity. Verifying Your Imported Data You can view the list of import activities from the Manage Import Activities page. You can verify your imported data by clicking the Status column for your import activity. Alternatively, you can also navigate to the Define Legal Entities task list from the Setup and Maintenance work area to view the legal entities that you have imported. Legal Entity Import Objects: How They Work Together The Legal Entity import object allows you to import legal entities, their detailed information, and contacts related to the entity. This topic describes the Legal Entity import object. It topic introduces the following information: Target import object concepts Target objects for the Legal Entity import object Target import object attributes Target import object attribute reference guide files for evaluating and mapping source file data 1-68 Oracle Sales Cloud Using Customer Data Management

77 Legal Entity Target Import Object Concepts The Legal Entity import object imports legal entity information and its contacts. The Legal Entity import object is split into separate target import objects for organizing the individual attributes for the different aspects of the legal entity and its contact. Before you import data, you must understand how the target objects are related and what attributes are included in each object. This information helps you create the mapping between the source data in your import file and the target attributes in the application. The target import objects in the Legal Entity import object are grouped into information about the legal entity and the contact. The organization profile is the target import object containing attributes to import information about the legal entity. You can have multiple contacts associated with a legal entity. There are multiple target import objects that include attributes to import contacts and their related information. When updating an existing legal entity with more information, you must provide the parent reference information for the existing legal entity. When importing contacts or contact information for a legal entity, you must provide relationship reference information in addition to the parent reference. This information is required because a contact can have multiple relationships with the legal entity. When importing information about a contact, you must refer to the specific relationship you want to import information for. For example, you might want to import information about John Smith the employee or John Smith the board member. If you do not include the reference information for a contact relationship, then the import process creates a relationship. To update the information for an existing legal entity or to create a legal entity, you can import legal entity profile information, addresses, and contact points, such as phone and fax. The following target import objects are for creating and updating the corresponding legal entity information: OrganizationProfile, PrimaryAddress, PrimaryPhone, Url, Fax, Classification, AdditionalName, and ContactPersonProfile. To update or create a contact, use the following target import objects: ContactPersonProfile, ContactJob, ContactPrimaryAddress, Contact , ContactPrimaryPhone, ContactMobile, ContactInstantMessenger, and ContactFax. All contact-related entities, such as primary phone or , include a child entity that captures the contact preference. For example, the Primary Phone Contact Preference entity captures the contact preference of the legal entity for the contact method primary phone. Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference files contain descriptions, logic used for default values, and validation information for each of the attributes. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import Import Customer Information Using File-Based Import 1-69

78 activity using File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Note If any of the attributes you want to import do not have an equivalent target object attribute, then review the Application Composer Extensibility features for the object. Target Import Objects Attributes Resources To access the reference guide files for the legal entity target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository ( fusionappsoer.oracle.com). The following table lists the reference guide files that are available from the Documentation tab for the Legal Entity File-Based Data Import asset. Target Import Object Description Attribute Reference File Name of Oracle Enterprise Repository OrganizationProfile PrimaryPhone Fax Includes detailed legal entity information, such as, organization name and organization type. OrganizationSize, RegistrationType, LegalStatus, and RegistrationType. PartyOrigSystem, PartyOrigSystemReference, and PartyId. Indicates the primary phone number of the legal entity. If the legal entity has multiple phone numbers, one of the phone numbers is designated as the primary phone number. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. CpOrigSystem and CpOrigSystemReference. Indicates the fax of the legal entity. PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. CpOrigSystem and CpOrigSystemReference. HZ_IMP_PARTIES_T_Reference HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_CONTACTPTS_T_Reference 1-70 Oracle Sales Cloud Using Customer Data Management

79 Url AdditionalName Indicates the Url of the legal entity. ContactPointType, PrimaryFlag, Url, and WebType. CpOrigSystem and CpOrigSystemReference Indicates alternative name of a legal entity. Additional Name, Additional Name Type, and GlobalPreferredNameFlag. HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_ADDTNLPARTYNAMES_T_Reference Classification AdditionalNameOrigSystem and AdditionalNameOrigSystemReference. Incudes classification information for a legal entity. Classification allows you to categorize entities such as parties, projects, tasks, and orders as hierarchies. HZ_IMP_CLASSIFICS_T_Reference Classification code, Classification category, PrimaryFlag, and Rank. PrimaryAddress ClassificationOrigSystem and ClassificationOrigSystemReference. Indicates the primary address of a legal entity. If the contact has multiple addresses, one of the addresses is designated as the primary address. HZ_IMP_PARTYSITES_T_Reference Address1, Address2, City, Country, County, and State. Reference attributes for location: LocationOrigSystem, LocationOrigSystemReference, and LocationId1. Reference attributes for party sites: SiteOrigSystem, SiteOrigSystemReference, and PartysiteId1. Import Customer Information Using File-Based Import 1-71

80 ContactPersonProfile Contact ContactFax Includes detailed information, such as, person name, relationship type, and marital status, of a legal entity contact. Gender, MaritalStatus, PartyType, PartyUsageCode, PersonFirstName, and PersonLastName. PartyOrigSystem, PartyID, PartyOrigSystemReference, RelOrigSystem, RelOrigSystemReference, and RelationshipId. Indicates the of the legal entity contact. ContactPointPurpose, Address, and start date. CpOrigSystem and CpOrigSystemReference. Indicates the fax of the legal entity contact. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, and PhoneExtension. HZ_IMP_RELSHIPS_T_Reference HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_CONTACTPTS_T_Reference ContactInstantMessenger CpOrigSystem and CpOrigSystemReference. Indicates the instant messenger or social networking information of a legal entity contact. HZ_IMP_CONTACTPTS_T_Reference ContactPointPurpose, end date, InstantMessagingAddress, and InstantMessengerType. CpOrigSystem and CpOrigSystemReference Oracle Sales Cloud Using Customer Data Management

81 ContactJob ContactMobile ContactPrimaryAddress Includes job information of a legal entity contact. Comments, ContactNumber, Department, DepartmentCode, and JobTitleCode. RelOrigSystem, RelationshipID, and RelOrigSystemReference. Indicates the mobile number of a legal entity's contact. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, PhoneNumber, and PrimaryFlag. CpOrigSystem and CpOrigSystemReference. Indicates the primary address of a legal entity contact. If the contact has multiple addresses, one of the addresses is designated as the primary address. Address1, Address2, City, Country, County, and State. Reference attributes for location: LocationOrigSystem, LocationOrigSystemReference, and LocationId1. Reference attributes for party sites: SiteOrigSystem, SiteOrigSystemReference, and PartysiteId1. HZ_IMP_CONTACTS_T_Reference HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_PARTYSITES_T_Reference Import Customer Information Using File-Based Import 1-73

82 ContactPrimaryPhone ContactAdditionalName Indicates the primary phone number of the legal entity contact. If the legal entity has multiple phone numbers, one of the phone numbers is designated as the primary phone number. ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, PhoneNumber, and PrimaryFlag. CpOrigSystem and CpOrigSystemReference. Indicates alternative name of a legal entity contact. NameId, PersonFirstName, PersonLastName, and PersonTitle. HZ_IMP_CONTACTPTS_T_Reference HZ_IMP_ADDTNLPARTYNAMES_T_Reference PrimaryPhoneContactPreference AdditionalNameOrigSystem and AdditionalNameOrigSystemReference. Indicates the legal entity's preference about being contacted through phone. HZ_IMP_CONTACTPREFS_Reference MobileContactPreference PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Indicates the legal entity's preference about being contacted through mobile. PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. HZ_IMP_CONTACTPREFS_Reference 1-74 Oracle Sales Cloud Using Customer Data Management

83 FaxContactPreference ContactPreference Indicates the legal entity's preference about being contacted through fax. PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Indicates the legal entity's preference about being contacted through . PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. HZ_IMP_CONTACTPREFS_Reference HZ_IMP_CONTACTPREFS_Reference CpOrigSystem and CpOrigSystemReference. ContactPrimaryAddressContactPreference Indicates the legal entity contact's preference about being contacted at the primary address. HZ_IMP_CONTACTPREFS_Reference PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. ContactPrimaryPhoneContactPreference Indicates the legal entity contact's preference about being contacted through the primary phone number. HZ_IMP_CONTACTPREFS_Reference PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Import Customer Information Using File-Based Import 1-75

84 PrimaryAddressContactPreference PrimaryPhoneContactPreference Indicates the legal entity's preference about being contacted at the primary address. PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. Indicates the legal entity's preference about being contacted through the primary phone number. PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. CpOrigSystem and CpOrigSystemReference. HZ_IMP_CONTACTPREFS_Reference HZ_IMP_CONTACTPREFS_Reference Importing Resource Teams Using File-Based Import Importing Resource Teams Using File-Based Import: Explained This topic explains how to prepare and import resource team data from an external data source into Oracle Sales Cloud using the File-Based Data Import feature. A resource team is a temporary group of resources that is formed to work on work objects. A resource team may contain a resource organization or resources or both. A resource team cannot be hierarchically structured and is not intended to implement an organization. You enter your resource team information using the Setup and Maintenance work area, Manage Resource Teams task, or you can import data to create new or update the existing resource teams. Consider the following questions when importing your data: How does your legacy system or source system represent the resource team compared to how Oracle Sales Cloud represent the same data? Do you have to configure values in Oracle Sales Cloud to map to your data values? Do you have to customize Oracle Sales Cloud to capture additional attributes that are critical to the way you do business? 1-76 Oracle Sales Cloud Using Customer Data Management

85 What import features are available for importing your business object? How do you verify your imported data? Comparing Business Object Structures You must understand how your resource team data corresponds with the data in Oracle Sales Cloud in order to be able to map your legacy data to the data needed by Oracle Sales Cloud. First, you must understand how Oracle Sales Cloud represent the structure of the data for a resource team. In Oracle Sales Cloud, one table stores the resource team definition and other tables optionally store profile details for that resource team. Profile details for a resource include information about a resource team's organization and team memberships. Import Objects for the Resource Team To facilitate the import of resource teams, Oracle Sales Cloud incorporate the structure of the resource team into import objects. The import object for the resource team is Resource Team. Comparing Business Object Data Each import object is a collection of attributes that helps to map your data to the Oracle Sales Cloud data and to support one-to-many relationships between the structural components that make up the resource team. A good understanding of the attribute details of the import objects is critical to preparing your import data. The reference guide files contain descriptions, logic used to choose default values, and validation information for each import object attribute. The validation information includes the navigation to the task where you can define values in Oracle Sales Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Sales Cloud, then the validation information for that attribute provides the task name in the Setup and Maintenance work area where you can define your values. For additional information, including a list of reference guide file names and locations that you need to complete this task, see the following table. Import Object Resource Team Related Import Object Topic Resource Team Import Objects: How They Work Together Hint: You can use the keyword importing resource teams to search for related topics in Oracle Sales Cloud help. Extensible Attributes If you need to extend the Oracle Sales Cloud object to import your legacy or source data, you must use Application Composer to design your object model extensions and to generate the required artifacts to register your extensions Import Customer Information Using File-Based Import 1-77

86 and make them available for importing. The corresponding import object is updated with the extensible attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes. Importing Resource Teams Using File-Based Data Import For the resource team business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. When creating a new contact, you import the Resource Team object. You must be assigned the Master Data Management Administrator job role to access and submit the import activities for resource teams. Verifying Your Imported Data Oracle Sales Cloud provide File-Based Import activity reports, which can be used to verify imported data. Users with the Master Data Management Administrator job role can also navigate to the Manage Resource Teams work area to view the imported resource teams. Resource Team Import Objects: How They Work Together This topic describes the Resource Team import object. You use two main import objects, ResourceTeam and ResourceTeamUsage, when you submit a file-based import activity to import resource team information. This topic introduces the following: Target import object concepts Target objects for the Resource Team import object Target import object attributes Target object attribute reference guide files Target Import Object Concepts The Resource Team import object is used to import resource teams and information to create or update associated organizations or persons. The Resource Team import object is split into separate target import objects for organizing the individual attributes of the different aspects of the resource team and the resource team's usage. To map the source data in your import file to the 1-78 Oracle Sales Cloud Using Customer Data Management

87 target attributes in Oracle Sales Cloud, you must understand how the target objects are related and what attributes are included in each target object. Resource Team Target Import Objects The target import objects in the Resource Team import object are generally grouped into information about the resource team and its usage. The ResourceTeam target import object contains information that identifies the resource team, such as the team's name, ID, active dates, and so on. The ResourceTeamUsage target import object contains information that captures the usage of the resource team. To import or update a resource team, use the ResourceTeam target import object. To import or update a resource team's usage, use the ResourceTeamUsage target import object. Target Import Objects Attributes You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference guide file includes attribute descriptions, default values, and validations performed by the import process. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required. To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area. Note If any of the attributes you want to import do not have an equivalent target object attribute, then review the Application Composer Extensibility features for the object. Target Import Objects Attributes Resources To access the reference guide files for the resource team's target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository ( fusionappsoer.oracle.com). The following table lists the reference guide files that are available from the Documentation tab for the Resource Team File-Based Data Import asset. Target Import Object Description Reference Guide File Names ResourceTeam Captured information that identifies a resource team. TeamId, TeamName, TeamDescription, and Language. HZ_IMP_TEAMS _Reference Import Customer Information Using File-Based Import 1-79

88 ResourceTeamUsage Contains information that indicates the usage of the resource team. RequestId, TeamUsageId, TeamId, and Usage. HZ_IMP_TEAM_USAGES_Reference 1-80 Oracle Sales Cloud Using Customer Data Management

89 2 Import Customer Information Using Data Import Overview of Data Import Data Import Objects: Explained Import objects are business entities that can be imported into the registry, for example, competitors, partners or resource teams. When you create a data import batch you should choose which business entity, or object, you are importing from the batch into the registry. For example, if you are responsible for resource management, you might want to import objects such as employee resource and resource team. The import process flow will change according to which object you have selected. There are two import process flows for the following sets of objects: 1. Customer, reference, competitor, and custom party. 2. Employee resource, resource team, partner, and partner contact. Customer, Reference, Competitor, and Custom Party When you select these objects you will receive the option to check for duplicates within the import batch before the import, and the option to check for duplicates between the import batch and the registry before import. You will also be able to choose to preview data before it is imported, specify if addresses will be cleansed before import, and set how many errors you will allow before the import is terminated. Employee Resource, Resource Team, Partner, and Partner Contact If you choose to import these objects you will not be able to deduplicate the batch or registry data. However, you will be able to choose to preview data before it is imported, specify if addresses will be cleansed before import, and set how many errors you will allow before the import is terminated. Import Customer Information Using Data Import 2-1

90 Updating Customer Data Through Import: Explained Oracle Fusion Applications provides two utilities to import data, File-Based Import and Data Import. You can import data to add customer data or update existing data. This topic discusses how you can update exiting customer data through import. The Oracle Fusion object structure is hierarchical to support one-to-many relationships between the components that make up the customer. At the root level we have the basic profile information, and at lower levels we have additional information. For example, the basic information for a customer includes customer name, party usage, and party type. The lower-level components include additional information components such as classifications, contacts, and sales account profiles. To import contact information for a customer, you must provide the relationship reference information. This is required because a customer can have multiple relationships with a customer. For example, you first import basic profile details such as first name, last name, party type, and party usage. You then import contacts and contact information, such as phone, address, contact points, and fax, for the customer. Updating Existing Information You can edit existing customer information through import, by providing the appropriate parent reference information. You can update the following entities through data import: Relationships: You can delete, end date, and update the primary status of relationships through import. When you delete a contact relationship, the corresponding contact points and party sites is end dated. Classifications: You can delete, end date, and update the primary status of classifications through import. Contact Points: You can delete, end date, and update the primary status of contact points through import. Additional Names and Identifiers: You can delete and update the primary status of additional names and identifiers through import. Party Sites: You can delete, end date, and update the primary status of party sites through import. Party Site Uses: You can delete, end date, and update the primary status of party site usages through import. When you delete a party site usage, the import process makes related changes in the account site usage. Contact Preferences: You can end date a contact preference through import. Addresses and Address Purposes: You can delete, end date, and update addresses and address purposes except for a sell-to address and its purpose. The import process performs a data cleanup process on all update data, after loading, to ensure data validity. For example, the process assigns the first entity 2-2 Oracle Sales Cloud Using Customer Data Management

91 in the list as the primary entity, whenever a primary entity is end dated because of an update. Deleting Parties You can delete some party types through import. You can delete Customer, Contacts, and Groups. You can delete parties, only if: The party has an unconditional party usage, such as Sales Account, Customer Contact, Organization Contact, Sales Contact, Group Member, Group Contact, and Related Person. You can define other unconditional party usages depending on your requirements. Additionally, the party should have used a conditional party usage at any time in the past. The party is the root node of an active hierarchy version. You can also delete the unconditional party usages of a party through import. You can delete only unconditional party usages, such as Contact, Sales Prospect, External Legal Entity, and Party of Interest. You cannot delete conditional party usages, because conditional party usages are assigned when a relationship is created between two parties. To delete conditional party usages, you must delete the relationship. The import process deletes a party usage when the party usage is specified. If you do not specify a party usage, the import process deletes the party and all party usages of the party. The import process also deletes some child entities for a party, if the deletion of child entity does not result in data integrity issues. The following child entities are deleted when a party is deleted: Sales account profile Relationship Classification code assignment Party usages Enter Import Process Information Using Data Quality Services During Data Import: Explained Data Quality Services help you ensure the quality of data being imported into the registry. You can select how to use the services before importing data into the registry. The data quality services are: Batch Deduplication: Batch deduplication allows you to define deduplication within the data being loaded. Registry Deduplication: Registry deduplication allows you to define deduplication of the data being loaded against the records that already exist in the registry. Import Customer Information Using Data Import 2-3

92 Import to Registry options: Import to Registry options allow you to define the import process mode, data cleansing, and geography validation. You can configure a data import or file import process to invoke these services before importing data into the database. Defining Data Quality Services for File-Based Import The file-based import process allows you to define process criteria, file mapping, and import schedule for importing external files containing business objects into staging tables. You can define Registry deduplication options in the file-based import process. You cannot define the other Data Quality Services, such as Batch Deduplication and Import to Registry options, for a file-based import activity during the file-based import process. However, an import activity can be paused and sent for administrator review after preprocessing and before importing the data. The administrator such as a data steward can then review the import process and configure data quality services. Import activities are paused and sent for administrator review if the HZ_IMP_PAUSE_FILE_IMPORT profile option is set to Yes in the Manage Import Profile Options page. If the profile option is set to Yes, all submitted import activities are sent for administrator review and appear in the Data Import Batches Overview page. The administrator can then review and edit import activity details and options. Based on the review, the administrator can decide to approve and schedule the import batch or reject the import batch. Defining Data Quality Services for Data Import You can configure data quality services for data import in the Define Import pages. For both the deduplication methods, you can select a match configuration to identify duplicates and also specify the action to perform on the duplicate records. In the Define Import: Import to Registry page, you can specify whether to run the import process in preview mode, whether to cleanse data before import, and whether to perform geography validation of data before import. You can also configure geography validation for data import at the site level using the HZ_IMP_DEFAULT_GEO_VALID_ADDRESS profile option in the Manage Import Profile Options page. The addresses are validated if the profile option is set to Yes in the Manage Import Profile Options page. The addresses are validated against the master reference geography data, according to the geography-based address validation settings for each country. The addresses with validation errors are not imported. Defining the Import Process for Customers and Consumers: Points to Consider In Oracle Sales Cloud, you can use File-Based Import to import data directly from a CSV or XML file. In addition, you can use the Data Import dashboard to monitor the import job and view reports and statistics. You can choose to pause a File-Import batch, and use Data Import work area to configure data quality services, monitor import jobs, view errors, and view batch statistics. Import activities are paused if the HZ_IMP_PAUSE_FILE_IMPORT profile option is set to Yes in the Manage Import Profile Options page. If the profile option is set to 2-4 Oracle Sales Cloud Using Customer Data Management

93 Yes, all submitted import activities are sent for administrator review and appear in the Data Import Batches Overview page. Note In on-premise deployment, you can use Data Import to import data from interface tables once the tables are populated by an external process. However, you cannot use Data Import in a Cloud deployment, because you cannot populate interface tables using an external process in a Cloud deployment. Before importing data into the registry, you need to decide if you want to use the data quality services and if so, how you want to configure the data quality services. The data quality services are: Batch deduplication Registry deduplication Import to registry options Batch Deduplication Within the batch deduplication page you can decide if you want to identify and resolve duplicates within the batch that you are importing from the interface tables. If you want to check for duplicates you need to choose what match configuration rule you want to use to identify duplicates for each entity. Then you need to specify what action will be taken on the persons, organizations, and address duplicates found within the batch. Your specified actions will be performed on the batch before the data is imported into the registry. Registry Deduplication Similar to batch deduplication, registry deduplication identifies duplicates between the data in the batch and the data in the registry before the data is imported into the registry. If you want to check for duplicates you need to choose what match configuration rule you want to use to identify duplicates for each entity. Then you need to specify what action will be taken on the persons, organizations, and address duplicates found in the registry deduplication check. Your specified actions will be performed when you import the batch into the registry. Import to Registry Options When defining an import process you can decide whether to run the import process in preview mode, or you can choose to load the data directly into the registry without previewing the data. You can also choose to cleanse addresses prior to import, validate addresses in an import batch against geography data, and define an error limit for the batch. Import Process Mode You can choose to run the import batch in preview mode, or you can skip the preview and load the data directly into the registry. Import Customer Information Using Data Import 2-5

94 If you select to run the batch in preview mode you will be able to review information about the level of duplicates or incorrect addresses in the batch data before the data is actually imported. You will also be able to preview how many records will be created and how many records will be updated for each entity. You can then continue to import the batch, or you can amend the match configuration rules and actions to be taken on the identified duplicates and then rerun the batch to review the data again. If you do not want to review the batch data before it is imported into the registry, then you can choose to skip the preview and allow the data to be loaded into the registry as soon as preprocessing is complete. You may prefer not to preview the batch data if the data source is frequently used. Note The Define Import: Import to Registry page is the only place that you can specify if you want to run the batch in preview mode. Once the option to skip the preview mode is selected, and you submit the batch for processing, you will not be able to review the batch data before it is imported. Cleanse Addresses You can choose to validate the addresses in the interface tables before importing them into the registry. The addresses are validated using an integrated third party service that verifies addresses and corrects them if they are incorrect. Geography Validation You can choose to validate the addresses in an import batch against geography data before importing them into registry. The addresses are validated against the master reference geography data, according to the geography-based address validation settings for each country. The addresses with validation errors are not imported. However, Geography Name Referencing is run on all imported addresses regardless of this profile option setting. Error Handling Limit You can define how many process errors can be generated by the import batch process before the process terminates automatically. Error reports are generated by the application for you to review. Defining the Import Process for Customers and Consumers: Worked Example This example demonstrates how to create an import batch, and how to define the import process data quality services you want to use on the data prior to completing the import. Note Once an import is completed, the data is loaded into the registry. Create an import batch containing customer and consumer objects, load the import data into the interface tables, and configure the data import process so 2-6 Oracle Sales Cloud Using Customer Data Management

95 that you can view the batch in preview mode to check that all duplicate data are removed. Creating an import batch 1. On the Data Import Batches Overview page, click on the Create Data Import Batch task located in the task pane. 2. On the Create Data Import Batch page, complete the fields as shown in this table: Field Batch Name Source System Object Value Estimated Number of Records 300 Batch Description Customer Import Batch Comma separated values Customer and Consumer Import of customer data 3. Click Save and Close 4. After creating the import batch, load your data into the interface tables using a standard ETL tool. Defining the Data Import Process: Batch Deduplication You want to check the batch for address, organization, and person duplicates; you also want to remove all of these duplicates from the batch. 1. On the Data Import Batches Overview page, highlight the Batch Name, but do not click on the Batch ID URL. 2. Click Actions and then click Import. 3. On the Define Import: Batch Deduplication page, select the Check for duplicates within the batch before import. 4. Complete the fields in the Select match configuration to determine duplicates within the import batch section, as shown in this table: Field Addresses Organizations Persons Value Batch Location Basic Duplicate Identification Batch Organization Basic Duplicate Identification Batch Person Basic Duplicate Identification 5. Complete the fields in the Override Default Actions section, as shown in this table: Field Select Action for Persons and Organizations Value Remove all duplicates Import Customer Information Using Data Import 2-7

96 Select Action for Addresses Remove all duplicates 6. Click Next. Defining the Data Import Process: Registry Deduplication You want to check for address, organization, and person duplicates between the import batch and the registry; you also do not want to import duplicate records. 1. On the Define Import: Registry Deduplication page, select the Check for duplicates between the import batch and the registry before import. 2. Complete the fields in the Select match configuration to determine duplicates within the import batch section, as shown in this table: Field Addresses Organizations Persons Value Batch Location Basic Duplicate Identification Batch Organization Basic Duplicate Identification Batch Person Basic Duplicate Identification 3. Complete the fields in the Override Default Actions section, as shown in this table: Field Select Action for Persons and Organizations Select Action for Addresses Value Do not import duplicate records Do not import duplicate records 4. Click Next. Defining the Data Import Process: Import to Registry You want to configure the data import process so that you can view the batch in preview mode, enabling you to review the data after preprocessing. You want to cleanse addresses before they are imported, and specify an error limit for the batch. You also want to validate all addresses in the import batch against geography data. This validates all incoming addresses as per the geography structure and validation level setup in Manage Geographies task. The addresses that are reported as Error during validation are not imported. 1. On the Define Import: Import to Registry page, select Run the batch in preview mode. 2. Select Cleanse addresses before import. 3. Select Validate address against geography. 4. In the Error Limit field, enter Click Submit. 2-8 Oracle Sales Cloud Using Customer Data Management

97 FAQs for Enter Import Process Information Can I redefine the data import process for an already imported batch and reimport it? Yes. If the data is still available in the interface tables and the batch status is Preimport Completed, Completed with Errors, Error, or Terminated when Error Limit Reached, then you can redefine the data import process and reimport the batch. However, once a batch has been successfully imported then you will not able to reimport the batch, even if the data is present in the interface tables. Can I try and import a batch again? Yes. You can reimport a batch to correct validation errors if the import process status is either Preimport Completed, Completed With Errors, Error, or Terminated When Error Limit Reached. FAQs for View Error Reports and Output Files How can I view the errors that occurred during preimport processing? You can view any errors that occurred after submitting the batch for import by selecting the batch in the data import batches Overview page, and then click Report. Why did I receive a message that the data enrichment process was declined? FAQs for Purge Batch The customer data quality application may be unavailable, or you may not have the necessary licenses for the data quality application. What happens if I purge a data import batch? You permanently remove all records in the batch from the import interface tables. You should purge batches after the batch has been imported successfully and you are sure that the data in the interface tables is no longer required. Import Customer Information Using Data Import 2-9

98 Purging the interface tables improves import performance. To archive imported data, you should copy the data to a set of custom tables. Why can't I purge a data import batch? Data import batches cannot be purged when they have a status of Processing. Purging a batch purges the batch data in the interface tables and so cannot be carried out while the batch is importing the data from the interface tables into the registry. Conduct What-If Analysis and Submit Performing What-If Analysis on Data Import Batches: Worked Example This example demonstrates how to perform What-If analysis on a data import batch that has been processed and has completed with a status of pre-import completed. The match configuration is redefined and the import process is resubmitted. The batch deduplication actions are then amended, and the batch import is completed. The following table summarizes key decisions for this scenario. Decisions to Consider Do you want to redefine batch deduplication match configuration? Do you want to redefine registry deduplication match configuration? What actions do you want to take on Persons, Organizations, and Addresses duplicates? In This Example Yes, a different match configuration is selected for the organizations entity. Yes, a different match configuration is selected for the persons entity. Within registry deduplication, choose Do not import duplicate records for Persons and Organizations. Within registry deduplication, choose Import duplicate records for Addresses. Prerequisites 1. The data import batch has been created. 2. The data is uploaded into the interface tables. 3. The batch is imported and has completed with a status of pre-import completed. Viewing the What-If Analysis 1. On the Data Import Batches Overview page, click on the batch ID URL. 2. On the Edit Data Import Batch page, review the summary and import process performance information. Click Import Details to open the What- If analysis page Oracle Sales Cloud Using Customer Data Management

99 3. On the Import Process Details page, click the Batch Deduplication tab. Check that you are satisfied with the batch deduplication results. 4. On the Import Process Details page, click the Registry Deduplication tab. Check that you are satisfied with the registry deduplication results. 5. On the Import Process Details page, click the Address Cleansing tab. Check that you are satisfied with the address cleansing results. Redefining the Match Configuration and Resubmitting the Import Process The results of the batch and registry deduplication are not as expected and so the match configurations need to be redefined. 1. On the Import Process Details page, click Cancel. 2. On the Data Import Batches Overview page, click on the batch name. Click Actions and then click Import. 3. On the Define Import: Batch Deduplication page, choose a different match configuration for the organizations entity. Click Next. 4. On the Define Import: Registry Deduplication page, choose a different match configuration for the persons entity. Click Next. 5. On the Define Import: Import Registry page, click Submit Changing the Action for Duplicates within the What-If Analysis You want to view the What-If analysis for the new match configurations that you selected for the batch. 1. On the Data Import Batches Overview page, click on the batch ID URL. 2. On the Edit Data Import Batch page, review the summary and import process performance information. Click Import Details to open the What- If analysis page. 3. The new match configurations have produced satisfactory results, but you would like to change the actions that will be carried out on the duplicates. On the Import Process Details page, click the Registry Deduplication tab. 4. For the Persons and Organizations duplicates, choose Do not import duplicate records from the choice list. 5. For the possible duplicates for Addresses, choose Import duplicate records from the choice list. 6. Click Complete Import. FAQs for View Batch Detail and Statistics Why can't I view the import process details? The import process details are only available when you have selected to run the batch in preview mode, and you have submitted the batch for import. Import Customer Information Using Data Import 2-11

100 2-12 Oracle Sales Cloud Using Customer Data Management

101 3 Enriching Sales Cloud Data Using Oracle Social Data and Insight Cloud Service Enriching Account and Account Contact Data: Explained Data enrichment improves the quality of your existing account or account contact data, and also enriches that data with additional information. You use the Oracle Social Data and Insight Cloud service to enrich your account and contact data in Oracle Sales Cloud. In order to enrich account data, you must: 1. Export the data you want to enrich from Oracle Sales Cloud to a CSV file. 2. Enrich the exported data using the Oracle Social Data and Insight Cloud service. 3. Download the enriched data file from Oracle Social Data and Insight Cloud service. 4. Import the enriched data file into Oracle Sales Cloud. Exporting Data from Oracle Sales Cloud You can export your account or account contact data from Oracle Sales Cloud using the Schedule Export Processes task. The export process provides two predefined objects, one each for exporting account and account contact data. While exporting data, you must choose the Organization for Data Cloud Enrichment object to export account data and the Person for Data Cloud Enrichment object to export account contact data. You can also configure the export objects to select the object attributes that you want to enrich. Enriching Data in the Oracle Social Data and Insight Cloud Service You can use the Enrich Data functionality of the Oracle Social Data and Insight Cloud service to enrich account or account contact data. To enrich data, select the CSV file exported from Oracle Sales Cloud in the Enrich Data Records window of the Oracle Social Data and Insight Cloud service. You must select the CRM Enriching Sales Cloud Data Using Oracle Social Data and Insight Cloud Service 3-1

102 template during enrichment, so that the enriched file can be downloaded in Oracle Sales Cloud. After enrichment is complete, a CSV file with the enriched data is available for download from the Jobs List. Importing Enriched Data into Oracle Sales Cloud To import the account or account contact data, import the CSV file you downloaded from Oracle Social Data and Insight Cloud service into Oracle Sales Cloud using the file-based import functionality. You create an import activity, enter the appropriate import details, provide the file mapping, and schedule the import to import the data from the CSV file into staging tables. Import processing is subject to the settings defined for the import object, mapping, and import activity. Import objects represent the application and attribute information for business objects that can be imported using external source files. While specifying the import object, you choose the Account to import account data and the Contact to import account contact data. Import mapping enables you to predefine a mapping between the columns provided in a source file and the attributes pertaining to the objects being imported. Oracle Sales Cloud provides seeded mappings to import account data or account contact data from Oracle Social Data and Insight Cloud service. You must select Seeded Data to view the available seeded mappings. While specifying the import mapping, you choose Data Cloud Account Import to import account data and Data Cloud Contact Import to import account contact data. Oracle Sales Cloud would then automatically map the data in the CSV file to object attributes. Importing New Records into Oracle Sales Cloud from Oracle Social Data and Insight Cloud Service: Explained Oracle Social Data and Insight Cloud service lets you directly import enriched records to your sales cloud instance. You can import accounts or account contacts from Oracle Social Data and Insight Cloud service into your sales cloud instance. In order to import data from Oracle Social Data and Insight Cloud service to Oracle Sales Cloud, you must: 1. Export the accounts or account contacts from Oracle Social Data and Insight Cloud service. 2. Import the CSV file into Oracle Sales Cloud. Before importing account contacts, you must ensure that the accounts related to the contacts exist in Oracle Sales Cloud. Exporting Accounts or Account Contacts from Oracle Social Data and Insight Cloud Service Before you can export account or account contact data, you must search for the data in the Oracle Social Data and Insight Cloud service, and select the data you 3-2 Oracle Sales Cloud Using Customer Data Management

103 want to export. You can search for accounts and account contacts from the Search window. You can also export all available accounts or account contacts. After searching for the records you want to export, click Export to export the data. You must select a template to specify the structure of the exported CSV file. You must select Use CRM Template so that the exported file can be imported in Oracle Sales Cloud. Importing Accounts or Account Contacts into Oracle Sales Cloud To import the account or account contact data, import the CSV file you downloaded from Oracle Social Data and Insight Cloud service into Oracle Sales Cloud using the file-based import functionality. You create an import activity, enter the appropriate import details, provide the file mapping, and schedule the import to import the data from the CSV file into staging tables. Import processing is subject to the settings defined for the import object, mapping, and import activity. Import objects represent the application and attribute information for business objects that can be imported using external source files. While specifying the import object, you choose Account to import account data and the Contact to import account contact data. Import mapping enables you to predefine a mapping between the columns provided in a source file and the attributes pertaining to the objects being imported. Oracle Sales Cloud provides seeded mappings to import account data or account contact data from Oracle Social Data and Insight Cloud service. You must select Seeded Data to view the available seeded mappings. While specifying the import mapping, you choose Data Cloud Account Import to import account data and Data Cloud Contact Import to import account contact data. Oracle Sales Cloud would then automatically map the data in the CSV file to object attributes. Enriching Sales Cloud Data Using Oracle Social Data and Insight Cloud Service 3-3

104 3-4 Oracle Sales Cloud Using Customer Data Management

105 4 Manage Customer Data Quality Overview of Data Quality Management Data Quality Management Components: How They Fit Together Data quality configurations, data quality management during import process, duplicate identification, duplicate resolution, and data cleansing processes constitute the data quality management business flow that is used to manage the quality of the incoming and existing Oracle Sales Cloud data. Data Quality Configurations Data quality configurations include the configurations required to enable data quality management processes such as data quality matching and cleansing operations. These operations include real-time and batch matching and cleansing of incoming and existing data. The data quality services invoke appropriate services of the embedded data quality engine based on the data quality configurations. Data Quality Management During Import Process Lets you: Define deduplication within the data being loaded. You can select a match configuration to identify duplicates and also specify the action to perform on the duplicate records. Define deduplication of the data being loaded against the records that already exist in the Oracle Sales Cloud architecture registry. You can select a match configuration to identify duplicates and also specify the action to perform on the duplicate records. Duplicate Identification Lets you identify potential duplicates during data entry, data integration, or among records already in the application. Duplicate Resolution Lets you resolve duplicates either by directly merging them or by creating duplicate resolution request such as merge or link that can be verified, approved or rejected, and processed at a later date. Manage Customer Data Quality 4-1

106 Data Cleansing The need to cleanse registry data arises owing to data decay over time and the need to resolve inherited issues from consolidated data in the registry. For example, postal codes and city boundaries change over time and require regular address cleansing to ensure that the addresses in the registry are correct, validated, and standardized at all times. Batch cleansing lets you cleanse data that already exists in the registry and ensures data accuracy over time, avoiding data decay. Besides, incoming data may originate from multiple sources with each source system following different data storage formats and norms. Real-time data cleansing ensures that the incoming data from source systems follows the same storage convention as the target system to achieve consistency in representation of information such as addresses. Party Information Management Party information management is done using the Party Center functionality. This functionality allows for a comprehensive management of party information such as profile, usage assignments, linked parties, contacts, accounts, tasks, interactions, and notes. A party is a physical entity, such as a person or organization, that the deploying company has an interest in tracking. Cleanse Customer Information Scheduling a Data Cleansing Process: Points to Consider You can schedule a data cleansing process whenever you want. However, since such a process can be time consuming, ideally you would like to schedule it at a time when sufficient system resources are available. Before scheduling a data cleansing process, you should consider one or all of the following points. The duration required to complete the process Amount of free system resources Process dependencies The Duration Required to Complete the Process The duration required to complete the process is based on the record volume, cleansing complexity, and hardware characteristics. So for each batch scheduled, calculate the possible duration taking into account these three factors and available benchmark. Amount of Free System Resources Scan through the batch and environment statistics to make more realistic estimates of the system performance based on recent data. Also scan through the various objects lists to find out a suitable time when enough system resources 4-2 Oracle Sales Cloud Using Customer Data Management

107 would be free to devote to the process. You can gather this from the individual high-level object list which captures the recent batch history. Process Dependencies Take process dependencies into account, for example, consider whether another process is waiting for the results of the batch cleansing process. Creating Address Cleansing Batches: Points to Consider You have the following options while creating an address cleansing batch: Create the address cleansing batch for a single run Create the address cleansing batch to be run periodically Create the address cleansing batch from a copy of an existing address cleansing batch Consider the following points to determine which batch creation option best suites your address cleansing needs. Address Cleansing Batch for a Single Run Create an address cleansing batch for a single run only if scheduling it to be run periodically is not required or practical or will simply waste valuable computing power. Address Cleansing Batch to be Run Periodically Create an address cleansing batch to be run periodically to remove the need for creating a new batch definition every time addresses in the registry require validation and standardization. You can define the batch selection criteria and address cleansing mode once and schedule the batch to run at a specific interval, such as daily, every night at 9 PM, or weekly, every Sunday at 10 PM. This functionality allows you to automate the execution of the registry address cleansing, a tasks that is mostly ongoing and repetitive. Using the Copy of an Existing Address Cleansing Batch Use the copy of an existing address cleansing batch to quickly create another address cleansing batch. Although the new batch inherits details such as batch selection criteria and address cleansing mode, you can edit them and also schedule the new batch to run just once or periodically. Accept Data Cleansing Process Results Accepting Data Cleansing Results: Critical Choices You can accept or reject the results of a batch data cleansing process run in simulated mode either in its entirety or selectively as follows: Accept or reject the data cleansing process results for an entire batch Manage Customer Data Quality 4-3

108 Note Accept or reject the data cleansing process results selectively by country Accept or reject data cleansing process results selectively by address record These choices are not available if you submit a batch for cleansing in the automated cleansing mode because in this mode the cleansed data is automatically saved to the database. Accept or Reject the Data Cleansing Process Results for an Entire Batch Accept the entire data cleansing process results for a batch only if you are confident that the data cleansing has happened accurately. If you feel that the results are not reliable and accepting the cleansed data might have any unwanted impact on the quality of the data, reject the results. Accept Or Reject the Data Cleansing Process Results Selectively by Country Depending on the quality of the data and coverage or maturity of the postal directory for individual country or region, the results may vary from country to country. From among the following approaches, select the one that best suits your requirements: If you feel that the percentage of errors is high and that results for all countries are not acceptable, accept data only for countries with acceptable cleansing results. If you feel that the percentage of errors is very high for a country, reject the entire data for that country. Accept or Reject Data Cleansing Process Results Selectively by Address Record Accept or reject cleansing results for each individual address based on the cleansing status and business rules and policies. Enter Data Cleansing Batch Information and Submit Specifying Selection Criteria for a Data Cleansing Batch: Worked Example Batch cleansing lets you validate and cleanse address data that already exist in the registry. The need to cleanse registry data arises owing to data decay over time and the need to resolve historic entering of errors in the database. For example, postal codes and city boundaries change over time and require regular address cleansing to ensure that the addresses in the registry are correct, validated, and standardized at all times. Besides, historic incoming address data may have originated from multiple sources with each source system following different data storage formats and norms and the addresses might not have been cleansed during the import or consolidation process. Batch cleansing of data ensures data accuracy over time, reducing data decay. 4-4 Oracle Sales Cloud Using Customer Data Management

109 Use the Selection Criteria table on the Create Data Cleansing Batch page to specify selection criteria to create data cleansing batches of the records. The selection criteria are treated as a query. Populate the Selection Criteria Table Populate the selection criteria columns: Object, Attribute, Operator, and Value. Each row of the selection criteria table creates a selection criterion. Multiple selection criteria are joined by an AND condition. 1. Navigate to the Create Data Cleansing Batch page. 2. Enter the following sample information in the Selection Criteria table. Object Attribute Operator Value Location Address1 Contains 500 Oracle Location Country Equal to US 3. Click Submit. FAQs for Cleanse Customer Information What's a Data Cleansing Batch? A batch of records built based on a set of selection criteria to cleanse data that already exists in the registry. The need to cleanse the registry data arises owing to data decay over time and the need to resolve inherited issues from consolidated data in the registry. For example, postal codes and city boundaries change over time and require regular address cleansing to ensure that the addresses in the registry are correct, validated, and standardized at all times. Besides, historic incoming address data may have originated from multiple sources with each source system following different data storage formats and norms and the addresses might not have been cleansed during the import or consolidation process. Can I edit and resubmit a data cleansing batch? No. But you can resubmit the data as part of another new batch. You can also edit fields, such as description, in a previously submitted batch. What's the difference between Automated Cleansing and Simulated Cleansing? Automated Cleansing mode does not require any user action. The data in a batch submitted in this mode is cleansed and automatically saved to the database. Manage Customer Data Quality 4-5

110 When you submit a data cleansing batch in the Simulated Cleansing mode, you get a chance to view the output of the batch cleansing process before saving the cleansed data. Additionally, you have the option of accepting or rejecting the cleansed data in its entirety, or by country, or by individual address. Why did the batch cleansing process skip some records? A record is skipped when the batch cleansing process considers it already cleansed and validated. For example, an address that already follows the formats, norms, and standards of the related postal directory. Identify Duplicate Customer Information Managing Duplicate Sets: Explained Managing duplicate sets involves reviewing the details of a completed duplicate identification batch and submitting duplicate resolution requests based on the duplicate sets identified. The activity has the following aspects: Deciding whether to resolve duplicates within each identified duplicate set through a merge or link request Determining which records to remove from the duplicate resolution request Marking records as nonduplicate Changing the master record Submitting the duplicate sets for resolution Deciding on the Duplicate Resolution Request Type Select the duplicate resolution request type as merge to combine duplicate records, link to join duplicate records, or generic to select the duplicate resolution request type later. Determining Which Records to Remove Remove those records from the set that you do not want to include in the duplicate resolution request. You can view the records removed from the set in the removed records table. You can also restore these records back to the original duplicate set. 4-6 Oracle Sales Cloud Using Customer Data Management

111 Marking Records as Nonduplicate Mark a pair of records as nonduplicate to prevent the pair from being identified as potential matches. To remove the pair from nonduplicate list, end date the nonduplicate record. Changing the Master Record The application randomly selects a record in a duplicate set as the master record to be preserved after merge. However, the data steward can select a different record as the master record. Submitting the Duplicate Sets for Resolution Submit the duplicate sets as merge or link requests for resolution. Creating Duplicate Identification Batches: Points to Consider You have the following options while creating a duplicate identification batch: Create the duplicate identification batch for a single run Create the duplicate identification batch to be run periodically Create the duplicate identification batch from a copy of an existing duplicate identification batch Consider the following points to determine which batch creation option best suites your business needs. Duplicate Identification Batch for a Single Run Create a duplicate identification batch for a single run only if the run is for a oneoff transaction or scheduling it to be run periodically is not required or practical or will simply waste valuable computing power. Duplicate Identification Batch to be Run Periodically Create the duplicate identification batch to be run periodically to remove the need for creating a new batch definition every time duplicates need to be identified in the registry. You can define the batch selection criteria and duplicate identification rules once and schedule the batch to run at a specific interval, such as daily, every night at 9 PM, or weekly, every Sunday at 10 PM. This functionality allows you to automate the execution of the registry duplicate identification, a tasks that is mostly ongoing and repetitive. Using the Copy of an Existing Duplicate Identification Batch Use the copy of an existing duplicate identification batch to quickly create another duplicate identification batch. Although the copied batch inherits most of the original batch details, such as batch selection criteria and duplicate identification rules, you can edit them and also schedule the new batch to run just once or periodically. Manage Customer Data Quality 4-7

112 Enter Duplicate Identification Batch Defining Subset Rules: Worked Example This example demonstrates how to define subset rules, also known as batch criteria rules, to create duplicate identification batches. You can go about identifying potential duplicate records either manually or by using the duplicate identification batch functionality. You can create a duplicate identification batch by defining subset rules also known as batch criteria rules. Use the Subset Rules for Identifying Duplicates table on the Create Duplicate Identification Batch page to specify criteria for retrieving a subset of records in the batch. The data quality engine identifies duplicate records from this subset of records. The rules for identifying duplicates are joined together by an AND condition. Adding New Subset Rules 1. Navigate to the Create Duplicate Identification Batch page as follows: Customer Data Management Dashboard - Duplicate Identification Overview - Create Duplicate Identification Batch 2. Use the Create menu option or button to add a couple of new subset rules. Populating Subset Rules and Submitting the Batch 1. Enter the following information in the Subset Rules for Identifying Duplicates table. Object Attribute Operator Value Person Name Contains John Address Address Line 1 Contains Redwood 2. Click Submit. View Nonduplicate Mapping Nonduplicate Records: Explained Mark a pair of records as nonduplicate to prevent the pair from being identified as potential matches. Nonduplicate End Date Used to revert nonduplicate records identified by data steward, so that going forward the records could be considered as potential duplicates again. 4-8 Oracle Sales Cloud Using Customer Data Management

113 Manage Nonduplicate Records Managing nonduplicate records involves modifying the period for which a record should be considered as a nonduplicate with the master record. You can achieve this by changing the end date. Revert Nonduplicate Remove a pair of records from the nonduplicate list by end dating the nonduplicate status. FAQs for Assign Duplicate Identification Batch Why am I unable to assign or reject duplicate identification batches? Only a Data Steward Manager can assign new duplicate identification batches. You can initiate the assignment of duplicate identification batches to an assignee from the duplicate identification work area, named Overview, or the customer data management dashboard, or from the Manage Duplicate Identification Batches page, and complete it on the Assign Duplicate Identification Batch page. A Data Steward Manager can reject any batch, but the Data Steward can only reject batches assigned to himself. How can I cancel a batch process? You can cancel a batch process using the Scheduled Processes option on the Tools menu of the Navigator. You can search for the batch process on the Scheduled Processes Overview page. Search for the batch process using its process ID received after submitting it using the appropriate setup and maintenance task. Enter Duplicate Resolution Request Creating Duplicate Resolution Request: Explained Create a data quality management request to resolve potential duplicates in the data registry. Select the value of the Automatic Processing Option as Create duplicate resolution request only to submit duplicate sets as generic resolution requests or None to edit the sets before request selection You can create a duplicate resolution request by selecting duplicates in one of the following two ways: By searching and selecting duplicates sets manually Manage Customer Data Quality 4-9

114 By selecting duplicate sets identified automatically Manual Selection of Duplicates This method of duplicate identification allows a user to easily identify parties that need to be merged or linked based on search criteria. The user can pick the duplicate records from the search results and then continue by deciding whether to create a merge or link request. Application Duplicate Identification Create a duplicate identification batch to use this method of duplicate identification. In this method of duplicate identification, the duplicate sets are identified using the embedded data quality matching engine. This method of creating a duplicate resolution request is a two-step process: 1. Run the duplicate identification batch program to identify potential duplicates. 2. Review the duplicate sets identified by the batch program and create either merge or link requests. Selecting Duplicate Resolution Request Type: Critical Choices You have the option of selecting any one of the following duplicate resolution request types to resolve potential duplicates: Merge Request Link Request However, the choice of duplicate resolution request type is a critical one. It determines how the duplicates records in a resolution request are resolved. It also determines how the records that are part of the duplicate resolution request are maintained in the data registry after the duplicate resolution process is complete. Consequently, you must consider the impact of selecting each duplicate resolution request type before you make your choice. Merge Request Select the merge duplicate resolution request type to combine the duplicate records into a single new master record. Note that after the duplicate resolution process is complete, the duplicate records will not exist in data registry any more and that you will be able to make updates only to the sole surviving master record. Link Request Select the link duplicate resolution request type to associate together the duplicate records. Note that linked records are first class citizens in the data model and have their own unique identifiers.. Records participating in a link have a master-duplicate relationships, in which one of the records participating in the link is designated as a master and others duplicates Oracle Sales Cloud Using Customer Data Management

115 Resolve Duplicate Customer Information Merging Duplicate Records: Explained Merging involves combining two or more duplicate records into one survivor record. Merging is one of the two ways of resolving duplicate records. The other way is to link the duplicate records. In a link, an association is created between duplicate records. Merging duplicate records has the following aspects: Creating a merge request Reviewing merge request statuses Selecting the master record and the records to merge Deciding to override system mapping Reviewing merge request related notifications The following figure illustrates the merge process flow: Manage Customer Data Quality 4-11