Skip Headers

Home

Contents

Book
List

Contact
Us

PDF

20 Define File-Based Data Import

This chapter contains the following:

Overview of File-Based Data Import

Import Objects for Contracts

Overview of 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
Application tables

Import Objects, Import Mapping, and Import Activity

The import objects you select when you create an import activity are provided by Oracle. They are managed using the Manage File Import Objects task.

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

Application Tables

The import activity loads your data into Oracle Fusion CRM application tables to complete the import.

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.
Click-to-Dial Agents	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	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:

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

Importing Data from a File: Getting Started

Using the Define File-Based Data Import group of tasks available from the Setup and Maintenance work area, you can import a wide range of application data from text or XML files. Your import can create or update application records. Use the steps outlined in this topic as a general guide only. Import options and other details differ by the type of data you are importing. Before you import, you must also understand how the data in your file will map to the attributes in the application and what values are expected as described in the related topics.

To help you get started, you can use the example templates provided in Document ID 1503223.1 on My Oracle Support. The templates include columns for the most common application attributes and reference numbers. To simplify mapping of source data to the target table columns, each template column is labeled with the combination of the target object and attribute you must select.

General Steps for Importing Data from a File

To import data from a file:

In the Navigator menu, click the Setup and Maintenance link located under the Tools heading.
The Setup and Maintenance work area appears.
From the All Tasks tab in the Overview region, search for the Manage File Import Activities task.
Click the Go to Task button for the task.
The Manage Import Activities page appears.

Tip

You can also navigate to the Manage Import Activities page by selecting the import task in the work areas for objects that support importing data.
Click the Create button.
The Create Import Activity: Enter Import Options page appears.
In the Name field, enter a name for your import.
In the Object field, select the object you are importing.
In the Source File region, select one of the Upload From options.
Note

If you are importing a file into one of the Oracle Cloud services, then you must upload files from your desktop.
- Desktop
  After you select this option, you must browse for the file.
- URL
- Network
  Enter the path with the following preface file://
  
  For example, if the file is located at /tmp/sample.csv , then your entry is file:///tmp/sample.csv. Note the extra slash in the entry.
If your data file includes a header row, then select the Header Row Included option.
While you can upload files without header rows, doing so makes it more difficult to complete the mapping between the data in your file and the application.
If your file does not use a comma to separate values, then select the correct delimiter in the Data Type field.
The import requires you to create a mapping between the data in the import file and the target attributes in the application. If you previously imported a file with the same format as the file you are importing now, then select an existing mapping from the Import Mapping list. By default, the application saves the import mapping under the import activity name appended with the activation date and time. If you are importing a file in this format for the first time, then you must create the mapping in the next step.
If you are importing one of the following objects, you can import attachments by selecting the Browse option in the Attachments region and selecting a Zip or JAR file of the attachments.
The following import objects support the import of a single attachment for each record:
- Assets
- Interactions
- Opportunities
- Partners
The following import objects support multiple attachments for each record:
- Leads
- Tasks
Note

You must include a column with the names of individual attachments in your import file as described in the Importing Attachments with File-Based Data Import: Explained topic.

In the Import Options region, some of the options in the following table may be available depending on the object you are importing

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	The maximum number of errors before you terminate import. Below the threshold, all records without errors are imported. Above the threshold, no records are imported.
Notification E-Mail	The e-mail address of the individual who will receive import processing notifications.
Customer Data Management Duplicates	This option 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.
Decimal Separator	Decimal separator used in your import file.
Date Format	The formatting of the date fields in your file.
Time Stamp Format	The formatting of time fields in your file.
File Encoding	The overall encoding for your file.

Click Next.
The Create Import Activity: Map Fields page displays the attributes in your file with some sample data. If you are reusing an import mapping, then both the Source and Target columns are already populated. The Source columns represent your file. If you are creating a new mapping, then the Target Object and Attribute columns are blank.
For each column in your file that you want to import, select the target object and one of its attributes. Each import object comes with its own set of attributes.
You can choose not to import a column in your file by selecting the Ignore check box.
If you want to specify a constant value for an attribute in the application, you can add the object, the attribute, and its value in the Set Constant Values region.
Note

