Oracle Fusion CRM File-Based Data Import Guide PDF

DRAFT
Oracle Fusion CRM File-Based Data Import Guide

11g Release 7 (11.1.7)
Part Number Draft Copy
June 2013
DRAFT
Oracle® Fusion CRM File-Based Data Import Guide
Part Number Draft Copy

E20374-03
Copyright © 2011-2013, Oracle and/or its affiliates. All rights reserved.
Author: Abhishek Sura, Brian Casey, Carmen Myrick, Charles Siegel, Gill Kenneweg, Jiri Weiss, Judy Wood, Lynn Raiser,
Peggy Larson, Rakesh Chaudhary, Ramana Murthy, Rick Stober, Rinku Mohapatra, Rob Cooper, Robyn King, Steve Safru,
Vijay Tiwary
Contributor: Carol Robinson, Damien Joly, David Hii, Deepika Rao, Gnanaprakesh Dasari, Hema Ravichandran, Jiang Li,
Kiran Basavaraju, Mansi Agarwal, Mladena Novakovic, Prasanna Jha, Raghu Sampathkrishna, Rama Gannabattula, Ramesh
Shankar, Ramin Modiri, Rory Delamere, Saradhi Boorela, Satheesh Challaveera, Sean Duffy, Shankar Iyer, Siddhartha Das,
Srikanth Mattegunta, Srinivasa Rangan, Sue Bose, Sundar Rajagopalan, Tamizhchelvi Balasubramanian, Tasman Tang, Varun
Gupta, Vibhor Gaur, Wai Pak, Wiebke Wiedemann, Ying Wang
This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform,
publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this
software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any
errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the
U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs
installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer
software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,
use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated
software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license
restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a risk of
personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates
disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under
license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the
AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of
The Open Group.
This software or hardware and documentation may provide access to or information on content, products and services from
third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind
with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for
any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
DRAFT
Contents
1 Overview
Getting Started with File-Based Import: Documentation Overview ..................................1-1
2 Configuring File-Based Data Import

File-Based Data Import: How It Works .............................................................................2-1
File-Based Data Import Tasks: How They Work Together ................................................ 2-3
3 File-Based Import Object and Target Objects

Understanding File-Based Data Import: Getting Started .................................................. 3-1
4 Define File-Based Data Import Activities

Import Activity Source File Options: Explained ............................................................... 4-1
Importing Attachments Using File-Based Data Import: Explained ................................... 4-2
Import Activity Import Options: Explained ..................................................................... 4-5
Import Activity Field Mapping: Explained .......................................................................4-8
File-Based Import Monitoring: Explained .........................................................................4-9
File Import Activity Statuses: Explained ........................................................................ 4-10
5 Importing Appointments
Importing Appointments Using File-Based Import: Explained .........................................5-1
Importing Notes Using File-Based Import: Explained ...................................................... 5-3
Appointment Import Objects Components: How They Work Together ............................ 5-5
6 Importing Attachments
Importing Attachments Using File-Based Data Import: Explained ................................... 6-1
7 Importing Click-to-Dial Agents

Importing Click-to-Dial Agents and Agent Connector Parameters Using File-Based
Import: Explained ................................................................................................................. 7-1
Click-to-Dial Agent and Agent Connector Parameter Components: How They Work
Together .................................................................................................................................7-3
8 Importing Consumers
DRAFT
Importing Consumers Using File-Based Import: Explained ............................................. 8-1
Consumer Import Objects: How They Work Together ......................................................8-3
Importing Person Profiles Using File-Based Import: Quick Start ......................................8-8
Importing Additional Party Identifiers: Quick Start ....................................................... 8-12
Importing Additional Party Names Using File-Based Import: Quick Start ..................... 8-17
Importing Classifications Using File-Based Import: Quick Start ..................................... 8-22
9 Importing Contacts
Importing Contacts Using File-Based Import: Explained ..................................................9-1
Contact Import Objects: How They Work Together ..........................................................9-3
Importing Person Profiles Using File-Based Import: Quick Start .................................... 9-12
Importing Additional Party Names Using File-Based Import: Quick Start ..................... 9-21
Importing Classifications Using File-Based Import: Quick Start ..................................... 9-26
Importing Contact Points and Contact Point Preferences Using File-Based Import: Quick
Start ..................................................................................................................................... 9-31
10 Importing Contracts
Importing Contracts Using File-Based Import: Explained .............................................. 10-1
Contract Import Objects: How They Work Together .......................................................10-3
11 Importing Country Structures

Importing Country Structures Using File-Based Import: Explained ............................... 11-1
Country Structure Import Objects: How They Work Together ........................................11-3
12 Importing Customers
Importing Customers Using File-Based Import: Explained ............................................ 12-1
Customer Import Objects: How They Work Together .....................................................12-3
Importing Organization Profiles Using File-Based Import: Quick Start ........................ 12-11
Importing Additional Party Identifiers: Quick Start ..................................................... 12-15
Importing Additional Party Names Using File-Based Import: Quick Start ................... 12-20
Importing Classifications Using File-Based Import: Quick Start ................................... 12-25
13 Importing Customer Hierarchies

Importing Customer Hierarchy Using File-Based Import: Explained ............................. 13-1
Customer Hierarchy Import Objects: How They Work Together .................................... 13-3
14 Importing Employee Resources

Importing Employee Resources Using File-Based Import: Explained ............................. 14-1
Employee Resource Import Objects: How They Work Together ..................................... 14-3
DRAFT
15 Importing Geographies
Importing Geographies Using File-Based Import: Explained ......................................... 15-1
Geography Import Object: How They Work Together .................................................... 15-3
Importing Geographies Using File-based Data Import: Worked Example ...................... 15-4
16 Importing Group Customers

Importing Group Customers Using File-Based Import: Explained ................................. 16-1
Group Customer Import Objects: How They Work Together ..........................................16-3
17 Importing Interactions
Importing Interactions Using File-Based Import: Explained ...........................................17-1
Interaction Import Objects: How They Work Together ................................................... 17-3
18 Importing Legal Entities

Importing Legal Entities Using File-Based Import: Explained ........................................ 18-1
Legal Entity Import Objects: How They Work Together ................................................. 18-3
Importing Organization Profiles Using File-Based Import: Quick Start ........................ 18-11
19 Importing Marketing Budgets

Importing Marketing Budgets Using File-Based Import: Explained ............................... 19-1
Marketing Budget Import ............................................................................................... 19-3
Note Import .................................................................................................................... 19-5
20 Importing Marketing Campaigns

Importing Marketing Campaigns Using File-Based Import: Explained .......................... 20-1
Campaign Import ........................................................................................................... 20-4
Note Import .................................................................................................................... 20-7
21 Importing Marketing Responses

Importing Marketing Responses Using File-Based Import: Explained ............................21-1
Response Import ............................................................................................................. 21-4
Note Import .................................................................................................................. 21-14
22 Importing Notes
DRAFT
Importing Notes Using File-Based Import: Explained .................................................... 22-1
23 Importing Partners
Importing Partners Using File-Based Import: Explained ................................................ 23-1
Partner Import ................................................................................................................ 23-4
Partner Contact Import ...................................................................................................23-6
Program Enrollments Import ........................................................................................ 23-12
Interaction Import .........................................................................................................23-14
Note Import .................................................................................................................. 23-18
24 Importing Product Groups

Importing Product Groups Using File-Based Import: Explained .................................... 24-1
Product Group Import Objects: How They Work Together .............................................24-3
Importing Product Groups : Worked Example ............................................................... 24-5
25 Importing Promotions
Importing Promotions Using File-Based Import: Explained ........................................... 25-1
Promotion Import Objects: How They Work Together ................................................... 25-3
Importing Promotions and Coupon Codes Using File-Based Import: Quick Start ...........25-4
26 Importing Resource Teams

Importing Resource Teams Using File-Based Import: Explained .................................... 26-1
Resource Team Import Objects: How They Work Together .............................................26-3
Importing Resource Teams and Resource Team Usages Using File-Based Import: Quick
Start ..................................................................................................................................... 26-5
27 Importing Sales Leads

Importing Sales Leads Using File-Based Import: Explained ........................................... 27-1
Lead Import .................................................................................................................... 27-4
Appointment Import .....................................................................................................27-20
Note Import .................................................................................................................. 27-28
28 Importing Sales Opportunities

Importing Sales Opportunities Using File-Based Import: Explained ...............................28-1
Opportunity Import ........................................................................................................ 28-4
Appointment Import .....................................................................................................28-26
Note Import .................................................................................................................. 28-34
29 Importing Tasks
DRAFT
Note Import .................................................................................................................... 29-1
DRAFT
DRAFT
Preface
This Preface introduces the guides, online help, and other information sources
available to help you more effectively use Oracle Fusion Applications.
Oracle Fusion Applications Help

You can access Oracle Fusion Applications Help for the current page, section,
activity, or task by clicking the help icon. The following figure depicts the help
icon.
You can add custom help files to replace or supplement the provided content.
Each release update includes new help content to ensure you have access to the
latest information. Patching does not affect your custom help content.
Oracle Fusion Applications Guides

Oracle Fusion Applications guides are a structured collection of the help
topics, examples, and FAQs from the help system packaged for easy download
and offline reference, and sequenced to facilitate learning. You can access the
guides from the Guides menu in the global area at the top of Oracle Fusion
Applications Help pages.
Guides are designed for specific audiences:
• User Guides address the tasks in one or more business processes. They are
intended for users who perform these tasks, and managers looking for an
overview of the business processes. They are organized by the business
process activities and tasks.
• Implementation Guides address the tasks required to set up an offering,
or selected features of an offering. They are intended for implementors.
They are organized to follow the task list sequence of the offerings, as
displayed within the Setup and Maintenance work area provided by
Oracle Fusion Functional Setup Manager.
• Concept Guides explain the key concepts and decisions for a specific
area of functionality. They are intended for decision makers, such as chief
financial officers, financial analysts, and implementation consultants. They
are organized by the logical flow of features and functions.
• Security Reference Manuals describe the predefined data that is included
in the security reference implementation for one offering. They are
DRAFT
intended for implementors, security administrators, and auditors. They are
organized by role.
These guides cover specific business processes and offerings. Common areas are
addressed in the guides listed in the following table.
Guide Intended Audience Purpose

Common User Guide All users Explains tasks performed by most
users.
Common Implementation Guide Implementors Explains tasks within the
Define Common Applications
Configuration task list, which is
included in all offerings.
Functional Setup Manager User Implementors Explains how to use Oracle
Guide Fusion Functional Setup Manager
to plan, manage, and track
your implementation projects,
migrate setup data, and validate
implementations.
Technical Guides System administrators, Explain how to install, patch,
application developers, administer, and customize Oracle
and technical members of Fusion Applications.
implementation teams
Note
Limited content applicable to
Oracle Cloud implementations.
For guides that are not available from the Guides menu, go to Oracle Technology
Network at http://www.oracle.com/technetwork/indexes/documentation.
Other Information Sources

My Oracle Support
Oracle customers have access to electronic support through My Oracle
Support. For information, visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=trs if you are hearing impaired.
Use the My Oracle Support Knowledge Browser to find documents for a product
area. You can search for release-specific information, such as patches, alerts,
white papers, and troubleshooting tips. Other services include health checks,
guided lifecycle advice, and direct contact with industry experts through the My
Oracle Support Community.
Oracle Enterprise Repository for Oracle Fusion Applications

Oracle Enterprise Repository for Oracle Fusion Applications provides details
on service-oriented architecture assets to help you manage the lifecycle of your
DRAFT
software from planning through implementation, testing, production, and
changes.
In Oracle Fusion Applications, you can use Oracle Enterprise Repository at

http://fusionappsoer.oracle.com for:
• Technical information about integrating with other applications, including

services, operations, composites, events, and integration tables. The
classification scheme shows the scenarios in which you use the assets, and
includes diagrams, schematics, and links to other technical documentation.
• Other technical information such as reusable components, policies,
architecture diagrams, and topology diagrams.
Note
The content of Oracle Enterprise Repository reflects the latest release of Oracle
Fusion Applications.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/us/corporate/
accessibility/index.html.
Comments and Suggestions

Your comments are important to us. We encourage you to send us feedback
about Oracle Fusion Applications Help and guides. Please send your
suggestions to oracle_fusion_applications_help_ww_grp@oracle.com. You can
use the Send Feedback to Oracle link in the footer of Oracle Fusion Applications
Help.
DRAFT
DRAFT
1
Overview
Getting Started with File-Based Import: Documentation Overview

This topic provides an overview of the types of help available for importing
legacy and other data into Oracle Fusion CRM using File-Based Data Import.
There are three main sources of information for import:
• Help topics about using the File-Based Data Import tool are linked to the
application pages and available by clicking the help icon.
These topics provide general information about import.
• Help topics on individual import objects are available by searching Oracle

Fusion Help Application.
Help topics provide information on the import objects, list the reference
guides you must consult for information on individual attributes, and
provide examples.
You can navigate to help by selecting Applications Help from the Help
menu at the top right of every application page.
There you can view individual help topics or download implementation

guides. In the implementation guides, you can find the import topics
grouped under the File-Based Data Import heading in the Define
Common CRM Configuration task group.
• Oracle Enterprise Repository, which contains reference guides with

detailed information on individual attributes.
You can search for the reference guides by name in the repository, which
is available at the following URL: https://fusionappsoer.oracle.com/oer/
index.jsp
To understand what attributes are available for import for each object, follow
these steps:
Overview 1-1
DRAFT
1. Start by searching help using the key word importing and the name of the
object you are importing.
For example, to get help on importing customers, enter importing

customers.
Depending on the complexity of the import, your search will return one or
more of the following help topic types:
Help Topic Title Description

Importing <import object name>: High-level topic that inform the user
Explained how each Oracle Fusion business
object is structured and explains its
relationship to the import object.
<import object name> Import Objects: This type of topic lists the target objects
How They Work Together associated with each import object
and provides the names of the Oracle
Enterprise Repository reference guides
that describe the attributes for those
target objects. Target objects are the
objects you select when you create the
import activity mapping.
Importing <import object name>: This type of topic provides an example
Conceptual Example of how to import the object without
detailed steps.
Importing <import object name>: This type of topic walks you through
Worked Example an example step by step.
2. Using the names of the reference guides listed in the <import object
name> Import Objects: How They Work Together topic, search for and
download the reference guides from the Oracle Enterprise Repository.
These guides include detailed descriptions of attributes and permitted

values.
1-2 Oracle Fusion CRM File-Based Data Import Guide

DRAFT
2
Configuring File-Based Data Import
File-Based Data Import: How It Works
The Define File-Based Data Import group of tasks relies on integration with
different Oracle Fusion Applications and architecture components, such as
interface tables and application base tables. This topic provides an overview of
these components to help you understand the import process and the different
import activity statuses.
The following figure provides an overview of the major application components

used when you import data from a file. These components include
• Import object
• Import mapping
• Import activity
• File repository
• Oracle Fusion CRM Application Composer
• Interface tables
• Oracle Fusion CRM base tables
Configuring File-Based Data Import 2-1

DRAFT
Import Objects, Import Mapping, and Import Activity

The import objects you select when you create an import activity are provided by
Oracle. They are managed using the Manage File Import Objects task.
When you create an import activity, you must specify a mapping of the fields in
your file to the attributes of the import object You can create the mapping either
while creating an import activity or separately using the Manage File Import
Mappings task. The mapping is stored and managed as a separate object.
File Repository
The text or XML data file you upload for import is stored in a file repository so
that it is available for import processing when you schedule an import activity.
Any attachments you upload are stored in the same repository.
Application Composer and Custom Extensions

When you create additional attributes for import using Oracle Fusion CRM
Application Composer, these extensions are stored in a separate repository and
are available when you create your mapping.
Interface Tables
The import activity populates the application interface tables with your data.
This is an intermediate holding area for your data that permits you to correct any
import errors. Oracle Fusion CRM application data is not changed at this point.

DRAFT
Oracle Fusion CRM Base Tables
The import activity loads your data into Oracle Fusion CRM base tables to
complete the import.
File-Based Data Import Tasks: How They Work Together

The tasks in the Define File-Based Data Import task group, available from the
Setup and Maintenance work area, enable you to import data from text or XML
files. This topic explains the role each task plays in the import process.
The following figure provides an overview of the File-Based Data Import group
of tasks and their relationships. Each task is explained in the sections that follow.
Manage File Import Activities Task

Use this task to import your data by creating import activities and monitoring
their progress. Creating an import activity involves completing the following
steps:
1. Set up the import options.
You select the object you are importing, specify the file format and
different import options, and upload the file with your data. The options
Configuring File-Based Data Import 2-3

DRAFT
that are available depend on the object you are importing. Some import
objects, for example, permit you to upload a ZIP or Java archive (JAR) file
of attachments that will be attached to the records in the application after
the data file import is complete.
2. Map the fields.
For this task, you create a mapping of the data in your file and the
attributes in the application. You can also reuse a mapping you have
created in past import activities or use the Manage File Import Mappings
task. Any mapping you create in an activity is automatically saved and
can be reused in subsequent imports and managed using the Manage File
Import Mappings task.
3. Schedule the import.
You can schedule to run the import at a time you specify or run it
immediately.
4. Review and activate the import activity.
You activate the import activity by clicking the Activate button.
Manage File Import Mappings Task

This task permits you to do the following:
• Manage existing mappings between the data in your import file and the
application attributes. For example, you can lock a mapping so that it
cannot be modified or edit the mapping to skip attributes during import.
• Create new mappings without a data file.
Creating a mapping using the Manage File Import Mappings task is

equivalent to creating it in the import activity, but you must enter any
import file column names manually. When you create a mapping as part
of the import activity, you upload the file, and the column headings in
your file are populated automatically.
Manage File Import Objects Task

This task lets you view all the import objects that have been created for you. All
of the objects you can import are already created for you, so you do not have to
create more import objects. Creating new objects is reserved for programmers.

DRAFT
3
File-Based Import Object and Target
Objects
Understanding File-Based Data Import: Getting Started

Using the Define File-Based Data Import group of tasks available from the
Setup and Maintenance work area, you can import application data from text
or XML files. Your import can be used to create or update records. The data you
can import ranges from geography reference data, used to validate addresses
in your application, to CRM transaction or legacy data, including customers,
accounts, opportunities, and leads. This topic provides an overview of what you
must understand to plan your import and prepare your import files. You must
read the help topics for each specific import object to learn how to import it.
This topic covers:
• What objects you can import
• Tasks involved in import
• Application business logic associated to the object you are importing
• How data is split into objects and what IDs you must include in your file
• What attributes are available for you to import and their validation
Objects You Can Import
Using file import, you can import a wide range of data listed in the following
table. Which of these objects are available to you for selection when you import
depends on the applications you have licensed and your security permissions.
Note
To obtain specific information on how to import each of these objects, search help
on the term import followed by the object name.
Import Object Description

Advertising Marketing Activity Specific instances of an advertising activity for a
marketing campaign.
Agreement Legacy service agreements for use in opportunities
and the Oracle Fusion Sales Prediction Engine.
Asset Legacy customer assets for use in opportunities and
the Oracle Fusion Sales Prediction Engine.
Campaign Marketing campaigns.
Campaign Members The contacts identified to receive the marketing
message for an instance of a marketing campaign
activity.
File-Based Import Object and Target Objects 3-1

Click-to-Dial Agents
DRAFT Click-to-Dial agents, including telemarketers,
salespersons, and customer service representatives,
who use the Click-to-Dial feature.
Click-to-Dial Agents Connector Parameters Agent connection parameters to access Click-to-Dial
functionality.
Consumer Individuals who are customers or prospects.
Contact Individuals who are contacts for an existing
customer or consumer, or contacts that do not yet
have an established association with a customer or a
consumer.
Contract Contracts header information for Oracle Fusion
Enterprise Contracts.
Country Structure Geographical structures for a country.
Customer Organizations who are sales accounts or prospects.
Customer Hierarchy Hierarchical structures for customers, such as
branches, subsidiaries, and paying relationships.
Customer Hierarchy Member Identifies the members of the hierarchical structures
for customers.
Employee Resource Use this object to import new users into your CRM
organization. You must create users as resources
to make it possible for them to participate in CRM
business processes.
Event Marketing Activity Specific instances of a marketing event for a
marketing campaign.
Geography The geographical data for a country.
Group Customer A group of organizations or persons, such as a
household or co-op, with whom you have a selling
relationship or a prospective selling relationship.
Incentive Compensation Transactions Sales compensation data.
Interaction Records of contacts or communications between
internal and external contacts.
Interaction Marketing Activity Specific instances of an outbound marketing
message for a marketing campaign.
Lead The interest or the potential interest of prospects or
existing customers in a product or service being sold.
Legal Entity Legal entities that have rights and responsibilities
under commercial law through the registration
with the country's appropriate authority. A legal
entity can represent your internal legal structure or
dependent authorities such as tax authorities.
Marketing Budget Business objects that are used to manage funds set
aside to fund partner incentives.
Note Notes associated with objects, such as leads,
customers, and opportunities.
Opportunity Pending sales stored in the application.
Opportunities are based on customer interest in a
product or service, and can be forecasted.

Partner
DRAFT Sales partners: independent companies that provide
sales and services on behalf of the vendor. In Oracle
Fusion Partner Relationship Management, a partner
must also be enrolled in a partner program and must
be active.
Partner Contact Contacts for a sales partner.
Product Group Product group hierarchies that represent the sales
catalog for marketing and sales.
Program Enrollments The enrollment of partners in partner programs,
selling programs that provide benefits and
incentives for partners.
Promotion Promotions and coupons which are used to track the
effectiveness of marketing campaigns.
Resource Team Temporary group of resources formed to complete
a business task. A resource team can contain both
individual resources and resource organizations. A
resource team cannot be hierarchically structured
and is not intended to implement an organization.
Response Responses to a marketing campaign.
Sales Account Resource Employee or partner resources assigned to a
customer.
Task Task that can be assigned to a resource for business
objects that support tasks.
Tasks Involved in Import

Importing data involves multiple tasks including the mapping of your data to
Oracle Fusion CRM and preparation of the data files to make them ready for
import.
The following figure lists the tasks you must perform to import data into Oracle
Fusion CRM:

You must:
DRAFT
• Perform a data comparison.
Compare the data you are importing with the attributes and valid values
expected by Oracle Fusion CRM.
• Customize Oracle Fusion CRM if required.
If you want to import attributes that do not have an equivalent in Oracle
Fusion CRM, then you may be able to add additional fields by using
Oracle Fusion CRM Application Composer. For some validated fields, you
can change the range of values available for import by editing the lookup
types where those values are stored.
• Prepare the source data.
This includes cleaning the data, removing duplicates, and splitting your
data into files that correspond to the available import objects. You must
ensure that the data meets the specifications required by the attributes in
Oracle Fusion CRM, and that the files include the appropriate unique IDs
required for import of the object.
• Import the data.
This involves creating import activities by using the Manage File
Import Activities task from the Setup and Maintenance work area and
creating maps between the columns in your files and the attributes in the
application.
• Validate the imported data
After the data is imported, you must validate the import by viewing the
data in the application.
Understanding Application Business Logic for the Object You Are Importing
You must understand how the data you want to import is used in Oracle
Fusion CRM by reviewing the user interfaces, data sheets, and application
documentation. If you are importing geography information, for example, you
must understand how that geography information is used to validate addresses
and what role it plays in sales territories. If you are importing customer data,
then you must understand that a sales account in Oracle Fusion applications
is a customer with a sell-to address. A customer without a sell-to address is
considered a prospect.
Tip
Some of the key business logic pertinent to import is described in the help topics
that you can review by searching help or implementation guides on the term
import followed by the object name.
Applications help is available as a selection in the Help menu on any application
page.
Understanding How Data Is Split into Objects and What IDs You Must Include
Before you import, you must also understand how the information you
import is represented in Oracle Fusion CRM application objects. Some objects

DRAFT
have a simple structure, but others include many child objects, which can be
shared with other objects. You must review documentation for each object to
understand how to import it.
Importing geography information that forms the basis of address validation, for
example, is relatively simple because the relationships between the geographical
data is determined within the data itself and the number of attributes that
determine an address is small.
Importing customer data is much more complex, requiring you to understand
how customer information is broken down into different objects and how those
objects must reference each other in your file.
Some legacy applications store information about customers and competitors
as separate entities. If a competitor becomes a customer, you have to copy
the information about the organization and create a customer record. In
Oracle Fusion, you indicate a competitor is now a customer. Similarly, contact
information is often part of the customer information so you must reenter the
information about that person each time he changes employers. In Oracle Fusion,
every individual and organization is a party in the model. If a contact moves
to work for a different customer, you simply indicate that the contact works for
someone else. You get to keep all the information you have about that contact.
This means that customer data is split into many objects that all have to reference
each other.
For example, customer contacts with phone numbers are made up of a hierarchy
of three objects: the customer, the contact, and the phone number. Each object
must have a unique ID and has to refer to the objects above it in the hierarchy
when you import.
The following figure provides an illustration with a simple example.
• Oracle is the customer at the top of the hierarchy with its unique
organization ID.
• The Oracle contact, John Tanaka, has its own unique ID and must also
reference the organization ID for Oracle.
• The contact's phone number, +1310-555-1212, must have its own ID and
reference both the contact and the customer.
Splitting data into multiple objects impacts the content of the import file:
• Your file must include many columns of IDs
If your legacy data does not already contain the required IDs, you can
create them manually in Microsoft Excel.

DRAFT
• Each row of your file must include the unique ID of the object you are
importing and the IDs of all the parent objects.
• You must import data in a specific order to make sure that a parent object
exists before you import the child object or you must include the parent
object information in the same file.
For example, if you want to import customer contacts, then you must
ensure that all the customer records already exist or that you include the
customer data in the same file.
Having multiple reusable objects also affects the way you create the mapping
between your file and the application attributes:
• When you create an import activity and map the attributes in your file to
the attributes in the application, you must select the child objects you are
importing before selecting the attributes.
• You will need to review separate documentation for each object to

find out which attributes are available for import and what values are
accepted.
Understanding What Attributes Are Available for Import and Their Validation
You must also understand what attributes you can import for each object, which
attributes are required and must be present in your file, and what attributes
values are permitted.
The list of attributes, their descriptions, and information about valid values
are provided in application help topics by import object and in documentation
available in the Oracle Enterprise Repository.
Note
The valid values that must be present in your import file are not necessarily the
same as those you see in the application. For example, values stored in lookup
types, require you to include the lookup code for each value rather than the
meaning displayed in the user interface.
To obtain the list of valid import values for validated fields, you must consult
the lookup types where those values are set. If the lookup type is extensible, then
you can edit it to match the values you are importing.
Some import objects permit you to add additional attributes using Oracle Fusion
CRM Application Composer. For these objects, you first create the additional
attributes in the composer and then create your mapping.

DRAFT
4
Define File-Based Data Import Activities
Import Activity Source File Options: Explained
The Import Activity consists of a step by step guided process to assist you with
creating an import activity for a given object.
This topic describes the source file options defined in the Import Activity that are
used by the import process to locate and parse the source file data.
Source File Data

Enter attribute details pertaining to the source file as follows:
Option Description
File Type Source file must be either Text or XML.
Data Type, Delimiter, and Header Row Included A Text file type can further be defined based on how
the data is delimited and if the source file is expected
to include a row of headings for each column.
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 outlines the options that are available to you when locating your
source file for import.
Define File-Based Data Import Activities 4-1

Option
DRAFT Description
File Selection Select from the following file selections:
• Specific file
Enables you to upload a specific source file

from a local file system, such as your desktop,
a URL address, or from a network path. A file
name is required for this option.
• Most recent file
Enables you to schedule repeating import

activities without having to select a new file
every time. This selection is only available
when you select Network from the Upload
From options.
You need to copy the new file to the specified

network path for repeating import activities.
You do not need to enter a file name for this
option and can only upload your source file
from a network path. The asterisk wildcard
is supported for multiple characters. The
question mark wildcard is supported for a
single character.
Upload From You can upload the source file from three locations:
• Desktop
• URL
• Network
If you select Desktop, a File Name field with an

associated Update button is displayed. Click Update
and browse to search for and select the file you want
to upload.
If you select URL, enter the address location

as in the following example format: http://
www.example.com/
If you select Network, enter the file name path as

in the following example format: \ComputerName
\SharedFolder\Resource\
Note
If you selected the Specific File as your file selection

option, then you will have to include the file name
for both URL and Network file path locations.
Importing Attachments Using File-Based Data Import: Explained

When you import data from a file using the Manage File Import Activities task,
you can include attachments for a subset of import objects, including leads,

DRAFT
opportunities, tasks, and other objects. This topic lists the objects that support
attachment import, explains how the import works, and provides guidelines.
Objects That Support Importing Attachments
A subset of import objects supports importing attachments. Some objects permit
you to import only one attachment for each record. A few objects permit the
import of multiple attachments.
The following table lists the import objects that support the import of
attachments. A subset of these supports the import of multiple attachments for
each record, as indicated in the following table.
Import Object Single or Multiple Attachments for Each Record

Assets Single
Interactions Single
Leads Multiple
Opportunities Single
Partners Single
Tasks Multiple
How You Import Attachments

To import attachment, you:
1. Create a ZIP or JAR file of the attachment files.
Note
The attachments can be organized in nested folders.
2. Add an additional column to the data file you are importing, and enter
the names of the attachment files. The header of this column must always
be: ATTACHMENT_FILE_NAME.
This reference column specifies which attachment file belongs to which
record. Other optional columns listed in the following table can be used to
upload other attachment information, such as a brief description.
The following table lists all of the available attributes with the header
names you must use.
Column Header Required or Optional Description

ATTACHMENT_FILE Required Captures the file names
_NAME in the ZIP file.
ATTACHMENT_FILE Optional Short description of the
_DESC file.
ATTACHMENT_FILE Optional File title. If you do not
_TITLE import a file title, then
the application uses the
file name as the title.
ATTACHMENT_CATEGORY
Optional Attachment category.
_NAME

DRAFT
3. Upload the ZIP or JAR file with the attachments when you create the file
import activity.
You do not map the attachment attributes. The application identifies the
special names in the column headers.
Note
You must upload one ZIP file of all the attachments. You cannot upload
attachments in multiple files or add additional attachments after you upload the
ZIP file the first time.
Importing Single Attachments

The following example illustrates the steps required for importing one
attachment for each record.
1. Create a ZIP or Java archive (JAR) file of all of your attachments, for
example: myfiles.zip:
• file_1.doc
• file_2.doc
• file_3.doc
• file_4.doc
Note
The numbers in the file names are provided for this example. They are not
required.
2. In the import file, add the additional columns to capture the attachment
information.
At a minimum, you must include a column with the header name:
ATTACHMENT_FILE_NAME to capture the attachment file names. You
must use this header name without variation so that the application will
identify it.
Unlike the other attributes in your import file, you do not map the
attachment columns to import objects and attributes when you create
an import activity. The application does the mapping automatically. The
mapping is based on the column name.
Your import file might contain data similar to that shown in the following
table.
LeadName StatusCD Score ATTACHMENT

_FILE _NAME
Lead 1 QUALIFIED 7 file_1.doc

Lead 4
DRAFT QUALIFIED 7 file_4.doc
3. When you create the import activity to import your file, you upload the
ZIP or JAR file from your desktop by cllicking the Browse button in the
Attachments region in the Import Options page.
The ZIP or JAR file is imported at the same time as the data file.
Note the following:
• If a record does not have an attachment, then leave the column value
blank.
• You can specify a single file to be the attachment for more than one or for
all records you are importing. For example, if you wanted the same file to
be attached to all the four leads, then your import file structure would be
like the data in the following table.
LeadName StatusCD Score ATTACHMENT_FILE

_NAME
Importing Multiple Attachments

For import objects that support multiple attachments, you repeat the column
header names.
Note
If you are adding any of the optional attachment columns, then you must repeat
all the columns in the same order.
Suppose you are importing four leads:
• Lead 1 includes attachments file_1.doc, file_2.doc, file_3.doc.
• Lead 2 includes the attachment file_4.doc.
• Lead 4 has no attachments.
Your data file might look like the data in the following table.
LeadName StatusCD ATTACHMENT ATTACHMENT ATTACHMENT

_FILE _NAME _FILE _NAME _FILE _NAME
Lead 1 QUALIFIED file_1.doc file_2.doc file_3.doc
Lead 2 QUALIFIED file_4.doc
Lead 4 QUALIFIED
Import Activity Import Options: Explained

This topic describes the import options available while creating import activities.

DRAFT
Source File Data Transformation
The following options are used to identify the formatting of source file data so
the data can be correctly interpreted and transformed by the import process:
Option Description
Decimal Separator The format of the fractional portion of numerical
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 you are importing and the application modules you
have implemented, you can select one or more of these options.
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

are available.
Allowable Error Count An error count above the threshold will stop the
import process for all records. If the error count
is below the threshold, records without errors are
imported. In either case, records with errors will be
reported in the Error and Exception files.
Validation errors include:
• Missing required values
• Values that exceed the attribute length
• Invalid identifiers and lookup codes
• Duplicates to existing records in the

destination tables based on the combination of
attributes selected for duplicate validation in
the predefined Import Mapping
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.

DRAFT
Customer Data Management Duplicates Using this option, which is available only if you have
licensed Oracle Fusion Trading Community Data
Quality, you can select different options for handling
duplicates when you are importing customers,
consumers, and legal entities either alone or as part
of another object.
The duplicates are determined using the following

matching configurations:
• Batch Location Basic Duplicate Identification
• Batch Person Basic Duplicate Identification
• Batch Organization Basic Duplicate

Identification
You can select from one of the following:
• Do Not Import Duplicate Records
If the main object of the Import Activity is a

consumer, customer, or a legal entity object,
rows that are matched to existing records will
not be imported. These duplicates records are
reported in the Exception and Error reports.
If the Customer Data Management objects

are components of another object and one or
more matches are found, the existing duplicate
records are evaluated to determine the most
recent record. The most recent record will
be associated with the main object being
imported.
For example, when importing a marketing

response object, the consumer object is also a
component of the response. If the consumer is
matched to an existing record, the consumer in
the interface tables is not imported. However,
the response object will import and the most
recent existing consumer record will be
associated to the response.
• Import Duplicate Records
The Customer Data Management objects will

be imported even if matched records exist.
• Import Duplicate Records and Create

Resolution Request
The Customer Data Management objects will

be imported even if matched records exist.
In addition, a duplicate resolution request is
created and displayed in the Customer Data
Management, Duplicate Resolution work area.

Duplicate Look Back Days
DRAFT This option applies only to the Lead import object.
Only existing leads created within the period
determined by the look back days value are
evaluated for duplicates based on the attributes
selected for duplicate validation in the predefined
import mapping. If a duplicate is found, the lead
will not be imported and the duplicate record will
be reported on the Exception report. Duplicate leads
are included in the calculation of the allowable error
count threshold.
Import Activity Field Mapping: Explained

