Oracle® Fusion Applications Customer Data Management Implementation Guide 11g Release 7 (11.1.7) Part Number E20433-07

Home

Contents

Book List

Contact Us

Previous

Next

PDF

27 Common Customer Data Management Configuration: Define File-Based Data Import

This chapter contains the following:

Define File-Based Data Import

Getting Started with File-Based Import: Documentation Overview

Importing Consumers

Importing Contacts

Importing Country Structures

Importing Customer Hierarchies

Importing Customers

Importing Employee Resources

Importing Geographies

Importing Group Customers

Importing Legal Entities

Importing Resource Teams

FAQs for Define File-Based Data Import

Define File-Based Data Import

File-Based Data Import Tasks: How They Work Together

The tasks in the Define File-Based Data Import task group, available from the Setup and Maintenance work area, enable you to import data from text or XML files. This topic explains the role each task plays in the import process.

The following figure provides an overview of the File-Based Data Import group of tasks and their relationships. Each task is explained in the sections that follow.

Manage File Import Activities Task

Use this task to import your data by creating import activities and monitoring their progress. Creating an import activity involves completing the following steps:

1. Set up the import options.

   You select the object you are importing, specify the file format and different import options, and upload the file with your data. The options that are available depend on the object you are importing. Some import objects, for example, permit you to upload a ZIP or Java archive (JAR) file of attachments that will be attached to the records in the application after the data file import is complete.

2. Map the fields.

   For this task, you create a mapping of the data in your file and the attributes in the application. You can also reuse a mapping you have created in past import activities or use the Manage File Import Mappings task. Any mapping you create in an activity is automatically saved and can be reused in subsequent imports and managed using the Manage File Import Mappings task.

3. Schedule the import.

   You can schedule to run the import at a time you specify or run it immediately.

4. Review and activate the import activity.

   You activate the import activity by clicking the Activate button.

Manage File Import Mappings Task

This task permits you to do the following:

• Manage existing mappings between the data in your import file and the application attributes. For example, you can lock a mapping so that it cannot be modified or edit the mapping to skip attributes during import.

• Create new mappings without a data file.

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

Manage File Import Objects Task

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

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.

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.

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.

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:

1. In the Navigator menu, click the Setup and Maintenance link located under the Tools heading.

   The Setup and Maintenance work area appears.

2. From the All Tasks tab in the Overview region, search for the Manage File Import Activities task.

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

4. Click the Create button.

   The Create Import Activity: Enter Import Options page appears.

5. In the Name field, enter a name for your import.

6. In the Object field, select the object you are importing.

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

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

9. If your file does not use a comma to separate values, then select the correct delimiter in the Data Type field.

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

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

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

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

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

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

16. Click Next

    The Create Import Activity: Schedule page appears.

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

18. Click Next.

    The Create Import Activity: Review and Activate page appears.

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

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

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.

How You Import Attachments

To import attachment, you:

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

   Note

   The attachments can be organized in nested folders.

2. Add an additional column to the data file you are importing, and enter the names of the attachment files. The header of this column must always be: ATTACHMENT_FILE_NAME.

   This reference column specifies which attachment file belongs to which record. Other optional columns listed in the following table can be used to upload other attachment information, such as a brief description.

   The following table lists all of the available attributes with the header names you must use.

   
   

   Column Header	Required or Optional	Description
   ATTACHMENT_FILE _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.

3. Upload the ZIP or JAR file with the attachments when you create the file import activity.

   You do not map the attachment attributes. The application identifies the special names in the column headers.

   Note

   You must upload one ZIP file of all the attachments. You cannot upload attachments in multiple files or add additional attachments after you upload the ZIP file the first time.

Importing Single Attachments

The following example illustrates the steps required for importing one attachment for each record.

1. Create a ZIP or Java archive (JAR) file of all of your attachments, for example: myfiles.zip:

   • file_1.doc

   • file_2.doc

   • file_3.doc

   • file_4.doc

   Note

   The numbers in the file names are provided for this example. They are not required.

2. In the import file, add the additional columns to capture the attachment information.

   At a minimum, you must include a column with the header name: ATTACHMENT_FILE_NAME to capture the attachment file names. You must use this header name without variation so that the application will identify it.

   Unlike the other attributes in your import file, you do not map the attachment columns to import objects and attributes when you create an import activity. The application does the mapping automatically. The mapping is based on the column name.

   Your import file might contain data similar to that shown in the following table.

   
   

   LeadName	StatusCD	Score	ATTACHMENT _FILE _NAME
   Lead 1	QUALIFIED	7	file_1.doc
   Lead 2	QUALIFIED	8	file_2.doc
   Lead 3	QUALIFIED	3	file_3.doc
   Lead 4	QUALIFIED	7	file_4.doc