If you are importing data using the import templates provided on My Oracle Support, then each column header in your template includes the names of both the target object and the target attribute to simplify your mapping process.
Click Next
The Create Import Activity: Schedule page appears.
By default, the import will start immediately after you click Activate in step 19. You can instead start the import at a time you specify by selecting Specific Date from the Schedule list and entering a start date.
Click Next.
The Create Import Activity: Review and Activate page appears.
Click Activate.
You return to the Manage Import Activities page where you can view the status of your import.

An import activity with the status of Completed indicates that your data was loaded into the application tables.
If the process completes with the status of Completed with Errors, click the status link.
You can view the errors at the bottom of the View Import Status page and by selecting the Attachments link in the Files Processed region.

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.

Tasks in the File-Based Data Import
task group.

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:

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 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.
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.
Schedule the import.
You can schedule to run the import at a time you specify or run it immediately.
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.

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

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:

Create a ZIP or JAR file of the attachment files.
Note

The attachments can be organized in nested folders.

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

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.

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.

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 2	QUALIFIED	8	file_2.doc
Lead 3	QUALIFIED	3	file_3.doc
Lead 4	QUALIFIED	7	file_4.doc

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
Lead 1	QUALIFIED	7	file_1.doc
Lead 2	QUALIFIED	8	file_1.doc
Lead 3	QUALIFIED	3	file_1.doc
Lead 4	QUALIFIED	7	file_1.doc

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 3 includes attachments file_5.doc, file_6.doc, file_7.doc.
Lead 4 has no attachments.

Your data file might look like the data in the following table.

LeadName	StatusCD	ATTACHMENT _FILE _NAME	ATTACHMENT _FILE _NAME	ATTACHMENT _FILE _NAME
Lead 1	QUALIFIED	file_1.doc	file_2.doc	file_3.doc
Lead 2	QUALIFIED	file_4.doc
Lead 3	QUALIFIED	file_5.doc	file_6.doc	file_7.doc
Lead 4	QUALIFIED

File-Based Import Processing: How it Works

The file-based data import process includes processing the source file data and inserting it into the interface tables, moving the interface table data into the destination application tables, and then processing the attachments for the imported objects. Processing factors are subject to the settings defined for the Import Activity, Mapping, and Import Object. You can monitor the processing steps and view process reports for each Import Activity.

This topic describes the following:

Inserting Data in the Interface Tables
Interface Table Data Validation and Error Counts
Interface Table to Destination Application Table Processing
Importing Attachments
Viewing Import Results

Inserting Data in the Interface Tables

Data exists in various sources and in various formats. The file import processing starts with reading the source data, parsing the data, and inserting into the appropriate interface tables. The source of the data comes from the following:

Source file values mapped to target object attributes in the Import Activity.
Constant values defined for target object attributes in the Import Activity.
Default values defined for target object attributes in the Import Object.

Interface Table Data Validation and Error Counts

The data is initially validated against the predefined Import Mapping and the Import Object settings as the interface tables are being populated by the initial file import process. The interface table data is validated again before importing into the destination application tables.

Validation includes:
- Missing required values
- Values that exceed the attribute length
- Invalid values
- Duplicates to existing records in the destination application tables based on the combination of attributes selected for duplicate validation in the predefined Import Mapping.
  
  Note
  
  For the Lead import object, the duplicate checking is only done for existing leads created within the look back days setting of the Import Activity.
- Duplicates to existing records in the destination application tables for Customer Data Management objects based on Matching Configurations.
Errors
Most validation issues are recorded as errors, with the exception of Customer Data Management duplicates found during the Matching Configuration process. In this case, matched records are only considered as errors if:
- Customer Management Duplicates option is set to Do Not Import for the Import Activity and
- The main object of the Import Activity is a consumer, customer, or legal entity object
Allowable Error Count Threshold
The validation of the interface table occurs before any records are imported into the destination application tables. Once the validation process has completed, the count of records with errors is compared to the Allowable Error Count Threshold value specified for the Import Activity. A count above the threshold will stop the import process for all records. If the count is below the threshold, records without errors will import. In either case, records with errors will be reported in the Error and Exception files.

Interface Table to Destination Application Table Processing

The import process orchestrates the import for each of the component objects that make up the overall main objects of the Import Activity.

Importing Attachments

Once the objects have imported successfully, the attachments are processed. The import process matches the source file attachment name to the file name included in the compressed file entered on the Import Activity. The attachment file is imported into Universal Content Manager and then associated as an attachment to the imported object.

Viewing Import Results

You can monitor all file-based 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. Once an Import Activity process has completed, the following processing reports are added as attachments to the process:

