4File-Based Import

This chapter contains the following:

Overview of File-Based Import

How File-Based Data Import Works

The Define File Import group of tasks relies on integration with different architecture components, such as interface tables and application base tables. This topic provides an overview of these components to help you understand the import process and the different import activity statuses.

The following figure provides an overview of the major application components used when you import data from a file. These components include:

  • Import object

  • Import mapping

  • Import activity

  • File repository

  • Application Composer

  • Interface tables

  • Base tables

You select the import object during setup. The import mapping is used in the import mapping step. The import file you upload is stored in a file repository. The additional attributes that you create in the Application Composer are stored in a separate extensions repository and are available for import and in the import mapping.

File-based data import overview showing how the
different components relate.
Note: If you change the NLS_LANG and the DATE_FORMAT environment variables, you must restart the Oracle Fusion applications.

Import Objects, Import Mapping, and Import Activity

When you create an import activity, the import objects you select are provided by Oracle. You manage these import objects using the Manage File Import Objects task.

Note: Avoid concurrent submission of File Import jobs for the same import object. Concurrent submission of multiple import jobs with same content results in creation of duplicate object records.

When you create an import activity, you must specify a mapping of the fields in your file to the attributes of the import object. You can create the mapping while creating an import activity or separately using the Manage File Import Mappings task. The mapping is stored and managed as a separate object.

File Repository

The text or XML data file that you upload during import is stored in a file repository. If you upload any attachments, they're also stored in the same repository.

Application Composer Extensions

When you create additional attributes for data import using the Application Composer, the extensions are stored in a separate repository and are available for import and export.

Interface Tables

The import activity populates the application interface tables with your data.

Base Tables

The import activity loads your data into the base tables to complete the import.

The Import Activity is a step-by-step guided process to help you create an import activity for a given object. This topic describes the source file options defined in the Import Activity that are used by the import process to locate and parse the source file data.

Source File Data

Enter attribute details pertaining to the source file as described in this table.

Option Description

File Type

Source file must be either Text, ZIP, or XML.

Data Type, Delimiter, and Header Row Included

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

Import Mapping

Displays a list of predefined mappings for the object selected for this import activity. The selected mapping will be used as the basis for mapping your source file in the next Import Activity step.

Source File Location

This table provides the available options when locating your source file for import.

Option Description

Upload From

You can upload the source file from the following locations:

  • Desktop

    If you select Desktop, then a File Name field with an associated Update button is displayed. Click Update and browse to search and select the file you want to upload.

  • WebCenter Content Server

    If you select WebCenter Content Server, then a File Name field with an associated Browse button is displayed. Click and browse to search and select the file you want to upload.

You can import data from a file using file-based data import.

You can import a wide range of application data from text or XML files by navigating to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage File Import Activities

Importing data can either create or update application records. The import options and other details differ by the type of data that you're importing. Before you import data, you must know how the data in your file maps to the attributes in the application and what values are expected.

To help you get started, you can use the example templates provided in Document ID 1596128.1 on My Oracle Support. The templates include columns for the most common application attributes and reference numbers.

Import Data

To import data from a file:

  1. In the Setup and Maintenance work area, navigate to:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

    Tip: You can also navigate to the Manage Import Activities page by selecting the import task in the work areas for objects that support importing data.
  2. Click the Create icon.

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

  4. In the Object field, select the object that you're importing.

  5. Depending on the object that you're importing, the corresponding file type is selected by default in the File Type drop-down list. For example, Deal Registration object supports only ZIP file.

  6. In the Source File region, select one of the Upload From options.

    Note: If you're importing a file into one of the services, then you must upload files from your desktop. The maximum number of records in each CSV file (either single CSV or ZIP file) should not exceed the maximum limit of 100,000 records.
    • Desktop

      After you select this option, you must browse for the file. You must select an import file in CSV format.

  7. If your data file includes a header row, then select the Header Row Included option. Although you can upload files without header rows, it becomes difficult to complete the mapping between the data in your file and the application. If the values in the CSV file contain new line character, enclose them within quotation marks.

  8. If your file doesn't use a comma to separate values, then select the correct delimiter in the Data Type field.

  9. You must create a mapping between the data in the import file and the target attributes in the application. If you had previously imported a file with the same format as the file that you're importing now, then select an existing mapping from the Import Mapping list. By default, the application saves the import mapping under the import activity name added with the activation date and time. If you're importing a file in this format for the first time, then you must create the mapping in the next step.

  10. If you're importing one of the following objects, then you can import attachments by selecting the Browse option in the Attachments region and selecting a .zip or .jar file of the attachments. You must include a column with the names of individual attachments in your import file as described in the Importing Attachments Using File-Based Data Import: Procedure topic. Your attachment file name should not contain special characters such as the Pound symbol or the pipe symbol (|). Don't submit File-Based Data Import jobs for the same import object because they create duplicate object records.

    The following import objects support importing a single attachment for each record:

    • Assets

    • Opportunities

    • Partners

    The following import objects support multiple attachments for each record:

    • Leads

    • Activities

  11. In the Import Options region, some of the options in the following table might be available depending on the object that you're importing.

    Option Description

    Import Mode

    For importing leads and employee resources only, you can specify whether you want to create and update records or update them only.

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

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

    Allowable Error Count

    The Allowable Error Count threshold determines whether to automatically cancel an import if the number of consecutive rows with validation errors exceeds the user-defined threshold value. The default value is 2000. You can change this value when configuring your import. If the number of consecutive rows in your source file with a validation error exceeds the Allowable Error Count value, the import is canceled. If the Allowable Error Count isn't reached, the data is imported. Errors encountered aren't counted toward the Allowable Error Count.

    Validation errors include:

    • Missing required values

    • Values that exceed the attribute length

    • Invalid identifiers and lookup codes

    Duplicates found using matching configurations for Customer Data Management objects don't contribute to the error count.

    Notification email

    The email of the individual who receives import processing notifications. Currently this option is supported only for Opportunity, Lead, and custom objects.

    Account Data Management Duplicates

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

    Decimal Separator

    The decimal separator used in your import file.

    Date Format

    The format of the date fields in your file.

    Time Stamp Format

    The format of time fields in your file.

    Execute Groovy Scripts and Workflows

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

    File Encoding

    The overall encoding for your file.

  12. Click Next.

    The Create Import Activity: Map Fields page displays the attributes in your file with some sample data. If you're reusing an import mapping, both the Source and Target columns are already populated. The Source columns represent your file. If you're creating a new mapping, the Target Object and Attribute columns are blank.

    Note: Oracle recommends that you use the Object Number (such as Opportunity Number) or Code (such as Claim Code) fields when available instead of Object ID (such as Opportunity ID) fields when importing objects.
  13. For each column in your file that you want to import, select the target object and one of its attributes. The target object and attribute name values are populated based on the display label values set in the Application Composer.

    Every import object comprises its own set of attributes.

    If you don't want to import a column in your file, select the Ignore check box.

    Note: Perform these steps to view the Language Independent Code of the target attributes:
    1. In the Setup and Maintenance work area, navigate to:

      • Offering: Sales

      • Functional Area: Sales Foundation

      • Task: Manage Administrator Profile Values

    2. In the Administrator Profile Values page, search for the profile option ZCA_IMPORT_ENABLE_LIC_COLUMN.

    3. Set the Profile Value to TRUE.

    4. In the Map Fields page, select Language Independent Code from the View menu.

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

    If you're importing data using the import templates provided on My Oracle Support, every column header in your template includes the names of both the target object and the target attribute to simplify the mapping process.

  15. Click Next.

    Tip: To schedule the import process for a specific date, you must select the Specific Date from the Schedule list and enter a start date.
  16. Click Next.

  17. Click Activate.

  18. You return to the Manage Import Activities page to view the status of your import. An import activity with a status of Completed or Completed with Errors indicates that the import activity completed.

  19. During the patching process, any import jobs running might fail with error. You must resubmit these jobs after the patching is complete.

  20. Click the status link to view data about the success of the import, including logs and error files that are linked in the Files Processed region. In the View Import Status page, click the file name link to download the CSV file associated with the import activity.

View and Interpret the Import Notification E-mail

After the data is imported, an e-mail is generated with the detailed results of the import and links to any failed operations for troubleshooting purposes. If you had specified an e-mail in the Notification e-mail field, an e-mail is sent to that address. The e-mail includes the following:

  • Name of the import job and the import activity identifier

  • The URL for the environment

  • The object name

  • Status of the import

  • The Name of the import (source) file, and the type of file that was used

  • Start and end times for the import (date and time)

  • Elapsed time

  • Record Counts: Read, Successful, Errors, Warnings

  • Submitted by

How You Import Data with Special Characters

You need to format the data, if your import file includes special characters. Follow the methods described in this topic to ensure that input data is properly parsed and imported by CX Sales and B2B Service.

Build the CSV File

To build your CSV file for importing data:

  1. In the Setup and Maintenance work area, navigate to:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. In the Manage File Import Mappings page, select the object, select the Seeded option and click Search.

  3. In the Edit Import Mappings page, click Download Template to save the CSV template file to your desktop.

  4. You can edit the file to include only those fields that you import.

Enter Data in the CSV File

After creating the CSV file, you must enter the data to be imported. Some of the special characters are quotation marks(") and a comma(,). You must prefix the special characters with quotation marks(").This list shows the different formats in which the input data can be entered for the Lead object CSV file and how it's interpreted due to the presence of special characters. LeadName and LeadNumber are the header fields for the file.

This table lists five Lead records of a CSV file, each with the LeadName first, followed by the LeadNumber (120, 121, and so on).

LeadName LeadNumber

Mark Twain lead

120

"Twain "secondary" lead"

121

Twain, Mark

122

Twain, Mark "Spring 2015" lead

123

"Twain "Fall 2014" lead

124

You can use escape characters for the Lead Name source data records, as shown in this table.

Row Number Source Data for LeadName How LeadName is Written to Database if no Escape Characters are Added Data with Escape Characters to Preserve Original Data How LeadName is Written to Database When Escape Characters are Included Comment Regarding Escape Characters

1

Mark Twain lead

Mark Twain lead

Not applicable

Not applicable

No escape characters are needed as the source data contains no special characters.

2

"Twain "secondary" lead"

Twain secondary" lead"

"""Twain ""secondary"" lead""",121

"Twain "secondary" lead"

The two series of three quotation mark each:

  • The quotation marks surrounding the field which is required to precede the quotation marks in the source data

  • The quotation marks in the source data

3

Twain, Mark

Twain

"Twain, Mark",122

Twain, Mark

Double quotation mark is required to surround the field entry, as a comma is in the source data. No additional escape character is required to precede the comma.

4

Twain, Mark "Spring 2015" lead

Twain

"Twain, Mark ""Spring 2015"" lead",123

Twain, Mark "Spring 2015" lead

A double quotation mark is required to surround the field entry, as at least one special character is present in the source data. Every double quotation mark in the source data requires a double quotation mark escape character. No additional escape character is required to precede the comma.

5

"Twain "Fall 2014" lead

Twain Fall 2014" lead