3. When you create the import activity to import your file, you upload the ZIP or JAR file from your desktop by cllicking the Browse button in the Attachments region in the Import Options page.

   The ZIP or JAR file is imported at the same time as the data file.

Note the following:

• If a record does not have an attachment, then leave the column value blank.

• You can specify a single file to be the attachment for more than one or for all records you are importing. For example, if you wanted the same file to be attached to all the four leads, then your import file structure would be like the data in the following table.

  
  

  LeadName	StatusCD	Score	ATTACHMENT_FILE _NAME
  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.

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.

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.

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.

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.

The following table includes information about the import object:

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.

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:

Target Options

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

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.

Import Activity Source File Options: Explained

The Import Activity consists of a step by step guided process to assist you with creating an import activity for a given object.

This topic describes the source file options defined in the Import Activity that are used by the import process to locate and parse the source file data.

Source File Data

Enter attribute details pertaining to the source file as follows:

Source File Location

The following outlines the options that are available to you when locating your source file for import.

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:

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.

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:

The following table outlines the target columns:

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:

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.

Getting Started with File-Based Import: Documentation Overview

This topic provides an overview of the types of help available for importing legacy and other data into Oracle Fusion CRM using File-Based Data Import.

There are three main sources of information for import:

• Help topics about using the File-Based Data Import tool are linked to the application pages and available by clicking the help icon.

  These topics provide general information about import.

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

  Help topics provide information on the import objects, list the reference guides you must consult for information on individual attributes, and provide examples.

  You can navigate to help by selecting Applications Help from the Help menu at the top right of every application page.

  There you can view individual help topics or download implementation guides. In the implementation guides, you can find the import topics grouped under the File-Based Data Import heading in the Define Common CRM Configuration task group.

• Oracle Enterprise Repository, which contains reference guides with detailed information on individual attributes.

  You can search for the reference guides by name in the repository, which is available at the following URL: https://fusionappsoer.oracle.com/oer/index.jsp

To understand what attributes are available for import for each object, follow these steps:

1. Start by searching help using the key word importing and the name of the object you are importing.

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

   Depending on the complexity of the import, your search will return one or more of the following help topic types:

   
   

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

2. Using the names of the reference guides listed in the <import object name> Import Objects: How They Work Together topic, search for and download the reference guides from the Oracle Enterprise Repository.

   These guides include detailed descriptions of attributes and permitted values.

Importing Consumers

Importing Consumers Using File-Based Import: Explained

This topic explains how to prepare and import consumer data from an external data source into Oracle Fusion Applications, using the File-Based Data Import feature. A consumer is a person who intends to purchase goods and services. Within Oracle Fusion Applications, a person with a selling relationship is referred to as a consumer. A consumer import object allows you to import all information about a consumer, such as the consumer profile, consumer address information, consumer contact point information, and consumer contact preference information.

You must consider the following questions before importing consumer information:

• How does your legacy or source system represent the consumer information compared to how Oracle Fusion Applications represent the same data?

• Do you have to configure values in Oracle Fusion Applications to map them to your existing data values?

• Do you have to customize Oracle Fusion Applications to capture attributes that are critical to the way you do business?

• What import features are available for importing your business object?

• How do I verify my imported data?

Comparing Business Object Structures

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

The Oracle Fusion Applications consumer structure is hierarchical. The root of the hierarchy is the consumer profile, which must exist before you can import lower-level entities, such as e-mail, sell-to address, sales account profile, and fax. These child entities can have other entities as their child entities. This hierarchical structure supports one-to-many relationships between the components that make up the consumer.

The following figure shows the consumer and its child entities.

The person profile contains basic information about the consumer, such as the first name, last name, and party usage. For each consumer, you can have other information, such as sell-to addresses, phone details, and sales account profile.

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

A good understanding of the import objects and attribute details is critical to preparing your import data. Oracle Fusion Applications attribute details are available for your reference in the Oracle Enterprise Repository. The reference guide files contain descriptions, default values, and validations for each of the 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.

Extensible Attributes