Log file. Includes the records that were successfully imported plus the unique destination application table identifiers for the objects.
Exception file. Includes the records that were not imported plus a reference to an error for each record that failed validation.
Error file. Includes all the errors for each record that failed validation.

File-Based Import Objects: Explained

Import objects represent the application and attribute information for business objects that can be imported using external source files.

This topic describes the following:

Import object management options
Custom objects

Import Object Management Options

A single import object can have multiple associated components that are considered objects by themselves. An object and associated objects that can be imported within the same source file are grouped together within the application module class.

Note

Each object includes the Import Activity object (MktImpJobs1). The Import Activity object is a required component of the application module but is not mapped to a source file. All values for this object are derived from the Import Activity definition. Consequently, do not update the Map, Required, and Default Value settings for the Import Activity object.

The following table includes information about the import object:

Option	Description
Attributes	A view-only listing of object attributes that represent each column in the interface table for the object.
Length	A view-only listing of widths for the columns in the interface tables. If the source file values for the attribute have more characters than the attribute length, the source file row will not be imported.
Default Value	Optionally, specify an attribute value to use if a value is not available from the source file or Import Activity constant value.
Map	Enable the list of attributes that can be mapped to a source file or constant value in the Import Mapping and Import Activity Map Fields step.
Required	Specify the list of attributes that must be mapped to source file columns. Consequently, if you have selected an attribute as required, you must also enable the Map option for that attribute. When mapping the external source file, the required target attribute defined for the object are displayed with an asterisk.

Custom Objects

To use the file-based import feature for custom objects, you must first generate the artifacts required for import. You generate these required artifacts within Oracle Fusion CRM Application Composer, after making your object model extensions.

File-Based Import Mapping: Explained

Import mapping enables you to predefine a mapping between the columns provided in a source file and the attributes pertaining to the objects being imported. Once you create a mapping, it can be reused in the Import Activity definition.

This topic contains the following sections:

Import options
Source file options
Target options

Import Options

The following attributes pertain to the import mapping.

Attribute	Description
Object	The business object to be imported.
Name	The name that identifies the mapping in the Import Mapping and Import Activity UIs. If the mapping was initially created while mapping fields directly in the Import Activity user interface and automatically saved without providing a user-defined mapping name, the mapping name is derived from the Import Activity name and date.
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 of values in columns mapped to attributes with a date attribute type.
Timestamp Format	The format of values in columns mapped to attributes with a time stamp attribute type.
Lock	If selected, prevents any user, other than the creator of the mapping, from editing the mapping.

Source File Options

Map each column that the source file is expected to contain with a specific attribute.

The following table describes the details pertaining to columns provided in the source file:

Source Column	Description
Sequence	The sequence number in which the columns are expected to be provided in the source file. Two rows cannot have the same sequence number.
Column Name	The column name expected in the source file if a header row is included, or more generic values such as Column A, Column B, and so on, if the header row is not included for Text file types. The tagging structure is represented for XML file types.
Column Width	Use when the delimiter value is fixed width for Text file types only.
Ignore	Ignore the source file column to exclude the data from being imported.
Required	If selected, a value must exist in the source file or the row will not be imported.

Target Options

The following table describes the details pertaining to corresponding attributes in the target application table:

Target Attributes	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.
Duplicate Validation	If selected, the attribute, along with other selected attributes, determines what constitutes a duplicate object when comparing objects in the interface tables and existing objects in the target application tables. For example, to validate the uniqueness of an object in the target application tables by the combination of an object's name and date, select Duplicate Validation for both attributes in the mapping.

Import Activity Import Options: Explained

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

Source File Data Transformation

The following options are used to identify the formatting of source file data so the data can be correctly interpreted and transformed by the import process:

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

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.

Frequently Asked Questions for File-Based Data Import

What determines the list of objects displayed?

A single import object can have multiple associated components that are considered objects by themselves. Whether or not an associated object can be grouped as a component of another object for the purpose of file import is determined by the complexity of the object structure and how it is stored in the data model. Oracle Fusion provides import objects predefined to meet the file processing import requirements. Consequently, in some cases, more than one source file may be required to capture all associated components of an object.

What happens if I inactivate an Import Activity?

The Import Activity will not stop the currently running process. However, it will stop the next process that has not started plus any future repeating file import activities. You can always activate the process at a later stage.

What happens if I add a marketing list in the Import Activity definition?

