14Import Your Data

This chapter contains the following:

Data Import Options

You can import your data from an external application into Oracle Applications Cloud in several different ways, including using public web services. Which import method you use depends on the type of data you're importing, the volume of data, and technical requirements. If you're integrating one cloud service with other cloud services, then you must use additional import methods as described in the appropriate guides.

When you're importing data for a particular object, you must make sure that any prerequisite objects already exist in the application. For example, if you're importing contacts for an account, then the account must already exist in the application. If one import job depends on the contents of another import job, then complete the prerequisite job before starting the dependent job. For example, if you're importing both accounts and opportunities, then import accounts before importing opportunities.

The following table lists the import methods and references to further information.

Import Method Description When to Use How to Access For More Information

Quick Import Excel Macros

You can use the import macros to speed up and simplify the import of up to 5000 records at a time for some objects. They validate your data entries, provide list of values, and automatically populate constant values.

The macros create data files that are automatically imported using Import Management.

You can import the following objects using import macros:

  • Sales Users

  • Products and product groups

  • Accounts

  • Contacts

  • Account Hierarchy

  • Leads

  • Opportunities

These are best to import data in your initial deployment.

The macros are targeted to the simple proof of concept sales automation use case covered in the Importing Sales Users chapter of the Getting Started with Your Sales Implementation guide. For example, the import macros assume that you're importing account, contact, and lead records for one country at a time.

The macros generate log files with information about the File Import job, and these log files can also serve as a learning tool for more complex import.

You can download the Excel macros and any required mapping files from the Getting Started with Your Implementation: Quick Import Macros (Document ID 2229503.1) article on My Oracle Support.

The chapters in the Getting Started with Your Sales Implementation guide provide detailed instructions and video tutorials for using the macros.

For instructions on how to add your own fields to the macros, see. How to Configure Quick Import Macro for importing Employee Resources (Doc ID 2364229.1) article on My Oracle Support.

Import Management

Import Management improves definition, error handling, and performance for importing flat files (.CSV). For example, Import Management has drag and drop mapping capabilities and validates the first ten records in your data file before you import to ensure the data meets the import constraints of the various attributes.

Import Management is available for importing data for the following application objects and their child objects:

  • Access Groups

  • Account

  • Action

  • Action Plan

  • Activity

  • Address

  • Asset

  • Attachment

  • Business Plan

  • Campaign

  • Case

  • Classification

  • Classification Code

  • Competitor

  • Consumer

  • Contact

  • Contract

  • Contests

  • Country Structure

  • Deal Registration

  • Hierarchy

  • Hierarchy Member

  • Household

  • Hub Source System Reference

  • Incentive Rule Assignments

  • Incentive Rule Attribute Values

  • Incentive Rules

  • Incentive Transaction

  • Interaction

  • MDF Budget

  • MDF Claim

  • MDF Request

  • Note

  • Objective

  • Opportunity

  • Organization

  • Partner

  • Partner Program

  • Person

  • Price Book Header

  • Product

  • Product Group

  • Program Enrollment

  • Promotion

  • Queue

  • Relationship

  • Resource

  • Resource Capacity

  • Sales Lead

  • Sales Order

  • Sales Territory

  • Sales Territory Quota

  • Self-Service Role

  • Service Request

  • Standard Text

  • Standard Text Folder

  • Standard Text User Variable

  • Subscription

  • Template

  • Template Action

  • Territory Geographies

  • Any additional objects you create

Use Import Management for importing outside the scope of the Getting Started with Your Implementation guide.

Click Import Management in the Navigator.

See the Understanding Import and Export Management guide for instructions on using the import.

External Data Loader Client

Command-line tool that's used to import high-volume flat source data files into CX Sales and B2B Service. This tool splits a large data file into multiple smaller files to adhere to import volume limits, and enables the tracking of import status.

The client supports the same objects as Import Management.

Use this import method for importing very large data files for the objects supported by Import Management.

You can download the client from Oracle Support Document 2325249.1 (External Data Loader Client) on My Oracle Support.

Instructions for using the client are available in the document and in the client itself.

The chapter Import Data Using External Data Loader Client in the guide Understanding Import and Export Management for CX Sales and B2B Service provides information about using the External Data Loader Client.

Web Services

Web services are available for external client applications to start and monitor import jobs. You can manage Import Management jobs using REST web services, and File Import jobs using SOAP web services.

Use web services to manage import jobs to import directly from an external application.

Public APIs are available for both the Import Management/REST services and the File Import/SOAP services.

The following REST APIs are available for import:

  • Import Activities

  • Import Activity Maps

  • Import Export Objects Metadata

The SOAP service is called the File Import Activity Service.

For REST API documentation, see the REST API for CX Sales and B2B Service guide.

For SOAP API documentation, see the SOAP Web Services for CX Sales and B2B Service guide.

High-Volume Import

The high-volume import mode is designed to import millions of records at once. This mode doesn't trigger any custom logic configured through the application composer. This option is available for the following objects and their child objects:

  • Account

  • Asset

  • Classification Code

  • Contact

  • Contract

  • Contract Line

  • Country Structure

  • Custom Object (custom top level objects and custom child objects)

  • Geography

  • Hierarchy

  • Hierarchy Member

  • Household

  • Hub Source System Reference

  • Incentive Transaction

  • Organization

  • Person

  • Sales Territory Quota

  • Territory Geographies

Use this import mode for importing very large number of records for the objects supported.

You can access High-Volume Import either using REST services or using External Data Loader Client.

When importing using REST, set the "High-volume" attribute to enable this mode of import.

When importing using the External Data Loader Client, set the command-line parameter "-high-volume" to enable this mode of import.

For REST API documentation, see the REST API for CX Sales and B2B Service guide.

The chapter Import Data Using External Data Loader Client in the guide Understanding Import and Export Management for CX Sales and B2B Service provides information about using the External Data Loader Client.

Note: Object work flows can't be invoked using Import Management.

The following figure provides an architectural overview of the different import methods:

  • File Import uses the SOA architecture to import data into Oracle CX Sales.

  • Quick Import uses the REST Web services to import data into Oracle CX Sales. When you import data using the quick import Excel macros, you're creating an import activity in Import Management using the REST web services. The macro import creates the same import activity and uses the same mapping as you do when you initiate the import from the application. You can monitor each import in the macro or in the application itself.

  • Both Import Management and the External Data Loader Client use the same scheduled processes for import. When you import very large files using the client, the REST APIs create multiple processes to respect the Import Management file size limit.

  • To import from an external application, use the SOAP and REST web services directly.

Architecture of the different import methods and their
flow.

You can import attachments associated with any supported object.

Supported Objects and File Types

The following objects support importing attachments:

  • Account

  • Activity

  • Asset

  • Business Plan

  • Contact

  • Custom Object

  • Deal Registration

  • Household

  • Message

  • Objective

  • Opportunity

  • Opportunity Revenue

  • Partner

  • Partner Program

  • Product

  • Sales Lead

  • Sales Lead Product

  • Service Request

