Using Customer Data Management

Oracle Customer Data Management
Cloud
Using Customer Data Management
Release 13 (update 18C)

Oracle Customer Data Management Cloud
Release 13 (update 18C)

Part Number E98207-01
Copyright © 2011-2018, Oracle and/or its affiliates. All rights reserved.
Author: Jesna Narayanan
Contributors: Abhishek Sura, Vijay Tiwary, Rakesh Chaudhary, Vimmika Dinesh, 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, then the
following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, 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 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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement
between you and Oracle.
The business names used in this documentation are fictitious, and are not intended to identify any real companies currently or previously in existence.
Contents
Preface i
1 About This Guide 1

Audience and Scope ................................................................................................................................................ 1
Related Guides ......................................................................................................................................................... 1
2 Managing Customer Information 3

Customer Data Management Cloud: Overview ......................................................................................................... 3
Managing Organization Information: Explained .......................................................................................................... 4
Managing Person Information: Explained .................................................................................................................. 5
Managing Group Information: Explained ................................................................................................................... 6
Profile: Explained ...................................................................................................................................................... 7
Profile History Tracking: Explained ............................................................................................................................ 7
Usage Assignments: Explained ................................................................................................................................. 8
Managing Relationships: Explained ........................................................................................................................... 8
Managing Source System References: Explained ..................................................................................................... 9
3 Importing Accounts and Contacts Using Import Management 11

About Import Management ..................................................................................................................................... 11
Importing Your Data ................................................................................................................................................ 16
4 Using File-Based Import 25

Overview of File-Based Import ................................................................................................................................ 25
Import Consumers Using File-Based Import ............................................................................................................ 48
Import Contacts Using File-Based Import ............................................................................................................... 53
Import Country Structures Using File-Based Import ................................................................................................ 58
Import Customer Hierarchies Using File-Based Import ............................................................................................ 61
Import Customers Using File-Based Import ............................................................................................................ 72
Import Employee Resources Using File-Based Import ............................................................................................. 79
Import Geographies Using File-Based Import .......................................................................................................... 83
Import Households Using File-Based Import ........................................................................................................... 86
Import Legal Entities Using File-Based Import ......................................................................................................... 91
Import Resource Teams Using File-Based Import ................................................................................................... 97
Import Common Supporting Objects ...................................................................................................................... 99
Importing Accounts ............................................................................................................................................... 187
Importing Contacts ............................................................................................................................................... 200
Importing Country Structures ................................................................................................................................ 233
Importing Customer Hierarchies ............................................................................................................................ 238
Importing Geographies .......................................................................................................................................... 251
Importing Households ........................................................................................................................................... 271
Importing Source System References ................................................................................................................... 281
5 Importing Accounts and Contacts Using Simplified View Import Objects 283
Importing Data Using Simplified View Import Objects: Overview ............................................................................ 283
Importing Contacts Using the Contact - Simplified View Import Object: Procedure ................................................ 283
Importing Accounts using the Account - Simplified View Import Object: Procedure ............................................... 295
6 Using File-Based Export 309

File-Based Data Export: Explained ........................................................................................................................ 309
Using File-Based Data Export to Export Data: Worked Example ........................................................................... 314
7 Using Round-Trip Export-Import 315

Exporting and Importing Data Between Oracle Sales Cloud Instances Using Automatic Mapping: Worked Example .. 315
Exporting and Importing Data Between Oracle Sales Cloud Instances Using Automatic Mapping: Procedure ......... 316
8 Enriching Data 319

Data Enrichment: Overview ................................................................................................................................... 319
Batch Data Enrichment: Explained ........................................................................................................................ 320
Creating a Data Enrichment Batch: Procedure ...................................................................................................... 321
Synchronizing D&B Updates: Procedure ............................................................................................................... 322
9 Cleansing Addresses 325

Cleanse Customer Information .............................................................................................................................. 325
FAQs for Cleanse Customer Information ............................................................................................................... 327
10 Identifying Duplicates 329

Identify Duplicate Customer Information ................................................................................................................ 329
View Nonduplicate Mapping ................................................................................................................................. 340
FAQs for Assign Duplicate Identification Batch ...................................................................................................... 340
11 Resolving Duplicates 343

Creating Duplicate Resolution Requests: Explained ............................................................................................... 343
Selecting Duplicate Resolution Request Type: Critical Choices ............................................................................. 344
Processing Duplicate Resolution Requests: Worked Example ............................................................................... 344
Duplicate Resolution Request Status: Explained ................................................................................................... 345
Merging Duplicate Records: Explained .................................................................................................................. 346
Merging Accounts and Contacts: Procedure ........................................................................................................ 349
Overriding System Mapping: Procedure ................................................................................................................ 349
Automerge: Explained ........................................................................................................................................... 350
Performing Automerge Using A SOAP Web Service: Worked Example ................................................................. 352
Managing Rejected Merge Requests: Explained ................................................................................................... 354
Linking Duplicate Records: Explained ................................................................................................................... 355
Managing Links: Explained .................................................................................................................................... 355
Purging Duplicate Resolution Data: Explained ....................................................................................................... 356
FAQs for Resolve Duplicate Customer Information ................................................................................................ 356
12 Managing Hierarchy Information 359

Manage Hierarchy Information .............................................................................................................................. 359
FAQs for Manage Hierarchy Information ............................................................................................................... 362
13 Managing Protected Information 365

Working with Protected Information: Explained ..................................................................................................... 365
14 Viewing Audit Histories 367

Audit History: Explained ........................................................................................................................................ 367
Audit Event Types: Explained ................................................................................................................................ 367
15 Using Customer Data Management with Other Cloud Services 369

Customer Data Management Cloud Integration Approaches: Explained ................................................................ 369
Merge Operation Process During Integration Cloud Service Based Integration: Explained ...................................... 371
Oracle Customer Data Management Cloud Preface
Preface
This preface introduces information sources that can help you use the application.
Using Oracle Applications

Using Applications Help
Use help icons to access help in the application. If you don't see any help icons on your page, click your user image
or name in the global header and select Show Help Icons. Not all pages have help icons. You can also access Oracle
Applications Help.
Watch: This video tutorial shows you how to find help and use help features.

You can also read Using Applications Help.
Additional Resources
• Community: Use Oracle Cloud Customer Connect to get information from experts at Oracle, the partner
community, and other users.
• Guides and Videos: Go to the Oracle Help Center to find guides and videos.
• Training: Take courses on Oracle Cloud from Oracle University.
Conventions
The following table explains the text conventions used in this guide.
Convention Meaning
boldface Boldface type indicates user interface elements, navigation paths, or values you enter or select.
monospace Monospace type indicates file, folder, and directory names, code examples, commands, and URLs.
> Greater than symbol separates elements in a navigation path.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website.
Videos included in this guide are provided as a media alternative for text-based help topics also available in this guide.
i
Oracle Customer Data Management Cloud Preface
Contacting Oracle
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For
information, visit My Oracle Support or visit Accessible Oracle Support if you are hearing impaired.
Comments and Suggestions

Please give us feedback about Oracle Applications Help and guides! You can send an e-mail to:
[email protected].
ii
Oracle Customer Data Management Cloud Chapter 1
Using Customer Data Management About This Guide
1 About This Guide
Audience and Scope

This guide is intended for the end users of the customer data management cloud service such as customer data stewards
and data steward managers.
This guide contains conceptual information and procedures needed to manage customer information and customer data
quality. You can use this guide to work with the customer data management cloud service capabilities such as duplicate
identification, duplicate resolution, address verification, and data enrichment.
Related Guides
You can refer to the related guides listed in the following table to understand more about the tasks covered in this guide.
Title Description
Oracle Customer Data Management Describes how to get started with the implementation of Customer Data Management cloud service
Cloud Getting Started with Your capabilities such as duplicate identification, duplicate resolution, address verification, and data
Customer Data Management enrichment. This guide uses the default settings provided by Oracle and does not provide detailed
Implementation explanations of all available features.

Oracle Customer Data Management Contains conceptual information and procedures needed to manage customer information and
Cloud Using Customer Data customer data quality. You can use this guide to work with the customer data management cloud
Management service capabilities such as duplicate identification, duplicate resolution, address verification, and
data enrichment.

Oracle Customer Data Management Provides conceptual information and procedures needed to implement the Customer Data
Cloud Implementing Customer Data Management cloud service.
Management

Oracle Sales Cloud Understanding File- Describes how to import legacy and other data into Oracle Sales Cloud using File-Based Data
Based Data Import and Export Import.

Oracle Sales Cloud File-Based Data Directs you to reference information that you can use to create an importable source data file for the
Import for Oracle Sales Cloud import of individual objects.

1
Using Customer Data Management About This Guide
2
Using Customer Data Management Managing Customer Information
2 Managing Customer Information
Customer Data Management Cloud: Overview

Oracle Customer Data Management Cloud comes with the following capabilities and components to enable you to manage
your customer data and its quality, and create a trusted master customer profile:
• Work areas to manage customer information

• Data quality configurations
• Data quality management capability during import process
• Separate work areas for duplicate identification, duplicate resolution, and address cleansing
• Work area for hierarchy management
• Data enrichment capability
Customer Information Management

You can manage customer information, such as profile, usage assignments, relationships, classifications, source system
references, hierarchy memberships, linked records, accounts, and contacts, in the Organizations, Persons, and Groups work
areas. You can also use these work areas to create customers.
Data Quality Configurations

Data quality configurations define how the data quality services, such as data quality matching and cleansing, are run during
real time and during batch execution. Data quality services use these configurations to call appropriate services of the
embedded data quality engine to consolidate, cleanse, and enrich customer data.
Data Quality Management During Import Process

You can configure the import process to:
• Define deduplication within the data being loaded.

• Define deduplication of the data being loaded against the records that exist in the registry.
You can also select a matching configuration to identify duplicates and specify the action to perform on the duplicate records
during the import process.
Duplicate Identification, Duplicate Resolution, and Address Cleansing

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. The resolution request can be verified, approved or rejected, and processed at a later date.
3
Address cleansing lets you cleanse address data existing in the registry and ensures data accuracy over time. Real-time
address cleansing ensures that the incoming data from source systems follows the same convention as the target system for
consistent information.
Hierarchy Management
You can leverage the hierarchy of your customers in many business processes. For example, you can use the hierarchy
management capability to capture your customer's corporate hierarchy and to show how headquarters, branches,
subsidiaries, and so on are related. You can use the corporate hierarchy information to process payments from one customer
and apply them to another customer in the same hierarchy.
Data Enrichment
You can use this functionality to enrich account and contact data to ensure it is comprehensive. Data enrichment improves
the quality of your existing account or contact data and address information as well as enriches that data with additional
information.
Managing Organization Information: Explained

Oracle Customer Data Management Cloud provides the Organization entity to manage information for different types of
institutional customers, such as business organizations and professional bodies.
An Organization exists separately from any business relationship that it enters into with another entity. For example, the same
Organization can enter into different business relationships, such as buying or selling, and can be referred to differently, such
as a customer or supplier, in different business flows across the application. In some Oracle Cloud applications, organizations
are referred to as accounts.
You can use the Organizations work area, to search for an organization, retrieve organization data from various systems,
review the data, and edit the data. The Organizations work area also provides you separate tabs to manage different types
of organization information such as profile, usage assignments, relationships, classifications, source system references,
hierarchy memberships, and linked records.
Creating Organizations
To create organizations:
1. Navigate to the Organizations work area as follows: Navigator > Customer Data Management >
Organizations.
2. Click the Create action menu option or button.
3. Complete the mandatory fields. Enter the following sample data:
◦ Usage: Party of Interest.
◦ Name: Green Corp.
◦ Registry ID: This is auto populated. However, you can override it with a unique identifier of your choice.
4. Click Save and Close or Save and Edit, as required.
4
Editing Organizations
To edit organizations:
1. Navigate to the Organizations work area as follows: Navigator > Customer Data Management >
Organizations.
2. Search for the organization that you want to edit. You can search by entering criteria such as the organization name
or registry ID. You can also use the saved searches.
3. Select the organization you want to edit from the Search Results region and click through its name or registry ID to
navigate to the Edit Organization page.
4. On the Edit Organizations page, you can edit the organization's details such as usage assignments, relationships,
source system references, classifications, and linked records.
5. Click Save and Close.
Managing Person Information: Explained

Oracle Customer Data Management Cloud comes with the Person entity to enable you to manage information for different
types of individual customers and business contacts.
A Person exists separately from any business relationship that it enters into with another entity. For example, the same
Person can enter into different business relationships, such as buying or selling, and can be referred to differently, such as a
customer or supplier, in different business flows across the application. In some Oracle Cloud applications, person customers
are referred to as contacts.
You can use the Persons work area, to search for a person, retrieve person data from various systems, review the data, and
edit the data. The Persons work area also provides you separate tabs to manage different types of person information such
as profile, usage assignments, relationships, classifications, source system references, hierarchy memberships, and linked
records.
Creating Persons
To create persons:
1. Navigate to the Persons work area as follows: Navigator > Customer Data Management > Persons.
◦ Usage: Contact
◦ Fist Name: Andrew
◦ Last name: Flintoff
Editing Persons
To edit persons:
1. Navigate to the Persons work area as follows: Navigator > Customer Data Management > Persons.
2. Search for the persons that you want to edit. You can search by entering criteria such as the person name or registry
ID. You can also use the saved searches.
5
3. Select the person you want to edit from the Search Results region and click through its name or registry ID to
navigate to the Edit Personpage.
4. On the Edit Person page, you can edit the person's details such as usage assignments, relationships, source
system references, classifications, and linked records.
Managing Group Information: Explained

Oracle Customer Data Management Cloud provides the Group entity to enable you to create a customer record consisting
of a collection of persons and organizations, and have a business relationship with other entities. A group can be assigned to
opportunities and leads.
A group includes basic information such as name, type, and certification level, and child entities such as group members,
relationships, classifications, and contact methods. The group type such as Couple, Household, or Joint Ownership classifies
a group based on its purpose. The Groups work area provides you separate tabs to manage different types of group
information such as profile, usage assignments, relationships, source system references, and linked parties.
Group Members
A group member can be a person or an organization, and their member type attribute defines the relationship of the member
with the group. For example, a member of type Group Contact is the contact for the group. You can manage members of a
group from the Profile tab of the Group work area.
Creating Groups
To create groups:
1. Navigate to the Groups work area as follows: Navigator > Customer Data Management > Groups.
◦ Name: John and Family

◦ Usage: Party of Interest
◦ Type: Household
Editing Groups
To edit groups:
1. Navigate to the Groups work area as follows: Navigator > Customer Data Management > Groups.
2. Search for the group that you want to edit. You can search by entering criteria such as the group name, registry ID,
and type. You can also use the saved searches.
3. Select the group you want to edit from the Search Results region and click through its identifier to navigate to the
Edit Group page.
4. On the Edit Group page, you can add new group members as well as edit group details such as usage
assignments, relationships, source system references, classifications, and linked records.
6
Profile: Explained
The profile for any customer entity, such as Group, Person, or Organization, includes information such as customer details,
additional names, additional identifiers, addresses, and contact points.
You can add most of the customer profile information during record creation, except for some profile attributes, such as an
organization's financial and bank details. You can edit these profile attributes for an entity from the Edit page for that entity,
such as, Edit Group, Edit Person, or Edit Organization. The Edit page for an entity lets you set a primary contact point or
address for that entity.
Oracle Applications Cloud maintains a history of the changes to the customer profile that you can view in the Profile History
page.
Some of the profile attributes, such as certification and primary contact details are common for all entity types and usages.
However, some other profile attributes are specific to a customer type. They are as follows:
• Organization: Includes name, organization information, certification information, legal information, and contact details.
• Person: Includes person details such as name, address, and contact information.
• Group: Includes name, group information, and group members.
Profile History Tracking: Explained

Profiles and profile attributes of customer entities, such as Groups, Persons, or Organizations, can evolve over times as a
result of duplicate identification and resolution activities aimed at consolidating data from several different source systems.
Oracle cloud applications maintain a history of the changes to the profile of a customer entity that you can view in the Profile
History tab on the Edit page for that entity.
Enabling Profile History Tracking

You must set the profile option: ZCH_ENABLE_SURVIVORSHIP to Yes to enable profile history tracking.
Viewing Profile History Information

To view the profile history information for a customer entity, navigate to the specific entity record as follows:
1. Sign in as a Customer Data Management Cloud user, such as Data Steward or Data Steward Manager.
2. Navigate to the relevant work area, such as Groups, Persons or Organizations as follows: Navigator > Customer
Data Management.
3. Search for the record. You can search by entering criteria such as the name, registry ID, and type. You can also use
the saved searches.
4. Select the record from the Search Results region and click through its name or identifier to navigate to the relevant
Edit page. The Edit Organization (account), Edit Person (contact), or Edit Group (Household) page appears.
5. Click the Profile History tab.
On the Profile History tab, you can use the From Date and To Date filters to view the profile history in a date range. Note
that the current, historical, and the future dated records are sorted by date descending. When multiple changes are done
within a day, use the sequence of changes on a given date along with the effective dates to determine the most recent
record. The profile history information also includes changed attributes such as name, legal status, and size.
7
Change Details
The change details include multiple changes done within a day and also indicate the record that is available to be used in
transactions. The old and new values of different attributes, such as name, legal status, and size, are also displayed.
You can export both the profile history information and the change details to spreadsheets.
Usage Assignments: Explained

Usage Assignments describe how entities can be used across the application, and can be used in business flows. Entities
can have multiple usage assignments, such as Partner or Customer. You can manage usage assignments for an entity from
the Edit page of the selected entity, such as Edit Group, Edit Person, or Edit Organization. You can navigate to this page by
searching for the required record from the Groups, Persons, or Organizations work area.
There are two types of usage assignments:
• Conditional usage assignments

• Unconditional usage assignments
Conditional Usage Assignments

A conditional usage assignment requires a business event to occur. For example, adding a person as a contact for a group
creates contact usage for the person.
You can assign rules to a conditional usage assignment to define the business event. There are four types of rules:
• Assignment rules: Define how the usage can and cannot be assigned.
• Exclusivity rules: Restrict usage assignment, so that between a specified date range the usage can be the only
usage allowed to be assigned.
• Incompatibility rules: Specify which usages cannot be assigned concurrently during a date range.
• Transition rules: Define which usages can transition to the usage you are creating or editing.
Unconditional Usage Assignments

You can update unconditional usage assignments without the need for a business event. For example, you can update the
usage for an organization from a party of interest to a customer.
Managing Relationships: Explained

You can manage complex real-life relationships among various entities such as employees, employers, contacts, and
organizations in the Edit page of the selected entity, such as, Edit Groups, Person or Organization. You can navigate to this
page by searching for the required record from the Groups, Persons or Organizations work area. In Oracle Applications
Cloud, a relationship is an entity's role in the context of another entity.
Note: You can only view the relationships for the entity in context, unless you have the manage privilege.
8
You must define the following for each relationship:

• Relation types, such as employment or subsidiaries.
• Relationship role pairs, such as employee and employer.
• Relationship phrase pairs, such as employee of and employer of
In the Edit page for an entity, you can:

• View all relationships for the entity in context.
• Create relationships for an entity by specifying the relationship role, the related party name, and the relationship start
and end dates for each relationship.
• Modify the end date information and any additional information captured using descriptive flexfields for the
relationships.
• Delete a relationship to make it inactive.
Managing Source System References: Explained

A source system is any data source from which entity records and other related data can be imported. Source system
references are the cross references between the source system unique identifier of a record and the unique identifier of that
record in Oracle Applications Cloud.
Source System References in Oracle Applications Cloud

Organizations use multiple software applications to run their businesses. These applications are supplied by different vendors
and run on different databases, which may cause the following issues:
• Duplication of records and data across systems.
• Logical representation or structure of a record may vary.
• Keeping the data in different systems synchronized, generating a consolidated view, and sharing data across
systems becomes highly complex because of the difference in the logical representation.
You can resolve these issues in Oracle Applications Cloud by:

• Defining multiple external systems as source systems. While defining source systems you can specify the type of the
source system. The source system can be a Spoke system, such as a legacy system, or a Purchased system, such
as data from a third party provider. You can also specify which objects, such as parties only or parties and contacts,
are importable from a particular source system
• Creating records in Oracle Applications Cloud database from one or multiple source systems by:
◦ Creating master records. Multiple source system references can create one master record by merging or
linking multiple duplicate records imported from multiple source systems.
◦ Creating records for every source system record. If you do not allow multiple source system references, then
a record will be created for every source system record. This means that you could potentially create duplicate
records in the database.
• Using source system references, also known as cross references, to present a consolidated view. You can maintain
a central register of global identities, links to master data in source systems, lists of transformation rules, and a minor
subset of information that is needed to aid in matching. At runtime, you can access the source systems' master data
and assemble a point-in-time consolidated view.
9
Managing Source Systems

In Oracle Applications Cloud, you can:
• View source systems contributing to the party in the context from the Referenced Source Systems table.
• View source system identifiers information for the child entities of a party for the source selected from the Referenced
Source Systems table.
• Delete source system identifiers to change the status of the source system reference to inactive.
• Add source system identifiers to include a new source system reference.
Note: The source system, source system reference identifier, and the start date cannot be updated. To change
a source system reference identifier, delete the current record and add a new source system reference.
10
Using Customer Data Management Importing Accounts and Contacts Using Import Management
3 Importing Accounts and Contacts Using

Import Management
About Import Management

Importing Data: Procedure
Using the Import Management option available from the Tools work area, you can import a wide range of business data
from text files. Your import data can either create, update, or delete application records.
Use the steps outlined in this topic as a guide to importing data. The import options and other details differ by the type of
data that you're importing. Before importing, you must understand how the data in your file maps to the attributes in Oracle
Applications Cloud and what values are expected in the import file.
Note: Do not submit duplicate import jobs for the same import object because they create duplicate object
records.
To help you get started, you can use the example import templates described in the related topics.
Importing Data from a File

You must be signed in as an administrator or setup user to perform the import. To import data:
1. In the Tools work area, click the Import Management icon.

2. On the Manage Imports page, click the Create Import Activity button. The Create Import Activity: Enter
Import Options page appears.
3. Provide values for each field on the page as shown in the following table:
Field Description of the value
Name Name of the import.

Object
Object that you are importing.
If you cannot find your object in the drop-down list, then you can search and select the object
by clicking the Search link. In the Search and Select dialog box, enter the object name in the
Object text box and click the Search button. Select your object from the result list and click OK.
You can also use the advanced search option by clicking the Advanced button. Here you can
search based on various filter criteria such as object name, Attachment supported, creation date,
and so on.
If the object you are importing is not listed then verify if you have the roles and privileges required
to import the object.
11
Field Description of the value
Attachment Object
To import an attachment for an existing object record in the database select the Attachments
object from the Object drop-down list. Next select the object from the Attachment Object
drop-down list.
For more details on importing attachments, review the topic Importing Attachments: Procedure in
the related topics section.
File Name Browse and select a text file in CSV format.

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

4. Optionally, to set additional import configurations, click the Advanced Options section. Here you can configure
settings under Source File, Import Options, or Create Schedule sections.
a. In the Source File and Import Options regions, some of the options in the following table might be available
depending on the object that you're importing:
Option Description
Import Mode
You can specify whether you want to create and update records or update them only.
• Update and create records - a new record is created if a matching record is not
found. This is the default option.
• Create records - all the records in the file are new records which have to be
created. If there are any existing matching records, then they are marked as errors.
• Delete records - all the records in the file are deleted.
Notification email The email of the individual who receives import processing notifications. The user submitting
the import receives an email notification automatically. To have more than one email
recipient, separate the email addresses with a semicolon.

Delimiter
If your file doesn't use a comma to separate values, then select the correct delimiter in the
Delimiter drop-down list.
Decimal Separator The decimal separator used in your import file.

Date Format The format of the date fields in your file.

Time Stamp Format The format of time fields in your file.

File Encoding The format in which your source file has been encoded.

b. In the Create Schedule region, you can schedule the import to either run immediately or at a future date. If
you select a future date, then provide the date and time to start the import.
12
5. Click Next. The Create Import Activity: Map Fields page displays the first row of the data in your source file. By
default, the application tries to automatically map each of the source file columns to the appropriate target object
attribute. If some of the columns in your file could not be mapped, then drag the target attribute onto the Attribute
Name column under the Source File region.
6. You also have the option of selecting an appropriate mapping from the list of available mappings under the Import
Mapping drop-down list. If you're reusing an import mapping, then both the source and target columns are already
populated. The Source File region represents your import file.
You can choose not to import a column in your file by leaving the Attribute Name field blank.
7. To validate the mapping of fields, click the Validate Data button. Validation process is triggered and displays any
mapping errors on the Mapping Validation screen. Additionally, the first 10 rows of the file are validated.
8. Click Next. The Create Import Activity: Review and Submit page appears. On this page, review the import
activity configuration. If you had not run the prevalidation on the Map Fields page, then you get a notification
message to run the validation process.
9. Click the Validate Data button to run the validation. Validation errors, if any, are displayed on the Mapping Validation
screen. The data in unmapped columns are not imported. If you get warnings about unmapped columns, then you
can ignore these columns, and proceed to submit the import job.
10. Submit to activate the import.
Monitoring the Import Status

To monitor the status of your import:
1. After you submit your import, you can view the status on the Manage Imports page that appears. It shows the
following infotiles:
Infotile Heading Description
All Imports Shows the active, completed, and unsuccessful imports.

Active Imports Shows all the imports that are currently running.

My Completed Imports Shows the imports that have completed.

Unsuccessful Shows the unsuccessful imports.

2. Click the My Completed Imports tab to view the imports that have completed.
3. Monitor the status of your import. A status of Completed or Completed with Errors indicates that the import has
completed. Alternatively, you can wait for the notification email. For more details on monitoring the status of import,
see the topic Import Monitoring: Explained referenced in the related links section.
4. Click the import name link to see additional information about the import. You can generate the diagnostics and log
files from the Action menu. Download the log files by clicking the download icon under the Import Attachments
section.
Suppressing Business Events for the Objects

While bulk loading data, business events on standard objects are triggered in the Create, Update, and Delete operations. This
may have an adverse impact on performance. You can suppress this behavior using the following profile options:
• HZ_ENABLE_ENTITY_EVENTS: You can use this profile option to suppress the granular entity events. This profile
option has the default value set to Y. Y indicates that no business events are suppressed. This profile option
suppresses the Create, Update, and Delete events of the Account and Contact objects.
13
• HZ_ENABLE_EVENT_TRACKING: Enables composite event tracking for customer and contact entities. This profile
option tracks changes to the entities, and raises an event whenever there is a change to the entities. This profile
option has the default value set to N.
• HZ_INVOKE_OBJ_WF_ON_TRACKING: Enables rollup of the child entity changes to the root object during event
tracking. This profile option initiates the root object workflow whenever the child entities change. This profile option
has the default value set to N.
• ZPM_ENABLE_PARTNER_EVENTS: You can use this profile option to suppress the business events for Partner,
Partner Contact, and Partner Notes objects. This profile option has the default value set to N. However, the profile
option ZCA_PUBLIC_BUSINESS_EVENTS should be disabled to suppress events for any object.
• ZCA_PUBLIC_BUSINESS_EVENTS: You can use this profile option to suppress the business events. This profile
option has the default value set to Y. Y indicates that all business events are enabled. When you set the profile
option value to N, then the business events are suppressed until the same profile option is set to Y once again. Once
disabled, then the events are not published even when using either Import Management or the REST web services.
This profile option overrides the other profile options mentioned above. You can also suppress the business events
for a user by creating a user profile level, defining a user name, and setting it to 'N'. The Create, Update, and Delete
events of the following objects are suppressed by this profile option:
◦ Account
◦ Activity
◦ Activity Note
◦ Asset
◦ Business Plan
◦ Business Plan Note
◦ Contact
◦ Contract
◦ Deal
◦ Deal Note
◦ Lead
◦ Lead Note
◦ Opportunity
◦ Opportunity Note
◦ Partner
◦ Partner Contact
◦ Partner Note
◦ Service Request
◦ Service Request Message
Related Topics
• File-Based Import Monitoring: Explained
• Import Activity Field Mapping: Explained
• File-Based Import Mapping: Explained
14
Importing Attachments: Procedure

This topic describes how to import attachments using the Import Management feature. You can import attachments
associated with any supported object.
The following objects support importing attachments:
• Activity
• Asset
• Lead
• Opportunity
The following are the file types supported for attachment files:
• CSV
• PDF
• PNG
• PPTX
• TIF
• TEXT
• XLSX
• XML
Importing Attachments
You can use the following steps to import attachments using Import Management:
1. Click Tools > Import Management.
2. On the Manage Imports page, click the Create Import Activity button. The Create Import Activity: Enter
Import Options page appears.
3. In the Name field, enter a name for your import. In the Object drop-down list, and select Attachment.
4. In the Attachment Object drop-down list that appears, select the object associated with the attachment.
5. Browse and select the ZIP file that contains the attachment files and the source data file with the object records
information for which you import the attachment.
6. The ZIP file must contain at least a file named Attachment.CSV, and optionally one or more attachment files. The
Attachment. CSV file has the format shown in the following table:
Pk1Value ObjectPuid FileName Url
300100111735265 Sales.txt

CDRM_L1011 www.Google.com

300100111735265 www.Yahoo.com

CDRM_L1212 file1.txt

15
Pk1Value and ObjectPuid column values uniquely identify an existing object record. FileName indicates the name of
attachment files. Url indicates the value of URL attachment to import.
An attachment can only be associated with an existing record of the object. A single record can be associated with
multiple attachments by having multiple rows in the CSV file. There is no limit on the number of attachments that can
be imported in a single import job. However, the size of the attachment ZIP file cannot exceed 250 MB.
Note: A record in the CSV file cannot have values for both FileName and Url columns. You can pass
either the Primary key or the PUID, but not both for an object record.
7. Click Next. On the Create Import Activity: Map Fields page, click the Apply button next to the Import Mapping
drop-down list to map the source and target attributes automatically.
8. Click Next to navigate to the Review and Submit page.
Review the import activity configuration and click Submit to activate the import. The Manage Imports page shows the
status of the submitted import. The topic Importing Data: Procedure in the related topics section contains more details about
the import process.
Importing Your Data

Importing Your Contact Data
Use this topic to import contact data into Oracle Applications Cloud. You can use the import functionality to create, update,
or delete contact records.
The contact object has the following child objects:
• Address
• Classification
• Relationship
• Sales Team Member
To import contact records, perform the following tasks:

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

To import your contact data into Oracle Applications Cloud, you must populate a CSV file with your source data and map that
source data to target object attributes in Oracle Applications Cloud.
You must do the following before creating the CSV file for data import:
• Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.
• Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your
objects.
• Understand your options for uniquely identifying the records.
16
• Ensure parent records exist before importing child records.

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

You must set certain options for some attributes in the application before you can populate them. For example, if you are
using source system reference information to identify your contact records, the source system of the Contact object should
be enabled for parties in the Manage Trading Community Source Systems task.
Also, when importing a child record, ensure that its parent record exists in the database.
Options for Uniquely Identifying the Records

To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import
process to uniquely identify the records. The file import process uses the attribute values to automatically map your source
data to the target object attributes in Oracle Applications Cloud.
The preferred options for uniquely identifying an object record are as follows:
• Public unique identifiers: If you are creating records, then you can provide a user-friendly public unique identifier
(attributes denoted with Number and usually visible in the business object's UI). If you update a record for which you
have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use
the Number attribute to identify the record.
• Source system and source system reference value: If you are importing data from a legacy or external system or are
updating records for which you have previously provided source system reference data, then you can provide the
source system code that identifies the external system (attributes typically denoted with SourceSystem) and source
system reference value, a unique identifier within the external system (typically denoted with SourceSystemReference).
Required Attributes and Validations

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure that
you provide valid values for the attributes. The following table lists the required attributes for importing new contact records,
required attributes for updating contact records, required attributes for deleting contact records, prerequisite setup tasks for
the attributes, and specific validations, if any, for contact import:
Attribute Description Prerequisite Setup Creating a Contact Updating an Existing Deleting an Existing
Task or Import Record Contact Record Contact Record
Validations
SourceSystem The code Identify the source

representing the system or configure Conditionally Conditionally Conditionally
source system for source systems Required For Required For Required For
the contact. either by using the uniquely identifying uniquely identifying uniquely identifying
Manage Trading a contact record, a contact record, a contact record,
Community Source provide one of the provide one of the provide one of the
System task, or following reference following reference following reference
by importing the information: information: information:
source system
information into • SourceSystem • SourceSystem • SourceSystem
Oracle Applications and and and
Cloud using the SourceSystemReferenceValue
SourceSystemReferenceValue
SourceSystemReferenceVal
Source System • PartyNumber • PartyNumber • PartyNumber
Reference import
object.

The reference Identify the source
number or text system or configure Conditionally Conditionally Conditionally
representing the source systems Required For Required For Required For
uniquely identifying uniquely identifying uniquely identifying
17
Attribute Description Prerequisite Setup Creating a Contact Updating an Existing Deleting an Existing
Task or Import Record Contact Record Contact Record
Validations
source system either by using the a contact record, a contact record, a contact record,
unique ID for the Manage Trading provide one of the provide one of the provide one of the
contact. Community Source following reference following reference following reference
System task, or information: information: information:
by importing the
source system • SourceSystem • SourceSystem • SourceSystem
information into and and and
Oracle Applications SourceSystemReferenceValue
Cloud using the • PartyNumber • PartyNumber • PartyNumber
Source System
Reference import
object.

PartyNumber The public unique No prerequisite Conditionally Conditionally Conditionally

identifier of the tasks Required Required Required
contact.

FirstName First name of a No prerequisite Required Not required Not required

person party. tasks

LastName Last name of a No prerequisite Required Not required Not required

person party. tasks

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

The CSV file is provided as source to the file-based data import process. You must populate the CSV file with the data you
want to import into Oracle Applications Cloud.
You can create a CSV file on your own or by using a predefined template. To download a preexisting template, do the
following:
1. In the Navigator, under Tools, click Import Management.

2. Click the Import Objects tab to open the Manage Object Details page.
3. Click the object name link under the Display Name column to navigate to the Manage Mapping page.
4. If you don't have an existing mapping, then click the Create Import Mapping button to create a mapping.
5. On the Edit Import Mapping page, map the required by dragging them from the Target Attributes section to the
Source File section. Save the mapping when you are done.
6. Click the link in the Mapping Number column of the required mapping.
Note: You can filter the mappings using the Find drop-down list.
7. On the Edit Import Mapping page, select Download Template from the Actions drop-down list.
8. Save the template CSV file to a location on your desktop.
You must edit the template CSV file and provide valid values for the required attributes. The following is an example of a CSV
file for the Contact object.
18
PartyNumber Address1 Address2 City State FirstName LastName OwnerPartyNumber

SourceSystemSourceSystemReferenceValue
Country
Contact_ 212 Suite 10 Foster CA Dennis Peattie Party_7231354

CSV CON_ US
1823894 Herrington City TST_OSR1_001

Boulevard

Contact_ Vision Vision Palo Alto CA Steve Braun Party_4657978

DNB CON_ US
6546546 Corporation Corporation TST_OSR1_741

Address Address
1 2

Creating the Import Activity

To import data into Oracle Applications Cloud, you must create an import activity and provide the CSV file as a source to the
activity. To create an import activity, do the following:
1. Sign in as a setup user.
3. On the Manage Imports page, click Create Import Activity.
4. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select
Contact from the Object drop-down list.
5. In File Name, browse and upload the required CSV file, and click Next.
6. In the Create Import Activity: Map Fields page edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to
check for data format issues.
7. In the Create Import Activity: Review and Submit page, click Submit.
Reviewing the Import Results

You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity
is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:
1. Sign in as a setup user.
3. On the Manage Imports page, search for the import activity that you created using one of the search criteria, such
as status, name, object, and so on.
4. Check the Status column for the import activity. The import is successful if the status displays as Completed. The
other valid values for the import activity status are: Queued for import, Preparing data for import, Importing
data, Completed with errors, and Unsuccessful.
Note: On this page, you can also view quickly the number and status of all active imports, completed
imports, and unsuccessful imports that have been submitted.
Importing Your Account Data

Use this topic to import account data into Oracle Applications Cloud. You can use the import functionality to create, update,
or delete account records.
19
The account object has the following child objects:

• Address
• Classification
• Relationship
• Sales Team Member
To import account records, perform the following tasks:

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

To import your account data into Oracle Applications Cloud, you must populate a CSV file with your source data and map
that source data to target object attributes in Oracle Applications Cloud.
You must do the following before creating the CSV file for data import:
• Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.
• Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your
objects.
• Understand your options for uniquely identifying the records.
• Ensure parent records exist before importing child records.
• Identify the target object attributes that are required in the CSV file for a successful import.
Prerequisite Setup Tasks
You must set certain options for some attributes in the application before you can populate them. For example, if you are
using source system reference information to identify your account records, the source system of the Account object should
be enabled for parties in the Manage Trading Community Source Systems task.
Also, when importing a child record, ensure that its parent record exists in the database. For example, when importing the
address of an account, ensure that its parent account exists in the database. If the parent record does not exist before
importing the child record, then the child record import fails.
Options for Uniquely Identifying the Records
To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import
process to uniquely identify the records. The file import process uses the attribute values to automatically map your source
data to the target object attributes in Oracle Applications Cloud.
The preferred options for uniquely identifying an object record are as follows:
• Public unique identifiers: If you're creating records, then you can provide a user-friendly public unique identifier
(attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which
you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can
use the Number attribute to identify the record. For Account object, the attribute is PartyNumber. It appears as Party
Number in the UI.
• Source system and source system reference value: If you're importing data from a legacy or external system
or are updating records for which you have previously provided source system reference data, then you
can provide the source system code that identifies the external system (attributes typically denoted with
'SourceSystem') and source system reference value, a unique identifier within the external system (typically
20
denoted with 'SourceSystemReferenceValue'). For Account object, these attributes are SourceSystem and
SourceSystemReferenceValue. They appear as Party Source System and Party Source System Reference Value in
the UI respectively.
Required Attributes and Validations
To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure that
you provide valid values for the attributes. The following table lists the required attributes for importing new account records,
required attributes for updating account records, prerequisite setup tasks for the attributes, and specific validations, if any, for
account import:
Attribute Description Prerequisite Setup Creating an Account Updating an Existing Deleting an Existing
Tasks or Import Record Account Record Account Record
Validations
SourceSystem The code Identify the source

representing the system or configure Conditionally Conditionally Conditionally
source system for source systems Required Required Required
the sales account. either by using the
Manage Trading For uniquely For uniquely For uniquely
Community Source identifying an identifying an identifying an
System task, or account record, account record, account record,
by importing the provide one of the provide one of the provide one of the
source system following reference following reference following reference
information into information: information: information:
Oracle Applications
Cloud using the • SourceSystem • SourceSystem • SourceSystem
Source System and and and
Reference import SourceSystemReferenceValue
object.
• PartyNumber • PartyNumber • PartyNumber

The reference Identify the source
number or text system or configure Conditionally Conditionally Conditionally
representing the source systems Required Required Required
source system either by using the
unique ID for the Manage Trading For uniquely For uniquely For uniquely
party (account or Community Source identifying an identifying an identifying an
contact) to which System task, or account record, account record, account record,
the sales profile by importing the provide one of the provide one of the provide one of the
belongs. source system following reference following reference following reference
information into information: information: information:
Oracle Applications
Cloud using the • SourceSystem • SourceSystem • SourceSystem
Source System and and and
Reference import SourceSystemReferenceValue
object.
• PartyNumber • PartyNumber • PartyNumber

PartyNumber The public unique Identify the party ID Conditionally Conditionally Conditionally
identifier of the and party number Required Required Required
party. value by exporting
the Party object.

OrganizationName The name of Identify the Required Conditionally Conditionally

the party of the organization name Required Required
Organization party of the resource by
type. navigating to the
Resource Directory.

21
Attribute Description Prerequisite Setup Creating an Account Updating an Existing Deleting an Existing
Tasks or Import Record Account Record Account Record
Validations
OwnerPartyNumber The public unique No prerequisite Conditionally

identifier of the tasks. Conditionally Conditionally Required
resource who owns Required Required
and manages the
sales account. Provide the Provide the
account owner, by account owner, by
including one of the including one of the
following reference following reference
information: information:
• OwnerPartyNumber • OwnerPartyNumber
• OwnerEmailAddress • OwnerEmailAddress
OwnerEmailAddress The email address No prerequisite Conditionally

of the resource who tasks. Conditionally Conditionally Required
owns and manages Required Required
the sales account.
Provide the Provide the
account owner, by account owner, by
including one of the including one of the
• OwnerPartyNumber • OwnerPartyNumber
• OwnerEmailAddress • OwnerEmailAddress
You can view the Account object along with all its child objects and attributes in the Manage Import Objects page of the
Import Objects tab. You can find attribute information like type, length, description, and so on, on this page.
Creating Source CSV File for Import

The CSV file is provided as source to the file-based data import process. You must populate the CSV file with the data you
want to import into Oracle Applications Cloud.
You can either create a CSV file on your own or make use of templates available in preexisting mappings. To download a
template, do the following:
2. Click the Import Objects tab to open the Import Object Details page.
3. In the table, select the Account object row and click the Download icon.
4. Save the Account_Templates ZIP file to a location on your desktop.
You must edit the Account.CSV file and provide valid values for the required attributes.
Creating the Import Activity

To import data into Oracle Applications Cloud, you must create an import activity and provide the CSV file as a source to the
activity. You must be signed in as an administrator or a setup user to perform this task. To create an import activity do the
following:
1. In the Navigator, click Tools > Import Management.
2. On the Manage Imports page, click Create Import Activity.
3. On the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select
Account from the Object drop-down list.
4. In File Name field, browse and upload the required CSV file, and click Next.
22
5. On the Map Fields page, the source and target attributes are automatically mapped. If required, manually edit the
attribute mappings, and save the mapping file. Click Next.
6. Click the Validate Data button to validate the mapping of the source file for unmapped columns and to check for
data format issues.
7. On the Review and Submit page, click Submit.
Reviewing the Import Results

You can review the import results by checking for the import activity on the Manage Import Activity page. You must be
signed in as an administrator or a setup user to perform this task. To check the status of the import activity, do as follows:
1. In the Navigator, click Tools > Import Management.
2. On the Manage Imports page, click the All Imports infotile. Search for the import activity that you created using
one of the search criteria, such as status, name, object, and so on.
3. Check the Status column for the import activity. The import is successful if the status displays as Completed.
Note: On this page, you can also view quickly the number and status of all active imports, completed
imports, and unsuccessful imports that have been submitted.
Related Topics
• Managing Import Mappings
23
24
Using Customer Data Management Using File-Based Import
4 Using File-Based Import
Overview of File-Based Import

File Import: How It Works
The Define File Import group of tasks relies on integration with different 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
• Base tables
25
You select the import object during setup. The import mapping is used in the import mapping step. The import file you upload
is stored in a file repository. Any additional attributes you create in Application Composer are stored in a separate extensions
repository and available for import and in the import mapping.
Application
Import Activity File Repository Composer
Data File 1
Import Object Setup File 1
File 1
Import Mapping Map Fields
Custom
Extensions
Schedule
Review and Activate
Oracle Sales Cloud

Base Tables
Interface Tables
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.
Note: Avoid concurrent submission of File Import jobs for the same import object. Concurrent submission of
multiple import jobs with same content results in creation of duplicate object records.
26
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 Extensions

When you create additional attributes for import using Application Composer, your extensions are stored in a separate
repository and are available for import and export.
Interface Tables
The import activity populates the application interface tables with your data.
Base Tables
The import activity loads your data into the base tables to complete the import.
Import Activity Source File Options: Explained

The Import Activity is 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 described in the following table.
Option Description
File Type Source file must be either Text, ZIP, or XML.

Data Type, Delimiter, and Header Row A Text file type can further be defined based on how the data is delimited and if the source file is
Included expected to include a row of headings for each column.

Import Mapping 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 table outlines the options that are available to you when locating your source file for import.
27
Option Description
Upload From
You can upload the source file from the following locations:
• Desktop
If you select Desktop, then 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.
• WebCenter Content Server
If you select WebCenter Content Server, then a File Name field with an associated
Browse button is displayed. Click and browse to search for and select the file you want to
upload.
Importing Data from a File: Procedure

Using the Manage File Import Activities task available from the Setup and Maintenance work area, you can import a wide
range of application data from text or XML files. Your import data can either create or update application records. Use the
steps outlined in this topic as a guide. The import options and other details differ by the type of data that you're importing.
Before importing, you must understand how the data in your file maps to the attributes in the application and what values are
expected as described in the related topics.
To help you get started, you can use the example templates provided in Document ID 1596128.1 on My Oracle Support. The
templates include columns for the most common application attributes and reference numbers.
Importing Data from a File

To import data from a file:
1. In the Setup and Maintenance work area, navigate to the following:
◦ Offering: Sales
◦ Functional Area: Data Import and Export
◦ Task: Manage File Import Activities
Tip: You can also navigate to the Manage Import Activities page by selecting the import task in the work
areas for objects that support importing data.
2. Click the Create icon.

3. In the Name field, enter a name for your import.
4. In the Object field, select the object that you're importing.
5. Depending on the object that you are importing, the corresponding file type is selected by default in the File Type
drop-down list. For example, Deal Registration object supports only ZIP file.
6. In the Source File region, select one of the Upload From options.
Note: If you're importing a file into one of the services, then you must upload files from your desktop.
The maximum number of records in each CSV file (either single CSV or ZIP file) should not exceed the
maximum limit of 100,000 records.
◦ Desktop
After you select this option, you must browse for the file. You must select an import file in CSV format.
28
7. If your data file includes a header row, then select the Header Row Included option. Although you can upload files
without header rows, doing so makes it more difficult to complete the mapping between the data in your file and
the application. If the values in the CSV file contain new line character, then they must be enclosed within quotation
marks.
8. If your file doesn't use a comma to separate values, then select the correct delimiter in the Data Type field.
9. You must create a mapping between the data in the import file and the target attributes in the application. If you had
previously imported a file with the same format as the file that you're importing now, then select an existing mapping
from the Import Mapping list. By default, the application saves the import mapping under the import activity name
appended with the activation date and time. If you're importing a file in this format for the first time, then you must
create the mapping in the next step.
10. If you're importing one of the following objects, then you can import attachments by selecting the Browse option
in the Attachments region and selecting a .zip or .jar file of the attachments. You must include a column with the
names of individual attachments in your import file as described in the Importing Attachments Using File-Based Data
Import: Procedure topic. Your attachment file name should not contain special characters such as the Pound symbol
or the pipe symbol (|). Do not submit File-Based Data Import jobs for the same import object because they create
duplicate object records.
The following import objects support importing a single attachment for each record:
◦ Assets
◦ Opportunities
◦ Partners
The following import objects support multiple attachments for each record:
◦ Leads
◦ Activities
11. In the Import Options region, some of the options in the following table might be available depending on the object
that you're importing.
Option Description
Import Mode For importing leads and employee resources only, you can specify whether you want to create
and update records or update them only.

If you select update, then the import process ignores any new records.

For all other import objects, both create and update operations are available.

Allowable Error Count

The Allowable Error Count threshold determines whether to automatically cancel an import if the
number of consecutive rows with validation errors exceeds the user-defined threshold value. The
default value is 2000 but you can change this value when configuring your import. During the
"Preparing Data for Import" step only, if the number of consecutive rows in your source file with
a validation error exceeds the Allowable Error Count value, then the import is canceled. If the
Allowable Error Count is not reached in this step, then the import proceeds. Errors found during
the "Importing Data" step are not counted toward the Allowable Error Count.
Validation errors include:
◦ Missing required values
◦ Values that exceed the attribute length
◦ Invalid identifiers and lookup codes
29
Option Description
Duplicates found using matching configurations for Customer Data Management objects do not
contribute to the error count.
Notification email The email of the individual who receives import processing notifications. Currently this option is
supported only for Opportunity, Lead, and custom objects.

Account Data Management Duplicates This option is available only if you have licensed data quality functionality. You can select different
options for handling duplicates when you're importing accounts, contacts, and legal entities either
alone or as part of another object.

Decimal Separator The decimal separator used in your import file.

Date Format The format of the date fields in your file.

Time Stamp Format The format of time fields in your file.

Execute Groovy Scripts and Workflows Selecting this check box enables import to trigger the execution of Groovy Scripts and Workflows
that have been configured for the object being imported. This check box is enabled only if your
source file has low-volume data records and the object to be imported supports Turbo Import.

File Encoding The overall encoding for your file.

12. Click Next.
The Create Import Activity: Map Fields page displays the attributes in your file with some sample data. If you're
reusing an import mapping, then both the Source and Target columns are already populated. The Source columns
represent your file. If you're creating a new mapping, then the Target Object and Attribute columns are blank.
Note: Oracle recommends that you use the Object Number (such as Opportunity Number) or Code (such
as Claim Code) fields when available instead of Object ID (such as Opportunity ID) fields when importing
objects.
13. For each column in your file that you want to import, select the target object and one of its attributes. The target
object and attribute name values are populated based on the display label values set in Application Composer.
Each import object comes with its own set of attributes.
If you don't want to import a column in your file then select the Ignore check box.
30
Note: Perform the following steps to view the Language Independent Code of the target attributes:
a. In the Setup and Maintenance work area navigate to the following:
• Offering: Sales
• Functional Area: Sales Foundation
• Task: Manage Administrator Profile Values
b. On the Administrator Profile Values page, search for the profile option
ZCA_IMPORT_ENABLE_LIC_COLUMN.
c. Set the Profile Value to TRUE.
d. On the Map Fields page, select Language Independent Code from the View menu.
14. To specify a constant value for an attribute in the application, then you can add the object, the attribute, and its value
in the Set Constant Values region.
If you're importing data using the import templates provided on My Oracle Support, then each column header in your
template includes the names of both the target object and the target attribute to simplify your mapping process.
15. Click Next.
Tip: To schedule the import process for a specific date, you must select the Specific Date from the
Schedule list and enter a start date.
16. Click Next.

17. Click Activate.
18. As a result of previous step, you return to the Manage Import Activities page to view the status of your import. An
import activity with a status of Completed or Completed with Errors indicates that the import activity completed.
19. During post-patching, some of the import components are in maintenance phase. Import jobs submitted during this
period are queued until the patching is complete.
20. Click the status link to see data on the success of the import, including logs and error files that are linked in the Files
Processed region. On the View Import Status page, click the file name link to download the CSV file associated
with import activity.
Viewing and Interpreting the Import Notification email

Once the import has been completed, an email is generated showing the detailed results of your import and links to any failed
operations for troubleshooting purposes. If you had specified an email in the Notification email field (in step 11) email is sent to
that address also. Included in the email are the following:
• Name of the import job and the import activity identifier

• The URL for the environment
• The object name
• Status of the import
• The Name of the import (source) file, and the type of file that was used
• Start and end times for the import (date and time)
• Elapsed time
• Record Counts: Read, Successful, Errors, Warnings
• Submitted by
31
Related Topics
• Getting Started with File-Based Import: Documentation Overview
• File-Based Data Import Objects: Explained
Importing Data with Special Characters Using File-Based Data

Import: Quick Start
This topic describes how to format your data if your import file includes special characters. You can follow the methods
described in this topic to ensure that input data is properly parsed and imported by Oracle Sales Cloud.
Building the CSV File

You can follow these steps to build your CSV file for importing the data.
1. In the Setup and Maintenance work area navigate to the following:
◦ Offering: Sales
◦ Task: Manage File Import Mappings
2. On the Manage File Import Mappings page, select the object name (say Lead object), select Seeded check box
and click Search.
3. On the Edit Import Mappings page, click Download Template to save the CSV template file to your desktop.
4. You can edit the file to include only the fields that you want to import.
Entering Data into the CSV File

After creating the CSV file, you must enter the data to import. Some of the special characters are quotation marks(") and a
comma(,). You must prefix the special characters with quotation marks(").The following list shows the various formats in which
the input data can be entered for the Lead object CSV file and how it is interpreted due to the presence of special characters.
LeadName and LeadNumber are the header fields for the file.
The following table lists five Lead records of a CSV file, each with the LeadName first, followed by the LeadNumber (120, 121,
and so on).
LeadName LeadNumber
Mark Twain lead 120

"Twain "secondary" lead" 121

Twain, Mark 122

Twain, Mark "Spring 2015" lead 123

"Twain "Fall 2014" lead 124

32
The following table provides information on how to use escape characters for the Lead Name source data records.
Row Number Source Data for How LeadName is Data with Escape How LeadName is Comment
LeadName Written to Database Characters to Written to Database Regarding Escape
if no Escape Preserve Original When Escape Characters
Characters are Data Characters are
Added Included
1 Mark Twain lead Mark Twain lead Not applicable Not applicable No escape
characters are
needed because
source data
contains no special
characters.

2 "Twain "secondary" Twain secondary" """Twain "Twain "secondary"

lead" lead" ""secondary"" lead" The two series of
lead""",121 three quotation
mark each:
• The
quotation
marks
surrounding
the entire
field which
is required
to precede
the quotation
marks in the
source data
• The
quotation
marks in the
source data
3 Twain, Mark Twain "Twain, Mark",122 Twain, Mark Double quotation

mark is required to
surround the entire
field entry because
a comma is in the
source data. No
additional escape
character is required
to precede the
comma.

4 Twain, Mark "Spring Twain "Twain, Mark Twain, Mark "Spring A double quotation
2015" lead ""Spring 2015"" 2015" lead mark is required
lead",123 to surround the
entire field entry
because at least one
special character
is in the source
data. Each double
quotation mark in
the source data
requires a double
quotation mark
escape character.
33
Row Number Source Data for How LeadName is Data with Escape How LeadName is Comment
LeadName Written to Database Characters to Written to Database Regarding Escape
if no Escape Preserve Original When Escape Characters
Characters are Data Characters are
Added Included
No additional
escape character is
required to precede
the comma.

5 "Twain "Fall 2014" Twain Fall 2014" """Twain ""Fall "Twain "Fall 2014" Although the
lead lead 2014"" lead",124 lead missing end
quotation mark
in the source
data is likely a
typo, the source
data still must
be written as is.
Thus three double
quotation marks
at the beginning,
but only a single
(surrounding) double
quotation mark at
the end.

As can be seen in the preceding table:
• If the source data contains at least one special character, then the entire field of source data must be surrounded by
double quotation marks in the CSV file.
• If the data for a field contains separator like a comma (,), then you must enclose the content within two double
quotation marks.
• If the first field has a special character at the beginning but not any matching special character at the end, then
the content of second field will also be considered as part of the first field, and the second field is blank. You must
provide a matching escape character to fix this problem.
• If you don't precede the special characters by an escape character, then the import process may write incorrect
data for a field, or incorrectly write data to the subsequent fields.
Note: Microsoft Excel and other spreadsheet programs may automatically escape the special characters.
Using Predefined Templates to Import Data Through File-Based Data

Import
This topic describes how to use predefined templates to import data using file-based data import. To import data using the
predefined templates, you must:
• Download templates you can use for import
• Understand the import templates
• Adapt the import templates to your needs
34
Downloading Templates You Can Use for Import

Oracle Sales Cloud provides templates to help you import data using File-Based Data Import tool. The templates are
spreadsheets that include the commonly used fields, in addition to the required. Each import object could have one or more
templates associated with it. The following table lists the objects and the templates for the object. Predefined mappings are
highlighted in bold.
Import Object Template Description
Account Data Cloud Account Import - Advanced Predefined mapping to import files generated
from Data Cloud and Insight service into
Oracle Sales Cloud for account enrichment.

Account Account Create and Update Predefined This mapping lets the user create or update
Mapping accounts with the most basic information.

Account Quick Create Account Predefined Mapping Predefined mapping to create Accounts with
basic information. This mapping cannot be
used to update any attribute other than those
mapped to the Account object.

Account Account Address Create and Update This mapping lets the user create or update
Predefined Mapping multiple addresses for existing accounts.

Account Account Relationship Create and Update This mapping lets users associate an
Predefined Mapping account with one or multiple contacts.

Activity Activity Predefined Mapping - Import Task Template to import activity predefined
mapping (Import Task)

Activity Activity Predefined Mapping - Import Template to import activity predefined

Appointment mapping (Import Appointment)

Contact Data Cloud Contact Import - Advanced Predefined mapping to import files generated
from Data Cloud and Insight service into
Oracle Sales Cloud for contact enrichment.

Contact Contact Create and Update Predefined This mapping lets the user create or update
Mapping contacts with the most basic information.
Additionally, this template can be used to
associate individual contacts with existing
accounts.

Contact Quick Create Contact Predefined Mapping Predefined mapping to create Contacts
with basic information. This mapping cannot
be used to update any attribute other than
the ones mapped to the Contact object.
Use Original System and Original System
Reference fields to establish the relationship
between Contacts and Accounts.

Contract Hierarchical Predefined Mapping-Contract Template to map hierarchical objects

Header, Parties and Contacts

35
Contract Contract Predefined Mapping-Contract Template to map contract objects

Header, Primary Party and Contacts

Customer Sales Team Template to import sales account resource

Sales Account Resource Team Seeded team
Mapping
Customer hierarchy Customer Hierarchy Create Predefined This template is used to create a customer
Mapping hierarchy. Customers who are part of this
hierarchy should be created first using the
"Create or update account" template.

Customer hierarchy member Customer Hierarchy Member Create This template can be used to add customers
Predefined Mapping (nodes) to an existing customer hierarchy
(tree).

Employee Resource Template to import Employee Resource with

Employee Resource Seeded Mapping - role, resource organization and hierarchy
Comprehensive information

Lead Lead Predefined Mapping Import Leads Template to import Leads with contact and
company information.

Lead Lead Predefined Mapping - Import Leads Template to import Leads with contact and
with Qualification information qualification information.

Note Note Predefined Mapping - Default required Template to import Note -Default required
Set with identifiers Set with identifiers

Note Note Predefined Mapping - Default required Template to import Note - Default required
Set with original system reference Set with original system reference

Opportunity Opportunity Predefined Mapping - Template to import Opportunity Resource

Opportunity Resource

Opportunity Opportunity Predefined Mapping - All related Template to import Opportunity with all
objects related objects.

Opportunity Opportunity Predefined Mapping - Template to import Opportunity Resource

Opportunity Resource Revenue and Revenue.

Partner Oracle Fusion Hierarchical File Import Map for Template to import Partners including child
Partner - Includes Child objects objects.

Partner Oracle Fusion Hierarchical File Import Map for Template to hierarchically import partners
Partner with minimum attributes

Partner Oracle Fusion File Import Map for Partner Template to import updates to partners
Update

36
Partner Oracle Fusion File Import Map for Partner Template to import partners with minimum
attributes

Partner Contact Oracle Fusion File Import Map for Partner Template to import partner contacts
Contacts

Partner Program Enrollments Oracle Fusion File Import Map for Enrollment Template to import updates to enrollment
Update

Partner Program Enrollments Oracle Fusion File Import Map for Enrollment Template to import enrollments with
minimum attributes

Product Group Product Group Predefined Mapping - Template to import product groups, items
Product Group Header and Child Entities related to product groups and product group
relationships used to define a hierarchy.

Quota Quota Predefined Mapping - Territory and Template to import Territory and Resource
Resource Quotas Quotas

Sales Promotion Sales Promotion Predefined Mapping - Template to import promotions and coupons
Header and Coupons associated with promotions.

Territory Template to import territory

Territory Import Seeded Map
Territory Geographies Territory Geographies Import Mapping Template to migration import territory
geographies

Territory Geographies Territory Geographies Incremental Import Template to import territory geographies
Mapping incrementally

To download an import template:

◦ Offering: Sales
2. In the Manage File Import Mappings page, select the object for which you need the template (such as Account)
from the Object drop-down list.
3. Select the Seeded check box.
4. Click Search.
5. Click the template you want to download from the search results. The Edit Import Mapping page is displayed.
6. In the Edit Import Mapping page, click Download Template.
7. Save the .csv file to a location on your desktop.
Understanding the Import Templates

You must understand the columns in the import templates to populate the templates with the correct data. To update existing
records, your source file must include the attributes that enable the import process to identify these records. These values are
37
source system and source system reference value combination, internal ID, or public unique identifiers, such as business keys
or external IDs. When the source of your data isn't an external system and you don't intend to regularly update the data, you
don't need the source system information.
Note: It is a best practice recommendation to include the source system information as requirements change
over time.
Copying and Modifying a predefined Mapping

The template file includes a header row with columns that map to the attributes for the objects. You can use the mapping
that is used to download the template and also to map columns to attributes during import. The columns are arranged in
the same order as the mapping in Oracle Sales Cloud. You can add additional attributes to the file by appending them after
the last column. In case you add additional attributes, you must copy and modify the predefined mapping to create a user-
defined mapping that includes these additional attributes. You can use the following steps to copy and modify a predefined
mapping:
◦ Offering: Sales

2. In the Manage File Import Mappings page, select the object for which you need the template (such as Account) from
the Object drop-down list.
3. Select the Seeded check box. Click Search.
4. Click the template you want to copy or modify from the search results. The Edit Import Mapping page is displayed.
5. In the Edit Import Mapping page, click Copy Mapping.
6. The target object attributes can be edited. You can also add attributes to the object by clicking Create icon.
7. click Save to save the modified template file.
Note: Perform the following steps to view the Language Independent Code of the target attributes:
◦ Offering: Sales
◦ Functional Area: Sales Foundation
◦ Task: Manage Administrator Profile Values

2. On the Administrator Profile Values page, search for the profile option
ZCA_IMPORT_ENABLE_LIC_COLUMN.
3. Set the Profile Value to TRUE.
4. On the Edit Import Mapping page, select Language Independent Code from the View menu.
Adapting the Import Templates

You may want to add additional attributes to your files to import additional information for your import data. You can review
all available attributes for your import object in a reference file located in File Based Data Import for Oracle Sales Cloud guide
available on the Oracle Sales Cloud Help Center (www.oracle.com/pls/topic/lookup?ctx=cloud&id=OEFBS). Review the
reference file to explore other attributes that are available for import and the possible prerequisite steps for those attributes.
The reference file includes the following information:
• All attributes available for your import object.
38
• The attribute descriptions, including the user interface display name for the attribute if the attribute is displayed on
the user interface.
• The data type, length, and validation logic, including the task or work area where you can view or define valid values
before importing data.
• The logic for default values, if values are not provided in your source file.
To view the reference file, see the File Based Data Import for Oracle Sales Cloud guide available on the Oracle Sales Cloud
Help Center (www.oracle.com/pls/topic/lookup?ctx=cloud&id=OEFBS).
Selecting the Template for Import Process

You can select the template that you downloaded during the import process, using the following steps:
◦ Offering: Sales

2. On the Manage Import Activities page, click the Create icon.
3. On the Create Import Activity page, provide the import name and object to import. Provide the file type, select
Header row included and Seeded check boxes.
4. On the Import Mapping drop-down list, select one of the predefined templates
5. Click Next to view the mapping and schedule the activation of import process.
Importing Attachments Using File-Based Data Import: Procedure

This topic describes how to include attachments when you use the Manage File Import Activities task.
Importing Attachments
You can use the following steps to import attachments using file-based data import:
1. Add one or more of the columns listed in the following table to the source file that you're 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.
The following table describes each of the supported column headers.
Column Header Description
ATTACHMENT_ FILE_NAME The .zip file selected when defining the import activity must contain a file with the specified
ATTACHMENT_ FILE_NAME value. Your attachment file name should not contain special
characters such as the Pound symbol or the pipe symbol (|). Otherwise, an error occurs.

ATTACHMENT_ FILE_DESC A description of the file to be attached to the record.

ATTACHMENT_ FILE_TITLE
Enter the file title. This is not a required field. If you don't specify a file title, then the Manage File
Import Activities task uses the file name as the title. For example, if the file name is abc.txt, and
39
Column Header Description

the ATTACHMENT_FILE_TITLE column value is not explicitly passed in the CSV, then it takes up
the value as abc.
ATTACHMENT_ CATEGORY_NAME Specify the attachment category. An attachment category is used to classify and secure
attachments. Each attachment UI must be defined with at least one category so that users can
add attachments. For example, you can categorize attachments for an expense report as a
receipt, scanned invoice image, and so on.

2. In each row of the source file, enter the name of the attachment file that the Manage File Import Activities task
must attach to the record.
The following table lists some attachment files for Leads. For 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




3. 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.
Note:
◦ You can specify multiple attachments for any type of business object or custom object.
◦ 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
◦ file_4.doc
You can also use a JAR file. You can organize these files in folders and subdirectories, at your discretion.
5. Sign in to the Oracle Sales Cloud application.
6. Navigate to the Setup and Maintenance work area, and then search for the Manage File Import Activities task.
7. In the Search Results list, click the link for the task..
8. On the Manage Import Activities page, click the Create icon.
9. On the Create Import Activity: Enter Import Options page, select an object from the Object drop-down list that
supports attachments. To identify the objects that support attachments, see the Prerequisites section.
40
10. In the Attachments section, click Browse, and then locate your .zip file.
Note:
◦ You can upload only one .zip file.
◦ You can't add more attachments after you upload the .zip file.
11. Enter the data in the remaining fields and activate the file-based data import activity.
The Manage File Import Activities task recognizes the reserved column header names, so you don't have to
map them in the Create Import Activity: Map Fields page. For more information about finishing this task, see the
Related Topics section at the end of this topic.
Constraints for Business Objects

You can import attachments only for the following business objects:
• Account
• Activity
• Contact
• Contract
• Campaign
• Household
• Lead
• Opportunity
• Partner
• Notes
• Sales custom object
• Common custom object
You cannot delete the file attachments from a record using file-based data import activities.
Related Topics
• Managing Attachments for Partner Objects: Explained
Import Activity Import Options: Explained

This topic describes the import options available while creating import activities.
Source File Data Transformation

The options provided in the following table are used to identify the formatting of source file data so that the data can be
correctly interpreted and transformed by the import process.
41
Option Description
Decimal Separator The format of the fractional portion of numeric values in columns mapped to attributes with a
decimal attribute type.

Date Format The format for values in columns mapped to attributes with a date attribute type.

Time Stamp Format The format for values in columns mapped to attributes with a time stamp attribute type.

File Encoding The overall encoding of the characters within the file.

Interface to Target Import Options

Depending on the object that you're importing and the application modules you implemented, you need to select some
options. All the options are provided in the following table.
Option Description
Import Mode 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. For all other import objects, both create and update operations are
available.

Allowable Error Count

The Allowable Error Count threshold determines whether to automatically cancel an import if the
number of consecutive rows with validation errors exceeds the user defined threshold value. The
default value for Allowable Error Count is 2000 but you can change this value when configuring
your import. During the "Preparing Data for Import" step only, if the number of consecutive rows in
your input file with a validation error exceeds the Allowable Error Count value, then the import will
be canceled. If the Allowable Error Count is not reached in this step, then the import will proceed.
Errors encountered during the "Importing Data" step are not counted as part of the Allowable Error
Count.
Validation errors include:
• Missing required values

• Values that exceed the attribute length
• Invalid identifiers and lookup codes
Duplicates found using matching configurations for Customer Data Management objects do not
contribute to the error count.
Notification E-Mail The e-mail of the intended recipient of import processing notifications. Currently this option is
supported only for Opportunity, Lead, and user-defined objects.

Customer Data Management Duplicates

You can select the options in the Customer Data Management LOV for handling duplicates when
you're importing accounts and legal entities either alone or as part of another object.
Note: You can use the Customer Data Management Duplicates LOV to retrieve
duplicates only if you have licensed the data quality functionality. Once licensed, you
must rebuild the keys for your matching configuration using the Manage Enterprise
Data Quality Matching Configurations task. For more information, see the Define Data
42
Option Description
Quality chapter in the Oracle Sales Cloud Implementing Customer Data Management
guide.

The duplicates are determined using the following matching configurations:
• Address Duplicate Identification

• Contact Duplicate Identification
• Account Duplicate Identification
Using this option, which is available only if you licensed the data quality functionality, you can select
different options for handling duplicates when you're importing accounts 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 an account or a legal entity object, then the 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, then 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.
• 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.
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.

Execute Groovy Scripts and Workflows Selecting this check box enables import to trigger the execution of Groovy Scripts and Workflows
that have been configured for the object being imported. This check box is enabled only if your
source file has low-volume data records and the object to be imported supports Turbo Import.

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 the following steps in the process:
43
• Mapping the Fields

• Saving the Import Mapping
• Constant Values
Mapping the 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. This is
for Text file type only.
• Generic values of Column A, Column B, and so on, if the Header Row Included option is not selected. This is for
Text file type only.
• XML tagging structure. This is for XML file type only.
The following table outlines the source columns.
Source Column Description
Column Header Represents the column header for Text file types and the tagging structure for XML file types.

Example Value Values are derived from the first source file saved with the predefined mapping. If you didn't select
a predefined mapping, then the example values are taken from the first data row in the source file
selected in the first step of the Import Activity definition.

Ignore Select this option if you don't want to import the source file data in that column.

The following table outlines the target columns.
Target Column Description
Object The group of import objects that represent the components of the business object being imported.

Attribute The attribute name that represents the corresponding interface table column for the object.

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 have selected a predefined mapping, then
the modifications made in the Import Activity to an unlocked mapping updates and saves the import activity to the predefined
mapping. If the predefined mapping is locked, then a modified mapping is 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 inherit. The value you are
setting when you configure a constant value is at the record level. For example, if a source file doesn't contain a column for
business unit and all of the objects in the file belong to the same business unit, then enter a constant value for the object and
44
business unit attribute. Each imported record has the specified attribute set to the constant value. The Constant value takes
precedence over any values mapped or ignored in the Map Fields section. This value applies to all import file types.
Related Topics
• Exporting and Importing Data Between Oracle Sales Cloud Instances Using Automatic Mapping: Procedure
• File-Based Import Mapping: Explained
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 Description
Queued for import The import request is queued for processing.

Preparing data for import The data is being staged to be imported.

Importing data The data is being validated and imported.

Importing attachments The attachments are stored in the file repository. This step is displayed only if the object being
imported supports the import of file attachments.

Completing import activity The cleanup tasks, such as the generation of log files, are in progress.

Completed All records were processed and loaded into the application tables.

Completed with errors 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.

Completed with warnings The import activity found warnings (but no errors) in the data file. You can view details about the
warnings by clicking the status link.

Unsuccessful The import activity encountered system error and the import is unsuccessful.

Related Topics
File-Based Import Monitoring: Explained

This topic explains how to 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 the
45
necessary updates for any failed records that you want to import again. You can also filter the import activities that are in
different states.
You can view the list of import activities from the Manage Import Activities page. You can filter the import activities based on
the status of the activity, file type, name of the activity, activity identifier, object name, or name of the import mapping used.
To filter,
1. Click the Query By Example icon This brings up the text boxes on each column header.
2. Enter the filter criteria in text boxes to filter the records. For example, you may want to filter all import activities that
are in the status Completed.
3. Select the import activity that you want to monitor by clicking the link in the corresponding Status column. The View
Import Status page is displayed, that shows status of the most recently executed instance of the import activity
definition. The View Import Status page contains the following sections:
◦ Files Processed (Import Processes in the case of multiple CSV files)
◦ Import Activity Progress
◦ Process Log
Files Processed
The Files Processed section displays a row for each source file that is processed, in the case of single CSV files. The import
processing details for single CSV files are summarized and displayed for each source file. The following table provides the
details of the import processing.
File Processing Summary Information Description
Records Read From File The number of rows in the CSV file.

Records Uploaded with Format Errors The number of records that were uploaded with format errors when processing data to insert
into the interface tables from the source file. View the error details in the Exception and Error files
attached to the process.

Records Failed with Errors The number of records that failed with errors 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.

Records Uploaded Successfully The number of import object records that were 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.

Records Uploaded With Warnings The number of records that were uploaded with warnings when importing data from the interface
tables to the destination application tables.


Records Read From File The number of records read from the source file.

Attachments
Once an Import Activity process has completed, processing reports are included in the Attachments
column. This column displays the log file in case of successful import, and error and exception file
in case of failure. The Log file includes the records that were successfully imported plus the unique
destination application table identifiers for the objects. The Exception file includes a row for each
46

record that failed. All the errors for that row are concatenated and displayed in the Error Message
column of the file. The Error file includes all the errors for each record that failed validation.
In the event that log generation was not completed for an import activity, you can click the
Generate Log link to generate the import log files. Once the request is submitted, you get a
confirmation message. The Generate Log link is displayed in the Attachments column.
The following are the contents of each file:
• Log files contain records that were successfully imported plus the unique destination
application table identifiers for the objects.
• Exception files include a row for each record that failed. All the errors for that row are
concatenated and displayed in the Error Message column of the file.
• Error files include all the errors for each record that failed validation.
Submitted By The value of the user who last submitted an import using the import definition.

In the case of multiple CSV files, the Import Processes section displays a row for each source file that is processed. The
following table provides the details of the import processing.
Records Read From File The number of records read from the source file.

Records Uploaded with Format Errors The number of records that were uploaded with format errors when processing data to insert
into the interface tables from the source file. View the error details in the Exception and Error files
attached to the process.

Records Failed with Errors The number of records that failed with errors 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.

Records Uploaded Successfully The number of import object records that were 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.

Rejected Data File The data files that were rejected due to format errors.

Error File
Once an Import Activity process has completed, error files are included in the Error File column.
This column displays error and exception files in case of failure, and is blank in case of successful
import. The Exception file includes a row for each record that failed. All the errors for that row are
concatenated and displayed in the Error Message column of the file. The Error file includes all the
errors for each record that failed validation.
In the event that log generation was not completed for an import activity, you can click the
Generate Log link to generate the import log files. Once the request is submitted, you get a
confirmation message. The Generate Log link is displayed in the Error File column.
47
The following are the contents of each file:
• Exception files include a row for each record that failed. All the errors for that row are
concatenated and displayed in the Error Message column of the file.
• Error files include all the errors for each record that failed validation.
Records Uploaded With Warnings The number of records that were uploaded with warnings when importing data from the interface
tables to the destination application tables.

Submitted By The value of the user who last submitted an import using the import definition.

Note: In the files that are generated after the completion of an import activity, all error message values are
enclosed within double quotation marks. The use of double quotation marks improves the format of the log files
by ensuring that the error messages containing commas are not treated as multiple values.
Import Activity Progress

From the Import Activity Progress 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 about processing steps within each underlying process. The
various steps involved in the import activity are summarized in the following table.
Step Name Description
Import activity queued The import activity that is to be processed is being queued.

Preparing data for import The data in the source files is being prepared for importing into the database.

Importing data The data is being imported into the database. This step also displays a count of the total number of
substeps that are performed during the data loading process. The number of substeps required to
load the data varies for each object.

Importing attachments The application is importing attachment files and is associating them to the appropriate records. This
step is only displayed if the object being imported supports the import of file attachments.

Completing import activity The import log files are generated and internal import activity cleanup tasks are executed.

Process Log
The Process Log section displays the log messages that are generated during the processing of an import activity. You can
filter the log messages based on the message types Information, Error and Debug. You can also export the log information
into an excel file.
Import Consumers Using File-Based Import
48
Importing Consumers: 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 consumer import object lets you import all information about a consumer, such as
the consumer profile, consumer address information, consumer contact point information, and consumer contact preference
information.
Note: The Consumer object is only applicable if you are using a prior release. All capabilities of the Consumer
object are now included in the Contact object. If you are upgrading from a prior release, then it is recommended
that you use the Contact object to update your consumer information using File-Based Data Import.
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 configure 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 so that you can map your
legacy data to the data that Oracle Sales Cloud requires. 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 e-mail, 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.
Consumer Profile
Instant Additional SellTo Primary Sales

Mobile Email Fax
Messenger Name Address Phone AccountProfile
Mobile Email PrimaryPhone Fax

Contact Contact Contact Contact
Preference Preference Preference Preference
49
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 e-mail, 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.
You must understand the attribute details of the import object so that you can prepare your import data. You can use
reference guide files that contain attribute descriptions, values that populate attributes by default when you do not provide
values, and validation information for each of the Oracle Fusion Applications attribute. The validation information includes the
navigation path 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.
Configurable Attributes
If you want to configure the Oracle Sales Cloud 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 configurable attributes, which you
can then map to your source file data. You can use the same source file to import both configurable 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 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. When you're creating a new consumer, you import the Consumer import object.
You must be assigned the Customer Relationship Management Application Administrator or Marketing Operations Manager
job role to access and submit the import activities for consumers.
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, e-mail, sell-to address, and primary phone for the
consumer.
Verifying Your Imported Data

Oracle Sales Cloud Applications provide File-Based Import activity reports, which you can use to verify imported data. 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.
50
Related Topics
• Extending Oracle Sales Cloud: How It Works
Consumer Import Objects: How They Work Together

The Consumer import object lets you import consumers, their detailed information, and contacts related to the consumer.
This topic introduces the following:
• Target objects for the Consumer import object
• Target import object attribute
• Target object attribute reference guide files
Note: The Consumer object is only applicable if you are using a prior release. All capabilities of the Consumer
object are now included in the Contact object. If you are upgrading from a prior release, then it is recommended
that you use the Contact object to update your consumer information using File-Based Data Import.
You use the Consumer import object to import consumer information. It 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 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, e-mail, 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 with their
valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use a reference
file. See the File Based Data Import for Oracle Sales Cloud guide available on the Oracle Sales Cloud Help Center (https://
docs.oracle.com/en/cloud/saas/index.html). In the File Based Data Imports chapter, see the topic for your import object of
interest, which includes links to reference files for target import objects. A 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 prerequisite 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 Manage File Import Mappings
task, or you can define the mapping when you define the import activity using the Manage File Import Activities 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 features for the consumer.
51
Reference Files for Target Import Object Attributes

To access reference files for this object's target import objects, see the File Based Data Import for Oracle Sales Cloud guide
available on the Oracle Sales Cloud Help Center (https://docs.oracle.com/en/cloud/saas/index.html). In the File Based Data
Imports chapter, see the topic for your import object of interest, which includes links to reference files for target import
objects.
The following table lists the reference files that are available for the various target import objects.
Target Import Object Description Reference Guide File Names
PersonProfile Includes detailed person information such as HZ_ IMP_ PARTIES_ T_Reference
person name, relationship type, gender, and
marital status.

SellToAddress Includes consumer addresses and party HZ_ IMP_ PARTYSITES_T_ Reference
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.

PrimaryPhone Indicates the primary phone number of the HZ_ IMP_ CONTACTPTS_T_ Reference
consumer. If the consumer has multiple
phone numbers, one of the phone numbers
is designated as the primary phone number.

Mobile Indicates the mobile phone number of the HZ_ IMP_ CONTACTPTS_T_ Reference
consumer.

Fax Indicates the fax number of the consumer. HZ_ IMP_ CONTACTPTS_T_ Reference

Email Indicates the e-mail of the consumer. HZ_ IMP_ CONTACTPTS_T_ Reference

InstantMessenger Indicates the instant messenger or social HZ_ IMP_ CONTACTPTS_T_ Reference
networking information of a consumer.

SalesAccountProfile Includes detailed information about a ZCA_ IMP_ SALES_ ACCOUNTS_ Reference
consumer sales account. A sales account
is a specific sell-to entity within a given
consumer. A consumer can have multiple
sales accounts and sales account profiles.

AdditionalName Indicates alternative name of a consumer. HZ_ IMP_ ADDTNLPARTYNAMES_ T_

Reference

Classification Includes classification information for a HZ_ IMP_ CLASSIFICS_T_ Reference

consumer. Classification lets you categorize
entities such as parties, projects, tasks, and
orders as hierarchies.

52
AdditionalIdentifier Includes detailed information about an HZ_ IMP_ ADDTNLPARTYIDS_ T_ Reference

additional identifier for a consumer.

Relationship Includes information about a relationship HZ_ IMP_ RELSHIPS_T_ Reference

between the consumer and another entity,
such as an organization or a person.

PrimaryPhoneContactPreference Indicates the consumer's preference about HZ_ IMP_ CONTACTPREFS_ Reference
being contacted through phone.

MobileContactPreference Indicates the consumer's preference about HZ_ IMP_ CONTACTPREFS_ Reference
being contacted through mobile phone.

FaxContactPreference Indicates the consumer's preference about HZ_ IMP_ CONTACTPREFS_ Reference
being contacted through fax.

EmailContactPreference Indicates the consumer's preference about HZ_ IMP_ CONTACTPREFS_ Reference

Related Topics
Import Contacts Using File-Based Import

Importing Contacts: 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 an individual who is a customer or a prospect, or a contact for an existing
customer or consumer, or a contact that does not yet have an established business association with a customer or
consumer. Thus, a contact could be an employee of a customer organization, a person you may have met who could help
with your business, or a prospective or current individual customer. 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, e-mail
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 account objects.
Consider the following questions when importing your data:
• How does your legacy system or source system represent the contact compared to how Oracle Sales Cloud
• Do you have to configure values in Oracle Sales Cloud to map to your data values?
• Do you have to configure Oracle Sales Cloud to capture additional attributes that are critical to the way you do
business?
53
• How do you verify your imported data?

You must understand how your contact data corresponds with the data in Oracle Sales Cloud so that you can map your
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, e-mail IDs,
Web site addresses, or instant messenger IDs.
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 e-mail.
Note: All contact-related entities, such phone or e-mail, 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.
To facilitate importing contacts, Oracle Sales Cloud incorporates the structure of the contact business object into import
objects. The import object for contacts is Contact.

one-to-many relationships between the structural components that make up the contact.
You must understand the attribute details of the import objects so that you can prepare your import data. You can use
values, and validation information for each attribute. The validation information includes the navigation path 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 topic listed in the following table.
Import Object Related Import Object Topic
Contact Contact Import Objects: How They Work Together

Note:
You can use the keyword importing contacts to search for related topics in Oracle Sales Cloud help.
54
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 a file-based import. The file-based import process reads the data in your source file, populates
the interface tables according to your mapping, and imports the data into the application destination tables.
for each import object. When you're 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.

can also access the Customer Center or Partner Center work area to view the contact information that you have imported.
Related Topics
• Contact Import Objects: How They Work Together
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 objects for the Contact import object
• Target import object attributes
• Reference guide files for target import object attributes
Contact Target Import Objects

You use the contact import object to import contact and information. The contact import object is split into separate target
import objects for organizing the individual attributes of the contact and the contact's relationship with other parties.
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 and contact
55
preference information: PersonProfile, Fax, PrimaryPhone, Url, SalesProfile, Classification, AdditionalName, Relationship, and
AdditionalIdentifier.
To update or create a contact point for a contact relationship, use the following target import objects: ContactRelationship,
ContactJob, ContactAddress, ContactEmail, ContactPhone, ContactMobile, ContactInstantMessenger, and ContactFax.
All contact-point-related entities, such as phone or e-mail, include a child entity that captures the contact preference. For
example, the ContactPhoneContactPreference entity captures the contact preference of the primary phone contact method.
Target Import Object Attributes

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 Manage File Import Mappings task, or
you can define the mapping when you define the import activity using the Manage File Import Activities 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 configuration features for the contact object.

objects.
PersonProfile Includes information that identifies a contact, HZ_ IMP_ PARTIES_ T_Reference
such as first name, last name, date of birth,
and so on.

SalesProfile Includes detailed information about a sales ZCA_ IMP_ Sales_ Accounts_ Reference
profile. A sales profile is a specific sell-to
entity within a given account. An account or
contact can have multiple sales profiles.

Fax Contact's fax number. HZ_ IMP_ CONTACTPTS_ T_Reference

FaxContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through Fax.

Phone Contact's phone number. If the contact has HZ_ IMP_ CONTACTPTS_ T_Reference
multiple phone numbers, then the first phone
number is designated as the primary phone
56

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.

PhoneContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
by phone.

Email Contact's e-mail. HZ_ IMP_ CONTACTPTS_ T_Reference

EmailContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through e-mail.

InstantMessenger Contact's instant messenger information. HZ_ IMP_ CONTACTPTS_ T_Reference

Mobile Contact's mobile number. HZ_ IMP_ CONTACTPTS_ T_Reference

MobileContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through mobile phone.

Classification Contact's classification information. HZ_ IMP_ CLASSIFICS_ T_Reference

Classification lets you categorize entities,
such as parties, projects, tasks, and orders
as hierarchies.

Address Contact's address. If the contact has HZ_ IMP_ PARTYSITES_ T_Reference
multiple addresses, then the first address is
designated as the primary address.

AddressContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
at the primary address.

AdditionalName Contact's alternative name. HZ_ IMP_ ADDTNLPARTYNAMES_

T_Reference

AdditionalIdentifier Includes the basic information about an HZ_ IMP_ ADDTNLPARTYIDS_ T_Reference
additional identifier for the contact.

ContactRelationship Includes information about a relationship HZ_ IMP_ RELSHIPS_ T_Reference

between the contact and other parties.

ContactEmail Contact's e-mail contact point. HZ_ IMP_ CONTACTPTS_ T_Reference

ContactEmailContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through the e-mail contact point.

ContactFax Indicates the number of the fax contact point HZ_ IMP_ CONTACTPTS_ T_Reference
of the contact.

57
ContactFaxContactPreference Contact's preference about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through the fax contact point.

ContactInstantMessenger Contact's instant messenger contact point. HZ_ IMP_ CONTACTPTS_ T_Reference

ContactMobile Contact's mobile contact point. HZ_ IMP_ CONTACTPTS_ T_Reference

ContactMobileContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through the mobile phone contact point.

ContactPhone Contact's phone contact point. If the contact HZ_ IMP_ CONTACTPTS_ T_Reference
has multiple phone numbers, then the first
phone number is designated as the primary
phone number.

ContactPhoneContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through the phone contact point.

ContactAddress Contact's address contact point. If the HZ_ IMP_ PARTYSITES_ T_Reference
contact has multiple addresses, then the
first address is designated as the primary
address.

ContactAddressContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
at the address contact point.

ContactJob Contacts' job information. HZ_ IMP_ CONTACTS_ T_Reference

Related Topics
Import Country Structures Using File-Based Import

Importing Country Structures: Explained
This topic explains how to prepare and import country structure data from an external data source 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 as the topmost level, followed by the County, then the City,
and finally the Postal Code.
You can use the country structure to set up the following:
• The relationships between geographies within a country
58
• The types of geographies that you can define for a country

• How does your legacy system or source system represent the geography data compared to how the application
• Do you have to configure values in the application to map to your data values?
• Do you have to configure the application to capture additional attributes that are critical to the way you do business?

You must understand how your country structure data corresponds with the data in the application so that you can map your
legacy data to the data that the application requires. First, you must understand how the application 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're 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 importing country structures, the application incorporates the structure of the country structure into import
objects. The import object for country structures is GeoStructureLevel.

Each import object is a collection of attributes that helps to map your data to the application data and to support one-to-
many relationships between the structural components that make up the country structure.
You must understand the attribute details of the import objects so that you can prepare your import data. . You can use
reference guide files that contain attribute descriptions, values that populate attributes by default when you don't provide
you can define values in the application. For example, if you have values in your data that correlate to a choice list in the
application, then the validation information for that attribute provides the task name in the Setup and Maintenance work area
where you can define your values.
If you need to configure the application object to import your legacy or source data, you must use the 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 configurable attributes, which can then be
mapped to your source file data. You can use the same source file to import both configurable 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 a file-based import. The file-based import process reads the data in your source file,
for each import object. When you're creating a new country structure, you import the Country Structure object. You must
59
be assigned the Master Data Management Administrator job role to access and submit the import activities for country
structures.

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.
Related Topics
• Country Structure Import Objects: How They Work Together
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 objects for the Country Structure import object

Country Structure Target Import Objects

The Country Structure import object contains one target import object. The target import object 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.

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.
60

objects.
For detailed information on importing geographies using file-based import, refer to Document No. 1481758.1, Importing
Master Reference Geography Data, on the Oracle Support site.
The following table lists the reference file for the ImpGeoStructureLevel target import object.
Target Import Object Description Reference File Names
ImpGeoStructureLevel Information that specifies a country's HZ_ IMP_ GEO_STRUCTURE _ LEVELS_

geography structure. Reference

Related Topics
• Importing Country Structures Using File-Based Import: Explained
• Importing Country Structures Using File-Based Import: Quick Start
Import Customer Hierarchies Using File-Based Import

Importing Customer Hierarchies: Explained
This topic describes how to import a customer hierarchy and customer hierarchy members. A customer hierarchy captures
the hierarchical relationships that an account has with other accounts. A customer hierarchy consists of hierarchy members.
A customer hierarchy can be used to process payments from one account and apply them to another account 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
accounts in a hierarchy.
Consider the following questions when importing customer hierarchy information:
• Are all members of the customer hierarchy in Oracle Sales Cloud?
• Do you 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 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 Hierarchy
import object?
business?
61
• How do you verify my imported data?
To import a customer hierarchy, you must:
1. Import accounts that 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 accounts into the hierarchy.

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 account object structure of Oracle Sales Cloud. You must understand how Oracle Sales Cloud represents
the structure of the data for a customer hierarchy.
The customer hierarchy import object structure is hierarchical. At the upper 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 and customer hierarchy nodes, such as the hierarchy type, hierarchy code,
hierarchy name, and hierarchy version.

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 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 customer hierarchy.
You must understand the attribute details of the import objects so that you can prepare your import data. Reference files with
detailed attribute information are provided in the File Based Data Import for Oracle Sales Cloud guide that is available on the
Oracle Sales Cloud Help Center (https://docs.oracle.com/cloud/latest/salescs_gs/docs.htm).
Reference files contain attribute descriptions, values that populate attributes by default when you don't provide values, and
validation information for each attribute. The validation information includes the navigation path 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.
If you want to configure the import object to import your legacy or source data, then you must use Application Composer
available for importing.
The corresponding import object is updated with the configurable attributes, which you can then map to your source file data.
You can use the same source file to import both configurable 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 a file-based import. The file-based import process reads the
data 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.
62
When importing customer hierarchy information, you first import the customer hierarchy information and then the customer
hierarchy members for the customer hierarchy. When importing customer hierarchy members, you must provide the parent
reference information that refers to the customer hierarchy of the member.

Oracle Sales Cloud provides 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 Manage Hierarchies task from Setup and
Maintenance to view the customer hierarchy information that you have imported.
Related Topics
• Hierarchies: Explained
• Customer Hierarchy Import Objects: How They Work Together
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 objects for the customer hierarchy import object
Customer Hierarchy 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.
3. Import existing customers as customer hierarchy members into the hierarchy.

file. See the File Based Data Import for Oracle Sales Cloud guide . In the File Based Data Imports chapter, see the topic for
your import object of interest, which includes links to reference files for target import objects. A 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 prerequisite setup tasks that are required.
63
review the Application Composer extensibility features for the customer hierarchy.

objects. The following table lists the reference files that are available for the target import objects.
CustomerHierarchy Customer hierarchy definition and root node HZ_ IMP_ HIERARCHIES_T _Reference
of the customer hierarchy

CustomerHierarchyMember Customer hierarchy members HZ_ IMP_ HIERARCHY_ NODES_ Reference

Related Topics
• Importing Customer Hierarchy Using File-Based Import: Explained
Importing Customer Hierarchies Using File-Based Import: Quick Start

This topic describes a few key concepts and provides guidance to get you started on importing customer hierarchies. It
includes the following information:
• Customer hierarchy overview

• Identifying and associating records
• The minimum data required and the prerequisite steps
• How to access and use reference files to evaluate attributes
• Additional tips
The following table lists the file-based import objects and target objects that you can use to import customer hierarchies.
Import Object Target Objects
Customer Hierarchy CustomerHierarchy

64
Customer Hierarchy Overview

A customer hierarchy captures the hierarchical relationships that a customer has with other customers, and 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 can create multiple versions of a customer hierarchy; however, only one hierarchy version can be active on a specific
date. You can create a new hierarchy to represent the structure of a new customer. If the customer has made minor changes
to its organization, you can create a new version rather than edit the existing one.
Identifying and Associating Records with Each Other

To update an existing customer hierarchy, your source file must include values that enable the import process to identify the
existing records. These values will be either a source system and source system reference value combination or an Oracle
Fusion record ID.
If the source of your data is a third party or external system, and you intend to import updates to previously imported records
from the same system, you can provide the source system code and the unique reference value for the party record in your
source system. Oracle Fusion stores a cross-reference between the source system information and Oracle's record ID. To
add a sales account profile to an existing party, you provide the source system code and reference values and the import
process uses the value combination to identify the existing party record in Oracle Fusion.
You can set up source systems to identify the source of the data you are importing. Source systems are external sources of
data that are used to import data into Oracle Sales Cloud. Source system references are used by the application to create
references between source IDs and the Oracle Sales Cloud database IDs. You can configure source systems either by using
the Manage Trading Community Source System task or by importing the source system information into Oracle Sales
Cloud using the Source System Reference import object.
When the source of your data is not an external system and you want to add a sales account profile to an existing party,
you need the Oracle Fusion party record ID in your source file. The import process uses the record ID to identify the existing
record. When the source of your data is not an external system and you do not plan to regularly update the data, you do not
need the source system information. To import updates to your existing data, you can export the Oracle Fusion record ID and
add it to your source file. The import process uses the record ID to identify the existing record.
Minimum Data Required and the Prerequisite Steps

The minimum data that is required to import customer hierarchy information depends on the following:
• The purpose of the import. The data requirements are different when you're creating a customer hierarchy or when
you're updating a customer hierarchy record.
• The data requirements are different when using source system information or record IDs to identify and associate
records.
The values that you provide in your source file may require a setup task or manual steps to ensure that the information passes
the import validation. Before you prepare your source file, complete the prerequisite steps to determine the data values, and
then include those values in your source file. The following table lists the minimum attributes required to import customer
hierarchies based on two possible scenarios for your import, any prerequisite setup or manual steps needed to prepare your
data, and the import attributes that you use to map your data to Oracle Fusion. You can optionally include attributes that are
available for import in your import file but that aren't listed in the table.
65
Attribute Description Prerequisite Setup Task Creating Party and Creating Customer
Customer Hierarchy Hierarchy Record for an
Records in the Same Existing Party
Batch
Language Indicates the code of View valid language Conditionally required. Conditionally required.
the language into which codes from the Setup
the contents of the and Maintenance, Required when creating Required when creating
translatable columns are Manage ISO Languages a new hierarchy (tree a new hierarchy (tree
translated. task. version). version).

Default is US if not
specified.

SourceLangFlag This check box indicates No setup task required. Conditionally required. Conditionally required.
whether the language
specified by the Required when creating Required when creating
Language attribute is a new hierarchy (tree a new hierarchy (tree
the source language in version). version).
which the contents of this
record are being created
or were originally created.

HierarchyType Unique Identifier for a tree Tree structure can be Required Required
structure. created and managed
using the Setup and
Maintenance, Manage
Tree Structures task.

HierarchyCode User-defined identifier for If the import object is Required Required

a tree. Employee resource,
then HiearchyCode must
be 'GLOBAL_ SALES_
MARKETING' else the
value is free text.

HierarchyName The name of the tree. No setup task required. Required Required

HierarchyVersionName The name of the tree No setup task required. Conditionally required. Conditionally required.
version.
Required when creating a Required when creating a
hierarchy (tree version). hierarchy (tree version).

ActionCode This attribute specifies Use the UPDATE value Conditionally required. Conditionally required.
to insert or to delete the when updating a record.
hierarchy (tree version). If If deleting an existing The value DELETE The value DELETE
provided, valid values are record, use the value, is required if you are is required if you are
INSERT, UPDATE, and DELETE. If inserting a deleting an existing deleting an existing
DELETE. record, use the value hierarchy (tree version). hierarchy (tree version).
INSERT.

AsOfDate The date that is used No setup task required. Conditionally required. Conditionally required.
to determine the tree
version to delete when A value is required if A value is required if
ActionCode is provided deleting an existing deleting an existing
as DELETE. Only one hierarchy (tree version). hierarchy (tree version).
version is active on any
given date.

66
Using Reference Files to Evaluate Attributes

For information about available import attributes, see the File Based Data Import for Oracle Sales Cloud guide available on the
Oracle Sales Cloud Help Center (https://docs.oracle.com/en/cloud/saas/index.html). In the File Based Data Imports chapter,
see the topic for your import object of interest, which includes links to reference files for target import objects.
Review a reference file to see attributes that are available to import and information for each attribute, including requirement
for inclusion in an import, validation requirements, default value, data type, data length, and description.
Additional Tips
Tip: You can explore related topics by entering the following keywords in the Oracle Fusion Help Application search. The Help
Application is available from any Oracle Fusion Application page by clicking Help and selecting Applications Help.
• Importing customer hierarchies.

• Importing customer hierarchy members.
Tip: If your data is not from a source system, then you can emulate a system by defining a source system and manually
generating reference values for your data. For example, if you periodically gather information at sales events or through sales
calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might
concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.
Related Topics
• Importing Customer Hierarchy Member Using File-Based Import: Quick Start
Importing Customer Hierarchy Member Using File-Based Import:

Quick Start
This topic describes a few key concepts and provides guidance to get you started on importing customer hierarchy
members. It includes the following information:

• Additional tips
The following table lists the file-based import object and target object that you can use to import customer hierarchy
members.
Import Object Target Object
Customer Hierarchy Member CustomerHierarchyMember

hierarchy members.
67

To update an existing customer hierarchy member, your source file must include values that enable the import process to
identify the existing records. These values will be either a source system and source system reference value combination or
an Oracle Fusion record ID. If the source of your data is a third party or external system, and you intend to import updates to
previously imported records from the same system, then you can provide the source system code and the unique reference
value for the party record in your source system. Oracle Fusion stores a cross-reference between the source system
information and Oracle's record ID. To add a sales account profile to an existing party, you provide the source system code
and reference values and the import process uses the value combination to identify the existing party record in Oracle Fusion.
Minimum Data Required and the Prerequisite Setup Tasks

The minimum data that is required to import customer hierarchy member information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the party and the
customer hierarchy member in the same import batch, adding customer hierarchy member to an existing party, or
updating a customer hierarchy member record.
• Identifying and associating records. The data requirements are different when you're using source system
information or record IDs to identify and associate records.
Attributes that are available for import in your import file but that aren't listed in the table. For each attribute, the prerequisite
setup task before importing that attribute is listed in the following table.
Customer Hierarchy Hierarchy Member
Member Records in the Record for an Existing
Same Batch Party
to insert or to delete when updating a record.
the hierarchy node (tree If deleting an existing A value is required if A value is required if
node). This attribute is record, use the value, deleting an existing deleting an existing
typically used only to DELETE. If inserting a hierarchy node. hierarchy node.
delete a record. record, use the value
INSERT.

AsOfDate When ActionCode is No setup task required. Conditionally required. Conditionally required.
provided as DELETE,
AsOfDate determines the A value is required if A value is required if
tree version from which deleting an existing deleting an existing
to delete the hierarchy hierarchy node. hierarchy node.
node. Only one version is
active on any given date.

68
Same Batch Party
using the Setup and
Maintenance, Manage

HierarchyCode User-defined identifier for HierarchyCode must Required Required

a tree. exist in the FND_TREE
table, column TREE_
CODE or, if the hierarchy
is being created in the
same batch as this node,
then HierarchyCode
must exist in HZ_ IMP_
HIERARCHIES_ T table
(the interface table for
the new hierarchy),
column TREE_ CODE
(the HierarchyCode
attribute for a hierarchy
import).

PartyOrigSystem The source system Predefine your source Conditionally required. Conditionally required.
code that identifies system code as enabled
the original source for parties, using the If deleting an existing If deleting an existing
system of the party Setup and Maintenance, node, then identify node, then identify
that you are inserting Manage Trading the node by providing the node by providing
as a new node or that Community Source either PartyId or both either PartyId or both
exists as the node to be Systems task. PartyOrigSystem and PartyOrigSystem and
deleted. You provide the PartyOrigSystemReference. PartyOrigSystemReference.
source system reference
(PartyOrigSystemReference)
and the source system
code (PartyOrigSystem)
when the source of your
data is your legacy or
external system. The
import process uses
the source system code
and source system
reference values to: * find
the Oracle Sales Cloud
internal ID (PartyId) that
uniquely identifies an
existing party record that
was originally imported
with the source system
reference and source
system code values in a
prior batch. The party is
either being inserted as a
new node or is a node to
be deleted in this batch.

PartyOrigSystemReference The ID that identifies the Identify the reference Conditionally required. Conditionally required.
party that is the parent value from your source
node of this node in system that was used If you're creating If you're creating
your legacy or external when you imported the a new node, then a new node, then
69
Same Batch Party
system. You provide the party in a prior batch, identify the parent node identify the parent node
source system reference or identify the source by providing either by providing either
(ParentPartyOrigSystemReference)
system reference you will ParentPartyId or both ParentPartyId or both
and the source use when importing the ParPartyOrigSystem and ParPartyOrigSystem and
system code party in the same batch ParPartyOrigSystemReference.
ParPartyOrigSystemReference.
(ParentPartyOrigSystem)
import process uses
and source system
internal ID (ParentPartyId)
that uniquely identifies
the existing parent
node (party record) that
system code values
in a prior batch. * find
for the new parent node
system code values that
is imported in the same
batch as this node.

PartyId The unique internal ID You can obtain the Conditionally required. Conditionally required.
of the existing party Party ID for an existing
record that is either being party by exporting the If deleting an existing If deleting an existing
inserted as a new node Party object using the node, then identify node, then identify
or is an existing node to Setup and Maintenance, the node by providing the node by providing
be deleted in this batch. Manage Bulk Data either PartyId or both either PartyId or both
Export, Schedule Export PartyOrigSystem and PartyOrigSystem and
Processes task. PartyOrigSystemReference. PartyOrigSystemReference.

ParentPartyId The unique internal ID for You can obtain the Conditionally required. Conditionally required.
the existing party record Parent Party ID for
that is the parent node of an existing party by If you're creating a new If you're creating a new
this node. exporting the Party node or deleting an node or deleting an
object using the Setup existing node, and the existing node, and the
and Maintenance, node is not the root node node is not the root node
Manage Bulk Data of the hierarchy, then you of the hierarchy, then you
Export, Schedule Export must identify the parent must identify the parent
Processes task. node by providing either node by providing either
ParentPartyId or both ParentPartyId or both
ParPartyOrigSystem and ParPartyOrigSystem and

ParentPartyOrigSystem The source system Predefine your source Conditionally required. Conditionally required.
code that identifies the system code as enabled
original source system for parent parties, If you're creating If you're creating
of the party that is the using the Setup and a new node, then a new node, then
70
Same Batch Party
parent node of this Maintenance, Manage identify the parent node identify the parent node
node. You provide the Trading Community by providing either by providing either
source system reference Source Systems task. ParentPartyId or both ParentPartyId or both
and the source ParPartyOrigSystemReference.
system code
import process uses
and source system
the existing parent
system code values
batch as this node.

ParentPartyOrigSystemReference
The ID that identifies the Identify the reference Conditionally required. Conditionally required.
your legacy or external when you imported a new node, then a new node, then
system. You provide the the parent party in a identify the parent node identify the parent node
source system reference prior batch, or identify by providing either by providing either
the source system ParentPartyId or both ParentPartyId or both
and the source reference you will use ParPartyOrigSystem and ParPartyOrigSystem and
system code when importing the ParPartyOrigSystemReference.
(ParentPartyOrigSystem) parent party in the same
when the source of your batch.
import process uses
and source system
the existing parent
system code values
71
Same Batch Party
batch as this node.


For information about available import attributes, see the File Based Data Import for Oracle Sales Cloud guide available on
the Oracle Sales Cloud Help Center (https://docs.oracle.com/en/cloud/saas/index.html). In the File Based Data Imports
chapter, see the topic for your import object of interest, which includes links to reference files for target import objects.
Additional Tips

Related Topics
• Importing Customer Hierarchies Using File-Based Import: Quick Start
Import Customers Using File-Based Import

Importing Customers: Explained
This topic explains how to prepare and import account data from an external data source into Oracle Sales Cloud using the
File-Based Data Import feature. An account is an entity with whom you have a selling relationship. Oracle Sales Cloud refers
to sales profile and sales prospects collectively as an Account. An account business object lets you capture all information
about an account, such as the account profile, account contact relationships information, and account contact points.
72
A sales profile is a specific sell-to entity within a given account. You can create leads and opportunities for sales profiles. An
entity with a sales profile 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.
• Account: A sales profile 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 Account import object to import sales profiles or sales prospects of the type organization. You can use the
Household import object to import accounts of the type household, and the Contact import object to import accounts of the
type person. 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 profiles?
• How does your legacy or source system represent the account information compared to how Oracle Sales Cloud
• Do you have to configure values in Oracle Sales Cloud to map your existing data values to the Account import
object?

You must understand how your account data corresponds with the data in Oracle Sales Cloud so that you can map your
structure of the data for an account.
The Account 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 profiles. These child entities
components that make up the account.
73
The following figure shows the account object and its child entities.
Organization Profile
Primary Contact SellTo Sales Additional

Classification Address Url Fax
Phone PersonProfile Address Profile Name
PrimaryPhone Address Address Fax

ContactPreference ContactPreference Purpose ContactPreference

Primary Primary Additional Instant
Job Email Mobile Fax
Phone Address Name Messenger
Contact Contact Contact Contact Contact

PrimaryPhone PrimaryAddress Email Mobile Fax
Preference Preference Preference Preference Preference
The organization profile contains basic information about the account, such as the customer name and party usage. For each
account, you can assign classifications, contacts, sell to addresses, phone details, and additional names. The contact of the
account, in turn, includes other child entities that capture information about the contact, such as contact job, contact primary
phone, contact primary address, and contact e-mail.
Note: All contact entities, such as primary phone or e-mail, include a child entity that captures the contact
preference. For example, the Primary Phone Contact Preference entity captures the contact preference of the
account for the contact method primary phone.

one-to-many relationships between the structural components that make up the account.
locations that you need to complete this task, see the topic Account Import Objects : How They Work Together.
Note: You can use the keyword importing accounts to search for related topics in Oracle Sales Cloud Help.
74
If you want to configure the object to import your legacy or source data, then you must use the 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 configurable attributes, which you can then map
to your source file data. You can use the same source file to import both the configurable attributes and the standard import
object attributes.
Importing Accounts Using File-Based Data Import

For the account business object, you must use the File-Based Data Import feature. You prepare XML or text source data files
The Define File 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. When you're creating a new account, you import the Account object. You must be assigned the Customer
Relationship Management Application Administrator job role to access and submit the import activities for accounts.
When importing account information, you first import the basic account profile information, followed by the child entities
for the account. 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 account.
You must provide the PartyOrigSystem and PartyOrigSystemReference of the account when importing contacts for
the account. PartyOrigSystem is the source system code that identifies the source of the information being imported.
and a unique reference. When importing contact information for an account, you must provide the relationship reference
information. This information is required because a contact can have multiple relationships with an account.

Oracle Sales Cloud Applications provide File-Based Import activity reports, which you can use to verify imported data.
Alternatively, you can also navigate to the Customer Center work area to view the account information that you have
imported.
Related Topics
• Account Import Objects: How They Work Together
Account Import Objects: How They Work Together

The Account import object lets you import accounts, their detailed information, and contacts related to the account. This
topic describes the Account import object. It introduces the following:
• Target objects for the Account import objects

• Target import object attribute reference guide files for evaluating and mapping source file data
75
Account Target Import Object Concepts

You use the Account import object to import accounts and contacts related to accounts. The Account import object is split
into separate target import objects for organizing the individual attributes of the account and account contact.
The target import objects in the Account import object are generally grouped into information about the account and
information about the account contact. The organization profile is the target import object containing attributes to import
information about the account. You can have multiple contacts associated with an account.
When updating an existing account with additional information, you must provide the parent reference information for the
existing account. When importing account contacts or contact information for an account, 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
an account-contact relationship, then the import process creates a relationship.
To update the information for an existing account or to create an account record, you can import account profile information,
addresses, and contact points, such as a phone and fax. The following target import objects are for creating and
updating account information: OrganizationProfile, Fax, Address, PrimaryPhone, Url, SalesAccountProfile, Classification,
AdditionalName, Relationship, SellToAddress, and AdditionalIdentifier.
To update or to create an account contact, use the following target import objects: ContactPersonProfile, ContactJob,
ContactPrimaryAddress, ContactEmail, ContactPrimaryPhone, ContactMobile, ContactInstantMessenger, and ContactFax.
All contact-related entities, such as primary phone or e-mail, 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.

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 account.
Target Import Objects Attributes Resources

objects.
The following table lists the reference files that are available for the target import objects.
76
OrganizationProfile Includes detailed account information, such HZ_ IMP_ PARTIES_ T_Reference
as, organization name and organization type.

PrimaryPhone Account's primary phone number. If the HZ_ IMP_ CONTACTPTS_T_ Reference
account has multiple phone numbers, one
of the phone numbers is designated as the
primary phone number.

Address Account's address. HZ_ IMP_ LOCATIONS_ T_Reference

Classification Account's classification. HZ_ IMP_ CLASSIFICS_ T_Reference

AdditionalName Account's additional or alternative name. HZ_ IMP_ ADDTNLPARTYNAMES_

T_Reference

Fax Account's fax number. HZ_ IMP_ CONTACTPTS_T _Reference

FaxContactPreference Indicates the account preference about being HZ_ IMP_ CONTACTPREFS_ Reference
contacted through Fax.

Url Account's URL. HZ_ IMP_ CONTACTPTS_T_ Reference

SalesProfile Account's sales account information. A sales ZCA_ IMP_ SALES_ACCOUNTS _Reference
account is a specific sell-to entity within a
given account. an account can have multiple
sales accounts and sales profiles.

SellToAddress Account's addresses and party sites HZ_ IMP_ PARTYSITES_T_ Reference
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.

AdditionalIdentifier Account's additional identifier information. HZ_ IMP_ ADDTNLPARTYIDS_ T _Reference

Relationship Account's relationship information. You HZ_ IMP_ RELSHIPS_ T_Reference

must enter a relationship code in the
RelationshipCode column, when creating a
relationship.

ContactPersonProfile Account contact's person information. HZ_ IMP_ RELSHIPS_ T_Reference

ContactAdditionalName Account contact's additional name. HZ_ IMP_ ADDTNLPARTYNAMES_ T

_Reference

ContactEmail Account contact's email. HZ_ IMP_ CONTACTPTS_T_ Reference

77
ContactInstantMessenger Account contact's instant messenger or HZ_ IMP_ CONTACTPTS_T_ Reference

social networking information.

ContactPrimaryAddress Account contact's primary address. If the HZ_ IMP_ PARTYSITES_T _Reference
contact has multiple addresses, one of the
addresses is designated as the primary
address.

ContactFax Account contact's fax. HZ_ IMP_ CONTACTPTS_T_ Reference

ContactJob Account contact's job information. HZ_ IMP_ CONTACTS_ T_Reference

ContactMobile Account contact's mobile number. HZ_ IMP_ CONTACTPTS_T_ Reference

ContactPrimaryPhone Account contact's primary phone number. HZ_ IMP_ CONTACTPTS_T _Reference
If the account has multiple phone numbers,
one of the phone numbers is designated as
the primary phone number.

PrimaryPhoneContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS _Reference
about being contacted through phone.

ContactEmailContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS_ Reference
about being contacted through e-mail.

ContactFaxContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS_ Reference
about being contacted through Fax.

ContactMobileContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS_ Reference
about being contacted through mobile
phone.

ContactPrimaryAddressContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS _Reference
about being contacted at the primary
address.

ContactPrimaryPhoneContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS _Reference
about being contacted through the primary
phone number.

Note: Oracle Sales Cloud supports the ContactPersonProfile target object. However, the object is now
deprecated. For updating any contact information, use the PersonProfile target object instead.
Related Topics
• Importing Accounts Using File-Based Import: Explained
78
• File Based Data Import for Oracle Sales Cloud
Import Employee Resources Using File-Based Import

Importing Employee Resources: 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.
• How does your legacy system or source system represent the employee resource compared to how Oracle Sales
business?

You must understand how your employee resource data corresponds with the data in Oracle Sales Cloud so that you can
map your legacy data to the data that Oracle Sales Cloud requires. First, you must understand how Oracle Sales Cloud
represents 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 shows the structure of the Employee Resource object.
Worker Profile
Resource Profile Primary Address
Resource
Resource Team
Organization
Membership
Membership
79
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 importing employee resources, Oracle Sales Cloud incorporates the structure of the employee resource into
import objects. The import object for the employee resource is Employee Resource.

one-to-many relationships between the structural components that make up the employee resource.
You must understand the attribute details of the import objects so that you can prepare your import data. You can use the
locations that you need to complete this task, see the following table.
Employee Resource Employee Resource Import Objects: How They Work Together

Note:
You can use the keyword importing employee resources to search for related topics in Oracle Sales Cloud help.
If you want to configure the Oracle Sales Cloud object to import your legacy or source data, then you must use the
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 configurable
attributes, which you can then map to your source file data. You can use the same source file to import both configurable
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 a file-based import. The file-based import process reads the data in your source
file, populates the interface tables according to your mapping, and imports the data into the application destination tables.
for each import object. When you're creating a new employee resource, you import the Employee Resource object.
80
Note: Employee Resource import is impacted by the error limit settings in the HCM loader. The default error
limit in HCM loader may not always be suitable for Oracle Sales Cloud implementations. It is recommended that
you review the current settings and set the Loader Maximum Errors Allowed parameter to an acceptable value
before launching Employee Resource Import. You can set this parameter in the Setup and Maintenance work
area, in the HCM Configuration for Coexistence task. The value for this parameter must be set depending upon
the batch sizes that you would run. For example, if you run import jobs with 5000 rows at a tolerance level of
20%, then you can set this parameter to 1000. On the other hand, if you run import jobs with 5000 rows at a
tolerance of .5%, then you can set this parameter to 25.
You must be assigned the Master Data Management Administrator job role to access and submit the import activities for
employee resources.
Note: The data quality options, such as matching and cleansing, are not relevant for Employee Resource
import. Hence, while importing employee resources using file-based import, ensure that the Customer Data
Management Duplicates LOV is set to blank.

Oracle Sales Cloud Applications provide File-Based Import activity reports, which you can use to verify imported data. Users
with the Master Data Management Administrator job role can also navigate to the Manage Resources work area to view the
imported employee resources.
Related Topics
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.
• Target objects for the Employee Resource import object

Employee Resource Target Import Objects

You can use the Employee Resource import object to import an employee resource's worker profile information, such as first
name, last name, address, and so on. You can also import 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.
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.
81
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.
To update or create an employee resource's resource profile, use the following target import objects:
ResourceOrganizationMembership and ResourceTeamMembership.

the Application Composer configuration features for the employee resource.

objects.
WorkerProfile Includes detailed employee information such HRC_ LOADER_ BATCH_LINES _

as employee resource name and address. Reference_ For_ Employee_ Resources

ResourceProfile Contains information about a resource, such HZ_ IMP_ RESOURCES_ Reference
as first name, last name, department, and job
code.

PrimaryAddress Employee resource's address. If the resource HZ_ IMP_ PARTYSITES_ T_Reference
has multiple addresses, then the first address
is designated as the primary address.

ResourceOrganizationMembership Employee resource's resource organization HZ_ IMP_ GROUP_MEMBERS _Reference

membership information.
82

ResourceTeamMembership Employee resource's resource team HZ_ IMP_ TEAM_MEMBERS_ Reference

membership information.

Related Topics
Import Geographies Using File-Based Import

Importing Geographies: Explained
This topic explains how to prepare and import geography data from an external data source using the File-Based Data Import
feature. A geography is any region with a boundary around it, regardless of its size. It might be a state, a country, a city, a
county, or a ward. You must create or import geographies before you can associate them with company-specific zones and
addresses.
Note: The application ships with third-party master geography data for multiple countries that can be imported.
You can import Oracle-licensed data from GBG | Loqate or Nokia, for those countries where the data is
available, such as the U.S. You can import geography data using the Manage Geographies task. Search for
the country, and select Import Geography Data from the Actions menu. If the licensed data is not available for
a particular country, then the Import Geography Data action is disabled. For more information, see Replacing
Existing Master Geography Data with Revised Oracle-Licensed Geography Data: Procedure. If GBG | Loqate
or Nokia geography data is not available for a country, then use the information in this chapter to import it using
File-Based Data Import.

• How does your legacy system or source system represent the geography data compared to how Oracle applications
represent the same data?

You must understand how your geography data corresponds with the data in the application so that you can map your
of the data for a geography.
example, if you are importing the country structure of Australia, the country structure could be the following: 1: Country, 2:
83
Import Objects for the Geography

To facilitate importing geographies, the application incorporates the structure of the geography into import objects. The
import object for the geography is ImpGeography.

many relationships between the structural components that make up the geography.
values, and validation information for each import object attribute. The validation information includes the navigation path to
the task where you can define values in the application. For example, if you have values in your data that correlate to a choice
list in the application, then the validation information for that attribute provides the task name in the Setup and Maintenance
work area where you can define your values.
You can use the keyword importing geographies to search for related topics in Help.
The application doesn't support configurable attributes for geographies. You can import only data for geography object that
already exist by default in the application.
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
for each import object. When you're 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.

Oracle applications provide File-Based Import activity reports, which you can use 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.
Related Topics
• Geography Import Objects: How They Work Together
Geography Import Objects: How They Work Together

This topic describes the Geography import object. You use the Geography import object to import geography information.

• Target objects for the Geography import object
84

Geography Target Import Objects

You can use the Geography import object 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 the application, you must understand how
the target objects are related and what attributes are included in each target object.
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.

the Application Composer extensibility features for geography.

To access the reference guide files for the geography's target import objects, see the File Based Data Import for Oracle Sales
Cloud guide available on the Oracle Sales Cloud Help Center (https://docs.oracle.com/cloud/latest/salescs_gs/docs.htm).
In the File Based Data Imports chapter, see the topic for your import object of interest, which includes links to reference files
for target import objects. For detailed information on importing geographies using file-based import, refer to Document No.
1481758.1, Importing Master Reference Geography Data, on the Oracle Support site.
The following table lists the reference file for the ImpGeography target import object.
Target Import Object Description Attribute Reference File Names
ImpGeography Contains information that captures a HZ_ IMP_ GEOGRAPHIES_T _Reference

country's geography hierarchy details, such
as geography type, geography code, and so
on.

85
Related Topics
• Importing Geographies Using File-Based Import: Explained
Import Households Using File-Based Import

Importing Households: Explained
This topic explains how to prepare and import household data from an external data source into Oracle Sales Cloud using the
A household is a party consisting of a collection of persons and organizations. A household, similar to a person or
organization, can enter into a business relationship with other parties and can be assigned to opportunities and leads. A
household can have members of party type person or organization. You can maintain household information in Oracle
Sales Cloud to create leads and opportunities for a household, or capture information about a household to know it better.
However, maintaining this information may not let you assign all sales and marketing activities to a household.
• How does your legacy or source system represent the household information compared to how Oracle Sales Cloud
• Do you have to configure values in Oracle Sales Cloud to map your existing data values to the Household import
object?

You must understand how your household data corresponds with the data in Oracle Sales Cloud so that you can map your
structure of the data for an household.
The Household import object structure is hierarchical. The root of the hierarchy is the group profile, which must exist before
you can import lower-level components, such as classifications, contacts, and relationships. 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 household.
86
The following figure shows the household import object and its child entities.
Group Profile
Additional Instant Additional

Member Classification Relationship Url
Name Messenger Identifier
Phone Address Mobile Email Fax

Address
Purpose
The household profile contains basic information about the household, such as the group name, group type, and the group-
party usage. For each household, you can assign classifications, members, relationships, additional identifier, and additional
names.
captures the contact preference. For example, the Phone Contact Preference entity captures the contact
preference of the household for the phone contact method.

one-to-many relationships between the structural components that make up the household.
Note:
You can use the keyword importing households to search for related topics in Oracle Sales Cloud Help.
87
Importing Households Using File-Based Data Import

For the household business object, you must use the File-Based Data Import feature. You prepare XML or text source
for each import object. When you're creating a new household, you import the household object.
You must be assigned the Customer Relationship Management Application Administrator job role to access and submit the
import activities for household.
When importing household information, you first import the basic household information, followed by the child entities for the
household. 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 name and household type. You then import contacts and contact
information, such as phone, address, contact points, and fax for the household. You must provide the PartyOrigSystem and
PartyOrigSystemReference of the household when importing contacts for the household. PartyOrigSystem is the source
system code that identifies the source of the information being imported.

Alternatively, you can also navigate to the Customer Center work area to view the household information that you have
imported.
Related Topics
• Household Import Objects: How They Work Together
Household Import Objects: How They Work Together

You use the Household import object to import households, their basic information, and members of the household. This
topic describes the Household import object and introduces the following:
• Target objects for the Household import object
Household Target Import Objects

The Household import object is split into separate target import objects for organizing the individual attributes for the different
aspects of the household. The target import objects in the Household import object are grouped into information about the
household and information about the member. The group profile is the target import object containing attributes to import
information about the household. You can have multiple members associated with a household. You can assign only an
organization or a person as a member of a household. You cannot assign a household as a member of another household.
When updating an existing household with additional information, you must provide the parent reference information for the
existing household. When importing contacts or contact information for a household, you must provide relationship reference
information in addition to the parent reference. When importing information about a member, you must refer to the specific
88
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 household or to create a household record, you can import household profile
information, addresses, and contact points, such as phone and fax. The following target import objects are for creating and
updating the household information: GroupProfile, Fax, Mobile, Phone, e-mail, InstantMessenger, Relationship, Member,
Address, Classification, AdditionalName, and AdditionalIdentifier.
All contact-related entities, such phone or e-mail, include a child entity that captures the contact preference. For example, the
Phone Contact Preference entity captures the contact preference of the household for the contact method primary phone.
Additionally, the Address import object for a household includes another child entity, AddressPurpose, that captures the
purpose of the current household address.

the Application Composer configuration features for the marketing response.

objects.
GroupProfile Household information. The default HZ_ IMP_ PARTIES_ T_Reference

party usage for a household is SALES_
PROSPECT.

Relationship Relationship between the household and HZ_ IMP_ RELSHIPS_T

the household member. You must enter a
relationship code in the RelationshipCode
column, when creating a relationship.

Member Household member's information. HZ_ IMP_ RELSHIPS_T

89
Classification Household classification. Classification lets HZ_ IMP_ CLASSIFICS_T

you categorize entities such as parties,
projects, tasks, and orders as hierarchies.

AdditionalIdentifier Household's additional identifier information. HZ_ IMP_ ADDTNLPARTYID_ T

AdditionalName Household's alternative name. HZ_ IMP_ ADDTNLPARTYNAMES _T

Url Household's URL. HZ_ IMP_ CONTACTPTS_T_ Reference

InstantMessenger Household's instant messenger or social HZ_ IMP_ CONTACTPTS_T _Reference

networking information.

Fax Household's fax. HZ_ IMP_ CONTACTPTS_T _Reference

FaxContactPreference Indicates the household preference about HZ_ IMP_ CONTACTPREFS _Reference

Mobile Household's mobile number. HZ_ IMP_ CONTACTPTS_T_ Reference

MobileContactPreference Indicates the household's preference about HZ_ IMP_ CONTACTPREFS_ Reference

Phone Primary phone number of the household. If HZ_ IMP_ CONTACTPTS_T_ Reference
the household has multiple phone numbers,

PrimaryPhoneContactPreference Indicates the household's preference about HZ_ IMP_ CONTACTPREFS_ Reference

Email Household's e-mail. HZ_ IMP_ CONTACTPTS_T_ Reference

EmailContactPreference Indicates the household's preference about HZ_ IMP_ CONTACTPREFS _Reference
being contacted through e-mail.

Address Household's address. If the household has HZ_ IMP_ LOCATIONS_T HZ_ IMP_
multiple addresses, one of the addresses is PARTYSITES_T

AddressContactPreference Indicates the household's preference about HZ_ IMP_ CONTACTPREFS _Reference
being contacted at the primary address.

Sample attributes: ContactType,
PreferenceCode, PreferenceEndDate,
PreferenceStartDate, and ReasonCode.

Reference attributes: CpOrigSystem,
CpOrigSystemReference.

90
AddressPurpose Indicates the purpose of a household's HZ_ IMP_ PARTYSITEUSES_ T

address.

Sample attributes: SiteUseType, EndDate,
and StartDate.

Reference attributes: SiteOrigSystem and
SiteOrigSystemReference.

Related Topics
• Importing Households Using File-Based Import: Explained
• Managing Group Information: Explained
Import Legal Entities Using File-Based Import

Importing Legal Entities: Explained
This topic explains how to prepare and import legal entities from an external data source into Oracle Sales Cloud using the
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.
Consider the following questions when importing legal entity information:

• How does your legacy or source system structure represent the legal entity information compared to how Oracle
Sales Cloud represents 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?
business?

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.
91
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 e-mail, 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.
Legal Entity Profile
Primary Primary Contact Additional

Classification Fax Url
Phone Address PersonProfile Name
PrimaryPhone PrimaryAddress Fax

ContactPreference ContactPreference ContactPreference


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 e-mail.
Note: All contact-related entities, such as primary phone or e-mail, 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.

After you understand the structure of the data, 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.
You must understand the attribute details of the import objects so that you can prepare your import data. The reference
guide files contain descriptions, default values, and validation for each of the attributes. You can use reference guide files
that contain attribute descriptions, values that populate attributes by default when you don't provide values, and validation
information for each attribute. The validation information includes the navigation path 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
92
information for that attribute provides the task name in the Setup and Maintenance work area where you can define your
values.
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
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, 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
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.
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.

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.
Related Topics
• Legal Entities: Explained
93
Legal Entity Import Objects: How They Work Together

The legal entity import object lets you import legal entities, their detailed information, and contacts related to the entity. This
topic describes the Legal Entity import object. It introduces the following:
• Target objects for the legal entity import object
Legal Entity Target Import Objects

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 of the legal entity and its contact.
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,

and target object attribute. You can predefine and manage import mappings using the Manage File Import Mappings task,
or you can define the mapping when you define the import activity using Manage File Import Activities task. Both tasks are
94
the Composer configuration features for the object.

objects.
Target Import Object Description Reference File Name
OrganizationProfile Detailed legal entity information, such as, HZ_ IMP_ PARTIES_ T_Reference
organization name and organization type.

PrimaryPhone Primary phone number of the legal entity. If HZ_ IMP_ CONTACTPTS_ T_Reference
the legal entity has multiple phone numbers,

Fax Fax of the legal entity. HZ_ IMP_ CONTACTPTS_ T_Reference

Url Url of the legal entity. HZ_ IMP_ CONTACTPTS_ T_Reference

AdditionalName Alternative name of a legal entity. HZ_ IMP_ ADDTNLPARTYNAMES_

T_Reference

Classification Classification information for a legal entity. HZ_ IMP_ CLASSIFICS_ T_Reference
Classification lets you categorize entities such
as parties, projects, tasks, and orders as
hierarchies.

PrimaryAddress Primary address of a legal entity. If the HZ_ IMP_ PARTYSITES_ T_Reference
address.

ContactPersonProfile Detailed information of a legal entity contact, HZ_ IMP_ RELSHIPS_ T_Reference
such as, person name, relationship type, and
marital status.

ContactEmail E-mail of the legal entity contact. HZ_ IMP_ CONTACTPTS_ T_Reference

ContactFax Fax of the legal entity contact. HZ_ IMP_ CONTACTPTS_ T_Reference

ContactInstantMessenger Instant messenger or social networking HZ_ IMP_ CONTACTPTS_ T_Reference

information of a legal entity contact.

ContactJob Job information of a legal entity contact. HZ_ IMP_ CONTACTS_ T_Reference
95
Target Import Object Description Reference File Name

ContactMobile Mobile number of a legal entity's contact. HZ_ IMP_ CONTACTPTS_ T_Reference

ContactPrimaryAddress Primary address of a legal entity contact. If HZ_ IMP_ PARTYSITES_ T_Reference
the contact has multiple addresses, one of
the addresses is designated as the primary
address.

ContactPrimaryPhone Primary phone number of the legal entity HZ_ IMP_ CONTACTPTS_ T_Reference
contact. If the legal entity has multiple phone
numbers, one of the phone numbers is
designated as the primary phone number.

ContactAdditionalName Alternative name of a legal entity contact. HZ_ IMP_ ADDTNLPARTYNAMES_

T_Reference

PrimaryPhoneContactPreference The legal entity's preference about being HZ_ IMP_ CONTACTPREFS_ Reference
contacted through phone.

MobileContactPreference The legal entity's preference about being HZ_ IMP_ CONTACTPREFS_ Reference
contacted through mobile.

FaxContactPreference The legal entity's preference about being HZ_ IMP_ CONTACTPREFS_ Reference
contacted through fax.

EmailContactPreference The legal entity's preference about being HZ_ IMP_ CONTACTPREFS_ Reference
contacted through e-mail.

ContactPrimaryAddressContactPreference The legal entity contact's preference about HZ_ IMP_ CONTACTPREFS_ Reference

ContactPrimaryPhoneContactPreference The legal entity contact's preference about HZ_ IMP_ CONTACTPREFS_ Reference
being contacted through the primary phone
number.

PrimaryAddressContactPreference The legal entity's preference about being HZ_ IMP_ CONTACTPREFS_ Reference
contacted at the primary address.

PrimaryPhoneContactPreference The legal entity's preference about being HZ_ IMP_ CONTACTPREFS_ Reference
contacted through the primary phone
number.

Related Topics
• Legal Entities: Explained
96
Import Resource Teams Using File-Based Import

Importing Resource Teams: 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 can't be hierarchically
structured and isn't 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.

• How does your legacy system or source system represent the resource team compared to how Oracle Sales Cloud
business?

You must understand how your resource team data corresponds with the data in Oracle Sales Cloud so that you can map
your legacy data to the data that Oracle Sales Cloud requires. First, you must understand how Oracle Sales Cloud represents
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 importing 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.

one-to-many relationships between the structural components that make up the resource team.
97
Resource Team Resource Team Import Objects: How They Work Together

Note:
You can use the keyword importing resource teams to search for related topics in Oracle Sales Cloud help.
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
for each import object. When you're 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.

Oracle Sales Cloud Applications provide File-Based Import activity reports, which you can use 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.
Related Topics
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 objects for the Resource Team import object
98

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.

the Application Composer Extensibility features for the object.

objects.
ResourceTeam Captured information that identifies a HZ_IMP_TEAMS _Reference

resource team.

ResourceTeamUsage Contains information that indicates the usage HZ_ IMP_ TEAM_ USAGES_ Reference
of the resource team.

Related Topics
99
Import Common Supporting Objects

Importing Additional Party Identifiers: Quick Start
This topic describes how to get you started with importing additional party identifiers. It includes the following information:
• An example of how to identify and associate records

• The minimum data required and the prerequisite tasks
• Additional tips
With an additional party identifier, you can capture other identifiers for an account, contact, or household. For example, a
person may have a driving license as the identifier in a record, and have passport as the identifier in another record. You can
import new additional identifiers or update existing additional identifier records, using the File-Based Data Import feature.
For example, an airline company may have an International Air Transport Association code and the D-U-N-S number as
identifiers.
The following table lists the file-based import objects and target objects that you can use to import additional identifiers.
Import Object Party Type Target Object
Account Organization AdditionalIdentifier

Contact Person AdditionalIdentifier

Household Household AdditionalIdentifier


To add additional identifiers to a party or to update existing additional identifiers using file-based import, your source file must
contain information about the organization, person, or household party to which the additional identifier belongs.
If you're creating the party and the additional identifier in the same import activity, then group the party and additional
identifier data together in your source file. The import process can import the party and then identify the party record so that it
can import the associated additional identifiers.
To add an additional identifier to an existing party or to update an existing additional identifier record, your source file must
include the values that enable the import process to identify the existing records. These values will be source system and
source system reference value combination, Oracle Sales Cloud internal ID, or public unique identifiers, such as business
keys or external IDs.
If the source of your data is an external system, and if you intend to import updates to previously imported records from the
external system, then you can provide the source system code and the unique reference value for the source system's record
in your source file. The file-based data import process stores a cross-reference between the source system information and
Oracle Sales Cloud internal ID. The import process uses the combination of source system and source system reference
value to identify the existing record.
100

The minimum data that is required to import additional identifier information depends on the following:
additional identifier in the same import batch, adding new additional identifiers to an existing party, or updating an
existing additional identifier record.
• Identifying and associating records. In some cases, you can choose which attributes you want to provide to the
import process when identifying and associating records.
The values that you provide in your source file may require a setup task or manual step to ensure that the information passes
the import validation. Before you prepare your source file, complete the prerequisite steps to determine the data values and
then include those values in your source file.
The following table lists the attributes (minimum data) that are required or conditionally required in your import file to create or
update an additional party identifier record. You can optionally include attributes that are available for import in your import file
but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed.
Attribute Description Prerequisite Setup Task Creating Party and Creating Additional Party
Additional Party Identifier Identifier Record for an
Batch
AdditionalPartyI The code representing When you predefine Conditionally required Conditionally required
dOrigSystem the source system for the your source system
additional identifier. code in the Setup and If the source of your If the source of your
Maintenance, Manage data is a third party or data is a third party or
Trading Community external system, and you external system, and you
Source Systems task, intend to import updates intend to import updates
select the Enabled for to previously imported to previously imported
Trading Community records from the same records from the same
Members check box. system, provide the system, provide the
original source system original source system
and source system and source system
reference values reference values

AdditionalPartyI The reference number Identify or generate Conditionally required Conditionally required
dOrigSystemReference or text representing the reference values for each
source system unique additional party identifier If the source of your If the source of your
ID for the additional record. The reference data is a third party or data is a third party or
identifier. value must be unique external system, and you external system, and you
for all additional party intend to import updates intend to import updates
identifiers for the source to previously imported to previously imported
system. records from the same records from the same
system, provide the system, provide the
reference values reference values

ObjectKey The Oracle Sales Cloud Identify the additional The attribute is neither The attribute is neither
internal ID for the party identifier value by required nor conditionally required nor conditionally
additional identifier. exporting the Additional required. required.
Party identifier object,
using the Setup and
Maintenance, Manage
Bulk Data Export,
Schedule Export
Processes task.

101
Batch
PartyId The Oracle Sales Cloud Identify the party ID The attribute is neither
internal ID for the party value by exporting required nor conditionally Conditionally required.
(account, contact, the Party object using required.
household, or legal entity) Setup and Maintenance, Provide reference
to which the additional Manage Bulk Data information to identify
identifier belongs. Export, Schedule Export the existing party. The
Processes task. reference information can
be:
• PartyId (Oracle
Sales Cloud
internal ID)
• PartyOrigSystem
and
PartyOrigSystemReference
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
PartyOrigSystem The code representing Identify the source Required

the source system for the system code that was Conditionally required
party (account, contact, used when you imported
household, or legal entity) the party in a prior batch, Provide reference
to which the additional or identify the source information to identify
identifier belongs. system code that you will the existing party. The
use when importing the reference information can
party in the same batch be:
as this additional party
identifier. • PartyId (Oracle
Sales Cloud
internal ID)
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
PartyOrigSystem The reference number Identify the reference Required

Reference or text representing the value from your source Conditionally required
source system unique ID system that was used
for the party (account, when you imported Provide reference
contact, household, or the party in a prior information to identify
legal entity) to which batch, or identify the the existing party. The
the additional identifier source system reference reference information can
belongs. that you will use when be:
importing the party in
the same batch as this • PartyId (Oracle
additional party identifier. Sales Cloud
record ID)
102
Batch
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
AdditionalPartyI The identifier type to Identify additional Required Required

dentifierType categorize the identifier. identifier types for the
party type using the
Setup and Maintenance,
Manage Additional
Identifier Types task.

AdditionalPartyI The additional identifier No prerequisite tasks Required Required

dentifierValue value for a party.

IssuingAuthority Name The name of the authority No prerequisite tasks Required, if you are The attribute is neither
that issued the additional not providing the Issue required nor conditionally
identifier. Authority Party ID. required.

IssuingAuthority PartyId The party ID of the Identify the party ID value Required, if you are The attribute is neither
issuing authority. by exporting the Party not providing the Issue required nor conditionally
object using Setup and Authority Party Name. required.
Maintenance, Manage
Additional Identifier Types
task.

Note: It is recommended that you include the issue date and expiry date for identifiers that become invalid after
the expiry date, such as passport and driving license.
103
The following figure shows a sample attribute mapping to import a new additional identifier for an existing organization. In this
scenario, origin system and origin system reference information are used to identify the existing party and the new additional
identifier.
The following figure shows a sample attribute mapping to update an existing additional identifier. In this scenario, origin
system reference information is used to identify the additional identifier and update its description.

Additional Tips
Tip: You can explore related topics by entering the following keywords in the Oracle Sales Cloud Help Application search.
• Importing contacts
• Importing accounts
• Importing households
Tip: The Identifier Type is defined for particular party types and for uniqueness. For example, when importing an organization
profile, the identifier type must allow assignment to the organization party type. You can also specify the value of an identifier
type must be unique. For example, you can define that the passport number listed for each person must be unique.
104
Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually
calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference values might
Related Topics
• Identifier Types: Explained
Importing Additional Party Names: Quick Start

This topic describes how to get you started with importing additional party names. It includes the following information:
• Additional tips
With an additional party name, you can capture other names for an account, contact, household, or legal entity. For example,
a person may have a maiden name, and an organization may also be known by a brand name. You can import new additional
names or update existing additional name records, using the File-Based Data Import feature. The following table lists the file-
based import objects and target objects. You can import additional names, using these file-based objects.
Contact Person AdditionalName

Account Organization AdditionalName

Contact Person (a contact for an account) AdditionalName

Household Group AdditionalName

Legal Entity Organization AdditionalName

Legal Entity Person (a contact for a legal entity) ContactAdditionalName


To add additional names to a party or to update existing additional party name assignments using file-based import, your
source file must contain information about the organization, person, or household party to which the additional name is being
assigned. You map your source file data to the organization, person, or group profile target object and to the additional party
name target object.
105
If you're creating the party and the additional party name assignment in the same import activity, then group the party and
additional party name data together in your source file. The import process can import the party, and then identify the party
record so that it can import the associated additional party name.
To add an additional party name to an existing party, or to update an existing additional party name record, your source file
must include values that enable the import process to identify the existing records. These values will be either source system
and source system reference value combination, Oracle Sales Cloud internal ID, or public unique identifiers, such as business

The minimum data that is required to import additional name information depends on the following:
additional party name in the same import batch, adding new additional names to an existing party, or updating an
additional party name record.
• Organization and group names compared with person names. A variety of components that make up a person's
name aren't used for organization and group names.
update an additional party name record. You can optionally include attributes that are available for import in your import file
Additional Party Name Name Record for an
Batch
internal ID for the party value by exporting the required nor conditionally Conditionally required.
(account, contact, Party object using the required.
to which the additional Manage Bulk Data information to identify
party name belongs. Export, Schedule Export the existing party. The
be:
• PartyId (Oracle
Sales Cloud
internal ID).
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
106
Batch
the organization
profile.
PartyOrigSystem The code representing Identify the source Conditionally required.

the source system for the system code that was Conditionally required.
party (account, contact, used when you imported If the source of your
household, or legal entity) the party in a prior batch, data is a third party or Provide reference
to which the additional or identify the source external system, and you information to identify
party name belongs. system code that you will intend to import updates the existing party. The
use when importing the to previously imported reference information can
party in the same batch records from the same be:
as this additional party system, provide the
name. original source system • PartyId (Oracle
and source system Sales Cloud
reference values. internal ID).

• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
PartyOrigSystem The reference number Identify the reference Conditionally required.

Reference or text representing the value from your source Conditionally required.
source system unique ID system that was used If the source of your
for the party (account, when you imported data is a third party or Provide reference
contact, household, or the party in a prior external system, and you information to identify
legal entity) to which the batch, or identify the intend to import updates the existing party. The
additional party name source system reference to previously imported reference information can
belongs. that you will use when records from the same be:
importing the party in system, provide the
the same batch as this original source system • PartyId (Oracle
additional party name. and source system Sales Cloud

• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed
107
Batch
AdditionalName The code representing When you predefine Conditionally required. Conditionally required.
OrigSystem the source system for the your source system
additional name. code in the Setup and If the source of your If the source of your
Maintenance, Manage data is a third party or data is a third party or
Trading Community external system, and you external system, and you
Source Systems task, intend to import updates intend to import updates
select the Enabled for to previously imported to previously imported
Members check box. system, provide the system, provide the
reference values. reference values.

AdditionalName The reference number Identify or generate Conditionally required. Conditionally required.
or text representing the reference values for each
source system unique ID additional party name If the source of your If the source of your
for the additional name. record. The reference data is a third party or data is a third party or
value must be unique for external system, and you external system, and you
all additional party names intend to import updates intend to import updates
for the source system. to previously imported to previously imported
records from the same records from the same

ObjectKey The Oracle Sales Cloud Identify the additional The attribute is neither The attribute is neither
internal ID for the party name ID value by required nor conditionally required nor conditionally
additional name. exporting the Additional required. required.
Party Name object,
using the Setup and
Maintenance, Manage
Bulk Data Export,
Schedule Export
Processes task.

NameType The name type to Review or define the Required Required

categorize the name. name types for each
party type (person,
organization, or
household), using the
Manage Additional Name
Types task.

Name The additional name No prerequisite tasks Required Required

value for an organization
or group.

108
The following figure depicts a sample attribute mapping to import an additional name for an existing party. In this scenario, the
OrigSystem and OrigSystemReference values are used to identify the party.

Oracle Sales Cloud Help Center (https://docs.oracle.com/cloud/latest/salescs_gs/docs.htm). In the File Based Data Imports
Additional Tips
Tip: You can explore related topics by entering the following keywords in Oracle Sales Cloud Help Application.
• Importing additional party names
Tip: The Name Type is defined for particular party types. For example, if you're importing an organization profile, ensure that
the name type definition allows assignment to the Organization party type.
Related Topics
• Importing Contacts Using File-Based Import: Explained
• Additional Name Types: Explained
109
Importing Addresses: Quick Start

This topic describes how to get you started with importing addresses. It includes the following information:
• Additional tips
An address enables you to capture detailed location information for an account, contact, household, employee resource,
and legal entity. For example, a person may have residential and official addresses, and an organization may have different
billing and shipping addresses. You can import new addresses or update existing address records, using the File-Based Data
Import feature.
The following table lists the file-based import objects and target objects that you can use to import addresses.
Account Organization Address, SellToAddress

Account Person (a contact for a account) Address, ContactPrimaryAddress

Household Household Address

Legal Entity Organization PrimaryAddress

Legal Entity Person (a contact for a legal entity) ContactPrimaryAddress

Employee Resource Person PrimaryAddress

Contact Person Address, ContactAddress

Lead Lead Consumer PersonAddress

Lead Lead Contact ContactPrimaryAddress

Partner Organization PrimaryAddress

Partner Contact Person PrimaryAddress

Campaign Response Organization OrganizationAddress

Campaign Response Consumer Respondent PersonAddress

Campaign Response Campaign Response Contact ContactPrimaryAddress

110

To add addresses to a party or to update existing address assignments using file-based import, your source file must contain
information about the account, contact, or household party to which the address belongs. You map your source file data to
the account, contact, or household profile target object and to the address target object.
If you're creating the party and the address assignment in the same import activity, then group the party and address data
together in your source file. The import process can import the party, and then identify the party record so that it can import
the associated address.
To add an address to an existing party, or to update an existing address record, your source file must include the values that
enable the import process to identify the existing records. These values will be source system and source system reference
value combination, an Oracle Sales Cloud internal ID, or Public Unique IDs , such as business keys or external IDs.
You can use external IDs or business keys to identify and associate records with each other when you're importing a smaller
set of records. Business keys are a set of attributes that uniquely identify a party record. For example, a person's last name
and first name uniquely identify a person. An external ID is a unique record identifier from a system outside of Oracle Sales
Cloud. You can use the following business keys or external IDs in Oracle Sales Cloud:
• Organization name for organizations

• First name and last name for persons
• Contact information, which is a combination of e-mail Id, mobile number, IM, and URL.
• Address information, which is a combination of address1, address2, city, and postal code.
You can configure source systems to identify the source of the data that you're importing. Source systems are external
sources of data that are used to import data into Oracle Sales Cloud. Oracle Sales Cloud uses source system references to
create references between source IDs and the Oracle Sales Cloud database IDs. You can configure source systems either by
using the Manage Trading Community Source System task, or by importing the source system information into Oracle
Sales Cloud using the Source System Reference import object.
When the source of your data isn't an external system and you don't intend to regularly update the data, you don't need the
source system information. To import updates to your existing data, you can export the Oracle Sales Cloud internal ID and
add it to your source file. The import process uses the internal ID to identify the existing record.

The minimum data that is required to import address information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the party and the address
in the same import batch, adding addresses to an existing party, or updating an address record.
The values that you provide in your source file may require a setup task or manual step to ensure the information passes the
import validation. Before you prepare your source file, complete the prerequisite steps to determine the data values, and then
include those values in your source file.
111
update an address record. You can optionally include attributes that are available for import in your import file but that aren't
listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed.
Attribute Description Prerequisite Setup Creating Party and Adding Address to Updating Existing
Task Adding Address in an Existing Party Addresses
the Same Batch
PartyId The Oracle Sales Identify the party ID The attribute is

Cloud internal ID for value by exporting neither required Conditionally Conditionally
the party (account, the Party object nor conditionally required. required.
contact, household, using the Setup required
or legal entity) to and Maintenance, Provide reference Provide reference
which the address Manage Bulk Data information to information to
belongs. Export, Schedule identify the existing identify the existing
Export Processes party. The reference party. The reference
task. information can be: information can be:

• PartyId • PartyId
(Oracle Sales (Oracle Sales
Cloud internal Cloud internal
ID). ID).
• PartyOrigSystem • PartyOrigSystem
and and
(source (source
system code system code
and source and source
system system
reference reference
values) values)
provided provided
when when
importing the importing the
organization organization
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
identifier identifier
for an for an
profile), profile),
which is which is
PARTY_SITE_NUMBER PARTY_SITE_NUMBER
for address. for address.
PartyOrigSystem The code Identify the source Conditionally

representing the system code that required. Conditionally Conditionally
source system for was used when you required. required.
the party (account, imported the party If the source of
contact, household, in a prior batch, or your data is an Provide reference Provide reference
or legal entity) to identify the source external system, information to information to
which the address system code that and if you intend to identify the existing identify the existing
belongs. you will use when import updates to party. The reference party. The reference
importing the party previously imported information can be: information can be:
in the same batch records from the
as this address. external system, • PartyId • PartyId
then you can (Oracle Sales (Oracle Sales
provide the source Cloud internal Cloud internal
system code and ID). ID).
112
the Same Batch
the unique reference • PartyOrigSystem • PartyOrigSystem
value for the source and and
system's record in PartyOrigSystemReference
your source file. (source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile), profile),
which is which is
PartyOrigSystem The reference Identify the Conditionally

Reference number or text reference value required. Conditionally Conditionally
representing the from your source required. required.
source system system that was If the source of
unique ID for the used when you your data is an Provide reference Provide reference
party (account, imported the party external system, information to information to
contact, household, in a prior batch, or and if you intend to identify the existing identify the existing
or legal entity) to identify the source import updates to party. The reference party. The reference
which the address system reference previously imported information can be: information can be:
belongs. that you will use records from the
when importing external system, • PartyId • PartyId
the party in the then you can (Oracle Sales (Oracle Sales
same batch as this provide the source Cloud internal Cloud internal
address. system code and ID). ID).
the unique reference
value for the source
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
113
the Same Batch
profile), profile),
which is which is
Country The country code Identify valid Required Required The attribute is
component of the country codes neither required
postal address. using the Setup nor conditionally
and Maintenance, required.
Manage Territories
task.

LocationId1 The unique ID Identify the The attribute is The attribute is

for the existing LOCATION_ID for neither required neither required Conditionally
location record in an existing location nor conditionally nor conditionally required.
the Oracle Sales by exporting the required. required.
Cloud destination Location object Provide reference
table. using the Setup information to
and Maintenance, identify the existing
Manage Bulk Data party. The reference
Export, Schedule information can be:
Export Processes
task. • ObjectKey
(Oracle Sales
Cloud internal
ID).
• LocationOrigSystem1
and
LocationOrigSystemReferen
(source
system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• Party
Number
(public
unique
identifier
for an
organization
profile),
which is
PARTY_SITE_NUMBER
for address.
LocationOrigSystem1 A source system Identify the source Conditionally Conditionally

code that identifies system code that required. required. Conditionally
the original source was used when required.
system of the you imported the If the source of If the source of
location. location in a prior your data is an your data is an Provide reference
batch, or identify external system, external system, information to
the source system and if you intend to and if you intend to identify the existing
code you will use import updates to import updates to
114
the Same Batch
when importing the previously imported previously imported party. The reference
location in the same records from the records from the information can be:
batch as this party external system, external system,
relationship to the then you can then you can • ObjectKey
location. provide the source provide the source (Oracle Sales
system code and system code and Cloud internal
the unique reference the unique reference ID).
value for the source value for the source • LocationOrigSystem1
system's record in system's record in and
your source file. your source file. LocationOrigSystemReferen
(source
system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• Party
Number
(public
unique
identifier
for an
organization
profile),
which is
PARTY_SITE_NUMBER
for address.
LocationOrigSystem Original System Identify the source Conditionally Conditionally

Reference1 Reference for system reference required. required. Conditionally
Location: A source that was used when required.
system reference you imported the If the source of If the source of
that identifies the location in a prior your data is an your data is an Provide reference
unique ID of the batch, or identify external system, external system, information to
location in your the source system and if you intend to and if you intend to identify the existing
legacy or external code you will use import updates to import updates to party. The reference
system. when importing the previously imported previously imported information can be:
location in the same records from the records from the
batch as this party external system, external system, • ObjectKey
relationship to the then you can then you can (Oracle Sales
location. provide the source provide the source Cloud internal
system code and system code and ID).
the unique reference the unique reference
• LocationOrigSystem1
value for the source value for the source
and
system's record in system's record in
LocationOrigSystemReferen
your source file. your source file.
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
115
the Same Batch
• Party
Number
(public
unique
identifier
for an
organization
profile),
which is
PARTY_SITE_NUMBER
for address.
TransliterationLang The language Identify valid A value is required A value is required A value is required
considered as the language codes if you're providing if you're providing if you're providing
local language for using the Setup address elements address elements address elements
the location. and Maintenance, in a translated in a translated in a translated
Manage ISO language. language. language.
Languages task.

Identifying Indicates that an No prerequisite A value is required A value is required A value is required
AddressFlag address is the tasks. if you're adding or if you're adding or if you're adding or
primary address for updating an address updating an address updating an address
a party. association and association and association and
where the import where the import where the import
default value or lack default value or lack default value or lack
of a value in the of a value in the of a value in the
source file results in source file results in source file results in
no address being no address being no address being
identified as the identified as the identified as the
primary address for primary address for primary address for
the party. the party. the party.

RelationshipId The unique identifier Identify the A value is required A value is required A value is required
for the existing relationship ID for an if you're adding an if you're adding an if you're adding an
party relationship existing relationship address association address association address association
record in the by exporting the to an existing to an existing to an existing
Oracle Sales Cloud Relationship and party relationship party relationship party relationship
destination table. Organization or updating an or updating an or updating an
The relationship Contact objects existing address existing address existing address
is between two using the Setup association record association record association record
parties, such as an and Maintenance, for a relationship, for a relationship, for a relationship,
organization and Manage Bulk Data and you're not and you're not and you're not
an organization's Export, Schedule providing the providing the providing the
contact. You Export Processes relationship's source relationship's source relationship's source
provide the task. system reference system reference system reference
relationship if the (RelOrigSystemReference)
(RelOrigSystemReference)
(RelOrigSystemReference)
context of the and the source and the source and the source
address association system code system code system code
is for a relationship. (RelOrigSystem). (RelOrigSystem). (RelOrigSystem).

RelOrigSystem The source system No prerequisite A value is required A value is required A value is required
code that identifies tasks. if you're adding an if you're adding an if you're adding an
the original source address association address association address association
system of the party to an existing party to an existing party to an existing party
relationship. relationship and relationship and relationship and
you're not providing you're not providing you're not providing
the relationship ID, the relationship ID, the relationship ID,
or if you're importing or if you're importing or if you're importing
the relationship in the relationship in the relationship in
116
the Same Batch
the same import the same import the same import
batch and you're batch and you're batch and you're
using the source using the source using the source
system reference system reference system reference
and source system and source system and source system
code to relate the code to relate the code to relate the
source file data. source file data. source file data.

RelOrigSystem The ID that No prerequisite A value is required A value is required A value is required
Reference identifies the party tasks. if you're adding an if you're adding an if you're adding an
relationship in your address association address association address association
legacy or external to an existing party to an existing party to an existing party
system. relationship and relationship and relationship and
you're not providing you're not providing you're not providing
the relationship ID, the relationship ID, the relationship ID,
or if you're importing or if you're importing or if you're importing
the relationship in the relationship in the relationship in
the same import the same import the same import
batch and you're batch and you're batch and you're
using the source using the source using the source
system reference system reference system reference
and source system and source system and source system
code to relate the code to relate the code to relate the
source file data. source file data. source file data.

ResourceEmail The employee Identify the e-mail A value is required if A value is required if A value is required if
Address resource's e-mail. ID for an existing you're importing the you're importing the you're updating the
resource using the employee resource employee resource employee resource
Resource Directory in the same batch in the same batch in the same batch
or the Setup and as this address as this address as this address
Maintenance, association and are association and are association and are
Manage Resources using the e-mail using the e-mail using the e-mail
task. You can address to relate the address to relate the address to relate the
also obtain the source file data. source file data. source file data.
e-mail address
by exporting the
Party object using
the Setup and
Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.

SiteOrigSystem A source system No prerequisite The attribute is The attribute is A value is required
code that identifies tasks. neither required neither required if you're updating a
the original source nor conditionally nor conditionally previously imported
system of the required. required. address association,
address association where you provided
(party site). a SiteOrigSystem
value, and you're
not providing the
address association
ID (ObjectKey), or
if you're importing
associated objects,
such as contact
preferences and
site uses, and are
117
the Same Batch
using the source
system reference
and source system
code to relate the
source file data

SiteOrigSystem A source system No prerequisite The attribute is The attribute is A value is required
Reference reference that tasks. neither required neither required if you're updating a
identifies the unique nor conditionally nor conditionally previously imported
ID of the address required. required. address association,
association (party where you provided
site) in your legacy a SiteOrigSystem
or external system. value, and you're
not providing the
address association
ID (ObjectKey), or
if you're importing
associated objects,
such as contact
preferences and
site uses, and are
using the source
system reference
and source system
code to relate the
source file data

ObjectKey The unique ID for Identify the party site The attribute is The attribute is A value is required
the existing address ID for an existing neither required neither required if you're updating
association record address association nor conditionally nor conditionally an existing address
(party site) in the by exporting the required. required. association and
Oracle Sales Cloud Party Site object are not providing
destination table. using the Setup the source system
and Maintenance, reference and
Manage Bulk Data source system code
Export, Schedule (SiteOrigSystemReference
Export Processes and
task. SiteOrigSystem).

There are four sets of reference information that you can use to refer to a record. However, you must use only one of them to
refer to a record; else, the import process would result in an error. The import process recognizes reference information in this
order:
1. Oracle Sales Cloud ID such as PartyId, ObjectKey, ad so on.

2. Public User ID such as organization name, contact name, ad so on.
3. Origin system and origin system reference
4. Other reference information such as business keys.
118
The following figure depicts a sample attribute mapping to import an address for an existing party. In this scenario, the
OrigSystem and OrigSystemReference values are used to identify the party.

Additional Tips
Tip: You can explore related topics by entering the following keywords in Oracle Sales Cloud Help Application search. You
can access help from any Oracle Sales Cloud page by clicking Help and selecting Applications Help.
• Importing addresses
• Importing location information
• Importing legal entities
Related Topics
119
Importing Address Purposes: Quick Start

This topic describes how to get you started with importing address purposes. It includes the following information:
• Additional tips
An address purpose enables you to capture functions performed by each address. For example, assign the bill-to address
purpose to account sites designated to receive and process bills. Similarly, assign the ship-to address purpose to account
sites designated to receive goods purchased by the customer account.
The following table lists the file-based import objects and target objects that you can use to import address purposes.
Contact Person ContactAddressPurpose

Account Organization AddressPurpose

Account Person (a contact for an account) ContactAddressPurpose

Household Household AddressPurpose

Household Person (a contact for a household) ContactAddressPurpose

Campaign Response Consumer Respondent AddressPurpose

Campaign Response Campaign Response Contact ContactAddressPurpose

Legal Entity Organization AddressPurpose

Legal Entity Person (a contact for a legal entity) ContactAddressPurpose

Lead Lead Consumer AddressPurpose

Lead Lead Contact ContactAddressPurpose

Partner Organization AddressPurpose

120

To add address purposes to a party or update existing address purpose assignments using file-based import, your source
file must contain information about the address and the account, contact, or household party to which the address purpose
belongs. You map your source file data to the account, contact, or household profile target object and to the address
purpose target object.
If you're creating the address and the address purpose assignment in the same import activity, then group the address and
address purpose data together in your source file. The import can import the address, and then identify the address record
so that it can import the associated address purpose.
To add an address purpose to an existing address, or to update an existing address purpose record, your source file must
include values that enable the import process to identify the existing records. These values will be source system and source
system reference value combination, Oracle Sales Cloud internal ID, or public unique identifiers, such as business keys or
external IDs.


The minimum data that is required to import address purpose information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the address and the
address purpose in the same import batch, adding address purposes to an existing address, or updating an address
purpose record.
121
The following table lists the attributes (minimum data) that are required or conditionally required in your import file to create
or update an address purpose record. You can optionally include attributes that are available for import in your import file but
that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed.
Attribute Description Prerequisite Setup Creating Party and Adding Address Updating Existing
Task Adding Address Purpose to an Address Purposes
Purpose in the Existing Party
Same Batch
PartyId The Oracle Sales Identify the party ID Required

Cloud internal ID for value by exporting Conditionally Conditionally
the party (account, the Party object required. required.
contact, household, using the Setup
or legal entity) to and Maintenance, Provide reference Provide reference
which the address Manage Bulk Data information to information to
belongs. Export, Schedule identify the existing identify the existing

ID). ID).
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• A business • A business
key that is a key that is a
combination combination
of of
PARTY_SITE_ID, PARTY_SITE_ID,
SITE_USE_TYPE, SITE_USE_TYPE,
START_DATE, START_DATE,
and and
END_DATE END_DATE
range. range.

representing the system code that required Conditionally Conditionally
or legal entity) to identify the source external system, information to information to
which the address system code that and if you intend to identify the existing identify the existing
belongs. you will use when import updates to
importing the party previously imported
records from the
122
Same Batch
in the same batch external system, party. The reference party. The reference
as this address. then you can information can be: information can be:
provide the source
system code and • PartyId • PartyId
the unique reference (Oracle Sales (Oracle Sales
value for the source Cloud internal Cloud internal
system's record in ID). ID).
your source file. • PartyOrigSystem • PartyOrigSystem
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
of of
and and
END_DATE END_DATE
range. range.
PartyOrigSystem The reference Identify the Conditionally

Reference number or text reference value required Conditionally Conditionally
or legal entity) to identify the source import updates to party. The reference party. The reference
which the address system reference previously imported information can be: information can be:
purpose belongs. that you will use records from the
when importing external system, • PartyId • PartyId
additional party system code and ID). ID).
name. the unique reference
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
123
Same Batch
of of
and and
END_DATE END_DATE
range. range.
SiteUseType The lookup code Identify the site use Required Required Required
that represents the type using the Setup
purpose for the and Maintenance,
address association. Manage Trading
Community Location
Lookups task.

PartySiteId The unique ID Identify the party site The attribute is Conditionally
for the existing ID for an existing neither required required. Conditionally
address association address association nor conditionally required.
record (party site) by exporting the required. If the source of
in the Oracle Sales Party Site object your data is an Provide reference
Cloud destination using the Setup external system, information to
table. The party and Maintenance, and if you intend to identify the existing
site represents the Manage Bulk Data import updates to party. The reference
association of a Export, Schedule previously imported information can be:
physical location Export Processes records from the
to an organization, task. external system, • ObjectKey
person, or to a then you can (Oracle Sales
relationship between provide the source Cloud internal
two parties, such system code and ID).
as an organization's the unique reference
• SiteuseOrigSystem
contact. value for the source
and
system's record in
SiteuseNameOrigSystemRe
your source file.
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• A business
key that is a
combination
of
PARTY_SITE_ID,
SITE_USE_TYPE,
START_DATE,
and
END_DATE
range.
124
Same Batch
SiteOrigSystem A source system Identify the source Conditionally Conditionally

address association address in a prior your data is an your data is an Provide reference
(party site). The batch, or identify external system, external system, information to
party site represents the source system and if you intend to and if you intend to identify the existing
the association of code that you will import updates to import updates to party. The reference
a physical location use when importing previously imported previously imported information can be:
to an organization, the address in the records from the records from the
person, or to a same batch as this external system, external system, • ObjectKey
relationship between address purpose. then you can then you can (Oracle Sales
two parties, such provide the source provide the source Cloud internal
as an organization's system code and system code and ID).
contact. the unique reference the unique reference
and
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• A business
key that is a
combination
of
PARTY_SITE_ID,
SITE_USE_TYPE,
START_DATE,
and
END_DATE
range.
SiteOrigSystem A source system Identify the Conditionally Conditionally

Reference reference that reference value from required. required. Conditionally
identifies the unique your source system required.
ID of the address that was used If the source of If the source of
association (party when you imported your data is an your data is an Provide reference
site) in your legacy the address in a external system, external system, information to
or external system. prior batch, or and if you intend to and if you intend to identify the existing
The party site identify the source import updates to import updates to party. The reference
represents the system reference previously imported previously imported information can be:
association of a that you will use records from the records from the
physical location when importing external system, external system, • ObjectKey
to an organization, the address in the then you can then you can (Oracle Sales
person, or to a same batch as this provide the source provide the source Cloud internal
relationship between address purpose. system code and system code and ID).
two parties, such the unique reference the unique reference
as an organization's value for the source value for the source
and
contact. system's record in system's record in
(source

system code
and source
125
Same Batch
system
reference
values)
provided
when
importing the
organization
profile.
• A business
key that is a
combination
of
PARTY_SITE_ID,
SITE_USE_TYPE,
START_DATE,
and
END_DATE
range.
SiteuseOrigSystem A source system Identify the source Conditionally Conditionally

party's address address purpose your data is an your data is an Provide reference
purpose. in a prior batch, external system, external system, information to
or identify the and if you intend to and if you intend to identify the existing
source system code import updates to import updates to party. The reference
that you will use previously imported previously imported information can be:
when importing the records from the records from the
address purpose external system, external system, • ObjectKey
in the same batch then you can then you can (Oracle Sales
as this address provide the source provide the source Cloud internal
purpose. system code and system code and ID).
and
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• A business
key that is a
combination
of
PARTY_SITE_ID,
SITE_USE_TYPE,
START_DATE,
and
END_DATE
range.
126
Same Batch
SiteuseOrigSystem A source system Identify the Conditionally Conditionally

Reference reference that reference value from required. required. Conditionally
ID of the party's that was used when If the source of If the source of
address purpose you imported the your data is an your data is an Provide reference
in your legacy or address purpose external system, external system, information to
external system. in a prior batch, or and if you intend to and if you intend to identify the existing
identify the source import updates to import updates to party. The reference
system reference previously imported previously imported information can be:
that you will use records from the records from the
when importing the external system, external system, • ObjectKey
address purpose then you can then you can (Oracle Sales
in the same batch provide the source provide the source Cloud internal
as this address system code and system code and ID).
purpose. the unique reference the unique reference
and
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• A business
key that is a
combination
of
PARTY_SITE_ID,
SITE_USE_TYPE,
START_DATE,
and
END_DATE
range.
ObjectKey, The unique ID for No prerequisite The attribute is The attribute is

PartySiteUseId the existing address tasks. neither required neither required Conditionally
purpose record in nor conditionally nor conditionally required.
the Oracle Sales required. required.
Cloud destination Provide reference
table. information to
identify the existing
party. The reference
information can be:
• ObjectKey
(Oracle Sales
Cloud internal
ID).
and
(source
system code
and source
127
Same Batch
system
reference
values)
provided
when
importing the
organization
profile.
• A business
key that is a
combination
of
PARTY_SITE_ID,
SITE_USE_TYPE,
START_DATE,
and
END_DATE
range.
order:
1. Oracle Sales Cloud ID such as PartyId, ObjectKey, and so on.

2. Public User ID such as organization name, contact name, and so on.
128
The following figure depicts a sample attribute mapping to import an address purpose for an existing party. In this scenario,
the OrigSystem and OrigSystemReference values are used to identify the party.

Additional Tips
• Importing addresses
• Importing address purposes
129
Related Topics
Importing Classifications: Quick Start

This topic describes how to get you started with importing classifications. It includes the following information:
• Additional tips
With classifications you can categorize entities, such as organizations, persons, and households. You define various
classification categories, eligibility rules, and the classification values. For example, you define a classification category for
parties interested in renewable energy types, including a solar energy classification value. Another classification category
represents industries, such as automotive and banking. You can classify a party as interested in solar energy and conducts
business in the automotive industry.
The following table lists the file-based import objects and target objects that you can use to import classifications.
Account Organization Classification

Legal Entity Organization Classification

Contact Person Classification

Consumer Organization Classification

Household Household Classification


To add classifications to a party or update existing classification assignments using file-based import, your source file must
contain information about the organization, person, or household party to which the classification is being assigned. You map
your source file data to the organization, person, or group profile target object and to the classification target object.
If you're creating the party and the classification assignment in the same import activity, then group the party and
classification data in your source file. The import process can import the party, and identify the party record so that it can
import the associated classifications.
130
To add a classification to an existing party or to update an existing classification record, your source file must include values
that enable the import process to identify the existing records. These values will be either source system and source system
reference value combination, Oracle Sales Cloud internal ID, or public unique identifiers, such as business keys or external
IDs.

The minimum data that is required to import classification information depends on the following:
classification in the same import batch, adding classifications to an existing party, or updating a classification record.
or update a classification record. You can optionally include attributes that are available for import in your import file but that
aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed.
Attribute Description Prerequisite Setup Task Creating Party and Creating Classification
Classification Records in Record for an Existing
the Same Batch Party
internal ID for the party value by exporting required nor conditionally Conditionally required
(account, consumer, the Party object using required.
contact, household, or Setup and Maintenance, Provide reference
legal entity) to which the Manage Bulk Data information to identify
classification belongs. Export, Schedule Export the existing party. The
be:
• PartyId (Oracle
Sales Cloud
internal ID).
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
• Business
keys such as
class_category
and class_code.
PartyOrigSystem The code representing Identify the source Conditionally required

the source system for system code that was Conditionally required
the party (account, used when you imported If the source of your data
consumer, contact, the party in a prior batch, is a third party or external
131
household, or legal entity) or identify the source system, and if you intend
to which the classification system code you will use to import updates to Provide reference
belongs. when importing the party previously imported information to identify
in the same batch as this records from the same the existing party. The
classification. system, then provide the reference information can
original source system be:
and source system
reference values. • PartyId (Oracle
Sales Cloud
internal ID).
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
• Business
keys such as
class_category
and class_code.
PartyOrigSystem The reference number Identify the reference Conditionally required

Reference or text representing the value from your source Conditionally required
source system unique ID system that was used If the source of your data
for the party (account, when you imported the is a third party or external Provide reference
consumer, contact, party in a prior batch, system, and if you intend information to identify
household, or legal entity) or identify the source to import updates to the existing party. The
to which the classification system reference you will previously imported reference information can
belongs. use when importing the records from the same be:
party in the same batch system, then provide the
as this classification. original source system • PartyId (Oracle

• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
• Business
keys such as
class_category
and class_code.
update classification record. You can optionally include attributes that are available for import in your import file but that aren't
132
ClassificationOrigSystem The code representing When you predefine Conditionally required Conditionally required
the source system for the your source system
classification. code in the Setup and If the source of your data If the source of your data
Maintenance, Manage is a third party or external is a third party or external
Trading Community system, and if you intend system, and if you intend
Source Systems task, to import updates to to import updates to
select the Enabled for previously imported previously imported
Members check box. . system, then provide the system, then provide the

ClassificationOri The reference value for Identify or generate Conditionally required Conditionally required
gSystemReference the classification record reference values for
in the external source each party classification If the source of your data If the source of your data
system. association record. The is a third party or external is a third party or external
reference value must system, and if you intend system, and if you intend
be unique for all party to import updates to to import updates to
classification associations previously imported previously imported
for the source system. records from the same records from the same
system, then provide the system, then provide the

ObjectKey The Oracle Sales Cloud Identify the party The attribute is neither The attribute is neither
internal ID for the party classification association required nor conditionally required nor conditionally
classification association. ID by exporting the required. required.
Classification Assignment
object, using the Setup
and Maintenance,
Manage Trading
Community Source
Systems task.

ClassificationCode The classification code The code should be Required Required

within classification valid for the classification
category. category. Review the
classification codes valid
for each classification
category, using the
Manage Classification
Categories, Setup and
Maintenance task.

ClassificationCategory The classification Identify the classification Required Required

category. category name and
review entity assignment
rules using the Manage
Classification Categories,
Setup and Maintenance
task.

133
There are four sets of reference information that you can use to refer to a record. However, only set of reference information
is sufficient to identify a record. If you have mentioned multiple reference sets that has conflict, then it results in an error. The
import process recognizes reference information in this order:

2. Public User ID such as PartyNumber (also called RegistryID), PartySiteNumber, and so on.
3. Origin system and Origin system reference
4. Other reference information such as business keys
The following figure shows a sample attributes mapping to import a new classification for an existing organization. In this
scenario, origin system and origin system reference information identifies the new classification and the existing organization.
The following figure shows a sample attribute mapping to update an existing classification of an existing organization, by
providing origin system and origin system reference information.

134
Additional Tips
• Importing classification codes
Review the entity assignment rules for the classification category to verify whether the import object meets the assignment
criteria.
If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating
reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then
you might define a source system, using a code of SALES_ACTIVITY. The format of your reference values might concatenate
the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.
Related Topics
• Classifications: Explained
Importing Contact Points: Quick Start

This topic describes how to get you started with importing contact points. It includes the following information:
• An overview of contact points
• The minimum data required and the prerequisites tasks
• Additional Tips
Note: Information for associating addresses with persons and organizations is included in this topic, although
contact points don't formally include addresses.
The following table lists the file-based import objects and target objects that you can use to import contact points directly
associated with the person.
Import Object Party Type Target Objects for Importing Contact Points
Contact Person Email, Fax, InstantMessenger, Mobile,

Phone, Address

Account Organization PrimaryPhone, Fax, Url, Address

135
Household Organization E-mail, Fax, InstantMessenger, Mobile,

Phone, Address, Url

Legal Entity Organization Fax, PrimaryPhone, PrimaryAddress, Url

Lead Organization (lead organization) OrganizationProfileFax,

OrganizationProfilePrimaryPhone,
OrganizationAddress, Url

Lead Person (lead individual) Email, PersonProfileFax,

InstantMessenger, Mobile, PersonAddress,
PersonProfilePrimaryPhone

Lead Person (contact at lead organization) ContactEmail, ContactFax,

ContactInstantMessenger,
ContactMobile, ContactPrimaryAddress,
ContactPrimaryPhone

Partner Organization Fax, PrimaryPhone, PrimaryAddress, Url

Partner Contact Person (contact for a partner) Email, Fax, InstantMessenger, Mobile,
PrimaryPhone, PrimaryAddress

Campaign Response Organization (respondent organization) OrganizationProfileFax,


Campaign Response Person (individual respondent) Email, PersonProfileFax, InstantMessenger,

Mobile, PersonProfilePrimaryPhone,
PersonAddress

Campaign Response Person (contact at respondent organization) ContactEmail, ContactFax,

ContactPrimaryPhone

The following table lists the file-based import objects and target objects that you can use to import contact points for a
contact relationship.
Import Object Party Type Target Objects for Importing Contacts
Contact Person (a contact for another root object ContactEmail, ContactFax,

such as account) ContactInstantMessenger, ContactMobile,
ContactAddress, ContactPhone

Account Person (a contact for an account) ContactEmail, ContactFax,

ContactPrimaryPhone

136
Legal Entity Person (contact for a legal entity) ContactEmail, ContactFax,

ContactPrimaryPhone

Contact Points Overview

A contact is an individual who is a customer or a prospect, or a contact for an existing customer or consumer, or a contact
that does not yet have an established business association with a customer or consumer. Thus, a contact could be an
employee of a customer organization, a person you may have met who could help with your business, or a prospective or
current individual customer. 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, e-mail IDs, URLs, messenger IDs, and so on.
The contact object also contains contact preference information for the contact.
Note: A contact point cannot be shared among multiple parties.

To add contact to a party or to update existing contact point assignments using file-based import, your source file must
contain information about the account, contact, or household party to which the contact point belongs. You map your source
file data to the account, contact, or household profile target object, the relationship record that captures the interconnection
between the contact and the account.
If you're creating the party and the contact point assignment in the same import activity, then group the party and contact
point data together in your source file. The import process can import the party, and then identify the party record so that it
can import the associated contact point.
To add a contact point to an existing party, or to update an existing contact point record, your source file must include
values that enable the import process to identify the existing records. These values will be source system and source system
reference value combination, an Oracle Sales Cloud internal ID, or public unique identifiers, such as business keys or external
IDs.

• Contact information, which is a combination of email Id, mobile number, IM, and URL.
137

The minimum data that is required to import contact point information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the party and the contact
point in the same import batch, adding contact points to an existing party, or updating a contact point record.
or update a contact point data record. You can optionally include attributes that are available for import in your import file but
Attribute Description Prerequisite Setup Creating Party and Adding Contact Updating Contact
Task Adding Contact Point Records to an Point Records
Points in the Same Existing Party
Batch
PartyId The Oracle Sales The attribute is

Cloud internal ID for Identify the party ID neither required Conditionally Conditionally
the party (account, value by exporting nor conditionally required. required.
contact, household, the Party object required.
partner, or legal using Setup and
Maintenance, Provide reference Provide reference
entity) to which information to information to
the contact point Manage Bulk Data
Export, Schedule identify the existing identify the existing
belongs. party. The reference party. The reference
Export Processes
ID). ID).
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
138
Batch
unique unique
for an for an
profile), profile),
which is which is
CONTACT_NUMBER CONTACT_NUMBER
for contact. for contact.

partner, or legal identify the source external system, information to information to
entity) to which system code that and if you intend to identify the existing identify the existing
the contact point you will use when import updates to party. The reference party. The reference
belongs. importing the party previously imported information can be: information can be:
as this contact external system, • PartyId • PartyId
point. then you can (Oracle Sales (Oracle Sales
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile), profile),
which is which is
The reference Identify the Conditionally
number or text reference value required. Conditionally Conditionally
partner, or legal identify the source import updates to
entity) to which system reference previously imported
the contact point that you will use records from the
belongs. when importing external system,
139
Batch
the party in the then you can party. The reference party. The reference
same batch as this provide the source information can be: information can be:
contact point. system code and
the unique reference • PartyId • PartyId
value for the source (Oracle Sales (Oracle Sales
system's record in Cloud internal Cloud internal
your source file. ID). ID).
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile), profile),
which is which is
ObjectKey The unique ID for The attribute is The attribute is

the existing contact Identify the contact neither required neither required Conditionally
point record in the point ID for an nor conditionally nor conditionally required.
Oracle Sales Cloud existing contact required. required.
destination table. point by exporting
the contact point Provide reference
information to
object using
the Setup and identify the existing
Maintenance, party. The reference
Manage Bulk Data information can be:
Export, Schedule
Export Processes • ObjectKey
task. (Oracle Sales
Cloud internal
ID).
• CpOrigSystem
and
CpOrigSystemReference
(source
system code
and source
system
reference
values)
provided
when
importing the
140
Batch
organization
profile.
• Party
Number
(public
unique
identifier
for an
organization
profile),
which is
CONTACT_NUMBER
for contact.
ContactPointType Type of the contact Required Required Required

point like phone, Identify valid lookup
email and so on. codes for the
COMMUNICATION_TYPE
lookup using
the Setup and
Maintenance,
Manage Contact
Point Lookups
task.
CpOrigSystem A source system Identify the source Conditionally Conditionally

contact point. contact point in your data is an your data is an Provide reference
a prior batch, or external system, external system, information to
identify the source and if you intend to and if you intend to identify the existing
system code that import updates to import updates to party. The reference
you will use when previously imported previously imported information can be:
importing the records from the records from the
contact point in external system, external system, • ObjectKey
the same batch as then you can then you can (Oracle Sales
this contact point provide the source provide the source Cloud internal
contact preference. system code and system code and ID).
• CpOrigSystem
and
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• Party
Number
(public
unique
identifier
for an
organization
141
Batch
profile),
which is
CONTACT_NUMBER
for contact.
CpOrigSystemReferenceA source system Identify the Conditionally Conditionally

reference that reference value from required. required. Conditionally
ID of the contact that was used when If the source of If the source of
point in your legacy you imported the your data is an your data is an Provide reference
or external system. contact point in external system, external system, information to
a prior batch, or and if you intend to and if you intend to identify the existing
contact point in then you can then you can (Oracle Sales
the same batch as provide the source provide the source Cloud internal
this contact point system code and system code and ID).
contact preference. the unique reference the unique reference
• CpOrigSystem
and
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• Party
Number
(public
unique
identifier
for an
organization
profile),
which is
CONTACT_NUMBER
for contact.
OwnerEmailAddress The e-mail address Optional

of the resource that Identify the party ID Conditionally Conditionally
owns and manages and party number required. required.
the sales account to of the owner by
which the contact is exporting the
Party object using Specify an owner, By default, the
associated. by including user importing
the Setup and
Maintenance, one of the the contact is
Manage Bulk Data following reference designated as the
Export, Schedule information: owner.
Export Processes
task. • OwnerEmailAddress
To specify a
• OwnerPartyID
different owner,
• OwnerPartyNumber
include one of the
142
Batch
following reference
information:
• OwnerEmailAddress
• OwnerPartyID
OwnerPartyId The unique identifier Optional

of a valid employee Identify the party ID Conditionally Conditionally
resource who owns and party number required. required.
and manages the of the owner by
sales account to exporting the
which the contact is by including user importing
associated. the Setup and
following reference designated as the
Manage Bulk Data
Export Processes
To specify a
• OwnerPartyID
different owner,
include one of the
following reference
information:
• OwnerPartyID
OwnerPartyNumber The party number Optional

Manage Bulk Data
Export Processes
To specify a
• OwnerPartyID
different owner,
include one of the
following reference
information:
• OwnerPartyID
order:
143
The following figure depicts a sample attribute mapping to import a contact point for an existing party. In this scenario, the
OrigSystem and OrigSystemReference values identify the party.

Additional Tips
• Importing employee resources
Related Topics
144
• Importing Contact Point Preferences Using File-Based Import: Quick Start
Importing Contact Point Preferences: Quick Start

This topic describes how to get you started with importing contact point preferences. It includes the following information:
• An overview of contact point preferences
• Additional Tips
The following table lists the file-based import objects and target objects that you can use to import contact point directly
Import Object Party Type Target Objects for Importing Contact Point
Preferences
Contact Person EmailContactPreference,

FaxContactPreference, and so on.

InstantMessenger has no contact point
preference.

Account Organization PrimaryPhoneContactPreference,

FaxContactPreference,
AddressContactPreference

Url has no contact point preference.

Household Organization EmailContactPreference,


InstantMessenger and Url have no contact
point preference.

Legal Entity Organization FaxContactPreference,

PrimaryPhoneContactPreference,
PrimaryAddressContactPreference


Lead Organization (lead organization) No contact point preferences

Lead Person (lead individual) No contact point preferences

145
Preferences
Lead Person (contact at lead organization) No contact point preferences

Partner Organization FaxContactPreference,



Partner Contact Person (contact for a partner) EmailContactPreference,


preference.

Campaign Response Organization (respondent organization) No contact point preferences

Campaign Response Person (individual respondent) No contact point preferences

Campaign Response Person (contact at respondent organization) No contact point preferences

The following table lists the file-based import objects and target objects that you can use to import contact point preferences
directly associated with a contact relationship.
Preferences
Contact Person (a contact for another root object ContactEmailContactPreference,

such as account) ContactFaxContactPreference, and so on.

ConactInstantMessenger has no contact
point preference.

Account Person (a contact for an account) ContactEmailContactPreference,

ContactFaxContactPreference, and so on.

ContactInstantMessenger has no contact
point preference.

Legal Entity Person (contact for a legal entity) ContactEmailContactPreference,


point preference.

Contact Point Preferences Overview

Every contact has contact points, such as phone numbers, faxes, e-mail IDs, and so on, and each contact point can have
associated contact point preferences. Contact point preferences indicate whether a contact point can be used to contact a
person. For example, Consider Pinnacle Flowers and Gifts, a customer of Vision Enterprises. At Pinnacle Flowers and Gifts,
the designated contact person for the company must not be contacted by phone, and the customer contact for the logistics
146
service that Vision Enterprises offers does not want to be contacted using faxes. Pinnacle Flowers and Gifts has assigned
phone and fax numbers to most of its contacts and has made these numbers available to its vendors, but the designated
contacts have specific preferences about how they do and do not want to be contacted. Vision Enterprises must store these
preferences to ensure that their employees do not reach out to customer contacts using contact points that the contacts do
not want to be used.

To add contact point preferences to a party or to update existing contact point preference assignments using file-based
import, your source file must contain information about the account, contact, or household party to which the contact point
preference belongs. You map your source file data to the account, contact, or household profile target object, the relationship
record that captures the interconnection between the contact point and the contact point preference target object.
If you're creating the party and contact point preference assignment in the same import activity, then group the party and
contact point preference data together in your source file. The import process can import the party, and then identify the party
record so that it can import the associated contact point preference. To add a contact point preference to an existing party,
or to update an existing contact point preference record, your source file must include values that enable the import process
to identify the existing records.

• The purpose of the import. The data requirements are different when you're creating both the party and contact
point preference in the same import batch, adding contact point preferences to an existing party, or updating a
contact preference record.
or update a contact point preference data record. You can optionally include attributes that are available for import in your
import file but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is
listed.
147
Task Adding Contact Point Preference Point Preference
Point Preferences in Records to an Records
the Same Batch Existing Party

contact, household, using Setup and required.
partner, or legal Maintenance, Provide reference Provide reference
entity) to which Manage Bulk Data information to information to
the contact point Export, Schedule identify the existing identify the existing
preference belongs. Export Processes party. The reference party. The reference

ID). ID).
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.

preference belongs. importing the party previously imported information can be: information can be:
as this contact point external system, • PartyId • PartyId
preference then you can (Oracle Sales (Oracle Sales
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
148
number or text reference value from required. Conditionally Conditionally
representing the your source system required. required.
source system that was used when If the source of
unique ID for the you imported the your data is an Provide reference Provide reference
party (account, party in a prior external system, information to information to
contact, household, batch, or identify and if you intend to identify the existing identify the existing
partner, or legal the source system import updates to party. The reference party. The reference
entity) to which reference that previously imported information can be: information can be:
the contact point you will use when records from the
preference belongs. importing the party external system, • PartyId • PartyId
in the same batch then you can (Oracle Sales (Oracle Sales
as this contact point provide the source Cloud internal Cloud internal
preference. system code and ID). ID).
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
ContactType The method of Identify the contact Required Required The attribute is
contact that should type from the Setup neither required
or should not be and Maintenance, nor conditionally
made, such as call Manage Trading required.
or mail. Community
Common Lookups
task.

PreferenceCode The lookup code Identify the Required Required The attribute is
that represents the preference code neither required
contact method from the Setup nor conditionally
preference phrase, and Maintenance, required.
such as Do Use, Manage Trading
Opt In, Do not use. Community
Common Lookups
task.

PreferenceStartDate The date from which The contact Required Required The attribute is
a contact preference preference period neither required
is valid. start date must nor conditionally
be less than or required.
equal to the contact
preference period
end date.

RequestedBy The lookup code Identify lookup Required Required The attribute is
that represents codes for the source neither required
the source of the of the contact
149
contact preference preference request nor conditionally
request, such as from the Setup required.
internal requirement and Maintenance,
or requested by the Manage Trading
party. Community
Common Lookups
task.

ContactPrefOrigSysRef The source system No prerequisite Conditionally

reference that tasks. required. Conditionally Conditionally
identifies the unique required. required.
ID of the contact If the source of
preference in your your data is an Provide reference Provide reference
legacy or external external system, information to information to
system. and if you intend to identify the existing identify the existing
import updates to party. The reference party. The reference
previously imported information can be: information can be:
records from the
external system, • ObjectKey • ObjectKey
• AdditionalPartyIdOrigSystem
and and
system's record in
AdditionalPartyIdOrigSystemReference
AdditionalPartyIdOrigSystem
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
ContactPrefOrigSystem A source system No prerequisite Conditionally

code that identifies tasks. required. Conditionally Conditionally
the original source required. required.
system of the If the source of
contact preference. your data is an Provide reference Provide reference
external system, information to information to
and if you intend to identify the existing identify the existing
records from the
and and
system's record in
your source file.
(source (source

system system
reference reference
150
values) values)
provided provided
when when
profile. profile.
ObjectKey The unique ID of Identify the contact The attribute is The attribute is
the existing contact preference ID of neither required neither required Conditionally
preference record an existing contact nor conditionally nor conditionally required.
in the Oracle Sales preference by required. required.
Cloud destination exporting the Provide reference
table. Contact Preference information to
object using identify the existing
the Setup and party. The reference
Maintenance, information can be:
Manage Bulk Data
Export, Schedule • ObjectKey
Export Processes (Oracle Sales
task. Cloud internal
ID).
and
(source
system code
and source
system
reference
values)
provided
when
importing the
organization
profile.

• CpOrigSystem
and
(source

system code
and source
system
reference
values)
151
provided
when
importing the
organization
profile.

• CpOrigSystem
and
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
152
The following figure depicts a sample attribute mapping to import a contact point preference for an existing party. In this
scenario, the OrigSystem and OrigSystemReference values identify the party.

Additional Tips
153
Related Topics
• Importing Contact Points Using File-Based Import: Quick Start
Importing Contact Jobs: Quick Start

This topic describes how to get you started with importing contact jobs. It includes the following information:
• Additional tips
A contact job enables you to capture information related to the work that a contact does. The target object contains
attributes that records data such as the name and code of the department where the contact works, the job title of the
contact, and so on.
The following table lists the file-based import objects and target objects that you can use to import contact jobs.
Contact Person ContactJob

Account Person (a contact for a account) ContactJob

Lead Lead Contact ContactJob

Legal Entity Person (a contact for a legal entity) ContactJob

Partner Partner Contact Job

Response Response Contact ContactJob

154

To add contact jobs to a party or to update existing contact job assignments using file-based import, your source file must
contain information about the account, contact, or household party to which the contact job belongs. You map your source
file data to the account, contact, or household profile target object and to the contact job target object.
If you're creating the party and the contact job assignment in the same import activity, then group the party and contact job
data together in your source file. The import process can import the party, and then identify the party record so that it can
import the associated contact job.
To add a contact job to an existing party, or to update an existing contact job record, your source file must include values
that enable the import process to identify the existing records.

The minimum data that is required to import contact job information depends on the following:
job in the same import batch, adding contact jobs to an existing party, or updating a contact job record.
update a contact job record. You can optionally include attributes that are available for import in your import file but that aren't
Attribute Description Prerequisite Setup Creating Party and Adding contact job Updating Existing
Task Adding contact job to an Existing Party Contact Jobs
in the Same Batch
PartyId The Oracle Sales Identify the party ID Required Conditionally Conditionally
Cloud internal ID for value by exporting required. required.
the party (account, the Party object
contact, household, using the Setup To identify the To identify the
or legal entity) to and Maintenance, party, provide party, provide
Manage Bulk Data either the internal ID either the internal ID
155
in the Same Batch
which the address Export, Schedule (PartyId) or both the (PartyId) or both the
belongs. Export Processes source system code source system code
task. (PartyOrigSystem) (PartyOrigSystem)
reference value reference value
that were provided that were provided
in a prior import of in a prior import of
the party. the party.

PartyOrigSystem The code Identify the source Conditionally Conditionally Conditionally

representing the system code that required. required. required.
source system for was used when you
the party (account, imported the party If the source of To identify the To identify the
contact, household, in a prior batch, or your data is an party, provide party, provide
or legal entity) to identify the source external system, either the internal ID either the internal ID
which the address system code that and if you intend to (PartyId) or both the (PartyId) or both the
belongs. you will use when import updates to source system code source system code
importing the party previously imported (PartyOrigSystem) (PartyOrigSystem)
in the same batch records from the and source system and source system
as this address. external system, reference value reference value
then you can (PartyOrigSystemReference)
provide the source that were provided that were provided
system code and in a prior import of in a prior import of
the unique reference the party. the party.
system's record in
your source file.

The reference Identify the Conditionally Conditionally Conditionally
number or text reference value required. required. required.
representing the from your source
source system system that was If the source of To identify the To identify the
unique ID for the used when you your data is an party, provide party, provide
party (account, imported the party external system, either the internal ID either the internal ID
contact, household, in a prior batch, or and if you intend to (PartyId) or both the (PartyId) or both the
or legal entity) to identify the source import updates to source system code source system code
which the address system reference previously imported (PartyOrigSystem) (PartyOrigSystem)
belongs. that you will use records from the and source system and source system
when importing external system, reference value reference value
the party in the then you can (PartyOrigSystemReference)
same batch as this provide the source that were provided that were provided
address. system code and in a prior import of in a prior import of
system's record in
your source file.

RelationshipId The unique ID identify the Conditionally Conditionally Conditionally

for the existing Relationship ID for required. required. required.
contact's an existing contact's
relationship with relationship by If the source of If the source of To identify the
the organization or exporting the your data is an your data is an existing contact
person record in the Relationship object external system, external system, job record, provide
destination table. using the Setup and if you intend to and if you intend to either the internal
and Maintenance, import updates to import updates to ID (ObjectKey) or
Manage Bulk Data previously imported previously imported both the source
Export, Schedule records from the records from the system code
external system, external system, (RelOrigSystem)
156
in the Same Batch
Export Processes then you can then you can and source system
task. provide the source provide the source reference value
system code and system code and (RelOrigSystemReference)
the unique reference the unique reference that were provided
value for the source value for the source in a prior import of
system's record in system's record in the party.

RelOrigSystem The source No prerequisite Conditionally Conditionally Conditionally

system code that tasks. required. required. required.
identifies the original
source system If the source of If the source of To identify the
of the contact's your data is an your data is an existing contact
relationship with external system, external system, job record, provide
the organization or and if you intend to and if you intend to either the internal
person. import updates to import updates to ID (ObjectKey) or
previously imported previously imported both the source
records from the records from the system code
then you can then you can and source system
provide the source provide the source reference value

RelOrigSystemReferenceThe ID that identifies No prerequisite Conditionally Conditionally Conditionally

the contact's tasks. required. required. required.
relationship with
the organization If the source of If the source of To identify the
or person in your your data is an your data is an existing contact
legacy or external external system, external system, job record, provide
system. and if you intend to and if you intend to either the internal
import updates to import updates to ID (ObjectKey) or

ContactNumber The contact job's Obtain the contact The attribute is The attribute is Conditionally
unique public number for an neither required neither required required.
identifier value. existing contact nor conditionally nor conditionally
using the Customers required. required. Required if you are
work area. updating a contact
job and are not
providing the object
key.

ObjectKey The unique ID for identify the contact The attribute is The attribute is Conditionally
the existing contact ID for an existing neither required neither required required.
contact by exporting
157
in the Same Batch
job record in the the Organization nor conditionally nor conditionally Required if you
destination table. Contact object required. required. are updating a
using the Setup contact job and are
and Maintenance, not providing the
Manage Bulk Data contact number.
Export, Schedule
Export Processes
task.


Additional Tips
• Importing contact jobs
• Importing groups
Importing Country Structures Using File-Based Import: Quick Start

This topic describes how to get you started with importing country structures.It includes the following information:
• Additional tips
With the country structure of a country you can define which geography types are part of the country, and how the
geography types are hierarchically related within the country. For example, you can create geography types called State, City,
and Postal Code. Then you can rank the State geography type as the highest level within the country, the City as the second
level, and the Postal Code as the lowest level within the country structure.
The following table lists the file-based import objects and target objects that you can use to import country structures.
158
Country Structure ImpGeoStructureLevel


To add country structures to a country, or to update existing country structure values using file-based import, your source file
must contain information about the country to which the country structure is being assigned. Also, you need to specify the
level number at which the geography types you are importing need to be placed. All countries are, by default, placed at Level
1. Create the country structure by increasing the level number as you go down the country structure. Thus, geography types
such as states, provinces, and so on, can be placed at Level 2; districts or counties at Level 3, and so on.
include values that enable the import process to identify the existing records. These values will be either source system and

update a country structure record. You can optionally include attributes that are available for import in your import file but that
Attribute Description Prerequisite Setup Task Creating Country Structure

Record for an Existing Country
CountryCode The code representing the Identify country codes using Required
country to which the country the Setup and Maintenance,
structure belongs. Manage Geographies task.

Oracle Sales Cloud uses two-
letter ISO country codes to refer
to countries.

GeographyType A code used for internal No prerequisite tasks Required

reference by Oracle Sales Cloud
at an administrative level. For
example, this administrative
code may be COUNTRY,
STATE, COUNTY, CITY, and so
on. You must include either the
LevelNumber or GeographyType
field to define the hierarchical
structure of your data.

LevelNumber The level number for the No prerequisite tasks Required

geography type in the hierarchy.
For example, a country has
the level of 1 in the hierarchy
because it is the highest level.

159
The following figure depicts a sample attribute mapping to import a country structure.

Additional Tips
Tip: You can explore related topics by entering the following keywords in Oracle Sales Cloud Help Application search.
• Importing country structures
Tip: For sample country structures and detailed steps for importing country structures, see article 1341174.1 on My Oracle
Support.
Related Topics
Importing Workers, Users, and Resources Using File-Based Data

Import: Quick Start
This topic describes how to get you started with importing workers, users, and resources. It includes the following
information:
• An overview of workers, users, and resources
160
• Additional tips
The following table lists the file-based import objects and target objects that you can use to import workers, users, and
resources.
Employee Resource WorkerProfile, ResourceProfile, ResourceOrganizationMembership, ResourceTeamMembership,

and PrimaryAddress

Workers, Users, and Resources Overview

The information of a newly hired employee, a contingent worker, or a partner contact is stored in Human Capital Management
(HCM) as a worker. The employees, contingent workers, and partner contacts who can be assigned work to accomplish
business objectives, such as performing Oracle Sales Cloud related tasks, are called resources.
You can import the worker information using the WorkerProfile target import object. This target import object allows import of
the basic person information, such as first name, last name, e-mail address, business unit, and legal entity.
The worker information from HCM is imported into Oracle Sales Cloud as a resource. For example, a worker in HCM
can be imported into Oracle Sales Cloud as a sales representative. You can import the resource information using the
ResourceProfile target import object. This target object allows import of the basic resource information, such as resource role
code, resource role type attributes.
A resource role denotes the function of a resource in an enterprise from the perspective of the deploying company. Resource
roles are used to not only describe who a resource is in the enterprise, but also what specific role the resource performs
within the context of an organization or team. A resource can have only one role in an resource organization during a given
period.
Resource role types organize roles into logical groups. For example, the Partner resource role type defines a set of partner-
specific roles, such as partner sales representative and partner sales manager. You can use the Sales resource role type and
the Marketing resource role type to categorize the appropriate sales and marketing roles for internal employees or contingent
worker resources.
You can define roles that can be assigned to resources within resource organizations using the Setup and Maintenance,
Manage Resource Roles task. When you assign specific roles to resources, they automatically receive access to specific
business functions, locations, applications, and data within the company.
A resource team is a group of resources formed to accomplish a particular task. A resource team may comprise resource
organizations, resources, or both. Resource organizations represent the internal organization and structure of the deploying
company. Resource organizations are hierarchically structured, and reporting relationships are derived from the organization
hierarchy that is created. You can import the resource organization and resource team membership information using the
ResourceOrganizationMembership and ResourceTeamMembership target objects, respectively. For more information about
resource team, see the Define Resource Team Information chapter in the Oracle Sales Cloud Implementing Customer Data
Management guide.

To add resource details such as resource role code and resource role type to an existing employee record or to update
existing employee record using file-based import, your source file must contain information about the employee.
When you add the resource details or update the resource details to an existing employee using file-based import, group the
worker and resource information together in your source file. The import process is then able to first import the worker data,
and then identify the employee record to import the associated resource details.
161

The minimum data that is required to import worker and resource profile information depends on the following:
• The purpose of the import. The data requirements are different when you're importing the worker data and resource
data in the same import batch, or adding resource details to an existing employee record.
• The values that you provide in your source file may require a setup task or manual step to ensure the information
passes the import validation. Before you prepare your source file, complete the prerequisite steps to determine the
data values, and then include those values in your source file. As part of the prerequisite setup tasks, ensure that the
Business Unit, Legal Entity, Resources Roles, and Resource Role Mappings are already created.
resource details or update an existing employee record with the resource details. You can optionally include attributes that are
available for import in your import file but that aren't listed in the table. For each attribute, the prerequisite setup task before
importing that attribute is listed.
Attribute Description Prerequisite Setup Task Creating Employee Resource

Record and Updating Employee
Resource Record in the Same
Batch
WorkerProfile_ BusinessUnit The business unit name to which Identify business unit Required
the resource is associated. names using the Setup and
Maintenance, Manage Business
Unit task.

WorkerProfile_ LegalEntity The legal entity name of the Identify legal entity names using Required
employer. the Setup and Maintenance,
Manage Legal Entity task.

WorkerProfile_ FirstName The worker's first name. No prerequisite tasks Required

WorkerProfile_ LastName The worker's last name. No prerequisite tasks Required

WorkerProfile_ EmailAddress The primary work email ID of the No prerequisite tasks Required
worker.

WorkerProfile_ ManagerEmail The primary work email ID of the No prerequisite tasks Conditionally required.
worker's manager.
If you want to identify an
employee in the resource
hierarchy, then you must
mention the manager email
address.

WorkerProfile_ PersonType Describes the person type, for No prerequisite tasks Conditionally required.
example, EMP for employees,
CWK for contingent workers. If the source of your data is a
contingent worker, then you
must mention the person type.
The default value of the person
type is EMP.

162

Batch
ResourceProfile_ RoleCode The value for the resource role Identify the employee resource Conditionally required.
code, which is predefined in the role code by reviewing the
Manage Resource Roles task. employee resource role types If you want to identify an
and codes in the Setup and employee as a resource, then
Maintenance, Manage Resource you must mention the resource
Roles task. role code.

ResourceProfile_ RoleTypeCode The value for the resource role Identify the employee resource Conditionally required.
type, which is predefined in the role type code by reviewing the
Manage Resource Roles task. employee resource role types If you want to identify an
and codes in the Setup and employee as a resource, then
Maintenance, Manage Resource you must mention the resource
Roles task. role type code.

ResourceOrganizationMembership_ The code for the organization No prerequisite tasks Conditionally required.
TreeCode hierarchy that the resource is
a member of. For employee If you want to associate a
resources, the value is GLOBAL_ resource to an organization
SALES_ MARKETING. For hierarchy, then you must
partner contacts (members), the mention the tree code of the
value is the code for the partner organization hierarchy to which
organization hierarchy. the resource belongs.

ResourceOrganizationMembership_ The code for the parent of the No prerequisite tasks Conditionally required.
ParentTreeCode resource's organization within
the organization hierarchy. If you want to associate a
For employee resources, the resource to an organization
value is GLOBAL_ SALES_ hierarchy, then you must
MARKETING. For partner mention the parent tree code of
contacts (members), the value the resource's organization.
is the code that represents the
parent in the partner organization
hierarchy.

ResourceOrganizationMembership_ The resource organization No prerequisite tasks Conditionally required.

OrganizationUsage usage, which is SALES_
RESOURCE_ ORG for sales, If you want to associate a
PARTNER_ RESOURCE_ resource to an organization
ORGANIZATION for partners, hierarchy, then you must
and MARKETING_ RESOURCE_ mention the resource
ORGANIZATION for marketing. organization usage.

ResourceOrganizationMembership_ The organization name of the Identify the organization name of Conditionally required.
OrganizationName resource. the resource by navigating to the
Resource Directory. If you want to associate a
resource to an organization
If the organization name that you hierarchy, then you must
use in the source file doesn't mention the organization name
already exist in the Resource of the resource.
Directory, then it is created
during the employee resource
import process.

ResourceOrganizationMembership_ The organization name of the Identify the organization name Conditionally required.
ParentOrganizationName resource's manager. of the resource's manager by
163

Batch
navigating to the Resource If you want to associate a
Directory. resource to an organization
hierarchy, then you must
mention the organization name
of the resource's manager.

Note: To view the imported workers in the Manage Users task, you must run the Update Person Search
Keywords ESS job from the Scheduled Processes work area. You can also choose to run this job automatically
by setting the Enable Keyword Crawler parameter to Y in the Manage HCM Configuration for
Coexistence task. The crawler updates the person-search keywords during the import process for every
worker.
The following figure depicts a sample attribute mapping to import an employee resource.

Additional Tips
• Importing users
164
• Importing resource teams

Related Topics
• Importing Resource Teams and Resource Team Usages Using File-Based Import: Quick Start
Importing Organization Profiles: Quick Start

This topic describes how to get you started with importing organization profiles.
It includes the following information:
• The minimum data required and the prerequisites steps
• Additional tips
With organization profile, you can capture organization information for an account, legal entity, and partner. The organization
profile contains information for the organization, such as the stock symbol, number of employees, and the CEO's name. You
can import new organization profiles or update existing organization profile records, using the File-Based Data Import feature.
The following table lists the file-based import objects and target objects that you can use to import organization profiles. You
can import organization profiles, using these file-based objects.
Account Organization OrganizationProfile

Legal Entity Organization OrganizationProfile

Lead Organization OrganizationProfile

Marketing Campaign Response Organization OrganizationProfile

Partner Organization PartnerInterface


To add organization profiles or to update existing organization profiles using file-based import, your source file must contain
information about the organizations you want to create or update.
To update an existing organization profile, your source file must include the values that enable the import process to identify
the existing records. These values will be source system and source system reference value combination, Oracle Sales Cloud
internal ID, or public unique identifiers, such as business keys or external IDs.
165


The minimum data that is required to import organization profile information depends on the following:
• The purpose of the import. The data requirements are different when you're creating a new organization profile or
updating an existing organization profile record.
update an organization profile record. You can optionally include attributes that are available for import in your import file but
Attribute Description Prerequisite Setup Task Create an Organization Update an Existing

Profile Organization Profile
PartyOrigSystem The code representing

the external source Predefine your source Conditionally required. Conditionally required
system. system code as
enabled for Trading
Community members, Provide reference Provide reference
using the Setup and information to identify information to identify
Maintenance, Manage the existing party. The the existing party. The
Trading Community reference information can reference information can
Source Systems task. be: be:
• PartyId (Oracle • PartyId (Oracle

Sales Cloud Sales Cloud
record ID). record ID).
166

and and
PartyOrigSystemReference PartyOrigSystemReference
(source system (source system
code and source code and source
system reference system reference
values) provided values) provided
when importing when importing
the organization the organization
profile. profile.
• Party Number • Party Number
(public unique (public unique
identifier for an identifier for an
profile). profile).
key such as key such as
name. name.
PartyOrigSystemReference The reference number Identify the reference

or text representing the value from your source Conditionally required Conditionally required
source system unique ID system.
for the organization. Provide reference Provide reference
information to identify information to identify
the existing party. The the existing party. The
reference information can reference information can
be: be:

and and
profile. profile.
profile). profile).
name. name.
OrganizationName The name of the No prerequisite tasks Required The attribute is neither
organization. required nor conditionally
required.

ObjectKey or PartyID The Oracle Sales The attribute is neither

Cloud record ID for the Identify the PartyId by required nor conditionally Conditionally required
organization. exporting the Party required.
object using the Setup
and Maintenance,
167

Manage Bulk Data
Export, Schedule Provide reference
Export Processes task. information to identify
the existing party. The
reference information can
be:
• PartyId (Oracle
Sales Cloud
record ID).
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
• Party Number
(public unique
identifier for an
organization
profile).
• A business
key such as
organization
name.
Type The organization type. No prerequisite tasks The attribute is neither The attribute is neither
The type is set to required nor conditionally required nor conditionally
Account by default for required. required.
new organization profiles.

The following figure shows a sample attribute mapping to import a new organization. In this scenario, origin system and origin
system reference information are used to identify the organization.
The following figure shows a sample attribute mapping to update an existing organization. In this example, the origin source
system and source system reference are used to identify an organization and update the CEO name.
168

Additional Tips
• Importing sales leads
• Importing marketing campaign responses
• Importing partners
Related Topics
Importing Person Profiles: Quick Start

This topic describes how to get you started with importing person profiles. It includes the following information:
• Additional tips
169
A person party profile enables you to import contacts, and household members. For example, you can use person profiles
to import contact information. A person profile contains various attributes, such as first name, last name, and so on. You can
import new person profiles or update existing person profile records using the File-Based Data Import feature.
The following table lists the file-based import objects and target objects that you can use to import person profiles.
Contact PersonProfile

Account (Account Contact) PersonProfile, ContactPersonProfile

Household (Customer Contact) PersonProfile, ContactPersonProfile

Legal Entity (Legal Entity Contact) PersonProfile, ContactPersonProfile

Employee Resource PersonProfile

Lead (Lead Contact) PersonProfile, ContactPersonProfile

Partner Contact PersonProfile

Marketing Campaign Response PersonProfile

(Contact Respondent)

Marketing Campaign Response PersonProfile, ContactPersonProfile

(Marketing Campaign Response
Contact)


To add person profiles or to update existing person profiles using file-based import, your source file must contain information
about the persons.
To update an existing person profile, your source file must include the values that enable the import process to identify the
existing records. These values will be source system and source system reference value combination, Oracle Sales Cloud
170


The minimum data that is required to import person profile information depends on the following:
• The purpose of the import. The data requirements are different when you're creating the person profile or updating
an existing person profile record.
or update a person profile record. You can optionally include attributes that are available for import in your import file but that
Attribute Description Prerequisite Setup Task Create Party and Person Update Person Profile
Profiles Records
ObjectKey or PartyId The Oracle Sales Cloud The attribute is neither

record ID for the party Identify the party ID value required nor conditionally Conditionally required.
(account, contact, by exporting the Party required.
household, or legal entity) object using the Setup
and Maintenance, Provide reference
to which the person information to identify
profile belongs. Manage Bulk Data
Export, Schedule the existing party. The
Export Processes task.
be:
• PartyId (Oracle
Sales Cloud
record ID).
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
171
Profiles Records
the organization
profile.
• Party Number
(public unique
identifier for an
organization
profile).
• A business key
such as person
name.

the external source Predefine your source Conditionally required. Conditionally required.
system for the party system code as
(account, contact, enabled for parties,
using the Setup and Provide reference Provide reference
household, or legal entity) information to identify information to identify
to which the person Maintenance, Manage
Trading Community the existing party. The the existing party. The
profile belongs. reference information can reference information can
Source Systems task.
be: be:

and and
profile. profile.
profile). profile).
• A business • A business key
key such as such as person
organization name.
name.

or text representing the value from your source Conditionally required. Conditionally required.
for the party (account, Provide reference Provide reference
contact, household, or information to identify information to identify
legal entity) to which the the existing party. The the existing party. The
person profile belongs. reference information can reference information can
be: be:

and and
172
Profiles Records
profile. profile.
profile). profile).
• A business key • A business key
such as person such as person
name. name.
PersonFirstName First name of a person No prerequisite tasks Required The attribute is neither
party. required nor conditionally
required.

PersonLastName Last name of a person No prerequisite tasks Required The attribute is neither
required.

The following figure depicts a sample attribute mapping to import a new contact. In this scenario, the OrigSystem and
OrigSystem values identify the party.
173
The following figure depicts a sample attribute mapping to update a contact. In this scenario, the OrigSystem and OrigSystem
values identify the party and update the person's middle name.

Additional Tips
• Importing person profiles

Related Topics
174
Importing Relationships: Quick Start

This topic describes how to get you started with importing relationships.

• Additional tips
The following table lists the file-based import objects and target objects that you can use to import relationships.
Account Organization Relationship

Account Person (a contact for an account) ContactPersonProfile

Household Household Relationship

Legal Entity Person (a contact for a legal entity) ContactPersonProfile

Contact Person ContactRelationship

Lead Lead Contact ContactPersonProfile

Partner Contact Partner Contact Partner

Campaign Response Campaign Response Contact ContactPersonProfile

With a relationship, you can capture the interconnection between parties such as contacts, households, and so on. For
example, you can capture the relationship between an account and the account's contact person by interconnecting the
contact person's party ID with the account's organization party ID using the CONTACT relationship type. Similarly, you
can associate one or more persons with a household, or family, using the relationship type MEMBER. You can import new
relationships or update existing relationship records, using the File-Based Data Import feature.

To add relationships to a party or update existing relationship assignments using file-based import, your source file must
contain data that identifies the subject and object of a relationship. For instance, if you're creating an 'is an employee of'
relationship between a person party and an organization, you need to provide reference information that identifies both the
subject, the person party, and the object, the organization, parties.
If you're creating the party and the relationship assignment in the same import activity, then group the party and relationship
import the associated relationship.
175
To add an relationship to an existing party, or to update an existing relationship record, your source file must include values
that enable the import process to identify the existing records. These values will be either source system and source system
reference value combination, Oracle Sales Cloud internal ID, or public unique identifiers, such as business keys or external
IDs.

The minimum that is required to import relationship information depends on the following:
relationship in the same import batch, adding relationships to an existing party, or updating an relationship record.
Attribute Description Prerequisite Setup Task Creating Party and Creating Relationship
Relationship Records in Record for an Existing
internal ID for the party value by exporting the required nor conditionally Conditionally required.
(account, contact, Party object using the required.
to which the relationship Manage Bulk Data information to identify
belongs. Export, Schedule Export the existing party. The
be:
• PartyId (Oracle
Sales Cloud
internal ID).
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
• Business
keys such as
Subject_Id,Object_Id,Relationship
and
Relationship_Code.
PartyOrigSystem The code representing Identify the source Conditionally required

the source system for the system code that was Conditionally required
party (account, contact, used when you imported
176
household, or legal entity) the party in a prior batch, If the source of your
to which the relationship or identify the source data is a third party or Provide reference
belongs. system code that you will external system, and you information to identify
use when importing the intend to import updates the existing party. The
party in the same batch to previously imported reference information can
as this relationship. records from the same be:
system, provide the
original source system • PartyId (Oracle
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
• Business
keys such as
and
Relationship_Code.
PartyOrigSystemReference The reference number Identify the reference Conditionally required

or text representing the value from your source Conditionally required
source system unique ID system that was used If the source of your
for the party (account, when you imported data is a third party or Provide reference
contact, household, or the party in a prior external system, and you information to identify
legal entity) to which the batch, or identify the intend to import updates the existing party. The
relationship belongs. source system reference to previously imported reference information can
that you will use when records from the same be:
importing the party in system, provide the
the same batch as this original source system • PartyId (Oracle
relationship. and source system Sales Cloud

• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
• Business
keys such as
and
Relationship_Code.
or update a relationship record. You can optionally include attributes that are available for import in your import file but that
177
RelationshipCode Describes the directional You can view the Conditionally required. Conditionally required.
connection between relationship type code
the object and subject definition from the Setup If the source of your If the source of your
relationship. For example, and Maintenance, data is a third party or data is a third party or
Employer of verses Manage Relationship external system, and you external system, and you
Employee of. Types task. intend to import updates intend to import updates
to previously imported to previously imported

RelationshipType Describes the You can view valid Required Required

relationship, such as relationship types
Contact or Membership. from the Setup and
Maintenance, Manage
Relationship Types task.

RelOrigSystem A source system code No prerequisite tasks Conditionally required. Conditionally required. .
that identifies the original
source system of the If the source of your If the source of your
relationship between the data is a third party or data is a third party or
object and the subject external system, and you external system, and you
parties. intend to import updates intend to import updates
to previously imported to previously imported

RelOrigSystemReference A source system No prerequisite tasks Conditionally required. Conditionally required.

reference that identifies
the original reference If the source of your If the source of your
ID of the relationship data is a third party or data is a third party or
between the object and external system, and you external system, and you
the subject parties in the intend to import updates intend to import updates
source system. to previously imported to previously imported

SubOrigSystem A source system code No prerequisite tasks This attribute is neither Conditionally required.
that identifies the original required nor conditionally
source system of the required If the source of your
subject party of the data is a third party or
relationship. external system, and you
intend to import updates
to previously imported
records from the same
system, provide the
original source system
and source system
reference values.
178

SubOrigSystemReference A reference ID for No prerequisite tasks This attribute is neither Conditionally required.
the subject of the required nor conditionally
relationship. If importing required If the source of your
from another system, data is a third party or
use the unique reference external system, and you
for the subject of the intend to import updates
relationship in that source to previously imported
system. records from the same
system, provide the
and source system
reference values.

There are four sets of reference information that you can use to refer to a record. However, only set of reference information
is sufficient to identify a record. If you have mentioned multiple reference sets that has conflict, then it results in an error. The
import process recognizes reference information in this order:
2. Public User ID such as PartyNumber (also called RegistryID), PartySiteNumber, and so on.
3. Origin system and Origin system reference
4. Other reference information such as business keys
The following figure depicts a sample attribute mapping to import a relationship between two parties. While importing
relationships, use the OrigSystem and OrigSystemReference values to identify one party and the SubOrigSystem and
SubOrigSystem values to identify the second party.
179

Additional Tips
• Importing relationships
Importing Sales Profiles: Quick Start

This topic describes how to get you started with importing sales profiles. It includes the following information:

• Additional tips
A sales profile enables you to capture information about a selling relationship with an account or consumer. When a party has
one sell-to address, it ceases to be a sales prospect and becomes a sales profile. You can import sales profiles or update
existing sales profiles, using the File-Based Data Import feature. The sales profile includes attributes that can be used for
assigning territories and providing account ownership details. You must have an organization or person with a sell-to address
defined before you can import sales profiles.
The following table lists the file-based import objects and target objects that you can use to import sales profiles.
Contact Person PersonProfile, SalesProfile

Account Organization OrganizationProfile, SalesProfile

Account Household GroupProfile, SalesProfile

180

To add a sales profile to an account or to update an existing sales profile using file-based import, your source file must
contain information about the customer organization or consumer person party to which the sales profile belongs. You map
your source file data to the organization or person profile target object and to the sales profile target object.
If you're creating the party and the sales profile in the same import activity, then group the party and sales profile data
together in your source file. The import process can import the party and then identify the party record so that it can import
the associated sales profile.
To add a sales profile to an existing party or to update an existing sales profile record, your source file must include the values
that enable the import process to identify the existing records. These values are source system and source system reference
value combination, internal ID, or public unique identifiers, such as business keys or external IDs.
If the source of your data is an external application, and if you intend to import updates to previously imported records
from the external application, then you can provide the source system code and the unique reference value for the source
system's record in your source file. The file-based data import process stores a cross-reference between the source system
information and internal ID. The import process uses the combination of source system and source system reference value to
identify the existing record.
and first name uniquely identify a person. An external ID is a unique record identifier from an application outside of Oracle
Sales Cloud. You can use the following business keys or external IDs in Oracle Sales Cloud:

When the source of your data isn't an external application and you don't intend to regularly update the data, you don't need
the source system information. To import updates to your existing data, you can export the internal ID and add it to your
source file. The import process uses the internal ID to identify the existing record.

The minimum data that is required to import sales profile information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the party and the sales
profile in the same import batch, adding new sales profile to an existing party, or updating a sales profile record.
• Identifying and associating records. In some cases, you can select which attributes you want to provide to the import
process when identifying and associating records.
181
or update a sales profile record. You can optionally include attributes that are available for import in your import file but that
Attribute Description Prerequisite Setup Creating Party Creating Sales Updating Sales
Task and Sales Profile Profile Record for an Profile Record
Records in the Existing Party
Same Batch

source system for was used when required required
the party (account you imported the Provide the source
or contact) to which party in a prior system and source Provide reference Provide reference
the sales profile batch, or identify the system reference information to information to
belongs. source system code values if the source identify the existing identify the existing
that you use when of your data is party. The reference party. The reference
importing the party a third party or information can be: information can be:
in the same batch external application
as this sales profile. and you intend to • PartyId • PartyId
import updates to (Oracle Sales (Oracle Sales
previously imported Cloud record Cloud record
records from the ID). ID).
same system.

and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile). profile).
name. name.
number or text reference value from required Conditionally Conditionally
representing the your source system required required
source system that was used when Provide the source
unique ID for the you imported the system and source Provide reference Provide reference
party (account or party in a prior system reference information to information to
contact) to which batch, or identify values if the source identify the existing identify the existing
the sales profile the source system of your data is party. The reference party. The reference
belongs. reference you use a third party or information can be: information can be:
when importing the external application
party in the same and you intend to • PartyId • PartyId
182
Same Batch
batch as this sales previously imported Cloud record Cloud record
profile records from the ID). ID).
same application. • PartyOrigSystem • PartyOrigSystem
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile). profile).
name. name.
PartyId The record ID for The attribute is

the party (account Identify the party ID neither required Conditionally Conditionally
or contact) to which value by exporting nor conditionally required required
the sales profile the Party object required.
belongs. using Setup and
information to information to
Manage Bulk Data
( record ID). ( record ID).
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
183
Same Batch
for an for an
profile). profile).
name. name.
AccountDirectorId The unique party

ID of the resource Identify the party ID Conditionally Conditionally Conditionally
assigned to manage value of the account required. required. required.
the sales profile. owner by exporting
the Party object
using Setup and By default, the By default, the By default, the
Maintenance, user importing user importing user importing
Manage Bulk Data the account is the account is the account is
Export, Schedule designated as the designated as the designated as the
Export Processes account owner. To account owner. To account owner. To
task. specify a different specify a different specify a different
account owner, account owner, account owner,
include one of include one of include one of
the reference the reference the reference
information for the information for the information for the
account owner in account owner in account owner in
the import file: the import file: the import file:
• Party ID of • Party ID of • Party ID of

the account the account the account
owner in the owner in the owner in the
AccountDirectorId AccountDirectorId AccountDirectorId
column. column. column.
• Origin system • Origin system • Origin system
and origin and origin and origin
system system system
reference of reference of reference of
OWNER_ORIG_SYSTEMOWNER_ORIG_SYSTEMOWNER_ORIG_SYSTEM
AND AND AND
OWNER_ORIG_SYSTEM_REFERENCE
OWNER_ORIG_SYSTEM_R
columns. columns. columns.
• Party • Party • Party
Number of Number of Number of
OWNER_PARTY_NUMBER OWNER_PARTY_NUMBER OWNER_PARTY_NUMBER
OwnerEmailAddress The e-mail address

of the resource that Identify the party ID Conditionally Conditionally Conditionally
owns and manages and party number required. required. required.
the sales profile of the account
owner by exporting
the Party object Specify an By default, the By default, the
using Setup and account owner, by user importing user importing
Maintenance, including one of the account is the account is
Manage Bulk Data designated as the designated as the
Export, Schedule account owner. account owner.
Export Processes
task.
184
Same Batch
following reference
information: To specify a different To specify a different
account owner, account owner,
include one of the include one of the
• E-mail
Address of
the account
owner
• E-mail • E-mail
• Party ID of Address of Address of
owner in the owner owner
OwnerPartyId
column • Party ID of • Party ID of
the account the account
• Party owner in the owner in the
Number of OwnerPartyId OwnerPartyId
the account column column
owner in the
OwnerPartyNumber • Party • Party
column Number of Number of
owner in the owner in the
OwnerPartyNumber OwnerPartyNumber
column column
OwnerPartyID The unique party

assigned to manage and party number required. required. required.
owner by exporting
Manage Bulk Data following reference designated as the designated as the
Export, Schedule information: account owner. account owner.
Export Processes
task. • E-mail
Address of To specify a different To specify a different
the account account owner, account owner,
owner include one of the include one of the
• Party ID of information: information:
the account
owner in the
• E-mail • E-Mail
OwnerPartyId
Address of Address of
column
• Party owner owner
Number of
• Party ID of • Party ID of
the account
owner in the
OwnerPartyNumber
OwnerPartyId OwnerPartyId
column
column column
• Party • Party
Number of Number of
column column
OwnerPartyNumber The unique party

number of the Identify the party ID Conditionally Conditionally Conditionally
resource assigned and party number required. required. required.
of the account
185
Same Batch
to manage the sales owner by exporting
profile the Party object Specify an By default, the By default, the
Export Processes
task. • E-mail
the account
owner in the
OwnerPartyId
column
Number of
the account
owner in the
OwnerPartyNumber
column
column column
• Party • Party
Number of Number of
column column
Note: During import, the attribute Type is set to Account for all new accounts.
The following figure shows a sample attribute mapping to import a new sales profile for an existing party. In this scenario,
origin system and origin system reference information are used to identify the existing party and the new sales profile.

186
Additional Tips
Importing Accounts
Importing Common Supporting Objects: Documentation Overview
Common supporting objects often support the primary import objects. For example, additional party identifiers support
accounts, contacts, and households. Notes support leads and opportunities. For a mapping of primary import objects to the
common object import topics that support them, see:
Related Topics
• Importing Common Supporting Objects: Overview
Importing Accounts Using File-Based Import: Explained

This topic explains how to prepare and import account data from an external data source into Oracle Sales Cloud using the
File-Based Data Import feature. An account is an entity with whom you have a selling relationship. Oracle Sales Cloud refers
to sales profile and sales prospects collectively as an Account. An account business object lets you capture all information
about an account, such as the account profile, account contact relationships information, and account contact points.
A sales profile is a specific sell-to entity within a given account. You can create leads and opportunities for sales profiles. An
entity with a sales profile 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.
• Account: A sales profile 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 Account import object to import sales profiles or sales prospects of the type organization. You can use the
Household import object to import accounts of the type household, and the Contact import object to import accounts of the
type person. 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 profiles?
187
• How does your legacy or source system represent the account information compared to how Oracle Sales Cloud
• Do you have to configure values in Oracle Sales Cloud to map your existing data values to the Account import
object?

You must understand how your account data corresponds with the data in Oracle Sales Cloud so that you can map your
structure of the data for an account.
The Account 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 profiles. These child entities
components that make up the account.
The following figure shows the account object and its child entities.
Organization Profile
Primary Contact SellTo Sales Additional

Classification Address Url Fax
Phone PersonProfile Address Profile Name
PrimaryPhone Address Address Fax

ContactPreference ContactPreference Purpose ContactPreference


The organization profile contains basic information about the account, such as the customer name and party usage. For each
account, you can assign classifications, contacts, sell to addresses, phone details, and additional names. The contact of the
account, in turn, includes other child entities that capture information about the contact, such as contact job, contact primary
phone, contact primary address, and contact e-mail.
188
Note: All contact entities, such as primary phone or e-mail, include a child entity that captures the contact
preference. For example, the Primary Phone Contact Preference entity captures the contact preference of the
account for the contact method primary phone.

one-to-many relationships between the structural components that make up the account.
locations that you need to complete this task, see the topic Account Import Objects : How They Work Together.
Note: You can use the keyword importing accounts to search for related topics in Oracle Sales Cloud Help.
If you want to configure the object to import your legacy or source data, then you must use the 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 configurable attributes, which you can then map
to your source file data. You can use the same source file to import both the configurable attributes and the standard import
object attributes.
Importing Accounts Using File-Based Data Import

For the account business object, you must use the File-Based Data Import feature. You prepare XML or text source data files
The Define File 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. When you're creating a new account, you import the Account object. You must be assigned the Customer
Relationship Management Application Administrator job role to access and submit the import activities for accounts.
When importing account information, you first import the basic account profile information, followed by the child entities
for the account. 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 account.
You must provide the PartyOrigSystem and PartyOrigSystemReference of the account when importing contacts for
the account. PartyOrigSystem is the source system code that identifies the source of the information being imported.
and a unique reference. When importing contact information for an account, you must provide the relationship reference
information. This information is required because a contact can have multiple relationships with an account.

Alternatively, you can also navigate to the Customer Center work area to view the account information that you have
imported.
189
Related Topics
Account Import Objects: How They Work Together

The Account import object lets you import accounts, their detailed information, and contacts related to the account. This
topic describes the Account import object. It introduces the following:
• Target objects for the Account import objects
• Target import object attribute reference guide files for evaluating and mapping source file data
Account Target Import Object Concepts

You use the Account import object to import accounts and contacts related to accounts. The Account import object is split
into separate target import objects for organizing the individual attributes of the account and account contact.
The target import objects in the Account import object are generally grouped into information about the account and
information about the account contact. The organization profile is the target import object containing attributes to import
information about the account. You can have multiple contacts associated with an account.
When updating an existing account with additional information, you must provide the parent reference information for the
existing account. When importing account contacts or contact information for an account, 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
an account-contact relationship, then the import process creates a relationship.
To update the information for an existing account or to create an account record, you can import account profile information,
addresses, and contact points, such as a phone and fax. The following target import objects are for creating and
updating account information: OrganizationProfile, Fax, Address, PrimaryPhone, Url, SalesAccountProfile, Classification,
AdditionalName, Relationship, SellToAddress, and AdditionalIdentifier.
To update or to create an account contact, use the following target import objects: ContactPersonProfile, ContactJob,

190
the Application Composer Extensibility features for the account.

objects.
OrganizationProfile Includes detailed account information, such HZ_ IMP_ PARTIES_ T_Reference
as, organization name and organization type.

PrimaryPhone Account's primary phone number. If the HZ_ IMP_ CONTACTPTS_T_ Reference
account has multiple phone numbers, one
of the phone numbers is designated as the
primary phone number.

Address Account's address. HZ_ IMP_ LOCATIONS_ T_Reference

Classification Account's classification. HZ_ IMP_ CLASSIFICS_ T_Reference

AdditionalName Account's additional or alternative name. HZ_ IMP_ ADDTNLPARTYNAMES_

T_Reference

Fax Account's fax number. HZ_ IMP_ CONTACTPTS_T _Reference

FaxContactPreference Indicates the account preference about being HZ_ IMP_ CONTACTPREFS_ Reference
contacted through Fax.

Url Account's URL. HZ_ IMP_ CONTACTPTS_T_ Reference

SalesProfile Account's sales account information. A sales ZCA_ IMP_ SALES_ACCOUNTS _Reference
account is a specific sell-to entity within a
given account. an account can have multiple
sales accounts and sales profiles.

SellToAddress Account's addresses and party sites HZ_ IMP_ PARTYSITES_T_ Reference
information. If party site usage of an address
is not defined, then the import process sets
191

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.

AdditionalIdentifier Account's additional identifier information. HZ_ IMP_ ADDTNLPARTYIDS_ T _Reference

Relationship Account's relationship information. You HZ_ IMP_ RELSHIPS_ T_Reference

must enter a relationship code in the
RelationshipCode column, when creating a
relationship.

ContactPersonProfile Account contact's person information. HZ_ IMP_ RELSHIPS_ T_Reference

ContactAdditionalName Account contact's additional name. HZ_ IMP_ ADDTNLPARTYNAMES_ T

_Reference

ContactEmail Account contact's email. HZ_ IMP_ CONTACTPTS_T_ Reference

ContactInstantMessenger Account contact's instant messenger or HZ_ IMP_ CONTACTPTS_T_ Reference

social networking information.

ContactPrimaryAddress Account contact's primary address. If the HZ_ IMP_ PARTYSITES_T _Reference
address.

ContactFax Account contact's fax. HZ_ IMP_ CONTACTPTS_T_ Reference

ContactJob Account contact's job information. HZ_ IMP_ CONTACTS_ T_Reference

ContactMobile Account contact's mobile number. HZ_ IMP_ CONTACTPTS_T_ Reference

ContactPrimaryPhone Account contact's primary phone number. HZ_ IMP_ CONTACTPTS_T _Reference
If the account has multiple phone numbers,

PrimaryPhoneContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS _Reference
about being contacted through phone.

ContactEmailContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS_ Reference
about being contacted through e-mail.

ContactFaxContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS_ Reference
about being contacted through Fax.

ContactMobileContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS_ Reference
about being contacted through mobile
phone.
192

ContactPrimaryAddressContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS _Reference
about being contacted at the primary
address.

ContactPrimaryPhoneContactPreference Indicates the account contact preference HZ_ IMP_ CONTACTPREFS _Reference
about being contacted through the primary
phone number.

Related Topics
• File Based Data Import for Oracle Sales Cloud
Importing Sales Profiles Using File-Based Import: Quick Start

This topic describes how to get you started with importing sales profiles. It includes the following information:

• Additional tips
A sales profile enables you to capture information about a selling relationship with an account or consumer. When a party has
one sell-to address, it ceases to be a sales prospect and becomes a sales profile. You can import sales profiles or update
existing sales profiles, using the File-Based Data Import feature. The sales profile includes attributes that can be used for
assigning territories and providing account ownership details. You must have an organization or person with a sell-to address
defined before you can import sales profiles.
The following table lists the file-based import objects and target objects that you can use to import sales profiles.
Contact Person PersonProfile, SalesProfile

Account Organization OrganizationProfile, SalesProfile

Account Household GroupProfile, SalesProfile

193

To add a sales profile to an account or to update an existing sales profile using file-based import, your source file must
contain information about the customer organization or consumer person party to which the sales profile belongs. You map
your source file data to the organization or person profile target object and to the sales profile target object.
If you're creating the party and the sales profile in the same import activity, then group the party and sales profile data
together in your source file. The import process can import the party and then identify the party record so that it can import
the associated sales profile.
To add a sales profile to an existing party or to update an existing sales profile record, your source file must include the values
that enable the import process to identify the existing records. These values are source system and source system reference
value combination, internal ID, or public unique identifiers, such as business keys or external IDs.
If the source of your data is an external application, and if you intend to import updates to previously imported records
from the external application, then you can provide the source system code and the unique reference value for the source
system's record in your source file. The file-based data import process stores a cross-reference between the source system
information and internal ID. The import process uses the combination of source system and source system reference value to
identify the existing record.
and first name uniquely identify a person. An external ID is a unique record identifier from an application outside of Oracle
Sales Cloud. You can use the following business keys or external IDs in Oracle Sales Cloud:

When the source of your data isn't an external application and you don't intend to regularly update the data, you don't need
the source system information. To import updates to your existing data, you can export the internal ID and add it to your
source file. The import process uses the internal ID to identify the existing record.

The minimum data that is required to import sales profile information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the party and the sales
profile in the same import batch, adding new sales profile to an existing party, or updating a sales profile record.
194
or update a sales profile record. You can optionally include attributes that are available for import in your import file but that
Same Batch

source system for was used when required required
the party (account you imported the Provide the source
or contact) to which party in a prior system and source Provide reference Provide reference
the sales profile batch, or identify the system reference information to information to
belongs. source system code values if the source identify the existing identify the existing
that you use when of your data is party. The reference party. The reference
importing the party a third party or information can be: information can be:
in the same batch external application
as this sales profile. and you intend to • PartyId • PartyId
previously imported Cloud record Cloud record
records from the ID). ID).
same system.

and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile). profile).
name. name.
number or text reference value from required Conditionally Conditionally
representing the your source system required required
source system that was used when Provide the source
unique ID for the you imported the system and source Provide reference Provide reference
party (account or party in a prior system reference information to information to
contact) to which batch, or identify values if the source identify the existing identify the existing
the sales profile the source system of your data is party. The reference party. The reference
belongs. reference you use a third party or information can be: information can be:
when importing the external application
party in the same and you intend to • PartyId • PartyId
195
Same Batch
batch as this sales previously imported Cloud record Cloud record
profile records from the ID). ID).
same application. • PartyOrigSystem • PartyOrigSystem
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile). profile).
name. name.
PartyId The record ID for The attribute is

the party (account Identify the party ID neither required Conditionally Conditionally
or contact) to which value by exporting nor conditionally required required
the sales profile the Party object required.
belongs. using Setup and
information to information to
Manage Bulk Data
( record ID). ( record ID).
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
196
Same Batch
for an for an
profile). profile).
name. name.
AccountDirectorId The unique party

assigned to manage value of the account required. required. required.
the sales profile. owner by exporting
the Party object
using Setup and By default, the By default, the By default, the
Maintenance, user importing user importing user importing
Manage Bulk Data the account is the account is the account is
Export, Schedule designated as the designated as the designated as the
Export Processes account owner. To account owner. To account owner. To
task. specify a different specify a different specify a different
account owner, account owner, account owner,
include one of include one of include one of
the reference the reference the reference
information for the information for the information for the
account owner in account owner in account owner in
the import file: the import file: the import file:
• Party ID of • Party ID of • Party ID of

AccountDirectorId AccountDirectorId AccountDirectorId
• Origin system • Origin system • Origin system
and origin and origin and origin
system system system
reference of reference of reference of
OWNER_ORIG_SYSTEMOWNER_ORIG_SYSTEMOWNER_ORIG_SYSTEM
AND AND AND
OWNER_ORIG_SYSTEM_R
columns. columns. columns.
• Party • Party • Party
Number of Number of Number of
OWNER_PARTY_NUMBER OWNER_PARTY_NUMBER OWNER_PARTY_NUMBER
OwnerEmailAddress The e-mail address

of the resource that Identify the party ID Conditionally Conditionally Conditionally
owns and manages and party number required. required. required.
owner by exporting
Manage Bulk Data designated as the designated as the
Export, Schedule account owner. account owner.
Export Processes
task.
197
Same Batch
following reference
information: To specify a different To specify a different
account owner, account owner,
include one of the include one of the
• E-mail
Address of
the account
owner
• Party ID of Address of Address of
owner in the owner owner
OwnerPartyId
column • Party ID of • Party ID of
• Party owner in the owner in the
Number of OwnerPartyId OwnerPartyId
the account column column
owner in the
OwnerPartyNumber • Party • Party
column Number of Number of
column column
OwnerPartyID The unique party

assigned to manage and party number required. required. required.
owner by exporting
Export Processes
task. • E-mail
the account
owner in the
• E-mail • E-Mail
OwnerPartyId
column
Number of
the account
owner in the
OwnerPartyNumber
column
column column
• Party • Party
Number of Number of
column column
OwnerPartyNumber The unique party

number of the Identify the party ID Conditionally Conditionally Conditionally
resource assigned and party number required. required. required.
of the account
198
Same Batch
to manage the sales owner by exporting
profile the Party object Specify an By default, the By default, the
Export Processes
task. • E-mail
the account
owner in the
OwnerPartyId
column
Number of
the account
owner in the
OwnerPartyNumber
column
column column
• Party • Party
Number of Number of
column column
Note: During import, the attribute Type is set to Account for all new accounts.
The following figure shows a sample attribute mapping to import a new sales profile for an existing party. In this scenario,
origin system and origin system reference information are used to identify the existing party and the new sales profile.

199
Additional Tips
Importing Contacts
Importing Contacts and Consumers: Important Considerations
The Consumer object is only applicable if you are using release 1.0.7 or an earlier release. All capabilities of the Consumer
object are included in the Contact object for releases 1.0.8 and later. If you are upgrading from an earlier release to release
1.0.8 or later, it is recommended that you use the Contact object to update your consumer information using file-based data
import in the current release.

Related Topics
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 an individual who is a customer or a prospect, or a contact for an existing
customer or consumer, or a contact that does not yet have an established business association with a customer or
consumer. Thus, a contact could be an employee of a customer organization, a person you may have met who could help
with your business, or a prospective or current individual customer. 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, e-mail
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 account objects.
200
• How does your legacy system or source system represent the contact compared to how Oracle Sales Cloud
business?

You must understand how your contact data corresponds with the data in Oracle Sales Cloud so that you can map your
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, e-mail IDs,
Web site addresses, or instant messenger IDs.
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 e-mail.
Note: All contact-related entities, such phone or e-mail, 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.
To facilitate importing contacts, Oracle Sales Cloud incorporates the structure of the contact business object into import
objects. The import object for contacts is Contact.

one-to-many relationships between the structural components that make up the contact.
Contact Contact Import Objects: How They Work Together

Note:
201
You can use the keyword importing contacts to search for related topics in Oracle Sales Cloud help.
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
for each import object. When you're 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.

can also access the Customer Center or Partner Center work area to view the contact information that you have imported.
Related Topics
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 objects for the Contact import object
Contact Target Import Objects

You use the contact import object to import contact and information. The contact import object is split into separate target
import objects for organizing the individual attributes of the contact and the contact's relationship with other parties.
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
202
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 and contact
preference information: PersonProfile, Fax, PrimaryPhone, Url, SalesProfile, Classification, AdditionalName, Relationship, and
AdditionalIdentifier.
To update or create a contact point for a contact relationship, use the following target import objects: ContactRelationship,
ContactJob, ContactAddress, ContactEmail, ContactPhone, ContactMobile, ContactInstantMessenger, and ContactFax.
All contact-point-related entities, such as phone or e-mail, include a child entity that captures the contact preference. For
example, the ContactPhoneContactPreference entity captures the contact preference of the primary phone contact method.

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 configuration features for the contact object.

objects.
PersonProfile Includes information that identifies a contact, HZ_ IMP_ PARTIES_ T_Reference
such as first name, last name, date of birth,
and so on.

SalesProfile Includes detailed information about a sales ZCA_ IMP_ Sales_ Accounts_ Reference
profile. A sales profile is a specific sell-to
entity within a given account. An account or
contact can have multiple sales profiles.

203
Fax Contact's fax number. HZ_ IMP_ CONTACTPTS_ T_Reference

FaxContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through Fax.

Phone Contact's phone number. If the contact has HZ_ IMP_ CONTACTPTS_ T_Reference
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.

PhoneContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
by phone.

Email Contact's e-mail. HZ_ IMP_ CONTACTPTS_ T_Reference

EmailContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through e-mail.

InstantMessenger Contact's instant messenger information. HZ_ IMP_ CONTACTPTS_ T_Reference

Mobile Contact's mobile number. HZ_ IMP_ CONTACTPTS_ T_Reference

MobileContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through mobile phone.

Classification Contact's classification information. HZ_ IMP_ CLASSIFICS_ T_Reference

Classification lets you categorize entities,
such as parties, projects, tasks, and orders
as hierarchies.

Address Contact's address. If the contact has HZ_ IMP_ PARTYSITES_ T_Reference
multiple addresses, then the first address is

AddressContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
at the primary address.

AdditionalName Contact's alternative name. HZ_ IMP_ ADDTNLPARTYNAMES_

T_Reference

AdditionalIdentifier Includes the basic information about an HZ_ IMP_ ADDTNLPARTYIDS_ T_Reference
additional identifier for the contact.

ContactRelationship Includes information about a relationship HZ_ IMP_ RELSHIPS_ T_Reference

between the contact and other parties.

ContactEmail Contact's e-mail contact point. HZ_ IMP_ CONTACTPTS_ T_Reference
204

ContactEmailContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through the e-mail contact point.

ContactFax Indicates the number of the fax contact point HZ_ IMP_ CONTACTPTS_ T_Reference
of the contact.

ContactFaxContactPreference Contact's preference about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through the fax contact point.

ContactInstantMessenger Contact's instant messenger contact point. HZ_ IMP_ CONTACTPTS_ T_Reference

ContactMobile Contact's mobile contact point. HZ_ IMP_ CONTACTPTS_ T_Reference

ContactMobileContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through the mobile phone contact point.

ContactPhone Contact's phone contact point. If the contact HZ_ IMP_ CONTACTPTS_ T_Reference
has multiple phone numbers, then the first
phone number is designated as the primary
phone number.

ContactPhoneContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
through the phone contact point.

ContactAddress Contact's address contact point. If the HZ_ IMP_ PARTYSITES_ T_Reference
contact has multiple addresses, then the
first address is designated as the primary
address.

ContactAddressContactPreference Contact's preferences about being contacted HZ_ IMP_ CONTACTPREFS_ Reference
at the address contact point.

ContactJob Contacts' job information. HZ_ IMP_ CONTACTS_ T_Reference

Related Topics
Importing Person Profiles Using File-Based Import: Quick Start

This topic describes how to get you started with importing person profiles. It includes the following information:
205
• Additional tips
A person party profile enables you to import contacts, and household members. For example, you can use person profiles
to import contact information. A person profile contains various attributes, such as first name, last name, and so on. You can
import new person profiles or update existing person profile records using the File-Based Data Import feature.
The following table lists the file-based import objects and target objects that you can use to import person profiles.
Contact PersonProfile

Account (Account Contact) PersonProfile, ContactPersonProfile

Household (Customer Contact) PersonProfile, ContactPersonProfile

Legal Entity (Legal Entity Contact) PersonProfile, ContactPersonProfile

Employee Resource PersonProfile

Lead (Lead Contact) PersonProfile, ContactPersonProfile

Partner Contact PersonProfile

Marketing Campaign Response PersonProfile

(Contact Respondent)

Marketing Campaign Response PersonProfile, ContactPersonProfile

(Marketing Campaign Response
Contact)


To add person profiles or to update existing person profiles using file-based import, your source file must contain information
about the persons.
To update an existing person profile, your source file must include the values that enable the import process to identify the
206


The minimum data that is required to import person profile information depends on the following:
• The purpose of the import. The data requirements are different when you're creating the person profile or updating
an existing person profile record.
or update a person profile record. You can optionally include attributes that are available for import in your import file but that
Profiles Records
ObjectKey or PartyId The Oracle Sales Cloud The attribute is neither

record ID for the party Identify the party ID value required nor conditionally Conditionally required.
(account, contact, by exporting the Party required.
household, or legal entity) object using the Setup
and Maintenance, Provide reference
to which the person information to identify
profile belongs. Manage Bulk Data
Export, Schedule the existing party. The
Export Processes task.
be:
• PartyId (Oracle
Sales Cloud
record ID).
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
207
Profiles Records
the organization
profile.
• Party Number
(public unique
identifier for an
organization
profile).
• A business key
such as person
name.

the external source Predefine your source Conditionally required. Conditionally required.
system for the party system code as
(account, contact, enabled for parties,
using the Setup and Provide reference Provide reference
household, or legal entity) information to identify information to identify
to which the person Maintenance, Manage
Trading Community the existing party. The the existing party. The
profile belongs. reference information can reference information can
Source Systems task.
be: be:

and and
profile. profile.
profile). profile).
• A business • A business key
key such as such as person
organization name.
name.

or text representing the value from your source Conditionally required. Conditionally required.
for the party (account, Provide reference Provide reference
contact, household, or information to identify information to identify
legal entity) to which the the existing party. The the existing party. The
person profile belongs. reference information can reference information can
be: be:

and and
208
Profiles Records
profile. profile.
profile). profile).
• A business key • A business key
such as person such as person
name. name.
PersonFirstName First name of a person No prerequisite tasks Required The attribute is neither
required.

PersonLastName Last name of a person No prerequisite tasks Required The attribute is neither
required.

The following figure depicts a sample attribute mapping to import a new contact. In this scenario, the OrigSystem and
OrigSystem values identify the party.
209
The following figure depicts a sample attribute mapping to update a contact. In this scenario, the OrigSystem and OrigSystem
values identify the party and update the person's middle name.

Additional Tips
• Importing person profiles

Related Topics
210
Importing Contact Points Using File-Based Import: Quick Start

This topic describes how to get you started with importing contact points. It includes the following information:
• An overview of contact points
• Additional Tips
The following table lists the file-based import objects and target objects that you can use to import contact points directly
Contact Person Email, Fax, InstantMessenger, Mobile,

Phone, Address

Account Organization PrimaryPhone, Fax, Url, Address

Household Organization E-mail, Fax, InstantMessenger, Mobile,

Phone, Address, Url

Legal Entity Organization Fax, PrimaryPhone, PrimaryAddress, Url

Lead Organization (lead organization) OrganizationProfileFax,


Lead Person (lead individual) Email, PersonProfileFax,

InstantMessenger, Mobile, PersonAddress,
PersonProfilePrimaryPhone

Lead Person (contact at lead organization) ContactEmail, ContactFax,

ContactPrimaryPhone

Partner Organization Fax, PrimaryPhone, PrimaryAddress, Url

Partner Contact Person (contact for a partner) Email, Fax, InstantMessenger, Mobile,
PrimaryPhone, PrimaryAddress

Campaign Response Organization (respondent organization) OrganizationProfileFax,

211

Campaign Response Person (individual respondent) Email, PersonProfileFax, InstantMessenger,

Mobile, PersonProfilePrimaryPhone,
PersonAddress

Campaign Response Person (contact at respondent organization) ContactEmail, ContactFax,

ContactPrimaryPhone

The following table lists the file-based import objects and target objects that you can use to import contact points for a
contact relationship.
Contact Person (a contact for another root object ContactEmail, ContactFax,

such as account) ContactInstantMessenger, ContactMobile,
ContactAddress, ContactPhone

Account Person (a contact for an account) ContactEmail, ContactFax,

ContactPrimaryPhone

Legal Entity Person (contact for a legal entity) ContactEmail, ContactFax,

ContactPrimaryPhone

Contact Points Overview

A contact is an individual who is a customer or a prospect, or a contact for an existing customer or consumer, or a contact
that does not yet have an established business association with a customer or consumer. Thus, a contact could be an
employee of a customer organization, a person you may have met who could help with your business, or a prospective or
current individual customer. 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, e-mail IDs, URLs, messenger IDs, and so on.
The contact object also contains contact preference information for the contact.
Note: A contact point cannot be shared among multiple parties.

To add contact to a party or to update existing contact point assignments using file-based import, your source file must
contain information about the account, contact, or household party to which the contact point belongs. You map your source
file data to the account, contact, or household profile target object, the relationship record that captures the interconnection
between the contact and the account.
If you're creating the party and the contact point assignment in the same import activity, then group the party and contact
point data together in your source file. The import process can import the party, and then identify the party record so that it
can import the associated contact point.
212
To add a contact point to an existing party, or to update an existing contact point record, your source file must include
values that enable the import process to identify the existing records. These values will be source system and source system
reference value combination, an Oracle Sales Cloud internal ID, or public unique identifiers, such as business keys or external
IDs.

point in the same import batch, adding contact points to an existing party, or updating a contact point record.
or update a contact point data record. You can optionally include attributes that are available for import in your import file but
Batch
PartyId The Oracle Sales The attribute is

Cloud internal ID for Identify the party ID neither required Conditionally Conditionally
value by exporting required. required.
213
Batch
the party (account, the Party object nor conditionally
contact, household, using Setup and required. Provide reference Provide reference
partner, or legal Maintenance, information to information to
entity) to which Manage Bulk Data identify the existing identify the existing
the contact point Export, Schedule party. The reference party. The reference
belongs. Export Processes information can be: information can be:
task.
ID). ID).
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile), profile),
which is which is

belongs. importing the party previously imported information can be: information can be:
as this contact external system, • PartyId • PartyId
point. then you can (Oracle Sales (Oracle Sales
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
214
Batch
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile), profile),
which is which is
number or text reference value required. Conditionally Conditionally
partner, or legal identify the source import updates to party. The reference party. The reference
entity) to which system reference previously imported information can be: information can be:
the contact point that you will use records from the
belongs. when importing external system, • PartyId • PartyId
contact point. system code and ID). ID).
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
• Party • Party
Number Number
(public (public
unique unique
for an for an
profile), profile),
which is which is
ObjectKey The unique ID for The attribute is The attribute is

the existing contact Identify the contact neither required neither required Conditionally
point record in the point ID for an required.
215
Batch
Oracle Sales Cloud existing contact nor conditionally nor conditionally
destination table. point by exporting required. required. Provide reference
the contact point information to
Manage Bulk Data
ID).
• CpOrigSystem
and
(source
system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• Party
Number
(public
unique
identifier
for an
organization
profile),
which is
CONTACT_NUMBER
for contact.
ContactPointType Type of the contact Required Required Required

point like phone, Identify valid lookup
email and so on. codes for the
COMMUNICATION_TYPE
lookup using
the Setup and
Maintenance,
Manage Contact
Point Lookups
task.

provide the source provide the source
216
Batch
this contact point system code and system code and Cloud internal
contact preference. the unique reference the unique reference ID).
value for the source value for the source • CpOrigSystem
system's record in system's record in and
your source file. your source file. CpOrigSystemReference
(source
system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• Party
Number
(public
unique
identifier
for an
organization
profile),
which is
CONTACT_NUMBER
for contact.

• CpOrigSystem
and
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.
• Party
Number
(public
unique
217
Batch
identifier
for an
organization
profile),
which is
CONTACT_NUMBER
for contact.
OwnerEmailAddress The e-mail address Optional

of the resource that Identify the party ID Conditionally Conditionally
owns and manages and party number required. required.
the sales account to of the owner by
which the contact is exporting the
associated. by including user importing
the Setup and
Manage Bulk Data following reference designated as the
Export Processes
To specify a
• OwnerPartyID
different owner,
include one of the
following reference
information:
• OwnerPartyID
OwnerPartyId The unique identifier Optional

Manage Bulk Data
Export Processes
To specify a
• OwnerPartyID
different owner,
include one of the
following reference
information:
• OwnerPartyID
OwnerPartyNumber The party number Optional

designated as the
Manage Bulk Data
Export, Schedule owner.
218
Batch
Export Processes following reference
task. information: To specify a
different owner,
include one of the
following reference
• OwnerPartyID information:
• OwnerPartyID
order:

The following figure depicts a sample attribute mapping to import a contact point for an existing party. In this scenario, the
OrigSystem and OrigSystemReference values identify the party.

219
Additional Tips
Related Topics
• Importing Contact Point Preferences Using File-Based Import: Quick Start
Importing Contact Point Preferences Using File-Based Import: Quick

Start
This topic describes how to get you started with importing contact point preferences. It includes the following information:
• An overview of contact point preferences
• Additional Tips
The following table lists the file-based import objects and target objects that you can use to import contact point directly
Preferences
Contact Person EmailContactPreference,

220
Preferences

preference.

Account Organization PrimaryPhoneContactPreference,

FaxContactPreference,
AddressContactPreference


Household Organization EmailContactPreference,


InstantMessenger and Url have no contact
point preference.

Legal Entity Organization FaxContactPreference,



Lead Organization (lead organization) No contact point preferences

Lead Person (lead individual) No contact point preferences

Lead Person (contact at lead organization) No contact point preferences

Partner Organization FaxContactPreference,



Partner Contact Person (contact for a partner) EmailContactPreference,


preference.

Campaign Response Organization (respondent organization) No contact point preferences

Campaign Response Person (individual respondent) No contact point preferences

Campaign Response Person (contact at respondent organization) No contact point preferences

The following table lists the file-based import objects and target objects that you can use to import contact point preferences
directly associated with a contact relationship.
221
Preferences
Contact Person (a contact for another root object ContactEmailContactPreference,

such as account) ContactFaxContactPreference, and so on.

ConactInstantMessenger has no contact
point preference.

Account Person (a contact for an account) ContactEmailContactPreference,


point preference.

Legal Entity Person (contact for a legal entity) ContactEmailContactPreference,


point preference.

Contact Point Preferences Overview

Every contact has contact points, such as phone numbers, faxes, e-mail IDs, and so on, and each contact point can have
associated contact point preferences. Contact point preferences indicate whether a contact point can be used to contact a
person. For example, Consider Pinnacle Flowers and Gifts, a customer of Vision Enterprises. At Pinnacle Flowers and Gifts,
the designated contact person for the company must not be contacted by phone, and the customer contact for the logistics
service that Vision Enterprises offers does not want to be contacted using faxes. Pinnacle Flowers and Gifts has assigned
phone and fax numbers to most of its contacts and has made these numbers available to its vendors, but the designated
contacts have specific preferences about how they do and do not want to be contacted. Vision Enterprises must store these
preferences to ensure that their employees do not reach out to customer contacts using contact points that the contacts do
not want to be used.

To add contact point preferences to a party or to update existing contact point preference assignments using file-based
import, your source file must contain information about the account, contact, or household party to which the contact point
preference belongs. You map your source file data to the account, contact, or household profile target object, the relationship
record that captures the interconnection between the contact point and the contact point preference target object.
If you're creating the party and contact point preference assignment in the same import activity, then group the party and
contact point preference data together in your source file. The import process can import the party, and then identify the party
record so that it can import the associated contact point preference. To add a contact point preference to an existing party,
or to update an existing contact point preference record, your source file must include values that enable the import process
to identify the existing records.
222

• The purpose of the import. The data requirements are different when you're creating both the party and contact
point preference in the same import batch, adding contact point preferences to an existing party, or updating a
contact preference record.
or update a contact point preference data record. You can optionally include attributes that are available for import in your
import file but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is
listed.

contact, household, using Setup and required.
partner, or legal Maintenance, Provide reference Provide reference
entity) to which Manage Bulk Data information to information to
the contact point Export, Schedule identify the existing identify the existing
preference belongs. Export Processes party. The reference party. The reference

ID). ID).
and and
(source (source
system system
reference reference
values) values)
provided provided
when when
profile. profile.
223

preference belongs. importing the party previously imported information can be: information can be:
as this contact point external system, • PartyId • PartyId
preference then you can (Oracle Sales (Oracle Sales
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
number or text reference value from required. Conditionally Conditionally
representing the your source system required. required.
source system that was used when If the source of
unique ID for the you imported the your data is an Provide reference Provide reference
party (account, party in a prior external system, information to information to
contact, household, batch, or identify and if you intend to identify the existing identify the existing
partner, or legal the source system import updates to party. The reference party. The reference
entity) to which reference that previously imported information can be: information can be:
the contact point you will use when records from the
preference belongs. importing the party external system, • PartyId • PartyId
in the same batch then you can (Oracle Sales (Oracle Sales
as this contact point provide the source Cloud internal Cloud internal
preference. system code and ID). ID).
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
224
ContactType The method of Identify the contact Required Required The attribute is
contact that should type from the Setup neither required
or should not be and Maintenance, nor conditionally
made, such as call Manage Trading required.
or mail. Community
Common Lookups
task.

PreferenceCode The lookup code Identify the Required Required The attribute is
that represents the preference code neither required
contact method from the Setup nor conditionally
preference phrase, and Maintenance, required.
such as Do Use, Manage Trading
Opt In, Do not use. Community
Common Lookups
task.

PreferenceStartDate The date from which The contact Required Required The attribute is
a contact preference preference period neither required
is valid. start date must nor conditionally
be less than or required.
equal to the contact
preference period
end date.

RequestedBy The lookup code Identify lookup Required Required The attribute is
that represents codes for the source neither required
the source of the of the contact nor conditionally
contact preference preference request required.
request, such as from the Setup
internal requirement and Maintenance,
or requested by the Manage Trading
party. Community
Common Lookups
task.

ContactPrefOrigSysRef The source system No prerequisite Conditionally

reference that tasks. required. Conditionally Conditionally
identifies the unique required. required.
ID of the contact If the source of
preference in your your data is an Provide reference Provide reference
legacy or external external system, information to information to
system. and if you intend to identify the existing identify the existing
records from the
and and
system's record in
your source file.
(source (source

225
system system
reference reference
values) values)
provided provided
when when
profile. profile.
ContactPrefOrigSystem A source system No prerequisite Conditionally

code that identifies tasks. required. Conditionally Conditionally
the original source required. required.
system of the If the source of
contact preference. your data is an Provide reference Provide reference
external system, information to information to
and if you intend to identify the existing identify the existing
records from the
and and
system's record in
your source file.
(source (source

system system
reference reference
values) values)
provided provided
when when
profile. profile.
ObjectKey The unique ID of Identify the contact The attribute is The attribute is
the existing contact preference ID of neither required neither required Conditionally
preference record an existing contact nor conditionally nor conditionally required.
in the Oracle Sales preference by required. required.
Cloud destination exporting the Provide reference
table. Contact Preference information to
Manage Bulk Data
ID).
and
(source
system code
and source
system
226
reference
values)
provided
when
importing the
organization
profile.

• CpOrigSystem
and
(source

system code
and source
system
reference
values)
provided
when
importing the
organization
profile.

• CpOrigSystem
and
(source

system code
and source
system
reference
227
values)
provided
when
importing the
organization
profile.
The following figure depicts a sample attribute mapping to import a contact point preference for an existing party. In this
scenario, the OrigSystem and OrigSystemReference values identify the party.

228
Additional Tips
Related Topics
• Importing Contact Points Using File-Based Import: Quick Start
Importing Contact Jobs Using File-Based Import: Quick Start

This topic describes how to get you started with importing contact jobs. It includes the following information:
• Additional tips
A contact job enables you to capture information related to the work that a contact does. The target object contains
attributes that records data such as the name and code of the department where the contact works, the job title of the
contact, and so on.
The following table lists the file-based import objects and target objects that you can use to import contact jobs.
Contact Person ContactJob

Account Person (a contact for a account) ContactJob

Lead Lead Contact ContactJob

229
Legal Entity Person (a contact for a legal entity) ContactJob

Partner Partner Contact Job

Response Response Contact ContactJob


To add contact jobs to a party or to update existing contact job assignments using file-based import, your source file must
contain information about the account, contact, or household party to which the contact job belongs. You map your source
file data to the account, contact, or household profile target object and to the contact job target object.
If you're creating the party and the contact job assignment in the same import activity, then group the party and contact job
import the associated contact job.
To add a contact job to an existing party, or to update an existing contact job record, your source file must include values
that enable the import process to identify the existing records.

The minimum data that is required to import contact job information depends on the following:
job in the same import batch, adding contact jobs to an existing party, or updating a contact job record.
update a contact job record. You can optionally include attributes that are available for import in your import file but that aren't
230
in the Same Batch
PartyId The Oracle Sales Identify the party ID Required Conditionally Conditionally
Cloud internal ID for value by exporting required. required.
the party (account, the Party object
contact, household, using the Setup To identify the To identify the
or legal entity) to and Maintenance, party, provide party, provide
which the address Manage Bulk Data either the internal ID either the internal ID
belongs. Export, Schedule (PartyId) or both the (PartyId) or both the
Export Processes source system code source system code
task. (PartyOrigSystem) (PartyOrigSystem)
reference value reference value
that were provided that were provided
in a prior import of in a prior import of
the party. the party.

PartyOrigSystem The code Identify the source Conditionally Conditionally Conditionally

representing the system code that required. required. required.
source system for was used when you
the party (account, imported the party If the source of To identify the To identify the
contact, household, in a prior batch, or your data is an party, provide party, provide
or legal entity) to identify the source external system, either the internal ID either the internal ID
which the address system code that and if you intend to (PartyId) or both the (PartyId) or both the
belongs. you will use when import updates to source system code source system code
importing the party previously imported (PartyOrigSystem) (PartyOrigSystem)
in the same batch records from the and source system and source system
as this address. external system, reference value reference value
then you can (PartyOrigSystemReference)
provide the source that were provided that were provided
system code and in a prior import of in a prior import of
system's record in
your source file.

The reference Identify the Conditionally Conditionally Conditionally
number or text reference value required. required. required.
representing the from your source
source system system that was If the source of To identify the To identify the
unique ID for the used when you your data is an party, provide party, provide
party (account, imported the party external system, either the internal ID either the internal ID
contact, household, in a prior batch, or and if you intend to (PartyId) or both the (PartyId) or both the
or legal entity) to identify the source import updates to source system code source system code
which the address system reference previously imported (PartyOrigSystem) (PartyOrigSystem)
belongs. that you will use records from the and source system and source system
when importing external system, reference value reference value
the party in the then you can (PartyOrigSystemReference)
same batch as this provide the source that were provided that were provided
address. system code and in a prior import of in a prior import of
system's record in
your source file.

RelationshipId The unique ID identify the Conditionally Conditionally Conditionally

for the existing Relationship ID for required. required. required.
contact's an existing contact's
relationship with relationship by If the source of If the source of To identify the
the organization or exporting the your data is an your data is an existing contact
231
in the Same Batch
person record in the Relationship object external system, external system, job record, provide
destination table. using the Setup and if you intend to and if you intend to either the internal
and Maintenance, import updates to import updates to ID (ObjectKey) or
Manage Bulk Data previously imported previously imported both the source
Export, Schedule records from the records from the system code
Export Processes external system, external system, (RelOrigSystem)
task. then you can then you can and source system

RelOrigSystem The source No prerequisite Conditionally Conditionally Conditionally

system code that tasks. required. required. required.
identifies the original
source system If the source of If the source of To identify the
of the contact's your data is an your data is an existing contact
relationship with external system, external system, job record, provide
the organization or and if you intend to and if you intend to either the internal
person. import updates to import updates to ID (ObjectKey) or

RelOrigSystemReferenceThe ID that identifies No prerequisite Conditionally Conditionally Conditionally

the contact's tasks. required. required. required.
relationship with
the organization If the source of If the source of To identify the
or person in your your data is an your data is an existing contact
legacy or external external system, external system, job record, provide
system. and if you intend to and if you intend to either the internal
import updates to import updates to ID (ObjectKey) or

ContactNumber The contact job's Obtain the contact The attribute is The attribute is Conditionally
unique public number for an neither required neither required required.
identifier value. existing contact nor conditionally nor conditionally
using the Customers required. required. Required if you are
work area. updating a contact
job and are not
232
in the Same Batch
providing the object
key.

ObjectKey The unique ID for identify the contact The attribute is The attribute is Conditionally
the existing contact ID for an existing neither required neither required required.
job record in the contact by exporting nor conditionally nor conditionally
destination table. the Organization required. required. Required if you
Contact object are updating a
using the Setup contact job and are
and Maintenance, not providing the
Manage Bulk Data contact number.
Export, Schedule
Export Processes
task.


Additional Tips
• Importing contact jobs
Importing Country Structures

Importing Country Structures Using File-Based Import: Explained
This topic explains how to prepare and import country structure data from an external data source 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 as the topmost level, followed by the County, then the City,
and finally the Postal Code.
233
You can use the country structure to set up the following:

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

• How does your legacy system or source system represent the geography data compared to how the application
• Do you have to configure the application to capture additional attributes that are critical to the way you do business?

You must understand how your country structure data corresponds with the data in the application so that you can map your
of the data for a country structure.
example, if you're importing the country structure of Australia, the country structure could be the following: 1: Country, 2:
Import Objects for the Country Structure

To facilitate importing country structures, the application incorporates the structure of the country structure into import
objects. The import object for country structures is GeoStructureLevel.

many relationships between the structural components that make up the country structure.
You must understand the attribute details of the import objects so that you can prepare your import data. . You can use
you can define values in the application. For example, if you have values in your data that correlate to a choice list in the
application, then the validation information for that attribute provides the task name in the Setup and Maintenance work area
where you can define your values.
If you need to configure the application object to import your legacy or source data, you must use the Application Composer
available for importing. The corresponding import object is updated with the configurable attributes, which can then be
mapped to your source file data. You can use the same source file to import both configurable 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
234
for each import object. When you're 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.

the Status column for your import activity.
Related Topics
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 objects for the Country Structure import object

Country Structure Target Import Objects

The Country Structure import object contains one target import object. The target import object 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.

235
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.

objects.
For detailed information on importing geographies using file-based import, refer to Document No. 1481758.1, Importing
Master Reference Geography Data, on the Oracle Support site.
The following table lists the reference file for the ImpGeoStructureLevel target import object.
ImpGeoStructureLevel Information that specifies a country's HZ_ IMP_ GEO_STRUCTURE _ LEVELS_

geography structure. Reference

Related Topics
• Importing Country Structures Using File-Based Import: Explained
• Importing Country Structures Using File-Based Import: Quick Start

• Additional tips

236




to countries.





237

Additional Tips
Support.
Related Topics
Importing Customer Hierarchies

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 an account has with other accounts. A customer hierarchy consists of hierarchy members.
A customer hierarchy can be used to process payments from one account and apply them to another account 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
accounts in a hierarchy.
238
Consider the following questions when importing customer hierarchy information:

• Are all members of the customer hierarchy in Oracle Sales Cloud?
• Do you 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 Sales
• Do you have to configure values in Oracle Sales Cloud to map your existing data values to the Customer Hierarchy
import object?
business?
• How do you verify my imported data?
To import a customer hierarchy, you must:

1. Import accounts that 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 accounts into the hierarchy.

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 account object structure of Oracle Sales Cloud. You must understand how Oracle Sales Cloud represents
the structure of the data for a customer hierarchy.
The customer hierarchy import object structure is hierarchical. At the upper 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 and customer hierarchy nodes, such as the hierarchy type, hierarchy code,
hierarchy name, and hierarchy version.

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 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 customer hierarchy.
You must understand the attribute details of the import objects so that you can prepare your import data. Reference files with
detailed attribute information are provided in the File Based Data Import for Oracle Sales Cloud guide that is available on the
Oracle Sales Cloud Help Center (https://docs.oracle.com/cloud/latest/salescs_gs/docs.htm).
Reference files contain attribute descriptions, values that populate attributes by default when you don't provide values, and
validation information for each attribute. The validation information includes the navigation path 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.
If you want to configure the import object to import your legacy or source data, then you must use Application Composer
available for importing.
The corresponding import object is updated with the configurable attributes, which you can then map to your source file data.
You can use the same source file to import both configurable attributes and the standard import object attributes.
239
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 a file-based import. The file-based import process reads the
data 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
When importing customer hierarchy information, you first import the customer hierarchy information and then the customer
hierarchy members for the customer hierarchy. When importing customer hierarchy members, you must provide the parent
reference information that refers to the customer hierarchy of the member.

Oracle Sales Cloud provides 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 Manage Hierarchies task from Setup and
Maintenance to view the customer hierarchy information that you have imported.
Related Topics
• Customer Hierarchy Import Objects: How They Work Together
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 objects for the customer hierarchy import object
Customer Hierarchy 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.
3. Import existing customers as customer hierarchy members into the hierarchy.
240

file. See the File Based Data Import for Oracle Sales Cloud guide . In the File Based Data Imports chapter, see the topic for
your import object of interest, which includes links to reference files for target import objects. A 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 prerequisite setup tasks that are required.
review the Application Composer extensibility features for the customer hierarchy.

objects. The following table lists the reference files that are available for the target import objects.
CustomerHierarchy Customer hierarchy definition and root node HZ_ IMP_ HIERARCHIES_T _Reference
of the customer hierarchy

CustomerHierarchyMember Customer hierarchy members HZ_ IMP_ HIERARCHY_ NODES_ Reference

Related Topics
• Importing Customer Hierarchy Using File-Based Import: Explained
Importing Customer Hierarchies Using File-Based Import: Quick Start

This topic describes a few key concepts and provides guidance to get you started on importing customer hierarchies. It
includes the following information:
• Customer hierarchy overview

241

• Additional tips
The following table lists the file-based import objects and target objects that you can use to import customer hierarchies.
Import Object Target Objects
Customer Hierarchy CustomerHierarchy

Customer Hierarchy Overview

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 can create multiple versions of a customer hierarchy; however, only one hierarchy version can be active on a specific
date. You can create a new hierarchy to represent the structure of a new customer. If the customer has made minor changes
to its organization, you can create a new version rather than edit the existing one.

To update an existing customer hierarchy, your source file must include values that enable the import process to identify the
existing records. These values will be either a source system and source system reference value combination or an Oracle
Fusion record ID.
If the source of your data is a third party or external system, and you intend to import updates to previously imported records
from the same system, you can provide the source system code and the unique reference value for the party record in your
source system. Oracle Fusion stores a cross-reference between the source system information and Oracle's record ID. To
add a sales account profile to an existing party, you provide the source system code and reference values and the import
process uses the value combination to identify the existing party record in Oracle Fusion.

The minimum data that is required to import customer hierarchy information depends on the following:
• The purpose of the import. The data requirements are different when you're creating a customer hierarchy or when
you're updating a customer hierarchy record.
• The data requirements are different when using source system information or record IDs to identify and associate
records.
242
The values that you provide in your source file may require a setup task or manual steps to ensure that the information passes
the import validation. Before you prepare your source file, complete the prerequisite steps to determine the data values, and
then include those values in your source file. The following table lists the minimum attributes required to import customer
hierarchies based on two possible scenarios for your import, any prerequisite setup or manual steps needed to prepare your
data, and the import attributes that you use to map your data to Oracle Fusion. You can optionally include attributes that are
available for import in your import file but that aren't listed in the table.
Batch
Language Indicates the code of View valid language Conditionally required. Conditionally required.
the language into which codes from the Setup
the contents of the and Maintenance, Required when creating Required when creating
translatable columns are Manage ISO Languages a new hierarchy (tree a new hierarchy (tree
translated. task. version). version).

Default is US if not
specified.

SourceLangFlag This check box indicates No setup task required. Conditionally required. Conditionally required.
whether the language
specified by the Required when creating Required when creating
Language attribute is a new hierarchy (tree a new hierarchy (tree
the source language in version). version).
which the contents of this
record are being created
or were originally created.

using the Setup and
Maintenance, Manage

HierarchyCode User-defined identifier for If the import object is Required Required

a tree. Employee resource,
then HiearchyCode must
be 'GLOBAL_ SALES_
MARKETING' else the
value is free text.

HierarchyName The name of the tree. No setup task required. Required Required

HierarchyVersionName The name of the tree No setup task required. Conditionally required. Conditionally required.
version.
Required when creating a Required when creating a
hierarchy (tree version). hierarchy (tree version).

to insert or to delete the when updating a record.
hierarchy (tree version). If If deleting an existing The value DELETE The value DELETE
provided, valid values are record, use the value, is required if you are is required if you are
INSERT, UPDATE, and DELETE. If inserting a deleting an existing deleting an existing
DELETE. record, use the value hierarchy (tree version). hierarchy (tree version).
INSERT.
243
Batch

AsOfDate The date that is used No setup task required. Conditionally required. Conditionally required.
to determine the tree
version to delete when A value is required if A value is required if
ActionCode is provided deleting an existing deleting an existing
as DELETE. Only one hierarchy (tree version). hierarchy (tree version).
version is active on any
given date.


Additional Tips
Related Topics
• Importing Customer Hierarchy Member Using File-Based Import: Quick Start
Importing Customer Hierarchy Member Using File-Based Import:

Quick Start
This topic describes a few key concepts and provides guidance to get you started on importing customer hierarchy
members. It includes the following information:

• Additional tips
244
The following table lists the file-based import object and target object that you can use to import customer hierarchy
members.
Customer Hierarchy Member CustomerHierarchyMember

hierarchy members.

To update an existing customer hierarchy member, your source file must include values that enable the import process to
identify the existing records. These values will be either a source system and source system reference value combination or
an Oracle Fusion record ID. If the source of your data is a third party or external system, and you intend to import updates to
previously imported records from the same system, then you can provide the source system code and the unique reference
value for the party record in your source system. Oracle Fusion stores a cross-reference between the source system
information and Oracle's record ID. To add a sales account profile to an existing party, you provide the source system code
and reference values and the import process uses the value combination to identify the existing party record in Oracle Fusion.

The minimum data that is required to import customer hierarchy member information depends on the following:
customer hierarchy member in the same import batch, adding customer hierarchy member to an existing party, or
updating a customer hierarchy member record.
Attributes that are available for import in your import file but that aren't listed in the table. For each attribute, the prerequisite
setup task before importing that attribute is listed in the following table.
Same Batch Party
to insert or to delete when updating a record.
the hierarchy node (tree If deleting an existing
node). This attribute is record, use the value,
245
Same Batch Party
typically used only to DELETE. If inserting a A value is required if A value is required if
delete a record. record, use the value deleting an existing deleting an existing
INSERT. hierarchy node. hierarchy node.

AsOfDate When ActionCode is No setup task required. Conditionally required. Conditionally required.
provided as DELETE,
AsOfDate determines the A value is required if A value is required if
tree version from which deleting an existing deleting an existing
to delete the hierarchy hierarchy node. hierarchy node.
node. Only one version is
active on any given date.

using the Setup and
Maintenance, Manage

HierarchyCode User-defined identifier for HierarchyCode must Required Required

a tree. exist in the FND_TREE
table, column TREE_
CODE or, if the hierarchy
is being created in the
same batch as this node,
then HierarchyCode
must exist in HZ_ IMP_
HIERARCHIES_ T table
(the interface table for
the new hierarchy),
column TREE_ CODE
(the HierarchyCode
attribute for a hierarchy
import).

PartyOrigSystem The source system Predefine your source Conditionally required. Conditionally required.
code that identifies system code as enabled
the original source for parties, using the If deleting an existing If deleting an existing
system of the party Setup and Maintenance, node, then identify node, then identify
that you are inserting Manage Trading the node by providing the node by providing
as a new node or that Community Source either PartyId or both either PartyId or both
exists as the node to be Systems task. PartyOrigSystem and PartyOrigSystem and
deleted. You provide the PartyOrigSystemReference. PartyOrigSystemReference.
source system reference
and the source system
code (PartyOrigSystem)
import process uses
and source system
internal ID (PartyId) that
uniquely identifies an
existing party record that
246
Same Batch Party
system code values in a
prior batch. The party is
either being inserted as a
new node or is a node to
be deleted in this batch.

PartyOrigSystemReference The ID that identifies the Identify the reference Conditionally required. Conditionally required.
your legacy or external when you imported the a new node, then a new node, then
system. You provide the party in a prior batch, identify the parent node identify the parent node
source system reference or identify the source by providing either by providing either
system reference you will ParentPartyId or both ParentPartyId or both
and the source use when importing the ParPartyOrigSystem and ParPartyOrigSystem and
system code party in the same batch ParPartyOrigSystemReference.
import process uses
and source system
the existing parent
system code values
batch as this node.

PartyId The unique internal ID You can obtain the Conditionally required. Conditionally required.
of the existing party Party ID for an existing
record that is either being party by exporting the If deleting an existing If deleting an existing
inserted as a new node Party object using the node, then identify node, then identify
or is an existing node to Setup and Maintenance, the node by providing the node by providing
be deleted in this batch. Manage Bulk Data either PartyId or both either PartyId or both
Export, Schedule Export PartyOrigSystem and PartyOrigSystem and
Processes task. PartyOrigSystemReference. PartyOrigSystemReference.

ParentPartyId The unique internal ID for You can obtain the Conditionally required. Conditionally required.
the existing party record Parent Party ID for
that is the parent node of an existing party by If you're creating a new If you're creating a new
this node. exporting the Party node or deleting an node or deleting an
247
Same Batch Party
object using the Setup existing node, and the existing node, and the
and Maintenance, node is not the root node node is not the root node
Manage Bulk Data of the hierarchy, then you of the hierarchy, then you
Export, Schedule Export must identify the parent must identify the parent
Processes task. node by providing either node by providing either
ParentPartyId or both ParentPartyId or both

ParentPartyOrigSystem The source system Predefine your source Conditionally required. Conditionally required.
code that identifies the system code as enabled
original source system for parent parties, If you're creating If you're creating
of the party that is the using the Setup and a new node, then a new node, then
parent node of this Maintenance, Manage identify the parent node identify the parent node
node. You provide the Trading Community by providing either by providing either
source system reference Source Systems task. ParentPartyId or both ParentPartyId or both
and the source ParPartyOrigSystemReference.
system code
import process uses
and source system
the existing parent
system code values
batch as this node.

ParentPartyOrigSystemReference
The ID that identifies the Identify the reference Conditionally required. Conditionally required.
your legacy or external when you imported a new node, then a new node, then
system. You provide the the parent party in a identify the parent node identify the parent node
source system reference prior batch, or identify by providing either by providing either
the source system ParentPartyId or both ParentPartyId or both
and the source reference you will use ParPartyOrigSystem and ParPartyOrigSystem and
system code when importing the ParPartyOrigSystemReference.
(ParentPartyOrigSystem) parent party in the same
when the source of your batch.
248
Same Batch Party
import process uses
and source system
the existing parent
system code values
batch as this node.


Additional Tips

Related Topics
• Importing Customer Hierarchies Using File-Based Import: Quick Start
249
Deleting Sales Account Hierarchies Using File-Based Data Import:

Procedure
This procedure describes how to delete the Sales Account Hierarchies using file-based data import.
Deleting a sales account hierarchy involves two steps:
• Deleting a hierarchy version

• Deleting a hierarchy member
Deleting a Hierarchy Version

You can use the following steps to delete a hierarchy version:
1. On the Setup and Maintenance work area, search for the Manage File Import Activities task.
2. On the Manage Import Activities page, click Create.
3. Structure the CSV file according to the information in the following table:
◦ The following table displays the required columns, their values, and comments, if any.
Column Name Value
CustomerHierarchy_ HierarchyType HZ_ CUSTOMER_ HIERARCHY

This field is required for deletion.

CustomerHierarchy_ HierarchyCode FIOrgTree_ BJUN9_2014

CustomerHierarchy_ HierarchyName FIOrgTree_ BJUN9_2014

CustomerHierarchy_ AsOfDate 7/25/2014

Enter current date.

CustomerHierarchy_ ActionCode DELETE

The ActionCode column is used to indicate that a record is deleted during import. Set the
ActionCode column to a value of DELETE for any hierarchy version that you want to delete.

CustsomerHierarchy_ FIOrgTree_ BJUN9_2014

HierarchyVersionName

4. Select CustomerHierarchy object from the drop-down list. Provide a name for the Import Activity in the Name text
box. Select the File Type Text File. Browse to select the CSV file that you created.
5. Select the check box Header row included and click Next to go to the Map Fields page.
6. Map the fields to the corresponding attributes.
7. Click Next and activate the import process on the Review and Activate page.
250
Deleting a Hierarchy Member

You can use the following steps to delete a hierarchy member:
1. Perform the steps 1 and 2 as outlined in the previous section.
2. Structure the CSV file according to the information in the following table.
Column Name Value
CustomerHierarchyMember_ HZ_ CUSTOMER_ HIERARCHY

HierarchyType

CustomerHierarchyMember_ FIOrgTree_ BJUN9_2014

HierarchyCode

CustomerHierarchyMember_ AsOfDate 25/7/2014

CustomerHierarchyMember_ DELETE
ActionCode
The ActionCode column is used to indicate that a record is deleted during import. Set the
ActionCode column to a value of DELETE for any hierarchy members you want to delete.

CustomerHierarchyMember_ CDRM_9153
PartyNumber
Either party number, party orig system or party orig system reference should be provided.

CustomerHierarchyMember_ DNB
PartyOrigSystem

CustomerHierarchyMember_ DNB_ 6_9_2014_A0


3. Select CustomerHierarchy member object from the drop-down list. Provide a name for the Import Activity in the
Name text box. Select the File Type Text File. Browse to select the CSV file that you created.
4. Select the check box Header row included and click Next to go to the Map Fields page.
5. Map the fields to the corresponding attributes.
Constraints for Deletion

The deletion process has the following constraints:
• You cannot delete a root node within a hierarchy.
• On deleting a node, its child nodes would be reassigned to its parent node.
Related Topics
• Deleting Records Using File-Based Data Import: Explained
Importing Geographies
251
Importing Geographies Using File-Based Import: Explained

This topic explains how to prepare and import geography data from an external data source using the File-Based Data Import
feature. A geography is any region with a boundary around it, regardless of its size. It might be a state, a country, a city, a
county, or a ward. You must create or import geographies before you can associate them with company-specific zones and
addresses.
Note: The application ships with third-party master geography data for multiple countries that can be imported.
You can import Oracle-licensed data from GBG | Loqate or Nokia, for those countries where the data is
available, such as the U.S. You can import geography data using the Manage Geographies task. Search for
the country, and select Import Geography Data from the Actions menu. If the licensed data is not available for
a particular country, then the Import Geography Data action is disabled. For more information, see Replacing
Existing Master Geography Data with Revised Oracle-Licensed Geography Data: Procedure. If GBG | Loqate
or Nokia geography data is not available for a country, then use the information in this chapter to import it using
File-Based Data Import.

• How does your legacy system or source system represent the geography data compared to how Oracle applications
represent the same data?

You must understand how your geography data corresponds with the data in the application so that you can map your
of the data for a geography.
example, if you are importing the country structure of Australia, the country structure could be the following: 1: Country, 2:
Import Objects for the Geography

To facilitate importing geographies, the application incorporates the structure of the geography into import objects. The
import object for the geography is ImpGeography.

many relationships between the structural components that make up the geography.
values, and validation information for each import object attribute. The validation information includes the navigation path to
the task where you can define values in the application. For example, if you have values in your data that correlate to a choice
list in the application, then the validation information for that attribute provides the task name in the Setup and Maintenance
You can use the keyword importing geographies to search for related topics in Help.
252
The application doesn't support configurable attributes for geographies. You can import only data for geography object that
already exist by default in the application.
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
for each import object. When you're 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.

Oracle applications provide File-Based Import activity reports, which you can use 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.
Related Topics
Geography Import Objects: How They Work Together

This topic describes the Geography import object. You use the Geography import object to import geography information.

• Target objects for the Geography import object
Geography Target Import Objects

You can use the Geography import object 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 the application, you must understand how
the target objects are related and what attributes are included in each target object.
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.
253

the Application Composer extensibility features for geography.

To access the reference guide files for the geography's target import objects, see the File Based Data Import for Oracle Sales
Cloud guide available on the Oracle Sales Cloud Help Center (https://docs.oracle.com/cloud/latest/salescs_gs/docs.htm).
In the File Based Data Imports chapter, see the topic for your import object of interest, which includes links to reference files
for target import objects. For detailed information on importing geographies using file-based import, refer to Document No.
1481758.1, Importing Master Reference Geography Data, on the Oracle Support site.
The following table lists the reference file for the ImpGeography target import object.
Target Import Object Description Attribute Reference File Names
ImpGeography Contains information that captures a HZ_ IMP_ GEOGRAPHIES_T _Reference

country's geography hierarchy details, such
as geography type, geography code, and so
on.

Related Topics
Importing Geographies Using File-Based Data Import: Worked

Example
This example demonstrates how to import data using the File-Based Data Import tool. In this example, you have a source
file containing geography data that you want to import into the application to make the geography data available for real time
address validation and tax purposes.
The following table summarizes the key decisions that you must make in this scenario.
254
Decisions to Consider In This Example
What type of object are you importing? Geography

What file type are you using for your source data? Text file

Where are you uploading your source data file from? Your desktop

What data type is your source data file? Comma separated

Which fields are you importing into the application? All, except for the RecordTypeCode field

When do you want to process the import? Immediately

Summary of the Tasks

You perform the following steps to create an import activity and activate the import:
1. Determining what information is in the source file.

2. Creating and scheduling the import activity.
3. Monitoring the import results.
Prerequisites for Importing Additional Geography Data After Your Initial Import
1. Ensure that the combination of the Source ID and Parent Source ID values is unique for each row of data within a
single import. However, your source data files don't need to have the same Source ID and Parent Source ID values
as your previously imported geography data. If the geography structure levels and the parents for each geography
value are the same, then the changed IDs will not affect the import.
2. Ensure that all the parents of a child geography are included in your data file so that the child geography can be
added. For example, if you originally imported US, CA, and San Francisco, and now you want to import the city of
San Jose in CA, then your data file must include US, CA, and San Jose.
3. Check that your source data file has the correct values for the geography data that you have already loaded.
For example, if your initial import included the value US for country and CA as state, and in a subsequent import
you have California as a state, then your geography import creates two state records (CA and California) in the
application data, with the US as the country parent.
Determining What Information Is in the Source File

1. The source geography data files must include a unique Source ID value for each row of data and Parent Source ID
value for the parent of that row of data. The Source or Parent Source IDs should not be longer than 18 characters.
2. You can structure your geography source data, as shown in the following table.
Geography Level Name Source ID Parent Source ID
1 (Country) US 1 NA

2 (State) CA 11 1

3 (County) Alameda 111 11

255
Geography Level Name Source ID Parent Source ID
4 (City) Pleasanton 1111 111

4 (City) Dublin 1112 111

Creating and Scheduling the Import Activity

You can create an import activity, enter the import details, and schedule the import. An import activity includes selecting the
source file or file location, mapping the source file to the database, and scheduling the import.
1. In the Setup and Maintenance work area, search for and select the task Manage File Import Activities.
2. In the Manage Import Activities page, click Create.
3. In the Create Import Activity: Map Fields page, map each field from your source file to the target object and attribute,
as shown in the following table.
Field Value
Name Master Reference Geographies

Object Geography

File Type Text File

File Selection Specific file

Upload From Desktop

File Name Choose relevant file from desktop

Data Type Comma separated

Note: Ensure that the file type that you select in the Create Import Activity: Set Up page matches the file
type of the source data file.
4. Click Next.
5. In the Create Import Activity: Map Fields page, map each field from your source file to the Oracle Sales Cloud
database object and attribute, as shown in the following table.
Column Header Example Value Ignore Object Attribute
Primary Geography Primary Geography United States Imp Geography Primary Geography
Name Name Name

Country Code US No Imp Geography Country Code

Record Type Code 0 Yes Imp Geography Record Type Code

256
Column Header Example Value Ignore Object Attribute
Source ID 10265 No Imp Geography Source ID

Parent Source ID 1053 No Imp Geography Parent Source ID

If you don't want to import a column in the text file, then you can select Ignore.
Note: If you can't map the fields from your source file to the relevant target object, then see the import
object spreadsheets.
6. Click Next.
7. In the Create Import Activity: Create Schedule page, select Immediate in the Schedule field so that the import will
start as soon as you activate it.
Instead of immediately importing the data, you can choose a date and time to start the import. You can also specify
whether the import will be repeated and the frequency of the repeated import.
8. Click Next.
Monitoring the Import Results

You can monitor the processing of the import activity and view the completion reports for both successful records and errors.
1. In the Create Import Activity: Review and Activate page, verify your import details in the Import Details, File Details,
Import Options, and Schedule sections. Update the import details if required by navigating to the previous screens
using the Back link.
2. Confirm your import details, and click Activate to submit the import.
After the import activity has finished, the Status field value changes to Completed.
Related Topics
• Importing Geographies: Explained

• Additional tips
257





to countries.





258

Additional Tips
Support.
Related Topics
Importing Geography Hierarchies Using File-Based Import: Quick

Start
This topic describes how to get you started with importing geography hierarchies. It includes the following information:
• An overview of geography hierarchies
• Additional tips
259
The following table lists the file-based import objects and target objects that you can use to import geography hierarchies.
Geography Hierarchies ImpGeography

Geography Hierarchies Overview

Geography hierarchy is a data model that establishes conceptual parent-child relationships between geographies. A
geography, such as Tokyo or Peru, describes a boundary on the surface of the earth. The application can extrapolate
information based on this network of hierarchical geographical relationships. For example, in the Master geography hierarchy,
the state of California is defined as the parent of San Mateo county, which is the parent of Redwood City, which is the parent
of the postal code 94065. If you enter just 94065, the application can determine that the postal code is in California, or that
the corresponding city is Redwood City.

Use the source ID and parent source ID of a geography to identify the geography's parent-child relationship with records
within the source file data. The ID can also be used to identify relationships with subsequent interface table data.
For example, when importing a country and its province, you may provide the following values:
• Data for a country: SOURCE_ ID = 1; PARENT_ID = (NULL). The PARENT_ID is null because the country is the
upper level of the geography hierarchy and has no parent.
• Data for a province: SOURCE_ ID = 2; PARENT_ID = 1 (the source ID of the country)

The minimum data that is required to import address information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the party and the address
in the same import batch, adding addresses to an existing party, or updating an address record.
or update a geography hierarchy data. You can optionally include attributes that are available for import in your import file
but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed in the
following table.
Attribute Description Prerequisite Setup Task Creating Geography Updating Geography

Hierarchies Hierarchy Records
CountryCode The unique code of the Identify country codes Required Required
country to which the using the Setup and
geography belongs. Maintenance, Manage
Geographies task.

260

LevelNumber The level number of No prerequisite tasks. Required if you're not Required if you're not
the geography in the specifying the geography specifying the geography
hierarchy of geography type. type.
types for a country where
level 1 is the country.

GeographyType The geography type, Identify geography Required if you're not Required if you're not
such as CITY, COUNTY, types by exporting specifying the level specifying the level
and PROVINCE. the Geography Type number. number.
object using the Setup
and Maintenance,
Manage Bulk Data
Export, Schedule Export
Processes task or
using the Setup and
Maintenance, Manage
Geographies task.

ParentSourceId The parent source ID of No prerequisite tasks. Required Required

the geography, along
with the source ID, is
used to identify the
geography's parent/
child relationship with
records within the
source file data. The
ID can also be used to
identify relationships with
subsequent interface
table data.

SourceId The source ID for the No prerequisite tasks. Required Required

geography, along with
the parent source ID,
is used to identify the
geography's parent/
child relationship within
the source file data and
subsequent interface
table data.

PrimaryGeographyName The name of the primary No prerequisite tasks. Required Required

geography.

RecordTypeCode No prerequisite tasks. Required Required

The record type code
that represents the intent
of the import data.
The values are:
• 0: Indicates a
geography already
exists in the base
table.
261

• 1: Indicates the
intent to create a
new geography.
• 2: Indicates the
intent to add
an alternate
identifying
name or code
to an existing
geography. If you
choose this record
type code, then
you must specify
the additional
fields required.
The following image depicts a sample attribute mapping to import geography hierarchy data.

262
Additional Tips
• Importing geographies
Related Topics
Importing Territory Geographies Using File-Based Data Import:

Explained
This topic describes the tasks that you must perform to import territory geography information. A territory is defined as the
jurisdiction of responsibility of a salesperson over a set of sales accounts. A territory can be based on various factors called
dimensions, such as the geography, product, organization type, industry, business size, account, account type, and sales
channel dimension. The territory geography defines the boundaries of a territory according to the selected dimensions, such
as Europe or Asia. Dimensions are attributes that define jurisdictional boundaries of territories. The geography dimension,
which you can use to define territories by country or postal code, is based on Territory Geographies. Therefore, you must
create or import territory geographies before they can be used in territory definitions.
You must create or import geographies, also referred to as Master Geographies, before you can associate them with custom
zones and addresses. You must also set up master geographies and create territory geography zone types used in the
import, before you can create and import territory geographies.
Importing of the Territory geographies is an incremental import, which either creates a new territory geography hierarchy in
the case of the fresh environment or adds branches to the existing territory geographies.

You must understand how your territory geography data corresponds with the data in Oracle Sales Cloud 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 territory geography.
The territory geographies are a combination of user-defined zones and master geography data (also known as Master). If you
use only master geographies to define your territory geography, then your territory definition is based only on the elements
seen in the master geography. For example, in the following figure, the territory North America includes the geography US
263
and Canada which are master geographies. This is because the territory geography is based only on country, state, and ZIP
code.
Territory Geographies Territory Geography

US Master North America US, Canada
PA Master US US
01243 Master East US <List of states or zip codes>
01244 Master Mid Atlantic <List of states or zip codes>
... Master PA <List of states or zip codes>
NY Master
... Master
Canada Master
If you use both zones and master geographies to define your territory geography dimension, then you have more flexibility.
You can create Masters under zones (for example, US is under North America), and zones can be placed under Masters (for
example, East Zone is under US) as shown in the following figure.
Territory Geographies Territory Geography

North America Zone North America North America
US Master US US
East Zone Zone East US East
Mid Atlantic Zone Mid Atlantic Mid Atlantic
PA Master PA PA
01243 Master
01244 Master
... Master
Western NY Master
Canada Master
Import Objects for the Territory Geography

To facilitate the import of territory geographies, Oracle Sales Cloud incorporates the structure of the territory geography into
import objects. The import object for the territory geography is ImpGeoTerritory.
264

one-to-many relationships between the structural components that make up the territory geography.
reference guide files that contain attribute descriptions, and validation information for each attribute. The validation information
includes the navigation path 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 require to complete this task, see the topic listed in the following
table.
ImpGeoTerritory Territory Geography Import Objects: How They Work Together

Note: You can use the keyword importing territory geographies to search for related topics in Help.
Oracle Sales Cloud does not support configurable attributes for territory geographies. You can import data only for attributes
provided by Oracle Sales Cloud.
Importing Territory Geographies Using File-Based Data Import

For the territory geography business object, you must use the File-Based Data Import feature. You prepare source data file
in a form of CSV (comma-separated values). The file-based import process reads the data in your source file, populates the
interface tables according to your mapping, and imports the data into the application destination tables. For more information
about the list of territory geography attributes and its descriptions, see the "Importing Territory Geography Hierarchies Using
File-Based Data Import: Quick Start" topic.
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 you're creating a new territory geography, you import the Territory Geography object. You must be
assigned the Master Data Management Administrator job role to access and submit the import activities for geographies.
When importing territory geography information, you must provide the complete territory geography hierarchy.

Oracle Sales Cloud provides File-Based Import activity reports, which you can use to verify imported data. Users with the
Master Data Management Administrator job role can also navigate to the Manage Territory Geographies work area to view the
imported territory geographies.
Territory Geography Import Objects: How They Work Together

This topic describes the territory geography import object. You use the territory geography import object to import territory
geography information.
265

• Target objects for the territory geography import object
Note: Importing of the Territory geographies is an incremental import, which either creates a new territory
geography hierarchy in the case of the fresh environment or adds branches to the existing territory geographies.
Territory Geography Target Import Objects

The territory geography import object is used to import territory geography hierarchy information to create branches of the
territory geography 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.
The target import objects in the territory geography import object contain information about the territory geography hierarchy.
When updating existing territory geographies, you must include the parent reference information of the existing territory
geography that connects it to the upper node of the hierarchy.
Use the ImpGeoTerritory target import object to create and update the territory geography information.
Note: Before you import the territory geography data, you must set up master geographies and create territory
geography zones.

and target object attribute. You can predefine and manage import mappings using the Manage File Import Mappings task,
or you can define the mapping when you define the import activity using the Manage File Import Activities task. Both tasks
are available in the Setup and Maintenance work area.
Importing Territory Geography Hierarchies Using File-Based Data

Import: Quick Start
This topic describes a few key concepts and provides guidance to get you started with importing territory geography
hierarchies. It includes the following information:
• An overview of territory geography hierarchies
266
• Additional tips
Note: Importing of the Territory geographies is an incremental import, which either creates a new territory
geography hierarchy in the case of the fresh environment or adds branches to the existing territory
geographies. .
The following table lists the file-based import objects and target objects that you can use to import territory geography
hierarchies.
Territory Geography Hierarchies ImpGeoTerritory

Territory Geography Hierarchies Overview

A territory geography hierarchy is a data model that establishes conceptual parent-child relationships between territory
geographies. The territory geographies form the basis for the geography dimension in territory management. It defines the
boundaries of the territories when used in the territory definitions. A territory geography is a combination of master geography
data and user-defined zones and master geography data.

Use the source ID and parent source ID of a territory geography to identify the territory geography's parent-child relationship
with records within the source file data. The ID can also be used to identify relationships with subsequent interface table data.
For example, when importing a country, which is the upper node, and its province, you may provide the following values:
• Data for a country: SOURCE_ ID = 1; PARENT_ID = (NULL). The PARENT_ID is null because the country is the
upper level of the territory geography hierarchy and has no parent.
• Data for a province: SOURCE_ ID = 2; PARENT_ID = 1 (the source ID of the country)
Minimum Data Required and the Prerequisite Set up Tasks

The minimum data that is required to import territory geography information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the master geography and
zone in the same import batch.
update a territory geography hierarchy data. You can optionally include attributes that are available for import in your import
file but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed.
Attribute Description Prerequisite Set up Task Creating Territory Geography

Hierarchy Branches
TerritoryGeographyName The name of a territory No prerequisite tasks. Required

geography.
267

Hierarchy Branches

SourceId The source ID for the territory No prerequisite tasks. Required

geography, along with the parent
source ID, is used to identify the
territory geography's parent/
child relationship within the
source file data and subsequent
interface table data.

ParentSourceId The parent source ID of the No prerequisite tasks. Required except when the
territory geography, along with territory geography is an upper
the source ID, is used to identify node.
the territory geography's parent/
child relationship with records
within the source file data. The
ID can also be used to identify
relationships with subsequent
interface table data.

LanguageCode The unique language code of No prerequisite tasks. Required

the country to which the territory
geography belongs. The default
value is US.

TerritoryGeographyType The territory geography type that Required

could either be a combination For master geographies, identify
of master geography data the geography type, such as
and user-defined zones. The country, state, province, using
master geography data includes the Setup and Maintenance,
values such as city, county, and Manage Geographies task.
province.
For zones, identify the existing
zone types in the application
using the Add Zone option
in the Manage Territory
Geographies task, from the
Setup and Maintenance work
area.
Note: You can

create a zone of a
specific type in the
Manage Territory
Geographies task
using the Add Zone
option. When you
delete the zone, the
zone type remains in
the application , and
appears in the Zone
Type drop-down list
the next time you
create a new zone.

ZoneCode A unique user-defined code of No prerequisite tasks. Required

the zone to which the territory
268

Hierarchy Branches
geography belongs. It is used
only for zones.

GeoCountryName The name of the country for that No prerequisite tasks. Required
geography. It is used only for
master geographies.

GeoParentName1 Required only for master

Used to specify the complete Identify the full path of the geography.
path of any master geography, master geography from the
starting with the country Setup and Maintenance,
name. For example, if your Manage Geographies task.
TerritoryGeographyName is San
Francisco, then the complete
path of the master geography is:
• GeoParentName1 =
"United States"
• GeoParentName2 = "CA"
• GeoParentName3 = "San
Francisco" (county)
Francisco" (city)
• GeoParentName5 = blank
GeoParentName2 Required for master geography,

Used to specify the complete Identify the full path of the only if the master path is at least
path of any master geography, master geography from the two elements long.
"United States"
Francisco" (county)
Francisco" (city)

path of any master geography, master geography from the three elements long.
"United States"
Francisco" (county)
Francisco" (city)
269

Hierarchy Branches

path of any master geography, master geography from the four elements long.
"United States"
Francisco" (county)
Francisco" (city)

path of any master geography, master geography from the five elements long.
"United States"
Francisco" (county)
Francisco" (city)
IncludeChildGeoType1 Used to include the specific type Required only if

of children of a specific master For master geographies, identify IncludeChildGeoType2 is
geography. the available children type, such specified.
as country, state, province, for
a given country from the Setup
and Maintenance, Manage
Geographies task.

Geographies task.

Geographies task.
270

Hierarchy Branches

Geographies task.
IncludeChildGeoType5 Used to include the specific type Required only if you want to
of children of a specific master For master geographies, identify specify a child node for the
geography. the available children type, such parent.
Geographies task.
StartDate The territory geography start No prerequisite tasks. The attribute is neither required
date. nor conditionally required.

EndDate The territory geography end No prerequisite tasks. The attribute is neither required
date. nor conditionally required.

Additional Tips
• Importing geographies
Importing Households
Related Topics
271
Importing Households Using File-Based Import: Explained

This topic explains how to prepare and import household data from an external data source into Oracle Sales Cloud using the
A household is a party consisting of a collection of persons and organizations. A household, similar to a person or
organization, can enter into a business relationship with other parties and can be assigned to opportunities and leads. A
household can have members of party type person or organization. You can maintain household information in Oracle
Sales Cloud to create leads and opportunities for a household, or capture information about a household to know it better.
However, maintaining this information may not let you assign all sales and marketing activities to a household.
• How does your legacy or source system represent the household information compared to how Oracle Sales Cloud
• Do you have to configure values in Oracle Sales Cloud to map your existing data values to the Household import
object?

You must understand how your household data corresponds with the data in Oracle Sales Cloud so that you can map your
structure of the data for an household.
The Household import object structure is hierarchical. The root of the hierarchy is the group profile, which must exist before
you can import lower-level components, such as classifications, contacts, and relationships. 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 household.
272
The following figure shows the household import object and its child entities.
Group Profile
Additional Instant Additional

Member Classification Relationship Url
Name Messenger Identifier

Address
Purpose
The household profile contains basic information about the household, such as the group name, group type, and the group-
party usage. For each household, you can assign classifications, members, relationships, additional identifier, and additional
names.
captures the contact preference. For example, the Phone Contact Preference entity captures the contact
preference of the household for the phone contact method.

one-to-many relationships between the structural components that make up the household.
Note:
You can use the keyword importing households to search for related topics in Oracle Sales Cloud Help.
273
Importing Households Using File-Based Data Import

For the household business object, you must use the File-Based Data Import feature. You prepare XML or text source
for each import object. When you're creating a new household, you import the household object.
You must be assigned the Customer Relationship Management Application Administrator job role to access and submit the
import activities for household.
When importing household information, you first import the basic household information, followed by the child entities for the
household. 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 name and household type. You then import contacts and contact
information, such as phone, address, contact points, and fax for the household. You must provide the PartyOrigSystem and
PartyOrigSystemReference of the household when importing contacts for the household. PartyOrigSystem is the source
system code that identifies the source of the information being imported.

Alternatively, you can also navigate to the Customer Center work area to view the household information that you have
imported.
Related Topics
Household Import Objects: How They Work Together

You use the Household import object to import households, their basic information, and members of the household. This
topic describes the Household import object and introduces the following:
• Target objects for the Household import object
Household Target Import Objects

The Household import object is split into separate target import objects for organizing the individual attributes for the different
aspects of the household. The target import objects in the Household import object are grouped into information about the
household and information about the member. The group profile is the target import object containing attributes to import
information about the household. You can have multiple members associated with a household. You can assign only an
organization or a person as a member of a household. You cannot assign a household as a member of another household.
When updating an existing household with additional information, you must provide the parent reference information for the
existing household. When importing contacts or contact information for a household, you must provide relationship reference
information in addition to the parent reference. When importing information about a member, you must refer to the specific
274
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 household or to create a household record, you can import household profile
information, addresses, and contact points, such as phone and fax. The following target import objects are for creating and
updating the household information: GroupProfile, Fax, Mobile, Phone, e-mail, InstantMessenger, Relationship, Member,
Address, Classification, AdditionalName, and AdditionalIdentifier.
All contact-related entities, such phone or e-mail, include a child entity that captures the contact preference. For example, the
Phone Contact Preference entity captures the contact preference of the household for the contact method primary phone.
Additionally, the Address import object for a household includes another child entity, AddressPurpose, that captures the
purpose of the current household address.

the Application Composer configuration features for the marketing response.

objects.
GroupProfile Household information. The default HZ_ IMP_ PARTIES_ T_Reference

party usage for a household is SALES_
PROSPECT.

Relationship Relationship between the household and HZ_ IMP_ RELSHIPS_T

the household member. You must enter a
relationship code in the RelationshipCode
column, when creating a relationship.

Member Household member's information. HZ_ IMP_ RELSHIPS_T

275
Classification Household classification. Classification lets HZ_ IMP_ CLASSIFICS_T

you categorize entities such as parties,
projects, tasks, and orders as hierarchies.

AdditionalIdentifier Household's additional identifier information. HZ_ IMP_ ADDTNLPARTYID_ T

AdditionalName Household's alternative name. HZ_ IMP_ ADDTNLPARTYNAMES _T

Url Household's URL. HZ_ IMP_ CONTACTPTS_T_ Reference

InstantMessenger Household's instant messenger or social HZ_ IMP_ CONTACTPTS_T _Reference

networking information.

Fax Household's fax. HZ_ IMP_ CONTACTPTS_T _Reference

FaxContactPreference Indicates the household preference about HZ_ IMP_ CONTACTPREFS _Reference

Mobile Household's mobile number. HZ_ IMP_ CONTACTPTS_T_ Reference

MobileContactPreference Indicates the household's preference about HZ_ IMP_ CONTACTPREFS_ Reference

Phone Primary phone number of the household. If HZ_ IMP_ CONTACTPTS_T_ Reference
the household has multiple phone numbers,

PrimaryPhoneContactPreference Indicates the household's preference about HZ_ IMP_ CONTACTPREFS_ Reference

Email Household's e-mail. HZ_ IMP_ CONTACTPTS_T_ Reference

EmailContactPreference Indicates the household's preference about HZ_ IMP_ CONTACTPREFS _Reference
being contacted through e-mail.

Address Household's address. If the household has HZ_ IMP_ LOCATIONS_T HZ_ IMP_
multiple addresses, one of the addresses is PARTYSITES_T

AddressContactPreference Indicates the household's preference about HZ_ IMP_ CONTACTPREFS _Reference

Sample attributes: ContactType,
PreferenceCode, PreferenceEndDate,
PreferenceStartDate, and ReasonCode.

Reference attributes: CpOrigSystem,
CpOrigSystemReference.

276
AddressPurpose Indicates the purpose of a household's HZ_ IMP_ PARTYSITEUSES_ T

address.

Sample attributes: SiteUseType, EndDate,
and StartDate.

Reference attributes: SiteOrigSystem and
SiteOrigSystemReference.

Related Topics
Importing Group Profiles Using File-Based Import: Quick Start

This topic describes how to get you started with importing groups.
• Additional tips
Groups allow you to create a collection of contacts and accounts. A group can enter into a business relationship with other
types of customers. You can assign member types to group members to define their relationship with the group. You use the
Group import object to import groups.

To add groups or to update existing group profiles using file-based import, your source file must contain information about
the groups.
To update an existing group profile, your source file must include the values that enable the import process to identify the
277

The minimum data that is required to import group profile information depends on the following:
• The purpose of the import. The data requirements are different when you're creating the group profile or updating an
existing group profile record.
or update a group profile record. You can optionally include attributes that are available for import in your import file but that
Attribute Description Prerequisite Setup Task Creating Group Profile Updating Group Profile

the external source Predefine your source Conditionally required Conditionally required
system. system code as
enabled for Trading
Community members, Provide reference Provide reference
using the Setup and information to identify information to identify
Maintenance, Manage the existing party. The the existing party. The
Trading Community reference information can reference information can
Source Systems task. be: be:

and and
278
profile. profile.
profile). profile).
name. name.

or text representing the value from your source Conditionally required Conditionally required
for the group. Provide reference Provide reference
information to identify information to identify
the existing party. The the existing party. The
reference information can reference information can
be: be:

and and
profile. profile.
profile). profile).
name. name.
GroupName The name of the group. No prerequisite tasks. Required The attribute is neither
required or conditionally
required.

ObjectKey or PartyID The Oracle Sales Cloud The attribute is neither

record ID for the group. Identify the PartyId for required nor conditionally Conditionally required
an existing group profile required.
by exporting the Group
object using the Setup Provide reference
and Maintenance, information to identify
Manage Bulk Data the existing party. The
Export, Schedule reference information can
Export Processes task. be:
• PartyId (Oracle
Sales Cloud
record ID).
279
• PartyOrigSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
• Party Number
(public unique
identifier for an
organization
profile).
• A business
key such as
organization
name.
GroupType The type of the group. Identify valid lookup Required The attribute is neither
codes for the HZ_ required nor conditionally
PARTY_ GROUP_ required.
TYPES lookup using the
Manage Standard
Lookups task.

Type The party type. The type No prerequisite tasks The attribute is neither The attribute is neither
is defaulted to Group for required nor conditionally required nor conditionally
new group profiles. required. required.

The following figure shows a sample attribute mapping to import a new group profile. In this scenario, origin system and origin
system reference information identify the group profile.
The following figure shows a sample attribute mapping to update an existing group profile. In this scenario, origin system
reference information identifies the group profile and updates its group type.
280

Additional Tips
Related Topics
Importing Source System References

Importing Source System References Using File-Based Import:
Explained
This topic explains how to prepare and import source system references from an external data source into Oracle Sales
Cloud, using the File-Based Data Import feature. Source systems are external sources of data that are used to import data
into Oracle Sales Cloud. Source system references identify the source of the data and specify the references to existing
source systems and base tables of Oracle Sales Cloud. Oracle Sales Cloud uses source system references to create
281
references between source system IDs and the Oracle Sales Cloud IDs. For example, if you're importing account records
from a legacy system, then you can import the source system reference to the legacy system. During an import, you can
specify the details of the legacy system and also specify the base table in Oracle Sales Cloud.
You can import the first set of Origin System and Origin System Reference for an object, while importing the object.
Additionally, you can import other sets of Origin System and Origin System Reference using the Source System Reference
import object. You must consider the following questions before importing source system references:
• How does your legacy or source system represent source system information compared with how Oracle Sales
• Do you have to configure values in Oracle Sales Cloud to map them to your existing data values?

You must understand how your source system data corresponds to the data in Oracle Sales Cloud so that you can map your
legacy data to the data that Oracle Sales Cloud requires.
In Oracle Sales Cloud, you must import separate source system references for each source system. Each of these source
system references must contain the owner table name, origin system, and origin system reference information. Additionally,
while importing records into Oracle Sales Cloud, you must specify the existing owner table, origin system, and origin system
reference.
Importing Source System References Using File-Based Data Import

For the Source System Reference business object, you must use the File-Based Data Import feature to import data into
Oracle Sales Cloud. You prepare XML or text source data files in a form that is suitable for a file-based import. The file-based
import process reads the data in your source file, populates the interface tables according to your mapping, and imports the
data into the application destination tables.
for each import object. When you're creating a classification, you use the Source System Reference import object. An import
activity defines the instructions for processing the import data, including the source file, the import mapping from the source
file to the object and attribute, and the import schedule.

the Status column for your import activity. Alternatively, you can also navigate to the Manage Trading Community Source
Systems work area to view the source system information that you have imported.
Related Topics
• Source Systems: Explained
• Managing Source System References: Explained
282
Using Customer Data Management Importing Accounts and Contacts Using Simplified View
Import Objects
5 Importing Accounts and Contacts Using

Simplified View Import Objects
Importing Data Using Simplified View Import Objects:

Overview
File-based data import using the simplified view import objects removes the step of complex manual mapping by
automatically mapping the source import file data to the target import objects and attributes.
You can import a wide range of data using file-based data import to create, update, or delete application records. Simplified
view import objects are currently available for Accounts and Contacts.
The simplified view import objects let you import your account and contact data into Oracle Applications Cloud using files
in .zip file. You can use these objects to import all object-related data in the form of a .zip file. The .zip file includes data about
the business object and its child objects. If you use automatic import mapping, then the application automatically maps the
source file columns to the target objects and target attributes for the object being imported. You can avoid manually mapping
the attributes.
Importing Contacts Using the Contact - Simplified View

Import Object: Procedure
You can import contact data into Oracle Applications Cloud using the Contact-Simplified View import object. You can use the
object to create, update, or delete contact records.
The Contact-Simplified View object is hierarchical. The root of the hierarchy is the Contact-Simplified View object that includes
basic information about the contact. It contains the following child objects:
• Sales Cloud Address: Includes detailed location information for a contact. If the profile option code
ZCA_ACCOUNT_ADDRESS_REQUIRED_ENABLED is set as Yes at site level, then you must provide address
information.
• Sales Cloud Classification: Includes classification information that is used to categorize a contact.
• Sales Cloud Relationship: Includes the relationship information of a contact with other entities, or parties.
• Sales Cloud Team Member: Includes the team member information of a contact.
• Sales Cloud Attachment: Includes the attachment information of a contact.
• Additional Name: Includes the additional names of a contact.
• Raw Phone Number: Includes the phone number information such as country code, area code, and so on.
To import contacts using the Contact-Simplified View import object, you must:
1. Create CSV files with the import data

2. Create an import activity
283
Import Objects
Create CSV files with the import data

Oracle Applications Cloud lets you import your contact data in CSV format. You can include contact and its child objects'
information in CSV files, and import them as a ZIP file. You must include a CSV file each for contact and its child objects.
The columns in the CSV files indicate the attributes you can import for each object. To import records, your source file must
include the attributes that enable the import process to identify these records. The File Import process uses these column
names to automatically map your source data to the attributes in Oracle Applications Cloud.
You must understand the following before populating the templates:

• Identifiers: Identifiers of a record let you reference the record when you want to update the record. Oracle
Applications Cloud generates an internal identifier for each new record. However, Oracle recommends that you
provide the origin system and origin system reference (OS/OSR) information when you are creating a record. The
OS/OSR information is used to update a record, as well as or to associate another record with it. For example, you
can use the OS/OSR information of a contact record to update the contact information, or to create a new address
for the contact. If you are updating a child resource, then you must provide the identifier information of the child and
its parent. For example, to update an address of a contact you must provide the identifier information of the contact
and the address. You can also use a record's internal ID to refer to a record. A record's internal ID, or object key, is
typically its row ID in the Oracle Applications Cloud database. The internal ID is a system-generated unique identifier
with an attribute name, such as PartyId, RelationshipId, or PartySiteId. However, to determine the internal ID you
must export the object from the Oracle Applications Cloud Database.
• Prerequisite Setup Tasks: Some attributes are dependent on other attributes or list of values for their values.
Similarly, some attributes require that certain options in the application are set before you can populate them. For
example, an origin system of a contact that you are importing should be enabled for parties in the Manage Trading
Community Source Systems task.
• Parent Records: When importing a child record, ensure that its parent record exists in the database. For example,
when importing the address of a contact, ensure that its parent contact exists in the database. You can import new
parent and child records in the import activity. You must ensure that the new child record in the import file should
refer to the parent using its identifier. For example, you can import a new contact in the contact import CSV file and
a new address in the address import CSV file. In this case, the address import file should include a reference to the
parent record in the contact import file.
You must also be aware of the following to be able to successfully populate the import templates:
• Required attributes while importing new records
• Required attributes while updating records
• Prerequisite setup tasks for attributes, if any.
The following table lists the required attributes for importing the Contact object.
Required Attributes Description Prerequisite Setup Task Create Contact Update Contact
ObjectKey The Oracle Applications Identify the ObjectKey Not required.

Cloud record ID for the value by exporting the Conditionally required.
party (account, contact, Party object using the
to which the person Manage Bulk Data information to identify
profile belongs. Export, Schedule Export the existing party. The
be:
• ObjectKey (Oracle
Sales Cloud
record ID).
284
Import Objects
• SourceSystem
and
(source system
code and source
system reference
values) provided
when importing
the organization
profile.
• PartyNumber
(public unique
identifier for an
organization
profile).
• A business key
such as person
name.
SourceSystem The code representing Identify the source

the external source system or configure Conditionally required. Conditionally required.
system for the party source systems either
(account, contact, by using the Manage Provide reference Provide reference
household, or legal entity) Trading Community information to create information to identify
to which the person Source System task, or contact. The reference the existing party. The
profile belongs. by importing the source information can be: reference information can
system information into be:
Oracle Sales Cloud • SourceSystem
using the Source System and • SourceSystem
Reference import object. SourceSystemReference. and
SourceSystemReference
• Party Number
provided when
importing the
contact.
• Party Number
• ObjectKey
SourceSystemReference The reference number Identify the source

or text representing the system or configure Conditionally required. Conditionally required.
source system unique ID source systems either
for the party (account, by using the Manage Provide reference Provide reference
contact, household, or Trading Community information to create information to identify
legal entity) to which the Source System task, or contact. The reference the existing party. The
person profile belongs. by importing the source information can be: reference information can
system information into be:
Oracle Sales Cloud • SourceSystem
using the Source System and • SourceSystem
Reference import object. SourceSystemReference. and
• Party Number
provided when
importing the
contact.
• Party Number
• ObjectKey
OwnerEmailAddress The e-mail address of Identify the party ID

the resource that owns and party number of Conditionally required. Conditionally required.
and manages the sales the owner by exporting
account to which the the Party object using By default, the user
contact is associated. Setup and Maintenance, importing the contact is
Manage Bulk Data designated as the owner.
285
Import Objects
Processes task. Specify an owner, by To specify a different
including one of following owner, include one of
reference information: the following reference
information:
• OwnerPartyId • OwnerEmailAddress
• OwnerPartyNumber • OwnerPartyId
OwnerPartyId The unique identifier of a Identify the party ID

valid employee resource and party number of Conditionally required. Conditionally required.
who owns and manages the owner by exporting
the sales account to the Party object using Specify an owner, by By default, the user
which the contact is Setup and Maintenance, including one of following importing the contact is
associated. Manage Bulk Data reference information: designated as the owner.
Processes task. • OwnerEmailAddress
To specify a different
• OwnerPartyId owner, include one of
• OwnerPartyNumber the following reference
information:
• OwnerPartyId
OwnerPartyNumber The party number of a Identify the party ID

valid employee resource and party number of Conditionally required. Conditionally required.
who owns and manages the account owner by
the sales account to exporting the Party Specify an owner, by By default, the user
which the contact is object using Setup including one of following importing the contact is
associated. and Maintenance, reference information: designated as the owner.
Manage Bulk Data
Export, Schedule Export • OwnerEmailAddress
Processes task. To specify a different
• OwnerPartyId
owner, include one of
• OwnerPartyNumber the following reference
information:
• OwnerPartyId
FirstName The first name of a party. No prerequisite tasks Required. Not required.

LastName The last name of a party. No prerequisite tasks Required. Not required.

The following table lists the attributes required to import Address object.
Attribute Description Prerequisite Setup Task Create Address Update Address
PartyId The Oracle Sales Cloud Identify the party ID

internal ID for the contact and party number value Conditionally required. Conditionally required.
to which the address by exporting the Party
belongs. object using the Setup
and Maintenance,
Manage Bulk Data
286
Import Objects
Processes task. Provide reference Provide reference
information to identify the information to identify the
contact: contact:
• PartyId. • PartyId.
• PartySourceSystem • PartySourceSystem
and and
PartySourceSystemReferenceValue
PartySourceSystemReferenceVal
provided in the provided in the
SalesCloudContact SalesCloudContact
CSV file. CSV file.
• Party Number. • Party Number.
PartyNumber The public unique Identify the party ID

identifier for the contact and party number value Conditionally required. Conditionally required.
belongs. object using the Setup Provide reference Provide reference
and Maintenance, information to identify the information to identify the
Manage Bulk Data contact: contact:
Processes task. • PartyId. • PartyId.

and and
CSV file. CSV file.
PartySourceSystem The code representing Identify the source

the source system for the system or configure Conditionally required. Conditionally required.
contact. source systems either
by using the Manage Provide reference Provide reference
Trading Community information to identify the information to identify the
Source System task, or contact: contact:
by importing the source
system information into • PartyId. • PartyId.
Oracle Sales Cloud
using the Source System
and and
Reference import object.

CSV file. CSV file.
The reference number Identify the source
for the contact. by using the Manage Provide reference Provide reference
Source System task, or contact: contact:
Oracle Sales Cloud
and and

CSV file. CSV file.
287
Import Objects
Country The country code Identify valid country Required. Required.

component of the codes using the Setup
address. and Maintenance,
Manage Territories task.

LocationId The unique ID for the Identify the Not required.

existing location record LOCATION_ID for an Conditionally required.
in the Oracle Sales Cloud existing location by
destination table. exporting the Location Provide any of the
object using the Setup following reference
and Maintenance, information to identify the
Manage Bulk Data address:
Processes task. • LocationId.

• SiteNumber.
• AddressSourceSystem
and
AddressSourceSystemReference
AddressSourceSystem The code representing Identify the source

address. source systems either
by using the Manage Provide the source Provide any of the
Trading Community system and source following reference
Source System task, or system reference values information to identify the
by importing the source if you intend to import address:
system information into updates to previously
Oracle Sales Cloud imported records from • LocationId.
using the Source System the same system. • SiteNumber.
• SiteNumber. and
• AddressSourceSystem AddressSourceSystemReference
and
AddressSourceSystemReference.
for the address. by using the Manage Provide the source Provide any of the
Oracle Sales Cloud imported records from • LocationId.
using the Source System the same system. • SiteNumber.
• SiteNumber. and
• AddressSourceSystem AddressSourceSystemReference
and
Site Number The public unique Identify the address Not required.
identifier for the address. number value by Conditionally required.
exporting the Party
object using the Setup Provide any of the
and Maintenance, following reference
Manage Bulk Data
288
Import Objects
Export, Schedule Export information to identify the
Processes task. address:

• SiteNumber.
and
AddressType The type of the address. A list of valid values is Required. Not required.
You can define multiple defined in the lookup
address types for an PARTY_ SITE_ USE_
address. CODE. Review and
update the codes
using the Setup and
Maintenance work
area, Manage Standard
Lookups task.

The following table lists the attributes required for importing the Classification object for Contact.
Attribute Description Prerequisite Setup Task Create Classification Update Classification

internal ID for the contact and party number value Required. Required.
to which the classification by exporting the Party

and and
CSV file. CSV file.

identifier for the contact and party number value Required. Required.

and and
CSV file. CSV file.

the source system for the system or configure Required. Required.
by using the Manage
289
Import Objects
Trading Community
Source System task Provide reference Provide reference
contact: contact:
and and
CSV file. CSV file.
or text representing the system or configure Required. Required.
Source System task contact: contact:

and and
CSV file. CSV file.
SourceSystem SourceSystem: The Identify the source Required.

code representing the system or configure Conditionally required.
source system for the source systems either Provide the source
classification. by using the Manage system and source Provide the reference
Trading Community system reference values. information to identify the
Source System task, or classification.
system information into • ObjectKey.
Oracle Sales Cloud
• SourceSystem
and
SourceSystemReference.

SourceSystemReference SourceSystemReference: Identify the source Required.

The reference number system or configure Conditionally required.
or text representing the source systems either Provide the source
source system unique ID by using the Manage system and source Provide the reference
for the classification. Trading Community system reference values. information to identify the
Source System task, or classification.
system information into • ObjectKey.
Oracle Sales Cloud
• SourceSystem
and
SourceSystemReference.

ClassificationCode The classification The classification and Required. Required.

category within classification code
classification category. should be valid for the
classification category.
Review the classifications
and classification codes,
using the Manage
290
Import Objects
task.

ClassificationCategory The classification code The classification and Required. Required.

within classification classification code
category. should be valid for the
using the Manage
task.

The following table lists the attributes for Relationship object.
Attribute Description Prerequisite Setup Task Create Relationship Update Relationship
RelationshipId The internal ID for the Identify the relationship Not required.
relationship. ID by exporting the Conditionally required.
Party object using the
Setup and Maintenance, Provide reference
Manage Bulk Data information to identify the
Export, Schedule Export relationship:
Processes task.
• RelationshipId.
• RelationshipSourceSystem
and
RelationshipSourceSystemRefere
RelationshipSourceSystem A source system code Identify the source Required.

that identifies the original system or configure Conditionally required.
source system of the source systems either
relationship between the by using the Manage Provide reference
object and the subject Trading Community information to identify the
parties. Source System task relationship:

• RelationshipId.
and
RelationshipSourceSystemReference
A source system Identify the source Required.
reference that identifies system or configure Conditionally required.
the original reference source systems either
ID of the relationship by using the Manage Provide reference
between the object and Trading Community information to identify the
the subject parties in the Source System task relationship:
source system.
• RelationshipId.
and
SubjectPartyId The Oracle Sales Cloud Identify the party ID

by exporting the Party
291
Import Objects
to which the classification object using the Setup
belongs. and Maintenance, Provide reference Provide reference
Manage Bulk Data information to identify the information to identify the
Export, Schedule Export contact: contact:
Processes task.
• SubjectPartyId • SubjectPartyId
• SubjectSourceSystem • SubjectSourceSystem
and and
SubjectSourceSystemReference
SalesAccount SalesAccount
CSV file. CSV file.
• SubjectPartyNumber • SubjectPartyNumber
SubjectPartyNumber The public unique Identify the party ID

Processes task. • SubjectPartyId • SubjectPartyId

and and
CSV file. CSV file.
SubjectSourceSystem The code representing Identify the source


and and
CSV file. CSV file.

and and
CSV file. CSV file.
292
Import Objects
RelationshipType Describes the directional You can view the Required. Not required.
connection between relationship type and
the object and subject relationship type code
relationship. For example, definition from the Setup
Employer of verses and Maintenance,
Employee of. Manage Relationship
Types task.

RelationshipCode Describes the You can view the Required. Not required.
relationship, such as relationship type and
Contact or Membership. relationship type code
definition from the Setup
and Maintenance,
Manage Relationship
Types task.

The following table lists the attributes required to import Team Member object for Contact.
Attribute Description Prerequisite Setup Task Add Team Member Update Team Member


and and
SalesCloudContact SalesAccount
CSV file. CSV file.


and and
CSV file. CSV file.

by using the Manage
293
Import Objects
Trading Community
Source System task Provide reference Provide reference
contact: contact:
and and
CSV file. CSV file.

and and
CSV file. CSV file.
ResourceId The Oracle Sales Cloud Identify the resource ID Not Required.
internal ID for sales team and resource number Conditionally required.
member. value by exporting the
Party object using the Provide reference
Setup and Maintenance, information to identify the
Manage Bulk Data resource team member:
Processes task. • ResourceId

• ResourcePartyNumber
ResourcePartyNumber The public unique Identify the resource ID Required.

identifier for the sales and resource number Conditionally required.
team member. value by exporting the
Party object using the Provide reference
Setup and Maintenance, information to identify the
Manage Bulk Data resource team member:
Processes task. • ResourceId

• ResourcePartyNumber
Create Import Activity

You use the Manage File Import Activities task to create import activities. It consists of a step by step guided process to
assist you with creating an import activity for a given object.
1. Sign in as a setup user and navigate to the Setup and Maintenance work area.
2. Search for and select the Manage File Import Activities task.
3. On the Manage File Import Activities page, click the Create icon.
294
Import Objects
4. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select the
Contact-Simplified View object from the Object list.
5. Select ZIP file from the File Type list, check the Desktop option, and browse and upload the required ZIP file.
6. To add attachments, under Attachments section, browse and upload your file. The attachment must be in ZIP
format.
Note: Ensure that you have the following columns and the required values in the
SalesCloudContact.csv file:
Column Name Expected Value
ATTACHMENT_ FILE_NAME The file name with extension. For example, Sales.jpg.

ATTACHMENT_ FILE_DESC The description of the file.

ATTACHMENT_ FILE_TITLE The title of the file.

ATTACHMENT_ CATEGORY_NAME The category of the file. For example, MISC.

7. Click Next.
8. In the Create Import Activity: Create Schedule page, select an appropriate scheduling option from the Schedule list.
9. Click Next.
10. On the Create Import Activity: Review and Activate page, click Activate to activate the import activity immediately, or
click Save and Close if you want to use the import activity later.
Importing Accounts using the Account - Simplified View

Import Object: Procedure
You can import account data into Oracle Applications Cloud using the Account-Simplified View import object. You can use
the object to create, update, or delete account records.
The Account-Simplified View object is hierarchical. The root of the hierarchy is the Account-Simplified View object that
includes basic information about the account. It contains the following child objects:
• Sales Cloud Address: Includes detailed location information for an account. If the profile option code
ZCA_ACCOUNT_ADDRESS_REQUIRED_ENABLED is set as Yes at site level, then you must provide address
information.
• Sales Cloud Classification: Includes classification information that is used to categorize an account.
• Sales Cloud Relationship: Includes the relationship information of an account with other entities, or parties, such as
contacts, households, and so on.
• Sales Cloud Team Member: Includes the team member information of an account.
• Sales Cloud Attachment: Includes the attachment information of an account.
• Additional Name: Includes the additional names of an account.
• Raw Phone Number: Includes the phone number information such as country code, area code, and so on.
295
Import Objects
To import accounts using the Account-Simplified View import object, you must:
1. Create CSV files with the import data
2. Create an import activity
Create CSV files with the import data

Oracle Applications Cloud lets you import account data in CSV format. You can include account and its child objects'
information in CSV files, and import them as a ZIP file. You must include a CSV file each for account and its child objects.
The columns in the CSV files indicate the attributes you can import for each object. To import records, your source file must
include the attributes that enable the import process to identify these records. The File Import process uses these column
names to automatically map your source data to the attributes in Oracle Applications Cloud.
You must understand the following before populating the templates:

• Identifiers: Identifiers of a record let you reference the record when you want to update the record. Oracle Sales
Cloud generates an internal identifier for each new record. However, Oracle recommends that you provide the origin
system and origin system reference (OS/OSR) information when you are creating a record. The OS/OSR information
is used to update a record, as well as or to associate another record with it. For example, you can use the OS/OSR
information of an account record to update the account information, or to create a new address for the account. If
you are updating a child resource, then you must provide the identifier information of the child and its parent. For
example, to update an address of an account you must provide the identifier information of the account and the
address. You can also use a record's internal ID to refer to a record. A record's internal ID, or object key, is typically
its row ID in the Oracle Applications Cloud database. The internal ID is a system-generated unique identifier with an
attribute name, such as PartyId, RelationshipId, or PartySiteId. However, to determine the internal ID you must export
the object from the Oracle Sales Cloud Database.
• Prerequisite Setup Tasks: Some attributes are dependent on other attributes or list of values for their values.
Similarly, some attributes require that certain options in the application are set before you can populate them. For
example, an origin system of an account that you are importing should be enabled for parties in the Manage Trading
Community Source Systems task.
• Parent Records: When importing a child record, ensure that its parent record exists in the database. For example,
when importing the address of an account, ensure that its parent account exists in the database. You can import
new parent and child records in the import activity. You must ensure that the new child record in the import file
should refer to the parent using its identifier. For example, you can import a new account in the account import CSV
file and a new address in the address import CSV file. In this case, the address import file should include a reference
to the parent record in the account import file.
You must also be aware of the following to successfully populate the import templates:
• Required attributes while importing new records
• Required attributes while updating records
• Prerequisite setup tasks for attributes, if any.
The following table lists the attributes required to import the Account object.
Required Attributes Description Prerequisite Setup Task Create Sales Account Update Sales Account
SourceSystem The code representing Identify the source Conditionally required

the source system for the system or configure Conditionally required
sales account. source systems either Provide the source
by using the Manage system and source Provide reference
Trading Community system reference values information to identify
Source System task, or if you intend to import the existing party. The
by importing the source updates to previously
296
Import Objects
system information into imported records from reference information can
Oracle Sales Cloud the same system. be:
Reference import object. • SourceSystem
and
provided when
importing the
sales account.
• Party Number
SourceSystemReference The reference number Identify the source Conditionally required

or text representing the system or configure Conditionally required
source system unique source systems either Provide the source
ID for the party (account by using the Manage system and source Provide reference
or contact) to which the Trading Community system reference values information to identify
sales profile belongs. Source System task, or if you intend to import the existing party. The
by importing the source updates to previously reference information can
system information into imported records from be:
Oracle Sales Cloud the same system.
using the Source System • SourceSystem
Reference import object. and
provided when
importing the
sales account.
• Party Number
OwnerEmailAddress The e-mail address of Identify the party ID

the resource that owns and party number of Conditionally required Conditionally required
and manages the sales the account owner by
account. exporting the Party Specify an account By default, the user
object using Setup owner, by including one importing the account
and Maintenance, of following reference is designated as the
Manage Bulk Data information: account owner.
Processes task. • Email Address of
the account owner To specify a different
account owner, include
• Party ID of the one of the following
account owner in
reference information:
the OwnerPartyId
column.
• Email Address of
• Party Number the account owner
of the account
• Party ID of the
owner in the
account owner in
OwnerPartyNumber
the OwnerPartyId
column.
column.
• Party Number
of the account
owner in the
OwnerPartyNumber
column.
OwnerPartyId The unique party ID of Identify the party ID

the resource assigned to and party number of Conditionally required Conditionally required
manage the sales profile. the account owner by
exporting the Party Specify an account By default, the user
object using Setup owner, by including one importing the account
and Maintenance, is designated as the
Manage Bulk Data account owner.
297
Import Objects
Export, Schedule Export of following reference
Processes task. information: To specify a different
account owner, include
one of the following
reference information:
the account owner
• Party ID of the • Email Address of
account owner in the account owner
the OwnerPartyId
column. • Party ID of the
account owner in
• Party Number the OwnerPartyId
of the account column.
owner in the
OwnerPartyNumber • Party Number
column. of the account
owner in the
OwnerPartyNumber
column.
OwnerPartyNumber The unique party number Identify the party ID

of the resource assigned and party number of Conditionally required Conditionally required
to manage the sales the account owner by Specify an account By default, the user
profile. exporting the Party owner, by including one importing the account
object using Setup of following reference is designated as the
and Maintenance, information: account owner.
Manage Bulk Data
Export, Schedule Export • Email Address of
the account owner To specify a different
Processes task. account owner, include
• Party ID of the one of the following
account owner in reference information:
the OwnerPartyId
column.
• Party Number the account owner
of the account
• Party ID of the
owner in the
account owner in
OwnerPartyNumber
the OwnerPartyId
column.
column.
• Party Number
of the account
owner in the
OwnerPartyNumber
column.
The following table lists the attributes required for importing the Address object for Accounts.

internal ID for the and party number value Required Required
account to which the by exporting the Party
address belongs. object using the Setup Provide reference Provide reference
Manage Bulk Data account: account:

and and
CSV file. CSV file.
298
Import Objects

identifier for the account and party number value Required Required

and and
CSV file. CSV file.

the source system for the system or configure Required Required
account. source systems either
Source System task, or account: account:
Oracle Sales Cloud
and and

CSV file. CSV file.
or text representing the system or configure Required Required
for the account. by using the Manage Provide reference Provide reference
Source System task, or account: account:
Oracle Sales Cloud
and and

CSV file. CSV file.
Country The country code Identify valid country Required Required

component of the codes using the Setup
address. and Maintenance,
Manage Territories task.

AddressSourceSystem The code representing Identify the source

the source system for the system or configure Conditionally required Conditionally required
address. source systems either
by using the Manage Provide the source Provide any of the
299
Import Objects
Oracle Sales Cloud imported records from • Site Number.
using the Source System the same system. • AddressSourceSystem
Reference import object. and
• Site Number. AddressSourceSystemReference
and
or text representing the system or configure Conditionally required Conditionally required
for the address. by using the Manage Provide the source Provide any of the
Oracle Sales Cloud imported records from • Site Number.
using the Source System the same system. • AddressSourceSystem
and
• Site Number. AddressSourceSystemReference
and
Site Number The public unique Identify the address Not required
identifier for the address. number value by Conditionally required
exporting the Party
object using the Setup Provide any of the
and Maintenance, following reference
Manage Bulk Data information to identify the
Export, Schedule Export address:
Processes task.
• Site Number.
and
AddressType The type of the address. A list of valid values is Required Not Required
You can define multiple defined in the lookup
address types for an PARTY_ SITE_ USE_
address. CODE. Review and
update the codes
using the Setup and
Maintenance work
area, Manage Standard
Lookups task.

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

classification belongs. object using the Setup
and Maintenance,
300
Import Objects
Manage Bulk Data
Export, Schedule Export Provide reference Provide reference
Processes task. information to identify the information to identify the
account: account:
and and
CSV file. CSV file.


and and
CSV file. CSV file.

sales account. source systems either
Source System task account: account:

and and
CSV file. CSV file.

and and
CSV file. CSV file.
301
Import Objects
SourceSystem SourceSystem: The Identify the source Conditionally required Required

code representing the system or configure
source system for the source systems either Provide the source Provide the reference
classification. by using the Manage system and source information to identify the
Trading Community system reference values classification.
Source System task, or if you intend to import
system information into imported records from

SourceSystemReference SourceSystemReference: Identify the source Conditionally required Required

The reference number system or configure
or text representing the source systems either Provide the source Provide the reference
source system unique ID by using the Manage system and source information to identify the
for the classification. Trading Community system reference values classification.
Source System task, or if you intend to import
system information into imported records from

ClassificationCode The classification The classification and Required Required

category within classification code
classification category. should be valid for the
using the Manage
task.

ClassificationCategory The classification code The classification and Required Required

within classification classification code
category. should be valid for the
using the Manage
task.

The following table lists the attributes required to import the Relationship object for the Account.
RelationshipId The internal ID for the Identify the relationship Conditionally required.
relationship. ID by exporting the Required.
Party object using the If the source of your
Setup and Maintenance, data is a third party or
Manage Bulk Data external system, and you
intend to import updates
302
Import Objects
Export, Schedule Export to previously imported
Processes task. records from the same Provide reference
system, provide the information to identify the
original source system account:
and source system
reference values. • RelationshipId.
and
RelationshipSourceSystem A source system code Identify the source Conditionally required. Required.
that identifies the original system or configure
source system of the source systems either If the source of your
relationship between the by using the Manage data is a third party or
object and the subject Trading Community external system, and you
parties. Source System task intend to import updates
to previously imported
system, provide the
and source system
reference values.

RelationshipSourceSystemReference
A source system Identify the source Conditionally required. Required.
reference that identifies system or configure
the original reference source systems either If the source of your
ID of the relationship by using the Manage data is a third party or
between the object and Trading Community external system, and you
the subject parties in the Source System task intend to import updates
source system. to previously imported
system, provide the
and source system
reference values.

SubjectPartyId The Oracle Sales Cloud Identify the party ID

classification belongs. object using the Setup Provide reference Provide reference

and and
CSV file. CSV file.
SubjectPartyNumber The public unique Identify the party ID


303
Import Objects
and and
CSV file. CSV file.
SubjectSourceSystem The code representing Identify the source


and and
CSV file. CSV file.

and and
CSV file. CSV file.
RelationshipType Describes the directional You can view the Required Not required
connection between relationship type and
the object and subject relationship type code
relationship. For example, definition from the Setup
Employer of verses and Maintenance,
Employee of. Manage Relationship
Types task.

RelationshipCode Describes the You can view the Required Not required
relationship, such as relationship type and
Contact or Membership. relationship type code
definition from the Setup
and Maintenance,
Manage Relationship
Types task.

The following table lists the attributes required to import the Team Member object for the Account.
304
Import Objects

classification belongs. object using the Setup Provide reference Provide reference

and and
CSV file. CSV file.


and and
CSV file. CSV file.


and and
CSV file. CSV file.

and and
305
Import Objects
CSV file. CSV file.
ResourceId The Oracle Sales Cloud Identify the resource ID

internal ID for sales team and resource number Required Required
member. value by exporting the
Party object using the Provide reference Provide reference
Setup and Maintenance, information to identify the information to identify the
Manage Bulk Data resource team member: resource team member:
Processes task. • ResourceId • ResourceId

• ResourcePartyNumber • ResourcePartyNumber
ResourcePartyNumber The public unique Identify the resource ID

identifier for the sales and resource number Required Required
team member. value by exporting the
Party object using the Provide reference Provide reference
Setup and Maintenance, information to identify the information to identify the
Manage Bulk Data resource team member: resource team member:
Processes task. • ResourceId • ResourceId

• ResourcePartyNumber • ResourcePartyNumber
Create Import Activity

You use the Manage File Import Activities task to create import activities. It consists of a step by step guided process to
assist you with creating an import activity for a given object.
1. Sign in as a setup user and navigate to the Setup and Maintenance work area.
2. Search for and select the Manage File Import Activities task.
3. On the Manage File Import Activities page, click the Create icon.
4. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select the
Account-Simplified View object from the Object list.
5. Select ZIP file from the File Type list, check the Desktop option, and browse and upload the required ZIP file.
6. To add attachments, under Attachments section, browse and upload your file. The attachment must be in ZIP
format.
Note: Ensure that you have the following columns and the required values in the
SalesCloudAccount.csv file:
Column Name Expected Value
ATTACHMENT_ FILE_NAME The file name with extension. For example, Sales.jpg.

ATTACHMENT_ FILE_DESC The description of the file.

ATTACHMENT_ FILE_TITLE The title of the file.

ATTACHMENT_ CATEGORY_NAME The category of the file. For example, MISC.

306
Import Objects
7. Click Next.
8. In the Create Import Activity: Create Schedule page, select an appropriate scheduling option from the Schedule list.
9. Click Next.
10. On the Create Import Activity: Review and Activate page, click Activate to activate the import activity immediately, or
click Save and Close if you want to use the import activity later.
307
Import Objects
308
Using Customer Data Management Using File-Based Export
6 Using File-Based Export
File-Based Data Export: Explained

File-Based Data Export lets you export a set of data from Oracle Sales Cloud. You can select a parent object and a set of
associated child objects, and output a ZIP file containing a separate file for each object. The output data sets contain only
those parent records which match the specified view criteria on the parent/child object and their associated child records
for the selected objects. File-Based Data Export supports the multi-CSV file format. This file format is also supported by File-
Based Data Import. You can use a combination of File-Based Data Export and File-Based Data Import to perform round-trip
export/import.
How Does File-Based Data Export Differ From Bulk Export

File-Based Data Export (FBDE) differs from Bulk Export in both the set of data exported as well as the format of the data that
is output. While Bulk Export supports the ability to export data at either the parent or child level, FBDE lets you configure an
export operation in which the output data set contains only the child records that are associated to the parent records that
match the specified filter criteria.
For example: Bulk Export - Account and Account Contact are selected. However the set of child records exported is
dependent upon the filter criteria configured at the child level. FBDE - Account and Account Contact are selected. However
the sets of child records exported include only those that are associated to a parent record that matches the specified filter
criteria at the parent level. FBDE does not support child level filter criteria.
The multiple CSV file format generated by FBDE consists of a ZIP file that contains one or more CSV files. Each CSV
file represents a separate object (either parent or child). The records within the child CSV file are associated to a parent
record contained within the parent CSV file. Association from child to parent record is accomplished by a foreign key to the
parent record. The foreign key for all child records associated to a parent record is the same. The output from an FBDE
operation appears as follows: USER_SPECIFIED_FILENAME.ZIP PARENTOBJECTNAME.CSV CHILDOBJECT1.CSV
CHILDOBJECT2.CSV CHILDOBJECTn.CSV. You can't rename the individual CSV files as part of the FBDE configuration.
Considerations for Exporting Data That You Plan to Import into Sales Cloud
Applications
You can export data from one Oracle Sales Cloud instance and then import it into another instance. In this case Oracle
recommends that you export all child objects and attributes for the selected parent object as doing so ensures that all
required attributes are included in the exported data set. The default values in FBDE for options such as Delimiter, time stamp
format and Date format all use the same default values as File Based Data Import so Oracle recommends that the default
values be used if the data is going to be imported back into an Oracle Sales Cloud instance.
File Based Data Export supports the ability to export the ID value of a record. This ID value is only valid within the source
instance and cannot be used on other Oracle Sales Cloud instances; therefore the ID value for a record should be set to
Ignore during the Map Fields step of File Based Data Import when importing data into the target Oracle Sales Cloud instance.
You must ensure that all custom objects and attributes exist in the target instance. If a corresponding custom object or
attribute haven't been created in the target instance, then it must be created before data can be successfully imported into
the target instance.
309
Exporting Your Data Objects

To export your data objects you must complete the following steps:
1. Create a File-Based Data Export activity
2. Schedule the activity
Creating a File-Based Data Export Activity

In the Setup and Maintenance work area navigate to the following:
• Offering: Sales
• Functional Area: Data Import and Export
• Task: Manage File Export Activities
You must create a new export activity, provide the parent object, activity name and file name details. When configuring a
file-based data export, you must consider how the exported data are used. If the data is to be consumed by an external
application, then you should select the appropriate time and date format as well as delimiter value to avoid the need to edit
the data once it has been exported.
Scheduling the Activity

You can schedule the activity immediately or at a later date. Scheduling at a later date has the following options:
• Incremental - For more information, see Configuring Incremental Export
• One Time Scheduling
• Repeating
For incremental export, you must provide the initial date time of interval, start and end date times, repeat frequency and
repeat unit. You must review the activity details and configurations and activate the activity to start the export process. The
export process generates the ZIP file containing the CSV files for each child object.
Parent-Child References in File-Based Data Export

When data is exported from Oracle Sales Cloud using File Based Data Export, the CSV files containing the child data contain
a reference to the parent object to which they are associated. The specific key used may vary between objects. The following
table illustrates the keys used to identify the parent object for each child object supported in File Based Data Export.
Supported Objects and Keys

The following table lists the various parent and child objects, corresponding output file names, and parent keys.
Parent Object Child Objects Output File Name Parent Key
Activity Activity Assignees Activity_ Assignee.csv ACTIVITY_ID

Activity Activity Contacts Activity_ Contact.csv ACTIVITY_ID

Asset Asset Contact Asset_ Contact.csv ASSETID

310
Asset Asset Resource Asset_ Resource.csv ASSETID

Contract Header Contract Party Contract_ Party.csv ID

Contract Header Contract Party Contract_ Party.csv MAJOR_VERSION

Contract Party Contract Party Contact Contract_ Party_ Contact.csv ID

Contract Party Contract Party Contact Contract_ Party_ Contact.csv MAJOR_VERSION

Account Profile Account Additional Name AdditionalName. csv PARTY_ID

Account Profile Account Address Address.csv PARTY_ID

Account Profile Account Address Purpose AddressPurpose. csv PARTY_ID

Account Profile Account Classification Classification. csv PARTY_ID

Account Profile Account Fax Fax.csv PARTY_ID

Account Profile Account Primary Phone PrimaryPhone. csv PARTY_ID

Account Profile Account Relationship Relationship. csv PARTY_ID

Account Profile Account Sales Profile SalesAccountProfile. csv PARTY_ID

Account Profile Account Web Url.csv PARTY_ID

Contact Profile Contact Additional Name AdditionalName. csv PARTY_ID

Contact Profile Contact Address Address.csv PARTY_ID

Contact Profile Contact Address Purpose AddressPurpose. csv PARTY_ID

Contact Profile Contact Classification Classification. csv PARTY_ID

Contact Profile Contact Relationship ContactRelationship. csv PARTY_ID

Contact Profile Contact e-mail Email.csv PARTY_ID

Contact Profile Contact Fax Fax.csv PARTY_ID

Contact Profile Contact Social Network InstantMessenger. csv PARTY_ID

311
Contact Profile Contact Mobile Mobile.csv PARTY_ID

Contact Profile Contact Phone Phone.csv PARTY_ID

Contact Profile Contact Sales Profile SalesAccountProfile. csv PARTY_ID

Lead Lead TC Member Lead_ Contact.csv LEAD_ID

Lead Lead Item Assoc Lead_ Product.csv LEAD_ID

Lead Lead Resource Lead_ Resource.csv LEAD_ID

Lead Lead Territory Assoc Lead_ Territories. csv LEAD_ID

Opportunity Opportunity Competitor OPPORTUNITY_ COMPETITOR. OPTY_ID

csv

Opportunity Opportunity Contact OPPORTUNITY_ CONTACT.csv OPTY_ID

Opportunity Opportunity Lead OPPORTUNITY_ LEAD.csv OPTY_ID

Opportunity Opportunity Reference OPPORTUNITY_ OPTY_ID

REFERENCE.csv

Opportunity Opportunity Resource OPPORTUNITY_ OPTY_ID

RESOURCE.csv

Opportunity Opportunity Response OPPORTUNITY_ OPTY_ID

RESPONSE.csv

Opportunity Revenue OPPORTUNITY_ REVENUE.csv OPTY_ID

Opportunity Revenue Partner OPPORTUNITY_ REVENUE_ OPTY_ID

PARTNER.csv

Opportunity Opportunity Source OPPORTUNITY_ SOURCE.csv OPTY_ID

Product Group Details Product Group Translations ProductGroup. csv PROD_GROUP_ID

Product Group Details Product Group Translations ProductGroup. csv REVISION_NUM

Product Group Details Product Group Products ProductGroupItem. csv PROD_GROUP_ID

Product Group Details Product Group Products ProductGroupItem. csv REVISION_NUM

Product Group Details Product Group Subgroups ProductGroupRelationship. csv PROD_GROUP_ID
312

Product Group Details Product Group Subgroups ProductGroupRelationship. csv REVISION_NUM

Sales Resource Quota Sales Resource Period Quota Resource_ Period_ Quota.csv RESOURCE_ QUOTA_ID

Sales Territory Sales Territory Coverage TERR_ COVERAGE.csv TERRITORY_ VERSION_ID

Sales Territory Sales Territory Line Of Business TERR_LOB.csv TERRITORY_ VERSION_ID

Sales Territory Sales Territory Resource TERR_ RESOURCE.csv TERRITORY_ VERSION_ID

Sales Territory Quota Sales Resource Quota Resource_ Quota.csv TERRITORY_ QUOTA_ID

Sales Territory Quota Sales Territory Period Quota Territory_ Period_ Quota.csv TERRITORY_ QUOTA_ID

Partner Partner Address Address.csv PARTY_ID

Partner Partner Fax Fax.csv PARTY_ID

Partner Partner Hierarchy Hierarchy.csv PARTY_ID

Partner Partner Certification PartnerCertification. csv PARTY_ID

Partner Partner Expertise PartnerExpertise. csv PARTY_ID

Partner Partner Dimension Geography PartnerGeography. csv PARTY_ID

Partner Partner Dimension Industry PartnerIndustry. csv PARTY_ID

Partner Partner Interface PartnerInterface. csv PARTY_ID

Partner Partner Dimension Product PartnerProductSpecialty. csv PARTY_ID

Partner Partner Account Resource PartnerTeam. csv PARTY_ID

Partner Partner Dimension Sales PartnerType. csv PARTY_ID

Channel

Partner Partner Primary Phone PrimaryPhone. csv PARTY_ID

Partner Partner Web Url.csv PARTY_ID

Program Enrollments Program Enrollment Contracts PartnerEnrollmentContract. csv PROGRAM_ ENROLLMENT_ID

Program Enrollments Program Enrollment Participants PartnerEnrollmentParticipant. csv PROGRAM_ ENROLLMENT_ID
313

Using File-Based Data Export to Export Data: Worked

Example
This example demonstrates how to export Opportunity object from an instance of Oracle Sales Cloud using File-Based Data
Export.
Exporting an Opportunity Object

To export an opportunity object, you must complete the following steps:
1. In the Setup and Maintenance work area navigate to the Manage File Export Activities.
2. On the Overview page, click Hierarchy Export. Click Create.
3. On the Create Export Process Definition page, enter name of activity, select Opportunity as parent object, and
enter the file name. Notification e-mail will be sent to your registered e-mail address after completion of export
activity. If you specify e-mail address in the Notification E-mail field, e-mail is sent to that e-mail address also.
4. Click Next. On the Create Export Process Definition: Review page, all attributes of the Opportunity object are
displayed.
5. Select the attributes that you want to export, using the Enabled check box.
6. You must create and save a view criteria to start the export process. Create a view criteria, by clicking the Edit Filter
Criteria button.
7. In the Edit Filter Criteria window, enter a name and a status for the view criteria. Click Save.
8. Click Next to go to the Create Export Process Definition page.
9. Schedule the export process either immediately or at a later date, by selecting the corresponding radio button.
10. Click Next to go to the review page, where you can either click Back to change any settings, Save and Close the
process to run at a later time, or Activate the process.
11. Review the status of your export activity on the Overview page.
12. Click on the generated ZIP file on the exported data file column and save the file to your desktop.
13. After completion of export activity, e-mail containing following information will be sent to the registered e-mail
addresses:
◦ Start and end times for the export (date and time), as well as a calculation of that interval
◦ The environment name
◦ Status of export
◦ The object name
◦ Record counts: Read, Successful, Errors, Warnings
◦ Submitted by
314
Using Customer Data Management Using Round-Trip Export-Import
7 Using Round-Trip Export-Import
Exporting and Importing Data Between Oracle Sales Cloud

Instances Using Automatic Mapping: Worked Example
This example demonstrates how to export Opportunity object from one instance of Oracle Sales Cloud using File-Based Data
Export. It also describes how to import the exported data into another instance of Oracle Sales Cloud using File-Based Data
Import without manually mapping the source file and the application attributes.
Exporting Data from Oracle Sales Cloud Using File-Based Data

Export
You can export data from Oracle Sales Cloud using File-Based Data Export, using the following steps:
1. In the Setup and Maintenance work area navigate to the Manage File Export Activities.
2. On the Overview page, click the Create icon.
3. On the Create Export Process Definition page, enter Name of activity, select Opportunity as Parent object, and
enter the File Name.
4. Click Next. On the Create Export Process Definition: Review page. All attributes of the Opportunity object are
displayed. Note that all child objects and their attributes are selected by default. Select the attributes that you want
to export, using the Enabled checkbox.
5. You must create a View Criteria before you can export. Click Edit Filter Criteria button to bring up the Edit Filter
Criteria dialog box.
6. You can use the View Criteria to filter the records based on certain criteria and save for future use. For instance,
you can create a criterion to filter records that were updated after a certain date, or records that were created by a
certain user. Add the required fields with conditions, and on the Saved Search drop down, click Personalize. On the
Personalize Saved Searches dialog box, provide the name for view criteria in the Name field. Click Apply and OK
to save.
11. Click on the generated ZIP file on the Exported data file column and save the file to your desktop.
Importing Data from Oracle Sales Cloud Using File-Based Data

Import
You can import data from Oracle Sales Cloud using File-Based Data Import, using the following steps:
1. In the Setup and Maintenance work area navigate to the Manage File Import Activities.
315

3. Select the FileType 'ZIP File'. Provide a name for the Import Activity in the Name textbox.
4. Select the Object Opportunity from the drop-down list. If you are trying to perform round trip export-import of a
custom object, make sure you have already generated the artifacts required for the importing and exporting of
custom fields and objects on the Generate Import and Export Artifacts page.
5. Click Next to get the Map Fields page.
Note: You can't map the Object Id value if you had exported the data from a different environment.
6. Click Next and Activate the import process in the Review and Activate page.
7. Review the status of your import activity on the Overview page.
Related Topics
• Using the Round-Trip Feature with the Export-Import Activity: Explained
• Exporting and Importing an Import Mapping Between Oracle Sales Cloud Instances: Procedure
Exporting and Importing Data Between Oracle Sales Cloud

Instances Using Automatic Mapping: Procedure
This procedure describes how to export data from one instance of Oracle Sales Cloud using File-Based Data Export. It also
describes how to import the exported data into another instance of Oracle Sales Cloud using File-Based Data Import without
manually mapping the source file and the application attributes.
Exporting Data from Oracle Sales Cloud Using File-Based Data Export
You can use the following steps to export data from an Oracle Sales Cloud instance using the automatic mapping feature:
◦ Offering: Sales
◦ Task: Manage File Export Activities

2. On the Overview page, click the Create icon.
3. On the Create Export Process Definition page, enter the name of the activity, select a Parent object, and enter
the File Name.
4. Click Next. On the Create Export Process Definition: Review page all attributes of the selected object are
displayed. All child objects and their attributes are selected by default. Select the attributes that you want to export,
using the Enabled check box.
5. You must create a View Criteria before you can export. Click the Edit Filter Criteria button to display the Edit Filter
Criteria dialog box.
6. You can use the View Criteria to filter the records based on certain criteria and save them for future use. For
instance, you can create a criterion to filter records that were updated after a certain date, or records that were
created by a certain user. Add the required fields with conditions, and on the Saved Search drop down list, click
Personalize. On the Personalize Saved Searches dialog box, provide the name for the view criteria in the Name
field. Click Apply and OK to save.
316

11. Click the generated ZIP file on the Exported data file column and save the file to your desktop.
Importing Data from Oracle Sales Cloud Using File-Based Data Import
You can use the following steps to import data from an Oracle Sales Cloud instance using the automatic mapping feature.
◦ Offering: Sales

3. Select the FileType ZIP File. Browse and select the file that you had generated as a result of export activity. Provide
a name for the import activity in the Name text box.
Note: Don't alter the name or contents of the ZIP file.
4. Select the Map Automatically check box to automatically map the columns in your source file to the application
attributes. Otherwise, you must manually map the columns in the data file for both the parent and child attributes.
5. Select the object that you want to import from the drop-down list.
If you're trying to perform round trip export-import of a custom object, make sure you have already generated the
artifacts required for the importing and exporting of custom fields and objects on the Generate Import and Export
Artifacts page. The Generate button is enabled only if the sandbox is not active. Disable the sandbox to activate
the Generate button.
6. Click Next to display the Map Fields page.
Note: You can't map the Object Id value if you had exported the data from a different Oracle Sales
Cloud environment. If one or more columns cannot be automatically mapped, then you must either
map them manually or select Ignore. Otherwise, the application generates an error.
7. Click Next and Activate to activate the import process in the Review and Activate page.
8. Review the status of your import activity on the Overview page.
Related Topics
• Exporting and Importing an Import Mapping Between Oracle Sales Cloud Instances: Procedure
• Using the Round-Trip Feature with the Export-Import Activity: Explained
317
318
Using Customer Data Management Enriching Data
8 Enriching Data
Data Enrichment: Overview

You can enrich your account and account contact (B2B contact) data in Oracle cloud applications using the Oracle Social
Data and Insight Cloud service, also known as, Data as a Service (DaaS). Data enrichment improves the quality of your
existing account or account contact data, address information, and enriches that data with additional information.
You can enrich Oracle cloud application data manually, real-time, or in bulk using batch data enrichment. Additionally, you
can also download enriched account and contact data from the Oracle Social Data and Insight Cloud service.
Batch Data Enrichment

The batch data enrichment option lets you enrich data in bulk by creating and submitting batch-processing jobs in the Data
Enrichment work area. This enrichment process flow comprises the following steps:
1. Create a DAAS user and assign appropriate privileges

2. Configure Sales Cloud to Data Cloud integration
3. Create and submit batch-processing jobs
4. Monitor batch status and take appropriate follow-up action
You can do the following two batch data enrichment types:
• Enrich Existing Records: Use this option to submit the existing records in the application for a bulk data
enrichment.
• Synchronize D&B Updates: Use this option to synchronize your D&B updates, including your previously enriched
organization and person records as well as new records imported from Data as a Service (DaaS), to uptake the latest
updated information form D&B
Manual Data Enrichment

If you require custom attributes for social data enrichment, then you must create a manual enrichment job. The manual
enrichment option lets you use custom import mappings to import the enriched records back. The manual enrichment
process flow is comprised of the following steps:
1. Export data from Sales Cloud to a CSV file
2. Enrich the data using 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
319
Real Time Data Enrichment

The real time enrichment option lets you enrich data one-record at a time during the create account or contact flow. It also
lets you enrich up to five existing records on the Accounts or Contacts simplified UI. This process flow is comprised of the
following steps:
1. Create a DAAS user and assign appropriate privileges
2. Set up real-time data enrichment preferences
3. Manage Sales Cloud and Data Cloud integration
4. Enrich Account and Account Contact Data real time on the Account and Contact pages
The following figure illustrates all the three available data enrichment process flows.
For more information, see the Using Oracle Social Data and Insight Cloud Service guide.
Batch Data Enrichment: Explained

You can use the batch data enrichment functionality to enrich your account and account contact (B2B contact) data in bulk
with additional information using D&B data.
You must complete the following prerequisites before you can enrich data in bulk:
1. Purchase a third-party Data as a Service (DaaS), also known as Oracle Social Data and Insight Cloud Service,
subscription.
320
2. The service administrator must create a new user with the Data Service Client API AppID role. This user is used by
Oracle Sales Cloud to securely communicate with the REST API for Oracle Social Data and Insight Cloud Service.
3. The service administrator must set up Oracle Sales Cloud and Data Cloud integration.
Batch Data Enrichment Types

You can do the following two batch data enrichment types:
• Enrich Existing Records: Use this option to submit the existing records in the application for a bulk data
enrichment.
• Synchronize D&B Updates: Use this option to synchronize your D&B updates, including your previously enriched
organization and person records as well as new records imported from Data as a Service (DaaS), to uptake the latest
updated information form D&B
Enriching Existing Data

You can enrich both organization (account) and person (contact) records by creating and submitting batch-processing jobs
in the Data Enrichment work area. These batches, in the background, export the records to Data as a Service (DaaS). The
exported records are enriched in DaaS by the REST API for Oracle Social Data and Insight Cloud Service with additional
information using D&B data. Finally, the enriched records are imported back. You can review the status of the scheduled and
processed batches on the Data Enrichment work area.
Note: Before enriching account contacts using the batch data enrichment process, you must enrich the
associated accounts.
Selecting Processing Options

To enrich your existing records, you can select one of the following two processing options:
• Review Batch: Select this processing option to review the results of data enrichment in the matched candidate
records in the batch before importing the enriched data. Note that the review batch option shows only the first 100
records from the data enrichment batch.
• Process Batch mode: Select this processing option to submit the data enrichment batch for processing without a
review.
Synchronizing Your D&B Updates

You can periodically synchronize your D&B updates, including your previously enriched organization and person records
as well as new records imported from Data as a Service (DaaS), to uptake the latest updated information form D&B. You
can synchronize these records from the Data Enrichment work area, using the Synchronize D&B Updates Oracle Enterprise
Scheduler Service job. For more information, see: Synchronizing Previously Enriched Data: Procedure.
Reviewing Results
You can search for the status of scheduled and processed batches on the Data Enrichment work area. The batch ID contains
the link to the Batch Details page. You can download the details of the processed records by clicking on the linked number
on the Batch Details table. Batches submitted with the Review Batch processing option appear on the Data Enrichment work
area in the status Review when completed. After reviewing the results of data enrichment in the matched candidate records in
the batch, you must click Import to uptake the enriched data.
321
Creating a Data Enrichment Batch: Procedure

Use this procedure to create a data enrichment batch to enrich existing customer data in bulk with additional information
using D&B data.
To create a data enrichment batch:
1. Navigate to the Data Enrichment work area as follows: Navigator > Customer Data Management > Data
Enrichment
2. Click the Create action menu option or button to run the data enrichment batch definition process train.
3. Enter the following basic information in the Create Data Enrichment Batch page. Enter the following sample data:
◦ Batch Name: Data_Enrichment_Batch_1
◦ Confidence Score: You can leave it at default 90 or specify a new score.
◦ Party Type: Select Organization to enrich an account record or Person to enrich a contact record.
◦ Processing Option:
• Review Batch: Select this processing option to review the results of data enrichment in the matched
candidate records in the batch before importing the enriched data. Note that the review batch option
shows only the first 100 records from the data enrichment batch.
• Process Batch: Select this option if you want to submit your data enrichment batch for processing
without a review. This is the default batch data enrichment option.
4. Click Next
5. Enter the record selection criteria on the Enrich Organizations: Selection Criteria page.
6. Click Preview to verify that the selection criteria yielded records in the batch.
7. Review the batch and click Next. Create Data Enrichment Batch: Review page appears.
8. Click Submit to send the records for batch data enrichment.
You can search for the status of scheduled and processed batches on the Data Enrichment work area. The batch ID contains
the link to the Batch Details page. You can download the details of the processed records by clicking on the linked number
on the Batch Details table.
Batches submitted with the Review Batch processing option appear on the Data Enrichment work area in the status
Review when completed. After reviewing the results of data enrichment in the matched candidate records in the batch, you
must click Import to uptake the enriched data.
Note: If you require custom attributes for social data enrichment, then you must create a manual enrichment
job. The manual enrichment option lets you use custom import mappings to import the enriched records back.
For more information about manual data enrichment, see the Related Links section.
Related Topics
• Enriching Account and Account Contact Data Manually: Explained
322
Synchronizing D&B Updates: Procedure

You can periodically synchronize your D&B updates, including your previously enriched organization and person records
as well as new records imported from Data as a Service (DaaS), to uptake the latest updated information form D&B. You
can synchronize these records from the Data Enrichment work area, using the Synchronize D&B Updates Oracle Enterprise
Scheduler Service job. You can update or synchronize records only if they have a DaaS ID assigned to them. In case some
records were originally excluded from synchronization in the DaaS Administrator UI, these records cannot be synchronized
and updated.
Note: Note that a synchronization job updates one million records at a time. If you have more than one million
records to update, you must submit the synchronization batch a second time.
Perform the following steps to synchronize your D&B updates:
1. Navigate to the Data Enrichment work area.

2. Click Actions.
3. Select Synchronize Organizations or Synchronize Persons. The Schedule Updates for Person or Schedule Updates
for Organization page appears.
4. Click Advanced to select batch run options such as 'As soon as possible' or 'Using a schedule'. By default, the
batch run is scheduled for 'As soon as possible'.
In the Advanced Option section of the Schedule Updates for Persons or Schedule Updates for Organizations page,
you can update the frequency in which you want the batch to run. You can also set a start and end date to the batch
schedule.
5. Click Submit.
6. Click OK in response to the confirmation message.
You can search for the status of scheduled synchronization batches on the Data Enrichment work area. The batch ID
contains the link to the Batch Details page. You can download the details of imported (synchronized) and not imported (not
synchronized) records by clicking the linked number on the Batch Details table.
Note: You cannot see the list of records that were excluded from synchronization in the Imported or Not
Imported record list.
323
324
Using Customer Data Management Cleansing Addresses
9 Cleansing Addresses
Cleanse Customer Information

Scheduling a Data Cleansing Process: Points to Consider
Data cleansing processes can be time consuming, depending on the batch size.
Consider the following before scheduling a data cleansing process:

• Time required for the process
• System resources
• Process dependencies
Time Required for the Process

The time required to complete the data cleansing process depends on the number of records, cleansing complexity, and
hardware characteristics. You must calculate the possible time taking into account these three factors and the available
benchmark.
System Resources
You must estimate system performance based on recent data, by reviewing the batch and environment statistics. You can
also review various object lists to know the time when most system resources are available for the data cleansing process.
Process Dependencies
You must understand process dependencies before scheduling the data cleansing process. For example, you must consider
whether other processes are waiting for the results of the data cleansing process.
Creating Address Cleansing Batches: Points to Consider

You create an address-cleansing batch to cleanse and validate addresses. Consider the following before creating an
address-cleansing batch that best suits your address cleansing needs:
• Use a copy of an existing address cleansing batch
• Create an address cleansing batch for a single run or to be run periodically
Use a Copy of an Existing Address Cleansing Batch

You can quickly create an address-cleansing batch by copying an existing cleansing batch. You can edit the batch details
such as batch selection criteria, address cleansing mode, and scheduling before you submit the batch.
Note: You can search for existing Address Cleansing batches using the Saved Searches.
You create a new address cleansing batch, instead of copying an existing cleansing batch, if your address cleansing batch
details are unique.
325
Create an Address Cleansing Batch for a Single Run or to be Run Periodically

You can create an address-cleansing batch for a single run or to be run periodically. You can run address-cleansing batches
periodically for tasks that are mostly ongoing and repetitive, such as the execution of registry address cleansing.
You can schedule the batch to run at a specific time or at a specific interval. For example, you can schedule the batch to run
daily, every night at 9 PM, weekly, or every Sunday at 10 PM.
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. This resolves existing errors as
well as updates the addresses with the changes in the geography reference data such as postal code.
You can create an address-cleansing batch and specify selection criteria on the Create Address Cleansing Batch page. You
can define the selection criteria similar to a database query for better results. For example, multiple selection criteria are joined
with an AND condition.
To create an address-cleansing batch and specify the selection criteria:
1. Navigate to the Create Address Cleansing Batch page as follows: Navigator > Customer Data Management >
Address Cleansing.
2. Enter a Batch Name.
3. Select an appropriate batch mode.
Select Simulated mode to review and accept the cleansed address before committing the address-cleansing job.
Select Automated mode to cleanse the address and save it automatically.
4. Provide a batch description, if required.
5. Click Create on the tools menu in the section Address Cleansing Batch: Selection Criteria.
6. Enter the Selection Criteria. The following table contains sample selection criteria.
Object Attribute Operator Value
Location Address1 Contains 500 Oracle

Location Country Equal to US

7. Click Schedule to specify process options. The Schedule Address Cleansing Batch page appears.
8. Click Submit.
9. Click OK to confirm the batch submission.
Accepting Address Cleansing Results: Critical Choices

You can accept or reject the results of a batch address cleansing process run in simulated mode as follows:
• Accept or reject the address cleansing process results for the entire batch
• Accept or reject the address cleansing process results by country
• Accept or reject address cleansing process results by address record
326
Note: If you submit a batch for cleansing in the automated cleansing mode, then you can't accept or reject the
process results. The cleansed address is automatically saved to the database.
Accept Or Reject the Address Cleansing Process Results for the Entire Batch
Accept the results for the entire batch only if you are sure that the address cleansing results are accurate. Reject the results if
you are not sure about the reliability or accuracy of the batch results, or if the process results may reduce the data quality.
Accept or Reject the Address Cleansing Process Results by Country

The address cleansing process results depend on the data quality, coverage, and the geography information of the country or
region.
Consider the following before accepting or rejecting address cleansing process results by country:
• If the percentage of errors is high and the results for all countries are not acceptable, then Accept data only for
countries with acceptable cleansing results.
• Reject data for countries with very high percentage of errors.
Accept or Reject Address Cleansing Process Results by Address Record

Accept or reject cleansing results for each individual address based on the cleansing status and business rules and policies.
FAQs for Cleanse Customer Information

What's an Address Cleansing Batch?
An address cleansing batch is a set of records that is submitted for address cleansing. Batch cleansing validates and
cleanses address data in the registry. This resolves existing errors as well as updates the addresses with the changes in the
geography reference data such as postal code.
Can I resubmit an address cleansing batch?

No. However, if you update or edit the addresses you can resubmit the addresses as a new batch.
What's the difference between automated cleansing and simulated

cleansing?
Automated Cleansing mode doesn't not require any user action. You use this mode to automatically save cleansed address
cleansing batch to the database.
Simulated Cleansing mode lets you review the output of the batch cleansing process before saving the cleansed data.
Additionally, you can accept or reject cleansed data in its entirety, by country, or by individual address.
327
Why did the batch cleansing process skip some records?

Batch cleansing skips a record if the record is already cleansed and validated. For example, an address that already follows
the formats, norms, and standards of the related postal directory.
328
Using Customer Data Management Identifying Duplicates
10 Identifying Duplicates
Identify Duplicate Customer Information

Managing Duplicate Sets: Explained
To identify potential duplicate customer information in your database, you must create and run duplicate identification
batches. When complete, these batches contain sets of two or more potential duplicate records. You can manage these
duplicate sets by reviewing the details of the completed duplicate identification batches, and submitting duplicate resolution
requests.
While managing duplicate sets you can do the following:
• Resolve duplicates within each identified duplicate set through a merge or link request. You create a merge request
to combine duplicate records, a link request to join duplicate records, or a generic request to select the resolution
later.
• Remove records that you do not want to include in the duplicate resolution request. You can view the removed
records in the removed records table, and can also restore these records back to the set.
• Mark a pair of records as nonduplicate to prevent them from being identified as potential matches. To remove the
pair from nonduplicate list, end date the nonduplicate record.
• Change the master record.
• 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 from scratch for a single or periodic run.
• Create the duplicate identification batch from a copy of an existing duplicate identification batch.
You can choose between two of the following batch match modes while creating a duplicate identification batch:
• Within the batch: Runs the duplicate identification process within the batch.
• Against the registry: Runs the duplicate identification process against the registry.
Duplicate Identification Batch for Single or Periodic Run

You can create a duplicate identification batch for a single run or periodic run. Periodic duplicate identification batches are
used for tasks that are mostly ongoing and repetitive such as the execution of registry duplicate identification.
You can schedule the periodic batch to run at a specific time or at a specific interval. For example, you can schedule the
batch to run daily, every night at 9 PM, weekly, or every Sunday at 10 PM.
329
Using the Copy of an Existing Duplicate Identification Batch

You can quickly create a duplicate identification batch by copying an existing duplicate identification batch. You can edit the
batch details such as subset rules or batch selection criteria rules, duplicate identification rules, and schedule of the batch
process before you submit the batch.
You create a new duplicate identification batch, instead of copying an existing batch, if your duplicate identification batch
details are unique.
Duplicate Identification Within the Batch Match Mode

In the Within the Batch Match mode, duplicate identification is limited to the records within a batch that meet the subset
rule conditions or the batch selection criteria rules. The records that do not meet the selection criteria are not processed in
this mode.
Duplicate Identification in Against the Registry Batch Match Mode

In the Against the Registry Batch Match mode, duplicate identification is not limited to the records within the batch. The
process aggregates the records that meet the subset rule conditions in a batch and these records are matched against one
another as well as against other records in the database.
Adding Additional Attributes to Define Subset Rules: Procedure

To create duplicate identification batches, you must specify subset rules, also known as batch selection criteria rules, on
the Create Duplicate Identification Batch page. You define the subset selection criteria similar to a database query for better
results. A subset rule is defined by joining multiple objects, attributes, operators, and their corresponding values with an AND
condition.
You can add additional custom or standard attributes of an account (organization) or contact (person) to the set of attributes
available in the UI for defining subset rules for identifying duplicates.
To add new attributes to the batch selection criteria, you must add the required attributes to the lookup types
ZCH_MATCH_OBJ_PERSON and ZCH_MATCH_OBJ_ORGANIZATION, as lookup codes. Before you update the lookup types, you must
identify the display name and API (internal) name for each attribute that you want to add.
Identifying Display Name and API Name for an Attribute

You must identify the display name and the API (internal) name of the attributes that you want to add as subset rule selection
criteria.
You can find the list of standard attributes for accounts and contacts, along with their lookup code, display name (meaning),
and API name (tag), from the topic "Standard Account and Contact Attributes". Use the following steps to identify the
display name and the API name of the custom attributes of an account (organization) or contact (person) using Application
Composer.
Note: You must be in an active sandbox, to view and update objects in the Application Composer.
1. Sign in as a setup user, such as Master Data Management Application Administrator, and navigate to Application
Composer.
2. Expand the Standard Objects list and navigate to Account or Contact.
3. Click Fields under Account or Contact. The Fields page appears.
4. Select the Custom tab to see the list of available attributes.
5. Click the Display Label link that you want to add. The Edit Custom Field page appears
330
6. Copy the Display Name and the API Name.
Updating the Attribute Lookups with New Attributes

To add new attributes to the subset selection criteria, you must add the required attributes to the attribute lookup types
for person (contact) object ZCH_MATCH_OBJ_PERSON or to the organization (account) object, ZCH_MATCH_OBJ_ORGANIZATION,
respectively.
Perform the following steps to add the required attributes to the attribute lookup types as lookup codes.
1. Sign in as a setup user, such as Master Data Management Application Administrator, and navigate to the Setup and
Maintenance work area.
2. Search for and navigate to the task Manage Standard Lookups.
3. Enter the required Lookup Type.
◦ Use the lookup type ZCH_MATCH_OBJ_ORGANIZATION to add new custom or standard attributes to the subset rule
selection criteria of the organization (account) object.
◦ Use the lookup type ZCH_MATCH_OBJ_PERSON to add new attributes to the subset rule selection criteria of the
person (contact) object.
4. Click Search.
5. Click New on the Lookup Codes section of the Manage Standard Lookups page.
6. Add a Lookup Code for each attribute.
◦ Lookup Code: An internal name for the attribute. This field is case-sensitive. The value should be in all capital
letters and the space should be replaced with an underscore. For example, CUSTOM_ATTR can be a lookup
code for custom attribute.
Note: For date fields, you must suffix the lookup code with _DATE. This enables the application to
identify the attribute value as date and display the date picker.
◦ Display Sequence: The order in which the lookup code must be displayed. This is not a mandatory field.
◦ Meaning: The display name of the attribute. This field is mandatory and case-sensitive.
◦ Description: The description of attribute that you see on the duplicate identification work area.
◦ Tag: The API (Internal) Name of the attribute. This field is mandatory and case-sensitive.
7. Click Save and close.
To hide or remove any attribute, you must delete the lookup code.
Note: You must publish the sandbox to activate the newly added attributes. Only after you publish the sandbox,
the newly added attributes appears in the Subset Rules for Identifying Duplicates section of the Create Duplicate
Identification Batch page. If the sandbox is not published, the tag value with the attribute name is considered
invalid.
Standard Account and Contact Attributes

This topic describes the standard account and contact attributes available for use in Subset Rule Selection Criteria.
Note: For date related attributes, you must suffix the lookup code with _DATE. Standard Attributes for
Accounts.
331
Standard Attributes for Accounts

The following table lists the standard attributes for account (organization) along with their lookup code, display name
(meaning), and API name (tag) that you can add as subset rule selection criteria for identifying duplicates:
Lookup Code Meaning (Attribute Display Name) Tag (API Name)
ANALYSIS_FY Analysis Year AnalysisFy

BANK_CODE Bank Code BankCode

BANK_ OR_ BRANCH_NUMBER Bank or Branch Number BankOrBranchNumber

BRANCH_CODE Branch Code BranchCode

BRANCH_FLAG Branch Indicator BranchFlag

BUSINESS_SCOPE Business Scope BusinessScope

CEO_NAME Chief Executive Name CeoName

CEO_TITLE Chief Executive Title CeoTitle

CERTIFICATION_ LEVEL Certification Level CertificationLevel

CERTREASON_ CODE Certification Reason CertReasonCode

CLEANLINESS_ SCORE Cleanliness CleanlinessScore

COMMENTS Comments Comments

COMPLETENESS_ SCORE Completeness CompletenessScore

CONG_DIST_CODE Congressional District CongDistCode

CONTROL_YR Organization Control Year ControlYr

CORPORATION_ CLASS Corporation Class CorporationClass

CREATION_DATE Creation Date CreationDate

CURRENT_ FY_ POTENTIAL_REV Current Fiscal Year's Potential Revenue CurrFyPotentialRevenue

DATA_ CLOUD_STATUS Enrichment Status DataCloudStatus

DATA_ CONFIDENCE_ SCORE Data Confidence DataConfidenceScore
332

DB_RATING D&B Credit Rating DbRating

DIS_ADV_IND Disadvantaged Indicator DisadvantagedIndicator

DOM_ ULTIMATE_ DUNSNUM_C Domestic D-U-N-S number DomesticUltimateDunsNumC

DO_ NOT_ CONFUSE_WITH Do Not Confuse With DoNotConfuseWith

DUNS_NUMBER_C D-U-N-S number DunsNumberC

DUPLICATE_ INDICATOR Duplicate Type DuplicateIndicator

DUPLICATE_ SCORE Duplication DuplicateScore

EMPS_ AT_ PRIMARY_ ADDRESS Number of Employees at Identifying Address EmpAtPrimaryAdr

EMPS_ AT_ PRIMARY_ ADDR_EST Number of Employees at Identifying Address EmpAtPrimaryAdrEstInd

Estimated Qualifier

EMPS_ AT_ PRIMARY_ ADDR_MIN Number of Employees at Identifying Address EmpAtPrimaryAdrMinInd

Minimum Qualifier

EMPLOYEES_ TOTAL Number of Employees EmployeesTotal

ENQUIRY_DUNS ENQUIRY_DUNS EnquiryDuns

ENRICHMENT_ SCORE Enrichment EnrichmentScore

EXPORT_IND Exporter Indicator ExportInd

FISCAL_ YEAREND_MONTH Fiscal Year End Month FiscalYearendMonth

GLOBAL_ ULTIMATE_ DUNSNUM_C Global Ultimate D-U-N-S Number GlobalUltimateDunsNumC

GROWTH_ STRATEGY_DESC Growth Strategy Description GrowthStrategyDesc

GSA_ INDICATOR_ FLAG GSA Indicator GsaIndicatorFlag

HOME_COUNTRY Home Country HomeCountry

HQ_ BRANCH_ INDICATOR HQ branch indicator HqBranchInd

IMPORT_IND Importer Indicator ImportInd

333
INCORP_YEAR Year Incorporated IncorpYear

INTERNAL_FLAG Internal InternalFlag

JGZZ_ FISCAL_CODE Taxpayer identification number JgzzFiscalCode

LABOR_ SURPLUS_IND Labor Surplus Indicator LaborSurplusInd

LAST_ ASSIGNMENT_ DATE Last Assigned Date LastAssignedDate

LAST_ ENRICHMENT_ DATE Last Enrichment Date LastEnrichmentDate

LAST_ SCORE_ UPDATE_DATE Last Score Date LastScoreUpdateDate

LAST_ SOURCE_ UPDATE_DATE Last Source Update Date LastSourceUpdateDate

LAST_ UPDATE_DATE Last modified date LastUpdateDate

LAST_ UPDATED_BY Last modified by LastUpdatedBy

LAST_ UPDATE_ SOURCE_SYSTEM Last Update Source System LastUpdateSourceSystem

LEGAL_STATUS Legal Status LegalStatus

LINE_ OF_BUSINESS Line of Business LineOfBusiness

LOCAL_ ACTIVITY_CODE Local Activity Code LocalActivityCode

LOCAL_ ACTIVITY_ CODE_TYPE Local Activity Code Type LocalActivityCodeType

LOCAL_ BUS_ IDENTIFIER Common Business Identifier LocalBusIdentifier

LOCAL_ BUS_IDEN_TYPE Common Business Identifier Type LocalBusIdenType

MINORITY_ OWNED_IND Minority-Owned Indicator MinorityOwnedInd

MINORITY_ OWNED_TYPE Type of Minority-Owned Organization MinorityOwnedType

MISSION_ STATEMENT Mission Statement MissionStatement

NAMED_FLAG Named Account NamedFlag

NEXT_ FY_ POTENTIAL_ REVENUE Next Fiscal Year's Potential Revenue NextFyPotentialRevenue

334
OOB_IND Out of Business Indicator OobInd

ORGANIZATION_ NAME Name OrganizationName

OWNER_PARTY_ID Owner ID OwnerPartyId

PARENT_ DUNS_NUMBER_C Parent D-U-N-S Number ParentDunsNumC

PARENT_SUB_IND Subsidiary Indicator ParentSubInd

PARTY_ID Party Id PartyId

PARTY_NUMBER Registry ID PartyNumber

PREF_ CONTACT_ METHOD Preferred Contact Method PreferredContactMethod

PREF_ CONTACT_ PERSON_ID Preferred Contact Person Id PreferredContactPersonId

PREF_ FUNCTIONAL_ CUR Preferred Functional Currency PrefFunctionalCurrency

PRINCIPAL_NAME Principal Name PrincipalName

PRINCIPAL_ TITLE Principal Title PrincipalTitle

PUBLIC_ PRIVATE_ OWNER_FLAG Private Ownership PublicPrivateOwnershipFlag

RECENCY_SCORE Recency RecencyScore

REGISTRATION_ TYPE Registration Type RegistrationType

RENT_OWN_IND Rent or Own Indicator RentOwnInd

SALES_ PROFILE_ STATUS Sales Profile Status SalesProfileStatus

SALES_ PROFILE_TYPE Type SalesProfileType

SMALL_BUS_IND Small Business Indicator SmallBusInd

STOCK_SYMBOL Stock Symbol StockSymbol

TOTAL_ EMP_EST_IND Number of Employees Estimated Qualifier TotalEmpEstInd

TOTAL_ EMPLOYEES_IND Number of Employees Includes Subsidiaries TotalEmployeesInd

335
TOTAL_ EMP_MIN_IND Number of Employees Minimum Qualifier TotalEmpMinInd

TOTAL_EMP_TEXT Total Number of Employees TotalEmployeesText

TOTAL_ PAYMENT_ AMOUNT Total Payments TotalPayments

UNIQUE_ NAME_ALIAS Organization Name UniqueNameAlias

UNIQUE_ NAME_SUFFIX Name Suffix UniqueNameSuffix

VALIDITY_SCORE Validity ValidityScore

WOMAN_ OWNED_IND Woman-Owned Indicator WomanOwnedInd

YEAR_ ESTABLISHED Year Established YearEstablished

Standard Attributes for Contact

The following table lists the standard attributes for contact (person) along with their lookup code, display name (meaning), and
API name (tag) that you can add as subset rule selection criteria for identifying duplicates:
CERTIFICATION_ LEVEL Certification Level CertificationLevel

CERT_ REASON_CODE Certification Reason CertReasonCode

CLEANLINESS_ SCORE Cleanliness CleanlinessScore

COMMENTS Comments Comments

COMPLETENESS_ SCORE Completeness CompletenessScore

CREATED_BY Created by CreatedBy

CREATION_DATE Creation date CreationDate

DATA_ CLOUD_STATUS Enrichment Status DataCloudStatus

DATA_ CONFIDENCE_ SCORE Data Confidence DataConfidenceScore

DATE_ OF_BIRTH_DATE Date of Birth DateOfBirth

DATE_ OF_DEATH_DATE Date of Death DateOfDeath
336

DECEASED_FLAG Person Deceased DeceasedFlag

DECLARED_ ETHNICITY Declared Ethnicity DeclaredEthnicity

DEPARTMENT Department Department

DEPARTMENT_ CODE Department Code DepartmentCode

DO_ NOT_CALL_FLAG Do not call DoNotCallFlag

DO_ NOT_ CONTACT_FLAG Do not contact DoNotContactFlag

DO_ NOT_ EMAIL_FLAG Do not e-mail DoNotEmailFlag

DO_ NOT_MAIL_FLAG Do not mail DoNotMailFlag

DUPLICATE_ INDICATOR Duplicate Type DuplicateIndicator

DUPLICATE_ SCORE Duplication DuplicateScore

ENRICHMENT_ SCORE Enrichment EnrichmentScore

GENDER Gender Gender

INTERNAL_FLAG Internal InternalFlag

JGZZFISCAL_ CODE Taxpayer identification number JgzzFiscalCode

JOB_TITLE Job Title JobTitle

JOB_TITLE_CODE Job Title Code JobTitleCode

LAST_ ASSIGNMENT_ DATE Last Assigned Date LastAssignedDate

LAST_ CONTACT_DATE Last Contact Date LastContactDate

LAST_ ENRICHMENT_ DATE Last Enrichment Date LastEnrichmentDate

LAST_KNOWN_GPS Last Known Location LastKnownGPS

LAST_ SCORE_ UPDATE_DATE Last Score Date LastScoreUpdateDate

LAST_ SOURCE_ UPDATE_DATE Last Source Update Date LastSourceUpdateDate
337

LAST_ UPDATE_DATE Last modified date LastUpdateDate

LAST_ UPDATED_BY Last modified by LastUpdatedBy

LAST_ UPDATE_ SOURCE_SYS LastUpdateSourceSystem LastUpdateSourceSystem

MARITAL_STATUS Marital Status MaritalStatus

MARITAL_ STATUS_ EFF_DATE Marital Status Effective Date MaritalStatusEffectiveDate

NAMED_FLAG Named Contact NamedFlag

OWNER_PARTY_ID Owner ID OwnerPartyId

PARTY_ID PartyId PartyId

PARTY_NUMBER Registry ID PartyNumber

PERSON_ ACADEMIC_ TITLE Academic Title PersonAcademicTitle

PERSONAL_ INCOME Annual Income PersonalIncome

PERSON_ FIRST_NAME First name PersonFirstName

PERSON_ INITIALS Initials PersonInitials

PERSON_ LAST_NAME Last name PersonLastName

PERSON_ LAST_ NAME_PREFIX Last Name Prefix PersonLastNamePrefix

PERSON_ MIDDLE_NAME Middle Name PersonMiddleName

PERSON_ NAME_SUFFIX Suffix PersonNameSuffix

PERSON_ PRENAME_ ADJUNCT Prefix PersonPreNameAdjunct

PERSON_ PREV_LASTNAME Previous Last Name PersonPreviousLastName

PERSON_ SECOND_ LASTNAME Second Last Name PersonSecondLastName

PERSON_TITLE Title PersonTitle

PLACE_OF_BIRTH Place of Birth PlaceOfBirth
338

PREF_ CONTACT_ METHOD Preferred Contact Method PreferredContactMethod

PREF_ FUNCTIONAL_ CUR Preferred Functional Currency PrefFunctionalCurrency

RECENCY_SCORE Recency RecencyScore

RENT_OWN_IND Rent or Own Indicator RentOwnInd

SALES_ AFFINITY_CODE Affinity SalesAffinityCode

SALES_ BUYING_ ROLE_CODE Buying Role SalesBuyingRoleCode

SALES_ PROFILE_ STATUS Sales Profile Status SalesProfileStatus

SALES_ PROFILE_TYPE Type SalesProfileType

SALUTATION Salutation Salutation

UNIQUE_ NAME_SUFFIX Name Suffix UniqueNameSuffix

VALIDITY_SCORE Validity ValidityScore

Creating Duplicate Identification Batches and Defining Subset Rules:

Worked Example
You can create a duplicate identification batch and define subset rules, also known as batch criteria rules, to retrieve a subset
of the records within the batch or in the registry.
Subset rules specify the criteria for retrieving a subset of records in the duplicate identification batch. The data quality engine
identifies duplicate records from this subset of records. The rules for identifying duplicates are defined using one of the
following options:
• Match all keywords: Select this option to perform an AND operation.

• Match any keyword: Select this option to perform an OR operation.
In this example, we first create a duplicate identification batch to identify duplicate persons in the registry, and then create a
rule to retrieve a subset of records where the person name contains John and the address contains Redwood.
1. Navigate to the Duplicate Identification work area as follows: Navigator > Customer Data Management >
Duplicate Identification .
2. Click Create menu option or button. The Create Duplicate Identification Batch page appears.
3. Enter a batch name and description.
339
Note: Alternatively, select an existing duplicate identification batch and Click copy to quickly create a new
duplicate identification batch. You can then edit the batch details before you submit the batch.
4. Specify the Batch Match Mode such as Against the Registry or Within the Batch.
In the Within the Batch Match mode, the duplicate identification is limited to the records in a batch that meet the
subset rule conditions. In the Against the Registry Batch Match mode, the process aggregates the records that
meet the subset rule conditions in a batch, and these records are matched against one another as well as against
other records in the database.
5. Specify the Party Type as Person.
6. Specify the Automatic Processing option as Create Merge Request to merge the duplicate persons.
7. Click Add menu option or button under Duplicate Identification Batch: Selection Criteria.
8. Specify the Apply Rules options as Match any keyword.
9. Enter the following sample information in the Duplicate Identification Batch: Selection Criteria table.
Object Attribute Operator Value
Person Name Contains John

Address Address Line 1 Contains Redwood

10. Click Save and Close or Schedule per your requirement.
View Nonduplicate Mapping

Nonduplicate Records: Explained
You mark a pair of records as nonduplicate to prevent the pair from being identified as potential matches. You can view
nonduplicate records on the Manage Nonduplicate Records UI page as follows:
1. Navigate to the Duplicate Identification work area.
2. Click Tasks.
3. Click Manage Nonduplicate records. The Manage Nonduplicate Records page appears.
4. Search for the nonduplicate records.
You can modify the period for which a record should be considered as a nonduplicate by changing the end date. You can
also delete the nonduplicate status of a record by end dating it.
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 to data stewards for review and processing.
You can initiate the assignment of duplicate identification batches to an assignee by clicking on the Assign button on the
340
Duplicate Identification work area and complete it on the Assign Duplicate Identification Batch page. Data Steward Managers
can reject any duplicate identification batch, but Data Stewards can only reject the batches that are assigned to them. Ensure
that the users to whom you want to assign a duplicate identification batch have the Customer Data Steward resource role
assigned to them. Unless the users have this role assigned, you may not see their names in the 'Assign To' drop down on the
duplicate resolution UI.
How can I cancel a batch process?

You can cancel a batch process in the Scheduled Processes Overview page. You can navigate to this page as follows:
Navigator > Tools > Scheduled Processes. You must search for the batch process by its process ID, and then cancel the
batch process request.
How can I schedule a saved duplicate identification batch?

You can schedule a saved duplicate identification batch by searching for it on the Duplicate Identification work area and
editing its processing options.
When do I select the Create Single Request option?

The Create Single Request option is available for individual duplicate sets in a duplicate identification batch. You can
use this option to specify duplicate processing options at individual duplicate set level that are different from the duplicate
processing options selected at the batch level. You can also use this option to specify different duplicate processing options
for different duplicate sets.
341
342
Using Customer Data Management Resolving Duplicates
11 Resolving Duplicates
Creating Duplicate Resolution Requests: Explained

You create a duplicate resolution request to resolve potential duplicates in the data registry.
Depending on your business scenarios, you may create duplicate resolution requests using one of the following options:
• Create Duplicate Resolution Requests on the Duplicate Resolution work area to process a generic resolution
request.
• Create Duplicate Resolution Requests manually on the Create Resolution Request UI page.
• Create Duplicate Resolutions Requests on the Duplicate Identification work area as part of the duplicate identification
flow.
Creating Duplicate Resolution Requests to Process a Generic Resolution

Request
If you selected Create Duplicate Resolution Request as the Automatic Processing Option, on the Create Duplicate
Identification Batch page, then generic duplicate resolution requests are created when the duplication identification process is
complete. You can also specify the creation of a generic resolution request while:
• Reviewing duplicate sets and creating single requests for each duplicate set on the Duplicate Identification Batch
details page.
• Creating a duplicate resolution request manually for confirmed duplicates on the Create Resolution Request UI page.
Specifying a generic resolution request lets you make the merge or link decision later. You select a generic resolution request
when you are not sure whether you want to merge or link the parties.
You can review these generic resolution requests on the Duplicate Resolution work area and complete processing them by
creating duplicate resolution requests of the type merge or link.
Note: You can process a generic resolution request only if its status is New. To process requests in pending
status, you must first request your administrator to run the Run Request Dispatch Job from the Setup and
Maintenance area to set their status to New.
Creating Duplicate Resolution Requests Manually

When you are sure that two or more records are confirmed duplicates, you can decide to create a duplicate resolution
request manually using the following steps:
1. Navigate to the Create Resolution Request UI page as follows: Navigator > Duplicate Resolution > Tasks.
2. Search for and multi-select the duplicate records using the shift key.
3. Create a duplicate resolution request of an appropriate type, such as a generic, merge, or link request for the
selected records.
343
Creating Duplicate Resolutions Requests during the Duplicate Identification

Flow
You create a duplicate identification batch on the Duplicate Identification work area to identify potential duplicates in the data
registry.
As part of the duplicate identification flow, you have the option of specifying a duplicate resolution request of an appropriate
type, such as merge, link or generic, to resolve the identified duplicates.
Selecting Duplicate Resolution Request Type: Critical

Choices
You can create a merge request or a link request to resolve potential duplicates. You decide the type of the duplicate
resolution request based on your business needs. The duplicate resolution request type determines how the records are
maintained after the resolution process is complete.
Note: The application also lets you create generic resolution requests. Specifying a generic resolution request
lets you make the merge or link decision later. You select a generic resolution request when you are not sure
whether you want to merge or link the records.
Merge Request
You create a merge duplicate resolution request to combine duplicate records into one new master record. The master
record is also called survivor record. After the merge request is completed, all duplicate records are deleted from the data
registry and you can update only the master record. The duplicate records that are deleted are also called victim records.
Link Request
You create a link request to associate the duplicate records. The linked records are treated as unique records in the data
registry, and have their own unique identifiers.
While creating the request, you define one of the records as the master record. The resolution process marks and links the
other records to the master record, and marks them as duplicates.
Processing Duplicate Resolution Requests: Worked

Example
If you selected Create Duplicate Resolution Request as the Automatic Processing Option, on the Create Duplicate
Identification Batch page, then generic duplicate resolution requests are created when the duplication identification process is
complete. You can also specify the creation of a generic resolution request while:
• Reviewing duplicate sets and creating single requests for each duplicate set on the Duplicate Identification Batch
details page.
344
• Creating a duplicate resolution request manually for confirmed duplicates on the Create Resolution Request UI page.
You can review these generic resolution requests in the Duplicate Resolution work area. On the Duplicate Resolution work
area, you can complete processing the generic duplicate resolution requests by submitting or rejecting them. You can also
select the duplicate resolution request type, merge or link, while submitting the generic request for resolution.
Note: The Process option on the Actions menu on the Duplicate Resolution work area is disabled if the status
of the duplicate resolution request is not new or if the duplicate resolution request type is link or merge. A
request dispatcher is run periodically for pending requests, and sets the status of pending requests to New. You
can also request your administrator to run the Run Request Dispatch Job from the Setup and Maintenance area
to set the status of the pending requests to new.
Processing a Duplicate Resolution Request involves the following tasks:
• Selecting the duplicate resolution request to process

• Selecting the duplicate resolution request type
• Managing the duplicate set
Note: Use the Purge Duplicate Resolution Data scheduled process to purge the duplicate resolution data
such as resolution logs and to delete duplicate resolution batches and requests. You can schedule this process
from the Scheduled Processes work area. You can access this work area as follows: Navigator > Tools >
Scheduled Processes.
Selecting the Duplicate Resolution Request

1. Navigate to the Duplicate Resolution work area.
2. Select a new generic duplicate resolution request.
Selecting Duplicate Resolution Request Type

1. Click the Process option on the Actions menu on the Duplicate Resolution work area.
2. On the Select Type of Request page, select the duplicate resolution request type as merge to combine duplicate
records, link to join duplicate records with the master record, or generic to select the duplicate resolution request
type later.
Managing the Duplicate Set

1. As appropriate, mark a record as nonduplicate, set as master a record other than the default master record, remove
records that you do not want to include in the resolution request.
2. Submit the duplicate set, as appropriate, as merge or link requests for resolution.
Related Topics
• Managing Duplicate Sets: Explained
345
Duplicate Resolution Request Status: Explained

A duplicate resolution request status provides detailed reasons for the rejection or failure of a duplicate resolution request.
You can use the status to correct data or system errors, and resubmit a resolution request with the updated data for
processing. For more information, see Configuring the Diagnostic Testing Framework for Normal Operation, Oracle Fusion
Applications Administrator's Guide 11g Release 1 (11.1.1.5).
The request status check uses the resolution request ID of the duplicated resolution request as an input parameter to check
the request status. The duplicate resolution request status can be Rejected, Error, Completed, or Pending. The check result
also includes the reasons for the status.
Merging Duplicate Records: Explained

This topic discusses the process to merge records for resolving duplicates.
A pending merge request may undergo some or all of the following processing stages before the merge is performed:
• First the survivorship rules are used to determine the master record for the merge.
• After this, the agreement rule check is performed to verify if the merge request is violating any veto conditions. If the
agreement rule check succeeds then a check is performed to determine if system mapping must be overridden or
not. If the agreement rule check fails, then the merge request is rejected and a rejection notification is sent to the
initiator.
• However, a rejected merge request can also be restored in which case a new merge request is created.
• If system mapping is overridden then the new mapping is stored before the merge request can be submitted. After
the merge request is submitted, the actual merge is performed.
• If the merge completes successfully then a completion notification is sent to the initiator and the submitter. If the
merge fails then an error notification is sent to the initiator and the submitter.
Note: Use the Purge Duplicate Resolution Data scheduled process to purge the duplicate resolution data
such as resolution logs and to delete duplicate resolution batches and requests. You can schedule this process
from the Scheduled Processes work area. You can access this work area as follows: Navigator > Tools >
Scheduled Processes.
346
The following figure illustrates the merge process flow.
Save in
Merge Mapping
Status? No
Request
Pending
Yes
Survivorship Passes Override Merge

Agreement Rule Yes New Merge
Rules Select System No Request
Check? Request Mapping?
Master Submitted
Yes
No
Merge Restore
Request Merge
Rejected Request?
Rejection Merge
Merge
Notification Sent to Request
Execution
the Initiator Ends in Error
Error Notification Merge

Sent to the Initiator Request
and the Submitter Completed
Completion
Notification Sent to
the Initiator and the
Submitter
Creating a Merge Request

A merge request is created as a result of one of the following:
• The batch duplicate identification process creates a duplicate resolution request automatically for each identified
duplicate set.
• A data steward or another user creates a merge request and submits the request through the Create Resolution
Request UI page or through the Enter Merge Request setup task.
347
• A data steward or another user creates a merge request for processing a generic resolution request on the Duplicate
Resolution work area.
• A bulk or file-based import process creates a merge request.
Note: You can also use the duplicate resolution request web service to create merge requests.
Status of Merge Requests

There are various statuses for a merge request.
The following table lists the possible statuses of a merge request.
Status Description
Pending All merge requests, and generic duplicate resolution requests, are created with the status as
Pending. The requests with pending status require review by a data steward.

New The request dispatcher is run periodically for pending requests, and sets status of pending requests
to New. When the request dispatcher is run, the application selects the master record and attributes
based on the survivorship rules, and runs the agreement rule check for the request.

Submitted This status indicates that the merge request has been submitted for processing. You can also
create merge requests with the status as Submitted to process the request without data steward
intervention.

Rejected This status indicates that the merge request is rejected by the data steward or by the process for
agreement rule violations. You can restore a rejected merge request.

Error This status indicates the request has failed because one or more records cannot be processed.

Completed This status indicates that the request has been processed successfully.

Selecting Master and Records to Merge

You can review new merge requests to:
• Select the master record
• Mark records as nonduplicates
• Remove records from the duplicate set to avoid merging them
The merge process selects the master record based on set master rules, if survivorship rules are active. However, you can
select to review and override system settings.
Deciding to Override System Mapping

You can override system mappings, during the merge request review, if you are not satisfied with system mapping of the
request. You can select the accounts, account addresses, and the relationships that should be merged, transferred, or
removed.
348
Reviewing Merge Request Related Notifications

The merge process sends the following related notifications:
• Rejection: This notification is sent to the merge request's initiator, such as a business user, salesperson, or
administrator. You can restore and resubmit a rejected merge request, by selecting a different master record or by
removing some records from the batch.
• Error: This notification is sent to the merge request's initiator and submitter. The notification indicates that the merge
request has errors and cannot be processed.
• Completion: This notification is sent to the initiator and the assignee of the merge process. The process merges
duplicate records and updates the record hierarchies. The notifications include information such as the master and
duplicate records.
After receiving the completion notification, the request initiator and assignee can:
• Verify if the updated hierarchies are correct in the Manage Hierarchies work area.
• Optionally, make the necessary edits to the updated hierarchies.
Merging Accounts and Contacts: Procedure

This topic explains how you can merge duplicate accounts or contacts into a single record.
You can merge duplicate accounts or contacts by either creating a request in the Enter Merge Request task or by merging
them in the Accounts or Contacts page of the simplified UI.
Note: You can merge a maximum of five accounts or contacts in a single merge request. You must create
multiple merge requests if you want to merge more than five accounts or contacts.
To merge duplicate accounts or contacts:
1. In the Accounts or Contacts page, search for the account or contact you want to merge.
2. Click Merge from Actions.
3. Select the duplicate accounts or contacts you want to merge.
4. Click Merge Selected.
The Request to Merge Accounts or Request to Merge Contacts page is displayed.

5. Enter a justification for the merge.
6. Click Submit.
You can configure merge request processing by using the ZCH_USER_MERGE_REQUESTS profile option from the Manage
Customer Hub Profile Options page. The profile option has two options:
• Allow Processing without Approval: The merge request is processed immediately without the need for Data Steward
Manager approval.
• Process Subject to Approval: The merge request is sent to the Data Steward Manager for review, and approval or
rejection.
349
Overriding System Mapping: Procedure

You can override system mapping for merge requests by manually modifying it. To manually modify system mapping, you
must select the master record and its associated attributes, and then specify the resolution for the child entity conflicts and
errors. You can resolve child entity conflicts and errors by merging, transferring, or removing the record attributes.
To override system mapping:
1. Navigate to the Duplicate Resolution work area as follows: Navigator > Customer Data Management >
Duplicate Resolution .
2. Select the duplicate resolution request for which you want to override system mappings and drill down through the
request ID to the Review Merge Request page.
Note: You can override system mappings only for those merge requests that are in New status. A
request dispatcher is run periodically for pending merge requests, and sets the status of pending
requests to New. You can also request your administrator to run the Run Request Dispatch Job from
the Setup and Maintenance area to set the status of the pending requests to new.
3. Click Override on the Review Merge Request page to view the Override System Mapping: Select Master
Record page.
4. In the duplicate set on the page, select the record that you want to make the master and click Set Master.
Optionally, you can also remove records from the duplicate set to prevent them from being merged. You can also
mark the removed record as a nonduplicate to exclude it from all merge requests.
5. Click Next to navigate to the Override System Mapping: Map Profile Attributes page.
6. Select a value from any of the duplicate records for each profile attribute to be retained in the master record.
In the profile attribute value choice list, you can hover over the value to see the attribute value's record. This helps
you associate the correct value with the master record. You can also manually enter a new value in the Final Value
column for an attribute.
7. Click Next to go to the Override System Mapping: Map Entities page. On this page, you can remove merge
entities, such as addresses, from the merge processes. You can also merge two or more entities into a single entity.
8. Click Next to view the Override System Mapping: Review page.
9. Review the mapping settings and either click Back to edit them further or click Submit to override the default
system mappings.
Automerge: Explained
The automerge functionality merges duplicate records without any approval or intervention from the data steward. Automatic
processing of merge requests is critical when processing large volumes of customer data as automerge can expedite the
resolution of duplicate records without manual review. Note that during automerge, the child entities of the duplicate records,
such as contact points, relationships, classifications, and cross references, become the child entities of the master record.
350
Understanding How Records are Selected for Automerge

Records are selected for automerge based on the following criteria:
• Match threshold: The match threshold is defined in the Match Configuration and determines if a record is included in
a duplicate set.
• Merge threshold: The merge threshold is defined by the ZCH_AUTO_MERGE_THRESHOLD profile option and
determines if the merge request for a duplicate set is processed automatically or if it must be reviewed manually.
Three possible outcomes for each record with regard to duplicate identification and merging are as follows:
• Low score below match threshold: The record is not included in duplicate set and in the merge request for that
duplicate set.
• Medium score above match threshold and below merge threshold: The record is included in duplicate set but merge
request for that duplicate set must be reviewed manually.
• High score above match threshold and above merge threshold: The record is included in duplicate set and merge
request is processed automatically.
The score for all the records in a duplicate set must be above the merge threshold for automated processing. If one record in
the duplicate set is below merge threshold, and the other records are above the merge threshold, the merge request must be
reviewed manually.
Note: When you merge two or more records with exactly same children information under phone, email, or
address the children information is merged and rolled up to the survivor record.
Configuring Automerge
Enabling Automerge involves several implementation steps that must be completed by an implementor using the following
tasks from the Customer Data Management offering in the Setup and Maintenance work area:
• Manage Customer Hub Profile Options: Use this task from the Customer Hub functional area to perform the
following implementation steps:
◦ Set Auto Merge Threshold profile option (ZCH_AUTO_MERGE_THRESHOLD) to the required value. This
profile option specifies the threshold for auto merge. Merge requests with lower scores need data steward
review. An exact match is 100.
◦ Review the Record Size Limit of Duplicate Set (ZCH_DI_MERGEREQ_REC_SIZE). This profile option
determines the maximum number of records in the duplicate set that can be merged automatically. By default,
the maximum number is set to 10 records.
◦ Set the Survivorship Enabled profile option (ZCH_ENABLE_SURVIVORSHIP) to Yes. This profile option
enables the survivorship rules to select the master record and retain the attributes during a merge operation.
• Manage Survivorship Rules: Use this task from the Customer Hub functional area to create Set Master
survivorship rules to choose the master record for merge requests created from the duplicate identification batch
and set the rule to active.
If there are no active Set Master rules or if the Set Master rules did not trigger, the merge request must be reviewed
manually, even if the ZCH_AUTO_MERGE_THRESHOLD profile option is set, the score for all records is above the
threshold value, and the number of records is below the record size limit.
351
Note: You can use the Set Attribute rules with Set Master rules to determine the Golden Master record.
For automerge, Set Master rule is mandatory.
• Manage Enterprise Data Quality Matching Configurations: Use this task from the Data Quality Foundation
functional area to perform the following implementation steps:
◦ Create an active Match Configuration in Manage Enterprise Data Quality Matching Configurations task or use
a predefined Match Configuration. Rebuild the keys if necessary.
◦ Enable EDQ Real Time and Batch Basic Match Server in Manage Server Configurations task.
Running Automerge
This task involves the following two steps:
1. Create a duplicate identification batch and select Create Merge Request as the Automatic Processing Option.
2. Perform the task Run Request Dispatch Job to disposition the duplicate resolution sets.
The Dispatch Job processes any resolution request in Pending or Submitted status. You can run this job in two modes:
• On demand: Run Request Dispatch Job > Submit
• Per a specific schedule: Do the following steps to set up a recurring job:
a. Click Advanced on the Run Request Dispatch Jobtask.
b. Click Schedule tab and select the Using a Schedule radio button.
c. Select the frequency you want and click Submit.
To see the list of dispatch jobs, and their statuses, navigate to Scheduled Processes under Tools.
Troubleshooting Automerge Issues

After you create your Duplicate Identification Batch, drill down into the completed batch to see the results. If duplicate sets
have been found, and automerge is enabled, resolution requests are automatically submitted for merge.
If the resolution request was not submitted automatically, you can drill down to the duplicate set and compare the score for
each record with the threshold in the ZCH_AUTO_MERGE_THRESHOLD profile option and the number of records with the
limit in the ZCH_DI_MERGEREQ_REC_SIZE profile option. If all scores are above the threshold and the number of records is
below the limit, verify that the following are true:
• Set Master rules are active and triggered to choose a master for the records in the duplicate set.
• ZCH_ENABLE_SURVIVORSHIP is set to yes.
Performing Automerge Using A SOAP Web Service:

Worked Example
This example demonstrates how to perform automerge or automatically merge confirmed potential duplicates based on
duplicate resolution requests created by invoking the DuplicateResolutionRequestService Web service using Oracle
Enterprise Manager (OEM). This example assumes that the survivor is a sales account and victims also include sales
352
accounts. Consequently, the merge behavior is to retain the survivor's sell-to address and merge the victim's sell-to
addresses to the survivor's sell-to address.
Performing automerge involves the following tasks:
• Enabling the automerge
• Accessing the DuplicateResolutionRequestService Web Service using OEM
• Creating an automatic merge request
• Finding out the merge result
Enable Automerge
1. Set the User Merge Requests profile option to Allow Processing Without Approval. When the User Merge
Requests profile option is set to this value, user merge requests are processed immediately without requiring any
approval from Data Steward.
2. Set the Merge Request Enabled (ZCA_MERGE_REQUEST) profile option to Yes.
3. Enable the User Merge Requests (ZCH_USER_MERGE_REQUESTS) profile option. This profile option controls the
behavior after the merge request is entered. See the section Customer Hub Profile Options.
Access the Web Service Using OEM

1. Sign in to Oracle Enterprise Manager.
2. From the Navigation menu, select Fusion Applications - Oracle Fusion Customer Relationship Management.
3. Select CrmCommonApp and then select CRMCommonServer_1.
4. Under the Web Services section, select DuplicateResolutionRequestService and click Test to launch the Web
Service Tester.
5. On the Request tab of the Test Web Service page, select Custom Policy security option and enter the Policy
URL syntax oracle/wss11_username_token_with_message_protection_client_policy and the username and
password for a user who has the ZCH_MASTER_DATA_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB role. For example,
in development environments, this could be MDM_ADMIN_V1.
Create A Merge Request

1. On the Test Web Service page, select the operation createMergeRequest from the Operation drop-down list and
enter the following payload:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:input="http://xmlns.oracle.com/apps/cdm/hubBase/publicModel/endUserMerge/types/">
<input:createMergeRequest xmlns="http://xmlns.oracle.com/apps/cdm/hubBase/publicModel/endUserMerge/">
<input:record>
<Master>HZ_PARTIES</Master>
<SourceSystemReference>100100001834094</SourceSystemReference>
<SourceSystem>SIEBEL</SourceSystem>
</input:record>
<input:record>
<NonMaster>HZ_PARTIES</NonMaster>
<SourceSystem>SIEBEL</SourceSystem>
</input:record>
</input:createMergeRequest>
</soap:Body>
353
</soap:Envelope>
2. Click Test Web Service.

3. Review the response to the operation createMergeRequest and make a note of the Duplicate Resolution Request ID,
which you can use in the operation getMergeResult to query the status of the Duplicate Resolution Request.
Running Automerge
Request your admin to perform the task Run Request Dispatch Job to disposition the duplicate resolution sets. The Dispatch
Job processes any resolution request in Pending or Submitted status. You can run this job in two modes:
On demand:
1. Navigate to the Run Request Dispatch Job task.

2. Click Submit.
Per a specific schedule:
1. Click Advanced on the Run Request Dispatch Job task.

2. Click Schedule tab and select the Using a Schedule radio button.
3. Select the frequency you want and click Submit.
Get Merge Result

1. On the Test Web Service page, select the operation getMergeResult from the Operation drop-down list and enter
the following payload:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:input="http://xmlns.oracle.com/apps/cdm/hubBase/publicModel/endUserMerge/types/">
<input:getMergeResult xmlns="http://xmlns.oracle.com/apps/cdm/hubBase/publicModel/endUserMerge/">
<input:record>
<Request>ZCH_DEDUP_HEADERS</Request>
<SourceSystem>FUSION</SourceSystem>
</input:record>
</input:getMergeResult>
</soap:Body>
</soap:Envelope>
2. Click Test Web Service.
Managing Rejected Merge Requests: Explained

Merge requests are rejected either manually by a data steward or automatically by the application if the agreement rules are
violated. You must login as a data steward to review or restore rejected merge requests in the Duplicate Resolution work
area.
354
As a data steward, you can:
• Review rejected requests: You review the rejected requests by drilling down through their request ID to the Review
Merge Request page to find out the rejection reasons.
• Restore rejected requests: After reviewing rejected requests, you can correct the rejection reason and then restore
rejected requests by clicking Restore on the Review Merge Request page. You can either select a different
master record or remove certain records from the merge request and submit the merge request for reprocessing.
Linking Duplicate Records: Explained

You use linking to associate two or more duplicate records while resolving duplicate records. This association only creates
a link between the records and does not affect the records. You use this association, which has a unique ID, to refer to the
member records of a link.
You can also create links for normal records even if they are not duplicate records. In a link, you designate one of the records
as the master and the others as duplicates. This helps users identify the master records for use in transactions.
During merge, duplicate records are combined into a single master record. However, some parties cannot be merged
because of functional or legal reasons. For example, for certain bank operations, you cannot merge duplicate records from
different business units or geographical regions. In these scenarios, we create a link between duplicate records instead of
merging them.
A link does not change the party and the associated child entities such as addresses, contact points, and relationships. A link
does not affect the transactional processing of the record. The link is a separate record in the data model, and has its own
registry ID.
Managing Links: Explained

You can manage links that are created either by duplicate resolution requests or by a data steward in the Manage Links page.
Data stewards create links to resolve duplicate parties by manually linking them without a duplicate resolution request on the
Create Link page.
You can access the managing links functionality by clicking on Manage Links on the Duplicate Resolution work area or by
clicking Linked Parties on the Organization, Person, or Groups work area.
Creating Links
To create links:
1. Navigate to the Manage Links page as follows: Navigator > Customer Data Management > Duplicate
Resolution > Tasks.
2. Select Create from the Actions menu.
3. In the Create Link page, enter the details about the link.
4. In the Link Members area, select and add two or more parties that you want to link by selecting Add from the
Actions menu. You must select one of the parties as the master.
355
Updating Links
To update links:
1. Navigate to the Manage Links page as follows: Navigator > Customer Data Management > Duplicate
Resolution > Tasks
2. Search for the link that you want to update. You can search by entering criteria such as link identification number,
status, description, or the names of member record. You must select the Master Party Type to search for links.
3. Select the link you want to update from the Search Results region and click Edit.
Optionally, you can also delete a link by selecting the link and clicking Delete.
4. In the Edit Link page, you can add link members, remove link members, and change the master record of the link.
Purging Duplicate Resolution Data: Explained

Legacy duplicate resolution data, such as resolution logs and legacy duplicate resolution batches and requests can clutter the
duplicate resolution work area as well as affect the performance of the application. Use the Purge Duplicate Resolution Data
scheduled process to purge the duplicate resolution data, such as resolution logs and to delete duplicate resolution batches
and requests. You can schedule this process from the Scheduled Processes work area. You can navigate to this work area
as follows: Navigator > Tools > Scheduled Processes.
This scheduled process lets you purge duplicate resolution data based on status and date range. You can specify the status
of the duplicate resolution requests to be purged, such as duplicate resolution requests in Completed, Error, or Rejected
status. You can also specify a date range by specifying the start and an end date to select duplicate resolution requests to be
purged. For more information, see: Submitting Scheduled Processes and Process Sets: Procedure
Related Topics
• Submitting Scheduled Processes and Process Sets: Procedure
• Process Sets: Explained
• Managing Scheduled Processes That You Submitted: Points to Consider
FAQs for Resolve Duplicate Customer Information

Can I include a member party in more than one link?
No. A member party can only participate in one link.
What happens if I include a record in a link?

Records participating in a link remain intact. Only an association is created between members of a link.
356
Can I create a link without a duplicate resolution request?

Yes. Use the managing link functionality to create a link directly. You can access the managing links functionality by clicking
on Manage Links on the Duplicate Resolution Work Area.
Can I include members of different party types in a link?

No. A link must contain members of the same party type.
Can I override system mapping for all types of duplicate resolution

request??
No. You can override system mapping only for duplicate resolution request of the type merge.
How can I access link information?

Use the managing links functionality to access link information. You can access the managing links functionality by clicking on
Manage Links on the Duplicate Resolution Work Area or by clicking Linked Parties in the Party Center.
How can I cancel a batch process?

You can cancel a batch process in the Scheduled Processes Overview page. You can navigate to this page as follows:
Navigator > Tools > Scheduled Processes. You must search for the batch process by its process ID, and then cancel the
batch process request.
Why am I unable to assign duplicate resolution requests?

You must be logged in as a Data Steward Manager to assign duplicate resolutions requests. Data Steward Managers assign
requests in the Duplicate Resolution work area.
Why am I unable to reject duplicate resolution requests?

You must be logged in as a Data Steward or a Data Steward Manager to reject a request. Data Steward Managers can reject
any request. Data Stewards can reject only those requests that are assigned to them.
357
Why am I unable to process a particular duplicate resolution request?

You can process duplicate resolution requests only if their status is New, and if the request type is not link or merge. In short,
you can only process generic duplicate resolution requests that are in New status.
358
Using Customer Data Management Managing Hierarchy Information
12 Managing Hierarchy Information
Manage Hierarchy Information

Hierarchies: Explained
A hierarchy captures the hierarchical relationships a party, such as a customer, has with other parties. This capability is
frequently used to capture your customer's corporate hierarchy and to show how headquarters, branches, subsidiaries, and
so on are related. It can be used to capture the hierarchy of any entity, such as a prospect, supplier, or partner, and not just
of customers.
Organizing customer data as hierarchies offers the following advantages:
• Enables you to understand and get a better view of your customer's organization.
• Enables you to better analyze customer-related data.
• Application modules using the hierarchy can use hierarchies to roll up transactions, and apply business rules.
You can leverage the hierarchy of your customers in many business processes. For example, the territory management
functionality uses customer hierarchy information to define account dimensions. Financial applications use customer hierarchy
information to process payments from one customer and apply them to another customer in the same hierarchy. The revenue
roll-up report uses customer hierarchy information to roll up revenue numbers from opportunities across all customers in a
hierarchy.
Oracle Cloud Applications have a common framework to manage various hierarchies called the Tree framework. The party
hierarchy uses this common framework.
You can create or modify hierarchies, using the Manage Hierarchies UI. You can access the Manage Hierarchies UI using one
of the following ways:
• Navigator > Customer Data Management > Hierarchies.
• Navigator > Setup and Maintenance > Tasks > Search > Search for the Manage Hierarchies task.
Creating Hierarchies
To create hierarchies:
1. Navigate to the Manage Hierarchies UI.
2. Click the Create option or button on the Actions menu. The Create Hierarchy: Enter Basic Information page
appears.
3. Complete the mandatory fields. You can use the following sample data:
◦ Hierarchy Name: Green Corp.
◦ Hierarchy Type: Customer Hierarchy
◦ Hierarchy Status: Active
◦ Effective Start Date: Enter appropriate date and time.

4. Click Next. The Create Hierarchy: Add Parties page appears.
5. Click the Add option or button on the Actions menu. The Add Tree Node pop-up appears.
359
6. Select one of the following as the Tree Node Type:
◦ Specific value
◦ Values from referenced hierarchy

7. Click Next. The Create Hierarchy: Review page appears. Verify the hierarchy information and click Back to make
any modifications.
8. Click Finish to complete creating the new hierarchy.
Editing Hierarchies
To edit hierarchies:
1. Navigate to the Manage Hierarchies UI.

2. Search and select the hierarchy you want to edit.
3. On the Actions menu, select one of the following options:
◦ Edit Hierarchy Version: Lets you make the changes to the hierarchy available immediately.
◦ Create New Version: Lets you make the changes to the hierarchy available at a later point in time.
4. Click Add or Remove option or button on the Actions menu as required to update the tree nodes.
5. Click Save and Close to complete editing the hierarchy.
Hierarchy Validation Rules: Explained

Hierarchy validation rules ensure that newly created or updated hierarchies are properly structured. These rules are run each
time you create or modify hierarchies.
All hierarchy types, including the predefined hierarchy types: Party Hierarchy, Dun and Bradstreet Hierarchy, and Customer
Hierarchy, enforce the following validation rules in active versions of customer hierarchies.
• A hierarchy can't contain a merged party.

• A hierarchy can contain parties with only certain party usages such as sales account, sales prospect, (internal) legal
entity, external legal entity, and buying customer. A buying customer is also considered as an external legal entity.
• If a party is an external legal entity, its parent can only be an external legal entity.
• If a party is an (internal) legal entity, its parent can only be a (internal) legal entity.
• If a party is not an external legal entity or (internal) legal entity, its parent can only be an eligible customer. For
example, a sales prospect, sales account, external legal entity, (internal) legal entity or a buying customer.
• A party can be present in only one active tree across all trees in the customer hierarchy.
• If there are sales accounts organized in a customer hierarchy, all nodes in that hierarchy must be sales accounts.
Sales accounts that appear within larger sales accounts are called in-between sales account nodes.
• A Named Sales Account can only have named sales accounts as ancestors.
Note: 'Named' is a sales account attribute stored in the Sales Account Profile entity.
These validation rules are enforced in the Hierarchy UI as much as possible while users select nodes to add to the hierarchy.
Also, a background audit job implements these rules to ensure that all hierarchies that do not pass the validation are marked
inactive.
360
Hierarchies and Hierarchy Versions: How They Fit Together

While creating hierarchies, you have to decide whether you want to create a new hierarchy or use a new version of an existing
hierarchy.
When to create a new hierarchy

You can create a new hierarchy when any of the following is true:
• You have a new customer, and a new hierarchy is required to represent the corporate structure of the new
customer.
• Your existing customer has changed the structure of its organization radically. It is quicker and more efficient to
create a new version rather than edit the existing one.
When to create a new hierarchy version

You can create a new version of a hierarchy when any of the following is true:
• You have minor changes to make to an existing version of a hierarchy, such as adding a new customer, or removing
or repositioning an existing customer in the hierarchy.
• You must make extensive changes to an active hierarchy, but want to render the changes active only when they are
all incorporated into the hierarchy. Then, create a new version of the hierarchy and set it to become active after a
reasonable window period. You can make all the required changes and have the new version ready for activation by
the scheduled date.
Hierarchy Edits and Hierarchy Versions: How They Work Together

While editing a hierarchy, you must decide whether you want to edit the existing version of the hierarchy or create a new one.
The changes you make to the existing version become active immediately, but the new versions of a hierarchy become active
only on the date on which the hierarchy becomes active.
Best Practices for Editing Hierarchies

When you edit the existing version of a hierarchy, the changes are saved instantly and are available to users even as you edit
them. However, you can't cancel any changes while editing existing hierarchy versions.
Two ways to deal with the changes while editing active hierarchies are:
• You can render hierarchies inactive before you edit them. Once you have made your changes, you can change their
status to active again.
Note: The hierarchy is not available to users while it is inactive.
• You can create a new hierarchy version and set it to be active the next day. Thus, while the existing version is active,
you can make your changes to the new version and activate it the next day.
361
Editing Hierarchies in Response to Merge

The merge process consolidates the duplicate parties and updates the hierarchies to which these parties belong. If the
updates to the hierarchies done by the merge process are not as expected, then edit the updated hierarchies in the Manage
Hierarchy Types task.
Related Topics
• Merging Duplicate Records: Explained
FAQs for Manage Hierarchy Information

How can I create a new hierarchy type?
You can create a new hierarchy type using the Manage Tree Structures task. Select Trading Community Model as the
application, an existing data source or new custom data source, and any labeling scheme you want. Next, enter the other
required details such as the appropriate usage of the new hierarchy type. Add the newly created hierarchy type under the
Party Hierarchy Type lookup to include the new hierarchy type in the lookups for hierarchy types.
Can I create multiple versions of the same hierarchy?

Yes. You must ensure that the date on which the new version is active doesn't overlap with the date of any existing active
version of the same hierarchy.
How can I respond to a merge completion notification if I don't have

the privileges to edit hierarchies?
If you don't have the privileges to edit hierarchies, reassign the merge completion notification to a user with the appropriate
privileges. For example, a sales person can reassign a merge completion notification to the Sales Administrator.
Why is the hierarchy type I created not visible in the Manage

Hierarchy UI?
When you create a hierarchy type, you must also update the list of hierarchy lookups. You cannot use the new hierarchy type,
unless you have updated the hierarchy lookup list.
You can update the list of hierarchy types using the Manage Hierarchy Lookups task. Select Party Hierarchy Type
(PARTY_HIERARCHY_TYPE) lookup type to edit. Add the new hierarchy type to the Party Hierarchy Type lookup type. After
updating the list of hierarchy type lookups and saving your changes, you can view the new hierarchy type under the list of
hierarchy types.
362
Why is an active hierarchy version that has been saved recently

sometimes set automatically to inactive?
By default, the newly edited hierarchy is saved as an auto-commit process, even before you save and close it. The application
triggers the tree flattening service and the audit job, when you save and close your changes. It doesn't wait for the job to
complete, and notifies you to revisit the version after the audit job is complete, to check the version status of the hierarchy.
If the audit job identifies any errors at the time of hierarchy validation, then the status of the hierarchy is set to Inactive.
However, the application does not notify you of this. You must revisit the hierarchy management interface and rectify issues in
the previously saved version, if the status is inactive.
363
364
Using Customer Data Management Managing Protected Information
13 Managing Protected Information
Working with Protected Information: Explained

Securing and protecting customer information against data breaches, data theft, or unauthorized access is an increasing
concern in any enterprise. To address this issue, Oracle Applications Cloud provides restricted access to information that is
considered private to an individual, also known as Personally Identifiable Information (PII).
PII is any information that uniquely identifies an individual, such as personal phone number, personal e-mail address, personal
address, citizenship number, or Social Security Number (SSN). PII data can be used to uniquely identify, contact, or locate an
individual, or can be used with other sources to uniquely identify a person. For example, a SSN uniquely and directly identifies
an individual, whereas a telephone area code identifies a set of people.
The attributes that are identified as PII are as follows:
• Home Address
• Home Phone Number
• Personal Email Address
• Taxpayer Identification Number (Social Security Number)
In Oracle Applications Cloud, access to the PII data is restricted to a set of job roles. If you need to work with PII data for
business purposes, then contact the IT security manager for the necessary privileges.
365
Using Customer Data Management Managing Protected Information
366
Using Customer Data Management Viewing Audit Histories
14 Viewing Audit Histories
Audit History: Explained

Using audit history you can view changes to the application data such as the business objects that were created, updated,
and deleted. To view the history or to create a report, you must have a role with the assigned privilege View Audit History
(FND_VIEW_AUDIT_HISTORY_PRIV). For appropriate assignment of roles and privileges, check with your security
administrator.
To open the Audit History work area, click Navigator > Audit Reports.
The default search displays a summary of the audit history in the search results table. It includes key data such as date, user,
product, event type, business object type, and description. For a detailed report, search again with modified search criteria.
You can export the report summary to Microsoft Excel.
The following table lists the search parameters used and the outcome of their selection in the detailed report.
Search Parameter Result of Selection
Business Object Type • Narrows the search results to that specific business object within the selected product.
• Enables the Show Attribute Details check box.
Note: This parameter is applicable

only for the business objects that
belong to Oracle Applications
Cloud.

Include Child Objects Displays all the child objects that were listed for that business object when audit was set up. For
example, a sales order object that contains several items as child objects.

Note: Displays the objects at the immediate parent-child level only. To view the children at
subsequent levels, select the child object as the business object type and search again.

Show Impersonator Displays the details of the impersonator who modified the objects during an impersonation session.

Show Attribute Details Enables the attribute list so that users can select either all attributes or a specific attribute to view
the changes. Based on the selection, the search results indicate whether the attribute is created,
updated or deleted, and the corresponding old and replaced values.

Show Additional Object Identifier Displays the instances (contexts) in which the business object was used. The context values identify
Columns the objects and the transactions in which they were used. Each context is unique and assigns a
unique description to the business object.

Note: The default report displays a standard set of columns that contain prominent details of the audit history.
To view additional details, you can change the display of columns.
367
Using Customer Data Management Viewing Audit Histories
Audit Event Types: Explained

Events trigger the audit process and the event details are stored in the audit table. Along with audit history, you can view
which events triggered the changes to the object data within a given period of time. However, for events to trigger the audit
process for the business objects, the objects must be enabled for auditing.
For Oracle Applications Cloud, transactional events trigger the audit process based on the create, update, and delete
operations. The attributes of the audited object data can be used in lookups and foreign keys to display values in the audit
history. Oracle Applications Cloud supports displaying the audited information as per the application's language settings.
For Oracle Fusion Middleware products, events such as failed sign in attempts are used as triggers. In absence of an audit
table, the information is stored in the sandbox and presented only in English.
Note: This topic focuses on the create, update, and delete event types available in Oracle Applications Cloud.
For details on events used in the Oracle Fusion Middleware products, refer to the Oracle Fusion Middleware
documentation.
• Create Operation - This event triggers audit activity whenever business object data is created and stored in the
database. The audit report displays the name of the created object, the name of the user who created the object,
and the time stamp.
• Update Operation - This event triggers audit activity whenever the existing business object data is updated. The
audit report displays both the old and updated values of the object, the name of the user who updated it, and the
time stamp.
• Delete Operation - This event triggers audit activity whenever the existing business object data is removed from the
database. The audit report displays the last value that the object attributes contained and the name of the user who
deleted the object.
368
Using Customer Data Management Using Customer Data Management with Other Cloud Services
15 Using Customer Data Management with

Other Cloud Services
Customer Data Management Cloud Integration

Approaches: Explained
You can integrate Customer Data Management Cloud with other cloud services using REST APIs and SOAP APIs to provide
address cleansing, duplicate identification, and duplicate resolution capabilities. Alternatively you can use the Integration
Cloud Service to develop work flows to integrate Customer Data Management with other cloud based or on-premise
applications.
Customer Data Management Cloud Integration Using REST APIs

Oracle Customer Data Management the (CDM) Cloud provides multiple public REST APIs that can be used to access data
stored in the CDM Cloud and construct integrations to other systems. The APIs include resources to Get, Post (create),
Patch (update), and Delete organizations (accounts) and persons (contacts). Also there are resources to identify and create
resolution request for duplicate parties.
For more information on public REST APIs, see REST API for Oracle Sales Cloud in the Related Topics section.
Customer Data Management Cloud Integration Using SOAP APIs

Oracle Customer Data Management (CDM) Cloud provides SOAP services to create and update organizations (accounts) and
persons (contacts). You can also use these services to identify and resolve duplicate parties.
For more information on SOAP APIs, see SOAP Web Services for Sales Cloud in the Related Topics section.
Customer Data Management Cloud Integration with Import and Export

Oracle Customer Data Management (CDM) Cloud lets you use File-Based Data Import and Export, Bulk Export, and Data
Import to import and export application data using text or XML files. You can also use import to create or update records in
Oracle Customer Data Management Cloud.
You can configure the import process to:
• Define deduplication within the data being loaded.

• Define deduplication of the data being loaded against the records that exist in the database.
You can also select a matching configuration to identify duplicates and specify the action to perform on the duplicate records
during the import process.
For more information on File-Based Data Import and Export, see Understanding File-Based Data Import and Export in the
Related Topics section.
369
Customer Data Management Cloud Integration Using the Integration Cloud

Service
You can use the Integration Cloud Service to leverage predefined integrations between Customer Data Management Cloud,
other cloud services, and on premise applications. For example, you can integrate Oracle Sale Cloud and Oracle Service
Cloud with Customer Data Management Cloud to provide the duplicate resolution capability. Using this capability, you can
merge an Oracle Sales Cloud account (organization) or contact (person) with an Oracle Service Cloud account (organization)
or contact (person).
For more information on the Integration Cloud Service, see Oracle Integration Cloud Service in the Related Topics section.
Customer Data Management Integrations for Accounts (Organization) and

Contacts (Persons)
The following table shows the possible integrations options for Oracle Customer Data Management Cloud:
CDM SOAP REST Data Import File-Based File-Based File-Based ICS Events Comments
Process Service Service (for account Data Import Data Import Data Export
(Batch Job) Receivables (Simplified
only) View)
Address No Address Yes No No Yes (Batch No File Export

Cleansing Cleansing is Summary is only
available by only). Does available
the REST not include from
service from child object Customer
Address such as Data
Verification duplicate Management
Cloud address and work area.
Service relationships.
only.

Duplicate No No Yes Yes No Yes (Batch No File Export

Identification Summary is only
only). Does available
not include from
child object Customer
such as Data
duplicate Management
address and work area.
relationships.

Duplicate Yes. SOAP Yes. Rest Yes No No Yes. Does Yes. Public Bulk Export
Resolution service can service can not include Resolution can be used
and create new create new child object Request for duplicate
Merging resolution resolution such as Updated. party details
requests request duplicate in the
and query and query address and Duplicate
existing existing relationships. Resolution.
resolution resolution See,
requests requests Implementing
but cannot but cannot CDM in the
update the update the Related
existing existing Topics
requests. requests. section.

370
CDM SOAP REST Data Import File-Based File-Based File-Based ICS Events Comments
Process Service Service (for account Data Import Data Import Data Export
(Batch Job) Receivables (Simplified
only) View)
Data No Data No No No Yes No

Enrichment enrichment
is available
by REST
service
from Oracle
Social Data
and Insight
Cloud
Service
only.

Related Topics
• REST API for Oracle Sales Cloud
• SOAP Web Services for Sales Cloud
• Understanding File-Based Data Import and Export
• Oracle Integration Cloud Service
• Implementing CDM
Merge Operation Process During Integration Cloud Service

Based Integration: Explained
Oracle Customer Data Management (CDM) Cloud acts as the customer master during Integration Cloud Service based
integration between different cloud services (also known as spoke systems). You can use CDM Cloud to cleanse,
consolidate, and share customer data across integrated cloud services, such as Oracle Sales Cloud and Oracle Service
cloud. This topic explains how the duplicate resolution capability of the Customer Data Management Cloud merges records
across integrated cloud services, for example, how it merges an Oracle Sales Cloud account or contact with an Oracle
Service Cloud account or contact.
Merge Operation Process for Point to Point Integration

In this integration scenario, the Customer Data Management Cloud provides the duplicate resolution capability to a single
spoke system.
371
The following diagram shows the before merge status of two contacts, Contact A and Contact B, of an account from Spoke
1.
Original System Reference A External Reference A

300012345634567862 300012345634567862
Contact A Contact A
First Name = John First Name = John
Middle Name = D. Middle Name = D.
Active Active
Original System Reference B External Reference B

300012987489378234 300012987489378234
Contact B Contact B
Middle Name = David Middle Name = David
Active Active
CDM Spoke 1
The following diagram illustrates how the two contacts, A and B, of the account from Spoke 1 are being merged in CDM
Cloud and how the Contact A emerges as the survivor and the Contact B becomes the victim.
372
Original System External Reference A

Reference A 300012345634567862
300012345634567862
Contact A Contact A
First Name = John Integration for Contact A stays intact First Name = John
Active Active
Original System External Reference B

Spoke 1 Identification for Contact B
Reference B 300012987489378234
300012987489378234
Contact B Contact B
First Name = John Integration should delete Contact B First Name = John
Inactive Active
CDM Spoke 1
The following diagram shows the after merge status of two contacts, A and B, of the account. Note that in Spoke 1 only
Contact A has survived and remained active after the merge.
373
Original System Reference A External Reference A

300012345634567862 300012345634567862
Contact A Contact A
First Name = John Integration for Contact A stays intact First Name = John
Active Active
Original System Reference B
300012987489378234
Contact B
First Name = John
Middle Name = David
Inactive
CDM Spoke1
Merge Operation Process for Publish and Subscribe Integration

In this integration scenario, the Customer Data Management Cloud provides the duplicate resolution capability to two or more
integrated cloud services or spoke systems. Duplicate data from spoke systems is consolidated in the CDM cloud and the
mastered data is published to the subscribing spoke systems.
374
The following diagram shows the before merge status of two contacts, A and B, of an account that exists both in Spoke 1
and Spoke 2.

Reference A 300012345634567862
300012345634567862
Contact A Contact A
Last Name = Doe Last Name = Doe
Active Active
Original System
External Reference B
Reference B
300012987489378234
300012987489378234
Contact B Contact B
Last Name = Doe Last Name = Doe
Active Active
CDM Spoke 1
External Reference A
300012345634567862
Contact A
First Name = John
Middle Name = D.
Last Name = Doe
Active External Reference B

300012987489378234
Contact B
First Name = John
Middle Name = David
Last Name = Doe
Active Spoke 2
The following diagram shows the after merge status of two contacts, A and B, of the account.
375

Reference A 300012345634567862
300012345634567862
Contact A
Contact A First Name = John
First Name = John Middle Name = D.
Middle Name = D. Last Name = Doe
Last Name = Doe
Active
Active
Original System External Reference B

Reference B 300012987489378234
300012987489378234
Contact B
Contact B First Name = John
First Name = John Middle Name = David
Middle Name = David Last Name = Doe
Last Name = Doe
Deleted
Inactive
Spoke 1
CDM
External Reference A
300012345634567862
Contact A
First Name = John
Middle Name = D.
Last Name = Doe
Active External Reference B

300012987489378234
Contact B
First Name = John
Middle Name = David
Last Name = Doe
Deleted
Spoke 2
Take note of the following:
• Data about Contacts A and B comes in the Customer Data Management cloud from both the spoke systems.
• The merge is taking place in the Customer Data Management cloud and any owned objects by the victims are
moved (re-parented) to survivor record in CDM.
• The mastered data is published to both the spoke systems and, consequently, Contact B is deleted from both the
spoke systems.
376
Oracle Customer Data Management Cloud Glossary
Glossary
external system or external application
A system or application that is external to and not part of Order Management. An order capture system that resides upstream
of Order Management is an example of an external system. A fulfillment application that resides downstream of Order
Management is an example of an external application.
interface table
A database table that stores data during data transfer between applications or from an external system or data file.
simulated cleansing
A mode for batch cleansing in which the results are available for preview before they are saved in the database.
377
Oracle Customer Data Management Cloud Glossary
378

Using Customer Data Management

Uploaded by

Copyright:

Available Formats

Using Customer Data Management

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Using Customer Data Management

Uploaded by

Copyright:

Available Formats

What are the main components of Customer Data Management?

What are the main components of Customer Data Management?

What is an interface table?

What is an interface table?

Oracle Customer Data Management

Release 13 (update 18C)

Release 13 (update 18C)

Author: Jesna Narayanan

1 About This Guide 1

2 Managing Customer Information 3

3 Importing Accounts and Contacts Using Import Management 11

4 Using File-Based Import 25

6 Using File-Based Export 309

7 Using Round-Trip Export-Import 315

8 Enriching Data 319

9 Cleansing Addresses 325

10 Identifying Duplicates 329

11 Resolving Duplicates 343

12 Managing Hierarchy Information 359

13 Managing Protected Information 365

14 Viewing Audit Histories 367

15 Using Customer Data Management with Other Cloud Services 369

Using Oracle Applications

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

> Greater than symbol separates elements in a navigation path.

Comments and Suggestions

1 About This Guide

Audience and Scope

2 Managing Customer Information

Customer Data Management Cloud: Overview

• Work areas to manage customer information

Customer Information Management

Data Quality Configurations

Data Quality Management During Import Process

• Define deduplication within the data being loaded.

Duplicate Identification, Duplicate Resolution, and Address Cleansing

Managing Organization Information: Explained

◦ Usage: Party of Interest.

◦ Name: Green Corp.

Managing Person Information: Explained

Managing Group Information: Explained

◦ Name: John and Family

Profile History Tracking: Explained

Enabling Profile History Tracking

Viewing Profile History Information

Usage Assignments: Explained

• Conditional usage assignments

Conditional Usage Assignments

Unconditional Usage Assignments

Managing Relationships: Explained

You must define the following for each relationship:

In the Edit page for an entity, you can:

Managing Source System References: Explained

Source System References in Oracle Applications Cloud

You can resolve these issues in Oracle Applications Cloud by:

Managing Source Systems

3 Importing Accounts and Contacts Using

About Import Management

Importing Data from a File