If you have to extend the Oracle Fusion Applications import object to import your legacy or source data, then you must use Oracle Fusion Applications CRM Application Composer to design your object model extensions and to generate the required artifacts to register your extensions and make them available for importing. The corresponding import object is updated with the extensible attributes, which can then be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the standard import object attributes.

Importing Consumers Using File-Based Data Import

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

The Define File-Based Data Import Setup and Maintenance task list includes the tasks required to configure the import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities for each import object. When creating a consumer, you use the Consumer import object. An import activity defines the instructions for processing the import data, including the source file, import mapping from the source file to the Oracle Fusion Applications object and attribute, and the import schedule.

When importing consumer information, you first import the basic person profile information and then the child entities for the consumer. When importing child entities, you must provide the parent reference information for all parent levels for the entity. You must provide the PartyOrigSystem and PartyOrigSystemReference of the consumer when importing contacts for the consumer. PartyOrigSystem is the source system code that identifies the source of the information being imported. PartyOrigSystemReference is unique for each row of data within a single import, and is a combination of PartyOrigSystem and a unique reference. For example, you first import basic profile details, such as first name, last name, party type, and party usage. You then import other information, such as additional names, e-mail, sell-to address, and primary phone for the consumer.

Verifying Your Imported Data

You can view the list of import activities from the Manage Import Activities page. You can verify your imported data by clicking the Status column for your import activity. Alternatively, you can also navigate to the Customer Center work area to view the consumer information that you have imported.

Consumer Import Objects: How They Work Together

The Consumer import object allows you to import consumers, their detailed information, and contacts related to the consumer. This topic describes the Consumer import object and introduces the following:

• Target import object concepts

• Target objects for the Consumer import object

• Target import object attribute

• Target object attribute reference guide files

Consumer Target Import Object Concepts

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

The target import objects included in the Consumer import object are grouped into information about the consumer. The person profile is the target import object containing attributes to import information about the consumer. When updating an existing consumer with additional information, you must provide the parent reference information for the existing consumer.

To update the information for an existing consumer or to create a consumer record, you can import consumer profile information, addresses, and contact points, such as phone and fax number. The following target import objects are for creating and updating the corresponding consumer information: PersonProfile, PersonAddress, PrimaryPhone, Fax, Mobile, AdditionalName, e-mail, SellToAddress, and SalesAccountProfile.

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 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 import object and target object attribute. You can predefine and manage import mappings using the File-Based Import Mapping task, or you can define the mapping when you define the import activity using the File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area.

Target Import Objects Attributes Resources

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

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

Importing Contacts

Importing Contacts Using File-Based Import: Explained

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

A contact is a person party related to a customer, and the contact object contains information that identifies the contact and offers the contact points of the contact. Contact points can be geographical addresses, phone numbers, e-mail IDs, URLs, messenger IDs, and so on. The contact object also contains contact preference information for the contact.

You must create or import contacts before you can associate them with customer objects. You must consider the following questions before importing contact information:

• How does your legacy system or source system represent the contact 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 contact 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 contact.

In Oracle Fusion Applications, one table stores the contact information and another table optionally stores contact point details for that contact. A contact point is an identified means to contact a party. Contact points can be phone numbers, e-mail IDs, Web site addresses, or instant messenger IDs.

The following figure shows the contact object and its child entities.

The contact profile contains basic information about the contact, such as the contact name, party type, and party usage. For each contact, you can assign classifications, phone details, and additional names. If the contact is a consumer, then the contact relationship of the consumer includes other child entities that capture information about the consumer contact, such as contact job, contact phone, contact address, and contact e-mail.

Import Objects for the Contact

To facilitate the import of contacts, Oracle Fusion Applications incorporate the structure of the contact business object into import objects. The import object for contacts is Contact.

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

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

Hint: You can use the keyword importing contacts 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 Contacts Using File-Based Data Import

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

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

Verifying Your Imported Data

Oracle Fusion Applications provide File-Based Import activity reports, which can be used to verify imported data. You can also navigate to the Customer Center work area to view the contact information that you have imported.

Contact Import Objects: How They Work Together

You can import all your contact information using the Contact import object. This topic describes this import object and introduces the following

• Target import object concepts

• Target objects for the Contact import object

• Target import object attributes

• Target import object attribute reference guide files

Target Import Object Concepts