File-based data import enables you to record consumers and organization contacts in a marketing list when importing consumer, lead, and response import objects. Select an existing list or create a new one. A marketing list is assigned the list type value of Imported if created while defining an import activity. After the objects are imported successfully, the consumers and contacts are added as members of the marketing list.

Import Objects for Contracts

Importing Contracts: Explained

You can import contracts into the application from a source file using file-based import. To initially set up file-based import for importing contract data, select the Manage File Import Objects and Manage File Import Mappings tasks. To schedule your contract imports, select the Manage File Import Activities task. These tasks are available by selecting Setup and Maintenance from the Tools menu and searching on the task name.

File-based import supports the import of data from an external text or xml file to interface tables and then from interface tables to target application tables.

This topic describes:

What you can import
The interface table
The import process

What You Can Import

Contracts for import can be in Draft, Active, or Expired status but must not have lines. The import file can use names as well as IDs to identify data, for example, Party ID or Party Name. You can import only one version for each contract, with the following data:

Contract header
Primary party (supplier, customer, or partner)
One contract owner: depending on the owner role, this is either an employee or salesperson of the contract's business
One primary contract party: a supplier or partner or customer
Primary contract document as an attachment
Additional attachments: the import file lists the attachments which are imported using the file import UI, either individually or as a ZIP file.

You can import new contracts, but you cannot update or delete existing contracts through imports.

Interface Table

The application uses the following database table for importing contracts:

Table	Description
OKC_IMP_CONTRACT_HEADERS	The interface table used to load contract data from external systems. This table maps to logical contract data: contract header, contract party, contract party contact, contract terms, and contract attachments.

Details about the fields and valid values for import are available from the Oracle Enterprise Repository for Oracle Fusion Applications.

Importing Contracts From a Source File

To import contracts, use the file-based import feature and upload contract data into the interface table. To access this feature, select the Manage File Import Activities task, available by selecting Setup and Maintenance from the Tools menu and searching on the task name. A detailed description of how to import data using file-based import is described in a related topic.

Note

An import mapping, which details the mapping between source file columns and contract attributes, is provided in the Edit Import Activity: Map Fields page for your use, but you can define additional import mappings if required.

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 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 need to customize Oracle Fusion Applications to capture additional attributes that are critical to the way you do your 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 contract data corresponds with the data in Oracle Fusion Applications 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 contract.

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.

Comparing Business Object Data

Each import object is a collection of attributes that help 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 contract.

A good understanding of the attribute details of the import objects is critical 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.

Import Object	Related Import Object Topic
Contract	Contract Import Objects: How They Work Together

Note

You can use the keywordimporting contracts to search for related topics in Oracle Fusion Applications Help.

Extensible Attributes

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.

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 feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables.

The Define File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the import objects, to create source file mappings, and to schedule the import activities. You submit file-based import activities for each import object. When creating a new 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

Verifying Your Imported Data

Oracle Fusion Applications provide File-Based Import activity reports, which 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:

Target import object concepts
Target objects for the Contract import object
Target import object attributes
Target object attribute reference guide files

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 import file to the target attributes in Oracle Fusion Applications, you must 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.

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.

Target Import Object Attributes

You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle 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.

To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area.

Note

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

Target Import Objects Attributes Resources

To access the reference guide file for the contract 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 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

Importing Employee Resources Using File-Based Import: Explained

This topic explains how to prepare and import employee resource data from an external data source into Oracle Fusion Applications using the File-Based Data Import feature.

Employee resources are employees within the deploying company who can be assigned work objects. You must create or import employee resources before you can associate them with resource organizations, resource teams, or work objects. You enter your employee resource information using the Setup and Maintenance work area, Manage Resources task, or you can import data to create new or update existing employee resources.

Consider the following questions when importing your data:

How does your legacy system or source system represent the employee resource compared to how Oracle 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 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.

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.

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 employee resource.

A good understanding of the attribute details of the import objects is critical to preparing your import data. The reference guide files contain descriptions, logic used to choose default values, and validation information for each 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
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.

Extensible Attributes

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 Employee Resources Using File-Based Data Import

For the employee resource business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables.

The Define File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. When creating a new employee resource, you import the Employee Resource import object.

You must be assigned the Master Data Management Administrator job role to access and submit the import activities for employee resources.

Verifying Your Imported Data