The following file types are supported for attachment files:

  • CSV

  • DOC

  • DOCX

  • JPG

  • PDF

  • PNG

  • PPTX

  • TIF

  • TEXT

  • XLSX

  • XML

  • ZIP

How to Create ZIP File

To import an attachment, you must create a ZIP file that contains the source data file and optionally one or more attachment files. Make sure you always name the source file as 'Attachment.CSV'. You must mention each of the attachment file names in the Attachment.CSV file. The Attachment.zip file has the structure shown in the following image:

Attachment file structure

Here are the examples for the attachment.csv file shown in purple box in the image above:

Pk1Value ObjectPuid FileName Url

100100004247330

http://www.yahoo.com

100100004247330

Clouds.jpg

100100004247330

Taxdocs.docx

CDRM_6493

http://www.google.com

CDRM_6493

Holidays.pdf

Pk1Value and ObjectPuid column values uniquely identify an existing object record. FileName indicates the name of attachment files. Url indicates the value of URL attachment to import.

Note: The attachment ZIP file name can include characters such as parenthesis (), ampersand (&), dots (.), and apostrophe (').

An attachment can only be associated with an existing record of the object. A single record can be associated with multiple attachments by having multiple rows in the CSV file. You can import any number of attachments in an import job, but the ZIP file should not exceed 250 MB in size.

Note: A record in the CSV file can't have values for both FileName and Url columns. You can pass either the Primary key or the PUID for an object record. If you pass both Primary key and PUID values, then Primary key will be considered and PUID will be ignored.

How to Import Attachments

To import attachments:

  1. Click Tools > Import Management.

  2. On the Manage Imports page, click Create Import Activity.

  3. On the Enter Import Options page, enter a name for your import. From the Object drop-down list select Attachment.

  4. In the Attachment Object drop-down list that appears, select the object associated with the attachment.

  5. Select the ZIP file that you created in the previous section.

  6. Click Next. On the Map Fields page, click the Apply button next to the Import Mapping drop-down list to map the source and target attributes automatically.

  7. Click Next to navigate to the Review and Submit page.

Review the import activity configuration and click Submit to activate the import. The Manage Imports page shows the status of the submitted import. The topic Import Data in the related topics section contains more details about the import process.

Use Import Management from the Tools work area, to import data from text files. You can create, update, or delete records through import.

Use this topic as a guide to importing data. The import options and other details differ by the type of data that you're importing. Before importing, understand how the data in your file maps to the attributes in Oracle Applications Cloud and what values are expected in the import file. The data records in the CSV source file may not be processed in the listed order. To learn how to monitor the status of your import, see the topic How You Monitor Your Import Activities in the Related Topics section.

Note: Don't submit duplicate import jobs for the same import object as they create duplicate object records.

To help you get started, you can use the example import object templates described in the related topics.

Import Data from a File

To import data:

  1. Click Tools > Import Management.

  2. On the Manage Imports page, click the Create Import Activity button.

  3. On the Enter Import Options page provide values for each field as shown in the following table:

    Field Description of the value

    Name

    Name of the import.

    Object

    Object that you're importing.

    If you can't find your object, then search for it by clicking the Search link. In the Search and Select dialog box, enter the object name in the Object text box and click the Search button. Select your object from the result list and click OK.

    You can also use the advanced search option by clicking the Advanced button. Here you can search based on various filter criteria such as object name, Attachment supported, creation date, and so on.

    If the object you're importing isn't listed then verify if you have the roles and privileges required to import the object. For information on the roles, see the topic Roles Required for Import and Export Management referenced in the Related Topics section.

    Attachment Object

    To import an attachment for an existing object record in the database select the Attachments object from the Object drop-down list. Next select the object from the Attachment Object drop-down list.

    For more details on importing attachments, review the topic Import Attachments.

    File Name

    Browse and select a text file in CSV format. The first row of the source file is treated as the header row. Provide a file name within 40 characters.

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

    Import Object Hierarchy

    To import a hierarchy of objects, such as child and grandchild objects, click on the Import Object Hierarchy link after you upload the source file for the parent object. Next select the Enabled check box for the child object you want to import, and select the related source file.

  4. Optionally, to set additional import configurations, click the Advanced Options section. Here you can configure settings under Source File, Import Options, or Create Schedule sections.

    1. In the Source File and Import Options regions, some of the options in the following table might not be available depending on the object that you're importing:

      Option Description

      Import Mode

      You can specify whether you want to create and update records or update them only.

      • Update and create records - a new record is created if a matching record isn't found. This is the default option.

      • Create records - all the records in the file are new records which have to be created. If there are any existing matching records, then they're marked as errors.

      • Delete records - all the records in the file are deleted.

      Enable High-Volume Import

      The high-volume import mode is designed to import millions of records at once. This mode doesn't trigger any custom logic configured through the application composer. For a list of supported objects, see the topic Data Import Options.

      By default, this mode is enabled for the supported objects.

      Enable Survivorship

      Survivorship on update is available for Account, Organization, Contact, and Person. The check box is visible if the attribute survivorship is configured on the objects. You can use high-volume import mode, only when the survivorship configuration uses only Source Confidence. You can't use the high-volume import mode when Data Quality Rules are enabled.

      Notification email

      The email of the individual who receives import processing notifications. The user submitting the import receives an email notification automatically. To have more than one email recipient, separate the email addresses with a semicolon. If you don't want to receive the notification, then set the profile option ORA_ZCA_IMPEXP_ENABLE_EMAIL_NOTIFY to 'N' at user level.

      Enable Custom Business Logic

      If you select this check box, then any custom triggers and validations configured for the object are enabled. This may affect import performance, because of configurations. Hence, disable this option for better performance.

      To enable this check box by default, set the profile option ZCA_FILE_IMPORT_ENABLE_CUSTOM_BUSINESS_LOGIC to 'Yes' by navigating to the Manage Administrator Profile Values task.

      Note: This selection has no effect on events and object workflows, and is applicable only on triggers and validations.

      Delimiter

      If your file doesn't use a comma to separate values, then select the correct delimiter in the Delimiter drop-down list. Possible values are:

      • Caret Symbol

      • Closing Curly Bracket

      • Closing Parenthesis

      • Closing Square Bracket

      • Colon

      • Comma

      • Exclamatory Mark

      • Minus

      • Opening Curly Bracket

      • Opening Parenthesis

      • Opening Square Bracket

      • Pipe Symbol

      • Plus

      • Question Mark

      • Semi-Colon

      • Star Symbol

      • Tilde Symbol

      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 the time fields in your file.

      File Encoding

      The format in which your source file is encoded.

    2. In the Create Schedule region, schedule the import to run immediately or at a future date. If you select a future date, then provide the date and time to start the import.

  5. Click Next. The Map Fields page shows the first row of the data from your source file. By default, the application tries to automatically map each of the source file columns to the appropriate target object attribute. If some of the columns in your file couldn't be mapped, then drag the target attribute onto the Attribute Display Name column under the Source File region.

    The data in unmapped columns aren't imported.

  6. You select a predefined mapping from the list of available mappings under the Import Mapping drop-down list. If you're reusing an import mapping, then both the source and target columns are already populated.

    Leave the Attribute Display Name field blank for any column that you don't want to import.

    Click Validate Data to check the field mapping.

  7. In the case of hierarchical import, you can see the mapping information for child objects in the subsequent tabs. Note that data validation isn't done for these objects.

  8. Click Next. On the Review and Submit page, review the import activity configuration. If you had not run the prevalidation on the Map Fields page, then you get a notification message to run the validation process. You can view any unmapped columns of parent or child objects on this page.

  9. Click Validate Data to check the data in your source file. Validation errors, if any, are displayed on the Mapping Validation screen. If you get warnings about unmapped columns, then you can ignore these columns, and proceed to submit the import job. Validations are for informational purposes and applicable only for low-volume imports.

    Note: In import activity with single CSV hierarchical records, explicit validation from the mapping UI isn't supported. For example, while importing the sales territory object, if there are matching values for the attributes ParentUniqueTerritoryNumber and UniqueTerritoryNumber, then validation isn't supported.
    Note: During the import validation process on the Mapping page, the following custom triggers aren't supported:
    • After Changes Posted to Database

    • Before Delete in Database

    • Before Insert in Database

    • Before Update in Database

    • Before Rollback

  10. Click Submit to queue the import.

    Note that business events aren't fired when using Import Management.

Automating and Scheduling Import Jobs

You can automate import jobs using the import REST services. The import REST services let you manage import activities, manage activity maps, and export object metadata. You can use an external scheduler that uses these REST services to run recurring import jobs, create and run import activities, manage maps, and review object metadata.

You can use the Oracle WebCenter Content Document Transfer Utility to manage the import files used by the scheduler. You can download the Oracle WebCenter Content Document Transfer Utility by navigating to the My Oracle Support (support.oracle.com) document Oracle WebCenter Content Document Transfer Utility Readme (document ID 1624063.1). Once downloaded, you can run the tool by navigating to the ridc folder after extraction.

For detailed instructions on automating and scheduling file import using REST API, see Oracle CX Sales and B2B Service: Automating and Scheduling File Import Activity Using REST API (Doc ID 2308691.1) article on My Oracle Support (support.oracle.com).

Set Up Event Notifications for Resources

In file-based data import, the SendCredentialsEmailFlag attribute allowed the import to specify the notification setting for each employee resource. You can do this in Import Management using the User Category option but this applies to all resources in a single import.

To set up notifications for all events:

  1. Navigate to Tools > Security Console on the home page.

  2. Click the User Categories tab.

  3. Click DEFAULT. Click the Notifications tab.

  4. Click the Edit button. If you want to turn on all notifications, then select the Enable Notifications check box under the Notification Preferences heading.

  5. Click the Save button.

  6. Click the Done button.

To set up notifications for a specific event:

  1. Navigate to Tools > Security Console on the home page.

  2. Click the User Categories tab.

  3. Click DEFAULT. Click the Notifications tab.

  4. Click the Edit button.

  5. If you want to turn on a specific event notifications, click the template for the desired event.

  6. On the Template Information page, select the Enabled check box and click Save and Close.

  7. Click the Save button.

  8. Click the Done button.

Import FCLs and DCLs

You must pass #NULL value for the FCL field in order to nullify a value for an FCL using Import Management.

Here is an example to nullify TargetGlobalPJDetailFlag1_c field:

PartyId TargetGlobalPJDetailFlag1_c

100000001527765

#NULL

How You Enable Survivorship During Import

Survivorship on update is available for the following four Import Management objects:

  • Account

  • Organization

  • Contact

  • Person

You include the data that you want to import into CX Sales and B2B Service in a source CSV file. This CSV file depends upon the object you want to import. Before you start importing, check that the CSV file contains the SourceSystem value. For more information, see Import Your Account Data, Import Your Contact Data, Import Your Person Data, and Import Your Organization Data topics in this guide.

Enable Survivorship

After you have the CSV file ready, create an import activity to import the account information and enable survivorship as follows:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select either Account, Organization, Contact, or Person from the Object drop-down list.

  4. Click to expand Advanced Options section.

  5. Select Enable survivorship logic.

    Note: This option is available only if the selected import object is Account, Organization, Contact, or Person and attribute survivorship has been already configured. High-Volume import mode is supported, if the survivorship configuration only uses Source Confidence. If Data Quality Rules are enabled, High-Volume mode import isn't available.

    You can continue to import and review the import results.

You can then import data. For more information on how to import data, see Import Data topic in Related Topics section.

Import Data

Import Your Account Data

You can use Import Management to create, update, or delete your account data.

You can import account records using these steps:

  1. Map your source account data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.

  2. Create the source CSV file with the account data you want to import.

  3. Kick off an import activity.

  4. Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

You import account data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.

You need to do the following before creating the .csv file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your objects.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

  • Identify the target object attributes that are required in the .csv file for a successful import

Note: You can enable automatic territory-based assignment after sales accounts are imported. You can enable this feature by turning the profile option ZCA_BATCH_ASSIGN_ON_BULK_IMPORT ON. If the profile option is disabled, then you must manually run a batch assignment or assign each sales account individually.

To better manage your account information, the account object has the following child objects:

  • Address

  • Classification

  • Relationship

  • Sales Team Member

Note: You can't set an attribute value to NULL in high-volume import (import management with the option Enable High-Volume Import selected). However, when updating a record, you can change an attribute value from NOT NULL to NULL

If you're importing account records with attributes specific to the parent account object or along with single child record details (like phone, email, address, and so on), then you can include the child record details in the same .csv file for account object. However, if you're importing multiple records of any child object, then you must create multiple .csv files to import- one for each child which has multiple records that you're importing. For example, if you're importing 5 emails, 5 phones, and 5 addresses for an account, then you must create three import files - one for Account object, one for Contact Point object (phone and email), and one for Address object. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.

Note: High-volume import for accounts now supports hierarchy management and generation.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data. For example, when using source system reference information to identify your account records, the source system of the account object should be enabled for parties using the Manage Trading Community Source Systems task.

  • You have all parent records in place before importing child records. For example, when importing the address of an account, ensure the account exists.

Select a Unique Identifier for Your Records

All records must be unique in the application. You can use one of these to identify records:

  • Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For account object, the attribute is PartyNumber and shows up in the UI as Party Number. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

  • Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new accounts or are updating accounts that have source system reference data, then provide the source system and source system reference values. For account object, these are SourceSystem and SourceSystemReferenceValue and show up as Party Source System and Party Source System Reference Value in the UI.

Review Required Attributes and Validations for Account Object

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.

This table lists the required attributes for account records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Tasks or Import Validations Creating an Account Record Updating an Existing Account Record Deleting an Existing Account Record

SourceSystem

The source system for the sales account.

Know the source system.

To view source systems, use the Manage Trading Community Source System task.

Conditionally Required

To identify an account record, use one of these:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required

To identify an account record, use one of these:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required

To identify an account record, use one of these:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

SourceSystemReferenceValue

The reference number or text representing the source system unique ID for the party (account or contact) to which the sales profile belongs.

Know the source system reference value.

To view the source systems reference, use the Manage Trading Community Source System task.

Conditionally Required

To identify an account record, use one of these:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required

To identify an account record, use one of these:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required

To identify an account record, use one of these:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

PartyNumber

The public unique identifier of the party.

The party must exist.

You get a list of all party IDs and party numbers by exporting the Party object.

Conditionally Required

Conditionally Required

Conditionally Required

OrganizationName

The name of the party of the Organization party type.

Organization names are listed in the Resource Directory.

Required

Conditionally Required

Conditionally Required

OwnerPartyId

The identifier of the account owner.

This attribute is required only in import management, but optional in high-volume import.

Required

Not Required

Not Required

Note: Provide a valid value for the DataFox Company ID import attribute to integrate DataFox with CX Sales and B2B Service.
Note: When deleting or updating accounts, you must ensure that the account related to the party number provided has the Sales Account usage. If you provide the party number of an account that doesn't have the Sales Account usage, then the relationships for that account are also deleted. For example, if you provide the party number ORA17292 that doesn't have a Sales Account usage, then the related partners, contacts, and so on are also deleted.

For the extension child objects of account, RecordName field isn't unique. Hence you can't update the records only by passing RecordName.

You can use the profile option ORA_HZ_IMPORT_MULTI_ADDRESS_TYPE to control how address types are entered. By default this profile option is set to Yes, so you can enter multiple address types, during high-volume import of Account, Contact, and Household objects . You can disable this profile option to improve the import performance. When you set this profile option to No, you can enter only a single address type.

Note: When importing accounts or legal entities, you can retrieve duplicates using the Customer Data Management Duplicates LOV 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. After the keys are rebuilt, the matching functionality uses the settings in the match configuration to identify duplicates.

Go to Navigator > Tools > Import Management > Import Objects to see all the attributes of the account object. The page also lists attribute information like type, length, description, and so on.

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Account object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Providing the ZIP and Country Code values in the import CSV file won't automatically populate the State/County/City fields. Values for these fields should be separately provided in the import file.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the account information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Account from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Note: After importing your data successfully, you need to run a couple of post processing jobs for duplicate identification, duplicate resolution, and account assignment. For more information on import management post processing jobs, see the topic: Import Management Post Processing for Accounts and Contacts.

When importing accounts using high-volume import, you can now load the account hierarchy data. Use the following attributes to import accounts using high-volume import:

  • ParentAccountPartyId

  • ParentAccountPartyNumber

  • ParentAccountSourceSystem

  • ParentAccountSourceSystemReferenceValue

Note: This is available only for low volume data and should not be used for high volume data.

You can load account hierarchy data. To load the account hierarchy data:

  1. Load the account data without providing values for the parent attributes mentioned above.

  2. Load the account hierarchy using the Hierarchy and Hierarchy Member import objects.

Import Your Contact Data

You can use the Import Management to create, update, or delete contact records.

You can import contact records using these steps:

  1. Map your source contact data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.

  2. Create the source CSV file with the contact data you want to import.

  3. Kick off an import activity.

  4. Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

To import your contact data into Oracle Applications Cloud, you must populate a .csv file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You must do the following before creating the .csv file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your objects.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

  • Identify the target object attributes that are required in the .csv file for a successful import

To better manage your contact information, the contact object has the following child objects:

  • Address

  • Classification

  • Relationship

  • Sales Team Member

Note: You can't set an attribute value to NULL in optimized import (standard import with the option Enable High-Volume Import selected). However, when updating a record, you can change an attribute value from NOT NULL to NULL

If you want to import only a few records, then you can create a single CSV file for all contact attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the contact child objects. Note that you must have imported the CSV file for contact object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

All records must be unique in the application. You can use one of these to identify records:

  • Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

  • Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new contacts or are updating contacts that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for the Contact Object

To import data successfully into Oracle Applications Cloud, your .csv file must include the required attributes. Ensure that you provide valid values for the attributes.

This table lists the required attributes for contact records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task or Import Validations Creating a Contact Record Updating an Existing Contact Record Deleting an Existing Contact Record

SourceSystem

The code representing the source system for the contact.

Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Applications Cloud using the Source System Reference import object.

Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

SourceSystemReferenceValue

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

Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Applications Cloud using the Source System Reference import object.

Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required For uniquely identifying a contact record, provide one of the following reference information:

  • SourceSystem and SourceSystemReferenceValue

  • PartyNumber

PartyNumber

The public unique identifier of the contact.

No prerequisite tasks

Conditionally Required

Conditionally Required

Conditionally Required

FirstName

First name of a person party.

No prerequisite tasks

Required

Not required

Not required

LastName

Last name of a person party.

No prerequisite tasks

Required

Not required

Not required

Note: For the Time Zone import attribute, specify the time zone of the contact to know the preferred time to call or send e-mail to the contact.

You can use the profile option ORA_HZ_IMPORT_MULTI_ADDRESS_TYPE to control how address types are entered. By default this profile option is set to Yes, so you can enter multiple address types, during high-volume import of Account, Contact, and Household objects . You can disable this profile option to improve the import performance. When you set this profile option to No, you can enter only a single address type.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the contact object. The page also lists attribute information like type, length, description, and so on.

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Contact object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Providing the ZIP and Country Code values in the import CSV file won't automatically populate the State/County/City fields. Values for these fields should be separately provided in the import file.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the contact information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Contact from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Note: After importing your data successfully, you need to run a couple of post processing jobs for duplicate identification, duplicate resolution, and account assignment. For more information on import management post processing jobs, see the topic: Import Management Post Processing for Accounts and Contacts.

Import Your Country Structure Data

You can use Import Management to create Country Structure records. It is recommended you use Import Management only if you're importing high-volume third-party data. If you 're importing licensed data from one of our vendors, then you can create the country structure by navigating to Setup and Maintenance > Manage Geographies Task page.

To import Country Structure records, perform the following tasks:

  1. Map your source data to Oracle Applications Cloud object attributes.

  2. Create source Comma Separated Values (CSV) file for import.

  3. Create the import activity.

  4. Review the import results.

How You Map Your Source Data to Target Object Attributes

To import your Country Structure data into Oracle Applications Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You need to do the following before creating the CSV file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

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

Required Attributes and Validations for Country Structure Object

To import data successfully into Oracle Applications Cloud, your CSV file must include values for the required attributes. This table lists the required attributes for importing new Country Structure records, prerequisite setup tasks for the attributes, and specific validations, if any, for Country Structure import:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Country Structure Record

CountryCode

The code for the country for which the country structure is applicable.

The GeographyType has to be "Country" and the LevelNumber has to be "1" for a country.

You can't pass different country codes when importing a record.

Yes

GeographyType

Geopolitical divisions such as Country, State, City, and so on. For example, for US the different geography types would be State, County, City, and Postal Code. For India, the different geography types would be State, District, City, and Postal Code. For Mexico, it would be State, Municipality, Locality, and Postal Code.

The country has to be present.

Yes

LevelNumber

You need these to create parent-child relationships between geography types for your country. The values can be 1, 2, 3, and so on.

To define a country, you must specify the LevelNumber as 1.

Yes

You can view the Country Structure object and its attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on the Manage Import Objects page. You can view the list of valid values for country codes in the UI by navigating to the Manage Geographies task and searching with % as the Country Code value. For more information on Geographies, see Overview of Geographies, Geographic Entities, and Locations in the Related Topics section.

Note: Note the following:
  • The import job will fail if you try to load any already existing country structure. Delete the existing country structure in the UI in Manage Geographies Tasks and import again.

  • You can't load additional lower geography structure levels for an existing country structure while importing geography country structure. You can add additional geography levels in the UI for an existing country structure in the Manage Geographies task page.

Create the Source CSV File

You include the data that you want to import into Oracle Applications Cloud in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Country Structure object in the table and click Download.

You can now edit the downloaded file and provide values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Country Structure from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Click Validate Data to check the file for unmapped columns or data format issues. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity. Here, you can download and review the successfully imported user data records, the mapping details used for import activity, and the data file that you provided in CSV format.

Example of Importing Country Structure Data

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.

To add a country structure using import management, your source file must contain information about the country to which the country structure belongs. You can view the list of valid values for country codes in the UI by navigating to the Manage Geographies task and searching with % as the Country Code value. 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 a country structure, your source file must include the values that let the import process identify the existing records.

Sample Input CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file. Here is a sample input CSV file for country as US.
CountryCode LevelNumber GeographyType

US

1

COUNTRY

US

2

STATE

US

3

COUNTY

US

4

CITY

US

5

POSTAL CODE

Here is another input CSV file for importing the country structure for India.

CountryCode LevelNumber GeographyType

IN

1

COUNTRY

IN

2

STATE

IN

3

DISTRICT

IN

4

CITY

IN

5

POSTAL CODE

In case you want to import the country structure for Mexico, your input CSV file would look like this:

CountryCode LevelNumber GeographyType

MX

1

COUNTRY

MX

2

STATE

MX

3

MUNICIPALITY

MX

4

LOCALITY

MX

5

POSTAL CODE

In this example, we are importing the Country Structure for US. You must create a source file (CSV) file with the attributes as shown in this table and import it using Import Management.

Attribute Name Value Description

CountryCode

US

The code for the country for which the country structure is applicable.

LevelNumber

1

The level number of the geography in the hierarchy. For example, Country is at Level 1 (Top level) and State (California) is at Level 2. You need these to create parent-child relationships between geography types for your country.

GeographyType

COUNTRY

Geopolitical divisions such as Country, State, City, and so on. For example, for US the different geography types would be State, County, City, and Postal Code. For India, the different geography types would be State, District, City, and Postal Code. For Mexico, it would be State, Municipality, Locality, and Postal Code.

Create an import activity to import the information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Country Structure from the Object drop-down list.

    Note: In the Advanced Options section, the option Enable High-Volume Import is selected by default. This mode is designed to import millions of records at once.

  4. Select the CSV file in the File Name field, and click Next.

  5. The source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit.

Import Your Geography Data

You can use Import Management to create Geography records. You can also add alternate name or code to existing geographies with import. For more information see Example of Importing Geography Data in the Related Topics section.

To import Geography records, perform the following tasks:

  1. Map your source data to Oracle Applications Cloud object attributes.

  2. Create source Comma Separated Values (CSV) file for import.

  3. Create the import activity.

  4. Review the import results.

How You Map Your Source Data to Object Attributes

To import your Geography data into Oracle Applications Cloud, you must populate a .csv file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You need to do the following before creating the CSV file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Create Country Structure before importing Geography data. For information on how to create Country Structure, see Import Your Country Structure and Example of Importing Country Structure in Related Topics Section.

  • Identify the target object attributes that are required in the CSV file for a successful import as mentioned in the table Required Attributes and Validations for the Geography Object below.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data such as creating a country structure.

Required Attributes and Validations for the Geography Object

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure that you provide values for the attributes. The following table lists the required attributes for importing new Geography records, prerequisite setup tasks for the attributes, and specific validations, if any, for Geography import:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Geography Record

CountryCode

The code of the country to which the geography belongs.

This is validated against the country structure to check if the structure is defined for this country.

Required

PrimaryGeographyName

The primary name of the geography.

This is validated against the name of country if geography type is 'Country' or LevelNumber is 1.

Required

RecordTypeCode

The record type code that represents the intent of the import data. The values are:

  • 0 - indicates the geography that already exists in the base table.

  • 1 - indicates the intent to create a new geography.

  • 2 - indicates the intent to add an alternate identifying name or code to an existing geography.

No Validation

Required

LevelNumber

The level number of the geography in the hierarchy. For example, Country is at Level 1 and State (California) is at Level 2.

The level should exist in the country structure.

Required

SourceID

The source ID for the geography, along with the parent source ID is used to identify the geography parent and child relationship within the source file data and the interface table data.

None

Required

ParentSourceID

The parent source ID for the geography, along with the source ID is used to identify the geography's parent and child relationship with records within the source file data. This should be null for the country record, as Country is at the top of the hierarchy.

None

Required

You can view the Geography object and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this Manage Import Objects page.

Note: Keep a note of the following:
  • You can't update geographies via import.

  • Before adding a new alternate name, make sure that the alternate name does not exist with the same value for any other geography name.

  • You can enable high-volume import for the Geography import object in the Manage Import Objects page.

  • PrimaryGeographyCodeType and PrimaryGeographyCode can't be added after PrimaryGeographyName is created via import. You must create them together. Alternatively, you can add primaryGeographyCodeType and PrimaryGeographyCode from the UI after the import is complete.

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Geography object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Geography from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. The source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Note: Geography names aren't 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.

Example of Importing Geography Data

This example demonstrates how to import data using Import Management. In this example, you have a source file containing geography data that you want to import into the application to make the geography data available for real time address validation and tax purposes. A geography is any region with a boundary around it, regardless of its size. It might be a state, a country, a city, a county, or a ward.

Summary of the Tasks

You perform the following steps to create an import activity and activate the import:

  1. Determine what information is in the source file.

  2. Create and schedule the import activity.

Before You Start

  1. You use the country structure of a country to define which geography types are part of the country. For more information about an example of importing a country structure, see the topic "Example of Importing Country Structure Data".

  2. Ensure that Source ID values are unique for each row of data within a single import.

  3. Ensure that all the parents of a child geography are included in your data file so that the child geography can be added. For example, if you originally imported US, CA, and San Francisco, and now you want to import the city of San Jose in CA, then your data file must include US, CA, and San Jose.

  4. Check that your source data file has the correct values for the geography data that you have already loaded. For example, if your initial import included the value US for country and CA as state, and in a subsequent import you have California as a state, then your geography import creates two state records (CA and California) in the application data, with the US as the country parent.

Determine the Information in the Source File

The source geography data files must include a unique Source ID value for each row of data and Parent Source ID value for the parent of that row of data. You include the data that you want to import into CX Sales and B2B Service in a source CSV file. A sample input CSV file for country as US is shown in this table.
RecordTypeCode PrimaryGeographyName CountryCode LevelNumber SourceId ParentSourceId LanguageCode

0

United States

US

1

1

<blank>

US

1

California

US

2

11

1

US

1

San Mateo

US

3

111

11

US

1

Redwood City

US

4

1111

111

US

1

94065

US

5

11111

1111

US

Here is a sample CSV file to import geographies with alternate name and code for country India:

RecordType PrimaryGeographyName CountryCode LevelNumber SourceId ParentSOurceId IdentifierType IdentifierSubType IdentifierValue

0

India

IN

1

1

1

Karnataka

IN

2

2

1

1

Bengaluru

IN

3

3

2

2

Bengaluru

IN

3

3

2

NAME

Standard_Name

Bangalore

1

Whitefield

IN

4

4

3

1

560066

IN

5

5

4

2

560066

IN

5

5

4

CODE

ISO_COUNTRY_CODE

91

Note: Note the following:
  • The hierarchy is modeled in the CSV file using the SourceId and ParentSourceId. The ParentSourceId for the Country Record (level Number 1) is always null.

  • If defining an alternate name (RecordTypeCode = 2) for any level below the country (LevelNumber >1), ensure that the SourceId and ParentSourceId columns match the values for the original record respectively.

  • You can't update geographies via import.

  • Before adding a new alternate name, make sure that the alternate name doesn't exist with the same value for any other geography name. You can check the existing values for alternate names in the Manage Geographies task page under Hierarchy Defined.

  • You can find the list of IdentifierSubTypes in Manage Geography Lookups page in the UI.

  • PrimaryGeographyCodeType and PrimaryGeographyCode can't be added after PrimaryGeographyName is created via import. You must create them together. Alternatively, you can add PrimaryGeographyCodeType and PrimaryGeographyCode from the UI after the import is complete.

You must create a source file (CSV) file with the attributes and import it using import management as shown in this table.

Attribute Name Value Description

RecordTypeCode

1

The record type code that represents the intent of the import data. The values are:

  • 0 - indicates the geography that already exists in the base table.

  • 1 - indicates the intent to create a new geography.

  • 2 - indicates the intent to add an alternate identifying name or code to an existing geography.

PrimaryGeographyName

India

This is the primary geography name. This will be marked as the primary name for the Geography and also displayed in the Manage Geographies Page.

CountryCode

IN

This indicates the Country Code for the country for which you're importing data.

LevelNumber

2

The level number of the geography in the hierarchy. For example, Country is at Level 1 and State (California) is at Level 2.

SourceId

2

The source ID for the geography, along with the parent source ID is used to identify the geography parent and child relationship within the source file data and the interface table data.

ParentSourceId

1

The parent source ID for the geography, along with the source ID is used to identify the geography's parent and child relationship with records within the source file data. This should be null for the country record, as Country is at the top of the hierarchy.

IdentifierType

Name

The type of the identifier. It can be either Name or Code.

IdentifierSubtype

Standard_Name or Standard_Code

The IdentifierSubtype can be Standard_Name or Secondary_Name. The default value is Standard_Name.

The valid Sub Types for Type "CODE" are FIPS_CODE, GEO_CODE, ISO_COUNTRY_CODE, PRIMARY_CITY, or UNKNOWN

IdentifierValue

Bangalore

The value of the identifier.

You can create an import activity, enter the import details, and schedule the import.

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Geography from the Object drop-down list.

    Note: In the Advanced Options section, the option Enable High-Volume Import is selected by default. This mode is designed to import millions of records at once.

  4. Select the CSV file in the File Name field, and click Next.

  5. The source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit.

Import Your Hierarchy Data

You can use the import functionality to create or update Hierarchy records.

The hierarchies supported are:

  • Customer hierarchy

  • Dun and Bradstreet hierarchy

  • Trading Community Party hierarchy

To import Hierarchy records, perform the following tasks:

  1. Map your source data to Oracle Applications Cloud object attributes.

  2. Create source Comma Separated Values (.csv) file for import.

  3. Create the import activity.

  4. Review the import results.

How You Map Your Source Data to Target Object Attributes

To import your Hierarchy data into Oracle Applications Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You need to do the following before creating the .CSV file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your objects.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

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

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Applications Cloud.

The preferred option to uniquely identifying an object record is the Internal ID. If you're identifying a record that already exists in Oracle Applications Cloud, then you can use the internal ID of the record, a system-generated unique identifier Attributes with "ID" in the attribute name are typically internal IDs. Use this option only if you're updating Hierarchies. You can determine the internal ID of a record by exporting Oracle Applications Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Hierarchy object, the attributes are TreeStructureCode, TreeCode, TreeName, and TreeVersionName.

Required Attributes and Validations for Hierarchy Object

To import data successfully into Oracle Applications Cloud, your .CSV file must include the required attributes. Ensure that you provide valid values for the attributes.

The following table lists the required attributes for importing new Hierarchy records, required attributes for updating Hierarchy records, prerequisite setup tasks for the attributes, and specific validations, if any, for Hierarchy import:

Attribute Description Data Type Data Length Prerequisite Setup Task/ Import Validations Creating a Hierarchy Record Updating an Existing Hierarchy Record

TreeStructureCode

Unique identifier for a tree structure.

Varchar2

30

Seeded data needs to be present.

Required

Required

TreeCode

User defined Identifier for the tree code.

Varchar2

30

No validation

Required

Required

TreeName

Name of the tree

Varchar2

80

No validation

Required

Not Required

TreeVersionName

Version Name of the tree

Varchar2

80

No validation

Required

Not Required

LangCode

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

Varchar2

4

No validation

Required

Not Required

AsofDate

The date that's used to determine the tree version when you're updating a tree version.

Date

No validation

Optional

Required

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

Create the Source CSV File

The .CSV file is provided as input to the file-based data import process. You must populate the .CSV file with the data you want to import into Oracle Applications Cloud.

You can either create a CSV file on your own or use templates available in preexisting mappings. To download a template, do the following:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Hierarchy object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

To import data into Oracle Applications Cloud, you need to create an import activity and provide the CSV file as an input to the activity.

To create an import activity, do the following:

  1. In the Navigator, under Tools, click Import Management.

  2. In the Manage Imports page, click Create Import Activity.

  3. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Hierarchy from the Object drop-down list.

  4. In File Name, browse and upload the required .CSV file, and click Next.

  5. In the Create Import Activity: Map Fields page edit the attribute mappings if required, and click Next.

    Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues.
  6. In the Create Import Activity: Review and Submit page, click Submit.

    Note: Initiate the Tree Flattening Service manually. Do one of the following:
    • From the navigator, select Scheduled Processes. In the Schedule New Process dialog, search for Party Hierarchy Generation and click OK.

    • From Setup and Maintenance, search and run the Trading Community Party Hierarchy Generation task.

Review the Import Results

You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:

  1. In the Navigator, under Tools, click Import Management.

  2. On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.

Note: On this page you can also quickly view the number and status of all active imports, completed imports, and unsuccessful imports that have been submitted.

Import Your Household Data

You can use Import Management to create or update Household records.

To import Household records, perform the following tasks:

  1. Map your source data to Oracle Applications Cloud object attributes.

  2. Create source Comma Separated Values (.csv) file for import.

  3. Create the import activity.

  4. Review the import results.

How You Map Your Source Data to Target Object Attributes

To import your Household data into Oracle Applications Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You need to do the following before creating the .CSV file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite steps are complete, such as understanding what attributes are required for importing your objects.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

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

Note: You can't set an attribute value to NULL in optimized import (standard import with the option Enable High-Volume Import selected). However, when updating a record, you can change an attribute value from NOT NULL to NULL

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Applications Cloud.

The preferred options to uniquely identify an object record are as follows:

  • Internal ID: If you're identifying a record that already exists in Oracle Applications Cloud, then you can use the internal ID of the record, a system-generated unique identifier Attributes with "ID" in the attribute name are typically internal IDs. Use this option only if you're updating Households. You can determine the internal ID of a record by exporting Oracle Applications Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Household object, the attributes are OwnerPartyId and PartyId.

  • Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Household object, the attribute is PartyNumber.

Required Attributes and Validations for Household Object

To import data successfully into Oracle Applications Cloud, your .CSV file must include the required attributes. Ensure that you provide valid values for the attributes.

The following table lists the required attributes for importing new Household records, required attributes for updating Household records, prerequisite setup tasks for the attributes, and specific validations, if any, for Household import:

Attribute Description Data Type Data Length Prerequisite Setup Task/ Import Validations Creating a Household Record Updating an Existing Household Record

SourceSystem

The code representing the source system for the household

String

30

Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Applications Cloud using the Source System Reference import object.

Optional

Required

SourceSystemReferenceValue

The reference number or text representing the source system unique ID for the household

String

240

Identify the source system or configure source systems either by using the Manage Trading Community Source System task, or by importing the source system information into Oracle Applications Cloud using the Source System Reference import object.

Optional

Required

PartyNumber

The public unique identifier of the party.

String

30

Identify the party number value by exporting the Household object.

Optional

Required

PartyId

The public unique identifier of the party

Long

18

Identify the party number value by exporting the Household object.

Optional

Required

Name

The name of the household

String

360

Identify the organization name of the resource by navigating to the Resource Directory.

Required.

Conditionally required

OwnerPartyId

Indicates the party ID of the resource who's designated as the owner of the household

Long

18

None.

Conditionally required.

Conditionally required

You can use the profile option ORA_HZ_IMPORT_MULTI_ADDRESS_TYPE to control how address types are entered. By default this profile option is set to Yes, so you can enter multiple address types, during high-volume import of Account, Contact, and Household objects . You can disable this profile option to improve the import performance. When you set this profile option to No, you can enter only a single address type.

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

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Household object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Household from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Import Your Hub Source System Reference Data

You can use Import Management to create or update Hub Source System Reference records.

To import Hub Source System Reference records, perform the following tasks:

  1. Map your source data to Oracle Applications Cloud object attributes.

  2. Create source Comma Separated Values (CSV) file for import.

  3. Create the import activity.

  4. Review the import results.

How You Map Your Source Data to Target Object Attributes

To import your Hub Source System Reference data into Oracle Applications Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You need to do the following before creating the CSV file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite setups are done, if applicable.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

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

  • Ensure that you don't insert duplicate addresses while importing, to avoid redundant data.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

All records must be unique in the application. You can use one of these to identify records:

  • Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

  • Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new hub source system reference records or are updating hub source system reference records that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Hub Source System Reference Object

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes. This table lists the required attributes for importing new Hub Source System Reference records, required attributes for updating Hub Source System Reference records, prerequisite setup tasks for the attributes, and specific validations, if any, for Hub Source System Reference import:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Hub Source System Reference Record Updating an Existing Hub Source System Reference Record

OwnerEntityId

Internal identifier or primary key of a record that exists in the OSC table

If provided, it has to be an active primary key value from the table name provided for the OwnerEntityObject.

If you export data from the OSC table provided for the OwnerEntityObject, provide the primary key data to this attribute. If you can't provide this data, provide valid values for the combination of ExistingSourceSystem and ExistingSourceSystemReferenceValue.

Not required

StartDateActive

The date on which the hub source system reference becomes valid.

If provided, this date should be earlier than the end date. If you don't specify a date, this defaults to the current date.

Optional

Optional

EndDateActive

The date on which the hub source system reference is no longer valid.

If provided, this date should be later than the start date. If you don't specify a date, this defaults to 12/31/4712.

Optional

Optional

SourceSystem

Specifies the original source system name

This has to be present in the HZ_ORIG_SYSTEMS_B table with the status "A".

Provide a valid value.

Conditionally required.

Provide one of the following:

  • SourceSystemReferenceId

  • A combination of SourceSystem, SourceSystemReference and OwnerEntityObject

SourceSystemReferenceValue

Specifies the original source system reference text or number in the original source system

No validation

Provide a valid value.

Conditionally required.

Provide one of the following:

  • SourceSystemReferenceId

  • A combination of SourceSystem, SourceSystemReference and OwnerEntityObject

OwnerEntityObject

Specifies the OSC table in which the record exists

This has to be a valid lookup code in the lookup type ORA_ZCH_OWNER_ENTITY_OBJECT.

Provide a valid value.

Conditionally required.

Provide one of the following:

  • SourceSystemReferenceId

  • A combination of SourceSystem, SourceSystemReference and OwnerEntityObject

SourceSystemReferenceId

Specifies the source system reference identifier. This is a primary key.

If provided, this has to be an active primary key value from the table HZ_ORIG_SYS_REFERENCES.

Not required

Conditionally required.

Provide one of the following:

  • SourceSystemReferenceId

  • A combination of SourceSystem, SourceSystemReference and OwnerEntityObject

ExistingSourceSystem

Specifies the original source system name of data that exists in Oracle Engagement Cloud

This has to be present in the HZ_ORIG_SYSTEMS_B table with status "A".

If you can't provide the OwnerEntityID, provide a combination of ExistingSourceSystem and ExistingSourceSystemReferenceValue values. Export the Source System Reference repository to obtain this value.

Not required

ExistingSourceSystemReferenceValue

Specifies the original source system reference of data that exists in Oracle Engagement Cloud

No validation

If you can't provide the OwnerEntityID, provide a combination of ExistingSourceSystem and ExistingSourceSystemReferenceValue values. Export the Source System Reference repository to obtain this value.

Not required

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

Note: A lookup type ORA_ZCH_OWNER_ENTITY_OBJECT is now available. You can now use this lookup without specifying the underlying physical tables, when providing input data in the CSV import file. When you migrate from File-Based Data Import to Optimized or Import Management, the underlying physical tables are secured to external parties.

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Hub Source System Reference object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Hub Source System Reference from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Import Your Organization Data

You can use Import Management to create or update Organization records.

To import Organization records, perform the following tasks:

  1. Map your source data to Oracle Applications Cloud object attributes.

  2. Create source Comma Separated Values (CSV) file for import.

  3. Create the import activity.

  4. Review the import results.

How You Map Your Source Data to Target Object Attributes

To import your Organization data into Oracle Applications Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You need to do the following before creating the CSV file for data import:

  • Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.

  • Ensure prerequisite setups are done, if applicable.

  • Understand your options for uniquely identifying the records.

  • Ensure parent records exist before importing child records.

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

  • Ensure that you don't insert duplicate addresses while importing, to avoid redundant data.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

All records must be unique in the application. You can use one of these to identify records:

  • Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

  • Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new organizations or are updating organizations that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Organization Object

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes. This table lists the required attributes for importing new Organization records, required attributes for updating Organization records, prerequisite setup tasks for the attributes, and specific validations, if any, for Organization import:

Attribute Description Prerequisite Setup Task/ Import Validations Creating an Organization Record Updating an Existing Organization Record

SourceSystem

The original source system name

Know the source system.

To view source systems, use the Manage Trading Community Source System task.

Conditionally Required

To identify an organization record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required

To identify an organization record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

SourceSystemReferenceValue

The identifier in the original source system

Know the source system reference value.

To view the source systems reference, use the Manage Trading Community Source System task.

Conditionally Required

To identify an organization record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally Required

To identify an organization record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

PartyNumber

The public unique identifier of the party.

Know party number.

To obtain a list of all party IDs and party numbers, export the Party object.

Conditionally Required

Conditionally Required

OrganizationName

The name of the party of the Organization party type.

The organization names are listed in the Resource Directory.

Required

Conditionally Required

PartyUsageCode

Specifies the party usage code to which the organization is associated

This should be an active value in the HZ_PARTY_USAGES_B table.

Required

Not required

CleanlinessScore

The overall score for the account or contact record for the category Cleanliness

No validation

Optional

Optional

CompletenessScore

The overall score for the account or contact record for the category Completeness

No validation

Optional

Optional

DataConfidenceScore

The overall data confidence score that indicates the level of data quality for a record

No validation

Optional

Optional

DatafoxCompanyId

A unique identifier for the "Datafox" company

No validation

Optional

Optional

DuplicateIndicator

Signifies the duplicate status of the record that's determined as follows:

  • A null value indicates that the record isn't a duplicate or hasn't been evaluated.

  • The record can also have one of 2 other values - DUPE (record is a duplicate) or LINK (record is linked to another record).

No validation

Optional

Optional

DuplicateScore

The overall score for the account or contact record for the category Duplicate

No validation

Optional

Optional

EnquiryDuns

A unique identifier used to query the Dun and Bradstreet data. If the location is a branch, in some countries the "DUNS" number of the headquarters is used to run the query. Otherwise, the "DUNS" number is considered.

No validation

Optional

Optional

EnrichmentScore

The overall score for the account or contact record for the category Enrichment

No validation

Optional

Optional

LastScoreUpdateDate

The date and time at which this record was updated by the source system in the last update source system column

No validation

Optional

Optional

RecencyScore

The overall score for the account or contact record for the category Recency

No validation

Optional

Optional

ThirdPartyFlag

This option tracks if a party has a direct relationship with the organization using Oracle receivables or through a third party supplier. The value Y denotes third party relationship, while the value N denotes direct relationship. If Oracle Service is installed, the Third Party field in the Customers window is mandatory.

No validation

Optional

Optional

ValidatedFlag

Indicates if the party was validated. The value Y denotes a validated party, while the value N denotes a party that's not validated.

No validation

Optional

Optional

ValidityScore

The overall score for the account or contact record for the category Validity

No validation

Optional

Optional

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

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Organization object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Organization from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.

Import Your Person Data

You can use the import functionality to create or update Person records.

You can import Person records using these steps:

  1. Map your source data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.

  2. Create the source CSV file with the Person data you want to import.

  3. Kick off an import activity.

  4. Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

You import Person data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.

Before you create the source data file, you should:

  • Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the Person import object.

  • Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.

  • Know how you can uniquely identify the records.

  • Check the target object attributes required in the CSV file for a successful import.

  • Ensure that you don't insert duplicate Person while importing, to avoid redundant data.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

  • You have completed all the prerequisites for importing each attribute in your source data.

  • You have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

All records must be unique in the application. You can use one of these to identify records:

  • Public unique identifiers: You can pass the PUID when creating Person records. If the PUID isn't passed, it will be auto generated. You can optionally provide the PUID when creating Person records. If you're updating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

  • Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new Persons or are updating Persons that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Person Object

To import data successfully into Oracle Applications Cloud, your .CSV file must include the required attributes. Ensure that you provide valid values for the attributes.

This table lists the required attributes for Person records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Person record Updating an Existing Person record

PartyId

The internal ID for the Person type party

When updating the record, this should already exist.

Not required

Conditionally required.

To identify a person record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

  • PartyId

Country

The country code of the postal address

Identify valid country codes using the Setup and Maintenance, Manage Territories task.

Conditionally required

A value is required only when you're creating an address for the Person record.

The attribute is neither required nor conditionally required.

AddressNumber

The internal unique identifier that's internally generated when creating an address

No validation

This is a PUID for Address. If a value is passed, it will be imported. Otherwise, it will be auto-generated.

Pass the AddressNumber.

OrganizationPartyNumber

The party number of the organization to which the person is related

This should already exist.

Not required

Not required

DeceasedFlag

The option that indicates whether the person imported is deceased

Y or N

The default value is N.

Not required

Not required

PartyNumber

The unique identifier of the party

Know the party number. To obtain a list of all party IDs and party numbers, export the Person object.

This is a PUID for Person. If a value is passed, it will be imported. Otherwise, it will be auto-generated.

Conditionally required

To identify a person record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

  • PartyId

FirstName

The first name of the person

No validation

Required. A value is required for the FirstName, MiddleName, or LastName.

Not required

MiddleName

The middle name of the person

No validation

Required. A value is required for the FirstName, MiddleName, or LastName.

Not required

LastName

The last name of the person

No validation

Required. A value is required for the FirstName, MiddleName, or LastName.

Not required

PartyUsageCode

Specifies the party usage code to which the person is associated

Select one of the following values:

  • EXTERNAL_PAYEE

  • CONTACT

  • PAYMENT_ISSUING_AUTHORITY

  • PARTY_OF_INTEREST

  • VIRTUAL_ASSISTANT

  • FS_TECH

You can assign a limited set of unrestricted party usages through the Person import object. To create persons of other types, use the specific import objects created for those purposes.

Required

Not required

SourceSystem

The original source system name

Know the source system. To view source systems, use the Manage Trading Community Source System task.

Conditionally required

To identify a person record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally required

To identify a person record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

  • PartyId

SourceSystemReferenceValue

The identifier in the original source system

Know the source system reference value. To view source system reference, use the Manage Trading Community Source System task.

Conditionally required

To identify a person record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

Conditionally required

To identify a person record, use one of these:

  • Combination of SourceSystem and SourceSystemReferenceValue

  • PartyNumber

  • PartyId

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the Person object. The page also lists attribute information like type, length, description, and so on.

Create the Source CSV File

You include the data that you want to import into CX Sales and B2B Service in a source CSV file.

You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Person object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the Person information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. On the Manage Imports page, click Create Import Activity.

  3. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Person from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.