The Contact import object is used to import a contact's profile information, such as first name, last name, address, and so on, and contact point information, such as phone numbers, fax, e-mail IDs, and so on. The Contact import object is split into separate target import objects for organizing the individual attributes of the different aspects of the contact's profile and contact points. To map the source data in your import file to the target attributes in Oracle Fusion Applications, you must understand how the target objects are related and what attributes are included in each target object.

Contact Target Import Objects

The target import objects included in the Contact import are grouped into information about the contact and the contact's relationship with other parties. The contact profile is the target import object containing attributes to import information about the contact. You can have multiple contact relationships associated with a contact. There are multiple target import objects that include attributes to import contacts and their related information.

When updating an existing contact, you must provide the parent reference information of the existing contact. When importing contact profile or contact point information for a contact, you must provide relationship reference information in addition to the parent reference. You must provide this information because a contact can have multiple relationships with an organization, such as employee or board member. When importing information about a contact, you must refer to the specific relationship that you want to import information for. For example, you must specify whether you want to import information for John Smith the employee or John Smith the board member. If you do not include the reference information for a contact relationship, then the import process creates a new relationship.

To update the information for an existing contact or to create a contact record, you can import contact profile information, addresses, and contact points. The following target import objects are for creating and updating contact information: PersonProfile, Fax, PrimaryPhone, Url, SalesAccountProfile, Classification, AdditionalName, Relationship, and AdditionalIdentifier.

To update or create a contact point, use the following target import objects: ContactRelationship, ContactJob, ContactAddress, ContactEmail, ContactPhone, ContactMobile, ContactInstantMessenger, and ContactFax. All contact-point-related entities, such as phone or e-mail, include a child entity that captures the contact preference. For example, the ContactPhoneContactPreference entity captures the contact preference of the primary phone contact method.

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

Target Import Objects Attributes Resources

To access the reference guide files for the response'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 Response File-Based Data Import asset.

Importing Country Structures

Importing Country Structures Using File-Based Import: Explained

This topic explains how to prepare and import country structure data from an external data source into Oracle Fusion Applications using the File-Based Data Import feature. A country structure is a hierarchical grouping of geography types for a country. For example, the geography structure for the United States has the geography type of State at the top, followed by the County, then the City, and finally the Postal Code.

You can use the country structure to set up the following:

• The relationships between geographies within a country

• The types of geographies that you can define for a country

Consider the following questions when importing your data:

• How does your legacy system or source system represent the country structure compared to how Oracle 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 country structure data corresponds with the data in Oracle Fusion Applications in order to be able to map your legacy data to the data needed by Oracle Fusion Applications. First, you must understand how Oracle Fusion Applications represent the structure of the data for a country structure.

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

Import Objects for the Country Structure

To facilitate the import of country structures, Oracle Fusion Applications incorporate the structure of the country structure into import objects. The import object for country structures is GeoStructureLevel.

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

A good understanding of the attribute details of the import objects is critical to preparing your import data. For information about the Oracle 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.

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 Country Structures Using File-Based Data Import

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

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

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

Verifying Your Imported Data

You can view the list of import activities from the Manage Import Activities page. You can verify your imported data by clicking the Status column for your import activity.

Country Structure Import Objects: How They Work Together

This topic describes the Country Structure import object. You use the Country Structure import object when you submit a file-based import activity to import your country structure information. This topic introduces the following:

• Target import object concepts

• Target objects for the Country Structure import object

• Target import object attributes

• Target object attribute reference guide files

Target Import Object Concepts

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

Country Structure Target Import Objects

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

Target Import Objects Attributes

You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Fusion Applications attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference guide file includes attribute descriptions, default values, and validations performed by the import process. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required.

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

Target Import Objects Attributes Resources

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

Importing Customer Hierarchies

Importing Customer Hierarchy Using File-Based Import: Explained

This topic describes how to import a customer hierarchy and customer hierarchy members. A customer hierarchy captures the hierarchical relationships that a customer has with other customers. A customer hierarchy consists of hierarchy members. A customer hierarchy can be used to process payments from one customer and apply them to another customer in the same hierarchy. It can also be used to create the revenue roll-up report that rolls up revenue numbers from opportunities for all customers in a hierarchy.

You must consider the following questions before importing customer hierarchy information:

• Are all members of the customer hierarchy in Oracle Fusion Applications?

• Do I have to import additional hierarchy members to complete the hierarchy?

• How does your legacy system or source system represent the promotion compared to how Oracle Fusion Applications represent the same data?