Oracle Fusion Applications provide File-Based Import activity reports, which can be used to verify imported data. Users with either the Master Data Management Administrator job role can also navigate to the Manage Resources work area to view the imported employee resources.

Employee Resource Import Objects: How They Work Together

Employee resources are employees to whom you can assign work objects, for example, service agents, sales managers, and so on. You can import all your employee resource information using the Employee Resource import object. This topic describes this import object.

This topic introduces the following:

Target import object concepts
Target objects for the Employee Resource import object
Target import object attributes
Target import object attribute reference guide files

Target Import Object Concepts

The Employee Resource import object is used to import an employee resource's worker profile information, such as first name, last name, address, and so on, and the employee resource's resource profile information, such as resource organization and resource team memberships. To map the source data in your import file to the target attributes in Oracle Fusion Applications, you must understand how the target objects are related and what attributes are included in each target object.

Employee Resource Target Import Objects

The target import objects included in the Employee Resource import object are grouped into information about the employee resource's profile and the employee resource's address information. The Worker profile is the target import object containing attributes to import information about the employee resource.

When updating an existing employee resource, you must provide the parent reference information of the existing employee resource. When importing an employee resource's resource team information, you must provide relationship reference information in addition to the parent reference, because an employee resource can belong to more than one team simultaneously.

To update the information for an existing employee resource or to create an employee resource record, you can import employee resource profile information and addresses. The following target import objects are for creating and updating employee resource information: WorkerProfile, ResourceProfile, and PrimaryAddress.

To update or create an employee resource's resource profile, use the following target import objects: ResourceOrganizationMembership and ResourceTeamMembership.

Target Import Objects Attributes

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 marketing response.

Target Import Objects Attributes Resources

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

The following table lists the reference guide files that are available from the Documentation tab for the Employee Resource File-Based Data Import asset.

Target Import Object	Description	Reference Guide File Names
WorkerProfile	Contains information that identifies an employee. Sample attributes: ResourceProfile and PrimaryAddress. Reference attributes: PartyOrigSystem, PartyOrigSystemReference, and PartyId.	HRC_LOADER_BATCH_LINES_Reference
ResourceProfile	Contains information about a resource. Sample attributes: PartyId, FirstName, LastName, Department, and JobCode. Reference attributes: PartyOrigSystem, PartyOrigSystemReference, and PartyId.	HZ_IMP_RESOURCES_Reference
PrimaryAddress	Indicates the address of a resource. If the resource has multiple addresses, then the first address is designated as the primary address. Sample attributes: Address1, Address2, City, Country, County, State, and PostalCode. Reference attributes: PartyOrigSystem, PartyOrigSystemReference, and PartyId.	HZ_IMP_PARTYSITES_T_Reference
ResourceOrganizationMembership	Contains the employee resource's resource organization membership information. Sample attributes: RequestId, PartyId, ParentOrganizationName, OrganizationId, OrganizationName, and OrganizationUsage. Reference attributes: PartyOrigSystem, PartyOrigSystemReference, and PartyId.	HZ_IMP_GROUP_MEMBERS_Reference
ResourceTeamMembership	Contains the employee resource's resource team membership information. Sample attributes: RequestId, TeamMemberId, TeamId, and TeamNumber. Reference attributes: PartyOrigSystem, PartyOrigSystemReference, and PartyId.	HZ_IMP_TEAM_MEMBERS_Reference

Importing Geographies Using File-Based Import: Explained

This topic describes the tasks you must perform to import geography information. A geography is any region with a boundary around it, regardless of its size. It might be a state, a country, a city, a county, or a ward. You must create or import geographies before you can associate them with custom zones and addresses.

Consider the following questions when importing your data:

How does your legacy system or source system represent the geography 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?
What import features are available for importing your business object?
How do you verify your imported data?

Comparing Business Object Structures

You must understand how your geography data corresponds with the data in Oracle 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.

Comparing Business Object Data

A good understanding of the attribute details of the import objects is critical 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.

Import Object	Related Import Object Topic
ImpGeography	Geography Import Objects: How They Work Together

Hint: You can use the keyword importing geographies to search for related topics in Oracle Fusion Applications Help.

Extensible Attributes

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 feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables.

The Define File-Based Data Import Setup and Maintenance task list includes the tasks needed to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. When creating a new geography, you import the Geography object. You must be assigned the Master Data Management Administrator job role to access and submit the import activities for geographies.