"""Twain ""Fall 2014"" lead",124

"Twain "Fall 2014" lead

Although the missing end quotation mark in the source data is likely a typo, the source data must be written as it appears. Enter three double quotation marks at the beginning, but only a single (surrounding) double quotation mark at the end.

  • If the source data contains at least one special character, the field of source data must be entered in double quotation marks in the CSV file.

  • If the data for a field contains separator such as a comma (,), you must enclose the content within two double quotation marks.

  • If the first field has a special character at the beginning but not any matching special character at the end, the content of the second field will also be considered as part of the first field, and the second field is blank. You must provide a matching escape character.

  • If you don't precede the special characters by an escape character, the import process may write incorrect data for a field, or incorrectly write data to the subsequent fields.

Note: Microsoft Excel and other spreadsheet programs may automatically override the special characters.

Use Predefined Templates to Import Data

You can use predefined templates to import data using file-based data import. To import data using the predefined templates, you must:

  • Download the import templates

  • Understand the import templates

  • Adapt the import templates to your needs

Download Import Templates

CX Sales and B2B Service provides templates to help you import data using File-Based Data Import tool. The templates are spreadsheets that include the commonly used fields, in addition to the required fields. Every import object could have one or more templates associated with itself. This table lists the objects and the templates for the object. Predefined mappings are highlighted in bold.

Import Object Template Description

Account

Data Cloud Account Import - Advanced

Predefined mapping to import files generated from Data Cloud and Insight service into CX Sales and B2B Service for account enrichment.

Account

Account Create and Update Predefined Mapping

This mapping lets the user create or update accounts with the most basic information.

Account

Quick Create Account Predefined Mapping

Predefined mapping to create Accounts with basic information. This mapping can't be used to update any attribute other than those mapped to the Account object.

Account

Account Address Create and Update Predefined Mapping

This mapping lets the user create or update multiple addresses for existing accounts.

Account

Account Relationship Create and Update Predefined Mapping

This mapping lets users associate an account with one or multiple contacts.

Activity

Activity Predefined Mapping - Import Task

Template to import activity predefined mapping (Import Task)

Activity

Activity Predefined Mapping - Import Appointment

Template to import activity predefined mapping (Import Appointment)

Contact

Data Cloud Contact Import - Advanced

Predefined mapping to import files generated from Data Cloud and Insight service into CX Sales and B2B Service for contact enrichment.

Contact

Contact Create and Update Predefined Mapping

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

Contact

Quick Create Contact Predefined Mapping

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

Contract

Hierarchical Predefined Mapping-Contract Header, Parties and Contacts

Template to map hierarchical objects

Contract

Contract Predefined Mapping-Contract Header, Primary Party and Contacts

Template to map contract objects

Customer Sales Team

Sales Account Resource Team Seeded Mapping

Template to import sales account resource team

Customer hierarchy

Customer Hierarchy Create Predefined Mapping

This template is used to create a customer hierarchy. Customers who are part of this hierarchy should be created first using the "Create or update account" template.

Customer hierarchy member

Customer Hierarchy Member Create Predefined Mapping

This template can be used to add customers (nodes) to an existing customer hierarchy (tree).

Employee Resource

Employee Resource Seeded Mapping - Comprehensive

Template to import Employee Resource with role, resource organization and hierarchy information

Lead

Lead Predefined Mapping Import Leads

Template to import Leads with contact and company information.

Lead

Lead Predefined Mapping - Import Leads with Qualification information

Template to import Leads with contact and qualification information.

Note

Note Predefined Mapping - Default required Set with identifiers

Template to import Note -Default required Set with identifiers

Note

Note Predefined Mapping - Default required Set with original system reference

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

Opportunity

Opportunity Predefined Mapping - Opportunity Resource

Template to import Opportunity Resource

Opportunity

Opportunity Predefined Mapping - All related objects

Template to import Opportunity with all related objects.

Opportunity

Opportunity Predefined Mapping - Opportunity Resource Revenue

Template to import Opportunity Resource and Revenue.

Partner

Oracle Fusion Hierarchical File Import Map for Partner - Includes Child objects

Template to import Partners including child objects.

Partner

Oracle Fusion Hierarchical File Import Map for Partner

Template to hierarchically import partners with minimum attributes

Partner

Oracle Fusion File Import Map for Partner Update

Template to import updates to partners

Partner

Oracle Fusion File Import Map for Partner

Template to import partners with minimum attributes

Partner Contact

Oracle Fusion File Import Map for Partner Contacts

Template to import partner contacts

Partner Program Enrollments

Oracle Fusion File Import Map for Enrollment Update

Template to import updates to enrollment

Partner Program Enrollments

Oracle Fusion File Import Map for Enrollment

Template to import enrollments with minimum attributes

Product Group

Product Group Predefined Mapping - Product Group Header and Child Entities

Template to import product groups, items related to product groups and product group relationships used to define a hierarchy.

Quota

Quota Predefined Mapping - Territory and Resource Quotas

Template to import Territory and Resource Quotas

Sales Promotion

Sales Promotion Predefined Mapping - Header and Coupons

Template to import promotions and coupons associated with promotions.

Territory

Territory Import Seeded Map

Template to import territory

Territory Geographies

Territory Geographies Import Mapping

Template to migration import territory geographies

Territory Geographies

Territory Geographies Incremental Import Mapping

Template to import territory geographies incrementally

To download an import template:

  1. In the Setup and Maintenance work area, navigate to:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. In the Manage File Import Mappings page, select the object for which you need the template (such as Account) from the Object drop-down list.

  3. Select the Seeded option.

  4. Click Search.

  5. Click the template you want to download from the search results. The Edit Import Mapping page is displayed.

  6. In the Edit Import Mapping page, click Download Template.

  7. Save the .csv file to a location on your desktop.

Understand the Import Templates

You must understand the columns in the import templates to populate the templates with the correct data. To update existing records, your source file must include the attributes that enable the import process to identify these records. These values are source system and source system reference value combination, internal ID, or public unique identifiers, such as business keys or external IDs. When the source of your data isn't an external system and you don't intend to regularly update the data, you don't need the source system information.

Note: Oracle recommends that you include the source system information, as requirements change over time.

Copy and Modify a Predefined Mapping

The template file includes a header row with columns that map to the attributes for the objects. You can use the mapping that's used to download the template and also to map columns to attributes during import. The columns are arranged in the same order as the mapping in CX Sales and B2B Service. You can add additional attributes to the file by adding them after the last column. In case you add additional attributes, you must copy and modify the predefined mapping to create a user-defined mapping that includes these additional attributes. To copy and modify a predefined mapping:

  1. In the Setup and Maintenance work area, navigate to:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. In the Manage File Import Mappings page, select the object for which you need the template (such as Account) from the Object drop-down list.

  3. Select the Seeded option. Click Search.

  4. Click the template you want to copy or modify from the search results. The Edit Import Mapping page is displayed.

  5. In the Edit Import Mapping page, click Copy Mapping.

  6. The target object attributes can be edited. You can also add attributes to the object by clicking the Create icon.

  7. Click Save to save the modified template file.

Note: Perform these steps to view the Language Independent Code of the target attributes:
  1. In the Setup and Maintenance work area, navigate to:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  2. In the Administrator Profile Values page, search for the profile option ZCA_IMPORT_ENABLE_LIC_COLUMN.

  3. Set the Profile Value to TRUE.

  4. In the Edit Import Mapping page, select Language Independent Code from the View menu.

Adapt the Import Templates

You may want to add additional attributes to your files to import additional information for your import data. You can review all available attributes for your import object in a reference file located in File-Based Data Import for CX Sales and B2B Service guide available on the Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). Review the reference file to explore other attributes that are available for import and the possible prerequisite steps for those attributes.

The reference file includes the following information:

  • All attributes available for your import object.

  • The attribute descriptions, including the user interface display name for the attribute if the attribute is displayed on the user interface.

  • The data type, length, and validation logic, including the task or work area where you can view or define valid values before importing data.

  • The logic for default values, if values aren't provided in your source file.

Select the Import Template

To select the template that you downloaded during the import process:

  1. In the Setup and Maintenance work area, navigate to:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

  2. In the Manage Import Activities page, click the Create icon.

  3. In the Create Import Activity page, provide the import name and object to import. Provide the file type, select Header row included and Seeded options.

  4. From the Import Mapping drop-down list, select one of the predefined templates

  5. Click Next to view the mapping and schedule the activation of import process.

Import Attachments Using File-Based Data Import

You can include attachments when you use the Manage File Import Activities task.

Import Attachments

To import attachments using file-based data import:

  1. Add one or more of the columns listed in this table to the source file you're importing.

    The ATTACHMENT_FILE_NAME header is the only required header. All other headers are optional. The Manage File Import Activities task reserves these header names for their described usage. You must not use them for any other purpose.

    This table describes each of the supported column headers.

    Column Header Description

    ATTACHMENT_FILE_NAME

    The .zip file selected when defining the import activity must contain a file with the specified ATTACHMENT_FILE_NAME value. Your attachment file name should not contain special characters such as the Pound symbol or the pipe symbol (|).

    ATTACHMENT_FILE_DESC

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

    ATTACHMENT_FILE_TITLE

    Enter the file title. This isn't a required field. If you don't specify a file title, then the Manage File Import Activities task uses the file name as the title. For example, if the file name is abc.txt, and the ATTACHMENT_FILE_TITLE column value isn't explicitly passed in the CSV, then the file title defaults to abc.

    ATTACHMENT_CATEGORY_NAME

    Specify the attachment category. An attachment category is used to classify and secure attachments. You must define every attachment UI with at least one category so that users can add attachments. For example, you can categorize attachments for an expense report as a receipt, scanned invoice image, and so on.

  2. In every row of the source file, enter the name of the attachment file that the Manage File Import Activities task must attach to the record.

    This table lists some attachment files for Leads. For example, you enter file_1.doc as the attachment file for Lead 1.

    LeadName StatusCD Score ATTACHMENT _FILE _NAME

    Lead 1

    QUALIFIED

    7

    file_1.doc

    Lead 2

    QUALIFIED

    8

    file_2.doc

    Lead 3

    QUALIFIED

    3

    file_3.doc

    Lead 4

    QUALIFIED

    7

    file_4.doc

  3. To specify the same attachment file for more than one record, enter the same file name for each record in the ATTACHMENT _FILE _NAME column. For example, you can specify file_1.doc for Lead 1 and for Lead 2.

    Note:
    • You can specify multiple attachments for any type of business object or custom object.

    • If you specify more than one attachment for the same record, and if you add any of the optional attachment columns, then you must repeat all the columns in the same order for each attachment file.

  4. Create a .zip file that includes the files that you must attach.

    For example, create a file named myfiles.zip that includes these files:

    • file_1.doc

    • file_2.doc

    • file_3.doc

    • file_4.doc

    You can also use a JAR file. You can organize these files in folders and subdirectories.

  5. Sign in to the application.

  6. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

  7. In the Search Results list, click the link for the task..

  8. In the Manage Import Activities page, click the Create icon.

  9. In the Create Import Activity: Enter Import Options page, select an object from the Object drop-down list that supports attachments.

  10. In the Attachments section, click Browse, and then locate your .zip file.

    Note:
    • You can upload only one .zip file.

    • You can't add more attachments after you upload the .zip file.

  11. Enter the data in the remaining fields and activate the file-based data import activity.

    The Manage File Import Activities task recognizes the reserved column header names, so you don't have to map them in the Create Import Activity: Map Fields page.

Constraints for Business Objects

You can import attachments only for these business objects:

  • Account

  • Activity

  • Contact

  • Contract

  • Campaign

  • Household

  • Lead

  • Opportunity

  • Partner

  • Notes

  • Sales custom object

  • Common custom object

You can't delete the file attachments from a record using file-based data import activities.

You can use the import options available in CX Sales and B2B Service to create import activities.

Source File Data Transformation

You use the options in this table to identify the formatting of source file data so that the data can be correctly interpreted and transformed by the import process.

Option Description

Decimal Separator

The format of the fractional portion of numeric values in columns mapped to attributes with a decimal attribute type.

Date Format

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

Time Stamp Format

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

File Encoding

The overall encoding of the characters within the file.

Interface to Target Import Options

Depending on the object you're importing and the application modules you implemented, you need to select some options. All the options are provided in this table.

Option Description

Import Mode

To import leads and employee resources, you have the option of specifying if you want to create and update records or only update records. If you select update, then any new records will be ignored by the import process. For all other import objects, both create and update operations are available.

Allowable Error Count

The Allowable Error Count threshold determines if the import operations need to be automatically canceled, if the number of consecutive rows with validation errors exceeds the user defined threshold value. The default value for Allowable Error Count is 2000 but you can change this value when configuring your import. During the "Preparing Data for Import" step, if the number of consecutive rows in your input file with a validation error exceeds the Allowable Error Count value, then the import will be canceled. If the Allowable Error Count isn't reached in this step, then the import will proceed. Errors encountered during the "Importing Data" step aren't counted as part of the Allowable Error Count.

Validation errors include:

  • Missing required values

  • Values that exceed the attribute length

  • Invalid identifiers and lookup codes

Duplicates found using matching configurations for Customer Data Management objects don't contribute to the error count.

Notification E-Mail

The e-mail of the intended recipient of import processing notifications. Currently this option is supported only for Opportunity, Lead, and user-defined objects.

Customer Data Management Duplicates

You can select the options in the Customer Data Management LOV for handling duplicates when you're importing accounts and legal entities either alone or as part of another object.

Note: You can use the Customer Data Management Duplicates LOV to retrieve duplicates only if you have licensed the data quality functionality. Once licensed, you must rebuild the keys for your matching configuration using the Manage Enterprise Data Quality Matching Configurations task. For more information, see the Implementing Customer Data Management for CX Sales and B2B Service guide.

The duplicates are determined using the following matching configurations:

  • Address Duplicate Identification

  • Contact Duplicate Identification

  • Account Duplicate Identification

Using this option, which is available only if you licensed the data quality functionality, you can select different options for handling duplicates when you're importing accounts and legal entities either alone or as part of another object.

The duplicates are determined using these matching configurations:

  • Batch Location Basic Duplicate Identification

  • Batch Person Basic Duplicate Identification

  • Batch Organization Basic Duplicate Identification

You can select from one of the following:

  • don't Import Duplicate Records

    If the main object of the Import Activity is an account or a legal entity object, then the rows that are matched to existing records aren't imported. These duplicates records are reported in the Exception and Error reports.

    If the Customer Data Management objects are components of another object and one or more matches are found, then the existing duplicate records are evaluated to determine the most recent record. The most recent record will be associated with the main object being imported.

  • Import Duplicate Records

    The Customer Data Management objects will be imported even if matched records exist.

  • Import Duplicate Records and Create Resolution Request

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

Duplicate Look Back Days

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

Execute Groovy Scripts and Workflows

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

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.

  • Mapping the Fields

  • Saving the Import Mapping

  • Constant Values

Map the Fields

The Map Fields section comprises source file columns and target attribute columns. The source column header value is derived from one of the following:

  • Predefined mapping, if one is selected

  • The source file, if the Header Row Included option is selected in the first step of the import activity definition. This is for Text file type only.

  • Generic values of Column A, Column B, and so on, if the Header Row Included option isn't selected. This is for Text file type only.

  • XML tagging structure. This is for XML file type only.

The source columns are explained in this table.

Source Column Description

Column Header

Represents the column header for Text file types and the tagging structure for XML file types.

Example Value

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

Ignore

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

The target columns are explained in this table.

Target Column Description

Object

The group of import objects that represent the components of the business object being imported.

Attribute

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

Save the Import Mapping

The mapping between source file information and target attributes is saved as a reusable mapping when the import activity is saved, using the import activity name and date to derive a mapping name. If you have selected a predefined mapping, then the modifications to an unlocked mapping in the Import Activity updates and saves the import activity to the predefined mapping. If the predefined mapping is locked, then a modified mapping is saved as a new mapping. To specify a mapping name for new mappings, select the Save As option from the Map Fields Actions menu.

Constant Values

Constant values provide a way to specify a value for a target attribute that all imported objects inherit. When you configure a constant value, the value set for a target attribute is at the record level. For example, if a source file doesn't contain a column for business unit and all of the objects in the file belong to the same business unit, then enter a constant value for the object and business unit attribute. Each imported record has the specified attribute set to the constant value. The Constant value takes precedence over any values mapped or ignored in the Map Fields section. This value applies to all import file types.

You need to know the different import activity statuses when you import data from a file using the Manage File Import Activities task.

The import activity statuses are listed and described in this table.

Status Description

Queued for import

The import request is queued for processing.

Preparing data for import

The data is being staged to be imported.

Importing data

The data is being validated and imported.

Importing attachments

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

Completing import activity

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

Completed

All records were processed and loaded into the application tables.

Completed with errors

The import activity found errors in the data file that you must correct. You can view details about the errors by clicking the status link.

Completed with warnings

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

Unsuccessful

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

You can monitor all file import activities that are currently scheduled to run, have completed successfully, or failed with errors. For every import activity, you can view the details pertaining to each underlying process and make the necessary updates for any failed records that you want to import again. You can also filter the import activities that are in different states.

You can view the list of import activities from the Manage Import Activities page. You can filter the import activities based on the status of the activity, file type, name of the activity, activity identifier, object name, or name of the import mapping used. To filter the import activities:

  1. Click the Query By Example icon This displays the text boxes on each column header.

  2. Enter the filter criteria in the text boxes to filter the records. For example, you may want to filter all import activities that are in the status Completed.

  3. Select the import activity that you want to monitor by clicking the link in the corresponding Status column. The View Import Status page is displayed, that shows the status of the most recently executed instance of the import activity definition. The View Import Status page contains these sections:

    • Files Processed (Import Processes in the case of multiple CSV files)

    • Import Activity Progress

    • Process Log

Files Processed

The Files Processed section displays a row for each source file that's processed, for single CSV files. The import processing details for single CSV files are summarized and displayed for each source file. The details of the import processing are provided in this table.

File Processing Summary Information Description

Records Read From File

The number of records read from the source file.

Records Uploaded with Format Errors

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

Records Failed with Errors

The number of records that failed with errors when importing data from the interface tables to the destination application tables. View the error details in the Exception and Error files attached to the process.

Records Uploaded Successfully

The number of import object records that were imported to the application destination tables. If the import object is made up of multiple components, every component is counted as successfully loaded. Consequently the Successfully Loaded count may be larger than the Records Read From File count. The successfully loaded record count includes the records with warnings. View the successful record details in the Log file attached to the process.

Records Uploaded With Warnings

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

Attachments

After an Import Activity process has completed, processing reports are included in the Attachments column. This column displays the log file in case of successful import, and error and exception file in case of failure. The Log file includes the records that were successfully imported and the unique destination application table identifiers for the objects. The Exception file includes a row for each record that failed. All the errors for that row are concatenated and displayed in the Error Message column of the file. The Error file includes all the errors for each record that failed validation.

If the logs aren't generated for an import activity, you can click the Generate Log link to generate the import log files. After the request is submitted, you get a confirmation message. The Generate Log link is displayed in the Attachments column.

Every file contains these items:

  • Log files contain records that were successfully imported and the unique destination application table identifiers for the objects.

  • Exception files include a row for each record that failed. All the errors for that row are concatenated and displayed in the Error Message column of the file.

  • Error files include all the errors for each record that failed validation.

Submitted By

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

For multiple CSV files, the Import Processes section displays a row for each source file that's processed. The details of the import processing are mentioned in this table.

File Processing Summary Information Description

Records Read From File

The number of records read from the source file.

Records Uploaded with Format Errors

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

Records Failed with Errors

The number of records that failed with errors when importing data from the interface tables to the destination application tables. View the error details in the Exception and Error files attached to the process.

Records Uploaded Successfully

The number of import object records that were imported to the application destination tables. If the import object is made up of multiple components, every component is counted as successfully loaded. Consequently the Successfully Loaded count may be larger than the Records Read From File count. The successfully loaded record count includes the records with warnings. View the successful record details in the Log file attached to the process.

Rejected Data File

The data files that were rejected due to format errors.

Error File

After an Import Activity process has completed, error files are included in the Error File column. This column displays error and exception files in case of failure, and is blank in case of successful import. The Exception file includes a row for each record that failed. All the errors for that row are concatenated and displayed in the Error Message column of the file. The Error file includes all the errors for each record that failed validation.

If the logs aren't generated for an import activity, you can click the Generate Log link to generate the import log files. After the request is submitted, you get a confirmation message. The Generate Log link is displayed in the Error File column.

Every file contains these items:

  • Exception files include a row for each record that failed. All the errors for that row are concatenated and displayed in the Error Message column of the file.

  • Error files include all the errors for each record that failed validation.

Records Uploaded With Warnings

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

Submitted By

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

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

Import Activity Progress

From the Import Activity Progress section, you can view details pertaining to each process involved in importing the objects in the source file. A listing of brief messages provides information about the processing steps within each underlying process. The steps involved in the import activity are summarized in this table.

Step Name Description

Import activity queued

The import activity that's to be processed is being queued.

Preparing data for import

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

Importing data

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

Importing attachments

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

Completing import activity

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

Process Log

The Process Log section displays the log messages that are generated during the processing of an import activity. You can filter the log messages based on the message types Information, Error and Debug. You can also export the log information to a spread sheet.

Import Consumers Using File-Based Import

Importing Consumers: Explained

You can import consumer data from an external data source into CX Sales and B2B Service using the File-Based Data Import feature.

A consumer is a person who intends to purchase goods and services. A person with a selling relationship is referred to as a consumer. Using the Consumer import object, you can import all information about a consumer, such as the consumer profile, consumer address information, consumer contact point information, and consumer contact preference information.

Note: You can use the Consumer import object only if you're using an earlier release of CX Sales and B2B Service. All capabilities of the Consumer object are now included in the Contact object. If you're upgrading from a prior release, then Oracle recommends that you use the Contact object to update your consumer information using File-Based Data Import.

Consider the following questions when importing your data:

  • How does your legacy or source system store and represent the consumer information compared to CX Sales and B2B Service?

  • Do you have to configure values in CX Sales and B2B Service to map your existing data to the Consumer import object?

  • Do you have to extend CX Sales and B2B Service to add attributes?

  • What import features are available to import your business object?

  • How do I verify my imported data?

How Business Objects are Structured

You must understand how your consumer data corresponds with the data in CX Sales and B2B Service to map your legacy data to the data in CX Sales and B2B Service.

The Consumer object 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. You use this structure to support one-to-many relationships between the objects that make up the consumer.

This image shows the consumer object and its child objects.

Consumer import object structure

The consumer profile contains basic information about the consumer, such as the first name, last name, and party usage. For every consumer, you can assign:

  • Sell-to addresses

  • Phone details

  • Sales account profiles

Note: All contact objects, such as primary phone or e-mail, include a child object that has the contact preference. For example, the Primary Phone Contact Preference object has the contact preference of the consumer for the contact method primary phone.

How Business Object Attributes are Structured

Every import object is a collection of attributes that help to map your data to the Oracle Applications Cloud data and to support one-to-many relationships between the structural components of a consumer.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for CX Sales and B2B Service) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Consumer Import Objects Work Together.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import Consumers Using File-Based Data Import

You must first prepare a source data file to import consumers. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You submit file import activities for each import object. When you're creating a new consumer, you use the Consumer object to import your data. You must have the Customer Relationship Management Application Administrator or Marketing Operations Manager job role to access and submit the import activities for consumers.

When importing consumer information, you import:

  1. the basic consumer profile information

  2. the child entities for the consumer

When importing child objects, you must provide the parent reference information for all parent levels of the object. For example, you:

  1. import basic consumer details, such as customer name, party type, and party usage

  2. import contacts and contact information, such as phone, address, contact points, and fax for the consumer

  3. 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. PartyOrigSystemReference is unique for each row of data within an import job, and is a combination of PartyOrigSystem and a unique reference. When importing contact information for a consumer, you must provide the relationship reference information. This information is required, as contacts can have multiple relationships with consumers.

How You Verify Your Imported Data

You can use the File Import activity reports to verify imported data. Alternatively, you can also navigate to the Customer Center work area to view the consumer information that you have imported.

How Consumer Import Objects Work Together

You use the Consumer import object to import consumers and objects related to the consumer. This topic describes the consumer import object and introduces:

  • Target objects

  • Target import object attributes

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

Note: You can use the Consumer import object only if you're using an earlier release of CX Sales and B2B Service. All capabilities of the Consumer object are now included in the Contact object. If you're upgrading from a prior release, then Oracle recommends that you use the Contact object to update your consumer information using File-Based Data Import.

Overview of Consumer Target Import Objects

Use the Consumer import object to import consumers and objects related to consumers. The Consumer import object 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 Cloud Applications, you must know how the target objects are related and what attributes are included in each target object.

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

To update the information for an existing consumer or to create a consumer record, you can import consumer profile information, addresses, and contact points, such as phone and fax number. Use these target import objects to create and update the corresponding consumer information:

  • PersonProfile

  • PrimaryPhone

  • Fax

  • Mobile

  • Classification

  • AdditionalIdentifier

  • AdditionalName

  • e-mail

  • SellToAddress

  • SalesAccountProfile

Target Import Object Attributes

Compare attributes that you want to import with the available target object attributes and their valid values. Use a reference file to evaluate your source data and attributes for mapping and validation. See the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. A reference guide file includes:

  • Attribute descriptions

  • Default values

  • Validations for the attributes

Review the validation for each attribute to know if you need to do any setup tasks.

Define and Manage Import Mappings

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. You can predefine and manage import mappings. Do one of the following:

  1. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when you define the import activity. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note: If any of your source attributes doesn't have a corresponding target object attribute, then you can extend the Consumer object. Review the Application Composer Extensibility features for the consumer object for more information.

Reference Files for Consumer Target Import Objects

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Here is a list of reference files and their target import objects.

Target Import Object Description Reference Guide File Names

PersonProfile

Includes detailed person information such as person name, relationship type, gender, and marital status.

HZ_IMP_PARTIES_T_Reference

SellToAddress

Includes consumer addresses and party sites information. If party site usage of an address isn't defined, then the import process sets it to Sell-To. In case there are multiple addresses without party site usage information, then the import process designates one of the addresses as the Sell-To address.

HZ_IMP_PARTYSITES_T_ Reference

PrimaryPhone

Indicates the primary phone number of the consumer. If the consumer has multiple phone numbers, one of the phone numbers is designated as the primary phone number.

HZ_IMP_CONTACTPTS_T_ Reference

Mobile

Indicates the mobile phone number of the consumer.

HZ_IMP_CONTACTPTS_T_ Reference

Fax

Indicates the fax number of the consumer.

HZ_IMP_CONTACTPTS_T_ Reference

Email

Indicates the e-mail of the consumer.

HZ_IMP_CONTACTPTS_T_ Reference

InstantMessenger

Indicates the instant messenger or social networking information of a consumer.

HZ_IMP_CONTACTPTS_T_ Reference

SalesAccountProfile

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

ZCA_IMP_SALES_ACCOUNTS_ Reference

AdditionalName

Indicates alternative name of a consumer.

HZ_IMP_ADDTNLPARTYNAMES_T_ Reference

Classification

Includes classification information for a consumer. Classification lets you categorize entities such as parties, projects, tasks, and orders as hierarchies.

HZ_IMP_CLASSIFICS_T_ Reference

AdditionalIdentifier

Includes detailed information about an additional identifier for a consumer.

HZ_IMP_ADDTNLPARTYIDS_T_ Reference

Relationship

Includes information about a relationship between the consumer and another entity, such as an organization or a person.

HZ_IMP_RELSHIPS_T_ Reference

PrimaryPhoneContactPreference

Indicates the consumer's preference about being contacted through phone.

HZ_IMP_CONTACTPREFS_ Reference

MobileContactPreference

Indicates the consumer's preference about being contacted through mobile phone.

HZ_IMP_CONTACTPREFS_ Reference

FaxContactPreference

Indicates the consumer's preference about being contacted through fax.

HZ_IMP_CONTACTPREFS_ Reference

EmailContactPreference

Indicates the consumer's preference about being contacted through mobile phone.

HZ_IMP_CONTACTPREFS_ Reference

Import Contacts Using File-Based Import

Importing Contacts: Explained

This topic explains how to prepare and import contact data from an external data source into CX Sales and B2B Service using the File-Based Data Import feature. A contact is an individual who's a customer or a prospect, or a contact for an existing customer or consumer, or a contact that doesn't yet have an established business association with a customer or consumer. Thus, a contact could be an employee of a customer organization, a person you may have met who could help with your business, or a prospective or current individual customer. The contact object contains information that identifies the contact and offers the contact points of the contact. Contact points can be geographical addresses, phone numbers, e-mail IDs, URLs, messenger IDs, and so on. The contact object also contains contact preference information for the contact. You must create or import contacts before you can associate them with account objects.

Consider the following questions when importing your data:

  • How does your legacy or source system store and represent the account information when compared to CX Sales and B2B Service?

  • Do you have to configure values in CX Sales and B2B Service to map your existing data to the Contact import object?

  • Do you have to extend CX Sales and B2B Service to add attributes?

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

  • How do I verify my imported data?

How Business Objects are Structured

You must understand how your contact data corresponds with the data in CX Sales and B2B Service to map your legacy data to the data in CX Sales and B2B Service.

In Oracle Cloud 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 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 such as contact job, contact phone, contact address, and contact e-mail.

Note: All contact objects, such as phone or e-mail, include a child object that has the contact preference. For example, the Phone Contact Preference object has the contact preference of the consumer for the contact method phone.

CX Sales and B2B Service incorporates the structure of the contact business object into import objects. The import object for contacts is Contact.

How Business Object Attributes are Structured

Every import object is a collection of attributes that help to map your data to the Oracle Applications Cloud data and to support one-to-many relationships between the structural components of a contact.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for CX Sales and B2B Service) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Contact Import Objects Work Together.

Import Object Related Import Object Topic

Contact

Contact Import Objects: How They Work Together

Note:

You can use the keyword importing contacts to search for related topics in CX Sales and B2B Service help.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import Contacts Using File-Based Data Import

You must first prepare a source data file to import contacts. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You can also access these tasks from the Data Import and Export functional area of the Sales offering. You submit file import activities for each import object. When you're creating a new contact, you use the Contact object to import your data. You must have the Master Data Management Administrator job role to access and submit the import activities for contacts.

The Define File-Based Data Import Setup and Maintenance task list includes the tasks that are required to configure the import objects, to create source-file mappings, and to schedule the import activities.

You submit file-based import activities for each import object. When you're creating a new 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.

How You Verify Your Imported Data

You can use the File Import activity reports to verify imported data. Alternatively, you can also navigate to the Accounts work area to view the account information that you have imported.

How Contact Import Objects Work Together

You use the Contact import object to import contacts and objects related to the contact. This topic describes the Contact import object and introduces:

  • Target import object

  • Target import object attributes

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

Overview of Contact Target Import Objects

Use the Contact import object to import contacts and objects related to contacts. The Contact import object is split into smaller objects to organize the individual attributes of the contact.

The target import objects in the Contact import object 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. You can also have 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 don't 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.

Use these target import objects to create and update the corresponding contact and contact preference information:

  • PersonProfile

  • Fax

  • PrimaryPhone

  • Url

  • SalesProfile

  • Classification

  • AdditionalName

  • Relationship

  • AdditionalIdentifier

Use these target import objects to update or create a contact point for a contact relationship:

  • ContactRelationship

  • ContactJob

  • ContactAddress

  • ContactEmail,

  • ContactPhone

  • ContactMobile

  • ContactInstantMessenger

  • ContactFax.

All contact-point-related objects, such as phone or e-mail, include a child object that saves the contact preference. For example, the ContactPhoneContactPreference object saves the contact preference of the primary phone contact method.

Multiple contact points exist for a contact. More than one contact point might share the same purpose. To set a contact point as the primary for each purpose, enable the PrimarybyPurpose check box when importing the object attributes.

If you set the DO_NOT_VALIDATE_FLAG to "Y" for a record in the HZ_LOCATIONS_T table for contacts, such records aren't validated.

Contact Target Import Object Attributes

Compare attributes that you want to import with the available target object attributes and their valid values. Use a reference file to evaluate your source data and attributes for mapping and validation. See the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. A reference guide file includes:

  • Attribute descriptions

  • Default values

  • Validations for the attributes

Review the validation for each attribute to know if you need to do any setup tasks.

Define and Manage Import Mappings

You must define a mapping between your source data and a combination of the target object and target object attributes to import your source file data. To define and manage import mappings, do one of these:

  1. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when you define the import activity. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note: If any of the attributes that you want to import don't have an equivalent for the target object attribute, then review the Application Composer configuration features for the contact object.

Reference Files for Contact Target Import Objects

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Here is a list of reference files and their target import objects.

Target Import Object Description Reference Guide File Names

PersonProfile

Includes information that identifies a contact, such as first name, last name, date of birth, and so on.

HZ_IMP_PARTIES_T_Reference

SalesProfile

Includes detailed information about a sales profile. A sales profile is a specific sell-to object within a given account. An account or contact can have multiple sales profiles.

ZCA_IMP_Sales_Accounts_Reference

Fax

Contact's fax number.

HZ_IMP_CONTACTPTS_T_Reference

FaxContactPreference

Contact's preferences about being contacted through Fax.

HZ_IMP_CONTACTPREFS_Reference

Phone

Contact's phone number. If the contact has multiple phone numbers, then the first phone number is designated as the primary phone number. The attributes of PrimaryPhone, Fax, and URL are the same. However, the value of the attribute ContactPointType is different for each of these contact point related objects.

HZ_IMP_CONTACTPTS_T_Reference

PhoneContactPreference

Contact's preferences about being contacted by phone.

HZ_IMP_CONTACTPREFS_Reference

Email

Contact's e-mail.

HZ_IMP_CONTACTPTS_T_Reference

EmailContactPreference

Contact's preferences about being contacted through e-mail.

HZ_IMP_CONTACTPREFS_Reference

InstantMessenger

Contact's instant messenger information.

HZ_IMP_CONTACTPTS_T_Reference

Mobile

Contact's mobile number.

HZ_IMP_CONTACTPTS_T_Reference

MobileContactPreference

Contact's preferences about being contacted through mobile phone.

HZ_IMP_CONTACTPREFS_Reference

Classification

Contact's classification information. Classification lets you categorize entities, such as parties, projects, tasks, and orders as hierarchies.

HZ_IMP_CLASSIFICS_T_Reference

Address

Contact's address. If the contact has multiple addresses, then the first address is designated as the primary address.

HZ_IMP_PARTYSITES_T_Reference

AddressContactPreference

Contact's preferences about being contacted at the primary address.

HZ_IMP_CONTACTPREFS_Reference

AdditionalName

Contact's alternative name.

HZ_IMP_ADDTNLPARTYNAMES_T_Reference

AdditionalIdentifier

Includes the basic information about an additional identifier for the contact.

HZ_IMP_ADDTNLPARTYIDS_T_Reference

ContactRelationship

Includes information about a relationship between the contact and other parties.

HZ_IMP_RELSHIPS_T_Reference

ContactEmail

Contact's e-mail contact point.

HZ_IMP_CONTACTPTS_T_Reference

ContactEmailContactPreference

Contact's preferences about being contacted through the e-mail contact point.

HZ_IMP_CONTACTPREFS_Reference

ContactFax

Indicates the number of the fax contact point of the contact.

HZ_IMP_CONTACTPTS_T_Reference

ContactFaxContactPreference

Contact's preference about being contacted through the fax contact point.

HZ_IMP_CONTACTPREFS_Reference

ContactInstantMessenger

Contact's instant messenger contact point.

HZ_IMP_CONTACTPTS_T_Reference

ContactMobile

Contact's mobile contact point.

HZ_IMP_CONTACTPTS_T_Reference

ContactMobileContactPreference

Contact's preferences about being contacted through the mobile phone contact point.

HZ_IMP_CONTACTPREFS_Reference

ContactPhone

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

HZ_IMP_CONTACTPTS_T_Reference

ContactPhoneContactPreference

Contact's preferences about being contacted through the phone contact point.

HZ_IMP_CONTACTPREFS_Reference

ContactAddress

Contact's address contact point. If the contact has multiple addresses, then the first address is designated as the primary address.

HZ_IMP_PARTYSITES_T_Reference

ContactAddressContactPreference

Contact's preferences about being contacted at the address contact point.

HZ_IMP_CONTACTPREFS_Reference

ContactJob

Contacts' job information.

HZ_IMP_CONTACTS_T_Reference

Import Country Structures Using File-Based Import

Importing Country Structures: Explained

You can import country structure data from an external data source into Sales and B2B Service 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 United States has the geography type of State at the topmost level, followed by the County, the City, and the Postal Code.

You can use the country structure to store information about:

  • The relationships between geographies within a country

  • The types of geographies for a country

Consider the following questions when importing your data:

  • How does your legacy or source system store and represent the country structure information when compared to Sales and B2B Service?

  • Do you have to configure values in Sales and B2B Service to map your existing data to the Country Structure import object?

  • Do you have to extend Sales and B2B Service to add attributes?

  • What import features are available to import your business data?

  • How do I verify my imported data?

How Business Objects Are Structured

You must understand how your country structure data corresponds with the data in Sales and B2B Service to map your legacy data to the data in Sales and B2B Service.

You must import a separate country structure import object for each country. Each of these import objects must contain the geography types that are used in the country's structure, organized in a hierarchy using geography level numbers. For example, if you're importing the country structure of Australia, you need to follow this country structure:

  1. Country

  2. State

  3. County

  4. Town

  5. ZIP

Import Object for the Country Structure

The import object for country structures is GeoStructureLevel.

How Business Object Attributes are Structured

Every import object is a collection of attributes that help to map your data to the Oracle Applications Cloud data and to support one-to-many relationships between the structural components of a country structure.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for CX Sales and B2B Service) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Country Structure Import Objects Work Together.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import Country Structures Using File-Based Data Import

You must first prepare a source data file to import accounts. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You can also access these tasks from the Data Import and Export functional area of the Sales offering.

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

How You Verify Your Imported Data

You can use the File Import activity reports to verify imported data. Alternatively, you can also navigate to the Country Structure work area to view the country structure information that you have imported.

How Country Structure Import Objects Work Together

You use the Country Structure import object to import country structures and objects related to the country structure. This topic describes the Country Structure import object and introduces:

  • Target objects

  • Target import object attributes

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

Overview of Country Structure Target Import Objects

Use the Country Structure import object to import country structures and objects related to country structures. The Country Structure import object is split into smaller objects to organize the individual attributes of the country structure. The target import objects in the Country Structure import object are grouped into information about the country structure and information about the other objects.

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.

Country Structure Target Import Object Attributes

Compare attributes that you want to import with the available target object attributes and their valid values. Use a reference file to evaluate your source data and attributes for mapping and validation. See the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. A reference guide file includes:

  • Attribute descriptions

  • Default values

  • Validations for the attributes

Review the validation for each attribute to know if you need to do any setup tasks.

Define and Manage Import Mappings

You must define a mapping between your source data and a combination of the target object and target object attributes to import your source file data. To define and manage import mappings, do one of these:

  1. Predefine the mappings in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when creating an import activity in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note: If any of your source attributes doesn't have a corresponding target object attribute, then you can extend the Country Structure object. Review the Application Composer Extensibility features for the Country Structure object for more information.

Reference Files for Country Structure Target Import Objects

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

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

Here is a list of reference files and their target import objects.

Target Import Object Description Reference Guide File Name

ImpGeoStructureLevel

Information that specifies a country's geography structure.

HZ_IMP_GEO_STRUCTURE _LEVELS_Reference

Import Customer Hierarchies Using File-Based Import

Importing Customer Hierarchies: Explained

You can import customer hierarchy and customer hierarchy data from an external data source into CX Sales and B2B Service using the File-Based Data Import feature. You use a customer hierarchy to save the hierarchical relationships of an account with other accounts. A customer hierarchy consists of hierarchy members. You can use a customer hierarchy to process payments from one account and apply them to another account in the same hierarchy. You can also use them to create the revenue roll-up report that rolls up revenue numbers from opportunities for all accounts in a hierarchy.

Consider the following questions when importing customer hierarchy information:

  • Are all members of the customer hierarchy available in CX Sales and B2B Service?

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

  • How does your legacy or source system store and represent the customer hierarchy information when compared to CX Sales and B2B Service?

  • Do you have to configure values in CX Sales and B2B Service to map your existing data to the Customer Hierarchy import object?

  • Do you have to extend CX Sales and B2B Service to add attributes?

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

  • How do I verify my imported data?

To import a customer hierarchy, you:

  1. Import accounts that must be a part of the customer hierarchy.

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

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

How Business Objects Are Structured

You must understand how your customer hierarchy data corresponds with the data in CX Sales and B2B Service to map your legacy data to the data in CX Sales and B2B Service. You must understand how the application represents the structure of the data for a customer hierarchy.

The customer hierarchy import object structure is hierarchical. The customer hierarchy is at the top level and 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.

How Business Object Attributes are Structured

Every import object is a collection of attributes that helps to map your data to the Oracle Cloud Applications data and to support one-to-many relationships between the structural components of a customer hierarchy.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for CX Sales and B2B Service) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Customer Hierarchy Import Objects Work Together.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import the Customer Hierarchy Using File-Based Data Import

You must first prepare a source data file to import customer hierarchies. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You can also access these tasks from the Data Import and Export functional area of the Sales offering.

You submit file import activities for each import object. When you're creating a new customer hierarchy, you use the Customer Hierarchy object to import your data.

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.

How You Verify Your Imported Data

You can use the File Import activity reports to verify imported data. Alternatively, you can also navigate to the Customer Hierarchy work area to view the customer hierarchy information that you have imported.

How Customer Hierarchy Import Objects Work Together

You use the Customer Hierarchy import object to import customer hierarchies and objects related to the customer hierarchy. This topic describes the Customer Hierarchy import object and introduces:

  • Target objects

  • Target import object attributes

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

Overview of Customer Hierarchy Target Import Objects

Use the CustomerHierarchy object to import customer hierarchies and the CustomerHierarchyMember object to import information about the customer hierarchy members. 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. You can have multiple hierarchy members associated with a customer hierarchy.

To import a customer hierarchy, you:

  1. Import customers are a 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.

Customer Hierarchy Target Import Object Attributes

Compare attributes that you want to import with the available target object attributes and their valid values. Use a reference file to evaluate your source data and CX Sales and B2B Service attributes for mapping and validation. See the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. A reference guide file includes:

  • Attribute descriptions

  • Default values

  • Validations for the attributes

Review the validation for each attribute to know if you need to do any setup tasks.

Define and Manage Import Mappings

You must define a mapping between your source data and a combination of the target object and target object attributes to import your source file data. To define and manage import mappings, do one of these:

  1. Predefine the mappings in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when creating an import activity in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note: If any of your source attributes doesn't have a corresponding target object attribute, then you can extend the Customer Hierarchy object. Review the Application Composer Extensibility features for the Customer Hierarchy object for more information.

Reference Files for Customer Hierarchy Target Import Object Attributes

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Here is a list of reference files and their target import objects.

Target Import Object Description Reference Guide File Names

CustomerHierarchy

Customer hierarchy definition and root node of the customer hierarchy

HZ_IMP_HIERARCHIES_T _Reference

CustomerHierarchyMember

Customer hierarchy members

HZ_IMP_HIERARCHY_NODES_ Reference

How You Import Customer Hierarchies

You can use the information in this topic to import customer hierarchies. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

Use the file-based import objects and target objects in this table to import customer hierarchies.

Import Object Target Objects

Customer Hierarchy

CustomerHierarchy

Overview of Customer Hierarchy

You use a customer hierarchy to save the hierarchical relationships of a customer with other customers. A customer hierarchy consists of hierarchy members.

You use a customer hierarchy to:

  • process payments from one customer and apply them to another customer in the same hierarchy

  • create the revenue roll-up report that rolls up revenue numbers from opportunities for all customers in a hierarchy

You can create multiple versions of a customer hierarchy. However, only one hierarchy version can be active on a specific date. You can create a new hierarchy to represent the structure of a new customer. If a customer has incorporated minor changes to the organization, you can create a new version instead of editing the existing customer hierarchy.

Identify and Associate Records with Each Other

To add or update an existing customer hierarchy, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process uses the combination of source system and source system reference value to identify the existing record.

You can use external IDs or business keys to identify and associate records with each other when you're importing a smaller set of records. Business keys are attributes that uniquely identify a party record. For example, a person's last name and first name uniquely identify a person. An external ID is a unique record identifier from an application outside of CX Sales and B2B Service.

You can extend source systems to identify the source of the data. You use source systems that are external sources of data to import data into Oracle Application Cloud. Oracle Application Cloud uses source system references to create references between source IDs and the Oracle Application Cloud database IDs. You can extend source systems in one of these ways:

  • Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  • Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

Before You Start

The minimum data required to import customer hierarchy information depends on:

  • The purpose of the import. The data is different when you create both the party and the customer hierarchy in the same import batch, add new customer hierarchy to an existing party, or update a customer hierarchy record.

  • The data requirements are different when using source system information or record IDs when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update an account profile and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Customer Hierarchy Records in the Same Batch Creating Customer Hierarchy Record for an Existing Party

Language

Indicates the code of the language into which the contents of the translatable columns are translated.

View the valid language codes. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage ISO Languages

Default is US if not specified.

Conditionally required.

Required when creating a new hierarchy (tree version).

Conditionally required.

Required when creating a new hierarchy (tree version).

SourceLangFlag

This check box indicates whether the language specified by the Language attribute is the source language in which the contents of this record are being created or were originally created.

No setup task required.

Conditionally required.

Required when creating a new hierarchy (tree version).

Conditionally required.

Required when creating a new hierarchy (tree version).

HierarchyType

Unique Identifier for a tree structure.

You can create and manage Tree structures. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Tree Structures

Required

Required

HierarchyCode

User-defined identifier for a tree.

If the import object is Employee resource, then HiearchyCode must be 'GLOBAL_SALES_MARKETING,' else the value is free text.

Required

Required

HierarchyName

The name of the tree.

No setup task required.

Required

Required

HierarchyVersionName

The name of the tree version.

No setup task required.

Conditionally required.

Required when creating a hierarchy (tree version).

Conditionally required.

Required when creating a hierarchy (tree version).

ActionCode

This attribute specifies to insert or to delete the hierarchy (tree version). If provided, valid values are INSERT, UPDATE, and DELETE.

Use the UPDATE value when updating a record. If deleting an existing record, use the value, DELETE. If inserting a record, use the value INSERT.

Conditionally required.

The value DELETE is required if you're deleting an existing hierarchy (tree version).

Conditionally required.

The value DELETE is required if you're deleting an existing hierarchy (tree version).

AsOfDate

The date that's used to determine the tree version to delete when ActionCode is provided as DELETE. Only one version is active on any given date.

No setup task required.

Conditionally required.

A value is required if deleting an existing hierarchy (tree version).

Conditionally required.

A value is required if deleting an existing hierarchy (tree version).

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CXSales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in the Oracle Fusion Help Application search. The Help Application is available from any Oracle Fusion Application page by clicking Help and selecting Applications Help.

  • Importing customer hierarchies.

  • Importing customer hierarchy members.

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

How You Import Customer Hierarchy Members

You can use the information in this topic to import customer hierarchy members. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

Use the file-based import object and target object in this table to import customer hierarchy members.

Import Object Target Object

Customer Hierarchy Member

CustomerHierarchyMember

You use a customer hierarchy to save the hierarchical relationships of a customer with other customers. A customer hierarchy consists of hierarchy members.

Identify and Associate Records with Each Other

To add or update a customer hierarchy member, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

You can set up source systems to identify the source of the data you're importing. Source systems are external sources of data that are used to import data. Source system references are used by the application to create references between source IDs and the database IDs. You can configure source systems either by using the Manage Trading Community Source System task or by importing the source system information into Oracle Cloud Applications using the Source System Reference import object.

You can use external IDs or business keys to identify and associate records with each other when you're importing a smaller set of records. Business keys are attributes that uniquely identify a party record. For example, a person's last name and first name uniquely identify a person. An external ID is a unique record identifier from an application outside of CX Sales and B2B Service.

You can extend source systems to identify the source of the data. You use source systems that are external sources of data to import data into Oracle Application Cloud. Oracle Application Cloud uses source system references to create references between source IDs and the Oracle Application Cloud database IDs. You can extend source systems in one of these ways:

  • Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  • Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

Before You Start

The minimum data required to import customer hierarchy member information depends on:

  • The purpose of the import. The data is different when you create both the party and the customer hierarchy member in the same import batch, add new customer hierarchy member to an existing party, or update a customer hierarchy member record.

  • Identifying and associating records. The data requirements are different when you're using source system information or record IDs to identify and associate records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update a customer hierarchy member and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Customer Hierarchy Member Records in the Same Batch Creating Customer Hierarchy Member Record for an Existing Party

ActionCode

This attribute specifies to insert or to delete the hierarchy node (tree node). This attribute is typically used only to delete a record.

Use the UPDATE value when updating a record. If deleting an existing record, use the value, DELETE. If inserting a record, use the value INSERT.

Conditionally required.

A value is required if deleting an existing hierarchy node.

Conditionally required.

A value is required if deleting an existing hierarchy node.

AsOfDate

When ActionCode is provided as DELETE, AsOfDate determines the tree version from which to delete the hierarchy node. Only one version is active on any given date.

No setup task required.

Conditionally required.

A value is required if deleting an existing hierarchy node.

Conditionally required.

A value is required if deleting an existing hierarchy node.

HierarchyType

Unique Identifier for a tree structure.

You can create and manage Tree structures. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Tree Structures

Required

Required

HierarchyCode

User-defined identifier for a tree.

HierarchyCode must exist in the FND_TREE table, column TREE_CODE, or, if the hierarchy is being created in the same batch as this node, then HierarchyCode must exist in HZ_IMP_HIERARCHIES_T table (the interface table for the new hierarchy), column TREE_CODE (the HierarchyCode attribute for a hierarchy import).

Required

Required

PartyOrigSystem

The source system code that identifies the original source system of the party that you're inserting as a new node or that exists as the node to be deleted. You provide the source system reference (PartyOrigSystemReference) and the source system code (PartyOrigSystem) when the source of your data is your legacy or external system. The import process uses the source system code and source system reference values to find the internal ID (PartyId) that uniquely identifies an existing party record that was originally imported with the source system reference and source system code values in a prior batch. The party is either being inserted as a new node or is a node to be deleted in this batch.

Predefine your source system code as enabled for parties. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

Conditionally required.

If deleting an existing node, then identify the node by providing either PartyId or both PartyOrigSystem and PartyOrigSystemReference.

Conditionally required.

If deleting an existing node, then identify the node by providing either PartyId or both PartyOrigSystem and PartyOrigSystemReference.

PartyOrigSystemReference

The ID that identifies the party that's the parent node of this node in your legacy or external system. You provide the source system reference (ParentPartyOrigSystemReference) and the source system code (ParentPartyOrigSystem) when the source of your data is your legacy or external system. The import process uses the source system code and source system reference values to:

  • find the internal ID (ParentPartyId) that uniquely identifies the existing parent node (party record) that was originally imported with the source system reference and source system code values in a prior batch.

  • find the internal ID (ParentPartyId) for the new parent node with the source system reference and source system code values that's imported in the same batch as this node.

Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference you will use when importing the party in the same batch

Conditionally required.

If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.

Conditionally required.

If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.

PartyId

The unique internal ID of the existing party record that's either being inserted as a new node or is an existing node to be deleted in this batch.

You can obtain the Party ID for an existing party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Conditionally required.

If deleting an existing node, then identify the node by providing either PartyId or both PartyOrigSystem and PartyOrigSystemReference.

Conditionally required.

If deleting an existing node, then identify the node by providing either PartyId or both PartyOrigSystem and PartyOrigSystemReference.

ParentPartyId

The unique internal ID for the existing party record that's the parent node of this node.

You can obtain the Parent Party ID for an existing party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Conditionally required.

If you're creating a new node or deleting an existing node, and the node isn't the root node of the hierarchy, then you must identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.

Conditionally required.

If you're creating a new node or deleting an existing node, and the node isn't the root node of the hierarchy, then you must identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.

ParentPartyOrigSystem

The source system code that identifies the original source system of the party that's the parent node of this node. You provide the source system reference (ParentPartyOrigSystemReference) and the source system code (ParentPartyOrigSystem) when the source of your data is your legacy or external system. The import process uses the source system code and source system reference values to:

  • find the internal ID (ParentPartyId) that uniquely identifies the existing parent node (party record) that was originally imported with the source system reference and source system code values in a prior batch.

  • find the internal ID (ParentPartyId) for the new parent node with the source system reference and source system code values that's imported in the same batch as this node.

Predefine your source system code as enabled for parent parties. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

Conditionally required.

If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.

Conditionally required.

If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.

ParentPartyOrigSystemReference

The ID that identifies the party that's the parent node of this node in your legacy or external system. You provide the source system reference (ParentPartyOrigSystemReference) and the source system code (ParentPartyOrigSystem) when the source of your data is your legacy or external system. The import process uses the source system code and source system reference values to:

  • find the internal ID (ParentPartyId) that uniquely identifies the existing parent node (party record) that was originally imported with the source system reference and source system code values in a prior batch.

  • find the internal ID (ParentPartyId) for the new parent node with the source system reference and source system code values that's imported in the same batch as this node.

Identify the reference value from your source system that was used when you imported the parent party in a prior batch, or identify the source system reference you will use when importing the parent party in the same batch.

Conditionally required.

If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.

Conditionally required.

If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in the Oracle Fusion Help Application search. The Help Application is available from any Oracle Fusion Application page by clicking Help and selecting Applications Help.

  • Importing customer hierarchies.

  • Importing customer hierarchy members.

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

Import Customers Using File-Based Import

Importing Customers: Explained

You can import account data from an external data source into Sales and B2B Service using the File-Based Data Import feature.

You use the account business object to store information about an account, such as:

  • profile

  • relationship information

  • contact points

Consider the following questions when importing your data:

  • How does your legacy or source system store and represent the account information when compared to Sales and B2B Service?

  • Do you have to configure values in Sales and B2B Service to map your existing data values to the Account import object?

  • Do you have to extend Sales and B2B Service to add attributes?

  • What import features are available to import your business data?

  • How do I verify my imported data?

How Business Objects Are Structured

You must understand how your account data corresponds with the data in Sales and B2B Service to map your legacy data to the data in Sales and B2B Service.

The Account object is hierarchical. Ensure that an account exists before you can import its child objects, such as classifications and contacts. These child objects can in turn consist of other objects. You use this structure to support one-to-many relationships between the objects that make up the account.

The image shows the account object and its child objects.

Account import object structure

The top-level account object contains basic information about the account, such as name and party usage. For every account, you can assign:

  • Classifications

  • Contacts

  • Sell to addresses

  • Phone details

  • Additional names

The contact of the account includes other child entities with information about the contact, such as:

  • Contact job

  • Contact primary phone

  • Contact primary address

  • Contact e-mail address

Note: All contact objects, such as primary phone or e-mail, include a child object that has the contact preference. For example, the Primary Phone Contact Preference object has the contact preference of the account for the contact method primary phone.

How Business Object Attributes Are Structured

Every import object is a collection of attributes that help to map your data to the Oracle Applications Cloud data and to support one-to-many relationships between the structural components of an account.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for Engagement) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Account Import Objects Work Together.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import Accounts Using File-Based Data Import

You must first prepare a source data file to import accounts. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You can also access these tasks from the Data Import and Export functional area of the Sales offering.

You submit file import activities for each import object. When you're creating a new account, you use the Account object to import your data. You must have the Customer Relationship Management Application Administrator job role to access and submit the import activities for accounts.

When importing account information, you import:

  1. the basic account profile information

  2. the child entities for the account

When importing child objects, you must provide the parent reference information for all parent levels of the object. For example, you:

  1. import basic profile details, such as customer name, party type, and party usage

  2. import contacts and contact information, such as phone, address, contact points, and fax for the account

  3. provide the PartyOrigSystem and PartyOrigSystemReference of the account when importing contacts for the account

PartyOrigSystem is the source system code that identifies the source of the information. PartyOrigSystemReference is unique for each row of data within an import job, and is a combination of PartyOrigSystem and a unique reference. When importing contact information for an account, you must provide the relationship reference information. This information is required, as contacts can have multiple relationships with accounts.

Note: Party Usages are created based on the input provided, but the import operation can't create multiple party usages provided in a single cell.

In the input file, if you attempt to pass the partyusagecode as "SALES_PROSPECT, CONTACT", the import operation doesn't process it as "SALES_PROSPECT, CONTACT". For a party ID, the "SALES_PROSPECT" is processed in one batch, while the "CONTACT" is processed in another batch.

How You Verify Your Imported Data

You can use the File Import activity reports to verify imported data. Alternatively, you can also navigate to the Accounts work area to view the account information that you have imported.

How Account Import Objects Work Together

You use the Account import object to import accounts and objects related to the account. This topic describes the Account import object and introduces:

  • Target objects

  • Target import object attributes

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

Overview of Account Target Import Objects

You use the Account import object to import accounts and objects related to accounts. The Account import object is split into smaller objects to organize the individual attributes of the account.

The target import objects in the Account import object are grouped into information about the account and information about the other objects. You can have multiple contacts associated with an account.

Consider these points when you import an account:

  • When you update an existing account with additional information, you must provide information about the existing account.

  • When you import account contacts or contact information for an account, you must provide relationship reference information in addition to the parent reference. This is required, as a contact can have many relationships with an organization, such as an employee or a board member.

  • When you import information about a contact, you must refer to the specific relationship for which you want to import information. For example, you might want to import information for John Smith the employee or John Smith the board member.

If you don't include the reference information for an account-contact relationship, then the import process creates a relationship.

Consider these points when you create or update an existing account and an account contact:

  • You can import account profile information, addresses, and contact points, such as a phone and fax.

  • Use these target import objects to create and update account and account contact information:

Account Account Contact

Account

ContactPersonProfile

Fax

ContactJob

Address

ContactPrimaryAddress

PrimaryPhone

ContactEmail

Url

ContactPrimaryPhone

SalesAccountProfile

ContactMobile

Classification

ContactInstantMessenger

AdditionalName

ContactFax

Relationship

 

SellToAddress

AdditionalIdentifier

  • Use contact-related entities, such as primary phone or e-mail that include a child entity with the contact preference. For example, the Primary Phone Contact Preference entity has the contact preference of the legal entity for the contact method Primary Phone.

An account has multiple contact points with more than one contact point sharing the same purpose. If you set a contact point as the primary for each purpose, enable the PrimarybyPurpose check box when importing the object attributes.

To skip validating a record, set the DO_NOT_VALIDATE_FLAG to "Y" for a record in the HZ_LOCATIONS_T table.

Account Target Import Object Attributes

Compare attributes that you want to import with the available target object attributes and their valid values. Use a reference file to evaluate your source data and CX Sales and B2B Service attributes for mapping and validation. See the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. A reference guide file includes:

  • Attribute descriptions

  • Default values

  • Validations for the attributes

Review the validation for each attribute to know if you need to do any setup tasks.

Define and Manage Import Mappings

You must define a mapping between your source data and a combination of the target object and target object attributes to import your source file data. To define and manage import mappings, do one of these:

  1. Predefine the mappings in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when creating an import activity in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note: If any of your source attributes doesn't have a corresponding target object attribute, then you can extend the Account object. Review the Application Composer Extensibility features for the account object for more information.

Reference Files For Account Target Import Objects

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Here is a list of reference files and their target import objects.

Target Import Object Description Reference Guide File Names

Account

Includes detailed account information, such as, organization name and organization type.

HZ_IMP_PARTIES_T_Reference

PrimaryPhone

The account's primary phone number. If the account has multiple phone numbers, one of the phone numbers is designated as the primary phone number.

HZ_IMP_CONTACTPTS_T_ Reference

Address

The account's address.

HZ_IMP_LOCATIONS_T_Reference

Classification

The account's classification.

HZ_IMP_CLASSIFICS_T_Reference

AdditionalName

The account's additional or alternative name.

HZ_IMP_ADDTNLPARTYNAMES_ T_Reference

Fax

The account's fax number.

HZ_IMP_CONTACTPTS_T _Reference

FaxContactPreference

Indicates the account preference about being contacted through Fax.

HZ_IMP_CONTACTPREFS_ Reference

Url

The account's URL.

HZ_IMP_CONTACTPTS_T_ Reference

SalesProfile

The account's sales account information. A sales account is a specific sell-to entity within a given account. an account can have multiple sales accounts and sales profiles.

ZCA_IMP_SALES_ACCOUNTS _Reference

SellToAddress

The account's addresses and party sites information. If party site usage of an address isn't defined, then the import process sets it to Sell-To. If there are multiple addresses without party site usage information, then the import process designates one of the addresses as the Sell-To address.

HZ_IMP_PARTYSITES_T_ Reference

AdditionalIdentifier

The account's additional identifier information.

HZ_IMP_ADDTNLPARTYIDS_T _Reference

Relationship

The account's relationship information. You must enter a relationship code in the RelationshipCode column, when creating a relationship.

HZ_IMP_RELSHIPS_T_Reference

ContactPersonProfile

The account contact's person information.

HZ_IMP_RELSHIPS_T_Reference

ContactAdditionalName

The account contact's additional name.

HZ_IMP_ADDTNLPARTYNAMES_T _Reference

ContactEmail

The account contact's email.

HZ_IMP_CONTACTPTS_T_ Reference

ContactInstantMessenger

The account contact's instant messenger or social networking information.

HZ_IMP_CONTACTPTS_T_ Reference

ContactPrimaryAddress

The account contact's primary address. If the contact has multiple addresses, one of the addresses is designated as the primary address.

HZ_IMP_PARTYSITES_T _Reference

ContactFax

The account contact's fax.

HZ_IMP_CONTACTPTS_T_ Reference

ContactJob

The account contact's job information.

HZ_IMP_CONTACTS_T_Reference

ContactMobile

The account contact's mobile number.

HZ_IMP_CONTACTPTS_T_ Reference

ContactPrimaryPhone

The account contact's primary phone number. If the account has multiple phone numbers, one of the phone numbers is designated as the primary phone number.

HZ_IMP_CONTACTPTS_T _Reference

PrimaryPhoneContactPreference

Indicates the account contact preference about being contacted through phone.

HZ_IMP_CONTACTPREFS _Reference

ContactEmailContactPreference

Indicates the account contact preference about being contacted through e-mail.

HZ_IMP_CONTACTPREFS_ Reference

ContactFaxContactPreference

Indicates the account contact preference about being contacted through Fax.

HZ_IMP_CONTACTPREFS_ Reference

ContactMobileContactPreference

Indicates the account contact preference about being contacted through mobile phone.

HZ_IMP_CONTACTPREFS_ Reference

ContactPrimaryAddressContactPreference

Indicates the account contact preference about being contacted at the primary address.

HZ_IMP_CONTACTPREFS _Reference

ContactPrimaryPhoneContactPreference

Indicates the account contact preference about being contacted through the primary phone number.

HZ_IMP_CONTACTPREFS _Reference

To update any contact information, use the Contact target object.

Import Employee Resources Using File-Based Import

Importing Employee Resources: Explained

You can import employee resource data from an external data source into Sales and B2B Service 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.

Consider the following questions when importing your data:

  • How does your legacy or source system store and represent the employee resource information when compared to Sales and B2B Service?

  • Do you have to configure values in Sales and B2B Service to map your existing data to the Employee Resource import object?

  • Do you have to extend Sales and B2B Service to add attributes?

  • What import features are available to import your business data?

  • How do I verify my imported data?

How Business Objects are Structured

You must understand how your employee resource data corresponds with the data in Sales and B2B Service to map your legacy data to the data in Sales and B2B Service.

You use one table to store 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.

This image shows the Employee Resource object.

Employee resource object structure

The worker profile contains basic information about the employee resource, such as the employee resource's primary address and resource profile details.

How Business Object Attributes are Structured

Every import object is a collection of attributes that help to map your data to the Oracle Applications Cloud data and to support one-to-many relationships between the structural components of an employee resource.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for Engagement) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Employee Resource Import Objects Work Together.

Note:

You can use the keyword importing employee resources to search for related topics in Sales and B2B Service help.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

    You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import Employee Resources Using File-Based Data Import

You must first prepare a source data file to import employee resources. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You can also access these tasks from the Data Import and Export functional area of the Sales offering. You submit file import activities for each import object. When you're creating a new employee resource, you use the Employee Resource object to import your data. You must have the Master Data Management Administrator job role to access and submit the import activities for employee resources.

Note: Employee Resource import is impacted by the error limit settings in the HCM loader. The default error limit in HCM loader may not always be suitable for Oracle Cloud Applications implementations. Oracle recommends that you review the current settings and set the Loader Maximum Errors Allowed parameter to an acceptable value before launching Employee Resource Import.

You can set this parameter in the Setup and Maintenance work area, in the HCM Configuration for Coexistence task. You need to set a value for this parameter depending on the batch sizes that you would run. For example, if you run import jobs with 5000 rows at a tolerance level of 20%, then you can set this parameter to 1000. On the other hand, if you run import jobs with 5000 rows at a tolerance of .5%, then you can set this parameter to 25.

Note: The data quality options, such as matching and cleansing, aren't relevant for Employee Resource import. Hence, while importing employee resources using file-based import, ensure that you set the Customer Data Management Duplicates LOV to blank.

How You Verify Your Imported Data

You can use the File Import activity reports to verify imported data. Alternatively, you can also navigate to the Employee Resources work area to view the account information that you have imported.

How Employee Resource Import Objects Work Together

Employee resources are employees to whom you can assign work objects, for example, service agents, sales managers, and so on. You use the Employee Resource import object to import employee resources and objects related to the employee resource. This topic describes the Employee Resource import object and introduces:

  • Target objects

  • Target import object attributes

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

Overview of Employee Resource Target Import Objects

Use the Employee Resource import object to import employee resources and objects related to employee resources. The Employee Resource import object is split into smaller objects to organize the individual attributes of the employee resource.

Consider these points when you import an employee resource:

  • The target import objects in the Employee Resource import object are grouped into information about the employee resource's profile and the 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 along with the parent reference, as an employee resource can belong to multiple teams simultaneously.

  • To update the information about an existing employee resource or to create an employee resource record, you can import employee resource profile information and addresses. Use these target import objects to create and update employee resource information:

    • WorkerProfile

    • ResourceProfile

    • PrimaryAddress

  • To update or create an employee resource's resource profile, use these target import objects:

    • ResourceOrganizationMembership

    • ResourceTeamMembership

Employee Resource Target Import Object Attributes

Compare attributes that you want to import with the available target object attributes and their valid values. Use a reference file to evaluate your source data and attributes for mapping and validation. See the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. A reference guide file includes:

  • Attribute descriptions

  • Default values

  • Validations for the attributes

Review the validation for each attribute to know if you need to do any setup tasks.

Define and Manage Import Mappings

You must define a mapping between your source data and a combination of the target object and target object attributes to import your source file data. To define and manage import mappings, do one of these:

  1. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when you define the import activity. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note: If any of your source attributes doesn't have a corresponding target object attribute, then you can extend the Employee Resource object. Review the Application Composer Extensibility features for the account object for more information.

Reference Files for Employee Resource Target Import Object Attributes

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Here is a list of reference files and their target import objects.

Target Import Object Description Reference Guide File Names

WorkerProfile

Includes detailed employee information such as employee resource name and address.

HRC_LOADER_BATCH_LINES _Reference_For_Employee_Resources

ResourceProfile

Contains information about a resource, such as first name, last name, department, and job code.

HZ_IMP_RESOURCES_Reference

PrimaryAddress

Employee resource's address. If the resource has multiple addresses, then the first address is designated as the primary address.

HZ_IMP_PARTYSITES_T_Reference

ResourceOrganizationMembership

Employee resource's resource organization membership information.

HZ_IMP_GROUP_MEMBERS _Reference

ResourceTeamMembership

Employee resource's resource team membership information.

HZ_IMP_TEAM_MEMBERS_ Reference

Import Geographies Using File-Based Import

Importing Geographies: Explained

A geography is any region with a boundary around it. It might be a state, a country, a city, a county, or a ward. You must create or import geographies before you can associate them with company-specific zones and addresses.

You can import geography data from an external data source into CX Sales and B2B Service using the File-Based Data Import feature.

Consider the following questions when importing your data:

  • How does your legacy or source system store and represent the geography information when compared to CX Sales and B2B Service?

  • Do you have to configure values in CX Sales and B2B Service to map your existing data to the Geography import object?

  • Do you have to extend CX Sales and B2B Service to add attributes?

  • What import features are available to import your business data?

  • How do I verify my imported data?

Note: CX Sales and B2B Service ships with third-party master geography data for multiple countries. You can import geography data using the Manage Geographies task. Search for the country, and select Import Geography Data from the Actions menu. If the licensed data isn't available for a country, then the Import Geography Data action is disabled. For more information, see the procedure Replacing Existing Master Geography Data with Revised Oracle-Licensed Geography Data.
Note: Geography names are not translatable and are always displayed in the same language in which they were loaded irrespective of the language of the signed in user. If you need different options of display, you can use the alternative names option.

How Business Objects are Structured

You must understand how your geography data corresponds with the data in CX Sales and B2B Service to map your legacy data to the data in CX Sales and B2B Service.

You must import a separate country structure import object for each country. Each of these import objects must contain the geography types that are used in the country's structure, organized in a hierarchy using geography level numbers. For example, if you're importing the country structure of Australia, the country structure might be:

  1. Country

  2. State

  3. County

  4. Town

  5. ZIP

How Business Objects are Structured

Every import object is a collection of attributes that help to map your data to the Oracle Applications Cloud data and to support one-to-many relationships between the structural components of a geography.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for CXSales and B2B Service) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Geography Import Objects Work Together.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import Geographies Using File-Based Data Import

You must first prepare a source data file to import geographies. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You can also access these tasks from the Data Import and Export functional area of the Sales offering.

You submit file import activities for each import object. When you're creating a new geography, you use the Geography object to import your data. You must have 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.

How You Verify Your Imported Data

You can use the File Import activity reports to verify imported data. Alternatively, you can also navigate to the Geographies work area to view the geography information that you have imported.

How Geography Import Objects Work Together

You use the Geography import object to import geographies and objects related to the geography. This topic describes the Geography import object and introduces:

  • Target import objects

  • Target import object attributes

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

Overview of Geography Target Import Objects

Use the Geography import object to import geographies and objects related to geographies. The Geography import object is split into smaller objects to organize the individual attributes of the geography.

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.

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

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

Geography Target Import Object Attributes

Compare attributes that you want to import with the available target object attributes and their valid values. Use a reference file to evaluate your source data and Sales and B2B Service attributes for mapping and validation. See the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. A reference guide file includes:

  • Attribute descriptions

  • Default values

  • Validations for the attributes

Review the validation for each attribute to know if you need to do any setup tasks.

Define and Manage Import Mappings

You must define a mapping between your source data and a combination of the target object and target object attributes to import your source file data. To define and manage import mappings, do one of these:

  1. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when you define the import activity. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note: If any of your source attributes doesn't have a corresponding target object attribute, then you can extend the Geography object. Review the Application Composer Extensibility features for the Geography object for more information.

Reference Files for Geography Target Import Objects

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Here is a list of reference files and their target import objects.

Target Import Object Description Attribute Reference File Names

ImpGeography

Contains information that saves a country's geography hierarchy details, such as geography type, geography code, and so on.

HZ_IMP_GEOGRAPHIES_T _Reference

Import Households Using File-Based Import

Importing Households: Explained

You can import household data from an external data source into CX Sales and B2B Service using the File-Based Data Import feature.

A household is a party consisting of a collection of persons and organizations. You use a household to enter into a business relationship with other parties and associate with opportunities and leads. A household can have members of party type person or organization. You can maintain household information to create leads and opportunities. However, maintaining this information may not let you assign all sales and marketing activities to a household.

Consider the following questions when importing your data:

  • How does your legacy or source system store and represent the household information when compared to CX Sales and B2B Service?

  • Do you have to configure values in CX Sales and B2B Service to map your existing data to the Household import object?

  • Do you have to extend CX Sales and B2B Service to add attributes?

  • What import features are available to import your business data?

  • How do I verify my imported data?

How Business Objects Are Structured

You must understand how your household data corresponds with the data in CX Sales and B2B Service to map your legacy data to the data in CX Sales and B2B Service.

The Household object is hierarchical. Ensure that a household exists before you can import its child objects, such as classifications, contacts, and relationships. These child entities can in turn consist of other objects. You use this structure to support one-to-many relationships between the objects that make up the household.

This image shows the household import object and its child entities.

Household import object structure

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

Note: All contact objects, such as primary phone or e-mail, include a child object that has the contact preference. For example, the Phone Contact Preference object has the contact preference of the household for the contact method primary phone.

How Business Object Attributes are Structured

Every import object is a collection of attributes that help to map your data to the Oracle Applications Cloud data and to support one-to-many relationships between the structural components of a household.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for CX Sales and B2B Service) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Household Import Objects Work Together.

Note:

You can use the keyword importing households to search for related topics in CX Sales and B2B Service Help.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import Households Using File-Based Data Import

You must first prepare a source data file to import households. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You can also access these tasks from the Data Import and Export functional area of the Sales offering. You submit file import activities for each import object. When you're creating a new household, you use the Household object to import your data. You must have the Customer Relationship Management Application Administrator job role to access and submit the import activities for households.

When importing household information, you import:

  1. the basic household information

  2. the child entities for the household

When importing child objects, you must provide the parent reference information for all parent levels of the object. For example, you:

  1. import basic profile details, such as name and household type

  2. import contacts and contact information, such as phone, address, contact points, and fax for the household

  3. provide the PartyOrigSystem and PartyOrigSystemReference of the household when importing contacts for the household

PartyOrigSystem is the source system code that identifies the source of the information. PartyOrigSystemReference is unique for each row of data within an import job, and is a combination of PartyOrigSystem and a unique reference. When importing contact information for a household, you must provide the relationship reference information. This information is required, as contacts can have multiple relationships with households.

How You Verify Your Imported Data

You can use the File Import activity reports to verify imported data. Alternatively, you can also navigate to the Households work area to view the account information that you have imported.

Household Import Objects: How They Work Together

You use the Household import object to import households and objects related to the household. This topic describes the Household import object and introduces:

  • Target import objects

  • Target import object attributes

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

Overview of Household Target Import Objects

Use the Household import object to import households and objects related to households. The Household import object is split into smaller objects to organize the individual attributes of the household.

The target import objects in the Household import object are grouped into information about the household and information about the other objects. You can have multiple contacts associated with a household. Consider these points when you import a household:

  • When you update an existing household with additional information, you must provide information about the existing household.

  • When you import household contacts or contact information for a household, you must provide relationship reference information in addition to the parent reference. This is required, as a contact can have many relationships with an organization, such as an employee or a board member.

  • When you import information about a contact, you must refer to the specific relationship for which you want to import information. For example, you might want to import information for John Smith the employee or John Smith the board member.

If you don't include the reference information for a household-contact relationship, then the import process creates a relationship.

Consider these points when you create or update an existing household and a household contact:

  • You can import household profile information, addresses, and contact points, such as a phone and fax.

  • Use these target import objects to create and update household and household contact information:

    • GroupProfile

    • Fax

    • Mobile

    • Phone

    • E-mail

    • InstantMessenger

    • Relationship

    • Member

    • Address

    • Classification

    • AdditionalName

    • AdditionalIdentifier

  • Use contact-related entities, such as primary phone or e-mail that include a child entity with the contact preference. For example, the Primary Phone Contact Preference entity has the contact preference of the legal entity for the contact method Primary Phone. Additionally, the Address import object for a household includes another child entity AddressPurpose that saves the purpose of the current household address.

A household has multiple contact points with more than one contact point sharing the same purpose. If you set a contact point as the primary for each purpose, enable the PrimarybyPurpose check box when importing the object attributes.

To skip validating a record, set the DO_NOT_VALIDATE_FLAG to "Y" for a record in the HZ_LOCATIONS_T table.

Household Target Import Objects Attributes

Compare attributes that you want to import with the available target object attributes and their valid values. Use a reference file to evaluate your source data and CX Sales and B2B Service attributes for mapping and validation. See the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. A reference guide file includes:

  • Attribute descriptions

  • Default values

  • Validations for the attributes

Review the validation for each attribute to know if you need to do any setup tasks.

Define and Manage Import Mappings

You must define a mapping between your source data and a combination of the target object and target object attributes to import your source file data. To define and manage import mappings, do one of these:

  1. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when you define the import activity. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note: If any of your source attributes doesn't have a corresponding target object attribute, then you can extend the Household object. Review the Application Composer Extensibility features for the household object for more information.

Reference Files for Household Target Import Objects

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Here is a list of reference files and their target import objects.

Target Import Object Description Reference Guide File Names

GroupProfile

Household information. The default party usage for a household is SALES_PROSPECT.

HZ_IMP_PARTIES_T_Reference

Relationship

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

HZ_IMP_RELSHIPS_T

Member

Household member's information.

HZ_IMP_RELSHIPS_T

Classification

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

HZ_IMP_CLASSIFICS_T

AdditionalIdentifier

Household's additional identifier information.

HZ_IMP_ADDTNLPARTYID_T

AdditionalName

Household's alternative name.

HZ_IMP_ADDTNLPARTYNAMES _T

Url

Household's URL.

HZ_IMP_CONTACTPTS_T_ Reference

InstantMessenger

Household's instant messenger or social networking information.

HZ_IMP_CONTACTPTS_T _Reference

Fax

Household's fax.

HZ_IMP_CONTACTPTS_T _Reference

FaxContactPreference

Indicates the household preference about being contacted through fax.

HZ_IMP_CONTACTPREFS _Reference

Mobile

Household's mobile number.

HZ_IMP_CONTACTPTS_T_ Reference

MobileContactPreference

Indicates the household's preference about being contacted through mobile phone.

HZ_IMP_CONTACTPREFS_ Reference

Phone

Primary phone number of the household. If the household has multiple phone numbers, one of the phone numbers is designated as the primary phone number.

HZ_IMP_CONTACTPTS_T_ Reference

PrimaryPhoneContactPreference

Indicates the household's preference about being contacted through phone.

HZ_IMP_CONTACTPREFS_ Reference

Email

Household's e-mail.

HZ_IMP_CONTACTPTS_T_ Reference

EmailContactPreference

Indicates the household's preference about being contacted through e-mail.

HZ_IMP_CONTACTPREFS _Reference

Address

Household's address. If the household has multiple addresses, one of the addresses is designated as the primary address.

HZ_IMP_LOCATIONS_T, HZ_IMP_PARTYSITES_T

AddressContactPreference

Indicates the household's preference about being contacted at the primary address.

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

Reference attributes: CpOrigSystem, CpOrigSystemReference.

HZ_IMP_CONTACTPREFS _Reference

AddressPurpose

Indicates the purpose of a household's address.

Sample attributes: SiteUseType, EndDate, and StartDate.

Reference attributes: SiteOrigSystem and SiteOrigSystemReference.

HZ_IMP_PARTYSITEUSES_T

Import Legal Entities Using File-Based Import

Importing Legal Entities: Explained

You can import legal entity data from an external data source into CX Sales and B2B Service using the File-Based Data Import feature.

Consider the following questions when importing your data:

  • How does your legacy or source system store and represent the legal entity information when compared to CX Sales and B2B Service?

  • Do you have to configure values in CX Sales and B2B Service to map your existing data values to the Legal Entity import object?

  • Do you have to extend CX Sales and B2B Service to add attributes?

  • What import features are available to import your business data?

  • How do I verify my imported data?

How Business Objects Are Structured

You must understand how your legal entity data corresponds with the data in CX Sales and B2B Service to map your legacy data to the data in CX Sales and B2B Service.

The Legal Entity object is hierarchical. Ensure that an legal entity exists before you can import its child objects, such as classifications and contacts. These child objects can in turn consist of other objects. You use this structure to support one-to-many relationships between the objects that make up the legal entity.

This image shows the legal entity and its child entities.

Legal entity import object structure

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

  • Additional names

Note: All contact-related entities, such as primary phone or e-mail, include a child entity that captures the contact preference. For example, the Primary Phone Contact Preference entity saves the contact preference of the legal entity for the contact method primary phone.

The contact of the legal entity includes other child entities with information about the contact, such as:

  • Contact job

  • Contact primary phone

  • Contact primary address

  • Contact e-mail address

How Business Object Attributes Are Structured

Every import object is a collection of attributes that help to map your data to the Oracle Applications Cloud data and to support one-to-many relationships between the structural components of an legal entity.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for CX Sales and Service) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Legal Entity Import Objects Work Together.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import Legal Entities Using File-Based Data Import

You must first prepare a source data file to import legal entities. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You can also access these tasks from the Data Import and Export functional area of the Sales offering.

You submit file import activities for each import object. When you're creating a new legal entity, you use the Legal Entity object to import your data. You must have the Customer Relationship Management Application Administrator job role to access and submit the import activities for legal entities.

When importing legal entity information, you import:

  1. the basic legal entity profile information

  2. the child entities for the legal entity

When importing child objects, you must provide the parent reference information for all parent levels of the object. For example, you:

  1. import basic profile details, such as customer name, party type, and party usage

  2. import contacts and contact information, such as phone, address, contact points, and fax for the legal entity

  3. provide the PartyOrigSystem and PartyOrigSystemReference of the legal entity when importing contacts for the legal entity

PartyOrigSystem is the source system code that identifies the source of the information. PartyOrigSystemReference is unique for each row of data within an import job, and is a combination of PartyOrigSystem and a unique reference. When importing contact information for an legal entity, you must provide the relationship reference information. This information is required, as contacts can have multiple relationships with legal entities.

How You Verify 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, navigate to the following in the Setup and Maintenance work area to view the legal entities that you have imported:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Define Legal Entities

How Legal Entity Import Objects Work Together

You use the legal entity import object to import legal entities and objects related to the legal entity. This topic describes the legal entity import object and introduces:

  • Target objects

  • Target import object attributes

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

Overview of Legal Entity Target Import Objects

The Legal Entity import object imports legal entity information and its contacts. The Legal Entity import object is split into separate target import objects for organizing the individual attributes of the legal entity and its contact.

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

When updating an existing legal entity with more information, you must provide the parent reference information for the existing legal entity. When importing contacts or contact information for a legal entity, you must provide relationship reference information in addition to the parent reference. This information is required because a contact can have multiple relationships with the legal entity. When importing information about a contact, you must refer to the specific relationship you want to import information for. For example, you might want to import information about John Smith the employee or John Smith the board member. If you don't 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.

Legal Entity Target Import Object Attributes

You must compare the attributes that you want to import with the target object attributes that are available and with their valid values. To evaluate your source data and CX Sales and B2B Service attributes for mapping and validation, you use a reference file. See the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/index.html). In the File-Based Data Imports chapter, see the topic for your import object of interest, which includes links to reference files for target import objects. A reference guide file includes attribute descriptions, default values, and validations performed by the import process. Review the validation for each attribute to determine whether there are functional prerequisites or prerequisite setup tasks that are required.

To import your source file data, you define a mapping between your source file data and the combination of the target object and target object attribute. You can predefine and manage import mappings. Do one of the following:

  1. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when you define the import activity. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note: If any of the attributes you want to import don't have an equivalent target object attribute, then review the Composer configuration features for the object.

Reference Files for Legal Entity Target Import Object Attributes

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Here is a list of reference files and their target import objects.

Target Import Object Description Reference File Name

OrganizationProfile

Detailed legal entity information, such as, organization name and organization type.

HZ_IMP_PARTIES_T_Reference

PrimaryPhone

Primary phone number of the legal entity. If the legal entity has multiple phone numbers, one of the phone numbers is designated as the primary phone number.

HZ_IMP_CONTACTPTS_T_Reference

Fax

Fax of the legal entity.

HZ_IMP_CONTACTPTS_T_Reference

Url

Url of the legal entity.

HZ_IMP_CONTACTPTS_T_Reference

AdditionalName

Alternative name of a legal entity.

HZ_IMP_ADDTNLPARTYNAMES_T_Reference

Classification

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

HZ_IMP_CLASSIFICS_T_Reference

PrimaryAddress

Primary address of a legal entity. If the contact has multiple addresses, one of the addresses is designated as the primary address.

HZ_IMP_PARTYSITES_T_Reference

ContactPersonProfile

Detailed information of a legal entity contact, such as, person name, relationship type, and marital status.

HZ_IMP_RELSHIPS_T_Reference

ContactEmail

E-mail of the legal entity contact.

HZ_IMP_CONTACTPTS_T_Reference

ContactFax

Fax of the legal entity contact.

HZ_IMP_CONTACTPTS_T_Reference

ContactInstantMessenger

Instant messenger or social networking information of a legal entity contact.

HZ_IMP_CONTACTPTS_T_Reference

ContactJob

Job information of a legal entity contact.

HZ_IMP_CONTACTS_T_Reference

ContactMobile

Mobile number of a legal entity's contact.

HZ_IMP_CONTACTPTS_T_Reference

ContactPrimaryAddress

Primary address of a legal entity contact. If the contact has multiple addresses, one of the addresses is designated as the primary address.

HZ_IMP_PARTYSITES_T_Reference

ContactPrimaryPhone

Primary phone number of the legal entity contact. If the legal entity has multiple phone numbers, one of the phone numbers is designated as the primary phone number.

HZ_IMP_CONTACTPTS_T_Reference

ContactAdditionalName

Alternative name of a legal entity contact.

HZ_IMP_ADDTNLPARTYNAMES_T_Reference

PrimaryPhoneContactPreference

The legal entity's preference about being contacted through phone.

HZ_IMP_CONTACTPREFS_Reference

MobileContactPreference

The legal entity's preference about being contacted through mobile.

HZ_IMP_CONTACTPREFS_Reference

FaxContactPreference

The legal entity's preference about being contacted through fax.

HZ_IMP_CONTACTPREFS_Reference

EmailContactPreference

The legal entity's preference about being contacted through e-mail.

HZ_IMP_CONTACTPREFS_Reference

ContactPrimaryAddressContactPreference

The legal entity contact's preference about being contacted at the primary address.

HZ_IMP_CONTACTPREFS_Reference

ContactPrimaryPhoneContactPreference

The legal entity contact's preference about being contacted through the primary phone number.

HZ_IMP_CONTACTPREFS_Reference

PrimaryAddressContactPreference

The legal entity's preference about being contacted at the primary address.

HZ_IMP_CONTACTPREFS_Reference

PrimaryPhoneContactPreference

The legal entity's preference about being contacted through the primary phone number.

HZ_IMP_CONTACTPREFS_Reference

Note: CX Sales and B2B Service supports the ContactPersonProfile target object. However, the object is now deprecated. For updating any contact information, use the PersonProfile target object instead.

Import Resource Teams Using File-Based Import

Importing Resource Teams: Explained

You can import resource team data from an external data source into CX Sales and B2B Service using the File-Based Data Import feature. A resource team is a temporary group of resources that's formed to work on work objects. A resource team may contain a resource organization or resources or both. You can't structure a resource team hierarchically and implement it in an organization. You enter your resource team information.

Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Resource Teams

Alternatively, 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 or source system store and represent the resource team information when compared to CX Sales and B2B Service?

  • Do you have to configure values in CX Sales and B2B Service to map your existing data to the Resource Team import object?

  • Do you have to extend CX Sales and B2B Service to add attributes?

  • What import features are available to import your business data?

  • How do I verify my imported data?

How Business Objects are Structured

You must understand how your resource team data corresponds with the data in CX Sales and B2B Service to map your legacy data to the data in CX Sales and B2B Service. The Resource Team object is hierarchical.

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.

How Business Object Attributes Are Structured

Every import object is a collection of attributes that help to map your data to the Oracle Applications Cloud data and to support one-to-many relationships between the structural components of a resource team.

You must know the attribute details of the import objects so that you can prepare your import data. You can use the import reference guide (File-Based Data Import for CX Sales and B2B Service) files that contain:

  • Attribute descriptions

  • Values that populate attributes by default when you don't provide values

  • Validation information for each attribute

The validation information includes the navigation path to the task where you can define values in Oracle Application Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the validation information provides the task name where you can define your values. For additional information, such as a list of reference guide file names and locations, see the topic How Resource Team Import Objects Work Together. This table lists the import object and the related import object topic.

Import Object Related Import Object Topic

Resource Team

Resource Team Import Objects: How They Work Together

Note:

You can use the keyword importing resource teams to search for related topics in CX Sales and B2B Service help.

Configurable Attributes

Here is how you can configure the objects to import your legacy or source data:

  • Use the Application Composer to design your object model extensions and to generate the required artifacts to register your extensions.

  • Make the artifacts available for importing the object.

You can map these configurable attributes to your source file data. You can use the same source file to import both the configurable attributes and the standard import object attributes.

How You Import Resource Teams Using File-Based Data Import

You must first prepare a source data file to import accounts. The source file can be either an XML file or a text file, such as a CSV files.

You use the file import process to:

  1. Read the data in your source file.

  2. Populate the interface tables according to your mapping.

  3. Import the data into the application destination tables.

The Define File Import Setup and Maintenance task list includes the tasks required to:

  • Configure the import objects

  • Create source-file mappings

  • Schedule the import activities

You can also access these tasks from the Data Import and Export functional area of the Sales offering.

You submit file import activities for each import object. When you're creating a new resource team, you use the Resource Team object to import your data. You must have the Master Data Management Administrator job role to access and submit the import activities for resource teams.

How You Verify Your Imported Data

You can use the File Import activity reports to verify imported data. Alternatively, you can also navigate to the Team Resources work area to view the team resource information that you have imported.

How Resource Team Import Objects Work Together

You use the ResourceTeam and ResourceTeamUsage import objects to import resource teams and objects related to the resource teams. This topic describes the Resource Team import object and introduces:

  • Target objects

  • Target import object attributes

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

Overview of Resource Team Target Import Objects

Use the Resource Team and Resource Team Usage import objects to import resource teams and objects related to resource teams. The Resource Team import object is split into smaller objects to organize the individual attributes of the resource team. The Resource Team Usage import object is split into smaller objects to organize the individual attributes of the resource team usage.

The target import objects in the Resource Team import object are grouped into information about the resource team and information about the other objects. The target import objects in the Resource Team Usage import object are grouped into information about the resource team usage and information about the other objects.

Resource Team Target Import Object Attributes

Compare attributes that you want to import with the available target object attributes and their valid values. Use a reference file to evaluate your source data and CX Sales and B2B Service attributes for mapping and validation. See the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. A reference guide file includes:

  • Attribute descriptions

  • Default values

  • Validations for the attributes

Review the validation for each attribute to know if you need to do any setup tasks.

Define and Manage Import Mappings

You must define a mapping between your source data and a combination of the target object and target object attributes to import your source file data. To define and manage import mappings, do one of these:

  1. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Mappings

  2. Define the mapping when you define the import activity. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage File Import Activities

Note:

If any of your source attributes doesn't have a corresponding target object attribute, then you can extend the Resource Team and Resource Team Usage objects. Review the Application Composer Extensibility features for the Resource Team and Resource Team Usage objects for more information.

Reference Files for Resource Team Target Import Object Attributes

To access reference files for this object's target import objects, see the File-Based Data Import for CX Sales and B2B Service guide (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Here is a list of reference files and their target import objects.

Target Import Object Description Reference File Names

ResourceTeam

Captured information that identifies a resource team.

HZ_IMP_TEAMS _Reference

ResourceTeamUsage

Contains information that indicates the usage of the resource team.

HZ_IMP_TEAM_USAGES_Reference

Import Common Supporting Objects

Importing Additional Party Identifiers: Quick Start

You can use the information in this topic to import additional party identifiers. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

Using an additional party identifier, you can save other identifiers for an account, contact, or household. For example, a person may have a driving license as the identifier in a record, and passport as the identifier in another record. You can import new additional identifiers or update existing additional identifier records, using the File-Based Data Import feature. For example, an airline company may have an International Air Transport Association code and the D-U-N-S number as identifiers.

Use the file-based import objects and target objects in this table to import additional party identifiers.

Import Object Party Type Target Object

Account

Organization

AdditionalIdentifier

Contact

Person

AdditionalIdentifier

Household

Household

AdditionalIdentifier

Identify and Associate Records with Each Other

To add or update an additional identifier using file-based import, your source file must contain information about the party to which the additional identifier belongs. You map your source file data to the additional identifier target object.

If you're creating the party and the additional identifier in the same import activity, then the party and the additional identifier should be grouped in your source file. The import process imports the additional identifier and then identifies the additional identifier record so that it can import the associated additional identifier.

To add or update an additional identifier, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process uses the combination of source system and source system reference value to identify the existing record.

Before You Start

The minimum data required to import additional identifier information depends on:

  • The purpose of the import. The data is different when you create both the party and the additional identifier in the same import batch, add new additional identifier to an existing party, or update an additional identifier record.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update an additional identifier and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Additional Party Identifier Records in the Same Batch Creating Additional Party Identifier Record for an Existing Party

AdditionalPartyI dOrigSystem

The code representing the source system for the additional identifier.

When you predefine your source system code, navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

  • Select the Enabled for Trading Community Members check box.

Conditionally required

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values

Conditionally required

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values

AdditionalPartyI dOrigSystemReference

The reference number or text representing the source system unique ID for the additional identifier.

Identify or generate reference values for each additional party identifier record. The reference value must be unique for all additional party identifiers for the source system.

Conditionally required

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values

Conditionally required

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values

ObjectKey

The internal ID for the additional identifier.

Identify the additional party identifier value by exporting the Additional Party identifier object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

PartyId

The internal ID for the party (account, contact, household, or legal entity) to which the additional identifier belongs.

Identify the party ID value by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID)

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

PartyOrigSystem

The code representing the source system for the party (account, contact, household, or legal entity) to which the additional identifier belongs.

Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this additional party identifier.

Required

Conditionally required

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID)

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

PartyOrigSystem Reference

The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the additional identifier belongs.

Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this additional party identifier.

Required

Conditionally required

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (record ID)

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

AdditionalPartyI dentifierType

The identifier type to categorize the identifier.

Identify additional identifier types for the party type. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Additional Identifier Types

Required

Required

AdditionalPartyI dentifierValue

The additional identifier value for a party.

No prerequisite tasks

Required

Required

IssuingAuthority Name

The name of the authority that issued the additional identifier.

No prerequisite tasks

Required, if you're not providing the Issue Authority Party ID.

The attribute is neither required nor conditionally required.

IssuingAuthority PartyId

The party ID of the issuing authority.

Identify the party ID value. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Additional Identifier Types

Required, if you're not providing the Issue Authority Party Name.

The attribute is neither required nor conditionally required.

Note: Oracle recommends that you include the issue date and expiry date for identifiers that become invalid after the expiry date, such as passport and driving license.

This image shows a sample attribute mapping to import a new additional identifier for an existing organization. In this scenario, you use origin system and origin system reference information to identify the existing party and the new additional identifier.

Sample import mapping to create new additional
identifier

This image shows a sample attribute mapping to update an existing additional identifier. In this scenario, you use the origin system reference information to identify the additional identifier and update its description.

Sample import mapping to update an existing additional
identifier

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in the Help Application search.

  • Importing contacts

  • Importing accounts

  • Importing households

Tip: The Identifier Type is defined for particular party types and for uniqueness. For example, when importing an organization profile, the identifier type must allow assignment to the organization party type. You can also specify the value of an identifier type must be unique. For example, you can define that the passport number listed for each person must be unique.

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference values might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

Importing Additional Party Names: Quick Start

You can use the information in this topic to import additional party names. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

Using an additional party name, you can save other names for an account, contact, household, or legal entity. For example, a person may have a maiden name, and an organization may also be known by a brand name. You can import new additional names or update existing additional name records, using the File-Based Data Import feature. This table lists the file-based import objects and target objects. You can import additional names, using these file-based objects.

Import Object Party Type Target Object

Contact

Person

AdditionalName

Account

Organization

AdditionalName

Contact

Person (a contact for an account)

AdditionalName

Household

Group

AdditionalName

Legal Entity

Organization

AdditionalName

Legal Entity

Person (a contact for a legal entity)

ContactAdditionalName

Identify and Associate Records with Each Other

To add or update an additional name using file-based import, your source file must contain information about the party to which the additional name belongs. You map your source file data to the additional name target object.

If you're creating the party and the additional party name assignment in the same import activity, then the party and the additional party name data should be grouped in your source file. The import process imports the additional party name and then identifies the additional party name record so that it can import the associated additional party name.

To add or update an additional party name, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process uses the combination of source system and source system reference value to identify the existing record.

Before You Start

The minimum data required to import additional name information depends on:

  • The purpose of the import. The data is different when you create both the party and the additional party name in the same import batch, add new additional party name to an existing party, or update an additional party name record.

  • Organization and group names compared with person names. Different components that make up a person's name aren't used for organization and group names.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update an additional party name and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Additional Party Name Records in the Same Batch Creating Additional Party Name Record for an Existing Party

PartyId

The internal ID for the party (account, contact, household, or legal entity) to which the additional party name belongs.

Identify the party ID value by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

PartyOrigSystem

The code representing the source system for the party (account, contact, household, or legal entity) to which the additional party name belongs.

Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this additional party name.

Conditionally required.

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

PartyOrigSystem Reference

The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the additional party name belongs.

Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this additional party name.

Conditionally required.

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update an additional party name and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Additional Party Name Records in the Same Batch Creating Additional Party Name Record for an Existing Party

AdditionalName OrigSystem

The code representing the source system for the additional name.

When you predefine your source system code, navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

  • Select the Enabled for Trading Community Members check box.

Conditionally required.

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.

Conditionally required.

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.

AdditionalName

The reference number or text representing the source system unique ID for the additional name.

Identify or generate reference values for each additional party name record. The reference value must be unique for all additional party names for the source system.

Conditionally required.

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.

Conditionally required.

If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.

ObjectKey

The internal ID for the additional name.

Identify the additional party name ID value by exporting the Additional Party Name object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

NameType

The name type to categorize the name.

Review or define the name types for each party type (person, organization, or household). Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Additional Name Types

Required

Required

Name

The additional name value for an organization or group.

No prerequisite tasks

Required

Required

This image depicts a sample attribute mapping to import an additional name for an existing party. In this scenario, you use the OrigSystem and OrigSystemReference values to identify the party.

Sample import mapping for Additional Name object

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in the Help Application.

  • Importing additional party names

  • Importing accounts

  • Importing contacts

  • Importing households

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

Tip: The Name Type is defined for particular party types. For example, if you're importing an organization profile, ensure that the name type definition allows assignment to the Organization party type.

Importing Addresses: Quick Start

You can use the information in this topic to import addresses. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

You use an address to save detailed location information for an account, contact, household, employee resource, and legal entity. For example, a person may have residential and official addresses, and an organization may have different billing and shipping addresses. You can import new addresses or update existing address records, using the File-Based Data Import feature.

Use the file-based import objects and target objects in this table to import addresses.

Import Object Party Type Target Object

Account

Organization

Address, SellToAddress

Account

Person (a contact for a account)

Address, ContactPrimaryAddress

Household

Household

Address

Legal Entity

Organization

PrimaryAddress

Legal Entity

Person (a contact for a legal entity)

ContactPrimaryAddress

Employee Resource

Person

PrimaryAddress

Contact

Person

Address, ContactAddress

Lead

Lead Consumer

PersonAddress

Lead

Lead Contact

ContactPrimaryAddress

Partner

Organization

PrimaryAddress

Partner Contact

Person

PrimaryAddress

Campaign Response

Organization

OrganizationAddress

Campaign Response

Consumer Respondent

PersonAddress

Campaign Response

Campaign Response Contact

ContactPrimaryAddress

Identify and Associate Records with Each Other

To add or update an address using file-based import, your source file must contain information about the account, contact, or household party to which the address belongs. You map your source file data to the account, contact, or household profile target object and to the address target object.

If you're creating the party and the address assignment in the same import activity, then the party and the address data should be grouped in your source file. The import process imports the address and then identifies the address record so that it can import the associated address.

To add or update an address, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process uses the combination of source system and source system reference value to identify the existing record.

You can use external IDs or business keys to identify and associate records with each other when you're importing a smaller set of records. Business keys are attributes that uniquely identify a party record. For example, a person's last name and first name uniquely identify a person. An external ID is a unique record identifier from an application outside of CX Sales and B2B Service. You can use the following business keys or external IDs in CX Sales and B2B Service:

  • Organization name for organizations

  • First name and last name for persons

  • Contact information, which is a combination of e-mail Id, mobile number, IM, and URL.

  • Address information, which is a combination of address1, address2, city, and postal code.

You can extend source systems to identify the source of the data. You use source systems that are external sources of data to import data into Oracle Application Cloud. Oracle Application Cloud uses source system references to create references between source IDs and the Oracle Application Cloud database IDs. You can extend source systems in one of these ways:

  • Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  • Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

Before You Start

The minimum data required to import address information depends on:

  • The purpose of the import. The data is different when you create both the party and the address in the same import batch, add new address to an existing party, or update an address record.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update an address and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Adding Address in the Same Batch Adding Address to an Existing Party Updating Existing Addresses

PartyId

The internal ID for the party (account, contact, household, or legal entity) to which the address belongs.

Identify the party ID value by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address.

PartyOrigSystem

The code representing the source system for the party (account, contact, household, or legal entity) to which the address belongs.

Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this address.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address.

PartyOrigSystem Reference

The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the address belongs.

Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this address.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address.

Country

The country code component of the postal address.

Identify valid country codes. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Territories

Required

Required

The attribute is neither required nor conditionally required.

LocationId1

The unique ID for the existing location record in the destination table.

Identify the LOCATION_ID for an existing location by exporting the Location object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • LocationOrigSystem1 and LocationOrigSystemReference1 (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address.

LocationOrigSystem1

A source system code that identifies the original source system of the location.

Identify the source system code that was used when you imported the location in a prior batch, or identify the source system code you will use when importing the location in the same batch as this party relationship to the location.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • LocationOrigSystem1 and LocationOrigSystemReference1 (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address.

LocationOrigSystem Reference1

Original System Reference for Location: A source system reference that identifies the unique ID of the location in your legacy or external system.

Identify the source system reference that was used when you imported the location in a prior batch, or identify the source system code you will use when importing the location in the same batch as this party relationship to the location.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • LocationOrigSystem1 and LocationOrigSystemReference1 (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address.

TransliterationLang

The language considered as the local language for the location.

Identify valid language codes. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage ISO Languages

A value is required if you're providing address elements in a translated language.

A value is required if you're providing address elements in a translated language.

A value is required if you're providing address elements in a translated language.

Identifying AddressFlag

Indicates that an address is the primary address for a party.

No prerequisite tasks.

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

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

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

RelationshipId

The unique identifier for the existing party relationship record in the destination table. The relationship is between two parties, such as an organization and an organization's contact. You provide the relationship if the context of the address association is for a relationship.

Identify the relationship ID for an existing relationship by exporting the Relationship and Organization Contact objects. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

A value is required if you're adding an address association to an existing party relationship or updating an existing address association record for a relationship, and you're not providing the relationship's source system reference (RelOrigSystemReference) and the source system code (RelOrigSystem).

A value is required if you're adding an address association to an existing party relationship or updating an existing address association record for a relationship, and you're not providing the relationship's source system reference (RelOrigSystemReference) and the source system code (RelOrigSystem).

A value is required if you're adding an address association to an existing party relationship or updating an existing address association record for a relationship, and you're not providing the relationship's source system reference (RelOrigSystemReference) and the source system code (RelOrigSystem).

RelOrigSystem

The source system code that identifies the original source system of the party relationship.

No prerequisite tasks.

A value is required if you're adding an address association to an existing party relationship and you're not providing the relationship ID, or if you're importing the relationship in the same import batch and you're using the source system reference and source system code to relate the source file data.

A value is required if you're adding an address association to an existing party relationship and you're not providing the relationship ID, or if you're importing the relationship in the same import batch and you're using the source system reference and source system code to relate the source file data.

A value is required if you're adding an address association to an existing party relationship and you're not providing the relationship ID, or if you're importing the relationship in the same import batch and you're using the source system reference and source system code to relate the source file data.

RelOrigSystem Reference

The ID that identifies the party relationship in your legacy or external system.

No prerequisite tasks.

A value is required if you're adding an address association to an existing party relationship and you're not providing the relationship ID, or if you're importing the relationship in the same import batch and you're using the source system reference and source system code to relate the source file data.

A value is required if you're adding an address association to an existing party relationship and you're not providing the relationship ID, or if you're importing the relationship in the same import batch and you're using the source system reference and source system code to relate the source file data.

A value is required if you're adding an address association to an existing party relationship and you're not providing the relationship ID, or if you're importing the relationship in the same import batch and you're using the source system reference and source system code to relate the source file data.

ResourceEmail Address

The employee resource's e-mail.

Identify the e-mail ID for an existing resource using the Resource Directory. Do one of the following:

  1. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Manage Resources

  2. You can also obtain the e-mail address by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Manage Bulk Data Export, Schedule Export Processes

A value is required if you're importing the employee resource in the same batch as this address association and are using the e-mail address to relate the source file data.

A value is required if you're importing the employee resource in the same batch as this address association and are using the e-mail address to relate the source file data.

A value is required if you're updating the employee resource in the same batch as this address association and are using the e-mail address to relate the source file data.

SiteOrigSystem

A source system code that identifies the original source system of the address association (party site).

No prerequisite tasks.

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

A value is required if you're updating a previously imported address association, where you provided a SiteOrigSystem value, and you're not providing the address association ID (ObjectKey), or if you're importing associated objects, such as contact preferences and site uses, and are using the source system reference and source system code to relate the source file data

SiteOrigSystem Reference

A source system reference that identifies the unique ID of the address association (party site) in your legacy or external system.

No prerequisite tasks.

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

A value is required if you're updating a previously imported address association, where you provided a SiteOrigSystem value, and you're not providing the address association ID (ObjectKey), or if you're importing associated objects, such as contact preferences and site uses, and are using the source system reference and source system code to relate the source file data

ObjectKey

The unique ID for the existing address association record (party site) in the destination table.

Identify the party site ID for an existing address association by exporting the Party Site object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

A value is required if you're updating an existing address association and aren't providing the source system reference and source system code (SiteOrigSystemReference and SiteOrigSystem).

There are four sets of reference information that you can use to refer to a record. However, you must use only one of them to refer to a record; else, the import process would result in an error. The import process recognizes reference information in this order:

  1. IDs such as PartyId, ObjectKey, ad so on.

  2. Public User ID such as organization name, contact name, ad so on.

  3. Origin system and origin system reference

  4. Other reference information such as business keys.

This image depicts a sample attribute mapping to import an address for an existing party. In this scenario, you use the OrigSystem and OrigSystemReference values to identify the party.

Sample import mapping for Address object

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in CX Sales and B2B Service Help Application search. You can access help from any CX Sales and B2B Service page by clicking Help and selecting Applications Help.

  • Importing addresses

  • Importing location information

  • Importing contacts

  • Importing accounts

  • Importing households

  • Importing legal entities

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

Importing Address Purposes: Quick Start

You can use the information in this topic to import address purposes. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

You use an address purpose to save functions performed by each address. For example, assign the bill-to address purpose to account sites designated to receive and process bills. Similarly, assign the ship-to address purpose to account sites designated to receive goods purchased by the customer account.

Use the file-based import objects and target objects in this table to import address purposes.

Import Object Party Type Target Object

Contact

Person

ContactAddressPurpose

Account

Organization

AddressPurpose

Account

Person (a contact for an account)

ContactAddressPurpose

Household

Household

AddressPurpose

Household

Person (a contact for a household)

ContactAddressPurpose

Campaign Response

Consumer Respondent

AddressPurpose

Campaign Response

Campaign Response Contact

ContactAddressPurpose

Legal Entity

Organization

AddressPurpose

Legal Entity

Person (a contact for a legal entity)

ContactAddressPurpose

Lead

Lead Consumer

AddressPurpose

Lead

Lead Contact

ContactAddressPurpose

Partner

Organization

AddressPurpose

Identify and Associate Records with Each Other

To add or update an address purpose using file-based import, your source file must contain information about the party to which the address purpose belongs. You map your source file data to the account, contact, or household profile target object and to the address purpose target object.

If you're creating the address and the address purpose assignment in the same import activity, then the address and the address purpose data should be grouped in your source file. The import process imports the address purpose and then identifies the address purpose record so that it can import the associated address purpose.

To add or update an address purpose, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process uses the combination of source system and source system reference value to identify the existing record.

You can use external IDs or business keys to identify and associate records with each other when you're importing a smaller set of records. Business keys are attributes that uniquely identify a party record. For example, a person's last name and first name uniquely identify a person. An external ID is a unique record identifier from an application outside of CX Sales and B2B Service. You can use the following business keys or external IDs in CX Sales and B2B Service:

  • Organization name for organizations

  • First name and last name for persons

  • Contact information, which is a combination of e-mail Id, mobile number, IM, and URL.

  • Address information, which is a combination of address1, address2, city, and postal code.

You can extend source systems to identify the source of the data. You use source systems that are external sources of data to import data into Oracle Application Cloud. Oracle Application Cloud uses source system references to create references between source IDs and the Oracle Application Cloud database IDs. You can extend source systems in one of these ways

  • Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  • Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

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

Before You Start

The minimum data required to import address purpose information depends on:

  • The purpose of the import. The data is different when you create both the address and the address purpose in the same import batch, add new address to an existing address purpose, or update an address purpose record.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update an address purpose and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Adding Address Purpose in the Same Batch Adding Address Purpose to an Existing Party Updating Existing Address Purposes

PartyId

The internal ID for the party (account, contact, household, or legal entity) to which the address belongs.

Identify the party ID value by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Required

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

PartyOrigSystem

The code representing the source system for the party (account, contact, household, or legal entity) to which the address belongs.

Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this address.

Conditionally required

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

PartyOrigSystem Reference

The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the address purpose belongs.

Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this additional party name.

Conditionally required

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

SiteUseType

The lookup code that represents the purpose for the address association.

Identify the site use type. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Location Lookups

Required

Required

Required

PartySiteId

The unique ID for the existing address association record (party site) in the destination table. The party site represents the association of a physical location to an organization, person, or to a relationship between two parties, such as an organization's contact.

Identify the party site ID for an existing address association by exporting the Party Site object Navigate to the following in the Setup and Maintenance work area:.

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • SiteuseOrigSystem and SiteuseNameOrigSystemRef (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

SiteOrigSystem

A source system code that identifies the original source system of the address association (party site). The party site represents the association of a physical location to an organization, person, or to a relationship between two parties, such as an organization's contact.

Identify the source system code that was used when you imported the address in a prior batch, or identify the source system code that you will use when importing the address in the same batch as this address purpose.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • SiteuseOrigSystem and SiteuseNameOrigSystemRef (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

SiteOrigSystem Reference

A source system reference that identifies the unique ID of the address association (party site) in your legacy or external system. The party site represents the association of a physical location to an organization, person, or to a relationship between two parties, such as an organization's contact.

Identify the reference value from your source system that was used when you imported the address in a prior batch, or identify the source system reference that you will use when importing the address in the same batch as this address purpose.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • SiteuseOrigSystem and SiteuseNameOrigSystemRef (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

SiteuseOrigSystem

A source system code that identifies the original source system of the party's address purpose.

Identify the source system code that was used when you imported the address purpose in a prior batch, or identify the source system code that you will use when importing the address purpose in the same batch as this address purpose.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • SiteuseOrigSystem and SiteuseNameOrigSystemRef (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

SiteuseOrigSystem Reference

A source system reference that identifies the unique ID of the party's address purpose in your legacy or external system.

Identify the reference value from your source system that was used when you imported the address purpose in a prior batch, or identify the source system reference that you will use when importing the address purpose in the same batch as this address purpose.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • SiteuseOrigSystem and SiteuseNameOrigSystemRef (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

ObjectKey, PartySiteUseId

The unique ID for the existing address purpose record in the destination table.

No prerequisite tasks.

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • SiteuseOrigSystem and SiteuseNameOrigSystemRef (source system code and source system reference values) provided when importing the organization profile.

  • A business key that's a combination of PARTY_SITE_ID, SITE_USE_TYPE, START_DATE, and END_DATE range.

There are four sets of reference information that you can use to refer to a record. However, you must use only one of them to refer to a record; else, the import process would result in an error. The import process recognizes reference information in this order:

  1. IDs such as PartyId, ObjectKey, and so on.

  2. Public User ID such as organization name, contact name, and so on.

  3. Origin system and origin system reference

  4. Other reference information such as business keys.

This image depicts a sample attribute mapping to import an address purpose for an existing party. In this scenario, you use the OrigSystem and OrigSystemReference values to identify the party.

Sample import mapping for Address Purpose object

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in CX Sales and B2B Service Help Application search. You can access help from any CX Sales and B2B Service page by clicking Help and selecting Applications Help.

  • Importing addresses

  • Importing address purposes

  • Importing accounts

  • Importing contacts

  • Importing households

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

Importing Classifications: Quick Start

You can use the information in this topic to import classifications. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

You use classifications to categorize entities, such as organizations, persons, and households. You define various classification categories, eligibility rules, and the classification values. For example, you define a classification category for parties interested in renewable energy types, including a solar energy classification value. Another classification category represents industries, such as automotive and banking. You can classify a party as interested in solar energy and conducts business in the automotive industry.

Use the file-based import objects and target objects in this table to import classifications.

Import Object Party Type Target Object

Account

Organization

Classification

Legal Entity

Organization

Classification

Contact

Person

Classification

Consumer

Organization

Classification

Household

Household

Classification

Identify and Associate Records with Each Other

To add or update classifications using file-based import, your source file must contain information about the party to which the classification belongs. You map your source file data to the classification target object.

If you're creating the party and the classification assignment in the same import activity, then the party and the classification assignment data should be grouped in your source file. The import process imports the party and then identifies the party record so that it can import the associated classifications.

To add or update a classification, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process uses the combination of source system and source system reference value to identify the existing record.

Before You Start

The minimum data required to import classification information depends on:

  • The purpose of the import. The data is different when you create both the party and the classification in the same import batch, add new classifications to an existing party, or update a classification record.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update a classification and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Classification Records in the Same Batch Creating Classification Record for an Existing Party

PartyId

The internal ID for the party (account, consumer, contact, household, or legal entity) to which the classification belongs.

Identify the party ID value by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

Conditionally required

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Business keys such as class_category and class_code.

PartyOrigSystem

The code representing the source system for the party (account, consumer, contact, household, or legal entity) to which the classification belongs.

Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code you will use when importing the party in the same batch as this classification.

Conditionally required

If the source of your data is a third party or external system, and if you intend to import updates to previously imported records from the same system, then provide the original source system and source system reference values.

Conditionally required

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Business keys such as class_category and class_code.

PartyOrigSystem Reference

The reference number or text representing the source system unique ID for the party (account, consumer, contact, household, or legal entity) to which the classification belongs.

Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference you will use when importing the party in the same batch as this classification.

Conditionally required

If the source of your data is a third party or external system, and if you intend to import updates to previously imported records from the same system, then provide the original source system and source system reference values.

Conditionally required

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Business keys such as class_category and class_code.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update a classification and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Classification Records in the Same Batch Creating Classification Record for an Existing Party

ClassificationOrigSystem

The code representing the source system for the classification.

When you predefine your source system code, navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

  • Select the Enabled for Trading Community Members check box.

Conditionally required

If the source of your data is a third party or external system, and if you intend to import updates to previously imported records from the same system, then provide the original source system and source system reference values.

Conditionally required

If the source of your data is a third party or external system, and if you intend to import updates to previously imported records from the same system, then provide the original source system and source system reference values.

ClassificationOri gSystemReference

The reference value for the classification record in the external source system.

Identify or generate reference values for each party classification association record. The reference value must be unique for all party classification associations for the source system.

Conditionally required

If the source of your data is a third party or external system, and if you intend to import updates to previously imported records from the same system, then provide the original source system and source system reference values.

Conditionally required

If the source of your data is a third party or external system, and if you intend to import updates to previously imported records from the same system, then provide the original source system and source system reference values.

ObjectKey

The internal ID for the party classification association.

Identify the party classification association ID by exporting the Classification Assignment object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

ClassificationCode

The classification code within classification category.

The code should be valid for the classification category. Review the classification codes valid for each classification category. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Classification Categories

Required

Required

ClassificationCategory

The classification category.

Identify the classification category name and review the entity assignment rules. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Classification Categories

Required

Required

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

  1. IDs such as PartyId, ObjectKey, and so on.

  2. Public User ID such as PartyNumber (also called RegistryID), PartySiteNumber, and so on.

  3. Origin system and Origin system reference

  4. Other reference information such as business keys

This image shows a sample attributes mapping to import a new classification for an existing organization. In this scenario, you use the origin system and origin system reference information to identify the new classification and the existing organization.

Sample import mapping to create classifications

This image shows a sample attribute mapping to update an existing classification of an existing organization, by providing origin system and origin system reference information.

Sample import mapping to update classifications

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in the CX Sales and B2B Service Help Application search.

  • Importing contacts

  • Importing accounts

  • Importing households

  • Importing legal entities

  • Importing classification codes

Review the entity assignment rules for the classification category to verify whether the import object meets the assignment criteria.

If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference values might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

Importing Contact Points: Quick Start

You can use the information in this topic to import contact points. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

You can import new contact points or update existing contact points, using the File-Based Data Import feature.

Note: You can associate addresses with persons and organizations, although contact points don't formally include addresses.

Use the file-based import objects and target objects in this table to import contact points.

Import Object Party Type Target Objects for Importing Contact Points

Contact

Person

Email, Fax, InstantMessenger, Mobile, Phone, Address

Account

Organization

PrimaryPhone, Fax, Url, Address

Household

Organization

E-mail, Fax, InstantMessenger, Mobile, Phone, Address, Url

Legal Entity

Organization

Fax, PrimaryPhone, PrimaryAddress, Url

Lead

Organization (lead organization)

OrganizationProfileFax, OrganizationProfilePrimaryPhone, OrganizationAddress, Url

Lead

Person (lead individual)

Email, PersonProfileFax, InstantMessenger, Mobile, PersonAddress, PersonProfilePrimaryPhone

Lead

Person (contact at lead organization)

ContactEmail, ContactFax, ContactInstantMessenger, ContactMobile, ContactPrimaryAddress, ContactPrimaryPhone

Partner

Organization

Fax, PrimaryPhone, PrimaryAddress, Url

Partner Contact

Person (contact for a partner)

Email, Fax, InstantMessenger, Mobile, PrimaryPhone, PrimaryAddress

Campaign Response

Organization (respondent organization)

OrganizationProfileFax, OrganizationProfilePrimaryPhone, OrganizationAddress, Url

Campaign Response

Person (individual respondent)

Email, PersonProfileFax, InstantMessenger, Mobile, PersonProfilePrimaryPhone, PersonAddress

Campaign Response

Person (contact at respondent organization)

ContactEmail, ContactFax, ContactInstantMessenger, ContactMobile, ContactPrimaryAddress, ContactPrimaryPhone

Use the file-based import objects and target objects in this table to import contact points for a contact relationship.

Import Object Party Type Target Objects for Importing Contacts

Contact

Person (a contact for another root object such as account)

ContactEmail, ContactFax, ContactInstantMessenger, ContactMobile, ContactAddress, ContactPhone

Account

Person (a contact for an account)

ContactEmail, ContactFax, ContactInstantMessenger, ContactMobile, ContactPrimaryAddress, ContactPrimaryPhone

Legal Entity

Person (contact for a legal entity)

ContactEmail, ContactFax, ContactInstantMessenger, ContactMobile, ContactPrimaryAddress, ContactPrimaryPhone

Overview of Contact Points

A contact is an individual who's a customer or a prospect, or a contact for an existing customer or consumer, or a contact that doesn't yet have an established business association with a customer or consumer. Thus, a contact could be an employee of a customer organization, a person you may have met who could help with your business, or a prospective or current individual customer. The contact object contains information that identifies the contact and offers the contact points of the contact. Contact points can be geographical addresses, phone numbers, e-mail IDs, URLs, messenger IDs, and so on. The contact object also contains contact preference information for the contact.

Note: You can't share a contact point among multiple parties.

Identify and Associate Records with Each Other

To add contact to a party or to update existing contact point assignments using file-based import, your source file must contain information about the account, contact, or household party to which the contact point belongs. You map your source file data to the account, contact, or household profile target object, the relationship record that captures the interconnection between the contact and the account.

If you're creating the party and the contact point assignment in the same import activity, then group the party and contact point data together in your source file. The import process can import the party, and then identify the party record so that it can import the associated contact point.

To add a contact point to an existing party, or to update an existing contact point record, your source file must include values that enable the import process to identify the existing records. These values will be source system and source system reference value combination, an internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file. The file-based data import process stores a cross-reference between the source system information and an internal ID. The import process uses the combination of source system and source system reference value to identify the existing record.

You can use external IDs or business keys to identify and associate records with each other when you're importing a smaller set of records. Business keys are a set of attributes that uniquely identify a party record. For example, a person's last name and first name uniquely identify a person. An external ID is a unique record identifier from a system outside of the application. You can use the following business keys or external IDs in Sales and B2B Service:

  • Organization name for organizations

  • First name and last name for persons

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

  • Address information, which is a combination of address1, address2, city, and postal code.

You can extend source systems to identify the source of the data that you're importing. Source systems are external sources of data that are used to import data. Source system references are used to create references between source IDs and the database IDs. You can extend source systems in one of these ways:

  • Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  • Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

Note: You can import duplicate contact point records for the same account. When you set the user profile option name Business Key Validation Enabled to Yes, validation is performed and you can't add duplicate contact points to the same account. However, if you set this option to No, validation isn't performed and you can add duplicate contact points to the same account.

Before You Start

The minimum data required to import account profile information depends on:

  • The purpose of the import. The data requirements are different when you're creating both the party and the contact point in the same import batch, adding contact points to an existing party, or updating a contact point record.

  • Identifying and associating records. In some cases, you can choose which attributes you want to provide to the import process when identifying and associating records.

The values that you provide in your source file may require a setup task or manual step to ensure the information passes the import validation. Before you prepare your source file, complete the prerequisite steps to determine the data values, and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update a contact point and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Adding Contact Points in the Same Batch Adding Contact Point Records to an Existing Party Updating Contact Point Records

PartyId

The internal ID for the party (account, contact, household, partner, or legal entity) to which the contact point belongs.

Identify the party ID value by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is CONTACT_NUMBER for contact.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is CONTACT_NUMBER for contact.

PartyOrigSystem

The code representing the source system for the party (account, contact, household, partner, or legal entity) to which the contact point belongs.

Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this contact point.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is CONTACT_NUMBER for contact.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is CONTACT_NUMBER for contact.

PartyOrigSystemReference

The reference number or text representing the source system unique ID for the party (account, contact, household, partner, or legal entity) to which the contact point belongs.

Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this contact point.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is CONTACT_NUMBER for contact.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (Internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is CONTACT_NUMBER for contact.

ObjectKey

The unique ID for the existing contact point record in the destination table.

Identify the contact point ID for an existing contact point by exporting the contact point object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • CpOrigSystem and CpOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is CONTACT_NUMBER for contact.

ContactPointType

Type of the contact point like phone, email and so on.

Identify valid lookup codes for the COMMUNICATION_TYPE lookup. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Contact Point Lookups

Required

Required

Required

CpOrigSystem

A source system code that identifies the original source system of the contact point.

Identify the source system code that was used when you imported the contact point in a prior batch, or identify the source system code that you will use when importing the contact point in the same batch as this contact point contact preference.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • CpOrigSystem and CpOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is CONTACT_NUMBER for contact.

CpOrigSystemReference

A source system reference that identifies the unique ID of the contact point in your legacy or external system.

Identify the reference value from your source system that was used when you imported the contact point in a prior batch, or identify the source system reference that you will use when importing the contact point in the same batch as this contact point contact preference.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (Internal ID).

  • CpOrigSystem and CpOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile), which is CONTACT_NUMBER for contact.

OwnerEmailAddress

The e-mail address of the resource that owns and manages the sales account to which the contact is associated.

Identify the party ID and party number of the owner by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Optional

Conditionally required.

Specify an owner, by including one of the following reference information:

  • OwnerEmailAddress

  • OwnerPartyID

  • OwnerPartyNumber

Conditionally required.

By default, the user importing the contact is designated as the owner.

To specify a different owner, include one of the following reference information:

  • OwnerEmailAddress

  • OwnerPartyID

  • OwnerPartyNumber

OwnerPartyId

The unique identifier of a valid employee resource who owns and manages the sales account to which the contact is associated.

Identify the party ID and party number of the owner by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Optional

Conditionally required.

Specify an owner, by including one of the following reference information:

  • OwnerEmailAddress

  • OwnerPartyID

  • OwnerPartyNumber

Conditionally required.

By default, the user importing the contact is designated as the owner.

To specify a different owner, include one of the following reference information:

  • OwnerEmailAddress

  • OwnerPartyID

  • OwnerPartyNumber

OwnerPartyNumber

The party number of a valid employee resource who owns and manages the sales account to which the contact is associated.

Identify the party ID and party number of the owner by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Optional

Conditionally required.

Specify an owner, by including one of the following reference information:

  • OwnerEmailAddress

  • OwnerPartyID

  • OwnerPartyNumber

Conditionally required.

By default, the user importing the contact is designated as the owner.

To specify a different owner, include one of the following reference information:

  • OwnerEmailAddress

  • OwnerPartyID

  • OwnerPartyNumber

You use four sets of reference information to refer to a record. However, you must use only one of them to refer to a record; else, the import process would result in an error. The import process recognizes reference information in this order:

  1. PartyId, ObjectKey, and so on.

  2. Public User ID such as organization name, contact name, and so on.

  3. Origin system and origin system reference

  4. Other reference information such as business keys.

This image depicts a sample attribute mapping to import a contact point for an existing party. In this scenario, you identify the party with the OrigSystem and OrigSystemReference values.

Sample import mapping for Contact Point

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/engagement/19b/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in Sales and B2B Service Help Application search. You can access help from any Sales and B2B Service page by clicking Help and selecting Applications Help.

  • Importing contacts

  • Importing accounts

  • Importing households

  • Importing legal entities

  • Importing employee resources

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

Importing Contact Point Preferences: Quick Start

You can use the information in this topic to import contact point preferences. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

Note: You can associate addresses with persons and organizations, although contact points don't formally include addresses.

Use the file-based import objects and target objects in this table to import contact point preferences.

Import Object Party Type Target Objects for Importing Contact Point Preferences

Contact

Person

EmailContactPreference, FaxContactPreference, and so on.

InstantMessenger has no contact point preference.

Account

Organization

PrimaryPhoneContactPreference, FaxContactPreference, AddressContactPreference

Url has no contact point preference.

Household

Organization

EmailContactPreference, FaxContactPreference, and so on.

InstantMessenger and Url have no contact point preference.

Legal Entity

Organization

FaxContactPreference, PrimaryPhoneContactPreference, PrimaryAddressContactPreference

Url has no contact point preference.

Lead

Organization (lead organization)

No contact point preferences

Lead

Person (lead individual)

No contact point preferences

Lead

Person (contact at lead organization)

No contact point preferences

Partner

Organization

FaxContactPreference, PrimaryPhoneContactPreference, PrimaryAddressContactPreference

Url has no contact point preference.

Partner Contact

Person (contact for a partner)

EmailContactPreference, FaxContactPreference, and so on.

InstantMessenger has no contact point preference.

Campaign Response

Organization (respondent organization)

No contact point preferences

Campaign Response

Person (individual respondent)

No contact point preferences

Campaign Response

Person (contact at respondent organization)

No contact point preferences

Use the file-based import objects and target objects in this table to import contact point preferences directly associated with a contact relationship.

Import Object Party Type Target Objects for Importing Contact Point Preferences

Contact

Person (a contact for another root object such as account)

ContactEmailContactPreference, ContactFaxContactPreference, and so on.

ConactInstantMessenger has no contact point preference.

Account

Person (a contact for an account)

ContactEmailContactPreference, ContactFaxContactPreference, and so on.

ContactInstantMessenger has no contact point preference.

Legal Entity

Person (contact for a legal entity)

ContactEmailContactPreference, ContactFaxContactPreference, and so on.

ContactInstantMessenger has no contact point preference.

Overview of Contact Point Preferences

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

Identify and Associate Records with Each Other

To add or update existing contact point preference assignments using file-based import, your source file must contain information about the account, contact, or household party to which the contact point preference belongs. You map your source file data to the account, contact, or household profile target object.

If you're creating the party and contact point preference assignment in the same import activity, then group the party and contact point preference data together in your source file. The import process can import the party, and then identify the party record so that it can import the associated contact point preference. To add a contact point preference to an existing party, or to update an existing contact point preference record, your source file must include values that enable the import process to identify the existing records.

To add or update a contact point preference, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file. The file-based data import process stores a cross-reference between the source system information and the internal ID. The import process uses the combination of source system and source system reference value to identify the existing record.

You can extend source systems to identify the source of the data. You use source systems that are external sources of data to import data into Oracle Application Cloud. Oracle Application Cloud uses source system references to create references between source IDs and the Oracle Application Cloud database IDs. You can extend source systems in one of these ways:

  • Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  • Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

Before You Start

The minimum data required to import contact point preference information depends on:

  • The purpose of the import. The data is different when you create both the party and the contact point preference in the same import batch, add new contact point preference to an existing party, or update a contact point preference record.

  • Identifying and associating records. In some cases, you can choose which attributes you want to provide to the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update a contact point preference and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Adding Contact Point Preferences in the Same Batch Adding Contact Point Preference Records to an Existing Party Updating Contact Point Preference Records

PartyId

The internal ID for the party (account, contact, household, partner, or legal entity) to which the contact point preference belongs.

Identify the party ID value by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

PartyOrigSystem

The code representing the source system for the party (account, contact, household, partner, or legal entity) to which the contact point preference belongs.

Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this contact point preference

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

PartyOrigSystemReference

The reference number or text representing the source system unique ID for the party (account, contact, household, partner, or legal entity) to which the contact point preference belongs.

Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this contact point preference.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (internal ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

ContactType

The method of contact that should or should not be made, such as call or mail.

Identify the contact type. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Common Lookups

Required

Required

The attribute is neither required nor conditionally required.

PreferenceCode

The lookup code that represents the contact method preference phrase, such as Do Use, Opt In, don't use.

Identify the preference code. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Common Lookups

Required

Required

The attribute is neither required nor conditionally required.

PreferenceStartDate

The date from which a contact preference is valid.

The contact preference period start date must be less than or equal to the contact preference period end date.

Required

Required

The attribute is neither required nor conditionally required.

RequestedBy

The lookup code that represents the source of the contact preference request, such as internal requirement or requested by the party.

Identify lookup codes for the source of the contact preference request. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Common Lookups

Required

Required

The attribute is neither required nor conditionally required.

ContactPrefOrigSysRef

The source system reference that identifies the unique ID of the contact preference in your legacy or external system.

No prerequisite tasks.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (internal ID).

  • AdditionalPartyIdOrigSystem and AdditionalPartyIdOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (internal ID).

  • AdditionalPartyIdOrigSystem and AdditionalPartyIdOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

ContactPrefOrigSystem

A source system code that identifies the original source system of the contact preference.

No prerequisite tasks.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (internal ID).

  • AdditionalPartyIdOrigSystem and AdditionalPartyIdOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (internal ID).

  • AdditionalPartyIdOrigSystem and AdditionalPartyIdOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

ObjectKey

The unique ID of the existing contact preference record in the destination table.

Identify the contact preference ID of an existing contact preference by exporting the Contact Preference object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (internal ID).

  • AdditionalPartyIdOrigSystem and AdditionalPartyIdOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

CpOrigSystem

A source system code that identifies the original source system of the contact point.

Identify the source system code that was used when you imported the contact point in a prior batch, or identify the source system code that you will use when importing the contact point in the same batch as this contact point contact preference.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (internal ID).

  • CpOrigSystem and CpOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

CpOrigSystemReference

A source system reference that identifies the unique ID of the contact point in your legacy or external system.

Identify the reference value from your source system that was used when you imported the contact point in a prior batch, or identify the source system reference that you will use when importing the contact point in the same batch as this contact point contact preference.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • ObjectKey (internal ID).

  • CpOrigSystem and CpOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

This image depicts a sample attribute mapping to import a contact point preference for an existing party. In this scenario, you use the OrigSystem and OrigSystemReference values to identify the party.

Sample import mapping for Contact Point Preference

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a//index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in CX Sales and B2B Service Help Application search. You can access help from any CX Sales and B2B Service page by clicking Help and selecting Applications Help.

  • Importing contacts

  • Importing accounts

  • Importing households

  • Importing legal entities

  • Importing employee resources

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

Importing Contact Jobs: Quick Start

You can use the information in this topic to import contact jobs. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

You use a contact job to store information related to the work done by a contact. You can import new contact jobs or update existing contact jobs, using the File-Based Data Import feature. The contact job contains attributes that records data such as the name and code of the department where the contact works, the job title of the contact, and so on.

Use the file-based import objects and target objects in this table to import contact jobs.

Import Object Party Type Target Object

Contact

Person

ContactJob

Account

Person (a contact for a account)

ContactJob

Lead

Lead Contact

ContactJob

Legal Entity

Person (a contact for a legal entity)

ContactJob

Partner

Partner Contact

Job

Response

Response Contact

ContactJob

Identify and Associate Records with Each Other

To add or update a contact job assignment using file-based import, your source file must contain information about the account, contact, or household party to which the contact job belongs. You map your source file data to the account, contact, or household profile target object and to the contact job target object.

If you're creating the party and the contact job assignment in the same import activity, then group the party and contact job data together in your source file. The import process imports the contact job, and then identifies the contact job record so that it can import the associated contact job.

To add or update an existing contact job, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process stores a cross-reference between the source system information and the internal ID. The import process uses the combination of source system and source system reference value to identify the existing record.

You can extend source systems to identify the source of the data. You use source systems that are external sources of data to import data into Oracle Application Cloud. Oracle Application Cloud uses source system references to create references between source IDs and the Oracle Application Cloud database IDs. You can extend source systems in one of these ways:

  • Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  • Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

Before You Start

The minimum data required to import account profile information depends on:

  • The purpose of the import. The data requirements are different when you're creating both the party and the contact job in the same import batch, adding contact jobs to an existing party, or updating a contact job record.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update a contact job and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Party and Adding contact job in the Same Batch Adding contact job to an Existing Party Updating Existing Contact Jobs

PartyId

The internal ID for the party (account, contact, household, or legal entity) to which the address belongs.

Identify the party ID value by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Required

Conditionally required.

To identify the party, provide either the internal ID (PartyId) or both the source system code (PartyOrigSystem) and source system reference value (PartyOrigSystemReference) that were provided in a prior import of the party.

Conditionally required.

To identify the party, provide either the internal ID (PartyId) or both the source system code (PartyOrigSystem) and source system reference value (PartyOrigSystemReference) that were provided in a prior import of the party.

PartyOrigSystem

The code representing the source system for the party (account, contact, household, or legal entity) to which the address belongs.

Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this address.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

To identify the party, provide either the internal ID (PartyId) or both the source system code (PartyOrigSystem) and source system reference value (PartyOrigSystemReference) that were provided in a prior import of the party.

Conditionally required.

To identify the party, provide either the internal ID (PartyId) or both the source system code (PartyOrigSystem) and source system reference value (PartyOrigSystemReference) that were provided in a prior import of the party.

PartyOrigSystemReference

The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the address belongs.

Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this address.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

To identify the party, provide either the internal ID (PartyId) or both the source system code (PartyOrigSystem) and source system reference value (PartyOrigSystemReference) that were provided in a prior import of the party.

Conditionally required.

To identify the party, provide either the internal ID (PartyId) or both the source system code (PartyOrigSystem) and source system reference value (PartyOrigSystemReference) that were provided in a prior import of the party.

RelationshipId

The unique ID for the existing contact's relationship with the organization or person record in the destination table.

identify the Relationship ID for an existing contact's relationship by exporting the Relationship object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

To identify the existing contact job record, provide either the internal ID (ObjectKey) or both the source system code (RelOrigSystem) and source system reference value (RelOrigSystemReference) that were provided in a prior import of the party.

RelOrigSystem

The source system code that identifies the original source system of the contact's relationship with the organization or person.

No prerequisite tasks.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

To identify the existing contact job record, provide either the internal ID (ObjectKey) or both the source system code (RelOrigSystem) and source system reference value (RelOrigSystemReference) that were provided in a prior import of the party.

RelOrigSystemReference

The ID that identifies the contact's relationship with the organization or person in your legacy or external system.

No prerequisite tasks.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file.

Conditionally required.

To identify the existing contact job record, provide either the internal ID (ObjectKey) or both the source system code (RelOrigSystem) and source system reference value (RelOrigSystemReference) that were provided in a prior import of the party.

ContactNumber

The contact job's unique public identifier value.

Obtain the contact number for an existing contact using the Customers work area.

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

Conditionally required.

Required if you're updating a contact job and aren't providing the object key.

ObjectKey

The unique ID for the existing contact job record in the destination table.

identify the contact ID for an existing contact by exporting the Organization Contact object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

Conditionally required.

Required if you're updating a contact job and aren't providing the contact number.

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in CX Sales and B2B Service Help Application search. You can access help from any CX Sales and B2B Service page by clicking Help and selecting Applications Help.

  • Importing contact jobs

  • Importing accounts

  • Importing contacts

  • Importing groups

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

How You Import Country Structures

You can use the information in this topic to import country structures. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

You use the country structure of a country to define which geography types are part of the country and how the geography types are hierarchically related within the country. For example, you can create geography types called State, City, and Postal Code. Then you can rank the State geography type as the highest level within the country, the City as the second level, and the Postal Code as the lowest level within the country structure.

Use the file-based import object and target object in this table to import country structures.

Import Object Target Object

Country Structure

ImpGeoStructureLevel

Identify and Associate Records with Each Other

To add or update a country structure using file-based import, your source file must contain information about the party to which the country structure belongs. You also need to specify the level at which the geography types need to be placed. By default, all countries are at Level 1. You create the country structure by increasing the level number as you go down the country structure. You place the geography types such as states, provinces, and so on at Level 2, districts or counties at Level 3, and so on.

To add or update a country structure, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process uses the combination of source system and source system reference value to identify the existing record.

You can use external IDs or business keys to identify and associate records with each other when you're importing a smaller set of records. Business keys are attributes that uniquely identify a party record. For example, a person's last name and first name uniquely identify a person. An external ID is a unique record identifier from an application outside of CX Sales and B2B Service.

You can extend source systems to identify the source of the data. You use source systems that are external sources of data to import data into Oracle Application Cloud. Oracle Application Cloud uses source system references to create references between source IDs and the Oracle Application Cloud database IDs. You can extend source systems in one of these ways:

  1. Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  2. Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

Before You Start

The minimum data required to import country structure information depends on:

  • The purpose of the import. The data is different when you create both the party and the country structure in the same import batch, add new country structure to an existing party, or update a country structure record.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update a country structure and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Country Structure Record for an Existing Country

CountryCode

The code representing the country to which the country structure belongs.

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

Identify the country codes. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Geographies

Required

GeographyType

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

No prerequisite tasks

Required

LevelNumber

The level number for the geography type in the hierarchy. For example, a country has the level of 1 in the hierarchy because it's the highest level.

No prerequisite tasks

Required

This image shows a sample attribute mapping to import a new country structure for an existing country structure.

Sample import mapping for Country Structure

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in Help Application search.

  • Importing country structures

Tip: For sample country structures and detailed steps for importing country structures, see article 1341174.1 on My Oracle Support.

How You Import Workers, Users, and Resources

You can use the information in this topic to import workers, users, and resources.

You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

Use the file-based import objects and target objects in this table to import workers, users, and resources.

Import Object Target Object

Employee Resource

WorkerProfile, ResourceProfile, ResourceOrganizationMembership, ResourceTeamMembership, and PrimaryAddress

Overview of Workers, Users, and Resources

You store information about a newly hired employee, a contingent worker, or a partner contact in Human Capital Management (HCM) as a worker. The employees, contingent workers, and partner contacts who can be assigned work to accomplish business objectives are called resources.

You can import the worker information using the WorkerProfile target import object. This target import object allows import of the basic person information, such as first name, last name, e-mail address, business unit, and legal entity.

The worker information from HCM is imported into Oracle Cloud Applications as a resource. For example, you can import a worker from HCM into Oracle Cloud Applications as a sales representative. You can import the resource information using the ResourceProfile target import object. This target object helps you to import basic resource information, such as resource role code, and resource role type attributes.

A resource role denotes the function of a resource in an enterprise. You use resource roles to describe a resource in the enterprise and the specific role performed by the resource for an organization or a team. You can use only one role for a resource in a resource organization during a specific period.

Resource role types organize roles into logical groups. For example, the Partner resource role type defines a set of partner-specific roles, such as partner sales representative and partner sales manager. You can use the Sales resource role type and the Marketing resource role type to categorize the appropriate sales and marketing roles for internal employees or contingent worker resources.

You can define roles that can be assigned to resources within resource organizations. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Resource Roles

When you assign specific roles to resources, they automatically receive access to specific business functions, locations, applications, and data within the company.

A resource team is a group of resources formed to accomplish a specific task. A resource team may comprise resource organizations, resources, or both. You use Resource organizations to represent the internal organization and structure of the deploying company. Resource organizations are hierarchically structured, and reporting relationships are derived from the organization hierarchy. You can import the resource organization and resource team membership information using the ResourceOrganizationMembership and ResourceTeamMembership target objects respectively.

Identify and Associate Records with Each Other

To add or update an employee resource using file-based import, your source file must contain information about the party to which the Employee Resource belongs.

To add or update an employee resource, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

Before You Start

The minimum data required to import employee resource information depends on:

  • The purpose of the import. The data is different when you create both the party and the employee resource in the same import batch, add new employee resource to an existing party, or update an employee resource record.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

  • The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update an employee resource and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Creating Employee Resource Record and Updating Employee Resource Record in the Same Batch

WorkerProfile_BusinessUnit

The business unit name to which the resource is associated.

Identify business unit names. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Business Unit

Required

WorkerProfile_LegalEntity

The legal entity name of the employer.

Identify legal entity names. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Legal Entity

Required

WorkerProfile_FirstName

The worker's first name.

No prerequisite tasks

Required

WorkerProfile_LastName

The worker's last name.

No prerequisite tasks

Required

WorkerProfile_EmailAddress

The primary work email ID of the worker.

No prerequisite tasks

Required

WorkerProfile_ManagerEmail

The primary work email ID of the worker's manager.

No prerequisite tasks

Conditionally required.

If you want to identify an employee in the resource hierarchy, then you must mention the manager email address.

WorkerProfile_PersonType

Describes the person type, for example, EMP for employees, CWK for contingent workers.

No prerequisite tasks

Conditionally required.

If the source of your data is a contingent worker, then you must mention the person type. The default value of the person type is EMP.

ResourceProfile_RoleCode

The value for the resource role code, which is predefined in the Manage Resource Roles task.

Identify the employee resource role code by reviewing the employee resource role types and codes. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Resource Roles

Conditionally required.

If you want to identify an employee as a resource, then you must mention the resource role code.

ResourceProfile_RoleTypeCode

The value for the resource role type, which is predefined in the Manage Resource Roles task.

Identify the employee resource role type code by reviewing the employee resource role types and codes. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Resource Roles

Conditionally required.

If you want to identify an employee as a resource, then you must mention the resource role type code.

ResourceOrganizationMembership_TreeCode

The code for the organization hierarchy that the resource is a member of. For employee resources, the value is GLOBAL_SALES_MARKETING. For partner contacts (members), the value is the code for the partner organization hierarchy.

No prerequisite tasks

Conditionally required.

If you want to associate a resource to an organization hierarchy, then you must mention the tree code of the organization hierarchy to which the resource belongs.

ResourceOrganizationMembership_ParentTreeCode

The code for the parent of the resource's organization within the organization hierarchy. For employee resources, the value is GLOBAL_SALES_MARKETING. For partner contacts (members), the value is the code that represents the parent in the partner organization hierarchy.

No prerequisite tasks

Conditionally required.

If you want to associate a resource to an organization hierarchy, then you must mention the parent tree code of the resource's organization.

ResourceOrganizationMembership_OrganizationUsage

The resource organization usage, which is SALES_RESOURCE_ORG for sales, PARTNER_RESOURCE_ORGANIZATION for partners, and MARKETING_RESOURCE_ORGANIZATION for marketing.

No prerequisite tasks

Conditionally required.

If you want to associate a resource to an organization hierarchy, then you must mention the resource organization usage.

ResourceOrganizationMembership_OrganizationName

The organization name of the resource.

Identify the organization name of the resource by navigating to the Resource Directory.

If the organization name that you use in the source file doesn't already exist in the Resource Directory, then it's created during the employee resource import process.

Conditionally required.

If you want to associate a resource to an organization hierarchy, then you must mention the organization name of the resource.

ResourceOrganizationMembership_ParentOrganizationName

The organization name of the resource's manager.

Identify the organization name of the resource's manager by navigating to the Resource Directory.

Conditionally required.

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

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

This image depicts a sample attribute mapping to import an employee resource.

Sample import mapping for Worker Profile and Resource
Profile

Evaluate Attributes with Reference Files

For more information about import attributes, see the Sales and B2B Service File-Based Data Import for Engagement guide available on the Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/engagement/19b/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects. Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in Sales and B2B Service Help Application search. You can access help from any Sales and B2B Service page by clicking Help and selecting Applications Help.

  • Importing users

  • Importing resource teams

  • Importing employee resources

Importing Organization Profiles: Quick Start

You can use the information in this topic to import organization profiles.

You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

You use an organization profile to store information about an account, legal entity, and partner. The organization profile contains information for the organization, such as the stock symbol, number of employees, and the CEO's name. You can import new organization profiles or update existing organization profiles, using the File-Based Data Import feature.

Use the file-based import objects and target objects in this table to import organization profiles.

Import Object Party Type Target Object

Account

Organization

OrganizationProfile

Legal Entity

Organization

OrganizationProfile

Lead

Organization

OrganizationProfile

Marketing Campaign Response

Organization

OrganizationProfile

Partner

Organization

PartnerInterface

Identify and Associate Records with Each Other

To add or update an organization profile using file-based import, your source file must contain information about the party to which the organization profile belongs. You map your source file data to the account, legal entity, lead, marketing campaign response, or partner (organization profile) target object.

To add or update an organization profile, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process uses the combination of source system and source system reference value to identify the existing record.

You can use external IDs or business keys to identify and associate records with each other when you're importing a smaller set of records. Business keys are a set of attributes that uniquely identify a party record. For example, a person's last name and first name uniquely identify a person. An external ID is a unique record identifier from a system outside of CX Sales and B2B Service. You can use the following business keys or external IDs in CX Sales and B2B Service:

  • Organization name for organizations

  • First name and last name for persons

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

  • Address information, which is a combination of address1, address2, city, and postal code.

You can extend source systems to identify the source of the data. You use source systems that are external sources of data to import data into Oracle Application Cloud. Oracle Application Cloud uses source system references to create references between source IDs and the Oracle Application Cloud database IDs. You can extend source systems in one of these ways:

  • Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  • Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

Before You Start

The minimum data required to import organization profile information depends on:

  • The purpose of the import. The data is different when you create both the party and the organization profile in the same import batch, add new organization profile to an existing party, or update an organization profile record.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update an organization profile and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Create an Organization Profile Update an Existing Organization Profile

PartyOrigSystem

The code representing the external source system.

Predefine your source system code as enabled for Trading Community members. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (record ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile).

  • A business key such as organization name.

Conditionally required

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (record ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile).

  • A business key such as organization name.

PartyOrigSystemReference

The reference number or text representing the source system unique ID for the organization.

Identify the reference value from your source system.

Conditionally required

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (record ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile).

  • A business key such as organization name.

Conditionally required

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (record ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile).

  • A business key such as organization name.

OrganizationName

The name of the organization.

No prerequisite tasks

Required

The attribute is neither required nor conditionally required.

ObjectKey or PartyID

The record ID for the organization.

Identify the PartyId by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

Conditionally required

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (record ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile).

  • A business key such as organization name.

Type

The organization type. The type is set to Account by default for new organization profiles.

No prerequisite tasks

The attribute is neither required nor conditionally required.

The attribute is neither required nor conditionally required.

This image figure shows a sample attribute mapping to import a new organization. In this scenario, you use the origin system and origin system reference information to identify the organization.

Sample attribute mapping to create organization

This image shows a sample attribute mapping to update an existing organization. In this example, you use the origin source system and source system reference to identify an organization and update the CEO name.

Sample attribute mapping to update an existing
organization

Evaluate Attributes with Reference Files

For more information about import attributes, see the File-Based Data Import for CX Sales and B2B Service guide available on the CX Sales and B2B Service Help Center (https://docs.oracle.com/en/cloud/saas/sales/20a/oefbs/index.html). See the topic for your import object, which includes links to reference files for target import objects.

Review a reference file to see attributes that are available to import and information for each attribute, including requirement for inclusion in an import, validation requirements, default value, data type, data length, and description.

Additional Tips

Tip: You can explore related topics by entering the following keywords in the CX Sales and B2B Service Help Application search.

  • Importing sales leads

  • Importing legal entities

  • Importing contacts

  • Importing marketing campaign responses

  • Importing partners

Tip: If your data isn't from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference values might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.

Importing Person Profiles: Quick Start

You can use the information in this topic to import account profiles. You will also learn how to:

  • Identify and associate records

  • Access and use reference files to evaluate attributes

You use a person party profile to import contacts and household members. For example, you can use person profiles to import contact information. A person profile contains various attributes, such as first name, last name, and so on. You can import new person profiles or update existing person profile records using the File-Based Data Import feature.

Use the file-based import objects and target objects in this table to import account profiles.

Import Object Target Object

Contact

PersonProfile

Account (Account Contact)

PersonProfile, ContactPersonProfile

Household (Customer Contact)

PersonProfile, ContactPersonProfile

Legal Entity (Legal Entity Contact)

PersonProfile, ContactPersonProfile

Employee Resource

PersonProfile

Lead (Lead Contact)

PersonProfile, ContactPersonProfile

Partner Contact

PersonProfile

Marketing Campaign Response (Contact Respondent)

PersonProfile

Marketing Campaign Response (Marketing Campaign Response Contact)

PersonProfile, ContactPersonProfile

Note: CX Sales and B2B Service supports the ContactPersonProfile target object. However, the object is now deprecated. For updating any contact information, use the PersonProfile target object instead.

Identify and Associate Records with Each Other

To add or update a person profile using file-based import, your source file must contain information about the party to which the person profile belongs.

To add or update a person profile, your source file must include the values that let the import process identify the existing records. These values are a combination of source system and source system reference values, internal ID, or public unique identifiers, such as business keys or external IDs.

If the source of your data is an external application and you plan to import updates, then you can provide the source system code and the unique reference value for the source system's record in your source file. The import process uses the combination of source system and source system reference value to identify the existing record.

You can use external IDs or business keys to identify and associate records with each other when you're importing a smaller set of records. Business keys are attributes that uniquely identify a party record. For example, a person's last name and first name uniquely identify a person. An external ID is a unique record identifier from an application outside of CX Sales and B2B Service. You can use the following business keys or external IDs in CX Sales and B2B Service:

  • First name and last name for persons

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

  • Address information, which is a combination of address1, address2, city, and postal code.

You can extend source systems to identify the source of the data. You use source systems that are external sources of data to import data into Oracle Application Cloud. Oracle Application Cloud uses source system references to create references between source IDs and the Oracle Application Cloud database IDs. You can extend source systems in one of these ways:

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

  • Navigate to the following in the Setup and Maintenance work area:

    • Offering: Sales

    • Functional Area: Data Import and Export

    • Task: Manage Trading Community Source System

  • Import the source system information into Oracle Application Cloud using the Source System Reference import object.

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

Before You Start

The minimum data required to import account profile information depends on:

  • The purpose of the import. The data is different when you create both the party and the person profile in the same import batch, add new person profile to an existing party, or update a person profile record.

  • Identifying and associating records. You can select the attributes you need for the import process when identifying and associating records.

The values provided in your source file may require a setup task or manual step to ensure that they're validated at the time of import. Before preparing the source file, complete the prerequisite steps to determine the data values and then include those values in your source file.

Listed below are the attributes (minimum data) required or conditionally required in your import file to create or update a person profile and their pre-requisite setup tasks. You can, optionally include attributes that are available for import in your import file but that aren't listed in the table.

Attribute Description Prerequisite Setup Task Create Party and Person Profiles Update Person Profile Records

ObjectKey or PartyId

The record ID for the party (account, contact, household, or legal entity) to which the person profile belongs.

Identify the party ID value by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

The attribute is neither required nor conditionally required.

Conditionally required.

Provide reference information to identify the existing party. The reference information can be:

  • PartyId (record ID).

  • PartyOrigSystem and PartyOrigSystemReference (source system code and source system reference values) provided when importing the organization profile.

  • Party Number (public unique identifier for an organization profile).

  • A business key such as person name.

PartyOrigSystem

The code representing the external source system for the party (account, contact, household, or legal entity) to which the person profile belongs.

Predefine your source system code as enabled for parties. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

Conditionally required.