• Do you have to configure values in Oracle Fusion Applications to map your existing data values to the Customer import object?

• Do you have to customize Oracle Fusion Applications to capture additional attributes that are critical to the way you do business?

• What import features are available for importing your business object?

• How do I verify my imported data?

To import a customer hierarchy, you must:

1. Import customers who must be a part of the hierarchy.

2. Import a hierarchy definition that includes the hierarchy structure and the root node.

3. Import members from the existing customers into the hierarchy.

Comparing Business Object Structures

Before you can import your legacy or source system customer hierarchy data, you must first analyze the data and see how it corresponds to the customer object structure of Oracle Fusion Applications. You must understand how Oracle Fusion Applications represent the structure of the data for a customer hierarchy.

The Oracle Fusion Applications customer hierarchy object structure is hierarchical. At the top level is the customer hierarchy, which must exist before you can import customer hierarchy members. The customer hierarchy and customer hierarchy member contain information about the customer hierarchy and customer hierarchy nodes, such as the hierarchy type, hierarchy code, hierarchy name, and hierarchy version.

Comparing Business Object Data

After you understand the structure of the data, then compare the detailed attribute values of your data with the Oracle Fusion Applications data. Each import object is a collection of attributes organized to assist you when mapping your data to the Oracle Fusion Applications data and to support one-to-many relationships between the structural components that make up the customer hierarchy.

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

Extensible Attributes

If you want to extend the Oracle Fusion Applications import object to import your legacy or source data, then you must use 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 Customer Hierarchy Using File-Based Data Import

For the customer hierarchy business object, you must use the File-Based Data Import feature. You prepare XML or text source data files, such as CSV, in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks required to configure the import objects, to create source file mappings, and to schedule the import activities. You submit file-based import activities for each import object.

An import activity defines the instructions for processing import data, including the source file, import mapping from the source file to the Oracle Fusion Applications object and attribute, and the import schedule.

When importing customer hierarchy information, you first import the customer hierarchy information and then the customer hierarchy members for the customer hierarchy. When importing customer hierarchy members, you must provide the parent reference information that refers to the customer hierarchy of the member.

Verifying Your Imported Data

Oracle Fusion Applications provide File-Based Import activity reports, which can be used to verify imported data. You can view the list of import activities from the Manage Import Activities page. You can verify the status of the import activity by clicking the Status column for your import activity. Alternatively, you can also navigate to the Manage Hierarchies task from Setup and Maintenance to view the customer hierarchy information that you have imported.

Customer Hierarchy Import Objects: How They Work Together

The Customer Hierarchy import object imports customer hierarchy and customer hierarchy members. This topic describes the Customer Hierarchy object and introduces the following:

• Target import object concepts

• Target objects for the Customer Hierarchy import object

• Target import object attributes

• Target import object attribute reference guide files for evaluating and mapping source file data

Customer Hierarchy Target Import Objects Concepts

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

Target Import Objects

The target import objects in the customer hierarchy import object are grouped into information about the customer hierarchy and information about the customer hierarchy members. The CustomerHierarchy is the target import object containing attributes to import information about the customer hierarchy, and the CustomerHierarchyMember is the target import object containing attributes to import information about the customer hierarchy members. You can have multiple hierarchy members associated with a customer hierarchy.

To import a customer hierarchy, you must do the following:

1. Import customers who must be part of the hierarchy.

2. Import the customer hierarchy definition that includes the hierarchy structure and the root node.

3. Import existing customers as customer hierarchy members into the hierarchy.

Target Import Objects Attributes

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

Target Import Objects Attributes Resources

To access the reference guide files for the customer hierarchy target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository 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 Customer Hierarchy File-Based Data Import asset.

Importing Customers

Importing Customers Using File-Based Import: Explained

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

A customer is an entity with whom you have a selling relationship. Oracle Fusion Applications refer to sales account and sales prospects collectively as a Customer. A customer business object allows you to capture all information about a customer, such as the customer profile, customer contact relationships information, and customer contact points.

A sales account is a specific sell-to entity within a given customer. You can create leads and opportunities for sales accounts. An entity with a sales account in Oracle Fusion Applications can be one of the following:

• Sales Prospect: A prospective entity or person who does not have a sell-to address. This entity is used to define leads.

• Customer: A sales account or sales prospects.