When importing geography information, you must provide the parent reference information for all parent levels for the entity.

Verifying Your Imported Data

Oracle Fusion Applications provide File-Based Import activity reports, which can be used to verify imported data. Users with the Master Data Management Administrator job role can also navigate to the Manage Geographies work area to view the imported geographies.

Geography Import Objects: How They Work Together

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

This topic introduces the following:

Target import object concepts
Target objects for the Geography import object
Target import object attributes
Target import object attribute reference guide files

Target Import Object Concepts

The Geography import object is used to import geography hierarchy information to create or update the geography data of a country. To map the source data in your import file to the target attributes in Oracle Fusion Applications, you must understand how the target objects are related and what attributes are included in each target object.

Geography Target Import Objects

The target import objects in the Geography import object contain information about the geography hierarchy. When updating an existing geography, you must provide the parent reference information of the existing geography, which connects the geography to the country of which it is a part.

Use the ImpGeography target import object to create and update geography information.

Note

Before you import geography data for a country, you must define the country's geography structure.

Target Import Objects Attributes

You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle 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.

Target Import Objects Attributes Resources

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

For detailed information on importing geographies using file-based import, refer to Document No. 1481758.1, Importing Master Reference Geography Data, on the Oracle Support site.

The following table lists the reference guide files that are available from the Documentation tab for the Geography File-Based Data Import asset.

Target Import Object	Description	Attribute Reference Guide File Names
ImpGeography	Contains information that captures a country's geography hierarchy details. Sample attributes: CountryCode, GeoDataProvider, GeographyType, PrimaryGeographyCode, PrimaryGeographyCodeType, and PrimaryGeographyName. Reference attribute: CountryCode	HZ_IMP_GEOGRAPHIES_T_Reference

Target Import Object

Description

Attribute Reference Guide File Names

ImpGeography

Contains information that captures a country's geography hierarchy details.

Sample attributes: CountryCode, GeoDataProvider, GeographyType, PrimaryGeographyCode, PrimaryGeographyCodeType, and PrimaryGeographyName.

Reference attribute: CountryCode

HZ_IMP_GEOGRAPHIES_T_Reference

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 information compared to how Oracle Fusion Applications represent the same data?
Do you have to configure values in Oracle Fusion Applications to map your existing data values to the Group Customer import object?
Do you have to customize Oracle Fusion Applications to capture additional attributes that are critical to the way you do business?
What import features are available for importing your business object?
How do I verify my imported data?

Comparing Business Object Structures

You must understand how your group customer data corresponds with the data in Oracle Fusion Applications 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 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-level components, such as classifications, additional names, additional identifier, and members. These child entities can have other entities as their child entities. This hierarchical structure supports one-to-many relationships between the components that make up the group customer.

The following figure shows the Group Customer import object and its child entities.

The group customer profile contains basic information about the group customer, such as the group name, group type, and the group-party usage. For each group customer, you can assign classifications, members, relationships, additional identifier, and additional names.

Note

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 Phone Contact Preference entity captures the contact preference of the group for the phone contact method.

Comparing Business Object Data

A good understanding of the import objects and attribute details is critical to preparing your import data. Oracle Fusion Applications attribute details are available for your reference in the Oracle Enterprise Repository. The reference guide files contain descriptions, default values, and validations for each of the Oracle Fusion Applications attributes. The validation information includes the navigation to the task where you can define values in Oracle Fusion Applications. For example, if you have values in your data that correspond to a choice list in Oracle Fusion Applications, then the validation information for that attribute will provide the task name in the Setup and Maintenance work area where you can define your values.

Extensible Attributes

If you want to extend the Oracle Fusion Applications object data 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 Group Customers Using File-Based Data Import

For the group customer business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables.

The Define File-Based Data Import Setup and Maintenance task list includes the tasks that are required to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. An import activity defines the instructions for processing import data, including the source file, import mapping from the source file to the 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.

Verifying Your Imported Data

Oracle Fusion Applications provide File-Based Import activity reports, which you can use to verify imported data. You can view the list of import activities from the Manage Import Activities page. You can verify the status of the import activity by clicking the Status column for your import activity. Alternatively, you can also navigate to the Party Center work area to view the customer information that you have imported.

Group Customer Import Objects: How They Work Together

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

Target import object concepts
Target objects for the Group Customer import object
Target import object attributes
Target import object attribute reference guide files for evaluating and mapping source file data