After entering your import options, the second step of the import activity
process is to map fields in the source file to the corresponding target attributes.
This topic explains:
• Map Fields
• Saving the Import Mapping
• Constant Values
Map Fields
The Map Fields section can be subdivided into source file columns and target
attribute columns.
The source column header value is derived from one of the following:
• Predefined mapping, if one is selected
• The source file, if the Header Row Included option is selected in the first
step of the Import Activity definition (for Text file type only)
• Generic values of Column A, Column B, and so on, if the Header Row

Included option is not selected (for Text file type only)
• XML tagging structure (for XML file type only)
The following table outlines the source columns:
Source Column 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 did not select a
predefined mapping, the example values are taken
from the first data row in the source file selected in
the first step of the Import Activity definition.

Ignore
DRAFT Select this option if you do not want to import the
source file data in that column.
The following table outlines the target columns:
Target Column 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 selected a predefined mapping,
modifications made in the Import Activity to an unlocked mapping will update
and save to the predefined mapping. If the predefined mapping is locked, a
modified mapping will be saved as a new mapping. To specify a mapping name
for new mappings, select the Save As option from the Map Fields Actions menu.
Constant Values
Constant values provide a way to specify a value for a target attribute that all
imported objects will inherit. For example, if a source file does not contain a
column for business unit and all of the objects in the file belong to the same
business unit, enter a constant value for the object and business unit attribute.
File-Based Import Monitoring: Explained
You can monitor all file import activities that are currently scheduled to run,
have completed successfully, or failed with errors. For each import activity, you
can view the details pertaining to each underlying process and make necessary
updates for any failed records to import again.
You can view the list of import activities from the Manage Import Activities
page. Select the import activity that you want to monitor by clicking on the
hyperlink in the corresponding Status column. The View Import Status results
page is displayed which contains the following sections:
• Files Processed
• Import Processes
Files Processed
The Files Processed section displays a row for each source file that is processed.

DRAFT
The import processing details are summarized and displayed for each source file
and include the following:
File Processing Summary Information Description

Records Read From File The number of records read from the source file.
Format Errors The number of errors found when processing data
to insert into the interface tables from the source
file, Import Activity constants, and Import Object
value default values. View the error details in the
Exception and Error files attached to the process.
Load Errors The number of errors found when importing
data from the interface tables to the destination
application tables. View the error details in the
Exception and Error files attached to the process.
Successfully Loaded The number of import objects imported to the
application destination tables. If the import object is
made up of multiple components, each component
is counted as successfully loaded. Consequently the
Successfully Loaded count may be larger than the
Records Read From File count. View the successful
record details in the Log file attached to the process.
Attachments Once an Import Activity process has completed,
processing reports are included in the Attachments
column. The Log file includes the records that were
successfully imported plus the unique destination
application table identifiers for the objects. The
Exception file includes the records that were not
imported plus a reference to one of the errors for
each record that failed. The Error file includes all the
errors for each record that failed validation.
Import Processes
From the Import Processes section, you can view details pertaining to each
process involved in importing the objects in the source file. A listing of brief
messages provides information on processing steps within each underlying
process.
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
No status displayed for the activity The new import activity definition is not complete.

New
DRAFT
The import activity definition is complete, but the
activity is not yet scheduled to run.
Scheduled The import activity definition is complete and
scheduled to run later.
Interface table upload in progress The data file is being loaded into the interface tables.
Base table upload in progress The data file is being loaded from the interface tables
into the application tables.
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.

DRAFT

DRAFT
5
Importing Appointments
Importing Appointments Using File-Based Import: Explained

This topic explains how to prepare and import Appointment data from an
external data source into Oracle Fusion Applications using the File-Based Data
Import feature.
An appointment is a business object that is used to record scheduled meetings,
including participants and references to specific objects of interest such as a sales
lead or an opportunity.
Consider the following questions when importing your data:
• How does your legacy system or source system represent an appointment
compared to how Oracle Fusion Applications represent the same data?
• Do you have to configure values in Oracle Fusion Applications to map to
your data values?
• Do you have to customize Oracle Fusion Applications to capture
additional attributes that are critical to the way you do business?
• What import features are available for importing your business object?
• How do you verify your imported data?
Comparing Business Object Structures
You must understand how your appointment data corresponds with the data
in Oracle Fusion Applications in order to be able to map your legacy data to the
data needed by Oracle Fusion Applications. To start, you must understand how
Oracle Fusion Applications represent the structure of an appointment.
Importing Appointments 5-1

DRAFT
In Oracle Fusion Applications, a single appointment contains information such
as the date and time, subject, description, and reminder setting. Additionally, a
single appointment can include one or more internal and external participants
and one or more references to the objects of interest.
Import Object for Appointments
To facilitate the import of appointments, Oracle Fusion Applications

incorporates the structure of the appointment into a single import object:
Appointment.
Comparing Business Object Data
Each import object is a collection of attributes that helps to map your data to
the Oracle Fusion Applications data and to support one-to-many relationships
between the structural components that make up the appointment.
A good understanding of the attribute details of the import objects is critical

to preparing your import data. The reference guide files contain descriptions,
logic used to choose default values, and validation information for each of the
Oracle Fusion Applications attributes. The validation information includes
the navigation to the task where you can define values in Oracle Fusion
Applications. For example, if you have values in your data that correlate to a
choice list in Oracle Fusion Applications, then the validation information for
that attribute provides the task name in the Setup and Maintenance work area
where you can define your values. For additional information, including a list of
reference guide file names and locations that you need to complete this task, see
the following table.
Import Object Related Import Object Topic

Appointments Appointment Import Objects: How They Work
Together
Hint: You can use the keyword importing appointments to search for related
topics in Oracle Fusion Applications Help.
Extensible Attributes
Oracle Fusion Applications does not support extensible attributes for the
appointment object.
Importing Appointments Using File-Based Data Import
For the appointment business object, you must use the File-Based Data Import
feature. You prepare XML or text source data files in a form that is suitable
for file-based import. The file-based import process reads the data included
in your source file, populates the interface tables according to your mapping,
and imports the data into the application destination tables. The Define File-
Based Data Import Setup and Maintenance task list includes the tasks needed to
configure the import object, to create source-file mappings, and to schedule the
import activities.

DRAFT
To associate appointments with internal and external participants and business
objects, you must include in your source file the unique internal identifier for
each participant and business object. Therefore, the associated participants
and business objects must be entered or imported before submitting the
Appointment import activity. The File-Based Data Import Activity log file
typically includes the internal identifier for internal resources, external contacts,
and business objects imported using the File-Based Data Import feature.
Optionally, you can obtain the internal identifier for existing resources, contacts,
and business objects by using the Manage Bulk Data Export, Schedule Export
Processes Setup and Maintenance task.
Importing attachments is not supported for the appointment import object.
You must be assigned the Customer Relationship Management Application
Administrator to access and submit the import activities for appointments.
Verifying Your Imported Data
Oracle Fusion Applications provide File-Based Import activity reports, which

can be used to verify imported data. Participants can view their appointments
using the Fusion calendar. Users with access to the related business objects or
sales accounts can also view the associated appointments.
Importing Notes Using File-Based Import: Explained

This topic explains how to prepare and import Note data from an external data
source into Oracle Fusion Applications using the File-Based Data Import feature.
A note is a business object that is used to record notes, including references to
specific objects of interest such as a sales lead or an opportunity. You enter your
note information within the same user interface as the associated object or you
can import data to create new notes.
Consider the following when importing notes:
• How does your legacy system or source system represent the note
your data values?
You must understand how your note data corresponds with the data in Oracle
Fusion Applications in order to be able to map your legacy data to the data