• Legal Entity: A legal entity is a party that can enter into legal contracts or a business relationship. It can be sued if it fails to meet contractual obligations.

You can use the Customer import object to import sales accounts or sales prospects of the type organization. You can use the Group Customer import object to import customers of the type group, and the Consumer import object to import customers of the type person.

You must consider the following questions when importing your data:

• Did you identify the records that should be imported as sales prospects, and the records that should be imported as sales accounts?

• How does your legacy or source system represent the customer 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 Customer import object?

• Do you have to customize Oracle Fusion Applications to capture attributes that are critical to the way you do business?

• What import features are available for importing your business object?

• How do I verify my imported data?

Comparing Business Object Structures

Before you can import your customer data from the legacy or source system, you must first analyze the data and see how it corresponds to the customer object structure of Oracle Fusion Applications. You must understand how Oracle Fusion Applications represent the structure of the data for a customer.

The Oracle Fusion Applications Customer import object structure is hierarchical. The root of the hierarchy is the organization profile, which must exist before you can import lower-level components, such as classifications, contacts, and sales account profiles. These child entities can have other entities as their child entities. This hierarchical structure supports one-to-many relationships between the components that make up the customer.

The following figure shows the customer object and its child entities.

The organization profile contains basic information about the customer, such as the customer name and party usage. For each customer, you can assign classifications, contacts, sell to addresses, phone details, and additional names. The contact of the customer, in turn, includes other child entities that capture information about the contact, such as contact job, contact primary phone, contact primary address, and contact e-mail.

Comparing Business Object Data

After you understand the structure of the data, the next step is to compare the detailed attribute values of your data with the Oracle Fusion Applications data. Each import object is a collection of attributes organized to assist you when mapping your data to the Oracle Fusion Applications data and to support one-to-many relationships between the structural components that make up the customer.

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

Extensible Attributes

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

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

The Define File-Based Import Setup and Maintenance task list includes the tasks required to configure the import objects, to create source file mappings, and to schedule the import activities. You submit file-based import activities for each import object. An import activity defines the instructions for processing import data including the source file, import data mapping from the source file to the Oracle Fusion Applications object and attribute, and the import schedule.

When importing customer information, you first import the basic customer profile information, followed by the child entities for the customer. When importing child entities, you must provide the parent reference information for all parent levels for the entity. For example, you first import basic profile details, such as customer name, party type, and party usage. You then import contacts and contact information, such as phone, address, contact points, and fax for the customer. You must provide the PartyOrigSystem and PartyOrigSystemReference of the customer when importing contacts for the customer. PartyOrigSystem is the source system code that identifies the source of the information being imported. PartyOrigSystemReference is unique for each row of data within a single import, and is a combination of PartyOrigSystem and a unique reference. When importing contact information for a customer, you must provide the relationship reference information. This information is required because a contact can have multiple relationships with a customer.

Verifying Your Imported Data

You can view the list of import activities from the Manage Import Activities page. You can verify your imported data by clicking the Status column for your import activity. Alternatively, you can also navigate to the Customer Center work area to view the customer information that you have imported.

Customer Import Objects: How They Work Together

The Customer import object allows you to import customers, their detailed information, and contacts related to the customer. This topic describes the Customer import object. It introduces the following:

• Target import object concepts

• Target objects for the Customer import object

• Target import object attribute

• Target import object attribute reference guide files for evaluating and mapping source file data

Customer Target Import Object Concepts

The Customer import object imports customer information and contacts related to customer. The Customer import object is split into separate target import objects for organizing the individual attributes for the different aspects of the customer and customer contact. Before you import customer information, you must understand how the target objects are related and what attributes are included in each object. This understanding helps you create the appropriate mapping between the source data in your import file and the target attributes.

The target import objects included in the Customer import object are grouped into information about the customer and the customer contact. The organization profile is the target import object containing attributes to import information about the customer. You can have multiple contacts associated with a customer. The Customer import object has multiple target import objects that include attributes to import customer contacts and their related information.

When updating an existing customer with additional information, you must provide the parent reference information for the existing customer. When importing customer contacts or contact information for a customer, you must provide relationship reference information in addition to the parent reference. This information is required because a contact can have multiple relationships with an organization, such as an employee or board member. When importing information about a contact you must refer to the specific relationship that you want to import information for. For example, you might want to import information for John Smith the employee or John Smith the board member. If you do not include the reference information for a customer-contact relationship, then the import process creates a relationship.