Group Customer Target Import Objects Concepts

The Group Customer import object imports group customers and its members. The Group Customer import object is split into separate target import objects for organizing the individual attributes for the different aspects of the group customer. To map the source data in your import file to the target attributes in Oracle 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.

Target Import Objects Attributes

You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle 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.

Note

If any of the attributes 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 group customer.

Target Import Objects Attributes Resources

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

The following table lists the reference guide files that are available from the Documentation tab for the Group Customer File-Based Data Import asset.

Target Import Object	Description	Reference Guide File Names
GroupProfile	Includes detailed group customer information, such as, group name and group type. The default party usage for a group customer is SALES_PROSPECT. Sample attributes: AnnualIncome, NumOfDependents, MedianAge, and CertificationLevel. Reference attributes: PartyOrigSystem, PartyOrigSystemReference, and PartyId.	HZ_IMP_PARTIES_T_Reference
Relationship	Includes information about the relationship between the group customer and the group member. You must enter a relationship code in the RelationshipCode column, when creating a relationship. Sample attributes: RelationshipCode and RelationshipType. Reference attributes: RelOrigSystem RelationshipID, and RelOrigSystemReference.	HZ_IMP_RELSHIPS_T
Member	Includes information about the group customer member. Sample attributes: ObjectKey and SubjectId. Reference attributes: RelOrigSystem RelationshipID, and RelOrigSystemReference.	HZ_IMP_RELSHIPS_T
Classification	Includes classification information for a group customer. 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.	HZ_IMP_CLASSIFICS_T
AdditionalIdentifier	Includes detailed information about an additional identifier for the group customer. Sample attributes: IdentifierValue, IdentifierType, Country, and IssuingAuthorityName. Reference attributes: IdentifierValue, AdditionaldentifierOrigSystem, and AdditionalldentifierOrigSystemReference.	HZ_IMP_ADDTNLPARTYID_T
AdditionalName	Indicates alternative name of a group customer. Sample attributes: Additional Name, Additional Name Type, and GlobalPreferredNameFlag. Reference Attributes: AdditionalNameOrigSystem and AdditionalNameOrigSystemReference.	HZ_IMP_ADDTNLPARTYNAMES_T
Url	Indicates the Url of the group customer. Sample attributes: ContactPointType, PrimaryFlag, Url, and WebType. Reference attributes: CpOrigSystem and CpOrigSystemReference	HZ_IMP_CONTACTPTS_T_Reference
InstantMessenger	Indicates the instant messenger or social networking information of a customer contact. Sample attributes: ContactPointPurpose, EndDate, InstantMessagingAddress, and InstantMessengerType. Reference attributes: CpOrigSystem, CpOrigSystemReference, and Objectkey.	HZ_IMP_CONTACTPTS_T_Reference
Fax	Indicates the fax of the group customer. Sample attributes: PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. Reference attributes: CpOrigSystem and CpOrigSystemReference.	HZ_IMP_CONTACTPTS_T_Reference
FaxContactPreference	Indicates the group customer preference about being contacted through fax. Sample attributes: ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. Reference attributes: CpOrigSystem and CpOrigSystemReference.	HZ_IMP_CONTACTPREFS_Reference
Mobile	Indicates the mobile number of group customer. Sample attributes: ContactPointPurpose, ContactPointType, PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, PhoneNumber, and PrimaryFlag. Reference attributes: CpOrigSystem and CpOrigSystemReference.	HZ_IMP_CONTACTPTS_T_Reference
MobileContactPreference	Indicates the group customer's preference about being contacted through mobile phone. Sample attributes: ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. Reference attributes: CpOrigSystem and CpOrigSystemReference.	HZ_IMP_CONTACTPREFS_Reference
Phone	Indicates the primary phone number of the group customer. If the group has multiple phone numbers, one of the phone numbers is designated as the primary phone number. Sample attributes: PhoneAreaCode, PhoneCountryCode, PhoneExtension, PhoneLineType, and PhoneNumber. Reference attributes: CpOrigSystem and CpOrigSystemReference.	HZ_IMP_CONTACTPTS_T_Reference
PrimaryPhoneContactPreference	Indicates the group customer's preference about being contacted through phone. Sample attributes: ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. Reference attributes: CpOrigSystem and CpOrigSystemReference.	HZ_IMP_CONTACTPREFS_Reference
Email	Indicates the e-mail of the group customer. Sample attributes: ContactPointPurpose, EmailAddress, and StartDate. Reference attributes: CpOrigSystem and CpOrigSystemReference.	HZ_IMP_CONTACTPTS_T_Reference
EmailContactPreference	Indicates the group customer's preference about being contacted through e-mail. Sample attributes: ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. Reference attributes: CpOrigSystem and CpOrigSystemReference.	HZ_IMP_CONTACTPREFS_Reference
Address	Indicates the address of a group customer. If the group has multiple addresses, one of the addresses is designated as the primary address. Sample attributes: Address1, Address2, City, Country, County, State, and PostalCode. Reference attributes for location: LocationOrigSystem, LocationOrigSystemReference, and LocationId1. Reference attributes or party sites: SiteOrigSystem, SiteOrigSystemReference, and PartysiteId1.	HZ_IMP_LOCATIONS_T, HZ_IMP_PARTYSITES_T
AddressContactPreference	Indicates the group customer's preference about being contacted at the primary address. Sample attributes: ContactType, PreferenceCode, PreferenceEndDate, PreferenceStartDate, and ReasonCode. Reference attributes: CpOrigSystem, CpOrigSystemReference.	HZ_IMP_CONTACTPREFS_Reference
AddressPurpose	Indicates the purpose of a group customer's address. Sample attributes: SiteUseType, EndDate, and StartDate. Reference attributes: SiteOrigSystem and SiteOrigSystemReference.	HZ_IMP_PARTYSITEUSES_T