DRAFT
needed by Oracle Fusion Applications. First, you must understand how Oracle
Fusion Applications represent the structure of the data for a note. In Oracle
Fusion Applications, the structure is a single level (non-hierarchical) and
contains information about the note such as the note type, text, author, and
associated object.
Import Object for the Notes
To facilitate the import of notes, Oracle Fusion Applications incorporates all the
data elements of the note into a single import object: Note.
Each import object has one or more target import objects. A target import object
is a collection of attributes that helps to map your data to the Oracle Fusion
Applications data. For the Note import object, all the attributes are contained in
the ImportNote target object.
You must compare the attributes that you want to import with the target object
attributes that are available and their valid values. To evaluate your source data
and Oracle Fusion Applications attributes for mapping and validation, you use
an Oracle Enterprise Repository reference guide, which is available for each
target import object. The reference guide file includes attribute descriptions,
default values, and validations performed by the import process. Review
the validation for each attribute to determine whether there are functional
prerequisites or setup tasks that are required.
To access the reference guide file for the Note's target import object, see the File-
Based Data Import assets in Oracle Enterprise Repository for Oracle Fusion
Applications (http://fusionappsoer.oracle.com). The following table lists the
reference guide file that is available from the Documentation tab for the Note
File-Based Data Import asset.
Import Object Target Import Object Reference Guide File Name

Note NoteImport ZMM_IMP_NOTES_Reference
If you need to extend the Oracle Fusion Applications object to import your
legacy or source data, you must use Oracle Fusion CRM Application Composer
to design your object model extensions and to generate the required artifacts
to register your extensions and make them available for importing. The
corresponding import object is updated with the extensible attributes, which
can then be mapped to your source file data. You can use the same source file
to import both extensible custom attributes and the standard import object
attributes.
Importing Notes Using File-Based Data Import
For the note 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

DRAFT
import. The file-based import process reads the data included in your source file,
populates the interface tables according to your mapping, and imports the data
into the application destination tables. The Define File-Based Data Import Setup
and Maintenance task list includes the tasks needed to configure the import
objects, to create source-file mappings, and to schedule the import activities.
To associate notes with business objects, you must include the unique internal
identifier for each business object in your source file. The File-Based Data Import
Activity log file typically includes the internal identifier for imported business
objects or you can obtain the internal identifier for an existing business object
by exporting it using the Manage Bulk Data Export, Schedule Export Processes
Setup and Maintenance task.

Administrator to access and submit the import activities for notes.

can be used to verify imported data. Users with access to the associated business
objects can view public notes and note authors can view all of their notes.
Appointment Import Objects Components: How They Work

Together
The File-Based Data Import feature supports importing appointment data

from an external data source into Oracle Fusion Applications. You use the
Appointment import object to submit a file-based import activity. This topic
describes the following about the Appointment import object:
• Target import object concepts
• Target objects for the Appointment import object
• Target import object attributes
• Target object attribute reference guide files
Target Import Object Concepts

The Appointment import object is used to import records containing
information about appointments representing scheduled meetings, including
participants and references to specific objects of interest such as a sales lead or an
opportunity.
The Appointment import object is split into separate target import objects for
organizing the individual attributes of the appointment and to manage the one-
to-many appointment structure. To map the source data in your import file to the

DRAFT
target attributes in Oracle Fusion Applications, you must understand how the
target objects are related and what attributes are included in each target object.
Appointment Target Import Objects

The target import objects in the Appointment import object are generally
grouped into information about the appointment, references to the internal and
external participants, and references to the objects of interest. The following
figure shows the target import objects included in the Appointment import
object, each represented by their familiar name and their formal target import
object name, shown in parentheses.
The AppointmentImport target object includes the attributes for the majority of
the information captured for an appointment, such as the date and time, subject,
description, and reminder setting. To import appointment participants, you
will use the ActivityAssigneeImport target object to associate internal resources
and the ActivityContactImport target object to associate external contacts.
When appointments pertain to specific business objects, such as a sales lead or
opportunity, the attributes pertaining to the association of the business objects
for the appointment are included in the AppointmentAssociationImport target
object.
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 File-Based Import Mapping
task, or you can define the mapping when you define the import activity using
the File-Based Import Activity task. Both tasks are available in the Setup and
Maintenance work area.
Target Import Object Attribute Resources

To access the reference guide files for the Appointment's target import objects,
see the File-Based Data Import assets in Oracle Enterprise Repository for Oracle
Fusion Applications (http://fusionappsoer.oracle.com).

DRAFT
The following table lists the reference guide files that are available from the
Documentation tab for the Appointment File-Based Data Import asset.
Target Import Object Description Reference Guide File Names

AppointmentImport Appointment information ZMM_ACTIVITIES_Reference
ActivityAssigneeImport Appointment internal resource ZMM_ACT_ASSIGNMENTS_Reference
participants
ActivityContactImport Appointment external contact ZMM_ACT_CONTACTS_Reference
participants

DRAFT

DRAFT
6
Importing Attachments
Importing Attachments Using File-Based Data Import: Explained

When you import data from a file using the Manage File Import Activities task,
you can include attachments for a subset of import objects, including leads,
opportunities, tasks, and other objects. This topic lists the objects that support
attachment import, explains how the import works, and provides guidelines.
Objects That Support Importing Attachments

A subset of import objects supports importing attachments. Some objects permit
you to import only one attachment for each record. A few objects permit the
import of multiple attachments.
The following table lists the import objects that support the import of
attachments. A subset of these supports the import of multiple attachments for
each record, as indicated in the following table.
Import Object Single or Multiple Attachments for Each Record

Assets Single
Interactions Single
Leads Multiple
Opportunities Single
Partners Single
Tasks Multiple
How You Import Attachments

To import attachment, you:
1. Create a ZIP or JAR file of the attachment files.
Note
Importing Attachments 6-1

DRAFT
The attachments can be organized in nested folders.
2. Add an additional column to the data file you are importing, and enter
the names of the attachment files. The header of this column must always
be: ATTACHMENT_FILE_NAME.
This reference column specifies which attachment file belongs to which
record. Other optional columns listed in the following table can be used to
upload other attachment information, such as a brief description.
The following table lists all of the available attributes with the header
names you must use.
Column Header Required or Optional Description

ATTACHMENT_FILE Required Captures the file names
_NAME in the ZIP file.
ATTACHMENT_FILE Optional Short description of the
_DESC file.
ATTACHMENT_FILE Optional File title. If you do not
_TITLE import a file title, then
the application uses the
file name as the title.
ATTACHMENT_CATEGORY
Optional Attachment category.
_NAME
3. Upload the ZIP or JAR file with the attachments when you create the file
import activity.
You do not map the attachment attributes. The application identifies the
special names in the column headers.
Note
You must upload one ZIP file of all the attachments. You cannot upload
attachments in multiple files or add additional attachments after you upload the
ZIP file the first time.
Importing Single Attachments

The following example illustrates the steps required for importing one
attachment for each record.
1. Create a ZIP or Java archive (JAR) file of all of your attachments, for
example: myfiles.zip:
• file_1.doc
• file_2.doc
• file_3.doc
• file_4.doc

Note
DRAFT
The numbers in the file names are provided for this example. They are not
required.
2. In the import file, add the additional columns to capture the attachment
information.
At a minimum, you must include a column with the header name:
ATTACHMENT_FILE_NAME to capture the attachment file names. You
must use this header name without variation so that the application will
identify it.
Unlike the other attributes in your import file, you do not map the
attachment columns to import objects and attributes when you create
an import activity. The application does the mapping automatically. The
mapping is based on the column name.
Your import file might contain data similar to that shown in the following
table.
LeadName StatusCD Score ATTACHMENT

_FILE _NAME
3. When you create the import activity to import your file, you upload the
ZIP or JAR file from your desktop by cllicking the Browse button in the
Attachments region in the Import Options page.
The ZIP or JAR file is imported at the same time as the data file.
Note the following:
• If a record does not have an attachment, then leave the column value
blank.
• You can specify a single file to be the attachment for more than one or for
all records you are importing. For example, if you wanted the same file to
be attached to all the four leads, then your import file structure would be
like the data in the following table.
LeadName StatusCD Score ATTACHMENT_FILE

_NAME
Importing Attachments 6-3

DRAFT
Importing Multiple Attachments
For import objects that support multiple attachments, you repeat the column
header names.
Note
If you are adding any of the optional attachment columns, then you must repeat
all the columns in the same order.
Suppose you are importing four leads:
• Lead 2 includes the attachment file_4.doc.
• Lead 4 has no attachments.
Your data file might look like the data in the following table.
LeadName StatusCD ATTACHMENT ATTACHMENT ATTACHMENT

_FILE _NAME _FILE _NAME _FILE _NAME
Lead 2 QUALIFIED file_4.doc
Lead 4 QUALIFIED

DRAFT
7
Importing Click-to-Dial Agents
Importing Click-to-Dial Agents and Agent Connector Parameters:

Explained
This topic explains how to prepare and import Click-to-Dial agent and agent
connector parameter data from an external data source into Oracle Fusion
Applications using the File-Based Data Import feature.
Click-to-Dial Agent is a business object that enables the users to sign in to click-
to-dial as an agent, establish the connection with their telephony system, then
make or receive calls using the Click-to-Dial toolbar.
• How does your source system represent the agent compared to how
Oracle Fusion Applications represent the same data?

your data values?


Before you import your legacy or source system agent information, you must
understand how the Agent data correlates to Oracle Fusion. This starts with an
understanding of how Oracle Fusion represents the structure of the data for a
Click-to-Dial agent and the agent connector parameters.
The Oracle Fusion click-to-dial object structure is essentially flat as opposed to a

deeply hierarchical structure. For any one agent there can be several connectors,
each with one-to-many agent parameters.
Importing Click-to-Dial Agents 7-1

DRAFT
The Click-to-Dial Agent contains the basic information about the agent and how
the agent connects to the telephone system, such as the connector name, the
Agent ID, Agent Group, Agent Password, a description, and the status of the
agent.
Each agent can have several connector parameters. This information is also
contained in the Click-to-Dial Agent import object. It includes such items as the
Connector Reference First and Last Name (the agent name), the connector name,
any agent connector parameters and their values, for example, the agent user ID
or extension.
Import Objects for the Enhanced Click-To-Dial Agent

To facilitate the import of the click-to-dial agent, Oracle Fusion has organized the
structure of the Agent information into import objects. The import object for the
agent and the agent connector parameters is the Click-to-Dial Agent.

Each import object is a collection of attributes that help to map your data to the
Oracle Fusion Applications data and support one-to-many relationships between
the structural components that make up the click-to-dial agent and connectors.


DRAFT
logic used to select default values, and validation information for each of the
choice list in Oracle Fusion Applications, 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, see Click-to-Dial Agent
and Agent Connector Parameter Components: How They Work Together.
Oracle Fusion Applications do not support extensible attributes for click-to-dial

objects. You can import only data for click-to-dial objects that already exist by
default in Oracle Fusion Applications.
Importing Click-to-Dial Agents and Agent Connector Parameters using File-

Based Data Import
For the click-to-dial 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 to configure the
import objects, create source-file mappings, and schedule the import activities.
You submit file-based import activities for each import object. When creating an
agent, you import the Agent object.
Administrator or Sales Administrator role to access and submit the import
activities for Click-to-Dial.
Oracle Fusion Applications provide File-Based Import activity reports,

which can be used to verify imported data. Users with either the Customer
Relationship Management Application Administrator or Sales Administrator
role can also navigate to the Click-to-Dial work area to view the imported agents
and agent connector parameters.
Click-to-Dial Agent and Agent Connector Parameter Components:

How They Work Together
You use the Click To Dial Agents import object to submit a file-based import
activity to import your agents and agent connector parameters. This topic
describes the following:

DRAFT
• Target objects for the Agent import object

The Click To Dial Agents import object is split into separate target import objects
for organizing the individual attributes of the agent and to manage the one-
to-many agent connector parameter structure. To map the source data in your
import file to the target attributes in Oracle Fusion Applications, you must
understand how the target objects are related and what attributes are included in
each target object. The Agent import object is used to import click-to-dial agents
and information to create or update associated connector parameters specific to
the agent.
Agent Target Import Object

The target import object in the Agent import object contains information
about agents and information about the agent parameters used by the named
connector. The agent connector parameters relate to an agent and connector
pairing. The following figure shows the target import objects included in the
Click-to-Dial Agent import object, each represented by their familiar name and
their formal target import object name, shown in parentheses.
Click-to-Dial Agent (ImpCommUser) is made up of the attributes that define that

agent, such as Agent ID, Agent Group, Agent First Name, Agent last name,
a Description, status and Connector name. The Agent Connector Parameter
import object (ImpConnUserParamValue) is associates with the Agent and consists
of the Connector Reference First and Last names (the agent names), Connector
Name, Connector User Parameter Name and Value, as well as the Connector
Record Language Code. User parameters can be designated, such as the agent's
extension (AcdExtension) and it's value (ImportTestAcdExtension) or the User ID,
(AcdUserid), and its value, (ImportTestAcdUser).
Target Import Objects Attributes


DRAFT
Target Import Objects Attributes Resources

To access the reference guide files for the agent and agent connector parameter
target import objects, see the File-Based Data Import assets in Oracle Enterprise
Repository for Oracle Fusion Applications (http://fusionappsoer.oracle.com).
Documentation tab for the Agent and Agent Connector Parameter File-Based
Data Import asset.
Target Import Objects (Seeded) Description Associated OER Attribute File

ImpCommUser Agent information, such as Agent MCT_IMP_COMM_USER_Reference
ID, Agent Group and so on.
ImpConnUserParamValue Agent connector parameters, such MCT_IMP_CONN_USR_PAR_VAL_Reference
as the users ID or extension.

DRAFT

DRAFT
8
Importing Consumers
Importing Consumers Using File-Based Import: Explained

This topic explains how to prepare and import consumer data from an external
data source into Oracle Fusion Applications, using the File-Based Data Import
feature. A consumer is a person who intends to purchase goods and services.
Within Oracle Fusion Applications, a person with a selling relationship is
referred to as a consumer. A consumer import object allows you to import
all information about a consumer, such as the consumer profile, consumer
address information, consumer contact point information, and consumer contact
preference information.
You must consider the following questions before importing consumer
information:
• How does your legacy or source system represent the consumer
information compared to how Oracle Fusion Applications represent the
same data?
• Do you have to configure values in Oracle Fusion Applications to map
them to your existing data values?
attributes that are critical to the way you do business?
• How do I verify my imported data?
You must understand how your consumer data corresponds with the data
in Oracle Fusion Applications to be able to map your legacy data to the data
Fusion Applications represent the structure of the data for a consumer.
The Oracle Fusion Applications consumer 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.
Importing Consumers 8-1

DRAFT
The following figure shows the consumer and its child entities.
The person profile contains basic information about the consumer, such as the
first name, last name, and party usage. For each consumer, you can have other
information, such as sell-to addresses, phone details, and sales account profile.
Note
All entities referring to contact information, such as primary phone or 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.

between the structural components that make up the consumer.
A good understanding of the import objects and attribute details is critical to
preparing your import data. Oracle Fusion Applications attribute details are
available for your reference in the Oracle Enterprise Repository. The reference
guide files contain descriptions, default values, and validations for each of the
Applications. For example, if you have values in your data that correspond to a
you can define your values.
If you have to extend the Oracle Fusion Applications import object to import
your legacy or source data, then you must use Oracle Fusion Applications CRM
Application Composer to design your object model extensions and to generate
the required artifacts to register your extensions and make them available for
importing. The corresponding import object is updated with the extensible
attributes, which can then be mapped to your source file data. You can use the
same source file to import both extensible custom attributes and the standard
import object attributes.
Importing Consumers Using File-Based Data Import
For the consumers business object, you must use the File-Based Data Import
imports the data into the application destination tables.

DRAFT
The Define File-Based Data Import Setup and Maintenance task list includes the
tasks required to configure the import objects, to create source-file mappings,
and to schedule the import activities. You submit file-based import activities for
each import object. When creating a consumer, you use the Consumer import
object. An import activity defines the instructions for processing the import
data, including the source file, import mapping from the source file to the Oracle
Fusion Applications object and attribute, and the import schedule.
When importing consumer information, you first import the basic person
profile information and then the child entities for the consumer. When
importing child entities, you must provide the parent reference information
for all parent levels for the entity. You must provide the PartyOrigSystem and
PartyOrigSystemReference of the consumer when importing contacts for the
consumer. PartyOrigSystem is the source system code that identifies the source
of the information being imported. PartyOrigSystemReference is unique for each
row of data within a single import, and is a combination of PartyOrigSystem
and a unique reference. For example, you first import basic profile details, such
as first name, last name, party type, and party usage. You then import other
information, such as additional names, e-mail, sell-to address, and primary
phone for the consumer.
page. You can verify your imported data by clicking the Status column for your
import activity. Alternatively, you can also navigate to the Customer Center
work area to view the consumer information that you have imported.
Consumer Import Objects: How They Work Together

The Consumer import object allows you to import consumers, their detailed
information, and contacts related to the consumer. This topic describes the
Consumer import object and introduces the following:
• Target objects for the Consumer import object
• Target import object attribute
Consumer Target Import Object Concepts
The Consumer import object imports consumer information, and is split into
separate target import objects for organizing the individual attributes of the
different aspects of the consumer. To map the source data in your import file to
the target attributes in Oracle Fusion Applications, you must understand how
the target objects are related and what attributes are included in each target
object.
The target import objects included in the Consumer import object are grouped
into information about the consumer. The person profile is the target import
object containing attributes to import information about the consumer. When
updating an existing consumer with additional information, you must provide
the parent reference information for the existing consumer.

DRAFT
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, PersonAddress, PrimaryPhone, Fax, Mobile, AdditionalName, e-
mail, SellToAddress, and SalesAccountProfile.

attributes that are available and their valid values. To evaluate your source
data and Oracle Fusion Applications attributes for mapping and validation,
you use an Oracle Enterprise Repository reference guide, which is available for
each target import object. The reference files contain descriptions, logic used to
choose default values, and validation information for each of the Oracle Fusion
Applications attributes. Review the validation for each attribute to determine
whether there are functional prerequisites or setup tasks that are required.
data and the combination of the target import object and target object attribute.
You can predefine and manage import mappings using the File-Based Import
Mapping task, or you can define the mapping when you define the import
activity using the File-Based Import Activity task. Both tasks are available in the
Setup and Maintenance work area.
Note
If any of the attributes that you want to import do not have an equivalent target
object attribute, then review the Oracle Fusion Applications CRM Application
Composer extensibility features for the consumer.

To access the reference guide files for the consumer target import objects, see the
File-Based Data Import assets in Oracle Enterprise Repository for Oracle Fusion
Applications (http://fusionappsoer.oracle.com).
Documentation tab for the Consumer File-Based Data Import asset.

PersonProfile Includes detailed person HZ_IMP_PARTIES_T_Reference
information such as person name,
relationship type, gender, and
marital status.
Sample attributes:
PersonFirstName,
PersonLastName, DateOfBirth,
PersonAcademicTitle, and
PlaceOfBirth.
Reference attributes:
PartyId, PartyOrigSystem,
PartyOrigSystemReference,
RelOrigSystem,
RelOrigSystemReference, and
RelationshipId.

SellToAddress
DRAFT
Includes consumer addresses and HZ_IMP_PARTYSITES_T_Reference
party sites information. If party
site usage of an address is not
defined, then the import process
sets it to Sell-To. In case there are
multiple addresses without party
site usage information, then the
import process designates one
of the addresses as the Sell-To
address.
Sample attributes include

Address1, Address2, City,
Country, County, State, and
PostalCode.
Reference attributes for

location: LocationOrigSystem,
LocationOrigSystemReference,
and LocationId1.
Reference attributes for party

sites: SiteOrigSystem and
SiteOrigSystemReference, and
PartysiteId1.

site use: SiteuseOrigSystem,
SiteuseOrigSystemRef, and
PartySiteUseId.
PrimaryPhone Indicates the primary phone HZ_IMP_CONTACTPTS_T_Reference
number of the consumer. If the
consumer has multiple phone
numbers, one of the phone
numbers is designated as the
primary phone number.
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
PhoneExtension, PhoneLineType,
and PhoneNumber.
CpOrigSystem and
CpOrigSystemReference.
Mobile Indicates the mobile phone HZ_IMP_CONTACTPTS_T_Reference
number of the consumer.
Sample attributes:
PhoneAreaCode,
PhoneCountryCode, and
PhoneNumber.
CpOrigSystem and

Fax
DRAFT
Indicates the fax number of the HZ_IMP_CONTACTPTS_T_Reference
consumer.
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
and PhoneNumber.
CpOrigSystem and
Email Indicates the e-mail of the HZ_IMP_CONTACTPTS_T_Reference
consumer.
Sample attributes:
ContactPointPurpose,
EmailAddress, and StartDate.
CpOrigSystem and
CpOrigSystemReference
InstantMessenger Indicates the instant messenger or HZ_IMP_CONTACTPTS_T_Reference
social networking information of a
consumer.
Sample attributes:
ContactPointPurpose, EndDate,
InstantMessagingAddress, and
InstantMessengerType.
CpOrigSystem and
SalesAccountProfile Includes detailed information ZCA_IMP_SALES_ACCOUNTS_Reference
about a 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.
Sample attributes:
AccountDirectorId, CreationDate,
NamedAccountFlag, and
AssgnExceptionFlag.
OwnerOrigSystem and
OwnerOrigSystemReference.

AdditionalName
DRAFT
Indicates alternative name of a HZ_IMP_ADDTNLPARTYNAMES_T_Reference
consumer.
Sample attributes:
NameId, PersonFirstName,
PersonLastName, and PersonTitle.
AdditionalNameOrigSystem and
AdditionalNameOrigSystemReference.
Classification Incudes classification information HZ_IMP_CLASSIFICS_T_Reference
for a consumer. Classification
allows you to categorize entities
such as parties, projects, tasks, and
orders as hierarchies.
Sample attributes:
ClassificationCode,
ClassificationCategory,
PrimaryFlag, and Rank.
Reference Attributes:
ClassificationOrigSystem and
ClassificationOrigSystemReference.
AdditionalIdentifier Includes detailed information HZ_IMP_ADDTNLPARTYIDS_T_Reference
about an additional identifier for a
consumer.
Sample attributes: IdentifierValue,

IdentifierType, Country, and
IssuingAuthorityName.
IdentifierValue,
AdditionaldentifierOrigSystem
and
AdditionalldentifierOrigSystemReference.
Relationship Includes information about HZ_IMP_RELSHIPS_T_Reference
a relationship between the
consumer and another entity, such
as an organization or a person.
Sample attributes:
RelationshipCode,
RelationshipType, and
DependentFlag.
RelationshipID, RelOrigSystem
and RelOrigSystemReference.

PrimaryPhoneContactPreference
DRAFT
Indicates the consumer's HZ_IMP_CONTACTPREFS_Reference
preference about being contacted
through phone.
Sample attributes:
ContactType, PreferenceCode,
PreferenceEndDate,
PreferenceStartDate, and
ReasonCode.
CpOrigSystem and
MobileContactPreference Indicates the consumer's HZ_IMP_CONTACTPREFS_Reference
through mobile phone.
Sample attributes:
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
FaxContactPreference Indicates the consumer's HZ_IMP_CONTACTPREFS_Reference
through fax.
Sample attributes:
PreferenceEndDate,
ReasonCode,
CpOrigSystem and
EmailContactPreference Indicates the consumer's HZ_IMP_CONTACTPREFS_Reference
Sample attributes:
PreferenceEndDate,
ReasonCode.
CpOrigSystem and

DRAFT
Importing Person Profiles Using File-Based Import: Quick Start
This topic describes a few key concepts and provides guidance to get you started
with importing person profiles.
It includes the following information:
• Person profiles overview
• An example of how to identify and associate records
• The minimum data required and the prerequisites steps
• How to use Oracle Enterprise Assets to evaluate optional attributes
• Additional tips
The following table lists the file-based import objects and target objects that you
can use to import person profiles.
Import Object Target Object

Consumer PersonProfile
Contact PersonProfile
Customer (Customer Contact) ContactPersonProfile
Group Customer (Customer Contact) ContactPersonProfile
Legal Entity (Legal Entity Contact) ContactPersonProfile
Employee Resource PersonProfile
Lead (Lead Consumer) PersonProfile
Lead (Lead Contact) ContactPersonProfile
Partner Contact PersonProfile
Response (Consumer Respondent) PersonProfile
Response (Response Contact) ContactPersonProfile
Person Profiles Overview

A person party profile enables you to import consumers, contacts, and group
members. For example, you can use person profiles to import consumer
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.
Identifying and Associating Records with Each Other
To import new person profiles or update existing person profiles using file
import, your source file must contain information about the person you want to
create or update. To update the person profile information for an existing record,
the import process must also be able to uniquely identify the record. To identify
the record, you will either provide 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 in your source file the source system code and the unique reference
value for the source system's record. Oracle Fusion stores a cross reference

DRAFT
between the source system information and Oracle's record ID. The import
process uses the source system and source system reference value combination 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 that is required to import person profile information depends on
the following:
• The purpose of the import. The data requirements are different when you
are creating a new person profile or updating an existing record.
• Identifying and associating records. 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 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.
The following table lists the minimum attributes required to import person
profile data based on the purpose of 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. A numbered footnote (n) indicates that
an option is provided. More information about the options is listed below the
table.
Person Profile Description Data Value Create Party Update Existing

Target Object Prerequisite and Add Person Person Profile
Attribute Profiles in the Records
Same Batch
ObjectKey or The Oracle Fusion Identify the Conditionally
PartyId record ID for the party ID value required. See
party (customer, by exporting the footnote [2].
consumer, contact, Party object using
group, or legal the Setup and
entity) to which Maintenance,
the person profile Manage Bulk Data
belongs. Export, Schedule
Export Processes
task.
PartyOrigSystem The code Predefine your Conditionally Conditionally
representing the source system required See required See
external source code as enabled footnote [1]. footnote [2].
system for the for Trading
party (customer, Community
consumer, contact, members, using
the person profile Manage Trading
belongs. Community Source
Systems task.

PartyOrigSystemReference
The reference
DRAFT Identify the Conditionally Conditionally
number or text reference value required See required See
representing the from your source footnote [1]. footnote [2].
source system system.
unique ID for the
party (customer,
consumer, contact,
group, or legal
entity) to which
the person profile
belongs.
PersonFirstName First name of a Required
person party.
PersonLastName Last name of a Required
person party.
[1] 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, provide
the original source system and source system reference values.
[2] To identify the existing person party, provide either the Oracle Fusion record
ID (PartyId) or both the source system code and reference values that you
provided when importing the party in a prior import batch (PartyOrigSystem
and PartyOrigSystemReference).
Using Oracle Enterprise Assets to Evaluate Optional Attributes
Information about all available attributes is included in a reference file located in

Oracle Enterprise Repository. Review the reference file to explore other person
profile attributes that are available to import and the possible prerequisite steps
for those attributes.
This in-depth reference file includes the following information:
• All person profile attributes available for import.
• The attribute descriptions. If the attribute is exposed in the user interface,
then the corresponding user interface display name is included with the
description.
• The data type, length, and validation logic. The validation information
includes 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 access the reference file for person profiles, follow these steps.
1. Using your browser, enter http://fusionappsoer.oracle.com. Sign in as a
user or a guest to Oracle Enterprise Repository.
2. Search for assets, using the following value for your Search String:
HZ_IMP_PARTIES_T.
3. Navigate to the results, and click the Documentation tab.
4. Select the HZ_IMP_PARTIES_T_Reference file. The File-Based Import
Target Object Name column indicates the target objects included in this
file. Review attributes for the ContactPersonProfile and PersonProfile
target objects.

DRAFT
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 in the top-right corner, and
selecting Applications Help.
• Importing person profiles
• Importing consumers
• Importing contacts
• Importing customers
• Importing groups
• Importing legal entities
• Importing employee resources
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.
Importing Additional Party Identifiers : Quick Start

with importing additional party identifiers.
• Additional identifiers overview
• Identifying and associating records
• The minimum data required and the prerequisite steps
• How to use Oracle Enterprise Repository Assets to evaluate optional
attributes
• Additional tips
can use to import additional identifiers.
Import Object Party Type Target Object

Customer Organization AdditionalIdentifier
Contact Person AdditionalIdentifier
Group Customer Group AdditionalIdentifier
Consumer Consumer AdditionalIdentifier
Additional Identifiers Overiview

An additional party identifier enables you to capture other identifiers for a
consumer, customer, contact, and group. For example, a person may have
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.

DRAFT
For example, an airline company may have an International Air Transport
Association code and the D-U-N-S number as identifiers
To add additional identifiers to a party or update existing additional identifiers
using file import, your source file must contain information about the
organization, person, or group party to which the additional identifier belongs.
If creating the party and the additional identifier in the same import activity,
group the party and additional identifier data together in your source file. The
import process is then able to first import the party, and then identify the party
record to 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 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.
The minimum that is required to import additional identifier information
depends on the following:
• The purpose of the import. The data requirements are different when
you are creating both the party and the 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 for identifying and
associating records.
values, and then include those values in your source file. The following tables
list the minimum attributes required to import party data based on the purpose
of 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.
A numbered footnote (n) indicates that an option is provided. More information
about the options is listed below the tables.
Organization Description Data Value Create Party Add Additional Update Existing
Profile, Prerequisite and Add Identifier to an Additional
Person Profile, Additional Existing Party Identifier

Group Profile
Target Object
DRAFT Identifier in the
Same Batch
Attribute
PartyId The Oracle Identify the Conditionally Conditionally
Fusion record party ID value required. required See
ID for the party by exporting footnote [2].
(customer, the Party See footnote [2].
consumer, object using
contact, group, Setup and
or legal entity) Maintenance,
to which the Manage Bulk
additional Data Export,
identifier Schedule
belongs. Export
Processes task.
PartyOrigSystem The code Identify the Conditionally Conditionally Conditionally
representing the source system required required required
source system code that was
for the party used when See footnote [1]. See footnote [2]. See footnote [2].
(customer, you imported
consumer, the party in
contact, group, a prior batch,
or legal entity) or identify the
to which the source system
additional code that you
identifier will use when
belongs. importing the
party in the
same batch as
this additional
party identifier.
The reference Identify the Conditionally Conditionally Conditionally
number or text reference required required required
representing value from
the source your source See footnote [1]. See footnote [2]. See footnote [2].
system unique system that
ID for the party was used when
additional reference that
identifier you will use
belongs. when importing
the party in the
same batch as
this additional
party identifier.
[2] To identify the existing party, provide either the Oracle Fusion record ID
(PartyId) or both the source system code and reference values that you provided
when importing the party in a prior import batch (PartyOrigSystem and
PartyOrigSystemReference).

DRAFT
The following tables list the minimum attributes required to import additional
identifier data based on the purpose of your import, any prerequisite setup or
tables.
Additional Description Data Value Create Party Add Additional Update Existing
Identifier Prerequisite and Add Identifier to an Additional
Target Object Additional Existing Party Identifiers
Attribute Identifier in the
Same Batch
AdditionalPartyIdOrigSystem
The code Predefine your Conditionally Conditionally Conditionally
representing source system required required required
the source code as enabled
system for for Trading See footnote [1]. See footnote [1]. See footnote [2].
the additional Community
identifier. members, using
the Setup and
Maintenance,
Manage
Trading
Community
Source Systems
task.
AdditionalPartyIdOrigSystemReference
The reference Identify or Conditionally Conditionally Conditionally
number or text generate required required required
representing the reference
source system values for each See footnote [1]. See footnote [1]. See footnote [2].
unique ID for additional
the additional party identifier
identifier. record. The
reference
value must
be unique for
all additional
party identifiers
for the source
system.
ObjectKey The Oracle Identify the Conditionally
Fusion record additional party required
ID for the identifier value
additional by exporting See footnote [2].
identifier. the Additional
Party identifier
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.

AdditionalPartyIdentifierType
The identifier
DRAFT
Identify Required Required
type to additional
categorize the identifier types
identifier. for the party
type using
the Setup and
Maintenance,
Manage
Additional
Identifier
Types task.
AdditionalPartyIdentifierValue
The additional Required Required
identifier value
for a party.
IssuingAuthorityName
The name of Required, if
the authority you are not
that issued providing the
the additional Issue Authority
identifier. Party ID.
IssuingAuthorityPartyId
The party ID Identify the Required, if
of the issuing party ID value you are not
authority. by exporting providing the
the Party Issue Authority
object using Party Name.
Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
[2] To identify the existing party additional identifier record, provide either
the Oracle Fusion record ID (ObjectKey) or both the source system code and
reference values that you provided when importing the party additional
identifier in a prior import batch (AdditionalPartyIdOrigSystem and
AdditionalPartyIdOrigSystemReference).
Information about all available attributes is included in a reference file located
in Oracle Enterprise Repository. Review the reference file to explore other
additional party identifier attributes that are available to import and the possible
prerequisite steps for those attributes.
• All additional identifier attributes available for import.
description.

DRAFT
To access the reference file for additional party identifiers, follow these steps.
user a guest to Oracle Enterprise Repository.
HZ_IMP_ADDTNLPARTYIDS_T.
4. Select the HZ_IMP_ADDTNLPARTYIDS_T_Reference file.
Additional Tips
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.
Importing Additional Party Names Using File-Based Import: Quick

Start
with importing additional party names. It includes the following information:
• Additional party names overview
• Additional tips
can use to import additional party names.

Consumer Person AdditionalName
Customer Organization AdditionalName
Customer Person (a contact for a customer) ContactAdditionalName
Group Customer Group AdditionalName
Legal Entity Organization AdditionalName

Legal Entity
DRAFT
Person (a contact for a legal entity) ContactAdditionalName
Additional Party Names Overview

An additional party name enables you to capture other names for a consumer,
customer, contact, group, and 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.
To add additional names to a party or update existing additional party name
assignments using file-based import, your source file must contain information
about the organization, person, or group 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.
If creating the party and the additional party name assignment in the same
import activity, group the party and additional party name data together in your
source file. The import process is then able to first import the party, and then
identify the party record to 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
Fusion record ID.
between the source system information and Oracle's record ID.
When the source of your data is not an external system, and you do not plan to
The minimum that is required to import additional name information depends
on the following:
you are creating both the party and the additional party name in the
same import batch, adding additional party names to an existing party, or
updating an additional party name record.
associate records.
• 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.
The following table lists the minimum attributes required to import additional
party name data based on the purpose of your import, any prerequisite setup or

DRAFT
table.
Organization Description Data Value Create Party Add Additional Update

Profile, Prerequisite and Add Party Name Additional
Person Profile, Additional Records to an Party Name
Group Profile Party Names in Existing Party Records
Target Object the Same Batch
Attribute
Fusion record party ID value required. See required. See
ID for the party by exporting footnote [2]. footnote [2].
(customer, the Party
contact, group, the Setup and
additional party Data Export,
name belongs. Schedule
Export
Processestask.
representing the source system required See required. See required. See
source system code that was footnote [1]. footnote [2]. footnote [2].
for the party used when
additional party code that you
name belongs. will use when
importing the
party in the
same batch as
this additional
party name.
number or text reference required See required. See required. See
representing value from footnote [1]. footnote [2]. footnote [2].
the source your source
additional party reference that
name belongs. you will use
when importing
the party in the
same batch as
this additional
party name.

DRAFT
tables.
Name Target Prerequisite and Add Name to an Additional
Object Additional Existing Party Names
Attribute Name in the
Same Batch
AdditionalNameOrigSystem
The code When you Conditionally Conditionally Conditionally
representing predefine your required. See required. See required. See
the source source system footnote [1]. footnote [1]. footnote [2].
system for code in the
the additional Setup and
name. Maintenance,
Manage
Trading
Community
Source Systems
task, select
the Enabled
for Trading
Community
Members check
box.
AdditionalNameOrigSystemReference
number or text generate required. See required. See required. See
representing the reference footnote [1]. footnote [1]. footnote [2].
source system values for each
unique ID for additional party
the additional name record.
name. The reference
value must be
unique for all
additional party
names for the
source system.

ObjectKey The Oracle
DRAFT
Identify the Conditionally
Fusion record additional party required. See
ID for the name ID value footnote [2].
additional by exporting
name. the Additional
Party Name
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
NameType The name type Review or Required Required
to categorize the define the
name. name types
for each party
type (person,
organization, or
group), using
the Setup and
Maintenance,
Manage
Additional
Name Types
task.
Name The additional Required Required
name value for
an organization
or group.
[2] To identify the existing additional party name record, provide either
the Oracle Fusion record ID (ObjectKey) or both the source system code
and reference values that you provided when importing the additional
party name in a prior import batch (AdditionalNameOrigSystem and
AdditionalNameOrigSystemReference).
additional party name attributes that are available to import and the possible
• All additional name attributes available for import.
description.

DRAFT
To access the reference file for additional party names, follow these steps.
HZ_IMP_ADDTNLPARTYNAMES_T.
4. Select the HZ_IMP_ADDTNLPARTYNAMES_T_Reference file.
Additional Tips
• Importing additional party names
• Importing additional names
Tip: The Name Type is defined for particular party types. For example, if you are
importing an organization profile, ensure that the name type definition allows
assignment to the Organization party type.
Importing Classifications Using File-Based Import: Quick Start

in importing classifications.
This topic includes the following information:
• Classifications overview
• Additional tips
can use to import classifications.

Customer Organization Classification
Legal Entity Organization Classification
Contact Person Classification
Consumer Organization Classification
Group Customer Group Classification

DRAFT
Classifications Overview
The classifications model allows you to categorize entities, such as organizations,
persons, and groups. 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. A party can then be classified as interested in
solar energy and conducts business in the automotive industry.
To add classifications to a party or update existing classification assignments
organization, person, or group 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 creating the party and the classification assignment in the same import activity,
group the party and classification data together in your source file. The import
process is then able to first import the party, and then identify the party record to
import the associated classifications.
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 a source system and
source system reference value combination or an Oracle Fusion record ID.
The minimum that is required to import classification information depends on
the following:
are creating both the party and the classification in the same import batch,
adding classifications to an existing party, or updating a classification
record.
associate records.
values, and then include those values in your source file. The following table
lists the minimum attributes required to import party data based on the purpose
about the options is listed below the table.

Organization Description
DRAFT
Data Value Create Party Add Update Existing
Profile, Prerequisite and Add Classification Classification
Person Profile, Classification to an Existing
Group Profile in the Same Party
Target Object Batch
Attribute
Fusion record party ID value required required
ID for the party by exporting
(customer, the Party See footnote [2] See footnote [2]
classification Data Export,
belongs. Schedule
Export
Processes task.
for the party used when See footnote [1]. See footnote [2] See footnote [2]
or legal entity) or identify
to which the the source
classification system code
belongs. you will use
when importing
the party
in the same
batch as this
classification.
the source your source See footnote [1]. See footnote [2] See footnote [2]
classification reference you
belongs. will use when
importing
the party
in the same
batch as this
classification.

DRAFT
The following tables list the minimum attributes required to import classification
data based on the purpose of 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. A numbered footnote (n) indicates that an option is
provided. More information about the options is listed below the tables.
Classification Description Data Value Create Party Add Update Existing

Target Object Prerequisite and Add Classification Classification
Attribute Classification to an Existing
in the Same Party
Batch
ClassificationOrigSystem
system for the for Trading See footnote [1]. See footnote [1]. See footnote [2].
classification. Community
members, using
the Setup and
Maintenance,
Manage
Trading
Community
Source Systems
task.
ClassificationOrigSystemReference
value for the generate required required required
classification reference values
record in the for each party See footnote [1]. See footnote [1]. See footnote [2].
external source classification
system. association
record. The
reference value
must be unique
for all party
classification
associations
for the source
system.
ObjectKey The Oracle Identify Conditionally
Fusion record the party required
ID for the party classification
classification association ID See footnote [2].
association. by exporting the
Classification
Assignment
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.

ClassificationCodeThe
DRAFT
The code should Required Required
classification be valid for the
code within classification
classification category.
category. Review the
classification
codes valid
for each
classification
category, using
the Manage
Classification
Categories,
Setup and
Maintenance
task.
ClassificationCategory
The Identify the Required Required
classification classification
category. category
name and
review entity
assignment
rules using
the Manage
Classification
Categories,
Setup and
Maintenance
task.
[2] To identify the existing party classification record, provide either the Oracle
Fusion record ID (ObjectKey) or both the source system code and reference
values that you provided when importing the party classification in a prior
import batch (ClassificationOrigSystem and ClassificationOrigSystemReference).

classification attributes that are available to import and the possible prerequisite
steps for those attributes.
• All classification attributes available for import.

description.

DRAFT
To access the reference file for classifications, follow these steps.
1. Using your browser, enter http://fusionappsoer.oracle.com.

2. Sign in as a user or a guest. Search assets using the following value for
your Search String: HZ_IMP_CLASSIFICS_T
4. Select the HZ_IMP_CLASSIFICS_T_Reference file.
Additional Tips
any Oracle Fusion Application page by clicking Help in the top, right corner, and
• Importing classification codes
Tip: Review the classification category entity assignment rules to verify if the
import object meets the assignment criteria.

DRAFT

DRAFT
9
Importing Contacts
Importing Contacts Using File-Based Import: Explained

This topic explains how to prepare and import contact data from an external data
A contact is a person party related to a customer, and the contact object contains
information that identifies the contact and offers the contact points of the contact.
Contact points can be geographical addresses, phone numbers, 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 customer
objects. You must consider the following questions before importing contact
information:
• How does your legacy system or source system represent the contact
your data values?

You must understand how your contact data corresponds with the data in Oracle
Fusion Applications represent the structure of the data for a contact.
In Oracle Fusion Applications, 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 following figure shows the contact object and its child entities.
Importing Contacts 9-1

DRAFT
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.
Import Objects for the Contact

To facilitate the import of contacts, Oracle Fusion Applications incorporate the
structure of the contact business object into import objects. The import object for
contacts is Contact.
between the structural components that make up the contact.

DRAFT

Contact Contact Import Objects: How They Work Together
Hint: You can use the keyword importing contacts to search for related topics in
Oracle Fusion Applications Help.
attributes.
Importing Contacts Using File-Based Data Import
For the Contact business object, you must use the File-Based Data Import feature.
into the application destination tables.
tasks needed to configure the import objects, to create source-file mappings, and
to schedule the import activities. You submit file-based import activities for each
import object. When creating a new contact, you import the Contact object. You
must be assigned the master Data Management Administrator job role to access
and submit the import activities for contacts.
can be used to verify imported data. You can also navigate to the Customer
Center work area to view the contact information that you have imported.
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

DRAFT
• Target import object attribute reference guide files
The Contact import object is used to import a contact's profile information, such
as first name, last name, address, and so on, and contact point information, such
as phone numbers, fax, e-mail IDs, and so on. The Contact import object is split
into separate target import objects for organizing the individual attributes of the
different aspects of the contact's profile and contact points. To map the source
data in your import file to the target attributes in Oracle Fusion Applications,
you must understand how the target objects are related and what attributes are
included in each target object.
Contact Target Import Objects
The target import objects included in the Contact import are grouped into
information about the contact and the contact's relationship with other parties.
The contact profile is the target import object containing attributes to import
information about the contact. You can have multiple contact relationships
associated with a contact. There are multiple target import objects that include
attributes to import contacts and their related information.
When updating an existing contact, you must provide the parent reference
information of the existing contact. When importing contact profile or
contact point information for a contact, you must provide relationship
reference information in addition to the parent reference. You must provide
this information because a contact can have multiple relationships with an
organization, such as employee or board member. When importing information
about a contact, you must refer to the specific relationship that you want
to import information for. For example, you must specify whether you
want to import information for John Smith the employee or John Smith the
board member. If you do not include the reference information for a contact
relationship, then the import process creates a new relationship.
To update the information for an existing contact or to create a contact record,
you can import contact profile information, addresses, and contact points.
The following target import objects are for creating and updating contact
information: PersonProfile, Fax, PrimaryPhone, Url, SalesAccountProfile,
Classification, AdditionalName, Relationship, and AdditionalIdentifier.
To update or create a contact point, use the following target import objects:
ContactRelationship, ContactJob, ContactAddress, 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.

DRAFT
Note
If any of the attributes that you want to import do not have an equivalent for
the target object attribute, then review the Oracle Fusion CRM Application
Composer Extensibility features for the marketing response.

To access the reference guide files for the response's target import objects, see the
Documentation tab for the Response File-Based Data Import asset.

PersonProfile Includes information that HZ_IMP_PARTIES_T_Reference
identifies a contact.
Sample attributes:
PersonFirstName,
PersonLastName, DateOfBirth,
gender, HouseholdIncome, and
PlaceOfBirth
PartyOrigSystem,
PartyOrigSystemReference, and
PartyId.
Fax Indicates the fax number of the HZ_IMP_CONTACTPTS_T_Reference
contact.
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
and PhoneNumber.
PartyOrigSystem,
PartyId.
FaxContactPreference Indicates the contact's preferences HZ_IMP_CONTACTPREFS_Reference
about being contacted through
Fax.
Sample attributes:
PreferenceEndDate,
ReasonCode.
PartyOrigSystem,
PartyId.

Phone
DRAFT
Indicates the phone number HZ_IMP_CONTACTPTS_T_Reference
of the contact. If the contact
has multiple phone numbers,
then the first phone number
is designated as the primary
phone number. The attributes of
PrimaryPhone, Fax, and URL are
the same. However, the value of
the attribute ContactPointType is
different for each of these contact
point related entities.
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
and PhoneNumber.
PartyOrigSystem,
PartyId.
PhoneContactPreference Indicates the contact's preferences HZ_IMP_CONTACTPREFS_Reference
about being contacted by phone.
Sample attributes:
PreferenceEndDate,
ReasonCode
PartyOrigSystem,
PartyId.
Email Indicates the e-mail of the contact. HZ_IMP_CONTACTPTS_T_Reference
Sample attributes:
PartyOrigSystem,
PartyId.
EmailContactPreference Indicates the contact's contact HZ_IMP_CONTACTPREFS_Reference
preferences about being contacted
through e-mail.
Sample attributes:
PreferenceEndDate,
ReasonCode
PartyOrigSystem,
PartyId.

InstantMessenger
DRAFT
Indicates the instant messenger HZ_IMP_CONTACTPTS_T_Reference
information of a contact.
Sample attributes:
PartyOrigSystem,
PartyId.
Mobile Indicates the mobile number of a HZ_IMP_CONTACTPTS_T_Reference
contact.
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneCountryCode,
PhoneNumber, and PrimaryFlag.
PartyOrigSystem,
PartyId.
MobileContactPreference Indicates the contact's preferences HZ_IMP_CONTACTPREFS_Reference
mobile phone.
Sample attributes:
PreferenceEndDate,
ReasonCode
PartyOrigSystem,
PartyId.
Classification Includes classification information HZ_IMP_CLASSIFICS_T_Reference
for a contact. Classification allows
you to categorize entities, such as
parties, projects, tasks, and orders
as hierarchies.
Sample attributes:
ClassificationCode,
PartyOrigSystem,
PartyId.

Address
DRAFT
Indicates the address of a contact. HZ_IMP_PARTYSITES_T_Reference
If the contact has multiple
addresses, then the first address
is designated as the primary
address.
Sample attributes: Address1,

Address2, City, Country, County,
State, and PostalCode.
PartyOrigSystem,
PartyId.
AddressContactPreference Indicates the contact's preferences HZ_IMP_CONTACTPREFS_Reference
about being contacted at the
primary address.
Sample attributes:
PreferenceEndDate,
ReasonCode
PartyOrigSystem,
PartyId.
AdditionalName Indicates the alternative name of a HZ_IMP_ADDTNLPARTYNAMES_T_Reference
contact.
Sample attributes: Additional

Name, Additional Name Type,
and GlobalPreferredNameFlag.
PartyOrigSystem,
PartyId.
AdditionalIdentifier Includes the basic information HZ_IMP_ADDTNLPARTYIDS_T_Reference
about an additional identifier for
the contact.

PartyOrigSystem,
PartyId.

ContactRelationship
DRAFT
Includes information about a HZ_IMP_RELSHIPS_T_Reference
relationship between the contact
and other parties.
Sample attributes:
RelationshipCode,
DependentFlag.
PartyOrigSystem,
PartyId.
ContactEmail Indicates the e-mail contact point HZ_IMP_CONTACTPTS_T_Reference
of the contact.
Sample attributes:
PartyOrigSystem,
PartyId.
ContactEmailContactPreference Indicates the contact's preferences HZ_IMP_CONTACTPREFS_Reference
about being contacted through the
e-mail contact point.
Sample attributes:
PreferenceEndDate,
ReasonCode
PartyOrigSystem,
PartyId.
ContactFax Indicates the number of the fax HZ_IMP_CONTACTPTS_T_Reference
contact point of the contact.
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneExtension.
PartyOrigSystem,
PartyId.

ContactFaxContactPreference
DRAFT
Indicates the contact's preference HZ_IMP_CONTACTPREFS_Reference
fax contact point.
Sample attributes:
PreferenceEndDate,
ReasonCode
PartyOrigSystem,
PartyId.
ContactInstantMessenger Captures information about HZ_IMP_CONTACTPTS_T_Reference
a contact's instant messenger
contact point.
Sample attributes:
PartyOrigSystem,
PartyId.
ContactMobile Indicates the number of a contact's HZ_IMP_CONTACTPTS_T_Reference
mobile contact point.
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneCountryCode,
PartyOrigSystem,
PartyId.
ContactMobileContactPreference Indicates the contact's preferences HZ_IMP_CONTACTPREFS_Reference
mobile phone contact point.
Sample attributes:
PreferenceEndDate,
ReasonCode
PartyOrigSystem,
PartyId.

ContactPhone
DRAFT
Indicates the number of the HZ_IMP_CONTACTPTS_T_Reference
contact's phone contact point. If
the contact has multiple phone
numbers, then the first phone
number is designated as the
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneCountryCode,
PartyOrigSystem,
PartyId.
ContactPhoneContactPreference Indicates the contact's preferences HZ_IMP_CONTACTPREFS_Reference
phone contact point.
Sample attributes:
PreferenceEndDate,
ReasonCode
PartyOrigSystem,
PartyId.
ContactAddress Indicates the address of a contact's HZ_IMP_PARTYSITES_T_Reference
address contact point. If the
contact has multiple addresses,
then the first address is designated
as the primary address.

PartyOrigSystem,
PartyId.

DRAFT
ContactAddressContactPreference Indicates the contact's preferences HZ_IMP_CONTACTPREFS_Reference
about being contacted at the
address contact point.
Sample attributes:
PreferenceEndDate,
ReasonCode
PartyOrigSystem,
PartyId.
ContactJob Includes the job information of a HZ_IMP_CONTACTS_T_Reference
contact.
Sample attributes: Comments,

ContactNumber, Department,
DepartmentCode, JobTitle, and
JobTitleCode.
PartyOrigSystem,
PartyId.

• Additional tips


Group Customer (Customer Contact)
DRAFT ContactPersonProfile
profiles.

the following:

DRAFT
associate records.
table.

Same Batch
Export Processes
task.
Systems task.
The reference Identify the Conditionally Conditionally
unique ID for the
party (customer,
consumer, contact,
group, or legal
entity) to which
the person profile
belongs.
person party.
PersonLastName Last name of a Required
person party.

DRAFT


description.

HZ_IMP_PARTIES_T.
target objects.
Additional Tips

DRAFT

attributes
• Additional tips



DRAFT
Fusion record ID.


Group Profile
Target Object
Same Batch
Attribute
identifier Schedule
belongs. Export
Processes task.
party in the
same batch as
this additional
party identifier.
the party in the
same batch as
this additional
party identifier.

DRAFT
tables.
Same Batch
the Setup and
Maintenance,
Manage
Trading
Community
Source Systems
task.
reference
value must
be unique for
all additional
party identifiers
for the source
system.
Party identifier
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.

The identifier
DRAFT
type to additional
type using
the Setup and
Maintenance,
Manage
Additional
Identifier
Types task.
identifier value
for a party.
Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
description.

DRAFT
Additional Tips

Start
• Additional tips


Legal Entity
DRAFT

file-based objects.
Fusion record ID.
on the following:
associate records.
file.

DRAFT
table.

Attribute
Export
Processestask.
importing the
party in the
same batch as
this additional
party name.
when importing
the party in the
same batch as
this additional
party name.

DRAFT
tables.
Same Batch
name. Maintenance,
Manage
Trading
Community
Source Systems
task, select
the Enabled
for Trading
Community
Members check
box.
name. The reference
value must be
unique for all
additional party
names for the
source system.

DRAFT
Party Name
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
name. name types
for each party
type (person,
organization, or
group), using
the Setup and
Maintenance,
Manage
Additional
Name Types
task.
name value for
an organization
or group.
description.

DRAFT
Additional Tips

• Additional tips


DRAFT
the following:
record.
associate records.

DRAFT
Target Object Batch
Attribute
belongs. Schedule
Export
Processes task.
when importing
the party
in the same
batch as this
classification.
importing
the party
in the same
batch as this
classification.

DRAFT

in the Same Party
Batch
members, using
the Setup and
Maintenance,
Manage
Trading
Community
Source Systems
task.
system. association
record. The
reference value
must be unique
for all party
classification
associations
for the source
system.
Classification
Assignment
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.

DRAFT
classification
codes valid
for each
classification
category, using
the Manage
Classification
Categories,
Setup and
Maintenance
task.
category. category
name and
review entity
assignment
rules using
the Manage
Classification
Categories,
Setup and
Maintenance
task.
description.

DRAFT
Additional Tips
Importing Contact Points and Contact Point Preferences Using File-

Based Import: Quick Start
with importing contact points and contact point preferences.
• Contact points and contact point preferences overview
• Additional Tips
can use to import contact points and contact point preferences.
Import Object Party Type Target Objects for Target Objects for
Importing Contacts Importing Contacts
Points
Contact Person Fax, Phone, Email, FaxContactPreference,
InstantMessenger, PhoneContactPreference,
Mobile, Address, URL EmailContactPreference,
and so on.
Consumer Person Fax, Phone, Email, FaxContactPreference,
and so on.

Customer
DRAFT
Organization Fax, PrimaryPhone, FaxContactPreference,
Email, InstantMessenger, PhoneContactPreference,
and so on.
Customer Person (a contact for a ContactFax, ContactFaxContactPreference,
customer) ContactPhone, ContactPhoneContactPreference,
ContactEmail, ContactEmailContactPreference,
ContactInstantMessenger, and so on.
ContactMobile,
ContactAddress
Group Customer Organization Fax, PrimaryPhone, FaxContactPreference,
and so on.
Legal Entity Organization Fax, PrimaryPhone, FaxContactPreference,
and so on.
Legal Entity Person (a contact for a ContactFax, ContactFaxContactPreference,
legal entity) ContactPhone, ContactPhoneContactPreference,
ContactMobile,
ContactAddress
Lead Lead Consumer Fax, Phone, Email, FaxContactPreference,
and so on.
Lead Lead Contact ContactFax, ContactFaxContactPreference,
ContactPhone, ContactPhoneContactPreference,
ContactMobile,
ContactAddress
Partner Partner Contact ContactFax, ContactFaxContactPreference,
ContactMobile,
ContactAddress
Response Consumer Respondent Fax, Phone, Email, FaxContactPreference,
and so on.
Response Response Contact ContactFax, ContactFaxContactPreference,
ContactMobile,
ContactAddress
Contact Points and 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.

DRAFT
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 points and contact point preferences to a party or update existing
contact point and contact point preference assignments using file-based import,
your source file must contain information about the organization, person, or
group party to which the contact point and contact point preference is being
assigned. You map your source file data to the organization, person, or group
profile target object, the relationship record that captures the interconnection
between the contact and the organization, the contact point, and the contact
point preference target object.
If creating the party and the contact point and contact point preference
assignment in the same import activity, group the party and contact point and
contact point preference data together in your source file. The import process is
then able to first import the party, and then identify the party record to import
the associated contact point and contact point preference.
To add a contact point and contact point preference to an existing party, or to

update an existing contact point and contact point preference record, 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
The import process uses the source system and source system reference value
combination 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.
The minimum that is required to import contact point and contact point
preference information depends on the following:
you are creating both the party and the contact point and contact point

DRAFT
preference in the same import batch, adding contact points and contact
point preferences to an existing party, or updating a contact point and
contact preference record.
associate records.
values, and then include those values in your source file
The following table lists the minimum attributes required to import contact point
and contact point preference data based on the purpose of 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. A numbered footnote
(n) indicates that an option is provided. More information about the options is
listed below the table.
Organization Description Data Value Create Party Add Contact Update Contact
Profile, Prerequisite and Add Point and Point and
Person Profile, Contact Contact Point Contact Point
Group Profile Points and Preference Preference
Target Object Contact Point Records to an Records
Attribute Preferences in Existing Party
the Same Batch
PartyId The Oracle Identify the Conditionally
Fusion record party ID value required. See
partner, or Maintenance,
legal entity) Manage Bulk
to which the Data Export,
contact point Schedule
and contact Export
point preference Processes task.
belongs.
representing the source system required See required See required See
partner, or or identify the
legal entity) source system
to which the code that you
contact point will use when
and contact importing the
point preference party in the
belongs. same batch as
this contact
point and
contact point
preference

The reference
DRAFT
Identify the Conditionally Conditionally Conditionally
number or text reference required See required See required See
partner, or or identify the
legal entity) source system
to which the reference that
contact point you will use
and contact when importing
point preference the party in
belongs. the same batch
as this contact
point and
contact point
preference.
The following tables list the minimum attributes required to import contact point
and contact point preference data based on the purpose of your import, any
prerequisite setup or manual steps needed to prepare your data, and the import
listed below the tables.
Contact Description Data Value Create Party Add Contact Update Contact
Point and Prerequisite and Add Point and Point and
Contact Point Contact Contact Point Contact Point
Preference Points and Preference Preference
Target Object Contact Point Records to an Records
Attribute Preferences in Existing Party
the Same Batch
ObjectKey The unique ID Identify the Conditionally
for the existing contact point ID required See
contact point for an existing footnote [2].
record in the contact point by
Oracle Fusion exporting the
destination contact point
table. object using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.

ContactPointType Type of the
DRAFTIdentify Required Required Required
contact point valid lookup
like phone, codes for the
email and so on. COMMUNICATION_TYPE
lookup using
the Setup and
Maintenance,
Manage
Contact Point
Lookups task.
CpOrigSystem A source system Identify the Conditionally Conditionally Conditionally
code that source system required. See required. See required. See
identifies the code that was footnote [1]. footnote [1]. footnote [2].
original source used when you
system of the imported the
contact point. contact point in
a prior batch,
or identify the
source system
code that you
will use when
importing the
contact point in
the same batch
as this contact
point contact
preference.
A source system Identify the Conditionally Conditionally Conditionally
reference that reference value required. See required. See required. See
identifies the from your footnote [1]. footnote [1]. footnote [2].
unique ID of the source system
contact point in that was used
your legacy or when you
external system. imported the
contact point in
a prior batch,
or identify the
source system
reference that
you will use
when importing
the contact
point in the
same batch as
this contact
point contact
preference.

RelOrigSystem The source
DRAFT
system original system required. See required. See required. See
code that code for footnote [1]. footnote [1]. footnote [2].
identifies the an existing
original source relationship
system of the by exporting
relationship relationships
whose object using the
is the contact Setup and
point. Maintenance,
Schedule
Export
Processes,
Manage Bulk
Data Export
task.
RelOrigSystemReference
The ID that Identify the Conditionally Conditionally Conditionally
identifies the original system required. See required. See required. See
relationship in reference for footnote [1]. footnote [1]. footnote [2].
your legacy or an existing
external system relationship
whose object by exporting
is the contact relationships
point. using the
Setup and
Maintenance,
Schedule
Export
Processes,
Manage Bulk
Data Export
task.
RelationshipId The unique ID Identify the ID Conditionally Conditionally Conditionally
for the existing of an existing required. See required. See required. See
relationship relationship footnote [1]. footnote [1]. footnote [2].
record in the by exporting
Oracle Fusion relationships
destination using the
table whose Setup and
object is the Maintenance,
contact point. Schedule
Export
Processes,
Manage Bulk
Data Export
task.
ContactType The method Identify the Required Required
of contact contact type
that should or from the
should not be Setup and
made, such as Maintenance,
call or mail. Manage
Trading
Community
Common
Lookups task.

PreferenceCode The lookup
DRAFT
Identify the Required Required
code that preference
represents the code from the
contact method Setup and
preference Maintenance,
phrase, such as Manage
Do Use, Opt In, Trading
Do not use. Community
Common
Lookups task.
PreferenceStartDate
The date from The contact Required Required
which a contact preference
preference is period start date
valid. must be less
than or equal
to the contact
preference
period end date.
RequestedBy The lookup Identify lookup Required Required
code that codes for
represents the source of
the source of the contact
the contact preference
preference request from
request, such the Setup and
as internal Maintenance,
requirement or Manage
requested by Trading
the party. Community
Common
Lookups task.
ContactPrefOrigSysRef
The source Conditionally
system required. See
reference that footnote [2].
identifies the
unique ID of
the contact
preference in
your legacy or
external system.
ContactPrefOrigSystem
A source Conditionally
system code required. See
that identifies footnote [2].
the original
source system
of the contact
preference.

ObjectKey The unique
DRAFT
Identify Conditionally
ID of the the contact required. See
existing contact preference footnote [2].
preference ID of an
record in the existing contact
Oracle Fusion preference
destination by exporting
table. the Contact
Preference
object using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
[2] To identify the existing contact point and contact point preference record,
provide either the Oracle Fusion record ID (ObjectKey) or both the source
system code and reference values that you provided when importing
the contact point and contact point preference in a prior import batch
(AdditionalPartyIdOrigSystem and AdditionalPartyIdOrigSystemReference).

Oracle Enterprise Repository. Review the reference file to explore other contact
point and contact point preferences attributes that are available to import and the
possible prerequisite steps for those attributes.
• All contact point and contact point preference attributes available for
import.

description.
To access the reference file for contact points, follow these steps.

HZ_IMP_CONTACTPTS_T.

DRAFT
4. Select the HZ_IMP_CONTACTPTS_T_Reference file.
To access the reference file for contact point preferences, follow these steps.

HZ_IMP_CONTACTPREFS_T.
4. Select the HZ_IMP_CONTACTPREFS_T_Reference file.
Additional Tips

DRAFT
10
Importing Contracts
Importing Contracts Using File-Based Import: Explained

This topic explains how to prepare and import contract data from an external
data source into Oracle Fusion Applications using the File-Based Data Import
feature.
A contract is a business object that is used to capture the terms and conditions
of a legally binding or valid agreement between two or more entities in which
there is an offer and an acceptance of that offer. To create new contracts in Oracle
Fusion Applications, you can either enter your contract information directly
using the Create Contracts task in the Contracts work area, or you can import
legacy contracts with no lines using the Enterprise Contracts: Define File-Based
Data Import tasks in the Setup and Maintenance work area.
Consider the following when importing data for this business object:
• How does your legacy system or source system represent the contract

your data values?
• Do you need to customize Oracle Fusion Applications to capture

additional attributes that are critical to the way you do your business?
You must understand how your contract data corresponds with the data in
Oracle Fusion Applications to be able to map your legacy data to the data
Fusion Applications represent the structure of the data for a contract.
Importing Contracts 10-1

DRAFT
In Oracle Fusion Applications, one table stores the contract definition or header
information and another table optionally stores line details for that contract.
A contract line is an entitlement to a specific valuable consideration with its
own terms and conditions, which businesses offer to their customers as part of
a contract. Zero, one, or many contract lines can be associated with any given
contract.
You can, however, import only contract header information and contract party
information. Contract header information contains basic information about the
contract, such as the name and number, start and end dates, type, amount, and
status.
Import Objects for the Contract
To facilitate the import of contracts, Oracle Fusion Applications incorporate the

structure of the contract into import objects. The import object for the contract is
Contract.
Each import object is a collection of attributes that help to map your data to
between the structural components that make up the contract.
to preparing your import data. Details about the Oracle Fusion Applications
attributes are available for your reference in the Oracle Enterprise Repository.
The reference guide files contain descriptions, logic used to choose default
values, and validation information for each of the Oracle Fusion Applications
attributes. The validation information includes the navigation to the task
where you can define values in Oracle Fusion Applications. For example, if
you have values in your data that correspond to a choice list in Oracle Fusion
Applications, then the validation information for that attribute provides the
task name in the Setup and Maintenance work area where you can define your
values. For additional information, including a list of reference guide file names
and locations that you need to complete this task, see the following table.

Contract Contract Import Objects: How They Work Together
Note
You can use the keywordimporting contracts to search for related topics in
If you need to extend the Oracle Fusion object to import your legacy or source
data, you must use Oracle Fusion CRM Application Composer to design your
object model extensions and to generate the required artifacts to register your
extensions and make them available for importing. The corresponding import
object is updated with the extensible attributes, which can then be mapped to
your source file data.

DRAFT
You can use the same source file to import both extensible custom attributes and
the standard import object attributes.
Importing Contracts Using File-Based Data Import
For the contract business object, you must use the File-Based Data Import
tasks needed to configure the import objects, to create source file mappings, and
import object. When creating a new contract, you import the Contract object.
To access and submit import activities for contracts, you must map your
predefined job roles to the Contract File Import Duty role or the Contract
Import from File Setup Duty role. Predefined job roles can be the generic one of
Customer Relationship Management Application Administrator or job roles that
are specific to Oracle Fusion Enterprise Contracts.
The Oracle Fusion Enterprise Contracts application has the following predefined
job roles:
• Customer Contract Manager
• Customer Contract Administrator
• Enterprise Contract Manager
• Enterprise Contract Administrator
• Supplier Contract Manager
• Supplier Contract Administrator
• Business Practices Director

can be used to verify imported data. Users with the Contract File Import Duty
role or the Contract Import from File Setup Duty role can also navigate to the
Contracts work area to view the imported contracts.
Contract Import Objects: How They Work Together

You use the Contract import object to import your contract by submitting a file-
based import activity. This topic describes the Contract import object.
This topic introduces the following:

DRAFT
• Target objects for the Contract import object
Target Import Objects

The Contract import object is used to import basic contract information and
party information about the customer or supplier, the contract organization
and party contacts. The Contract target import object organizes the individual
attributes of the contract and party information. To map the source data in your
understand the target object and the attributes that are included in the target
object.
Contract Target Import Objects

The target import object in the Contract import object usually contains
information about the contract and information about the parties. The party
information can include the customer or supplier organization, a person who is
a consumer or vendor and a person who is a contact of the customer or supplier.
The following figure shows the information that forms the Contract import
object and the familiar names for them.

DRAFT
A single contract includes specific information about the products that are
to be exchanged between the customer or supplier and the contract-owning
organization. The contract can include one or more goods or services. The
Contract target object includes the attributes that are required to import this
information.
If the customer or supplier is an organization and an existing party, then you can
associate the customer or supplier with the contract by using the Contract target
object.

Note
If any of the attributes you want to import do not have an equivalent target
object attribute, then review the Oracle Fusion CRM Application Composer
extensibility features for the contract.

To access the reference guide file for the contract target import object, see the
The following table lists the reference guide file that is available from the
Documentation tab for the Contract File-Based Data Import asset.
Target Import Object Description OER Attribute Reference File

Name
Contract Contract and party information OKC_IMP_CONTRACT_HEADERS_Reference

DRAFT

DRAFT
11
Importing Country Structures
Importing Country Structures Using File-Based Import: Explained

This topic explains how to prepare and import country structure data from an
Import feature. A country structure is a hierarchical grouping of geography
types for a country. For example, the geography structure for the United States
has the geography type of State at the top, followed by the County, then the City,
and finally the Postal Code.
You can use the country structure to set up the following:
• 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 country
structure compared to how Oracle Fusion Applications represent the same
data?

your data values?

You must understand how your country structure data corresponds with the
data in Oracle Fusion Applications in order to be able to map your legacy data
to the data needed by Oracle Fusion Applications. First, you must understand
Importing Country Structures 11-1

DRAFT
how Oracle Fusion Applications represent the structure of the data for a country
structure.
You must import a separate country structure import object for each country.
Each of these import objects must contain the geography types that are used in
the country's structure, organized in a hierarchy using geography level numbers.
For example, if you are importing the country structure of Australia, the country
structure could be the following: 1: Country, 2: State, 3: County, 4: Town, 5: ZIP.
Import Objects for the Country Structure

To facilitate the import of country structures, Oracle Fusion Applications
incorporate the structure of the country structure into import objects. The import
object for country structures is GeoStructureLevel.
between the structural components that make up the country structure.
to preparing your import data. For information about the Oracle Fusion
Applications attributes, see the Oracle Enterprise Repository. The reference
files contain descriptions, logic used to choose default values, and validation
information for each of the Oracle Fusion Applications attributes. The validation
information includes the navigation to the task where you can define values
in Oracle Fusion Applications. For example, if you have values in your
data that correlate to a choice list in Oracle Fusion Applications, then the
validation information for that attribute provides the task name in the Setup
and Maintenance work area where you can define your values. For additional
information, including a list of reference file names and locations that you need
to complete this task, see the following table.

Country Structure Country Structure Import Objects: How They Work
Together
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

DRAFT
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.
import object. When creating a new country structure, you import the Country
Structure object.
You must be assigned the Master Data Management Administrator job role to
access and submit the import activities for country structures.
import activity.
Country Structure Import Objects: How They Work Together
This topic describes the Country Structure import object. You use the Country
Structure import object when you submit a file-based import activity to import
your country structure information. This topic introduces the following:
• Target objects for the Country Structure import object

The Country Structure import object is used to import a country structure
hierarchy, including details, such as geography type, geography type name,
parent geography type, geography level numbers, and so on. To map the source
data in your import file to the target attributes in Oracle Fusion Applications,
you must understand how the target objects are related and what attributes are
included in each target object.
Country Structure Target Import Objects

The Country Structure import object contains one target import object that
organizes the individual attributes of the different aspects of the geography
structure. When updating an existing country structure, you must provide the
parent reference information of the existing country structure. This reference
information connects the imported geography structure to the existing one. Use
Importing Country Structures 11-3

DRAFT
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
extensibility features for country structures.

To access the reference guide files for the country code's 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.
Documentation tab for the Country Code File-Based Data Import asset.

ImpGeoStructureLevel Contains information that HZ_IMP_GEO_STRUCTURE_LEVELS_Reference
specifies a country's geography
structure.
Sample attributes:
GeographyType,
GeographyTypeName,
LevelNumber, and
ParentGeographyType.
Reference attribute: CountryCode

DRAFT
12
Importing Customers
Importing Customers Using File-Based Import: Explained

This topic explains how to prepare and import customer data from an external
feature.
A customer is an entity with whom you have a selling relationship. Oracle
Fusion Applications refer to sales account and sales prospects collectively as
a Customer. A customer business object allows you to capture all information
about a customer, such as the customer profile, customer contact relationships
information, and customer contact points.
A sales account is a specific sell-to entity within a given customer. You can create
leads and opportunities for sales accounts. An entity with a sales account in
Oracle Fusion Applications can be one of the following:
• Sales Prospect: A prospective entity or person who does not have a sell-to
address. This entity is used to define leads.
• Customer: A sales account or sales prospects.
• Legal Entity: A legal entity is a party that can enter into legal contracts
or a business relationship. It can be sued if it fails to meet contractual
obligations.
You can use the Customer import object to import sales accounts or sales
prospects of the type organization. You can use the Group Customer import
object to import customers of the type group, and the Consumer import object to
import customers of the type person.
You must consider the following questions when importing your data:
• Did you identify the records that should be imported as sales prospects,
and the records that should be imported as sales accounts?
• How does your legacy or source system represent the customer
same data?
your existing data values to the Customer import object?
attributes that are critical to the way you do business?
Before you can import your customer data from the legacy or source system,
you must first analyze the data and see how it corresponds to the customer
Importing Customers 12-1

DRAFT
object structure of Oracle Fusion Applications. You must understand how Oracle
Fusion Applications represent the structure of the data for a customer.
The Oracle Fusion Applications Customer import object structure is hierarchical.
The root of the hierarchy is the organization profile, which must exist before
you can import lower-level components, such as classifications, contacts, and
sales account profiles. These child entities can have other entities as their child
entities. This hierarchical structure supports one-to-many relationships between
the components that make up the customer.
The following figure shows the customer object and its child entities.
The organization profile contains basic information about the customer, such
as the customer name and party usage. For each customer, you can assign
classifications, contacts, sell to addresses, phone details, and additional names.
The contact of the customer, in turn, includes other child entities that capture
information about the contact, such as contact job, contact primary phone,
contact primary address, and contact 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 customer for the contact
method primary phone.
After you understand the structure of the data, the next step is to compare the
detailed attribute values of your data with the Oracle Fusion Applications data.
Each import object is a collection of attributes organized to assist you when
mapping your data to the Oracle Fusion Applications data and to support one-
to-many relationships between the structural components that make up the
customer.
preparing your import data. The reference guide files contain descriptions,
default values, and validations for each of the Oracle Fusion Applications
attributes. The validation information includes the navigation to the task
where you can define values in Oracle Fusion Applications. For example, if
you have values in your data that correspond to a choice list in Oracle Fusion
Applications, then the validation information for that attribute provides the

DRAFT
task name in the Setup and Maintenance work area where you can define your
values.
To extend the Oracle Fusion Applications object to import your legacy or source
your source file data. You can use the same source file to import both extensible
custom attributes and the standard import object attributes.
Importing Customers Using File-Based Data Import
For the customer business object, you must use the File-Based Data Import
The Define File-Based Import Setup and Maintenance task list includes the tasks
required to configure the import objects, to create source file mappings, and to
schedule the import activities. You submit file-based import activities for each
import object. An import activity defines the instructions for processing import
data including the source file, import data mapping from the source file to the
Oracle Fusion Applications object and attribute, and the import schedule.
When importing customer information, you first import the basic customer
profile information, followed by the child entities for the customer. When
for all parent levels for the entity. For example, you first import basic profile
details, such as customer name, party type, and party usage. You then
import contacts and contact information, such as phone, address, contact
points, and fax for the customer. You must provide the PartyOrigSystem and
PartyOrigSystemReference of the customer when importing contacts for the
customer. PartyOrigSystem is the source system code that identifies the source
row of data within a single import, and is a combination of PartyOrigSystem
and a unique reference. When importing contact information for a customer, you
must provide the relationship reference information. This information is required
because a contact can have multiple relationships with a customer.
import activity. Alternatively, you can also navigate to the Customer Center
work area to view the customer information that you have imported.
Customer Import Objects: How They Work Together

The Customer import object allows you to import customers, their detailed
information, and contacts related to the customer. This topic describes the
Customer import object. It introduces the following:
• Target objects for the Customer import object
• Target import object attribute
• Target import object attribute reference guide files for evaluating and
mapping source file data

DRAFT
Customer Target Import Object Concepts
The Customer import object imports customer information and contacts related
to customer. The Customer import object is split into separate target import
objects for organizing the individual attributes for the different aspects of the
customer and customer contact. Before you import customer information, you
must understand how the target objects are related and what attributes are
included in each object. This understanding helps you create the appropriate
mapping between the source data in your import file and the target attributes.
The target import objects included in the Customer import object are grouped
into information about the customer and the customer contact. The organization
profile is the target import object containing attributes to import information
about the customer. You can have multiple contacts associated with a customer.
The Customer import object has multiple target import objects that include
attributes to import customer contacts and their related information.
When updating an existing customer with additional information, you must
provide the parent reference information for the existing customer. When
importing customer contacts or contact information for a customer, you must
provide relationship reference information in addition to the parent reference.
This information is required because a contact can have multiple relationships
with an organization, such as an employee or board member. When importing
information about a contact you must refer to the specific relationship that
you want to import information for. For example, you might want to import
information for John Smith the employee or John Smith the board member. If
you do not include the reference information for a customer-contact relationship,
then the import process creates a relationship.
To update the information for an existing customer or to create a customer
record, you can import customer profile information, addresses, and
contact points, such as a phone and fax. The following target import objects
are for creating and updating the corresponding customer information:
OrganizationProfile, Fax, PrimaryPhone, Url, SalesAccountProfile, Classification,
AdditionalName, Relationship, SellToAddress, and AdditionalIdentifier.
To update or to create a customer contact, use the following target import
objects: ContactPersonProfile, ContactJob, ContactPrimaryAddress,
ContactEmail, ContactPrimaryPhone, ContactMobile, ContactInstantMessenger,
and ContactFax. All contact-related entities, such as primary phone or e-mail,
Primary Phone Contact Preference entity captures the contact preference of the
legal entity for the contact method primary phone.

Note
DRAFT
Composer extensibility features for the customer.

To access the reference guide files for the customer target import objects, see the
Documentation tab for the Customer File-Based Data Import asset.

OrganizationProfile Includes detailed customer HZ_IMP_PARTIES_T_Reference
information, such as, organization
name and organization type.
Sample attributes:
OrganizationSize,
UniqueNameAlias, CeoName, and
CertificationLevel.
PartyOrigSystem,
PartyId.
number of the customer. If the
customer has multiple phone
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
and PhoneNumber.
CpOrigSystem and
Classification Includes classification information HZ_IMP_CLASSIFICS_T_Reference
for a customer. Classification
Sample attributes:
ClassificationCode,

AdditionalName
DRAFT
Indicates alternative name of a HZ_IMP_ADDTNLPARTYNAMES_T_Reference
customer.

Fax Indicates the fax of the customer. HZ_IMP_CONTACTPTS_T_Reference
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
and PhoneNumber.
CpOrigSystem and
FaxContactPreference Indicates the customer preference HZ_IMP_CONTACTPREFS_Reference
Fax.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
Url Indicates the Url of the customer HZ_IMP_CONTACTPTS_T_Reference
organization.
Sample attributes:
ContactPointType, PrimaryFlag,
Url, and WebType.
CpOrigSystem and

SalesAccountProfile
DRAFT
Includes detailed information ZCA_IMP_SALES_ACCOUNTS_Reference
about a customer sales account.
A sales account is a specific sell-
to entity within a given customer.
A customer can have multiple
sales accounts and sales account
profiles.
Sample attributes:
AccountDirectorId,
NamedAccountFlag, and
AssgnExceptionFlag.
OwnerOrigSystem and
OwnerOrigSystemReference.
SellToAddress Includes customer addresses HZ_IMP_PARTYSITES_T_Reference
and party sites information. If
party site usage of an address
is not defined, then the import
process sets it to Sell-To. If there
are multiple addresses without
party site usage information, then
the import process designates
one of the addresses as the Sell-To
address.

and State.

and LocationId1.

party sites: SiteOrigSystem,
PartysiteId1.

site use: SiteuseOrigSystem,
SiteuseOrigSystemRef, and
PartySiteUseId.
AdditionalIdentifier Includes detailed information HZ_IMP_ADDTNLPARTYIDS_T_Reference
the customer.

IdentifierValue,
AdditionaldentifierOrigSystem,
and

Relationship
DRAFT
Includes information about a HZ_IMP_RELSHIPS_T_Reference
relationship between the customer
and another entity, such as an
organization or a person. You
must enter a relationship code in
the RelationshipCode column,
when creating a relationship.
Sample attributes:
RelationshipCode,
DependentFlag.
ContactPersonProfile Includes detailed information, HZ_IMP_RELSHIPS_T_Reference
such as, person name, relationship
type, and marital status, of a
customer contact.
Sample attributes:
Gender, MaritalStatus,
PartyType, PartyUsageCode,
PersonFirstName, and
PersonLastName.
PartyID, PartyOrigSystem,
RelOrigSystem,
RelationshipId.
ContactAdditionalName Indicates alternative name of a HZ_IMP_ADDTNLPARTYNAMES_T_Reference
customer contact.
Sample attributes:
ContactEmail Indicates the e-mail of the HZ_IMP_CONTACTPTS_T_Reference
customer contact.
Sample attributes:
CpOrigSystem and

ContactInstantMessenger
DRAFT
Indicates the instant messenger or HZ_IMP_CONTACTPTS_T_Reference
customer contact.
Sample attributes:
CpOrigSystem and
ContactPrimaryAddress Indicates the primary address of HZ_IMP_PARTYSITES_T_Reference
a customer contact. If the contact
has multiple addresses, one of
the addresses is designated as the
primary address.

and State.

loaction: LocationOrigSystem,
and LocationId1.
Reference attributes or
PartysiteId1.
ContactFax Indicates the fax of the customer HZ_IMP_CONTACTPTS_T_Reference
contact.
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneExtension.
CpOrigSystem and
ContactJob Includes job information of a HZ_IMP_CONTACTS_T_Reference
customer contact.

DepartmentCode, and
JobTitleCode.
and RelOrigSystemReference

ContactMobile
DRAFT
Indicates the mobile number of a HZ_IMP_CONTACTPTS_T_Reference
customer contact.
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneCountryCode,
CpOrigSystem and
ContactPrimaryPhone Indicates the primary phone HZ_IMP_CONTACTPTS_T_Reference
number of the customer contact.
If the customer has multiple
phone numbers, one of the phone
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneCountryCode,
CpOrigSystem and
PrimaryPhoneContactPreference Indicates the customer contact HZ_IMP_CONTACTPREFS_Reference
through phone.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
ContactEmailContactPreference Indicates the customer contact HZ_IMP_CONTACTPREFS_Reference
through e-mail.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and

ContactFaxContactPreference
DRAFT
Indicates the customer contact HZ_IMP_CONTACTPREFS_Reference
through Fax.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
ContactMobileContactPreference Indicates the customer contact HZ_IMP_CONTACTPREFS_Reference
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
ContactPrimaryAddressContactPreference
at the primary address.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
ContactPrimaryPhoneContactPreference
through the primary phone
number.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and

DRAFT
Importing Organization Profiles Using File-Based Import: Quick
Start
with importing organization profiles.
• Organization profiles overview
• Additional tips
can use to import organization profiles.

Customer Organization OrganizationProfile
Legal Entity Organization OrganizationProfile
Lead Organization OrganizationProfile
Response Organization OrganizationProfile
Partner Organization PartnerInterface
Organization Profile Overview

An organization profile enables you to capture organization information for a
customer, 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.

To import new organization profiles or update existing organization profiles
organizations you want to create or update. To update the organization profile
information for an existing record, the import process must also be able to
uniquely identify the record.
To update an existing organization profile, your source file must include values
that enable the import process to identify the existing records. To update the
organization profile information for an existing record, the import process must
also be able to uniquely identify the record. To identify the record, you will be
either provide the Oracle Fusion record ID or a source system and source system
reference value combination.

DRAFT

The minimum that is required to import organization profile information
are creating a new organization profile or updating an existing record.
associate records.
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 organization profile data
based on two possible scenarios for your import, any prerequisite setup or
an option is provided. More information about the options is listed after the
following table.
Organization Description Data Value Create an Update an Existing

Profile Target Prerequisite Organization Organization
Object Attribute Profile Profile
representing the source system required required
external source code as enabled
system. for Trading See footnote [1]. See footnote [2].
Community
members, using
the Setup and
Maintenance,
Manage Trading
Community Source
Systems task.
number or text reference value required required
representing the from your source
source system system. See footnote [1]. See footnote [2].
unique ID for the
organization.
OrganizationName The name of the Required
organization.

ObjectKey or
DRAFT
The Oracle Fusion Identify the PartyId Conditionally
PartyID record ID for the for an existing required
organization. organization profile
by exporting the See footnote [2].
Organization or
Partner Profile
object using
the Setup and
Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.
[2] To identify the existing organization profile, provide either the Oracle Fusion
record ID (PartyId) or both the source system code and reference values that
you provided when importing the organization profile in a prior import batch
(PartyOrigSystem and PartyOrigSystemReference).

OrganizationProfile and PartnerInterface attributes that are available to import
and the possible prerequisite steps for those attributes. This reference file
includes the following information:
• All OrganizationProfile and PartnerInterface attributes available for
import.
description.
To access the reference file for OrganizationProfile and PartnerInterface, follow
these steps.
HZ_IMP_PARTIES_T.
4. Select HZ_IMP_PARTIES_T_Reference file.
Additional Tips

DRAFT
• Importing sales leads
• Importing marketing responses
• Importing partners

attributes
• Additional tips



DRAFT
Fusion record ID.


Group Profile
Target Object
Same Batch
Attribute
identifier Schedule
belongs. Export
Processes task.
party in the
same batch as
this additional
party identifier.
the party in the
same batch as
this additional
party identifier.

DRAFT
tables.
Same Batch
the Setup and
Maintenance,
Manage
Trading
Community
Source Systems
task.
reference
value must
be unique for
all additional
party identifiers
for the source
system.
Party identifier
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.

The identifier
DRAFT
type to additional
type using
the Setup and
Maintenance,
Manage
Additional
Identifier
Types task.
identifier value
for a party.
Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
description.

DRAFT
Additional Tips

Start
• Additional tips


Legal Entity
DRAFT

file-based objects.
Fusion record ID.
on the following:
associate records.
file.

DRAFT
table.

Attribute
Export
Processestask.
importing the
party in the
same batch as
this additional
party name.
when importing
the party in the
same batch as
this additional
party name.

DRAFT
tables.
Same Batch
name. Maintenance,
Manage
Trading
Community
Source Systems
task, select
the Enabled
for Trading
Community
Members check
box.
name. The reference
value must be
unique for all
additional party
names for the
source system.

DRAFT
Party Name
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
name. name types
for each party
type (person,
organization, or
group), using
the Setup and
Maintenance,
Manage
Additional
Name Types
task.
name value for
an organization
or group.
description.

DRAFT
Additional Tips

• Additional tips


DRAFT
the following:
record.
associate records.

DRAFT
Target Object Batch
Attribute
belongs. Schedule
Export
Processes task.
when importing
the party
in the same
batch as this
classification.
importing
the party
in the same
batch as this
classification.

DRAFT

in the Same Party
Batch
members, using
the Setup and
Maintenance,
Manage
Trading
Community
Source Systems
task.
system. association
record. The
reference value
must be unique
for all party
classification
associations
for the source
system.
Classification
Assignment
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.

DRAFT
classification
codes valid
for each
classification
category, using
the Manage
Classification
Categories,
Setup and
Maintenance
task.
category. category
name and
review entity
assignment
rules using
the Manage
Classification
Categories,
Setup and
Maintenance
task.


description.

DRAFT

Additional Tips

DRAFT
13
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 a
customer has with other customers. A customer hierarchy consists of hierarchy
members. A customer hierarchy can be used to process payments from one
customer and apply them to another customer in the same hierarchy. It can also
be used to create the revenue roll-up report that rolls up revenue numbers from
opportunities for all customers in a hierarchy.
You must consider the following questions before importing customer hierarchy
information:
• Are all members of the customer hierarchy in Oracle Fusion Applications?
• Do I have to import additional hierarchy members to complete the

hierarchy?
• How does your legacy system or source system represent the promotion

your existing data values to the Customer import object?

To import a customer hierarchy, you must:
1. Import customers who must be a part of the hierarchy.

2. Import a hierarchy definition that includes the hierarchy structure and the
root node.
Importing Customer Hierarchies 13-1

DRAFT
3. Import members from the existing customers 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 customer
object structure of Oracle Fusion Applications. You must understand how Oracle
Fusion Applications represent the structure of the data for a customer hierarchy.
The Oracle Fusion Applications customer hierarchy object structure is

hierarchical. At the top level is the customer hierarchy, which must exist before
you can import customer hierarchy members. The customer hierarchy and
customer hierarchy member contain information about the customer hierarchy
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 Fusion Applications data. Each
import object is a collection of attributes organized to assist you when mapping
your data to the Oracle Fusion Applications data and to support one-to-many
relationships between the structural components that make up the customer
hierarchy.

attribute will provide the task name in the Setup and Maintenance work area
where you can define your values.
If you want to extend the Oracle Fusion Applications import object to import
your legacy or source data, then you must use Oracle Fusion Applications CRM
importing.
The corresponding import object is updated with the extensible attributes, which
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

DRAFT
that is suitable for file-based import. The file-based import process reads the
data included in your source file, populates the interface tables according to
your mapping, and imports the data into the application destination tables. The
Define File-Based Data Import Setup and Maintenance task list includes the tasks
required to configure the import objects, to create source file mappings, and to
import object.
An import activity defines the instructions for processing import data, including
the source file, import mapping from the source file to the Oracle Fusion
Applications object and attribute, and the import schedule.
When importing customer hierarchy information, you first import the customer
hierarchy information and then the customer hierarchy members for the
customer hierarchy. When importing customer hierarchy members, you must
provide the parent reference information that refers to the customer hierarchy of
the member.

can be used to verify imported data. You can view the list of import activities
from the Manage Import Activities page. You can verify the status of the import
activity by clicking the Status column for your import activity. Alternatively, you
can also navigate to the Manage Hierarchies task from Setup and Maintenance to
view the customer hierarchy information that you have imported.
Customer Hierarchy Import Objects: How They Work Together

The Customer Hierarchy import object imports customer hierarchy and
customer hierarchy members. This topic describes the Customer Hierarchy
object and introduces the following:
• Target objects for the Customer Hierarchy import object
Customer Hierarchy Target Import Objects Concepts

The Customer Hierarchy import object imports customer hierarchy and
customer hierarchy members. The Customer Hierarchy and Customer Hierarchy
Members import objects are split into separate target import objects for
organizing the individual attributes for the different aspects of the customer
hierarchy. To map the source data in your import file to the target attributes in
Oracle Fusion Applications, you must understand how the target objects are
related and what attributes are included in each target object.

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

Note
If any of the attributes that you want to import do not have an equivalent target
Composer extensibility features for the customer hierarchy.

To access the reference guide files for the customer hierarchy target import
objects, see the File-Based Data Import assets in Oracle Enterprise Repository for
Oracle Fusion Applications (http://fusionappsoer.oracle.com).
Documentation tab for the Customer Hierarchy File-Based Data Import asset.

CustomerHierarchy Customer hierarchy definition HZ_IMP_HIERARCHIES_T_Reference
and root node of the customer
hierarchy

CustomerHierarchyMember
DRAFT
Customer hierarchy members HZ_IMP_HIERARCHY_NODES_Reference

DRAFT

DRAFT
14
Importing Employee Resources
Importing Employee Resources Using File-Based Import: Explained

This topic explains how to prepare and import employee resource data from an
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 Fusion Applications represent the same
data?
your data values?
You must understand how your employee resource data corresponds with the
data in Oracle Fusion Applications in order to be able to map your legacy data to
the data needed by Oracle Fusion Applications. First, you must understand how
Oracle Fusion Applications represent the structure of the data for an employee
resource.
In Oracle Fusion Applications, 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.
Importing Employee Resources 14-1

DRAFT
The following figure illustrates the structure of the Employee Resource object.
The worker profile contains basic information about the employee resource, such
as the employee resource's primary address and resource profile details.
Import Objects for the Employee Resource
To facilitate the import of employee resources, Oracle Fusion Applications
incorporate the structure of the employee resource into import objects. The
import object for the employee resource is Employee Resource.
between the structural components that make up the employee resource.

Employee Resource Employee Resource Import Objects: How They Work
Together
Hint: You can use the keyword importing employee resources to search for
related topics in Oracle Fusion Applications Help.
attributes.

DRAFT
Importing Employee Resources Using File-Based Data Import
For the employee resource business object, you must use the File-Based Data
The Define File-Based Data Import Setup and Maintenance task list includes
the tasks needed to configure the import objects, to create source-file mappings,
and to schedule the import activities. You submit file-based import activities
for each import object. When creating a new employee resource, you import the
Employee Resource import object.
access and submit the import activities for employee resources.
which can be used to verify imported data. Users with either the Master Data
Management Administrator job role can also navigate to the Manage Resources
work area to view the imported employee resources.
Employee Resource Import Objects: How They Work Together

Employee resources are employees to whom you can assign work objects, for
example, service agents, sales managers, and so on. You can import all your
employee resource information using the Employee Resource import object. This
topic describes this import object.
• Target objects for the Employee Resource import object
The Employee Resource import object is used to import an employee resource's
worker profile information, such as first name, last name, address, and so on,
and the employee resource's resource profile information, such as resource
organization and resource team memberships. To map the source data in your
each target object.
Employee Resource Target Import Objects
The target import objects included in the Employee Resource import object
are grouped into information about the employee resource's profile and the
employee resource's address information. The Worker profile is the target import
object containing attributes to import information about the employee resource.

DRAFT
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.
Note
extensibility features for the marketing response.

To access the reference guide files for the employee resource's target import
Documentation tab for the Employee Resource File-Based Data Import asset.

WorkerProfile Contains information that HRC_LOADER_BATCH_LINES_Reference
identifies an employee.
Sample attributes: ResourceProfile

and PrimaryAddress.
PartyOrigSystem,
PartyId.

ResourceProfile
DRAFT
Contains information about a HZ_IMP_RESOURCES_Reference
resource.
Sample attributes: PartyId,

FirstName, LastName,
Department, and JobCode.
PartyOrigSystem,
PartyId.
PrimaryAddress Indicates the address of a HZ_IMP_PARTYSITES_T_Reference
resource. If the resource has
multiple addresses, then the
first address is designated as the
primary address.

PartyOrigSystem,
PartyId.
ResourceOrganizationMembership Contains the employee resource's HZ_IMP_GROUP_MEMBERS_Reference
resource organization membership
information.
Sample attributes:
RequestId, PartyId,
ParentOrganizationName,
OrganizationId,
OrganizationName, and
OrganizationUsage.
PartyOrigSystem,
PartyId.
ResourceTeamMembership Contains the employee resource's HZ_IMP_TEAM_MEMBERS_Reference
resource team membership
information.
Sample attributes: RequestId,

TeamMemberId, TeamId, and
TeamNumber.
PartyOrigSystem,
PartyId.

DRAFT

DRAFT
15
Importing Geographies
Importing Geographies Using File-Based Import: Explained

This topic describes the tasks you must perform to import geography
information. A geography is any region with a boundary around it, regardless of
its size. It might be a state, a country, a city, a county, or a ward. You must create
or import geographies before you can associate them with custom zones and
addresses.
• How does your legacy system or source system represent the geography
your data values?
You must understand how your geography data corresponds with the data in
Oracle Fusion Applications in order to be able to map your legacy data to the
data needed by Oracle Fusion Applications. First, you must understand how
Oracle Fusion Applications represent the structure of the data for a geography.
You must import a separate country structure import object for each country.
Each of these import objects must contain the geography types that are used in
the country's structure, organized in a hierarchy using geography level numbers.
For example, if you are importing the country structure of Australia, the country
structure could be the following: 1: Country, 2: State, 3: County, 4: Town, 5: ZIP.
Import Objects for the Geography

To facilitate the import of geographies, Oracle Fusion Applications incorporate
the structure of the geography into import objects. The import object for the
geography is ImpGeography.
Importing Geographies 15-1

DRAFT
between the structural components that make up the geography.
to preparing your import data. For information about the Oracle Fusion
Applications attributes, see the Oracle Enterprise Repository. The reference
files contain descriptions, logic used to choose default values, and validation
information for each of the Oracle Fusion Applications attributes. The validation
information includes the navigation to the task where you can define values
in Oracle Fusion Applications. For example, if you have values in your
data that correlate to a choice list in Oracle Fusion Applications, then the
validation information for that attribute provides the task name in the Setup
and Maintenance work area where you can define your values. For additional
information, including a list of reference file names and locations that you need
to complete this task, see the following table.

ImpGeography Geography Import Objects: How They Work
Together
Hint: You can use the keyword importing geographies to search for related
Oracle Fusion Applications do not support extensible attributes for geographies.

You can only import data for attributes provided by Oracle Fusion Applications.
Importing Geographies Using File-Based Data Import
For the geography business object, you must use the File-Based Data Import
each import object. When creating a new geography, you import the Geography
object. You must be assigned the Master Data Management Administrator job
role to access and submit the import activities for geographies.
When importing geography information, you must provide the parent reference
information for all parent levels for the entity.

can be used to verify imported data. Users with the Master Data Management

DRAFT
Administrator job role can also navigate to the Manage Geographies work area
to view the imported geographies.
Geography Import Objects: How They Work Together

This topic describes the Geography import object. You use the Geography import
object to import geography information.
• Target objects for the Geography import object

The Geography import object is used to import geography hierarchy information
to create or update the geography data of a country. To map the source data in
your import file to the target attributes in Oracle Fusion Applications, you must
each target object.
Geography Target Import Objects

The target import objects in the Geography import object contain information
about the geography hierarchy. When updating an existing geography, you
must provide the parent reference information of the existing geography, which
connects the geography to the country of which it is a part.
Use the ImpGeography target import object to create and update geography
information.
Note
Before you import geography data for a country, you must define the country's
geography structure.


DRAFT

To access the reference guide files for the geography's target import objects, see
the File-Based Data Import assets in Oracle Enterprise Repository for Oracle
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.
Documentation tab for the Geography File-Based Data Import asset.
Target Import Object Description Attribute Reference Guide File

Names
ImpGeography Contains information that HZ_IMP_GEOGRAPHIES_T_Reference
captures a country's geography
hierarchy details.
Sample attributes:
CountryCode, GeoDataProvider,
GeographyType,
PrimaryGeographyCode,
PrimaryGeographyCodeType, and
PrimaryGeographyName.
Reference attribute: CountryCode
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 particular example you have a source file containing geography data
that you want to import into the application, so that the geography data can be
used for uses related to locations, such as real time address validation and tax
purposes.
The following table summarizes the key decisions for this scenario:
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

DRAFT
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 Oracle Fusion All, except for the RecordTypeCode field
applications?
When do you want to process the import? Immediately
Summary of the Tasks

These are the steps that are required to create an import activity and submit the
import:
1. Determine what information is in the source file.

2. Create and schedule the import activity.
3. Monitor the import results.
Prerequisites when importing additional geography data after your

initial import
1. You need to ensure that the combination of Source ID and Parent
Source ID values are unique for each row of data within a single import.
However, your source data files do not 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, the changed IDs will not affect the import.
2. Ensure that all of 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 needs to 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, your geography import will result
in two state records (CA and California) in the application data, with the
US as the country parent.
Determine what information is in the source file

1. Your source geography data files should include a unique Source ID value
for each row of data, and a Parent Source ID value which identifies the
parent of that row of geography data. Source IDs, or Parent Source IDs,
should not exceed 18 characters. An example of geography source data
could be as follows:
Geography Name Source ID Parent

Level Source ID
1 (Country) US 1

DRAFT
2 (State) CA 11 1
3 (County) Alameda 111 11
4 (City) Pleasanton 1111 111
4 (City) Dublin 1112 111
Create and schedule the import activity

You create an import activity, enter the import details, and schedule the import.
An import activity definition provides the instructions for the import processing
- this includes selecting the source file, or file location; mapping fields from the
source file to the Oracle Fusion object and attribute; and scheduling the import.
1. Navigate to Setup and Maintenance and search for the Manage File
Import Activities task. Click Go to Task.
2. In the Manage Import Activities page, click the Create icon.
3. In the Create Import Activity: Set Up page, create an import activity for
the Geography object type by completing the fields, as shown in this 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. On the Create Import Activity: Map Fields page, map each field from
your source file to the Oracle Fusion object and attribute, as shown in this
example:
Column Example Ignore Object Attribute

Header Value
Primary Primary United Imp Primary
Geography Geography States Geography Geography
Name Name Name
Country US No Imp Country
Code Geography Code

DRAFT
Record Type 0 Yes Imp Record Type
Code Geography Code
Source ID 10265 No Imp Source ID
Geography
Parent 1053 No Imp Parent
Source ID Geography Source ID
If you do not want to import a column in the text file you can select
Ignore.
Note
If you have any difficulties mapping the fields from your source file to the
relevant Oracle Fusion applications object, you can use the import object
spreadsheets for reference.
6. Click Next.
7. On the Create Import Activity: Create Schedule page, select Immediate in
the Schedule field so that the import will start immediately.
Instead of immediately importing the data, you can choose a date

and time to start the import. You can also specify if the import will be
repeated, and the frequency of the repeated import.
8. Click Next.
Monitor the import results

You monitor the progress of the Import Activity processing, and view
completion reports for both successful records and errors.
1. On the Create Import Activity: Review and Activate page, you verify your
import details in the Import Details, File Details, Import Options, and
Schedule sections.
2. Your import details are correct so you click Activate to submit the import.
Once the import activity has completed, the Status field value will change
to Completed.

DRAFT

DRAFT
16
Importing Group Customers
Importing Group Customers Using File-Based Import: Explained

This topic explains how to prepare and import group customer data from an
external data source into Oracle Fusion Applications, using the File-Based Data
Import feature.
A group customer is a party consisting of a collection of persons and
organizations. A group, similar to a person or organization, can enter into a
business relationship with other parties and can be assigned to opportunities and
leads. A group can have members of party type person or organization. You can
maintain group customers information in Oracle Fusion Applications CRM to
create leads and opportunities for a group, or capture information about a group
to know them better. However, maintaining this information may not let you
assign all sales and marketing activities to a group.
You must consider the following questions before importing group customer
information:
• How does your legacy or source system represent the group customer
same data?
your existing data values to the Group Customer import object?
You must understand how your group customer data corresponds with the data
Fusion Applications represent the structure of the data for a group customer.
The Oracle Fusion Applications Group Customer structure is hierarchical. At
the top level is the group profile, which must exist before you can import lower-
Importing Group Customers 16-1

DRAFT
level components, such as classifications, additional names, additional identifier,
and members. These child entities can have other entities as their child entities.
components that make up the group customer.
The following figure shows the Group Customer import object and its child
entities.
The group customer profile contains basic information about the group
customer, such as the group name, group type, and the group-party usage. For
each group customer, you can assign classifications, members, relationships,
additional identifier, and additional names.
Note
All entities referring to contact information, such as primary phone or e-mail,
Phone Contact Preference entity captures the contact preference of the group for
the phone contact method.
between the structural components that make up the group customer.
attribute will provide the task name in the Setup and Maintenance work area
where you can define your values.
If you want to extend the Oracle Fusion Applications object data to import your
legacy or source data, then you must use Oracle Fusion Applications CRM

DRAFT
Importing Group Customers Using File-Based Data Import
For the group customer business object, you must use the File-Based Data Import
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 Oracle Fusion Applications object and attribute, and the import
schedule.
When importing group customer information, you must first import the basic
group customer profile information, followed by the child entities for the
group customer. When importing child entities, you must provide the parent
reference information for all parent levels for the entity. You must provide the
PartyOrigSystem and PartyOrigSystemReference of the group customer when
importing contacts for the group customer. PartyOrigSystem is the source
system code that identifies the source of the information being imported.
PartyOrigSystemReference is unique for each row of data within a single import,
and is a combination of PartyOrigSystem and a unique reference. For example,
you first import basic profile details, such as first name, last name, party type,
and party usage. You then import contact information, such as phone, address,
contact points, and fax for the group customer.

you can use to verify imported data. You can view the list of import activities
from the Manage Import Activities page. You can verify the status of the import
activity by clicking the Status column for your import activity. Alternatively,
you can also navigate to the Party Center work area to view the customer
information that you have imported.
Group Customer Import Objects: How They Work Together

The Group Customer import object allows you to import group customers, their
basic information, and members of the group. This topic describes the Group
Customer import object and introduces the following:
• Target objects for the Group Customer import object

DRAFT
Group Customer Target Import Objects Concepts

The Group Customer import object imports group customers and its members.
The Group Customer import object is split into separate target import objects
for organizing the individual attributes for the different aspects of the group
customer. To map the source data in your import file to the target attributes in
Oracle Fusion Applications, you must understand how the target objects are
related and what attributes are included in each target object.
Group Customer Target Import Objects

The target import objects in the Group Customer import object are grouped
into information about the group customer and information about the member.
The group profile is the target import object containing attributes to import
information about the group customer. You can have multiple members
associated with a group customer. You can assign only an organization or a
person as a member of a group. You cannot assign a group as a member of
another group.
When updating an existing group customer with additional information, you
must provide the parent reference information for the existing group customer.
When importing contacts or contact information for a group customer, you must
provide relationship reference information in addition to the parent reference.
When importing information about a member, you must refer to the specific
relationship that you want to import information for. For example, you might
want to import information for John Smith the employee or John Smith the board
member. If you do not include the reference information for a relationship, then
the import process will create a relationship.
To update the information for an existing group customer or to create a group
customer record, you can import group customer profile information, addresses,
and contact points, such as phone and fax. The following target import objects
are for creating and updating the group customer information: GroupProfile,
Fax, Mobile, Phone, 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 group customer for the contact
method primary phone. Additionally, the Address import object for a group
customer includes another child entity, AddressPurpose, that captures the
purpose of the current group customer address.


DRAFT
Note
Composer extensibility features for the group customer.

To access the reference guide files for the group customer target import objects,
Documentation tab for the Group Customer File-Based Data Import asset.

GroupProfile Includes detailed group customer HZ_IMP_PARTIES_T_Reference
information, such as, group name
and group type. The default party
usage for a group customer is
SALES_PROSPECT.
Sample attributes: AnnualIncome,

NumOfDependents, MedianAge,
and CertificationLevel.
PartyOrigSystem,
PartyId.
Relationship Includes information about the HZ_IMP_RELSHIPS_T
relationship between the group
customer and the group member.
You must enter a relationship code
in the RelationshipCode column,
when creating a relationship.
Sample attributes:
RelationshipCode and
RelationshipType.
RelOrigSystem RelationshipID,
Member Includes information about the HZ_IMP_RELSHIPS_T
group customer member.
Sample attributes: ObjectKey and

SubjectId.
RelOrigSystem RelationshipID,

Classification
DRAFT
Includes classification HZ_IMP_CLASSIFICS_T
information for a group customer.
Classification allows you to
categorize entities such as parties,
projects, tasks, and orders as
hierarchies.
Sample attributes:
ClassificationCode,
AdditionalIdentifier Includes detailed information HZ_IMP_ADDTNLPARTYID_T
the group customer.

IdentifierValue,
AdditionaldentifierOrigSystem,
and
AdditionalName Indicates alternative name of a HZ_IMP_ADDTNLPARTYNAMES_T
group customer.

Url Indicates the Url of the group HZ_IMP_CONTACTPTS_T_Reference
customer.
Sample attributes:
Url, and WebType.
CpOrigSystem and

InstantMessenger
DRAFT
Indicates the instant messenger or HZ_IMP_CONTACTPTS_T_Reference
customer contact.
Sample attributes:
CpOrigSystem,
CpOrigSystemReference, and
Objectkey.
Fax Indicates the fax of the group HZ_IMP_CONTACTPTS_T_Reference
customer.
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
and PhoneNumber.
CpOrigSystem and
FaxContactPreference Indicates the group customer HZ_IMP_CONTACTPREFS_Reference
through fax.
Sample attributes:
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
Mobile Indicates the mobile number of HZ_IMP_CONTACTPTS_T_Reference
group customer.
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneCountryCode,
CpOrigSystem and

MobileContactPreference
DRAFT
Indicates the group customer's HZ_IMP_CONTACTPREFS_Reference
Sample attributes:
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
Phone Indicates the primary phone HZ_IMP_CONTACTPTS_T_Reference
number of the group customer.
If the group has multiple phone
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
and PhoneNumber.
CpOrigSystem and
PrimaryPhoneContactPreference Indicates the group customer's HZ_IMP_CONTACTPREFS_Reference
through phone.
Sample attributes:
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
Email Indicates the e-mail of the group HZ_IMP_CONTACTPTS_T_Reference
customer.
Sample attributes:
CpOrigSystem and

EmailContactPreference
DRAFT
Indicates the group customer's HZ_IMP_CONTACTPREFS_Reference
through e-mail.
Sample attributes:
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
Address Indicates the address of a group HZ_IMP_LOCATIONS_T,
customer. If the group has HZ_IMP_PARTYSITES_T
multiple addresses, one of the
addresses is designated as the
primary address.


and LocationId1.
Reference attributes or
PartysiteId1.
AddressContactPreference Indicates the group customer's HZ_IMP_CONTACTPREFS_Reference
Sample attributes:
PreferenceEndDate,
ReasonCode.
CpOrigSystem,
AddressPurpose Indicates the purpose of a group HZ_IMP_PARTYSITEUSES_T
customer's address.
Sample attributes: SiteUseType,

EndDate, and StartDate.
SiteOrigSystem and
SiteOrigSystemReference.

DRAFT
attributes
• Additional tips


Fusion record ID.

DRAFT
Group Profile Identifier in the
Target Object Same Batch
Attribute
identifier Schedule
belongs. Export
Processes task.
party in the
same batch as
this additional
party identifier.

The reference
DRAFT
the party in the
same batch as
this additional
party identifier.
tables.
Same Batch
the Setup and
Maintenance,
Manage
Trading
Community
Source Systems
task.

DRAFT
reference
value must
be unique for
all additional
party identifiers
for the source
system.
Party identifier
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
The identifier Identify Required Required
type to additional
type using
the Setup and
Maintenance,
Manage
Additional
Identifier
Types task.
identifier value
for a party.

The party ID
DRAFT
Identify the Required, if
Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
description.
Additional Tips

DRAFT

Start
• Additional tips

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

file-based objects.

DRAFT
Fusion record ID.
on the following:
associate records.
file.
table.

Person Profile, Additional

Group Profile
Target Object
DRAFT Party Names in
the Same Batch
Records to an
Existing Party
Party Name
Records
Attribute
Export
Processestask.
importing the
party in the
same batch as
this additional
party name.
when importing
the party in the
same batch as
this additional
party name.

DRAFT
tables.
Same Batch
name. Maintenance,
Manage
Trading
Community
Source Systems
task, select
the Enabled
for Trading
Community
Members check
box.
name. The reference
value must be
unique for all
additional party
names for the
source system.
Party Name
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.

NameType The name type
DRAFT
Review or Required Required
name. name types
for each party
type (person,
organization, or
group), using
the Setup and
Maintenance,
Manage
Additional
Name Types
task.
name value for
an organization
or group.
description.
Additional Tips

DRAFT

• Additional tips


DRAFT

the following:
record.
associate records.
Organization Description Data Value Create Party Add Update Existing

Person Profile, Classification

Group Profile
Target Object
DRAFT in the Same
Batch
to an Existing
Party
Attribute
belongs. Schedule
Export
Processes task.
when importing
the party
in the same
batch as this
classification.
importing
the party
in the same
batch as this
classification.

DRAFT

in the Same Party
Batch
members, using
the Setup and
Maintenance,
Manage
Trading
Community
Source Systems
task.
system. association
record. The
reference value
must be unique
for all party
classification
associations
for the source
system.
Classification
Assignment
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.

DRAFT
classification
codes valid
for each
classification
category, using
the Manage
Classification
Categories,
Setup and
Maintenance
task.
category. category
name and
review entity
assignment
rules using
the Manage
Classification
Categories,
Setup and
Maintenance
task.


description.

DRAFT

Additional Tips

DRAFT

DRAFT
17
Importing Interactions
Importing Interactions Using File-Based Import: Explained
This topic explains how to prepare and import Interaction data from an external
feature.
An interaction is a business object that is used to record interactions between

your internal resources and external contacts, including references to specific
objects of interest such as a sales lead or an opportunity. You enter your
interaction information within the same user interface as the associated business
object or sales account, or you can import data to create new or update existing
interactions.
• How does your legacy system or source system represent the interaction

your data values?

You must understand how your interaction data corresponds with the data in
Oracle Fusion Applications represent the structure of an interaction.
Importing Interactions 17-1

DRAFT
In Oracle Fusion Applications, a single interaction contains information such as

the date and time, customer, description, and outcome. Additionally, a single
interaction can include one or more internal and external participants and one or
more references to the objects of interest. You can attach a file to your interaction
using the Attachment feature.
Import Object for Interactions
To facilitate the import of interactions, Oracle Fusion Applications incorporates

the structure of the interaction into a single import object with the name of
Interaction.
between the structural components that make up the interaction.


Interaction Interaction Import Objects: How They Work
Together
Hint: You can use the keyword importing interactions to search for related topics
in Oracle Fusion Applications Help.

DRAFT
attributes.
Importing Interactions Using File-Based Data Import
For the interaction business object, you must use the File-Based Data Import
file-based import. The file-based import process reads the data included in your
source file, populates the interface tables according to your mapping, imports
the data into the application destination tables, and associates any attachments.
tasks needed to configure the import object, to create source-file mappings, and
to schedule the import activities.
To associate interactions with internal and external participants and business

each participant and business object. Therefore, the associated participants and
business objects must be entered or imported before submitting the Interaction
import activity. The File-Based Data Import Activity log file typically includes
the internal identifier for internal resources, external parties, and business objects
imported using the File-Based Data Import feature. Optionally, you can obtain
the internal identifier for existing resources, parties, and business objects by
using the Manage Bulk Data Export, Schedule Export Processes Setup and
Maintenance task.
Importing attachments is supported for the Interaction import object, however,

you are limited to one attachment per interaction. You include the attachment
file name in your source file along with the other data about the interaction. You
select the files when defining your Interaction File-Based Import Activity for
import processing.

Administrator to access and submit the import activities for interactions.

objects or sales accounts can also view the interactions.
Interaction Import Objects: How They Work Together
You use the Interaction import object to submit a file-based import activity to
import your Interactions. This topic describes the following:

DRAFT
• Target objects for the Interaction import object

The Interaction import object is used to import records containing information
about interactions between your internal resources and external contacts,
including references to specific objects of interest such as a sales lead or an
opportunity.
The Interaction import object is split into separate target import objects for
organizing the individual attributes of the Interaction and to manage the one-
to-many relationship structure. To map the source data in your import file to the
Interaction Target Import Objects

The target import objects in the Interaction import object are grouped into
information about the interaction, references to the internal and external
participants, and references to the objects of interest. The following figure
shows the target import objects included in the Interaction import object, each
represented by their familiar name and their formal target import object name,
shown in parentheses.
The InteractionImport target object includes the attributes for the majority of
information captured for an interaction, such as the date and time, customer,
description, and outcome. The InteractionParticipantImport target object
includes the attributes to associate internal resources and external contacts
who participated in the interaction. When interactions pertain to specific
business objects, such as a sales lead or opportunity, the attributes pertaining
to the association of the business objects to the interaction are included in the
InteractionAssociationImport target object.


DRAFT
Note
extensibility features for the Interaction.

To access the reference guide files for the Interaction target import objects, see
Documentation tab for the Interaction File-Based Data Import asset.

InteractionImport Interaction information ZMM_INTER_INTERACTIONS_Reference
InteractionAssociationImport Interaction business objects ZMM_INTER_ASSOCIATIONS_Reference
InteractionParticipantImport Interaction participants ZMM_INTER_PARTICIPANTS_Reference

DRAFT

DRAFT
18
Importing Legal Entities
Importing Legal Entities Using File-Based Import: Explained

This topic explains how to prepare and import legal entities from an external
feature.
A legal entity is a recognized party with rights and responsibilities that is
established by legislation. You create a legal entity for each registered company
or other entity recognized in law for which you want to record assets, liabilities,
expenses and income, pay transaction taxes, or perform intercompany trading.
Within Oracle Fusion Applications CRM, a legal entity is a representation of the
legal unit of a customer.
You must consider the following questions before importing legal entity
information:
• How does your legacy or source system structure represent the legal
entity information compared to how Oracle Fusion Applications represent
the same data?
• How do your legacy or source system legal entities relate to business
units, divisions, ledgers, balancing segments, consolidation rules,
intercompany transactions, and payroll reporting?
your existing data values to the Legal Entity import object?
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 Fusion Applications. You must understand how Oracle
Fusion Applications represent the structure of the data for a legal entity.
The legal entity structure of Oracle Fusion Applications 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
Importing Legal Entities 18-1

DRAFT
one-to-many relationships between the components that make up the legal
entity.
The following figure shows the legal entity and its child entities.
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, then compare the detailed
attribute values of your data with the Oracle Fusion Applications data. Each
import object is a collection of attributes organized to help you when mapping
your data to the Oracle Fusion Applications data and to support one-to-many
relationships between the structural components that make up a legal entity.
preparing your import data. The attribute details of Oracle Fusion Applications
are available for your reference in the Oracle Enterprise Repository. The
reference guide files contain descriptions, default values, and validation for
each of the Oracle Fusion Applications attributes. The validation information
includes the navigation to the task where you can define values in Oracle Fusion
you can define your values.
If you have to extend the Oracle Fusion Applications import object to import
your legacy or source data, you must use Oracle Fusion Applications CRM

DRAFT
Importing Legal Entities Using File-Based Data Import
For the legal entity business object, you must use the File-Based Data Import
Based Data Import Setup and Maintenance task list includes the tasks required
to configure the import objects, create source file mappings, and schedule the
import activities. You submit file-based import activities for each import object.
An import activity defines the instructions for processing the import data,
including the source file, import mapping from the source file to the Oracle
Fusion Applications object and attribute, and the import schedule.
When importing legal entity information, you first import the basic legal
entity profile information and then the child entities for the legal entity. When
for all parent levels for the entity. You must provide the PartyOrigSystem and
PartyOrigSystemReference of the legal entitywhen importing contacts for the
legal entity. PartyOrigSystem is the source system code that identifies the source
row of data within a single import, and is a combination of PartyOrigSystem and
a unique reference. For example, you first import basic profile details, such as
first name, last name, party type, and party usage. You then import contacts and
contact information, such as phone, address, contact points, and fax for the legal
entity.
Note
When importing contact information for a legal entity, you must provide the
relationship reference information. This information is required because a
contact can have multiple relationships with a legal entity.
import activity. Alternatively, you can also navigate to the Define Legal Entities
task list from the Setup and Maintenance work area to view the legal entities that
you have imported.
Legal Entity Import Objects: How They Work Together

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

DRAFT
Legal Entity Target Import Object Concepts
The Legal Entity import object imports legal entity information and its contacts.
The Legal Entity import object is split into separate target import objects
for organizing the individual attributes for the different aspects of the legal
entity and its contact. Before you import data, you must understand how the
target objects are related and what attributes are included in each object. This
information helps you create the mapping between the source data in your
import file and the target attributes in the application.
The target import objects in the Legal Entity import object are grouped into
information about the legal entity and the contact. The organization profile is the
target import object containing attributes to import information about the legal
entity. You can have multiple contacts associated with a legal entity. There are
multiple target import objects that include attributes to import contacts and their
related information.
When updating an existing legal entity with more information, you must
provide the parent reference information for the existing legal entity. When
importing contacts or contact information for a legal entity, you must provide
relationship reference information in addition to the parent reference. This
information is required because a contact can have multiple relationships with
the legal entity. When importing information about a contact, you must refer to
the specific relationship you want to import information for. For example, you
might want to import information about John Smith the employee or John Smith
the board member. If you do not include the reference information for a contact
relationship, then the import process creates a relationship.
To update the information for an existing legal entity or to create a legal entity,
you can import legal entity profile information, addresses, and contact points,
such as phone and fax. The following target import objects are for creating
and updating the corresponding legal entity information: OrganizationProfile,
PrimaryAddress, PrimaryPhone, Url, Fax, Classification, AdditionalName, and
ContactPersonProfile.
To update or create a contact, use the following target import objects:
ContactPersonProfile, ContactJob, ContactPrimaryAddress, 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.
each target import object. The reference files contain descriptions, logic used
for default values, and validation information for each of the Oracle Fusion
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.

DRAFT
activity using File-Based Import Activity task. Both tasks are available in the
Note
Composer extensibility features for the marketing response.

To access the reference guide files for the legal entity target import objects, see
Documentation tab for the Legal Entity File-Based Data Import asset.
Target Import Object Description Attribute Reference File Name of

Oracle Enterprise Repository
OrganizationProfile Includes detailed legal entity HZ_IMP_PARTIES_T_Reference
information, such as, organization
name and organization type.
Sample attributes:
OrganizationSize,
RegistrationType, LegalStatus, and
RegistrationType.
PartyOrigSystem,
PartyId.
number of the legal entity. If
the legal entity has multiple
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
and PhoneNumber.
CpOrigSystem and
Fax Indicates the fax of the legal entity. HZ_IMP_CONTACTPTS_T_Reference
Sample attributes:
PhoneAreaCode,
PhoneCountryCode,
and PhoneNumber.
CpOrigSystem and

Url
DRAFT
Indicates the Url of the legal HZ_IMP_CONTACTPTS_T_Reference
entity.
Sample attributes:
Url, and WebType.
CpOrigSystem and
AdditionalName Indicates alternative name of a HZ_IMP_ADDTNLPARTYNAMES_T_Reference
legal entity.

Classification Incudes classification information HZ_IMP_CLASSIFICS_T_Reference
for a legal entity. Classification
Sample attributes: Classification

code, Classification category,
PrimaryAddress Indicates the primary address of HZ_IMP_PARTYSITES_T_Reference
a legal entity. If the contact has
multiple addresses, one of the
addresses is designated as the
primary address.

and State.

and LocationId1.

PartysiteId1.

ContactPersonProfile
DRAFT
Includes detailed information, HZ_IMP_RELSHIPS_T_Reference
such as, person name, relationship
type, and marital status, of a legal
entity contact.
Sample attributes:
Gender, MaritalStatus,
PartyType, PartyUsageCode,
PersonFirstName, and
PersonLastName.
PartyOrigSystem, PartyID,
RelOrigSystem,
RelationshipId.
ContactEmail Indicates the e-mail of the legal HZ_IMP_CONTACTPTS_T_Reference
entity contact.
Sample attributes:
EmailAddress, and start date.
CpOrigSystem and
ContactFax Indicates the fax of the legal entity HZ_IMP_CONTACTPTS_T_Reference
contact.
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneExtension.
CpOrigSystem and
ContactInstantMessenger Indicates the instant messenger or HZ_IMP_CONTACTPTS_T_Reference
legal entity contact.
Sample attributes:
ContactPointPurpose, end date,
CpOrigSystem and

ContactJob
DRAFT
Includes job information of a legal HZ_IMP_CONTACTS_T_Reference
entity contact.

DepartmentCode, and
JobTitleCode.
RelOrigSystem, RelationshipID,
ContactMobile Indicates the mobile number of a HZ_IMP_CONTACTPTS_T_Reference
legal entity's contact.
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneCountryCode,
CpOrigSystem and
ContactPrimaryAddress Indicates the primary address of a HZ_IMP_PARTYSITES_T_Reference
legal entity contact. If the contact
has multiple addresses, one of
the addresses is designated as the
primary address.

and State.

and LocationId1.

PartysiteId1.

ContactPrimaryPhone
DRAFT
Indicates the primary phone HZ_IMP_CONTACTPTS_T_Reference
number of the legal entity contact.
If the legal entity has multiple
Sample attributes:
ContactPointType,
PhoneAreaCode,
PhoneCountryCode,
CpOrigSystem and
ContactAdditionalName Indicates alternative name of a HZ_IMP_ADDTNLPARTYNAMES_T_Reference
legal entity contact.
Sample attributes:
PrimaryPhoneContactPreference Indicates the legal entity's HZ_IMP_CONTACTPREFS_Reference
through phone.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
MobileContactPreference Indicates the legal entity's HZ_IMP_CONTACTPREFS_Reference
through mobile.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and

FaxContactPreference
DRAFT
Indicates the legal entity's HZ_IMP_CONTACTPREFS_Reference
through fax.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
EmailContactPreference Indicates the legal entity's HZ_IMP_CONTACTPREFS_Reference
through e-mail.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
ContactPrimaryAddressContactPreference
Indicates the legal entity contact's HZ_IMP_CONTACTPREFS_Reference
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
ContactPrimaryPhoneContactPreference
Indicates the legal entity contact's HZ_IMP_CONTACTPREFS_Reference
number.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and

DRAFT
PrimaryAddressContactPreference Indicates the legal entity's HZ_IMP_CONTACTPREFS_Reference
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and
PrimaryPhoneContactPreference Indicates the legal entity's HZ_IMP_CONTACTPREFS_Reference
number.
Sample attributes:
PreferenceCode,
PreferenceEndDate,
ReasonCode.
CpOrigSystem and

Start
• Additional tips


DRAFT


associate records.
following table.

Organization
DRAFT
Description Data Value Create an Update an Existing
Community
members, using
the Setup and
Maintenance,
Manage Trading
Community Source
Systems task.
unique ID for the
organization.
organization.
ObjectKey or The Oracle Fusion Identify the PartyId Conditionally
Organization or
Partner Profile
object using
the Setup and
Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.
import.
description.

DRAFT
these steps.
HZ_IMP_PARTIES_T.
Additional Tips

Start
• Additional tips


Legal Entity
DRAFT

file-based objects.
Fusion record ID.
on the following:
associate records.
file.

DRAFT
table.

Attribute
Export
Processestask.
importing the
party in the
same batch as
this additional
party name.
when importing
the party in the
same batch as
this additional
party name.

DRAFT
tables.
Same Batch
name. Maintenance,
Manage
Trading
Community
Source Systems
task, select
the Enabled
for Trading
Community
Members check
box.
name. The reference
value must be
unique for all
additional party
names for the
source system.

DRAFT
Party Name
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.
name. name types
for each party
type (person,
organization, or
group), using
the Setup and
Maintenance,
Manage
Additional
Name Types
task.
name value for
an organization
or group.
description.

DRAFT
Additional Tips

• Additional tips


DRAFT
the following:
record.
associate records.

DRAFT
Target Object Batch
Attribute
belongs. Schedule
Export
Processes task.
when importing
the party
in the same
batch as this
classification.
importing
the party
in the same
batch as this
classification.

DRAFT

in the Same Party
Batch
members, using
the Setup and
Maintenance,
Manage
Trading
Community
Source Systems
task.
system. association
record. The
reference value
must be unique
for all party
classification
associations
for the source
system.
Classification
Assignment
object, using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes task.

DRAFT
classification
codes valid
for each
classification
category, using
the Manage
Classification
Categories,
Setup and
Maintenance
task.
category. category
name and
review entity
assignment
rules using
the Manage
Classification
Categories,
Setup and
Maintenance
task.


description.

DRAFT

Additional Tips

DRAFT
19
Importing Marketing Budgets
Importing Marketing Budgets Using File-Based Import: Explained

This topic explains how to prepare for and import marketing budget data from
an external data source into Oracle Fusion Applications using the File-Base Data
Import feature.
A marketing budget is a business object that is used to manage funds set aside
to fund partner incentives. You enter your budget information using the Budgets
work area or you can import data to create or update marketing budgets.
• How does your legacy system or source system represent the budget
compared to how Oracle Fusion Applications represent same data?
• Do you have to configure values in Oracle Fusion to map to your data

values?
• Do you have to customize Oracle Fusion to capture additional attributes

that are critical to the way you do business?
You must understand how your marketing budget data corresponds with the
data in Oracle Fusion Applications to be able to map your legacy data to the data
Fusion Applications represent the structure of the data for a marketing budget.
In Oracle Fusion Applications, the marketing budget structure is hierarchical. At

the top level is the marketing budget summary, which must exist before you can
import lower level components such as notes and attachments. This hierarchical
structure supports one-to-many relationships between the components that
Importing Marketing Budgets 19-1

DRAFT
make up the marketing budget. For example, a marketing budget can have many
notes.
The marketing budget summary contains basic information about the budget
such as the type, start and end dates, and budget amount. For each marketing
budget, you can post notes and attach documents relevant to the budget.
Import Objects for the Marketing Budget
To facilitate the import of marketing budgets, Oracle Fusion Applications

incorporate the structure of the promotion into import objects. The import
objects for the marketing budget are shown in the following table.
Import Objects Structure

Marketing Budget Marketing Budget
Note Note
the Oracle Fusion Applications data and so support one-to-many relationships
between the structural components that make up the marketing budget.
A good understanding of the attribute details of the import objects is critical to
your import data. The reference guide files contain descriptions, logic used to
select default values, and validation information for each of the Oracle Fusion
Applications attributes. The validation information includes the navigation
to the task where you can define values in Oracle Fusion Applications. For
example, if you have values in your data that correlate to a choice list in Oracle
Fusion Applications, then the validation information for that attribute provides
the task name in the Setup and Maintenance work area where you can define
your values. For additional information, including a list of reference guide file
names and locations that you need to complete this task, see the following table.

Marketing Budget Marketing Budget Import Objects and Attributes:
Note Note Import Objects and Attributes: How They
Work Together
Hint: You can use the keyword "importing marketing budgets" to search for
related topics in Oracle Fusion Applications Help.

DRAFT
your source file data. You can use the same source file to import both custom
attributes and the standard import object attributes.
Importing Marketing Budgets Using File-Based Data Import
For the marketing budget business object, you must use the File-Based Data
import object. When creating a marketing budget, you first import the Marketing
Budget object, follow by subsequent import activities for each of the other import
objects (in this case, notes). The exception is attachments, which are imported by
including the file names in your source file for the Marketing Budget object and
selecting the files when defining the import activity.
You must be assigned the Channel Account Manager, Channel Sales Director,
or Channel Sales Manager job role to access and submit the import activities for
marketing budgets.

which can be used to verify imported data. Users with the Marketing Budget
Maintenance Duty role can also navigate to the Budgets work area to view the
imported marketing budgets. Oracle Fusion Applications assign this role to
the following predefined job roles: Channel Account Manager, Channel Sales
Director, and Channel Sales Manager.
Marketing Budget Import
Marketing Budget Import Object: How It Works

You use two main import objects, Marketing Budget and Note, when you
submit a file-based import activity to import your marketing budgets. This topic
describes the Marketing Budget import object. It introduces the following:

DRAFT
• Target objects for the Marketing Budget import object

The Marketing Budget import object is used to import marketing budgets. To
map the source data in your import file to the target attributes in Oracle Fusion
Applications, you must understand how the target objects are related and what
attributes are included in each target object.
Marketing Budget Target Import Object

The target import object in the Marketing Budget import object is
ImportBudgets1. The target import object includes information about the budget,
such as the budget type, initial amount, currency, and fund request submission
deadlines.

data and the combination of target object and target object attribute. You can
Note
Target Import Object Attributes Resources

To access the reference guide files for the marketing budget's target import
Documentation tab for the Marketing Budget File-Based Data Import asset.

ImportBudgets1 Marketing budgets of interest MKT_IMP_BDT_BUDGETS_Reference

DRAFT
Note Import

your data values?
associated object.

DRAFT

attributes.


DRAFT
20
Importing Marketing Campaigns
Importing Marketing Campaigns Using File-Based Import:

Explained
This topic explains how to prepare and import marketing campaign data from an
Import feature.
A marketing campaign is a business object that is used to capture the plan and
design that allows a marketer to achieve a specific marketing goal or objective
through customer interaction, strategic advertisements, and lead generation. You
enter your campaign information using the Campaigns work area or you can
import data to create or update campaigns.
• How does your legacy or source system represent the marketing
campaign compared to how Oracle Fusion Applications represent the
same data?
• Do you need to configure values in Oracle Fusion Applications to map to
your data values?

You must understand how your marketing campaign data corresponds with the
data in Oracle Fusion Applications to be able to map your legacy data to the data
Fusion Applications represent the structure of the data for a campaign.
In Oracle Fusion Applications, the marketing campaign structure is hierarchical.
At the top level is the campaign summary, which must exist before you can
import lower level components such as team members, tasks, and stages.
Importing Marketing Campaigns 20-1

DRAFT
components that make up the campaign. For example, a campaign can have
many team members, tasks, and stages.
The campaign summary contains basic information about the campaign such
as the planned dates, owner, and overall purpose. For each campaign, you can
assign team members, assign tasks and due dates, attach documents relevant to
the campaign, and post notes for the campaign or for specific tasks.
Each campaign can have one or more stages. A stage is a unit of the marketing
campaign design representing a single purpose that contributes to the overall
objective of the campaign. The stage purpose can be for events, advertising,
and outbound communication, such as e-mail, direct mail, or automated lead
generation. Campaign members are the intended recipients of the marketing
message and lead follow-up.
Import Objects for the Marketing Campaign

To facilitate the import of marketing campaigns, Oracle Fusion Applications
incorporate the structure of the campaign into import objects. The import objects
for the marketing campaign are shown in the following table.

Campaign Campaign Summary
Team Members
Attachments
Interaction Marketing Activity Outbound Communication Stages
Event Marketing Activity Event Stages
Advertising Marketing Activity Advertising Stages
Campaign Members Campaign Members
Task Team Tasks
Notes
Note Notes

between the structural components that make up the marketing campaign.

DRAFT

Campaign Campaign Import Objects and Attributes: How They
Work Together
Campaign Members Campaign Members Import Object and Attributes:
Task Task Import Object and Attributes: How They Work
Together
Note Note Import Object and Attributes: How They Work
Together
Interaction Marketing Activity Interaction Marketing Activity Import Object and
Attributes: How They Work Together
Event Marketing Activity Event Import Object and Attributes: How They
Work Together
Advertising Marketing Activity Advertising Marketing Activity Import Object and
Attributes: How They Work Together
Hint: You can use the keyword "importing campaigns" to search for related
can then be mapped to your source file data. You can use the same source file to
import both custom attributes and the standard import object attributes.
Importing Campaigns Using File-Based Data Import

For the campaign business object, you must use the File-Based Data Import
source file, populates the interface tables based on your mapping, and imports
the data into the application destination tables.
tasks required to configure the import objects, to create source file mappings,
each import object. When creating a marketing campaign, you first import the

DRAFT
Campaign object, followed by subsequent import activities for each of the other
import objects. The exception is attachments, which are imported by including
the file names in your source file for the Campaign object and selecting the files
when defining the import activity.
Administrator or the Marketing Operations Manager job role to access and
submit the import activities for marketing campaigns.

can be used to verify imported data. Users with the Marketing Analysis Duty
role can also navigate to the Campaigns work area to view the imported
campaigns. Oracle Fusion assigns this role to the following, predefined job roles:
Marketing VP, Corporate Marketing Manager, Marketing Operations Manager,
and Marketing Analyst.
Campaign Import
Campaign Import Objects: How They Work Together

You use the following main import objects when you submit file-based import
activities to import your marketing campaigns:
• Campaign
• Campaign Members
• Advertising Marketing Activity
• Event Marketing Activity
• Interaction Marketing Activity
This topic describes each of these import objects . It introduces the following:
• Target objects for the campaign import objects
Two additional import objects, Note and Task, are described in separate topics.

The campaign import objects are used to import marketing campaign
information. The main import objects are split into separate target import objects

DRAFT
for organizing the individual attributes of the different aspects of the campaign.
To map the source data in your import file to the target attributes in Oracle
Fusion Applications, you must understand how the target objects are related and
what attributes are included in each target object.
Campaign Target Import Objects

The Campaign import object is broken down into two target import objects:
Campaign Summary and Campaign Team. The Campaign Summary includes
three stages: Outbound Communications, Event, and Advertising, each of which
includes its own import object: Interaction Marketing Activity, Event Marketing
Activity, and Advertising Marketing Activity, respectively. The following figure
shows the hierarchy of the import objects and target import objects for the
marketing campaign, each represented by their familiar name and their formal
target import object name, shown in parentheses.
A single campaign summary includes specific information about the stages of

the campaign and the marketing team members. The multiple campaign stages
can include information about outbound communications and the campaign
members to whom the communications are sent, events associated with the
campaign, and campaign advertising.
• The Interaction Marketing Activity import object includes two target

import objects: InteractionStage and AllocationActivity.
• The Event Marketing Activity import object includes two target import
objects: EventStage and EventActivity.
• The Advertising Marketing Activity import object includes two target

import objects: AdvertisingStage and AdvertisingActivity.
The Campaign Members import object includes information about campaign

members to whom the communications are sent, and includes a single target

DRAFT
import object, StageMembers. You must import the Interaction Marketing
Activity import object before importing the Campaign Members import object.
The Campaign import object includes one additional target import object,
Campaign Team, which includes information about the marketing team
members associated with the campaign.

file and the combination of the target object and target object attribute. You can
Note

To access the reference guide files for the campaign's target import objects, see
Documentation tab for the Campaign File-Based Data Import asset.
Import Object Target Import Object Description Reference Guide File

Names
Advertising Marketing AdvertisingStage The association with MKT_IMP_STAGES_Reference
Activity the campaign and the
advertising activity
dates.
Advertising Marketing AdvertisingActivity The advertising MKT_IMP_ADVTG_ACTIVITY_Reference
Activity treatment.
Campaign Campaigns Campaigns of interest. MKT_IMP_CAMPAIGNS_Reference
Campaign CampaignTeam Marketing team MKT_IMP_CAMP_TEAM_Reference
members associated with
the campaign.
Campaign Members StageMembers Campaign members MKT_IMP_STG_MEMBERS_Reference
to whom outbound
communications are sent.

DRAFT
Event Marketing Activity EventStage The association with the MKT_IMP_STAGES_Reference
campaign and the event
activity dates.
Event Marketing Activity EventActivity The event venue MKT_IMP_EVT_ACTIVITY_Reference
information.
Interaction Marketing InteractionStage The association MKT_IMP_STAGES_Reference
Activity with the campaign
and the outbound
communication activity
dates.
Interaction Marketing AllocationActivity Information about the MKT_IMP_ALLOC_ACTIVITY_Reference
Activity allocation of treatments
to audiences.
Note Import


your data values?


DRAFT
associated object.

attributes.

DRAFT



DRAFT

DRAFT
21
Importing Marketing Responses
Importing Marketing Responses Using File-Based Import:

Explained
This topic explains how to prepare and import marketing response data from an
Import feature.
A marketing response is a business object that is used to record the reaction

of a prospect or customer to a marketing activity. You enter your response
information using the Response Management work area or you can import data
to create or update responses.
• How does your legacy or source system represent the response compared
to how Oracle Fusion Applications represent the same data?

your data values?

You must understand how your response data corresponds with the data in
Fusion Applications represent the structure of the data for a marketing response.
Importing Marketing Responses 21-1

DRAFT
An Oracle Fusion marketing response consists of two import objects: Response
and Notes. You import your marketing response, followed by a subsequent
import activity for any associated notes.
The Oracle Fusion marketing response structure is hierarchical. At the top level
is the response summary, under which are lower level components such as
products, surveys, and notes. This hierarchical structure supports one-to-many
relationships between the components that make up the response. For example,
a response can have many products, surveys, and notes.
The response summary contains basic information about the response such
as the response method, marketing source code, and responder information.
For each response, you can associate products and surveys, attach documents
relevant to the response, and post notes for the response.
Import Objects for the Response
To facilitate the import of responses, Oracle Fusion Applications incorporate

the structure of the response into import objects. The import objects for the
marketing response are shown in the following table.

Response Response Summary and Responder Details
Note
You can create customers, consumers, and contacts

or associate existing ones to capture your responder
information.
Products
Surveys
Attachments
Note Notes
Attachments
between the structural components that make up the response.

DRAFT

Response Response Import Object and Attributes: How They
Work Together
Together
Hint: You can use the keyword "importing responses" to search for related topics
corresponding import object is updated with extensible attributes, which can
then be mapped to your source file data. You can use the same source file to
import both custom attributes and the standard import object attributes.
Importing Responses Using File-Based Data Import
For the response business object, you must use the File-Based Data Import
to schedule the import activities. You submit file-based import objects, create
source file mappings, and schedule the import activities. You submit file-based
import activities for each import object. When creating a marketing response,
you first import the Response object, followed by subsequent import activities
for any associated notes. The exception is attachments, which are imported by
including the file names in your source file for the Response object and selecting
the files when defining the import activity.
You must be assigned the Marketing Operations Manager or the Customer

Relationship Management Application Administrator job role to access and
submit the import activities for marketing responses.

DRAFT

can be used to verify imported data. Users with the Marketing Response Data
Review Duty role can also navigate to the Response Management work area to
view the imported responses. Oracle Fusion assigns this role to the following
predefined job roles: Marketing VP, Corporate Marketing Manager, Marketing
Operations Manager, and Marketing Analyst.
Response Import
Response Import Objects: How They Work Together

You use two main import objects, Response and Note, when you submit a file-
based import activity to import your marketing responses. This topic describes
the Response import object. It introduces the following:
• Target objects for the Response import object

The Response import object is used to import marketing responses and
information to create or update associated organization or person information
for the customer, consumer, or contact who responded. The Response import
object is split into separate target import objects for organizing the individual
attributes of the different aspects of the response and respondent. To map
the source data in your import file to the target attributes in Oracle Fusion
Response Target Import Objects

The target import objects in the Response import object are generally grouped
into information about the response and information about the respondent. The
respondent information is further broken down, depending on whether the
respondent is a customer organization, a person who is a consumer, or a person
who is a contact of the customer or consumer. The following figure shows the
grouping and the target import objects included in the Response import object,
each represented by their familiar name and their formal target import object
name, shown in parentheses.

DRAFT
A single response includes specific information about how the customer,

consumer, or contact responded to a marketing activity. The response can include
one or more products of interest and survey questions and answers, such as
a telemarketer script. The Response, ResponseProducts, and ResponseSurvey
target objects include the attributes to import this information for your
marketing response.
If the respondent is an organization and an existing customer, then you can
associate the customer with the response by using the Response target object.
However, if you want to update the information for an existing customer
or create a customer record, then you musts use additional target objects to
import customer profile information, addresses, and contact points, such as
a phone and fax number. The following target import objects are for creating
and updating customer information for a respondent: OrganizationProfile,
OrganizationAddress, PrimaryPhone, Fax, and Url.
Similarly, you can associate an existing consumer with the response by using the
Response target object. To update the information for an existing consumer or
create a consumer record, use the following target import objects: PersonProfile,
PersonAddress, Email, PrimaryPhone, Mobile, InstantMessenger, and Fax.
To associate an existing contact for the responding consumer or customer with
the response, you use the Responses target object. To update or create a contact,
use the following target import objects: ContactPersonProfile, ContactJob,
ContactPrimaryAddress, ContactEmail, ContactPrimaryPhone, ContactMobile,
ContactInstantMessenger, and ContactFax.


DRAFT
data and the combination of target object and target object attribute. You can
Note

Documentation tab for the Response File-Based Data Import asset.

ResponseProduct Response products of interest MKT_IMP_RESP_PRODUCT_T_Reference
ResponseSurvey Response survey questions and MKT_IMP_RESP_SVY_LOG_T_Reference
answers
Response Response summary and MKT_IMP_RESPONSES_T_Reference
associated respondent information
OrganizationProfile Customer profile information HZ_IMP_PARTIES_T_Reference
PersonProfile Consumer summary information HZ_IMP_PARTIES_T_Reference
ContactPersonProfile Contact summary information HZ_IMP_RELSHIPS_T_Reference
OrganizationAddress Customer address HZ_IMP_PARTYSITES_T_Reference
PersonAddress Consumer address HZ_IMP_PARTYSITES_T_Reference
ContactPrimaryAddress Contact address HZ_IMP_PARTYSITES_T_Reference
ContactJob Contact job information HZ_IMP_CONTACTS_T_Reference
PrimaryPhone Customer primary phone HZ_IMP_CONTACTPTS_T_Reference
PrimaryPhone Consumer primary phone HZ_IMP_CONTACTPTS_T_Reference
ContactPrimaryPhone Contact primary phone HZ_IMP_CONTACTPTS_T_Reference
Mobile Consumer mobile HZ_IMP_CONTACTPTS_T_Reference
ContactMobile Contact mobile HZ_IMP_CONTACTPTS_T_Reference
Email Consumer e-mail HZ_IMP_CONTACTPTS_T_Reference
ContactEmail Contact e-mail HZ_IMP_CONTACTPTS_T_Reference
InstantMessenger Consumer social network HZ_IMP_CONTACTPTS_T_Reference

ContactInstantMessenger
DRAFT
Contact social network HZ_IMP_CONTACTPTS_T_Reference
Fax Customer fax HZ_IMP_CONTACTPTS_T_Reference
Fax Consumer fax HZ_IMP_CONTACTPTS_T_Reference
ContactFax Contact fax HZ_IMP_CONTACTPTS_T_Reference
Url Customer Web site URL HZ_IMP_CONTACTPTS_T_Reference

Start
• Additional tips




DRAFT

associate records.
following table.

Community
members, using
the Setup and
Maintenance,
Manage Trading
Community Source
Systems task.

DRAFT
unique ID for the
organization.
organization.
Organization or
Partner Profile
object using
the Setup and
Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.


import.

description.

these steps.


DRAFT
HZ_IMP_PARTIES_T.
Additional Tips

• Additional tips


Contact
DRAFT PersonProfile
profiles.

the following:

DRAFT

associate records.
table.

Same Batch
Export Processes
task.
Systems task.
unique ID for the
party (customer,
consumer, contact,
group, or legal
entity) to which
the person profile
belongs.
person party.

PersonLastName
DRAFT
Last name of a Required
person party.


description.

HZ_IMP_PARTIES_T.
target objects.
Additional Tips

DRAFT
Note Import



your data values?


DRAFT
associated object.

attributes.

DRAFT



DRAFT
22
Importing Notes


your data values?

associated object.
Importing Notes 22-1

DRAFT

attributes.

DRAFT


Importing Notes 22-3

DRAFT

DRAFT
23
Importing Partners
Importing Partners Using File-Based Import: Explained

This topic explains how to prepare and import partner data from an external
feature. A partner is an independent corporation that works with one or many
channel organizations. A partner engages with a channel organization in many
ways, such as sales, service, influence, support, and so on. You enter your
partner information using the Partners work area or you can import data to
create new or update existing partners.
• How does your legacy or source system structure the partner information
compared to how Oracle Fusion Applications represents the same data?
your data values?
You must understand how your partner data corresponds with the data in
Fusion Applications represent the structure of the data for a partner.
In Oracle Fusion Applications, partner information is organized into specific
nodes on the Oracle Fusion Partner Center user interface. These nodes include
the partner profile, the partner public profile, partner members, partner
interactions, partner program enrollments, tasks, notes, and contracts. This
hierarchical structure supports one-to-many relationships between the
Importing Partners 23-1

DRAFT
components that make up the partner object. For example, a partner can have
many partner members, tasks, and enrollments.
The Partner Profile and Public Profile are organized into regions that provide
basic information about the partner, such as the partner organization name,
current status, key details about the partner, such as the partner type and level,
and additional information about the partner such as industries and geographies
served, product specialties, expertise, and certifications.
The Partner Members node is organized into regions that provide detailed
information about each partner member. The Person Details region provides the
contact name and contact preferences for phone, and e-mail. You can use the
User Details region to create the contact as an Oracle Fusion Applications user
account, as an Oracle Fusion Applications resource, or as both.
You use the Interactions node to list the interaction history that you have with
the partner and to create new interactions with the partner.
The Enrollments node displays information about the partner programs in

which the partner has enrolled, such as the enrollment participants in the partner
organization, enrollment contracts for the partner program, and any attachments
with enrollment information about the partner program.
Import Objects for Partners
To facilitate the import of partners, Oracle Fusion Applications have organized

the structure of the partner into import objects. The import objects for partners
are shown in the following table.

Profile and Public Profile Industries Served, Expertise, Geographies Served,
Product Specialties, Certifications, Attachments,
Contact Points, Addresses
Partner Members Contact Points, Contact Preferences
Interactions Type, Resolution, Related To, Partner, Contacts,
Resources, Attachments, Extensible fields
Enrollments Enrollment Participants, Enrollment Contracts,
Attachments
Tasks Tasks, Task Notes, Task Attachments
Notes Notes, Note Attachments
Contracts Contract Summary
between the structural components that make up the partner object.


DRAFT

Profile and Public Profile Partner Import Objects: How They Work Together
Partner Members Partner Contact Import Objects: How They Work
Together
Interactions Partner Interaction Import Objects: How They Work
Together
Enrollments Program Enrollment Import Objects: How They
Work Together
Tasks Task Import Object and Attributes: How They Work
Together
Notes Note Import Object and Attributes: How They Work
Together
Contracts Importing Contracts: Explained
Hint: You can use the keyword importing partners to search for related topics in
If you need to extend the partner object to import your legacy or source data,
you must use Oracle Fusion CRM Application Composer to design your
your source file data. You can use the same source file to import both extensible
custom attributes and the standard import object attributes.
Importing Partners Using File-Based Data Import
For the partner business object, you must use the File-Based Data Import feature.
tasks needed to configure the import objects, create source-file mappings, and
import object. When creating new partners, you first import the Partner import
object, followed by subsequent import activities for each of the other import
objects. The exception is attachments, which are imported by including the file
names in your source file for the Partner import object and selecting the files
when defining the import activity.

DRAFT
You must be assigned the Channel Partner Portal Administrator or the Customer
Relationship Management Application Administrator job role to access and
submit the import activities for marketing campaigns.

Relationship Management Application Administrator or Channel Partner Portal
Administrator role can also navigate to Partner Center to view the imported
partners.
Partner Import
Partner Import Objects: How They Work Together

You use three main import objects, Partner, Partner Contact, and Enrollments
when you submit a file-based import activity to import your partner data. This
topic describes the Partner import object. It introduces the following:
• Target objects for the Partner import object

The Partner import object is used to import partner information to populate
the partner profile and partner public profile. The Partner import object is split
into separate target import objects for organizing the individual attributes of
the different aspects of the partner profile and partner public profile. To map
the source data in your import file to the target attributes in Oracle Fusion
Partner Target Import Objects

The target import objects in the Partner import object are generally grouped into
basic information about the partner, such as the partner organization name, and
current status; key details about the partner, such as the partner type and level;
and additional information about the partner, such as industries and geographies
served, product specialties, expertise, and certifications.
The following diagram shows the import objects for the Partner import object.

DRAFT
default values and validations performed by the import process. Review
attributes and the combination of the target object and target object attribute.
Note: If any of the attributes you want to import do not have an equivalent
target object, then review the Oracle Fusion CRM Application Composer
extensibility features for the Partner object.

To access the reference guide files for the partner's target import objects, see the
Documentation tab for the Partner File-Based Data Import asset.
Target Import Object Description Reference Guide File Name

PartnerHierarchy Provides information about HZ_IMP_HIERARCHIES_T_Reference
the hierarchical structure of the
partner relationship
PartnerInterface Provides a variety of information HZ_IMP_PARTIES_T_Reference
used to populate the partner
profile and partner public profile
Fax FAX number for the partner HZ_IMP_CONTACTPTS_T_Reference
PrimaryAddress Partner primary address HZ_IMP_PARTYSITES_T_Reference
PrimaryPhone Partner primary phone number HZ_IMP_CONTACTPTS_T_Reference
ImpPartnerP Provides a variety of information ZPM_IMP_PARTNER_Reference
used to populate the partner
profile and partner public profile
ImpPartnerCertP Partner certifications ZPM_IMP_PARTNER_CERT_Reference
ImpPartnerDimGeoP Partner geographies served ZPM_IMP_PARTNER_DIM_GEO_Reference
ImpPartnerDimIndstP Partner industries served ZPM_IMP_PARTNER_DIM_INDST_Reference

ImpPartnerDimProdP
DRAFT
Partner products ZPM_IMP_PARTNER_DIM_PROD_Reference
ImpPartnerDimSChnlP Partner type information such as ZPM_IMP_PARTNER_DIM_SCHNL_Reference
var, partner, systems integrator,
and so on.
ImpPartnerExpertP Partner expertise ZPM_IMP_PARTNER_EXPERT_Reference
ImpPartnerAcctResP Member function for Account ZPM_IMP_PARTNER_ACCT_RES_Reference
Resources (team)
Url URL to the partner's Web site HZ_IMP_CONTACTPTS_T_Reference
FaxContactPreference FAX number by which the partner HZ_IMP_CONTACTPREFS_Reference
wants to be contacted
PrimaryAddressContactPreference Primary address by which the HZ_IMP_CONTACTPREFS_Reference
partner wants to be contacted
PrimaryPhoneContactPreference Primary phone number by which HZ_IMP_CONTACTPREFS_Reference
the partner wants to be contacted
Partner Contact Import
Partner Contact Import Objects: How They Work Together

You use three main import objects, Partner, Partner Contact, and Program
Enrollments, when you submit a file-based import activity to import your
partner data. This topic describes the Partner Contact import object. It introduces
the following:
• Target objects for the Partner Contact import object
Target Import Objects Concepts

The Partner Contact import object is used to import the contact information
to populate the Partner Members node in Oracle Fusion Partner Relationship
Management Partner Center. To map the source data in your import file to the
Partner Contact Target Import Objects

The target import objects in the Partner Contact import object provide key
contact information for the partner organization, including how they can be
contacted, such as by phone, e-mail, or FAX, and the way that they prefer to be
contacted.

DRAFT
The following diagram shows the import objects for the partner contact import
object.
The Partner Members node is organized into regions that provide detailed
information about each partner member. The Person Details region provides
the contact name and contact preferences for phone and e-mail. You can use the
User Details region to create the contact as an Oracle Fusion Applications user
account, as an Oracle Fusion Applications resource, or as both.

default values and validations performed by the import process. Review
file data and the combination of the target object and the target object attribute.
Note
extensibility features for the partner contact.

To access the reference guide files for the partner contact's target import objects,
Documentation tab for the Partner Contact File-Based Data Import asset.

PersonProfile Consumer information HZ_IMP_PARTIES_T_Reference
Fax Consumer FAX HZ_IMP_CONTACTPTS_T_Reference

InstantMessenger
DRAFT
Instant messenger account for the HZ_IMP_CONTACTPTS_T_Reference
partner organization
Mobile Mobile phone number for the HZ_IMP_CONTACTPTS_T_Reference
PrimaryPhone Primary phone number for the HZ_IMP_CONTACTPTS_T_Reference
Partner Allows you to associate a contact HZ_IMP_RELSHIPS_T_Reference
to a partner
Job Information about the partner HZ_IMP_CONTACTS_T_Reference
contact's job such as Department,
Job Title, Start Date and End Date.
ResourceProfile Resource information HZ_IMP_RESOURCES_Reference
ResourceOrganizationMembership Resource organization to which HZ_IMP_GROUP_MEMBERS_Reference
the partner belongs
ResourceTeamMembership Resource team to which the HZ_IMP_TEAM_MEMBERS_Reference
partner belongs
PrimaryAddress Primary address for the partner HZ_IMP_PARTYSITES_T_Reference
organization
EmailContactPreference E-mail address by which the HZ_IMP_CONTACTPREFS_Reference
partner prefers to be contacted
FaxContactPreference FAX number by which the partner HZ_IMP_CONTACTPREFS_Reference
prefers to be contacted
MobileContactPreference Mobile phone number by which HZ_IMP_CONTACTPREFS_Reference
the partner prefers to be contacted
PrimaryPhoneContactPreference Primary phone number by which HZ_IMP_CONTACTPREFS_Reference
the partner prefers to be contacted
PrimaryAddressContactPreference Primary address by which the HZ_IMP_CONTACTPREFS_Reference
partner prefers to be contacted

• Additional tips

Import Object
DRAFT Target Object
profiles.

the following:

DRAFT

associate records.
table.

Same Batch
Export Processes
task.
Systems task.
unique ID for the
party (customer,
consumer, contact,
group, or legal
entity) to which
the person profile
belongs.
person party.

PersonLastName
DRAFT
person party.


description.

HZ_IMP_PARTIES_T.
target objects.
Additional Tips

DRAFT
Program Enrollments Import
Program Enrollments Import Objects: How They Work Together
You use three main import objects, Partner, Partner Contact, and Program
Enrollments, when you submit a file-based import activity to import your
partner data. This topic describes the Program Enrollments import object. It
introduces the following:
• Target objects for the Program Enrollments import object

The Program Enrollments import object is used to import contact information
to populate the Enrollments node in Oracle Fusion Partner Relationship
Management Partner Center. To map the source data in your import file to the
Program Enrollments Target Import Objects

The target import objects in the Program Enrollments import object include
information about the partner programs in which the partners are enrolled, such
as details about the enrollment contracts, who is enrolled in these programs, and
attachments containing enrollment information.

DRAFT
The following diagram shows the import objects for the Program Enrollments
import object.
The Enrollments node in Oracle Fusion Partner Center displays information

about the partner programs into which the partner has enrolled, such as the
enrollment participants in the partner organization, enrollment contracts for the
partner program, and any attachments with enrollment information about the
partner program.

Note
extensibility features for the program enrollments.

To access the reference guide files for the program enrollments' target import
Documentation tab for the Program Enrollments File-Based Data Import asset.

ImpProgramEnrollmentsPVO2 Information about the program in ZPM_IMP_PROGRAM_ENROLLMENTS_Reference
which the partner is enrolled
ImpProgramEnrollmentContractPVO3
Information about the enrollment ZPM_IMP_PGM_ENRLMNT_CNTRCT_Reference
contract for the program in which
the partner is enrolled

DRAFT
ImpProgramEnrollmentParticipantsPVO3
Participants in the partner ZPM_IMP_PGM_ENRLMNT_PRTCPNTS_Reference
organization who are enrolled in
the partner program
Interaction Import

feature.
interactions.
your data values?

DRAFT

Interaction.


Together
attributes.

DRAFT
Maintenance task.
import processing.



opportunity.

DRAFT


Note

DRAFT

Note Import



your data values?


DRAFT
associated object.

attributes.

DRAFT



DRAFT
24
Importing Product Groups
Importing Product Groups Using File-Based Import: Explained

This topic explains how to prepare and import product group data from an
Import feature.
A product group is a business object that groups related products, so that you
can work with them together. You can use product groups to create a multilevel
hierarchy that can be used as a sales catalog, a rollup hierarchy, or a promotion
catalog. For example, you might create a product group named Consumer
Electronics that includes all of your consumer electronics products so that
customers can browse through all the products in this group in your product
catalog.
your data values?
You must understand how your promotion data corresponds with the data in
Oracle Fusion Applications represent the structure of the data for a promotion.
The structure of the Oracle Fusion Applications product group is hierarchical.
At the top level is the product group, which must exist before you can associate
lower-level components, including products, promotions, and subgroups. A
subgroup is another product group that is lower in the hierarchy).
The hierarchical structure of product groups import objects supports one-
to-many relationships between the root product group and the subgroups
and products for that product group. For example, a product group can have
Importing Product Groups 24-1

DRAFT
many subgroups and products. The subgroups can have many subgroups
and products. The following diagram shows that product groups can contain
products or can contain other product groups.
Import Objects for the Product Group

To facilitate the import of product groups, Oracle Fusion has incorporated the
structure of the product group into import objects. The import object for the
product group is Product Group.
If you want products (also known as items) to be visible in a catalog that is
represented by a product group hierarchy, then those products must be imported
before the product groups are imported, or they must already exist in the Oracle
Fusion Product Information Model. In other words, products must be present in
Oracle Fusion before you import the product groups with which those products
are associated. The objects of the product group hierarchy do not have to be
imported in any specific order. However, you must make sure that all product
groups referenced in a product group hierarchy are imported.
between the structural components that make up the product group.
For information about the Oracle Fusion attributes, see the Oracle Enterprise
Repository. The reference files contain descriptions, logic used in choosing
default values, and validation information for each of the Oracle Fusion
attributes. The validation information includes the navigation to the task where
you can define values in Oracle Fusion. For example, if you have values in
your data that correspond to a choice list in Oracle Fusion, then the validation
information for that attribute provides the task name in the setup work area
where you can define your values. For additional information including a list of
reference file names and locations that you need to complete this task, see the
following table.

Product Group Product Group Import Object and Attributes: How
They Work Together

DRAFT
attributes.
Importing Product Groups Using File-Based Data Import
For the promotion business object, you must use the File-Based Data Import
import object. When creating a new promotion, you import the Promotion object.
You must be assigned the Sales Catalog Administrator or Customer Relationship
Management Application Administrator job role to access and submit the import
activities for product groups.
Relationship Management Application Administrator or Marketing Operations
Manager job role can also navigate to the Product Group work area to view the
imported product groups.
Product Group Import Objects: How They Work Together

You use one main import object, Product Group, when you submit a file-based
import activity to import your product groups. This topic describes the Product
Group import object. It introduces the following
• Target objects for the Product Group import object
A single product group can include associated products and subgroups. You
can use product groups to create a multilevel hierarchy of product groups and
products that can be used as a sales catalog, a rollup hierarchy, or a promotion
catalog.
The Product Group import object is used to import product groups and
associated subgroups. The Product Group import object is split into separate
target import objects for product groups, product group products, and product
group subgroups associated with the product groups. To map the source data in
your import file to the target attributes in Oracle Fusion Applications, you must

DRAFT
each target object.
Product Group Target Import Objects
The target import objects in the Product Group import object are generally
grouped into information about the Product Group, Product Group
Products, and Product Group Subgroups business objects, which are
represented by the ProductGroupBulkImport, ProductGroupItemBulkImport,
ProductGroupRelationBulkImport target import objects, respectively. The Product
Group Item business object holds the products in the product group, and the
Product Group Relation business object holds other product groups that are
subgroups of the product group. The following figure shows the grouping and
the target import objects included in the Product Group import object, each
The following figure shows the product groups, and product group products
and subgroups, that can be grouped in a product group import object.
INSERT GRAPHIC HERE
Before importing product groups, ask yourself the following questions:
• Do you have a product group to import? ProductGroupBulkImport includes
the basic definition of the product group, such as name, description,
active flag, and dates.
• Do you have any product associated with this product group?
ProductGroupItemsBulkImport allows you to identify the products that
must be associated with the product group. It includes the product ID that
must be associated with the product group.
• Do you have any product groups that are subgroups of this product
group? ProductGroupRelationsBulkImport allows you to identify the
product groups that must be associated with this product group as its
children.
Note
extensibility features for the product group.

DRAFT
Applications: http://fusionappsoer.oracle.com.
Documentation tab for the Product Group File-Based Data Import asset.

ProductGroupBulkImport Product Group QSC_IMP_PROD_GROUPS_Reference
ProductGroupItemBulkImport Product Group Product QSC_IMP_PROD_GROUP_ITEMS_Reference
ProductGroupRelationBulkImport Product Group Subgroup QSC_IMP_PROD_GROUP_REL_Reference
Importing Product Groups: Worked Example

You are the inventory manager of a small retail business. Your enterprise
is importing its active sales catalogs from a legacy application into Oracle
Fusion Customer Relationship Management (CRM). The Electronics sales
catalog consists of two main categories, Computers and Phones. The Computer
category has two subcategories, Laptop Computers and Desktop Computers.
Each category has multiple products, but in this example, you import just two
products into the Phones category.
In the legacy application, Electronics is a Sales Catalog record, while Computers,
Phones, Laptop Computers, and Desktop Computers are Category records.
In Oracle Fusion CRM, both of these record types are replaced by Product
Groups of the hierarchical type, because Oracle Fusion CRM catalogs consist of a
hierarchy of product groups.
Because your enterprise is a small company with a relatively small data set, you
enter the legacy data manually into a spreadsheet and then import the data from
the spreadsheet into Oracle Fusion CRM. A larger company with more data
would export the data from its legacy application into a spreadsheet and then
import the data from the spreadsheet into Oracle Fusion CRM. Companies with
very large volumes of data can export their legacy data to an XML file and then
import it into Oracle Fusion CRM in that format.
Before importing these product groups, you have imported products from your
legacy system. In this example, you import the values needed to associate these
previously imported products with the product groups that are currently being
imported.
The following table summarizes key decisions for this scenario:
Decision Resolution
How do I know which information from the legacy Identify the fields in Oracle Fusion CRM that map
application to import into Oracle Fusion CRM? to the data you are importing from the legacy
application.

DRAFT
How can I indicate the hierarchical relationships Assign a reference number to each product group.
among the product groups? Use those numbers to indicate which product groups
are parents and children in the hierarchy.
How can I indicate the associations of products with Associate existing product numbers with the
the product groups? reference numbers of the appropriate product
groups.
The following tasks show how to import product groups, the hierarchical
relationships of those product groups, and the associations of products with their
product groups:
• Prerequisites
• Finding Reference Information for Product Group Imports
• Entering Product Group Information to Import
• Setting Up the Product Group Import in Oracle Fusion CRM
• Importing Product Group Data into Oracle Fusion CRM
• Viewing the Imported Product Groups
Prerequisites
Before importing product groups, perform the following prerequisite tasks:
1. Import products from the legacy system into Oracle Fusion CRM.
2. Identify the product numbers for the imported legacy products in Oracle
Fusion CRM.
Finding Reference Information for Product Group Imports

To import product groups, you begin by locating and viewing the content of the
appropriate reference spreadsheets to determine which fields you need to import
to map your legacy product groups to Oracle Fusion CRM product groups.
When referring to the spreadsheets, consider the following issues:
• Determine the required target attributes for creating new records in
QSC_IMP_PROD_GROUPS_Reference.xls. In the File-Based Import
Source File Candidate column, see the Required and Conditionally
Required values.
• Determine additional target attributes that you might need to conform to
the business model of your company. View the attributes descriptions and
defaulting logic. In the File-Based Import Source File Candidate column,
see the Yes values.
• Review defaulting logic for information you are not going to import.
For example, if you decide not to import inactive product groups, then
accept the default value of Y for the Active flag, rather than importing
values for this flag.
• Review File-Based Import Attribute Length and Data Types.
• Understand how to approach your values for Primary Language and
Translated. Note that the product group display name, product group
description, language, and source language flag attributes work together.
For example, if US English is the primary language, then enter Y as the
source language flag, and enter the product group name and description
in US English. In the same implementation, if the language is the code for

DRAFT
Spanish, then enter N as the source language flag, and enter the product
group name and description in Spanish.
• Review the validation column to see what values are valid for each field.
• To find predefined language codes, see the Setup and Maintenance task
listed in the validation column of the spreadsheet.
1. Navigate to the Oracle Enterprise Repository at http://
fusionappsoer.oracle.com and search for the string
QSC_IMP_PROD_GROUP to find the spreadsheets that contain reference
information for importing product groups and related objects.
2. Look at the search result to find that you must refer to the spreadsheets
listed in the following table for Product Group import:
Spreadsheet References
QSC_IMP_PROD_GROUPS_Reference.xlsProduct groups
QSC_IMP_PROD_GROUP_REL_Reference.xls
Hierarchical relationships of product
groups
QSC_IMP_PROD_GROUP_ITEMS_Reference.xls
Relationships of products to product
groups
3. Look in the QSC_IMP_PROD_GROUPS_Reference.xls spreadsheet, which

contains information about the Product Group, and you find you need
the file-based import attributes with the display names shown in the
following table.
Attribute Display Name Description

PgInternalName The unique internal name of the
product group.
PgRefNumber The unique reference number that
identifies the product group. Used to:
• Identify the product group and

the related subgroups and items
imported in the same batch.
• Identify the product group for

additional translated product
group names and descriptions
imported in the same batch.
• Derive the product group ID

(PROD_GROUP_ID) when
updating an existing product
group.
ProdGroupName The product group name displayed in
the catalog.
Language The code that represents the language
for the contents of the translatable
columns PROD_GROUP_NAME and
PROD_GROUP_DESC_TEXT.

DRAFT
SourceLangFlag Indicates whether the language
(LANGUAGE) for the record is the
primary language for the product
group name (PROD_GROUP_NAME)
and product group description
(PROD_GROUP_DESC_TEXT).
ProdGroupDescText Text that describes the product group.
SourceObjectType Indicates whether the product group
being imported is a product line or a
sales catalog.
AllowDupContentFlag Indicates whether to allow duplicate
children, that is, whether products
or product groups are allowed to be
added to the product group hierarchy
more than once.
Note
You must enter N as the value for

AllowDupContentFlag. This is because
duplicate children are not supported in
Oracle Fusion CRM sales catalogs.
4. Look at the QSC_IMP_PROD_GROUP_REL_Reference.xls spreadsheet,

which contains information for creating hierarchical relations among
product groups, and you find you need the fields in the following table:
File-Based Import Attribute Display Description

Name
PgRefNumber The reference number of the parent
product group, used to derive the
PROD_GROUP_ID.
PgRelChildRefNumber The unique internal name of the
subgroup, used to derive the
PROD_GROUP_REL_ID.

DRAFT
RelationTypeCode The lookup code that represents the
relationship type between product
groups.
• A hierarchical relationship type

indicates the product groups are
arranged in a hierarchy.
• A revenue relationship type

indicates the product group of
a specific revenue type can be a
related to another product group.
• A service relationship type

indicates the products in one
service product group cover
products in another product
group.
Language The code that represents the language
for the contents of the translatable
columns (PROD_GRP_REL_NAME).
SourceLangFlag Indicates whether the language
(LANGUAGE) for the record
is the primary language for
the product group name
(PROD_GRP_REL_NAME).
5. Look at the QSC_IMP_PROD_GROUP_ITEMS_Reference.xls spreadsheet,

which contains information needed to relate products to product groups,
and you find you need the following fields:
File-Based Import Attribute Display Description

Name
PgRefNumber The reference number of the parent
product group, used to derive the
PROD_GROUP_ID.
ItemNumber The unique number that identifies
the product item. Used to derive
the INVENTORY_ITEM_ID and
the associated item organization
(INV_ORG_ID).
Entering Product Group Information to Import

Next, you create a spreadsheet and enter the values you want to import into
Oracle Fusion CRM. You can use meaningful names in the header row of this
spreadsheet, and you will map these user-defined names to the attribute display
names in a later task.
1. On your local drive C:\, add a directory named Exports and, in that
directory, create a spreadsheet file named Product_Catalog_Import.xls.
2. In the header row, enter a header representing each of the fields to import,
using the following values as the names of the columns: Internal Name,

DRAFT
Reference Number, Product Group Name, Language, Primary Language
Flag, Product Group Description, Object Type, Allow Duplicate Children,
Parent Reference Number, Child Reference Number, Relationship Type,
Relationship Language, Relationship Primary Language Flag, Parent
Reference Number, and Product Number.
Note: Be sure these headers are in Row 1 of the spreadsheet.

3. In rows 2 through 6, enter the values shown in the following table, which
represent product groups.
Internal ReferenceProduct Language Primary Product Object Allow

Name Number Group Language Group Type Duplicate
Name Flag Description Children
Vision_Electronics
E1000 ElectronicsUS Y All Sales N
electronicsCatalog
products
Vision_Electronics_Computers
EC10001 ComputersUS Y All Sales N
computer Catalog
products
Vision_Electronics_Computers_Laptops
ECL100001Laptop US Y Laptop Sales N
Computers computersCatalog
and
accessories
Vision_Electronics_Computers_Desktop
ECD100002 Desktop US Y Desktop Sales N
Computers computersCatalog
and
accessories
Vision_Electronics_Phones
EP10002 Phones US Y All Sales N
smart Catalog
phones
products
4. In rows 7 through 10, enter the values shown in the following table, which
represent the hierarchical relationships among product groups.
Parent Child Relationship Relationship Relationship

Reference Reference Type Language Primary
Number Number Language
Flag
E1000 EC10001 PRODUCT_GROUP_HIERARCHY
US Y
EC10001 ECL100001 PRODUCT_GROUP_HIERARCHY
US Y
EC10001 ECD100002 PRODUCT_GROUP_HIERARCHY
US Y
E1000 EP10002 PRODUCT_GROUP_HIERARCHY
US Y
5. In rows 11 and 12, enter the values shown in the following table, which
represent the association of existing product with a product group
included in this example.

DRAFT
Parent Reference Number Product Number
EP10002 AS66312
EP10002 AS66313
6. When you have finished, save the spreadsheet file as a Comma Separated
Value (CSV) file named C:/Exports/Product_Catalog_Import.csv.
Setting Up the Product Group Import in Oracle Fusion CRM

Next, you map the column headers in the CSV file to the names of the equivalent
fields in Oracle Fusion CRM.
1. Log on to Oracle Fusion CRM with the CRM Application Administrator
responsibility.
2. Open the Navigator menu and choose Setup and Maintenance.
3. On the Setup and Maintenance page, search for Define File-Based Data
Import.
4. In the Search Results list, under Define File-Based Data Import, click the
Go to Task icon for Manage File Import Activities.
5. In the Manage Import Activities list, create a new record.
6. In the Enter Import Options form, enter the values in the following table,
and then click Next.
Field Value
Name Name for the import operation. For
this example, enter PL 100 Product
Catalog.
Object Product Group
File Type Text file
File Selection Specific file
Upload From Desktop
Data Type Comma separated
Header row included Selected
Note
You select the Header row included

check box so the names you entered
in the first row of the spreadsheet
are used to identify the spreadsheet
columns in the next step of this task.
Import Mapping N/A

File Name Name and directory location
of the imported CSV file. For
this example, enter C:/Exports/
Product_Catalog_Import.csv.

DRAFT
7. In the Map Fields list, map the names of the values in the spreadsheet
header to the equivalent attribute names in Oracle Fusion CRM, as shown
in the following table, and then click Next.
Column Header Object Attribute

Internal Name ProductGroupBulkImport PgInternalName
Reference Number ProductGroupBulkImport PgRefNumber
Product Group Name ProductGroupBulkImport ProdGroupName
Language ProductGroupBulkImport Language
Primary Language Flag ProductGroupBulkImport SourceLangFlag
Product Group ProductGroupBulkImport ProdGroupDescText
Description
Object Type ProductGroupBulkImport SourceObjectType
Allow Duplicate ProductGroupBulkImport AllowDupContentFlag
Children
Parent Reference ProductGroupRelationBulkImport
PgRefNumber
Number
Child Reference Number ProductGroupRelationBulkImport
PgRelChildRefNumber
Relationship Type ProductGroupRelationBulkImport
RelationTypeCode
Relationship Language ProductGroupRelationBulkImport
Language
Relationship Primary ProductGroupRelationBulkImport
SourceLangFlag
Language Flag
Parent Reference ProductGroupItemBulkImport
PgRefNumber
Number
Product Number ProductGroupItemBulkImport
ItemNumber
Importing Product Group Data into Oracle Fusion CRM

Next, you run the import process. It is possible to import the product group
records but not activate them until later, but in this example, the product groups
are activated immediately.
1. Click Next to skip the Schedule page.
2. In the Review and Activate page, click Activate.
3. In the Manage Import Activities list, locate the row with the Name value
of PL 100 Product Catalog and view the value in the Status column.
4. When the Status value changes to Completed, the import is done.
5. Click the Status value link to display the View Import Status page, where
you can view details of the import process.
Viewing the Imported Product Groups

After the import has been completed, you view the product groups in Oracle
Fusion CRM to verify that the ones you imported are there.

DRAFT
1. Open the Navigator menu and choose Setup and Maintenance.
2. On the Setup and Maintenance page, search for Manage Product Groups.
3. In the Search Results list, click the icon in the Go to Task column.
4. In the Manage Product Groups region, in the unlabeled field above Name
column of the list, enter Vision_Electronics to see the product groups you
added.
Note: Because all the product groups you added have Internal Name
values beginning with Vision_Electronics, they are all displayed.
5. Select the Vision_Electronics product group and click the tree icon to
see the product groups as a hierarchy, to verify that the hierarchical
relationships you indicated have been imported correctly.

DRAFT

DRAFT
25
Importing Promotions
Importing Promotions Using File-Based Import: Explained

This topic explains how to prepare and import marketing promotion data from
an external data source into Oracle Fusion Applications using the File-Based
Data Import feature.
A promotion is a business object that is used to offer special pricing to your
customers to promote products, such as a percentage discount, free shipping, or
a coupon.
your data values?
You must understand how your promotion data corresponds with the data in
Oracle Fusion Applications represent the structure of the data for a promotion.
In Oracle Fusion Applications, one table stores the promotion definition and
another table optionally stores coupon details for that promotion. A coupon is
an entitlement to a specific discount, which businesses give to their customers
as part of a promotion. Zero, one, or many coupons can be associated with any
given promotion.
Import Objects for the Promotion
To facilitate the import of promotions, Oracle Fusion Applications incorporate
the structure of the promotion into import objects. The import object for the
promotion is Promotion.
Importing Promotions 25-1

DRAFT
between the structural components that make up the promotion.
logic used in choosing default values, and validation information for each
of the Oracle Fusion Applications attributes. The validation information
includes the navigation to the task where you can define values in Oracle Fusion
where you can define your values. For additional information including a list of

Promotion Promotion Import Object and Attributes: How They
Work Together
Note
You can use the keyword importing promotions to search for related topics in
Oracle Fusion Application Help.
Oracle Fusion Applications do not support extensible attributes for promotion
objects. You can import data only for promotion model objects that already exist
by default in Oracle Fusion Applications.
Importing Promotions Using File-Based Data Import

For the promotion business object, you must use the File-Based Data Import
import object. When creating a new promotion, you import the Promotion object.
Administrator or Marketing Operations Manager job role to access and submit
the import activities for promotions.

Relationship Management Application Administrator or Marketing Operations
Manager job role can also navigate to the Promotions work area to view the
imported promotions.

DRAFT
Promotion Import Objects: How They Work Together
You use one main import object, Promotion, when you submit a file-based
import activity to import your promotions. This topic describes the Promotion
import object. It introduces the following:
• Target objects for the Promotion import object
The Promotion import object is used to import promotions and coupon codes
associated with the promotions. The Promotion import object is split into
separate target import objects for organizing the individual import attributes. To
map the source data in your import file to the target attributes in Oracle Fusion
Promotion Target Import Objects
The target import objects included in the Promotion import object are grouped
into information about the promotion (PromotionBulkImport) and information
about the coupon code (PromotionCouponBulkImport).
A single promotion contains basic information such as the promotion name,

description, and active status. A promotion name and description can have
translated values for the languages of your users. A promotion can optionally
have associated coupon codes.

DRAFT

To access the reference guide files for the promotion's target import objects, see
Documentation tab for the Promotion File-Based Data Import asset.

PromotionBulkImport Promotions and translated MOP_IMP_ PROMOTIONS_
promotion names and Reference
descriptions
PromotionCouponBulkImport Coupon codes associated with MOP_IMP_
promotions PROMO_COUPONS_Reference
Importing Promotions and Coupon Codes Using File-Based Import:

Quick Start
This topic describes some key concepts and provides guidance to get you
started with importing promotions and coupon codes. It includes the following
information:
• Additional tips
Promotion names and associated coupon codes provide tracking for offers
extended to customers. You can import promotion and coupon code records,
import object and target objects for promotions and coupon codes.
Import Object Target Objects

Promotion PromotionBulkImport
PromotionCouponBulkImport
To explain how you can identify and associate records, consider the following
example. You are promoting a new product during for your Spring sales event
in Canada. The promotion name has both English and French translations.
Coupons for a free gift will be provided to some customers. When you import
the promotional data, a record is created for the promotion, in the primary

DRAFT
language, and a record is created for each coupon code. Additional records are
created for each translation of the promotion name that you import.
The promotion number, which you provide in your source file, is used by the
import process to identify and process the related information in your source file.
If you are importing translated values or coupons in subsequent batches, you
can still provide a promotion number for the promotion, or the import process
will generate one when creating the promotion. If you later import translated
values, coupon codes, and updates to the promotion, you provide the promotion
number in your source file. The import process uses the number to uniquely
identify the existing promotion record.
The following table shows how to use the promotion number to identify and
associate records for various scenarios. An asterisk (*) indicates data included
with the translated value and coupon code for the purpose of identifying the
related promotion.
Scenario Promotion in the Promotion in Additional Promotional Coupon

Primary Language Languages Codes
You import the Promotion Number:
promotion in English, SPRING_SALES_EVENT
providing the promotion
number. Promotion Name: Spring
sales event
Language: US
Source Language: Y
You import the Promotion Number: *Promotion Number: * Promotion Number:
promotion in English and SPRING_SALES_EVENT SPRING_SALES_EVENT SPRING_SALES_EVENT
a French translation, plus
two coupons codes, in Promotion Name: Spring Promotion Name: Vente Coupon Code:
the same import batch. sales event de printemps US_SPRING_FREE_GIFT
Language: US Language: FR * Promotion Number:

SPRING_SALES_EVENT
Source Language: Y Source Language: N
Coupon Code:
FR_SPRING_FREE_GIFT
You import a French *Promotion Number: * Promotion Number:
translation, plus SPRING_SALES_EVENT SPRING_SALES_EVENT
two coupons codes,
for an existing Promotion Name: Vente Coupon Code:
promotion (a promotion de printemps US_SPRING_FREE_GIFT
previously imported
with a promotion Language: FR * Promotion Number:
number value of SPRING_SALES_EVENT
Source Language: N
SPRING_SALES_EVENT)
Coupon Code:
FR_SPRING_FREE_GIFT
You import the Promotion Number:
promotion in English. 30000987
You do not provide
a promotion number Promotion Name: Spring
value. The import sales event
process generates a
promotion number Language: US
value.
Source Language: Y

You import a French
DRAFT *Promotion Number: * Promotion Number:
translation, plus two 30000987 30000987
coupons codes, for an
existing promotion (a Promotion Name: Vente Coupon Code:
promotion previously de printemps US_SPRING_FREE_GIFT
imported with a
generated promotion Language: FR * Promotion Number:
number value). 30000987
Source Language: N
Coupon Code:
FR_SPRING_FREE_GIFT
The minimum that is required to import promotion and coupon information

depends on the purpose of the import. The data requirements are different
when you are creating new promotion and coupon records, adding translated
promotion data, or updating existing promotion records.
table lists the minimum attributes required to import promotion and coupon
data. Entries in the table are based on four 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. A numbered
footnote (n) indicates that an option is provided. More information about the
option is listed after the following table.
Attribute Description Data Value Create Update Create Create

Prerequisite Promotion Existing Promotion Coupon
Records Promotions Translations Codes
PromotionNumThe Assign Conditionally Required Required Required
promotion unique required.
number to promotion
uniquely number See footnote
identify the values for [1].
promotion. each new
promotion.
Identify the
value for
an existing
promotion.
You can view
the number
in the Edit
Promotion
page, using
the Setup and
Maintenance,
Manage
Marketing
Promotions
task.

PromotionNameThe
DRAFT Required Required
promotion
name.
PromotionStatusCode
The current Review or Required
promotion define the
status. lookup code
that best
represents
the current
status of the
promotion
using the
Setup and
Maintenance,
Manage
Marketing
Promotion
Standard
Lookups
task.
Language The code that Review valid Required Required
represents language
the language codes using
of the the Setup and
promotion Maintenance,
name. Manage ISO
Languages
task.
SourceLangFlagIndicates Required Required
whether the
language is
the primary
language.
Valid values
are Y (yes)
and N (no).
PromoCouponCode
The unique Required
coupon code.
[1] If importing a translated value or a coupon code in the same batch as the
promotion, you must provide the promotion number for the promotion.
promotion attributes that are available to import and the possible prerequisite
steps for those attributes. This reference file includes the following information:
• All promotion attributes available for import.
description.

DRAFT
To access the reference file for promotions, follow these steps.
1. In your browser, enter http://fusionappsoer.oracle.com. Sign in as a user

or a guest to Oracle Enterprise Repository.
MOP_IMP_PROMOTIONS

4. Select the MOP_IMP_PROMOTIONS_Reference file.
Additional Tips
The Help Application is available from any Oracle Fusion Application page by
clicking Help in the top right corner, and selecting Applications Help. You can
explore related topics by entering the following keywords in the Oracle Fusion
Help Application search.
• Importing promotions

DRAFT
26
Importing Resource Teams
Importing Resource Teams Using File-Based Import: Explained

This topic explains how to prepare and import resource team data from an
Import feature. A resource team is a temporary group of resources that is formed
to work on work objects. A resource team may contain a resource organization
or resources or both. A resource team cannot be hierarchically structured and
is not intended to implement an organization. You enter your resource team
information using the Setup and Maintenance work area, Manage Resource
Teams task, or you can import data to create new or update the existing resource
teams.

• How does your legacy system or source system represent the resource
team compared to how Oracle Fusion Applications represent the same
data?
your data values?
You must understand how your resource team data corresponds with the data
Oracle Fusion Applications represent the structure of the data for a resource
team.
Importing Resource Teams 26-1

DRAFT
In Oracle Fusion Applications, one table stores the resource team definition and
other tables optionally store profile details for that resource team. Profile details
for a resource include information about a resource team's organization and team
memberships.
Import Objects for the Resource Team

To facilitate the import of resource teams, Oracle Fusion Applications
incorporate the structure of the resource team into import objects. The import
object for the resource team is Resource Team.
between the structural components that make up the resource team.


Resource Team Resource Team Import Objects: How They Work
Together
Hint: You can use the keyword importing resource teams to search for related
attributes.
Importing Resource Teams Using File-Based Data Import
For the resource team business object, you must use the File-Based Data Import

DRAFT
each import object. When creating a new contact, you import the Resource Team
object.
access and submit the import activities for resource teams.

can be used to verify imported data. Users with the Master Data Management
Administrator job role can also navigate to the Manage Resource Teams work
area to view the imported resource teams.
Resource Team Import Objects: How They Work Together
This topic describes the Resource Team import object. You use two main import
objects, ResourceTeam and ResourceTeamUsage, when you submit a file-based
import activity to import resource team information.
• Target objects for the Resource Team import object

The Resource Team import object is used to import resource teams and
information to create or update associated organizations or persons. The
Resource Team import object is split into separate target import objects for
organizing the individual attributes of the different aspects of the resource team
and the resource team's usage. To map the source data in your import file to the
Response 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

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

Note

To access the reference guide files for the resource team's target import objects,
Documentation tab for the Resource Team File-Based Data Import asset.

ResourceTeam Captured information that HZ_IMP_TEAMS_Reference
identifies a resource team.
Sample attributes: TeamId,

TeamName, TeamDescription, and
Language.
ResourceTeamUsage Contains information that HZ_IMP_TEAM_USAGES_Reference
indicates the usage of the resource
team.
Sample attributes: RequestId,

TeamUsageId, TeamId, and Usage.

DRAFT
Importing Resource Teams and Resource Team Usages Using File-
Based Import: Quick Start
with importing resource teams and resource team usages.
• Resource teams and resource team usages overview
• Additional tips
can use to import resource teams and resource team usages.

Resource Team ResourceTeam
Resource Teams and Resource Team Usages Overview
A resource team is a group of resources formed to work on work objects.

A resource team may comprise resource organizations, resources, or both.
A resource team cannot be hierarchically structured and is not intended to
implement an organization structure. You can also use resource teams as a
quick reference to groups of related resources that you can quickly assign work
objects to. A resource team usage denotes how a resource team is being used
within the deploying company. For example, you may have a resource team
comprising resources and resource organizations in your organization, dedicated
to managing all the sales in one part of the world. This resource team could be
assigned the usage: Sales.
To add resource teams and resource team usages to a party using file-based
import, you must provide a team name and team number. Use the resource
team's unique Oracle Fusion record ID to add usages to the resource team in
subsequent batches.
When you create the resource team and the resource team usage assignment
using file-based import, group the resource team and resource team usage
data together in your source file. The import process is then able to first import
the resource team, and then identify the resource team record to import the
associated resource team usage record.

DRAFT
The minimum that is required to import resource team and resource team usage
information depends on the purpose of the import. The data requirements are
different when you are importing the resource team and team usages in the same
import batch, or adding team usages to an existing resource team.
Note
Resource team and resource team usage data cannot be updated using file-based
import.
The following tables list the minimum attributes required to import resource
team data based on the purpose of your import, any prerequisite setup or
tables.
Resource Team Target Description Data Value Prerequisite Create Resource Team
Object Attribute
TeamName The name of the resource Required
team.
TeamNumber The resource team's Generate a unique team Required
unique identifier value. number value for each
new team.
Language The code that represents View valid language Required
the language for the codes from the Setup
team name and team and Maintenance,
description values. Manage ISO Languages
task.
SourceLangFlag Indicates whether the Required
language for the record is
the primary language for
the team name and team
description values.
The following tables list the minimum attributes required to import resource
team data based on the purpose of your import, any prerequisite setup or
tables.
Resource Team Description Data Value Create Party and Add Resource
and Resource Prerequisite Add Resource Team and Resource
Team and Resource

Team Usage Target
Object Attribute
DRAFT Team Usage in the
Same Batch
Team Usage to an
Existing Party
TeamNumber The resource team's Identify the Conditionally
unique identifier team number Required. See
value. for an existing footnote [1].
resource team
using the Setup
and Maintenance,
Manage Resource
Teams task, and
by exporting
the Resource
Team object using
the Setup and
Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.
TeamId The unique ID Identify the ID Conditionally
for the existing for an existing Required. See
resource team resource team footnote [1]
record in the Oracle record by exporting
Fusion destination the Resource
table. Team object using
the Setup and
Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.
Usage The lookup code Identify the Required Required
that represents the usage value using
team type and how the Setup and
the team will be Maintenance,
used. For example, Manage Resource
a marketing usage Lookups task.
might indicate a
group of resources
that work together,
usually across
organization
hierarchy
boundaries, to
plan and prepare
marketing content
and campaigns.
If you are adding team usages to an existing resource team, provide either the
team number (TeamNumber) or the Oracle Fusion record ID (TeamId).

Oracle Enterprise Repository. Review the reference file to explore other resource
team and resource team usage attributes that are available to import and the
possible prerequisite steps for those attributes.

DRAFT
• All resource team and resource team usage attributes available for import.

description.
To access the reference file for resource teams and resource team usages, follow
these steps.

HZ_IMP_TEAMS_T for resource teams, and HZ_IMP_TEAM_USAGE_T
for resource team usages.
4. Select the HZ_IMP_TEAM_T_Reference file for detailed
attribute information about resource teams, and
HZ_IMP_TEAM_USAGE_T_Reference file for detailed attribute
information about resource team usage.
Additional Tips
• Importing resource teams and resource team usages
• Importing resource team usages

DRAFT
27
Importing Sales Leads
Importing Sales Leads Using File-Based Import: Explained

This topic explains how to prepare and import sales lead data from an external
feature.
A sales lead is a business object that is used to represent the interest of a new
prospect or existing customer in a product or service being sold. You enter your
lead information using the Lead Qualification work area or you can import data
to create or update sales leads.
• How does your legacy system or source system represent the sales lead
your data values?
You must understand how your sales lead data corresponds with the data
Fusion Applications represent the structure of the data for a sales lead.
In Oracle Fusion Applications, the sales lead structure is hierarchical. At the top
level is the lead summary, which must exist before you can import lower level
components such as team members, tasks, and appointments. This hierarchical
structure supports one-to-many relationships between the components that
Importing Sales Leads 27-1

DRAFT
make up the lead. For example, a lead can have many sales team members, tasks,
and appointments.
The lead summary contains basic information about the lead such as the
customer or prospect, status, and deal size. For each lead, you can add contacts,
assign sales team members, and associate products. As you pursue the lead,
you can track appointments and interactions, assign tasks and due dates, attach
documents relevant to the lead, and post notes for the lead or for specific tasks.
Import Objects for the Sales Lead
To facilitate the import of sales leads, Oracle Fusion Applications incorporate the
structure of the sales lead into import objects. The following table lists the import
objects for the lead.
Import Object Structure

Lead Contacts
Note
You can create new customers, consumers, and

contacts or associate existing ones.
Sales Team
Products
Attachments
You can optionally create marketing responses that

are associated with the leads.
Task Tasks
Attachments
Notes
Note Notes
Attachments
Appointment Appointments
Attachments
Interaction Interactions
Attachments

DRAFT
between the structural components that make up the sales lead.
the attribute provides the task name in the Setup and Maintenance work area

Lead Lead Import Object and Attributes: How They Work
Together
Task Task Import Object and Attributes: How They Work
Together
Together
Appointment Appointment Import Object and Attributes: How
They Work Together
Interaction Interaction Import Object and Attributes: How They
Work Together
Hint: You can use the keyword "importing leads" to search for related topics in
your source file data. You can use the same source file to import both custom
attributes and the standard import object attributes.
Importing Sales Leads Using File-Based Data Import
For the lead business object, you must use the File-Based Data Import feature.
to schedule the import activities. You submit file-based import objects, create
source file mappings, and schedule the import activities. You submit file-based

DRAFT
import activities for each import object. When creating a marketing lead, you
first import the Lead object, followed by subsequent import activities for each of
the other import objects. The exception is attachments, which are imported by
including the file names in your source file for the Lead object and selecting the
files when defining the import activity.
You must be assigned the Corporate Marketing Manager, Marketing Analyst,
Marketing Manager, Marketing Operations Manager, Marketing VP, or Sales
Lead Qualifier job role to access and submit the import activities for sales leads.
can be used to verify imported data. Users with the Sales Lead Data Access Duty
role can also navigate to the Lead Qualification work area to view the imported
lead. Oracle Fusion Applications assign this role to the following predefined
job roles: Marketing VP, Corporate Marketing Manager, Marketing Operations
Manager, and Marketing Analyst.
Lead Import
Lead Import Objects: How They Work Together

You use two main import objects, Sales Lead and Note, when you submit a file-
based import activity to import your sales leads. This topic describes the Sales
Lead import object. It introduces the following:
• Target objects for the Lead import object
The Sales Lead import object is used to import sales leads and information to
create or update associated organization or person information for the customer,
consumer, or contact associated with the lead. The Sales Lead import object is
split into separate target import objects for organizing the individual attributes
of the different aspects of the lead. To map the source data in your import file
to the target attributes in Oracle Fusion Applications, you must understand
how the target objects are related and what attributes are included in each target
object.
Lead Target Import Objects
The target import objects in the Lead import objects are generally grouped into
information about the lead, the originating marketing response, and the contact,
consumer, or customer associated with the lead. The following figure shows the
grouping and the target import objects included in the Lead import object, each

DRAFT
A single lead includes information about the lead such as the interested party,
lead rank, and qualification status. The lead can include one or more products of
interest. You can add specific resources to the sales team responsible for the lead
or use assignment rules to assign resources.
The Lead, LeadProduct, and LeadResource target objects include the attributes to
import this information for your sales lead.
If the lead customer is an organization and an existing customer, then you

can associate the customer with the lead by using the Lead target object.
However, if you want to update the information for an existing customer or
create a customer record, then you must use additional target objects to import
customer profile information, addresses, and contact points, such as a phone
and fax number. The following target import objects are used for creating and
updating customer information for a lead respondent: OrganizationProfile,
OrganizationAddress, PrimaryPhone, Fax, and Url.
Similarly, you can associate an existing consumer with the lead by using the
Lead target object. To update the information for an existing consumer or create
a consumer record, use the following target import objects: PersonProfile,
PersonAddress, Email, PrimaryPhone, Mobile, InstantMessenger, and Fax.
To associate an existing contact for the responding consumer or customer

with the lead, you use the Lead target object. To update or create a contact,
use the following target import objects: ContactPersonProfile, ContactJob,

DRAFT
ContactPrimaryAddress, ContactEmail, ContactPrimaryPhone, ContactMobile,
ContactInstantMessenger, and ContactFax.
You can also import the marketing response that is the source for your lead.
The response can include one or more products of interest and survey questions
and answers, such as a telemarketer script. The Response, ResponseProduct,
and ResponseSurvey target objects include the attributes to import this
information for your marketing response. If you are importing the lead contact
and the customer or consumer, the same information is used as the respondent
information for the marketing response.
Note
extensibility features for the sales lead.

To access the reference guide files for the lead's target import objects, see the
Applications (http://fusionappsoer.com).
Documentation tab for the Lead File-Based Data Import asset.
Target Import Object Short Description OER Attribute Reference File

Name
Lead Sales lead summary information MKT_IMP_LEADS_T_Reference
LeadProduct Lead products of interest MKT_IMP_LEAD_PRODUCT_T_Reference
LeadResource Lead sales team MKT_IMP_LEAD_RESOURCES_Reference
Response Response summary and MKT_IMP_RESPONSES_T_Reference
associated respondent information
ResponseProduct Response products of interest MKT_IMP_RESP_PRODUCT_T_Reference
ResponseSurvey Response survey questions and MKT_IMP_RESP_SVY_LOG_T_Reference
answers
OrganizationProfile Customer profile information HZ_IMP_PARTIES_T_Reference
OrganizationAddress Customer address HZ_IMP_PARTYSITES_T_Reference

ContactPersonProfile
DRAFT
Contact summary information HZ_IMP_RELSHIPS_T_Reference
ContactPrimaryAddress Contact address HZ_IMP_PARTYSITES_T_Reference
ContactEmail Contact e-mail HZ_IMP_CONTACTPTS_T_Reference
ContactFax Contact fax HZ_IMP_CONTACTPTS_T_Reference
ContactInstantMessenger Contact social network HZ_IMP_CONTACTPTS_T_Reference
ContactJob Contact job information HZ_IMP_CONTACTS_T_Reference
ContactMobile Contact mobile HZ_IMP_CONTACTPTS_T_Reference
ContactPrimaryPhone Contact primary phone HZ_IMP_CONTACTPTS_T_Reference
Fax Customer fax HZ_IMP_CONTACTPTS_T_Reference
PrimaryPhone Customer primary phone HZ_IMP_CONTACTPTS_T_Reference
Url Customer Web site URL HZ_IMP_CONTACTPTS_T_Reference
PersonProfile Consumer summary information HZ_IMP_PARTIES_T_Reference
PersonAddress Consumer address HZ_IMP_CONTACTPTS_T_Reference
Fax Consumer fax HZ_IMP_CONTACTPTS_T_Reference
InstantMessenger Consumer social network HZ_IMP_CONTACTPTS_T_Reference
Mobile Consumer mobile HZ_IMP_CONTACTPTS_T_Reference
PrimaryPhone Consumer primary phone HZ_IMP_CONTACTPTS_T_Reference
Importing Lead and Lead Products Using File-Based Import: Quick

Start
with importing leads and lead products. A lead is a business object that is used
to represent a new prospect or an existing customer who has interest in or the
potential for interest in a product or service being sold.
• Additional tips
To explain how the import process identifies and associates records, consider
the following example. Within your sales catalog, you have defined a product
group for desktops and another product group for office accessories. The office
accessories product group includes individual products, including specific
mouse and mouse pad designs. When importing leads, it is your practice to
provide the names to identify product groups and item IDs to identify specific
products.
The following figure shows the structure of a typical, sales catalog product.

DRAFT
You have just completed your Spring Sales Event. You have acquired a lead who
is interested in the desktops and a specific mouse and mouse pad, and a second
lead who is interested in the desktops.
The import process imports the lead summary and then imports the products
of interest for the lead. To correctly associate the products with the right lead
record, the import process uses the product group name and item ID to identify
the products in your sales catalog.
The following figure shows the structure of the source file and the associated
mapping for importing a lead (SpringEventLead1) and the associated lead
products.
The following figure shows the imported structure of the lead record after
importing a lead and the associated lead products.

DRAFT
When the data is imported, a record is created in Oracle Fusion Applications for
each lead summary and associated product of interest. Each record in Oracle
Fusion has a unique ID. This ID is often referred to as the internal ID or object
key. In the example, the Oracle Fusion ID for the Spring Event Lead 1 record is
55. The ID for the association between the desktop and the lead is 5501, and the
ID for the association between the flower mouse pad and the lead is 5502. You
can use these IDs to uniquely identify the records when importing updates to the
records. To identify the lead summary data for import, you can either provide
a lead number or the import process will generate a value. The lead number,
which appears on the imported lead, is an alternate value to identify the lead
summary record when importing updates to the lead summary in subsequent
batches.
The following figure shows the structure of the lead record after importing a lead
and the associated lead products.

The minimum that is required to import lead summary and product data
are creating a new lead, updating an existing lead record, or associating
lead products of interest to the lead in the same batch.
attributes you want to provide to the import process for identifying
records.
table lists the minimum attributes required to import new lead and lead product
data. The entries in the table are based on any prerequisite setup or manual
steps needed to prepare your data and the import attributes that you use to map
provided. More information about the options is listed after the table.
Attribute Description Data Value Create Lead Data Create Lead

Prerequisite Product Data
LeadName The display name Identify a lead Required
for the sales lead. name for each sales
lead.

ItemId
DRAFT
The unique ID for Identify the Conditionally
the existing product INVENTORY_ITEM_ID required
(item) record in for an existing
the Oracle Fusion product (item) See footnote [1]
destination table. by exporting the
Product Group
Products object,
using the Setup
and Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.
ProductName The name for the Identify the product Conditionally
product (item) of name, using required
interest. the Setup and
Maintenance, See footnote [1]
Manage Product
Groups task. Or,
export the names
by exporting the
Product Group
Products object,
using the Setup
and Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.
ProductGroupId The unique ID for Identify the product Conditionally
the existing product group ID for an required
group record in existing product
the Oracle Fusion group by exporting See footnote [1]
destination table. the Product Group
Details object,
using the Setup
and Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.
ProductGroupName The name for the Identify the product Conditionally
product group of group name, using required
interest. the Setup and
Maintenance, See footnote [1]
Manage Product
Groups task. Or,
export the names
by exporting the
Product Group
Details object,
using the Setup
and Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.

[1]
DRAFT
To optionally import products of interest for the response, the import process
needs to uniquely identify either a sales catalog's product or product group.
To identify a product, you can provide either the product's unique ID (ItemId)
or the product's internal name (ProductName). To identify a product group,
you can provide either the product group's unique ID (ProductGroupId) or the
product group's internal name (ProductGroupName).
The following table lists the minimum attributes required to import updates
to existing lead and lead product data. Entries in the table are based on any
prerequisite setup or manual steps needed to prepare your data and the import
listed after the table.
Attribute Description Data Value Update Lead Data Update Lead

Prerequisite Product Data
LeadNumber The lead's public Identify the lead Conditionally
unique identifier number for an required
value. existing lead
by doing the See footnote [1]
following:
• Using
the Lead
Qualification
work area
• Exporting the
Lead object,
using the
Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule
Export
Processes
task.
ObjectKey The unique ID for Identify the unique Conditionally
the existing lead Oracle Fusion ID required
record in the Oracle (LEAD_ID) for
Fusion destination an existing lead See footnote [1]
table. by Exporting the
Lead object, using
the Setup and
Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.

ProdAssocId
DRAFT
The unique ID for Identify the Required
the existing lead PROD_ASSOC_ID
product record or for an existing lead
lead product group product or lead
record in the Oracle product group by
Fusion destination exporting the Lead
table. Item Assoc object,
using the Setup
and Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.
[1] To uniquely identify the lead, either provide the lead number (LeadNumber)
or the Oracle Fusion record ID (ObjectKey).

Information about all available lead and lead product attributes are included in a
reference file located in Oracle Enterprise Repository. Review the reference files
to explore other lead and lead product attributes that are available to import and
the possible prerequisite steps for those attributes. These reference files include
the following information:
• All lead and lead product attributes available for import.

description.
To access the reference file for leads, follow these steps:

MKT_IMP_LEAD_T.
4. Select the MKT_IMP_LEAD_T_Reference file.
To access the reference file for lead products, follow these steps:

MKT_IMP_LEAD_PRODUCT_T.
4. Select the MKT_IMP_LEAD_PRODUCT_T_Reference file.

DRAFT
Additional Tips
You can explore related topics by entering the following keywords in the Oracle
Fusion Help Application search: importing sales leads. The Help Application is
available from any Oracle Fusion Application page by clicking Help in the top-
right corner, and selecting Applications Help.
My Oracle Support topic, Fusion CRM File-Based Data Import Templates, ID
1503223.1, includes a downloadable source file example for leads that includes
importing a product group association using the product group name.

Start
• Additional tips



DRAFT

associate records.
following table.

Community
members, using
the Setup and
Maintenance,
Manage Trading
Community Source
Systems task.

DRAFT
unique ID for the
organization.
organization.
Organization or
Partner Profile
object using
the Setup and
Maintenance,
Manage Bulk Data
Export, Schedule
Export Processes
task.


import.

description.

these steps.


DRAFT
HZ_IMP_PARTIES_T.
Additional Tips

• Additional tips


Contact
DRAFT PersonProfile
profiles.

the following:

DRAFT

associate records.
table.

Same Batch
Export Processes
task.
Systems task.
unique ID for the
party (customer,
consumer, contact,
group, or legal
entity) to which
the person profile
belongs.
person party.

PersonLastName
DRAFT
person party.


description.

HZ_IMP_PARTIES_T.
target objects.
Additional Tips

DRAFT
Appointment Import

Import feature.



your data values?


DRAFT


Appointment.


Together
appointment object.

DRAFT
import activities.




Together

DRAFT
opportunity.

object.


DRAFT


participants
participants
Interaction Import

feature.

interactions.

your data values?


DRAFT


Interaction.


Together

DRAFT
attributes.

Maintenance task.

import processing.



DRAFT

opportunity.



DRAFT
Note


Note Import


DRAFT

your data values?

associated object.

Import Object
DRAFT
Target Import Object Reference Guide File Name
attributes.



DRAFT
28
Importing Sales Opportunities
Importing Sales Opportunities Using File-Based Import: Explained

This topic explains how to prepare and import opportunity data from an external
feature.
A sales opportunity is a business object that is used to track and store data
about potential sales. Opportunities can be created directly in the opportunity
application, by converting leads, or using file-based data import.
• How does your legacy system or source system represent the sales
opportunity compared to how Oracle Fusion Applications represent the
same data?
your data values?
You must understand how your opportunity data corresponds with the data
in Oracle Fusion Applications in order to be able to map your legacy data to
the data needed by Oracle Fusion Applications. First, you must understand
how Oracle Fusion Applications represent the structure of the data for a sales
opportunity.
In Oracle Fusion Applications, the sales opportunity structure is hierarchical. At
the top level is the sales opportunity object, with lower-level components, such
as competitors, resources, contacts, and revenue items, playing a subordinate
role. This hierarchical structure supports one-to-many relationships between
the components that make up the opportunity. For example, an opportunity can
have many competitors, resources, and revenue items.
The following two figures show the sales opportunity object and its subordinate
objects.
Following is part one of the opportunity object diagram.
Importing Sales Opportunities 28-1

DRAFT
Following is part two of the opportunity object diagram.
In spite of this hierarchical relationship of the object and lower-level

components, you can import the other components independently of the sales
opportunity object. When doing so, you must reference the opportunity number
associated with these lower-level components.
The sales opportunity summary object contains basic information about
the opportunity, such as the owner, close date, source, and so on. For each
opportunity, you can associate revenue items, assign team members, set a close
date, attach relevant documents, and post notes, among other activities.
Import Objects for the Sales Opportunity
To facilitate the import of opportunities, Oracle Fusion Applications incorporate
the structure of the opportunity into import objects. The import objects for the
opportunity are as follows:
• Sales Opportunity: Includes the following sublevel objects associated
with an opportunity. Note that all of these objects store the associations
between the opportunity and the objects.

DRAFT
• Competitors
• Contacts
• Leads
• Partners
• References
• Resources
• Responses
• Revenue items
• Revenue line set revenue items
• Sources
• Note: Opportunity notes. A note is a record attached to a business
object that is used to capture nonstandard information received while
conducting business.
• Interaction: Opportunity interactions. An interaction is a record
of customer communication. An interaction can track the mode of
communication, the direction of communication, the business objects
discussed in the communication, such as an opportunity or lead, and with
whom the information was discussed. It can also track the outcome of the
communication, and it supports attachments.
• Appointment: Opportunity appointments. Appointments enable the
creation and management of calendar appointments.
• Task: Opportunity tasks. A task is a unit of work to be completed by one
or more people by a specific completion date.
Note
Importing the common components listed above requires a separate import
activity. With file import, you cannot, for example, import notes associated with
an opportunity at the same time as importing the opportunity.

Each import object is a collection of attributes that help to map your data to the
Oracle Fusion Applications data and support one-to-many relationships between
the structural components that make up the opportunity.
to preparing your import data. The reference files contain descriptions, logic
used to choose default values, and validation information for each of the
where you can define your values. For additional information, including a list
of reference file names and locations that you need to complete this task, see the
following table.

Import Object
DRAFT Related Import Object Topic
Sales opportunity, including sub-objects Sales Opportunity Import Objects: How They Work
Together
Note Importing Notes Using File-Based Import: Explained
Interaction Importing Interactions Using File-Based Import:
Explained
Appointment Importing Appointments Using File-Based Import:
Explained
Task Importing Tasks Using File-Based Import: Explained
Importing Opportunities Using File-Based Data Import

For the sales opportunity business object, you must use the File-Based Data
mapping, and imports the data into the application destination tables. The
Define File-Based Data Import Setup and Maintenance task list includes the
tasks needed to configure the import objects, to create source-file mappings,
and to schedule the import activities. You submit file-based import activities
for each import object. When creating a new opportunity, you import the sales
opportunity object.
Administrator or Sales Administrator role to access and submit the import
activities for opportunities.
attributes.

Relationship Management Application Administrator or Sales Administrator
role can also navigate to the Opportunity work area to view the imported
opportunities.
Opportunity Import

DRAFT
Sales Opportunity Import Objects: How They Work Together
This topic describes the components of the Sales Opportunity import object. It
introduces the following:
• The target objects for the Sales Opportunity import object
Sales Opportunity import includes the import of attributes of the opportunity,
plus information to create or update several other data points of the opportunity,
such as competitors, revenue items, and reference customers. The Sales
Opportunity import object is split into separate target import objects for
organizing the individual attributes of the opportunity. Before you import,
you must understand how the target objects are related and which attributes
are included in the object. This understanding helps you create the mapping
between the source data in your import file and the target attributes expected by
the application.
A single opportunity includes specific information about the opportunity. In
addition to various attributes of the opportunity, for example, opportunity name,
owner, close date, and so on, the opportunity can have several revenue lines,
each of which can have one product or product group. A single opportunity also
typically includes one or more CRM resources that make up the opportunity
team. It also can include contacts, competitors, reference customers, and
other target objects. These target objects are supplied as part of the import
infrastructure.
The following two figures show the supplied Opportunity import target objects.
It lists the formal target import object name in parentheses if it differs from the
object name.
Following is part one of the target object diagram.

DRAFT
Following is part two of the target object diagram.
The following table shows the Opportunity import target objects and their
descriptions.
Note
All of these objects store the associations between the opportunity and the
objects.
Target Objects of Sales Opportunity Description

Opportunity Main opportunity object
Competitor • Competitor associated with the opportunity
• Can be associated at header or revenue line

level
• One-to-many relationship with the

opportunity
Contact • Contact associated with the opportunity

opportunity
Lead Lead associated with the opportunity
Reference • Reference associated with the opportunity
• One-to-one relationship with the opportunity

Resource • Resource associated with the opportunity

opportunity
Response Marketing response that generated the opportunity
(reserved for future use)
Source • Source (sales campaign) associated with the
opportunity
• One-to-one relationship with the opportunity

Revenue
DRAFT • Revenue item or group associated with the
opportunity

opportunity
Revenue Partner • Partner associated with the opportunity

opportunity
Revenue Line Set • Revenue-line-set revenue item associated with
the opportunity. (The revenue line sets are
categories of revenue lines.)

opportunity

Note
extensibility features for opportunities.

To access the reference guide files for the Sales Opportunity's target import
Documentation tab for the Sales Opportunity File-Based Data Import asset.
Target Objects of Sales Opportunity Reference Guide File Names

Opportunity MOO_IMP_OPTY_Reference
OpportunityCompetitor MOO_IMP_OPTY_COMPETITORS_Reference
OpportunityContact MOO_IMP_OPTY_CON_Reference
OpportunityLead MOO_IMP_OPTY_LEADS_Reference

OpportunityReference
DRAFT MOO_IMP_OPTY_REFERENCES_Reference
OpportunityResource MOO_IMP_OPTY_RESOURCES_Reference
OpportunityResponse MOO_IMP_OPTY_RESPONSES_Reference
OpportunitySource MOO_IMP_OPTY_SRC_Reference
OpportunityRevenue MOO_IMP_REVN_Reference
OpportunityRevenuePartner MOO_IMP_REVN_PARTNER_Reference
OpportunityRevenueLineSet MOO_IMP_REVN_LINE_SET_Reference
Importing Opportunities Using File-Based Import: Quick Start

in importing opportunities.
• Identifying resources for the import file
• Using Oracle Enterprise Assets to evaluate optional attributes
• Additional tips
A sales opportunity is a business object that is used to track and store data
about potential sales. Opportunities can be created directly in the opportunity
application, by converting leads, or using file-based data import. You can import
opportunities using the File-Based Data Import feature.
The following table lists the file-based import object and target object for
importing an opportunity.

Opportunity Opportunity
Opportunity Opportunity Resource

The minimum that is required to import originating opportunities depends on
the following:
are creating the opportunity as a new opportunity, updating an existing
opportunity, or deleting an existing opportunity.

DRAFT
table lists the minimum attributes required to import opportunity data based on
the purpose of 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.
Note
This table does not list resource (owner, created by, and the like) attributes. For
those, see the following section on identifying resources for the import file.
Opportunity Description Data Value Create Update Existing Delete Existing

Attribute Prerequisite Opportunity Opportunity Opportunity
ActionCode Indicates Use the value, Required
the import DELETE, if
operation for deleting an
the record. existing record.
ActualCloseDate Actual Close Required if Required if
Date - The date the status the status
the opportunity (StatusCd) (StatusCd)
was closed. value is value is
something other something other
than OPEN. than OPEN.
BuName Business Unit - Identify Required Conditionally Conditionally
The name of the business unit Required (1) Required (1)
business unit names using the
associated with Define Business
the opportunity. Units for
Sales, Manage
Business Unit,
Setup and
Maintenance
task.
ExpectedCloseDate
Close Date - The Required
date for which
the opportunity
should be
included in the
forecast.
Language The code Default is US if Required Conditionally Conditionally
representing not specified. if creating Required (1) Required (1)
the language translated
into which the values or
contents of the providing
translatable translated
columns are values used
translated. by the import
process to set
default Oracle
Fusion IDs.
Name Opportunity Required
Name - The
name that
identifies the
opportunity.

OptyCreationDateOpportunity
DRAFT Required
Creation Date
- The date
and time the
opportunity
was created
in the source
system.
OptyCurcyCode Currency - You can view Required
The code that valid currency
represents the codes from
currency of the the Manage
opportunity Currencies,
amount. Setup and
Maintenance
task.
OptyId The unique ID You can obtain Do not provide. Conditionally Conditionally
for the existing the OptyID Required (1) Required (1)
opportunity for an existing
record in the opportunity by
Oracle Fusion exporting the
destination Opportunity
table. object using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.
OptyLastUpdateDate
Opportunity Required
Last Update
Date - The date
and time the
opportunity
was last
updated in the
source system.
OptyNumber Opportunity Required Conditionally Conditionally
Number - The Required (1) Required (1)
opportunity's
public unique
identifier value.

ReasonWonLostCdWin/Loss
DRAFT Required if: Required if:
Reason - The
lookup code • Profile • Profile
that represents option option
the reason for Close Close
closing the Opportunity Opportunity
opportunity. Win/Loss Win/Loss
Reason Reason
Required Required
value is value is
Yes; and Yes; and
• Status • Status
(StatusCd) (StatusCd)
value is value is
something something
other than other than
OPEN. OPEN.
You can view You can view

the profile the profile
setting using setting using
the Setup and the Setup and
Maintenance, Maintenance,
Manage Manage
Opportunity Opportunity
Profile Options Profile Options
task. task.
StatusCd Status - The Used to derive Required
lookup code the revenue
that represents line status if
the status of the imported in
opportunity as the same batch
open, won, lost, and a value is
or no sale. not provided
(MOO_IMP_REVN
table,
STATUS_CODE
column). Valid
values provided
by lookup type,
ZBS_SALESLOOKUPS_CATEGORY.
Identifying Resources for the Import File

Opportunity import requires that you provide certain identifiers in the import
file so that the system can identify resources (for example, the Owner and the
Created By and Last Updated By values). Use the following information to help
you identify these values:
• Oracle Fusion Record ID: The internal database ID for a record, assigned
by the system. For opportunities, this is the Opportunity ID. It can be used
alone to uniquely identify the resource data.
• Resource Registry ID: The enterprise information Registry ID available in
various user interfaces in Oracle Fusion. Registry ID is the same as Party
ID. It can be used alone to uniquely identify the resource (person).
• Combination of Source System and Source System Reference: You can also
use this combination of unique IDs to identify a resource from a legacy
system, but the data may not be readily available if it has been a long
time since you migrated from the legacy system. For example, you may

DRAFT
be able to use these two identifiers if you are migrating resources and
opportunities at the same time from the legacy system. Or, you may be
able to these identifiers if your external system and Oracle Fusion co-exist
with updates being imported on a regular basis.
To explain how you can identify and associate records, consider the following
example. You are importing an opportunity, Pinnacle Opportunity, from your
external system (which you refer to as the legacy system). Burt Smith and
Sue Smith are both associated with the Pinnacle Opportunity, and both have
identifying records, both in the legacy system and in Fusion Applications when
they were created as resources. To identify the Owner, Created By, and Last
Updated By values for your import spreadsheet, you can use Burt's Fusion data,
Sue's data, or the combination data from the legacy system.
The following table lists the attributes you can use to identify:
• The created by user

OptyCreatedBy The user who Conditionally
created the required (1)
opportunity
in the source
system.
OptyCreatedByPartyId
The unique ID Identify the Required if
for the existing Party ID for not providing
opportunity an existing the created
creator's party resource's party by user name
record in the by exporting (OptyCreatedBy)
Oracle Fusion the Resource or the user's
destination object using party number
table. the Setup and or source
Maintenance, system and
Manage Bulk source system
Data Export, reference
Schedule Export (OptyCreatedByPartyNumber
Processes task. or
OptyCreatedByPartyOrigSys
and
OptyCreatedByPartyOsr).

OptyCreatedByPartyNumber
The opportunity
DRAFT
Identify the Required if
creator's party's Registry ID not providing
public unique (party number) the created
identifier value. for an existing by user name
resource's (OptyCreatedBy)
party using or the user's
the Setup and party ID
Maintenance, or source
Manage system and
Resources task, source system
or by exporting reference
the Party (OptyCreatedByPartyId
object using or
the Setup and OptyCreatedByPartyOrigSys
Maintenance, and
Manage Bulk OptyCreatedByPartyOsr).
Data Export,
Schedule Export
Processes task.
The source Identify the Required if
system original system not providing
code that and system the created
identifies the reference values by user name
original source from your (OptyCreatedBy)
system of the source system or the user's
opportunity which were party ID or
creator's party. imported when party number
you imported (OptyCreatedByPartyId
the resource. or
OptyCreatedByPartyNumber).
OptyCreatedByPartyOsr
The ID that Identify the Required if
identifies the original system creating a new
opportunity and system opportunity
creator's party reference values and not
in your legacy from your providing
or external source system the created
system. which were by user name
imported when (OptyCreatedBy)
you imported or the user's
the resource. party ID or
party number
(OptyCreatedByPartyId
or
OptyCreatedByPartyNumber).
• The last updated by user

Opportunity Description
DRAFT
Data Value Create Update Existing Delete Existing
OptyLastUpdatedBy
User who last To identify the Required if Required if
updated the Created By user, you are not you are not
opportunity provide one of providing the providing the
in the source the following user's party user's party
system. attributes: ID, number, ID, number,
OptyCreatedBy, or source or source
OptyCreatedByPartyId,
system and system and
OptyCreatedByPartyNumber,
source system source system
or provide reference reference
both the
and
values.
OptyLastUpdByPartyId
The unique ID Identify the Required if not Required if not
for the existing party ID value providing last providing last
opportunity by exporting updated by user updated by user
last updated the Party object name or user's name or user's
by's party using Setup and party number party number
record in the Maintenance, or source or source
Oracle Fusion Manage Bulk system and system and
destination Data Export, source system source system
table. Schedule Export reference reference
Processes task.
OptyLastUpdByPartyNum
The opportunity Identify the Required if Required if
last updated party ID value not providing not providing
by's party's by exporting last updated last updated
public unique the Party object by user name by user name
identifier value. using Setup and or user's party or user's party
Maintenance, ID or source ID or source
Manage Bulk system and system and
Data Export, source system source system
Schedule Export reference reference
Processes task.
OptyLastUpdByPartyOs
The source Identify the Required if not Required if not
system party ID value providing last providing last
code that by exporting updated by updated by
identifies the the Party object user name or user name or
original source using Setup and user's party ID user's party ID
system of the Maintenance, or party number or party number
opportunity last Manage Bulk
updated by's Data Export,
party. Schedule Export
Processes task.
OptyLastUpdByPartyOsr
The ID that Identify the Required if not Required if not
identifies the party ID value providing last providing last
opportunity by exporting updated by updated by
last updated the Party object user name or user name or
by's party in using Setup and user's party ID user's party ID
your legacy or Maintenance, or party numbe or party numbe
external system. Manage Bulk
Data Export,
Schedule Export
Processes task.

DRAFT
• The opportunity owner

and Prerequisite Opportunity Opportunity Opportunity
Opportunity
Resource
Attribute
OwnerResourceIdUnique ID for To identify the Required if Required if
the existing Created By user, not providing not providing
opportunity provide one of the resource's the resource's
owner record the following party number party number
in the Oracle attributes: or source or source
Fusion OptyCreatedBy, system and system and
destination OptyCreatedByPartyId,
source system source system
table. OptyCreatedByPartyNumber,
reference reference
or provide (OwnerResourceNumber
(OwnerResourceNumber
both the or or
OwnerOrigSystemOwnerOrigSystem
and and and
OwnerOrigSystemReference).
values.
OwnerResourceNumber
The opportunity To identify the Required if not Required if not
owner party's Created By user, providing the providing the
public unique provide one of resource's party resource's party
identifier value. the following ID or source ID or source
attributes: system and system and
OptyCreatedBy, source system source system
reference reference
(OwnerResourceId(OwnerResourceId
or provide or or
both the OwnerOrigSystemOwnerOrigSystem
and and
and OwnerOrigSystemReference).
values.
OwnerOrigSystemSource system To identify the Required if Required if
code that Created By user, not providing not providing
identifies the provide one of the resource's the resource's
original source the following party ID or party ID or
system of the attributes: party number party number
opportunity OptyCreatedBy, (OwnerResourceId(OwnerResourceId
owner. OptyCreatedByPartyId,
or or
OwnerResourceNumber).
or provide
both the
and
values.

OwnerOrigSystemReference
The ID that
DRAFTTo identify the Required if Required if
identifies the Created By user, not providing not providing
opportunity provide one of the resource's the resource's
owner in your the following party ID or party ID or
legacy or attributes: party number party number
external system. OptyCreatedBy, (OwnerResourceId(OwnerResourceId
or or
or provide
both the
and
values.

opportunity attributes that are available to import and the possible prerequisite
steps for those attributes. This in-depth reference file includes the following
information:
• All opportunity attributes available for import.
description.
To access the reference file, follow these steps.
user or a guest.
2. Search assets using the following value for your Search String:
MOO_IMP_OPTY and MOO_IMP_OPTY_RESOURCES.
4. Select the MOO_IMP_OPTY_Reference file and the
MOO_IMP_OPTY_RESOURCES file.
Additional Tips
• Importing opportunity
Tip: The My Oracle Support topic, Fusion CRM File-Based Data Import
Templates, ID 1503223.1, includes a downloadable source file example for
opportunities that includes importing an opportunity and opportunity owner.

DRAFT
Importing Opportunity-Lead Relationships Using File-Based
Import: Quick Start
in importing the relationship between the opportunity and the originating sales
leads.
• Additional tips
Importing opportunity leads creates a relationship between the opportunity

and the sales lead that led to the creation of the opportunity. The relationship
between the opportunity and the opportunity's source information (marketing
campaign source codes, marketing responses, and sales leads) allows you to
track marketing and sales activity effectiveness by recording the progression
from the marketing campaign to the opportunity. You can import new lead
relationships or delete existing relationships records using the File-Based Data
Import feature.
The following table lists the file-based import object and target object for
importing the opportunity's sales lead relationships.
Import Object Source Object Target Object

Opportunity Sales Lead OpportunityLead
The following opportunity object diagram indicates the structure of the

opportunity and the association with the originating marketing campaign source
codes, marketing responses, and sales leads.

The minimum that is required to import originating lead relationship
information depends on the following:

DRAFT
are creating both the opportunity and the originating lead relationship
in the same import batch, adding a new lead relationship to an existing
opportunity, or deleting an existing lead relationship record.
table lists the minimum attributes required to import lead relationship data
based on the purpose of 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. A numbered footnote (n) indicates choices. More
information about the options is listed below the table.
Attribute Description Data Value Create Create Lead Deleting Lead

Prerequisite Opportunity Relationship Relationship
and Lead Records for Records for
Relationship an Existing an Existing
Records in the Opportunity Opportunity
Same Batch
LeadNumber Lead Number Identify the Required Conditionally
- The lead's Lead Number required
unique for an existing
identifier value. sales lead See footnote (2)
using the Lead
Qualification
work area and
by exporting
the Lead object
using the
Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.
OptyId The unique ID Identify the ID Conditionally Conditionally
for the existing for an existing required required
opportunity opportunity by
record in the exporting the See footnote (1) See footnote (2)
Oracle Fusion Opportunity
destination object using
table. the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.

OptyNumber Opportunity
DRAFT
If providing Required Conditionally Conditionally
Number - The a value and required required
opportunity's creating a new
unique opportunity in See footnote (1) See footnote (2)
identifier value. the same import
batch, identify
and use the
same number
for your lead
relationship.
If providing
the value for
an existing
opportunity,
identify the
Opportunity
Number using
the Opportunity
user interface
or by exporting
the Opportunity
object using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.
OptyLeadId The unique Identify the Conditionally
ID for the ID for an required
existing lead existing lead
relationship relationship by See footnote (2)
record in the exporting the
destination Lead object
table. using the
Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.
(1) To identify the existing opportunity, provide either the Oracle Fusion record
ID (OptyId) or the opportunity number (OptyNumber).
(2) To identify the existing lead relationship record, provide either the Oracle
Fusion record ID (OptyLeadId), or provide the lead number (LeadNumber) and
the opportunity's Oracle Fusion record ID (OptyId), or provide the lead number
(LeadNumber) and the opportunity number (OptyNumber).

in Oracle Enterprise Repository. Review the reference file to explore other lead
relationship attributes that are available to import and the possible prerequisite
information:

DRAFT
• All lead relationship attributes available for import.
description.
To access the reference file, follow these steps.
user or a guest.
MOO_IMP_OPTY_LEADS.
4. Select the MOO_IMP_OPTY_LEADS_Reference file.
Additional Tips
Importing Opportunity-Response Relationships Using File-Based

Import: Quick Start
in importing the relationship between the opportunity and the originating
marketing responses. This topic includes the following information:
• Additional tips
Importing opportunity responses creates a relationship between the opportunity
and the marketing response that led to the creation of the opportunity. The
relationship between the opportunity and the opportunity's source information
(marketing campaign source codes, marketing responses, and sales leads)
allows you to track marketing and sales activity effectiveness by recording the
progression from the marketing campaign to the opportunity. You can import
new response relationships or delete existing relationships records using the
File-Based Data Import feature. The following table lists the file-based import
object and target object for importing the opportunity's marketing response
relationships.

Import Object
DRAFT
Source Object Target Object
Opportunity Marketing Response OpportunityResponse

The minimum that is required to import originating response relationship
information depends on the following:
you are creating both the opportunity and the originating response
relationship in the same import batch, adding a new response relationship
to an existing opportunity, or deleting an existing response relationship
record.
manual steps to ensure the information passes the import validation. Before you
lists the minimum attributes required to import response relationship data based
on the purpose of 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. A numbered footnote (n) indicates choices. More information
Attribute Description Data Value Create Create Deleting

Prerequisite Opportunity Response Response
and Response Relationship Relationship
Relationship Records for Records for
Records in the an Existing an Existing
Same Batch Opportunity Opportunity
ResponseNumber Response Identify the Required Conditionally
Number - The Response required See
response's Number for footnote (2)
unique an existing
identifier value. marketing
response using
the Response
Management
work area and
by exporting
the Response
object using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.

OptyId The unique ID
DRAFT
Identify the ID Conditionally Conditionally
for the existing for an existing required See required See
opportunity opportunity by footnote (1) footnote (2)
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.
OptyNumber Opportunity If providing Required Conditionally Conditionally
Number - The a value and required See required See
opportunity's creating a new footnote (1) footnote (2)
unique opportunity
identifier value in the same
import batch,
identify and
use the same
number for
your response
relationship.
If providing
the value for
an existing
opportunity,
identify the
Opportunity
Number using
the Opportunity
user interface
or by exporting
the Opportunity
object using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.
OptyResponseId The unique ID Identify the ID Conditionally
for the existing for an existing required See
response response footnote (2)
relationship relationship by
destination Response
table. object using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.

DRAFT
(2) To identify the existing response relationship record, provide either the
Oracle Fusion record ID (OptyResponseId), or provide the response number
(ResponseNumber) and the opportunity's Oracle Fusion record ID (OptyId), or
provide the response number (ResponseNumber) and the opportunity number
(OptyNumber).
Oracle Enterprise Repository. Review the reference file to explore other response
relationship attributes that are available to import and the possible prerequisite
information:
• All response relationship attributes available for import.
description.
To access the reference file for opportunity marketing response relationships,
follow these steps.
user or a guest.
MOO_IMP_RESPONSES.
4. Select the MOO_IMP_RESPONSES_Reference file.
Additional Tips
Importing Opportunity-Source Code Associations Using File-Based

Import: Quick Start
in importing the relationship between the opportunity and the originating
marketing campaign source codes. This topic includes the following information:
• Additional tips
Importing opportunity sources creates a relationship between the opportunity
and the marketing campaign source code that led to the creation of the

DRAFT
opportunity. The relationship between the opportunity and the opportunity's
source information (marketing campaign source codes, marketing responses,
and sales leads) allow you to track marketing and sales activity effectiveness
by recording the progression from the marketing campaign to the opportunity.
You can import new source relationships or delete existing relationships records
import object and target object for importing the opportunity's campaign source
ode relationships.
Import Object Source Object Target Object

Opportunity Marketing Campaign Source Code OpportunitySource

The minimum that is required to import originating campaign source code
relationship information depends on the following:
are creating both the opportunity and the originating campaign source
code relationship in the same import batch, adding a new campaign
source code relationship to an existing opportunity, or deleting an existing
campaign source code relationship record
manual steps to ensure the information passes the import validation. Before you
values, and then include those values in your source file. The following table lists
the minimum attributes required to import campaign source code relationship
your data to Oracle Fusion. A numbered footnote (n) indicates choices. More
information about the options is listed below the table.
Attribute Description Data Value Create Create Deleting

Prerequisite Opportunity Response Response
and Response Relationship Relationship
Relationship Records for Records for
Records in the an Existing an Existing
Same Batch Opportunity Opportunity
MktgSourceCode Source Code Identify Required Conditionally
- The source the source required See
code of the code using footnote (2)
marketing the Review
campaign Setup and
activity. Maintenance,
Marketing
Source Codes
task.

OptyId The unique ID
DRAFT
Identify the ID Conditionally Conditionally
for the existing for an existing required See required See
opportunity opportunity by footnote (1) footnote (2)
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.
OptyNumber Opportunity If providing Required Conditionally Conditionally
Number - The a value and required See required See
opportunity's creating a new footnote (1) footnote (2)
unique opportunity
identifier value in the same
import batch,
identify and
use the same
number for
your response
relationship.
If providing
the value for
an existing
opportunity,
identify the
Opportunity
Number using
the Opportunity
user interface
or by exporting
the Opportunity
object using
the Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.
OptySrcId The unique ID Identify the ID Conditionally
for the existing for an existing required See
campaign campaign footnote (2)
source code source code
relationship relationship by
destination Source object
table. using the
Setup and
Maintenance,
Manage Bulk
Data Export,
Schedule Export
Processes task.

DRAFT
(2) To identify the existing campaign source code relationship record, provide
either the Oracle Fusion record ID (OptySrcId), or provide the campaign source
code (MktgSourceCode) and the opportunity's Oracle Fusion record ID (OptyId),
or provide the campaign source code (MktgSourceCode) and the opportunity
number (OptyNumber).

campaign source code relationship attributes that are available to import and
the possible prerequisite steps for those attributes. This in-depth reference file
• All campaign source code relationship attributes available for import.

description.
To access the reference file for opportunity campaign source code relationships,
follow these steps.

user or a guest.
MOO_IMP_SRC.
4. Select the MOO_IMP_SRC_Reference file.
Additional Tips
Appointment Import

DRAFT
Import feature.
your data values?


Appointment.

DRAFT

Together
appointment object.
import activities.


DRAFT
Together

opportunity.


DRAFT
object.



participants
participants
Interaction Import

feature.

DRAFT
interactions.
your data values?


Interaction.

DRAFT

Together
attributes.
Maintenance task.
import processing.

DRAFT



opportunity.


DRAFT

Note


Note Import

DRAFT


your data values?

associated object.

DRAFT

attributes.



DRAFT
29
Importing Tasks
Note Import


your data values?

Importing Tasks 29-1

DRAFT
associated object.

attributes.

DRAFT


Importing Tasks 29-3

DRAFT

DRAFT
Glossary
interface table
A database table used for transferring data between applications or from an

external application or data file.
lookup code
A value available for lookup within a lookup type such as the code BLUE within
the lookup type COLORS.
lookup type
A set of lookup codes to be used together as a list of values on a field in the user
interface.
Glossary-1

Oracle Fusion CRM File-Based Data Import Guide PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Oracle Fusion CRM File-Based Data Import Guide PDF

Загружено:

Авторское право:

Доступные форматы

DRAFT

Oracle Fusion CRM File-Based Data Import Guide

Part Number Draft Copy

Copyright © 2011-2013, Oracle and/or its affiliates. All rights reserved.

2 Configuring File-Based Data Import

3 File-Based Import Object and Target Objects

4 Define File-Based Data Import Activities

7 Importing Click-to-Dial Agents

11 Importing Country Structures

13 Importing Customer Hierarchies

14 Importing Employee Resources

16 Importing Group Customers

18 Importing Legal Entities

19 Importing Marketing Budgets

20 Importing Marketing Campaigns

21 Importing Marketing Responses

24 Importing Product Groups

26 Importing Resource Teams

27 Importing Sales Leads

28 Importing Sales Opportunities

Oracle Fusion Applications Help

Oracle Fusion Applications Guides

Guides are designed for specific audiences:

Guide Intended Audience Purpose

Other Information Sources

Oracle Enterprise Repository for Oracle Fusion Applications

In Oracle Fusion Applications, you can use Oracle Enterprise Repository at

• Technical information about integrating with other applications, including

Comments and Suggestions

Getting Started with File-Based Import: Documentation Overview

There are three main sources of information for import:

These topics provide general information about import.

• Help topics on individual import objects are available by searching Oracle

There you can view individual help topics or download implementation

• Oracle Enterprise Repository, which contains reference guides with

For example, to get help on importing customers, enter importing

Help Topic Title Description

These guides include detailed descriptions of attributes and permitted

1-2 Oracle Fusion CRM File-Based Data Import Guide

File-Based Data Import: How It Works

The following figure provides an overview of the major application components

• Oracle Fusion CRM Application Composer

• Oracle Fusion CRM base tables

Configuring File-Based Data Import 2-1

Import Objects, Import Mapping, and Import Activity

Application Composer and Custom Extensions

2-2 Oracle Fusion CRM File-Based Data Import Guide

File-Based Data Import Tasks: How They Work Together

Manage File Import Activities Task

Configuring File-Based Data Import 2-3

You activate the import activity by clicking the Activate button.

Manage File Import Mappings Task

• Create new mappings without a data file.

Creating a mapping using the Manage File Import Mappings task is

Manage File Import Objects Task

2-4 Oracle Fusion CRM File-Based Data Import Guide

Understanding File-Based Data Import: Getting Started

Import Object Description

File-Based Import Object and Target Objects 3-1

3-2 Oracle Fusion CRM File-Based Data Import Guide

Tasks Involved in Import

File-Based Import Object and Target Objects 3-3

3-4 Oracle Fusion CRM File-Based Data Import Guide