To update the information for an existing customer or to create a customer record, you can import customer profile information, addresses, and contact points, such as a phone and fax. The following target import objects are for creating and updating the corresponding customer information: OrganizationProfile, Fax, PrimaryPhone, Url, SalesAccountProfile, Classification, AdditionalName, Relationship, SellToAddress, and AdditionalIdentifier.

To update or to create a customer contact, use the following target import objects: ContactPersonProfile, ContactJob, ContactPrimaryAddress, ContactEmail, ContactPrimaryPhone, ContactMobile, ContactInstantMessenger, and ContactFax. All contact-related entities, such as primary phone or e-mail, include a child entity that captures the contact preference. For example, the Primary Phone Contact Preference entity captures the contact preference of the legal entity for the contact method primary phone.

Target Import Objects Attributes

You must compare the attributes that you want to import with the target object attributes that are available and their valid values. To evaluate your source data and Oracle Fusion Applications attributes for mapping and validation, you use an Oracle Enterprise Repository reference guide, which is available for each target import object. The reference guide file includes attribute descriptions, default values, and validations performed by the import process. Review the validation for each attribute to determine whether there are functional prerequisites or setup tasks that are required.

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

Target Import Objects Attributes Resources

To access the reference guide files for the 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 Customer File-Based Data Import asset.

Importing Employee Resources

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.

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

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.

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.

Importing Geographies

Importing Geographies Using File-Based Import: Explained

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

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

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

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.

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.

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.

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

Target Import Objects Attributes Resources

To access the reference guide files for the geography's target import objects, see the File-Based Data Import assets in Oracle Enterprise Repository 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.

Importing Group Customers

Importing Group Customers Using File-Based Import: Explained

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

A group customer is a party consisting of a collection of persons and organizations. A group, similar to a person or organization, can enter into a business relationship with other parties and can be assigned to opportunities and leads. A group can have members of party type person or organization. You can maintain group customers information in Oracle Fusion Applications CRM to create leads and opportunities for a group, or capture information about a group to know them better. However, maintaining this information may not let you assign all sales and marketing activities to a group.

You must consider the following questions before importing group customer information:

• How does your legacy or source system represent the group customer 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.

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

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.

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

Target Import Objects Attributes Resources

To access the reference guide files for the 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.

Importing Legal Entities

Importing Legal Entities Using File-Based Import: Explained

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

A legal entity is a recognized party with rights and responsibilities that is established by legislation. You create a legal entity for each registered company or other entity recognized in law for which you want to record assets, liabilities, expenses and income, pay transaction taxes, or perform intercompany trading. Within Oracle Fusion Applications CRM, a legal entity is a representation of the legal unit of a customer.

You must consider the following questions before importing legal entity information:

• How does your legacy or source system structure represent the legal entity information compared to how Oracle Fusion Applications represent the same data?

• How do your legacy or source system legal entities relate to business units, divisions, ledgers, balancing segments, consolidation rules, intercompany transactions, and payroll reporting?

• Do you have to configure values in Oracle Fusion Applications to map to your existing data values to the Legal Entity 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

Before you can import your legacy or source system legal entity data, you must first analyze the data and see how it corresponds with the legal entity object structure of Oracle Fusion Applications. You must understand how Oracle Fusion Applications represent the structure of the data for a legal entity.

The legal entity structure of Oracle Fusion Applications is hierarchical. The organization profile is at the root level of the legal entity. The organization profile must exist before you can import lower-level components, such as e-mail, classification, additional name, primary address, and fax. These child entities can have other entities as their child entities. This hierarchical structure supports one-to-many relationships between the components that make up the legal entity.

The following figure shows the legal entity and its child entities.

The organization profile contains basic information about the legal entity, such as the legal entity name and party usage. For each legal entity, you can assign classifications, contacts, phone details, and additional names. The contact of the legal entity, in turn, includes other child entities that capture information about the contact, such as contact job, contact primary phone, contact primary address, and contact e-mail.

Comparing Business Object Data

After you understand the structure of the data, then compare the detailed attribute values of your data with the Oracle Fusion Applications data. Each import object is a collection of attributes organized to help you when mapping your data to the Oracle Fusion Applications data and to support one-to-many relationships between the structural components that make up a legal entity.