Importing Resource Teams Using File-Based Import: Explained

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

Consider the following questions when importing your data:

How does your legacy system or source system represent the resource team compared to how Oracle 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 resource team 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 resource team.

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.

Comparing Business Object Data

Import Object	Related Import Object Topic
Resource Team	Resource Team Import Objects: How They Work Together

Hint: You can use the keyword importing resource teams to search for related topics in Oracle Fusion Applications Help.

Extensible Attributes

Importing Resource Teams Using File-Based Data Import

For the resource team business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables.

You must be assigned the Master Data Management Administrator job role to access and submit the import activities for resource teams.

Verifying Your Imported Data

Oracle Fusion Applications provide File-Based Import activity reports, which can be used to verify imported data. Users with the Master Data Management Administrator job role can also navigate to the Manage Resource Teams work area to view the imported resource teams.

Resource Team Import Objects: How They Work Together

This topic describes the Resource Team import object. You use two main import objects, ResourceTeam and ResourceTeamUsage, when you submit a file-based import activity to import resource team information.

This topic introduces the following:

Target import object concepts
Target objects for the Resource Team import object
Target import object attributes
Target object attribute reference guide files

Target Import Object Concepts

The Resource Team import object is used to import resource teams and information to create or update associated organizations or persons. The Resource Team import object is split into separate target import objects for organizing the individual attributes of the different aspects of the resource team and the resource team's usage. To map the source data in your import file to the target attributes in Oracle Fusion Applications, you must understand how the target objects are related and what attributes are included in each target object.

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 ResourceTeam target import object contains information that identifies the resource team, such as the team's name, ID, active dates, and so on. The ResourceTeamUsage target import object contains information that captures the usage of the resource team.

To import or update a resource team, use the ResourceTeam target import object. To import or update a resource team's usage, use the ResourceTeamUsage target import object.

Target Import Objects Attributes

You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle 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.

Note

Target Import Objects Attributes Resources

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

The following table lists the reference guide files that are available from the Documentation tab for the Resource Team File-Based Data Import asset.

Target Import Object	Description	Reference Guide File Names
ResourceTeam	Captured information that identifies a resource team. Sample attributes: TeamId, TeamName, TeamDescription, and Language.	HZ_IMP_TEAMS_Reference
ResourceTeamUsage	Contains information that indicates the usage of the resource team. Sample attributes: RequestId, TeamUsageId, TeamId, and Usage.	HZ_IMP_TEAM_USAGES_Reference

Target Import Object

Description

Reference Guide File Names

ResourceTeam

Captured information that identifies a resource team.

Sample attributes: TeamId, TeamName, TeamDescription, and Language.

HZ_IMP_TEAMS_Reference

ResourceTeamUsage

Contains information that indicates the usage of the resource team.

Sample attributes: RequestId, TeamUsageId, TeamId, and Usage.

HZ_IMP_TEAM_USAGES_Reference