A good understanding of the import objects and attribute details is critical to preparing your import data. The attribute details of Oracle Fusion Applications are available for your reference in the Oracle Enterprise Repository. The reference guide files contain descriptions, default values, and validation for each of the Oracle Fusion Applications attributes. The validation information includes the navigation to the task where you can define values in Oracle Fusion 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.

Extensible Attributes

If you have to extend the Oracle Fusion Applications import object to import your legacy or source data, you must use Oracle Fusion Applications CRM 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 Legal Entities Using File-Based Data Import

For the legal entity business object, you must use the File-Based Data Import feature. You prepare XML or text source data files in a form that is suitable for file-based import. The file-based import process reads the data included in your source file, populates the interface tables according to your mapping, and imports the data into the application destination tables. The Define File-Based Data Import Setup and Maintenance task list includes the tasks required to configure the import objects, create source file mappings, and schedule the import activities. You submit file-based import activities for each import object.

An import activity defines the instructions for processing the import data, including the source file, import mapping from the source file to the Oracle Fusion Applications object and attribute, and the import schedule.

When importing legal entity information, you first import the basic legal entity profile information and then the child entities for the legal entity. When importing child entities, you must provide the parent reference information for all parent levels for the entity. You must provide the PartyOrigSystem and PartyOrigSystemReference of the legal entitywhen importing contacts for the legal entity. PartyOrigSystem is the source system code that identifies the source of the information being imported. PartyOrigSystemReference is unique for each row of data within a single import, and is a combination of PartyOrigSystem and a unique reference. For example, you first import basic profile details, such as first name, last name, party type, and party usage. You then import contacts and contact information, such as phone, address, contact points, and fax for the legal entity.

Verifying Your Imported Data

You can view the list of import activities from the Manage Import Activities page. You can verify your imported data by clicking the Status column for your import activity. Alternatively, you can also navigate to the Define Legal Entities task list from the Setup and Maintenance work area to view the legal entities that you have imported.

Legal Entity Import Objects: How They Work Together

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

• Target import object concepts

• Target objects for the Legal Entity import object

• Target import object attributes

• Target import object attribute reference guide files for evaluating and mapping source file data

Legal Entity Target Import Object Concepts

The Legal Entity import object imports legal entity information and its contacts. The Legal Entity import object is split into separate target import objects for organizing the individual attributes for the different aspects of the legal entity and its contact. Before you import data, you must understand how the target objects are related and what attributes are included in each object. This information helps you create the mapping between the source data in your import file and the target attributes in the application.

The target import objects in the Legal Entity import object are grouped into information about the legal entity and the contact. The organization profile is the target import object containing attributes to import information about the legal entity. You can have multiple contacts associated with a legal entity. There are multiple target import objects that include attributes to import contacts and their related information.

When updating an existing legal entity with more information, you must provide the parent reference information for the existing legal entity. When importing contacts or contact information for a legal entity, you must provide relationship reference information in addition to the parent reference. This information is required because a contact can have multiple relationships with the legal entity. When importing information about a contact, you must refer to the specific relationship you want to import information for. For example, you might want to import information about John Smith the employee or John Smith the board member. If you do not include the reference information for a contact relationship, then the import process creates a relationship.

To update the information for an existing legal entity or to create a legal entity, you can import legal entity profile information, addresses, and contact points, such as phone and fax. The following target import objects are for creating and updating the corresponding legal entity information: OrganizationProfile, PrimaryAddress, PrimaryPhone, Url, Fax, Classification, AdditionalName, and ContactPersonProfile.

To update or create a contact, use the following target import objects: ContactPersonProfile, ContactJob, ContactPrimaryAddress, ContactEmail, ContactPrimaryPhone, ContactMobile, ContactInstantMessenger, and ContactFax. All contact-related entities, such as primary phone or e-mail, include a child entity that captures the contact preference. For example, the Primary Phone Contact Preference entity captures the contact preference of the legal entity for the contact method primary phone.

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 files contain descriptions, logic used for 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 File-Based Import Activity task. Both tasks are available in the Setup and Maintenance work area.

Target Import Objects Attributes Resources

To access the reference guide files for the legal entity 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 Legal Entity File-Based Data Import asset.

Importing Resource Teams

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

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

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

Hint: You can use the keyword importing resource teams 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 Resource Teams Using File-Based Data Import

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

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

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

Verifying Your Imported Data

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

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

Target Import Objects Attributes Resources

To access the reference guide files for the 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.

FAQs for Define 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.

Previous

Next

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

Home

Contents

Book List

Contact Us