9Import Your Data

This chapter contains the following:

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

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 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 account 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 account child objects. Note that you must have imported the CSV file for account 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.

Note: Optimized 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.

Know party number.

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

Note: Provide a valid value for the DataFox Company ID import attribute to integrate DataFox with CX Sales and B2B Service.

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.

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.

Import Your Action Data

You can use the import functionality to create, update, or delete your action data.

You can import action 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 action 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 action 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 action 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.

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

  • Action Attribute

  • Action Condition

If you want to import only a few records, then you can create a single CSV file for all action 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 action child objects. Note that you must have imported the CSV file for action 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 actions or are updating actions that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Action 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 action records, prerequisite setup tasks and specific validations, if any:

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

Action

The name of the action that's associated associated with an action plan template or action plan instance.

None

Required

Not required

Action Id

The unique Id of the existing Action record in the Oracle Fusion destination table.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Required

A value is required if you're updating an existing Action and you're not providing the Action Number. The Action ID is autogenerated in Oracle Fusion applications, if you don't specify a value.

ActionNumber

The unique ID for the existing Action record in the Oracle Fusion destination table.

None

Optional

A value is required if you're updating an existing Action and you're not providing the Action Id.

Parent Entity Name

The entity name of the object for which the action can be used in an action plan.

None

If providing a value, it must be ServiceRequest.

Conditionally required

A value is required only when you're inserting a parent entity name. However, a value isn't required when you delete or update an existing parent entity name.

Conditionally required

A value is required only when you're inserting a parent entity name. However, a value isn't required when you delete or update an existing parent entity name.

Duration

The estimated time to complete the action.

None

Required

Required

Duration Unit

The unit of measurement for lead time.

None

If you intend to specify a value, select a value from the list of valid values in the lookup type ORA_SVC_AP_LEAD_TIME_UNIT.

Required

Required

Object Entity Name

Entity name of the object on which the action is based.

None

Conditionally required

A value is required only when you're inserting an object entity name. However, a value isn't required when you delete or update an existing object entity name.

Conditionally required

A value is required only when you're inserting an object entity name. However, a value isn't required when you delete or update an existing object entity name.

Original System Reference

Specifies the original system reference if this record was imported.

Identify the original system and system reference values from your source system that were imported when you imported the resource.

Optional

Optional

Object Entity Type

The entity type of the object on which the action is based.

The valid values are ServiceRequest, Task, and Appointment.

Required

Not required

A value is required only when you're inserting an object entity type. However, a value isn't required when you delete or update an existing object entity type.

Visibility

Indicates the visibility level of the action.

If you intend to specify a value, select a value from the list of valid values in the lookup type ORA_SVC_AP_VISIBILITY_CD.

Required

Not required

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the action 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 Action 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 action information. To create an import activity:

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

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

  3. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Action 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.

    Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues.
  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 Action Attribute Data

You can use the import functionality to create, update, or delete action attribute data.

You can import action attribute 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 action condition 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 action attribute 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 action 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.

If you want to import only a few records, then you can create a single CSV file for all action conditions. 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 action child objects. Note that you must have imported the CSV file for action 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 actions or are updating actions that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Action Attribute 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 action attribute records, prerequisite setup tasks and specific validations, if any:

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

Action Attribute Id

The unique Id of the existing Action Attribute record in the Oracle Fusion destination table.

Identify the Action Attribute ID value by exporting the Action object using Setup and Maintenance, Manage Bulk Data Export, Schedule Export Processes task

Not required

A value is required if you're updating an existing Action attribute and you're not providing the Action source system (original system)

Action Code

Indicates the operation to be performed on a row, such as insert, update, and so on

If a value isn't provided, records are matched to determine if a record is updated (if it already exists) or inserted (if it doesn't exist).

Not required

A value is required, if you're deleting an action attribute.

Action Id

Specifies the foreign key that references the Action ID to which the action is assigned.

Identify the Action ID value by exporting the Action object using Setup and Maintenance, Manage Bulk Data Export, Schedule Export Processes task.

Not required

A value is required, if you're updating an existing Action Id and you're not providing the Action Id source system code and reference Action OSR.

ActionOSR

Specifies the action original system reference, if the record was imported.

Identify the original system and system reference values from your source system which were imported when you imported the resource.

Required

A value is required if you're updating an existing Action Id record and you're not providing the record's unique ID (ActionId)

AttributeName

Attribute from the entity object of the associated action.

None

Not Required

Not Required

AttributeValue

The value to be set on the Action attribute.

None

Not Required

Not Required

AttributeValueContextCd

The context of how the attribute value should be interpreted (for example, as an attribute of the parent action's object, an attribute of the parent action, or a custom value).

The valid values provided by the lookup type ORA_SVC_AP_CONTEXT_CD.

Required

Not required

Deleted

Indicates whether the service request is to be deleted. If the value is Y, then the service request is deleted. The default value is N.

None

Not required

Not required

ErrorMessage

This column displays the error messages, if any.

None

Not required

Not required

ErrorMessage

This column displays the error messages, if any.

None

Not required

Not required

InternalOvn

This is meant for internal use.

None

Not required

Not required

JobDefinitionName

Indicates the name of the job that created or last updated the row.

None

Not required

Not required

JobDefinitionPackage

Indicates the package name of the job that created or last updated the row.

None

Not required

Not required

UsageCd

Indicates when the attribute is to be used.

The valid value is ORA_SVC_CREATE.

Required

Not required

You can view the Action Attribute 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 Action Attribute 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 action attribute 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 Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Action Attribute 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 Action Condition Data

You can use the import functionality to create, update, or delete your action condition data.

You can import action condition 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 action condition 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 action condition 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 action 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.

If you want to import only a few records, then you can create a single CSV file for all action conditions. 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 action child objects. Note that you must have imported the CSV file for action 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:

The preferred option to uniquely identify an object record is through 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. 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 Action Condition Object, the attributes are Action ConditionId and ActionId:

Required Attributes and Validations for Action Condition 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 action condition records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task/ Import Validations Creating an Action Condition record Updating an Existing Action Condition record

ActionCode

Indicates the operation to be performed on a row, such as insert, update, and so on

If a value isn't provided, records are matched to determine if a record is updated (if it already exists) or inserted (if it doesn't exist).

Not required

A value is required, if you're deleting an action condition.

Action ConditionId

The unique Id of the existing Action Condition record in the Oracle Fusion destination table.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Not required

A value is required if you're updating an existing Action Condition attribute and you're not providing the Action source system (original system)

Action Id

Specifies the foreign key that references the Action ID to which the action is assigned.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Not required

A value is required, if you're updating an existing Action Id and you're not providing the Action Id source system code and reference Action OSR.

ActionStatus

Indicates the status to set an action if the condition is met.

Valid values provided by the lookup type ORA_SVC_AP_STATUS_CD.

Required

Not required

ActionNumber

Specifies the action original system reference, if the record was imported.

Identify the original system and system reference values from your source system which were imported when you imported the resource.

Required

A value is required only if you're not specifying the Action ID.

You can view the Action Condition 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 Action Condition 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 action condition 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 Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Action Condition 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 Activity Data

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

You can import activity records using these steps:

  1. Map your source activity 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 activity 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 activity data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.

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 activity information, the activity object has the following child objects:

  • Activity Assignee

  • Activity Contact

  • Activity Objectives

If you want to import only a few records, then you can create a single CSV file for all activity 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 activity child objects. Note that you must have imported the CSV file for activity 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 activities or are updating activities that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Activity 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 activity records, prerequisite setup tasks and specific validations, if any:

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

AccountId

The internal identifier of the account associated with the activity. Examples of account are: customer, organization, person, partner.

The party must exist. You can determine the PartyId of the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Not Required

If during update, you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId.

AccountOrigSystem

The code representing the source system for the account associated with the activity.

The party must exist. Identify the source system code that was used when you imported the party in a prior batch.

Not Required

If during update, you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId.

AccountPartyNumber

The public unique identifier of the account associated with the activity.

The party must exist and be a valid party unique identifier

Not Required

If during update, you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId.

ActionCode

Indicates explicitly the operation to be performed on a row: INSERT to create a new record in the destination tables, UPDATE to update an existing record in the destination table, DELETE to delete the record.

The valid values are INSERT, UPDATE, and DELETE. If not provided, record matching is used to determine whether a record is updated (if it already exists) or inserted (if it doesn't exist).

Not Required

To delete a record, you must provide the value as DELETE. It is optional to provide values for insert and update as the framework internally decides the action as INSERT if it's a new record or UPDATE if it's an existing record.

ActivityEndDate

The date and time when an appointment ends or the time when a task is completed.

This must be a valid date and should not be less than the ActivityStartDate.

A value is required if you're creating a new activity having ActivityFunctionCode as APPOINTMENT.

Optional

ActivityFunctionCode

Identifies the activity as an appointment or a task. This attribute is for internal use only and the value is set based on the user's navigation to the activity.

Valid values are APPOINTMENT, TASK, and CALLREPORT. Lookup type used is ZMM_ACTIVITY_FUNCTION_TYPE_CD.

A value is required while creating an activity.

Not Required

ActivityId

The internal identifier of the activity.

Automatically generated by the import process if creating a new activity record.

Not Required

A value is required if you're updating an existing activity and you're not providing other values to identify the activity record.

To update an existing activity, choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId)

  • The activity number (ActivityNumber)

  • The source system code and reference (OrigEntityNumber and OrigEntityCode)

ActivityNumber

The public unique identifier of the activity. Indicates a default system-generated number for the activity.

If a value is provided while creating a new activity, the value must be unique. For update, you can determine the existing unique value of the object by exporting the Activity object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

The table ZMM_ACTY_ACTIVITIES with column ACTIVITY_NUMBER holds the existing value.

Required

A value is required if you're updating an existing activity and you're not providing other values to identify the activity record.

To update or delete an existing activity you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId)

  • The activity number (ActivityNumber)

  • The source system code and reference (OrigEntityNumber and OrigEntityCode)

ActivityStartDate

The starting date and time of an appointment or a task. The default value for an appointment is null. The default value for a task is the date and time at which the task is created.

If no value is provided, the corresponding value from Activity production table is used.

A value is required if you're creating a new activity having ActivityFunctionCode as APPOINTMENT.

Optional

ActivityTypeCode

The channel through which communication has taken place.

If no value is provided, the corresponding value from Activity production table is used. If the ActivityFunctionCode is 'APPOINTMENT' and the action is 'INSERT' then the default value is set to 'MEETING'.

If no value is provided, the corresponding value is used from the Activity production table. If the ActivityFunctionCode is APPOINTMENT and the action is INSERT, the default value is set to MEETING.

Optional

CampaignId

The internal identifier of the related campaign.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an Activity, if you associate the Activity with a campaign, then you must provide either the internal ID, such as CampaignId, or the public unique value, such as CampaignNumber.

When updating an Activity, if you associate the Activity with a campaign, then you must provide either the internal ID, such as CampaignId, or the public unique value, such as CampaignNumber.

CampaignNumber

The public unique identifier of the related campaign.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an Activity, if you associate the Activity with a campaign, then you must provide either the internal ID, such as CampaignId, or the public unique value, such as CampaignNumber.

When updating an Activity, if you associate the Activity with a campaign, then you must provide either the internal ID, such as CampaignId, or the public unique value, such as CampaignNumber.

ClaimCode

The public unique identifier for claim.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an Activity, if you associate the Activity with a claim, provide either the internal ID, such as claim ID, or the public unique value, such as claim code. Ensure that this is a valid claim code from MKT_BDT_CLAIMS.

Optional. Ensure that this is a valid claim code from MKT_BDT_CLAIMS.

ClaimId

The internal identifier of the claim.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a claim, then you must provide either the internal ID, such as claim ID, or the public unique value, such as claim code. Ensure that this is a valid claim ID from the MKT_BDT_CLAIMS table.

Optional. Ensure that this is a valid claim ID from the MKT_BDT_CLAIMS table.

CorpCurrencyCode

The corporate currency used by the activity.

If no value is provided, the corresponding value from Activity production table is used.

If no value is provided, the corresponding value is used from the Assignee production table.

If no value is provided, the corresponding value is used from the Assignee production table.

CurcyConvRateType

The rate of currency conversion for an activity.

If no value is provided, the corresponding value from Activity production table is used.

If no value is provided, the corresponding value is used from the Assignee production table.

If no value is provided, the corresponding value is used from the Assignee production table.

CurrencyCode

The corporate currency used by the activity.

If no value is provided, the corresponding value from Activity production table is used.

If no value is provided, the corresponding value is used from the Assignee production table.

If no value is provided, the corresponding value is used from the Assignee production table.

CustomerAccountId

The internal identifier of the customer account related to the activity. It is the sales activity identifier from ZCA_SALES_ACCOUNTS table.

If no value is provided, the corresponding value from Activity production table is used.

The internal identifier of the customer account related to the activity. It is the sales account identifier from ZCA_SALES_ACCOUNTS table.

This should be a valid sales account identifier from the ZCA_SALES_ACCOUNTS table.

DealId

The internal identifier of the related deal registration.

You can determine the public unique value of the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Optional

When creating an activity, if you associate the activity with a deal, you must provide either the internal ID, such as dealId, or the public unique value, such as DealNumber.

Optional

When creating an activity, if you associate the activity with a deal, you must provide either the internal ID, such as dealId, or the public unique value, such as DealNumber.

DealNumber

The public unique identifier of the deal associated with the activity. The identifier can also be generated from an external source.

You can determine the public unique value of the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Optional

When creating an activity, if you associate the activity with a deal, you must provide either the internal ID, such as dealId, or the public unique value, such as DealNumber.

Optional

When creating an activity, if you associate the activity with a deal, you must provide either the internal ID, such as dealId, or the public unique value, such as DealNumber.

DelegatorId

The internal identifier of the activity resource that delegated activity ownership to another resource.

The party must exist. You can determine the PartyId of the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Optional

The party must exist. You can determine the PartyId of the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Optional

The party must exist. You can determine the PartyId of the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

DelegatorOrigSystem

The source system reference to the delegator of original system identifier.

The party must exist. Identify the source system code that was used when you imported the party in a prior batch.

The party must exist. Identify the source system code that was used when you imported the party in a prior batch.

Optional

DirectionCode

The direction options for an activity. The options are inbound, outbound, or optional. The default value is null.

If no value is provided, the corresponding value from Activity production table is used.

This should be a valid lookup code corresponding to ZMM_ACTIVITY_DIRECTION from fnd_lookups.

This should be a valid lookup code corresponding to ZMM_ACTIVITY_DIRECTION from fnd_lookups.

DueDate

The date the activity is due to be completed.

If no value is provided, the corresponding value from Activity production table is used.

This should be a valid date.

This should be a valid date

Duration

The actual duration of the activity in the appropriate unit of measure.

If no value is provided, then the corresponding value from Activity production table is used. If the ActivityFunctionCode is 'APPOINTMENT' and the Duration is NULL then the default value is the duration of days between the Activity Start Date and the Activity End Date.

This is a derived field. Any value provided is ignored.

This is a derived field. Any value provided is ignored

EnrollmentId

The internal identifier of the related program enrollment.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a program enrollment, then you must provide either the internal ID, such as EnrollmentId, or the public unique value, such as EnrollmentNumber. This must be a valid value in the ZPM_PROGRAM_ENROLLMENTS table.

If during update, you associate the activity with a program enrollment, then you must provide either the internal ID, such as EnrollmentId, or the public unique value, such as EnrollmentNumber.

EnrollmentNumber

The public unique identifier of the related program enrollment.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a program enrollment, then you must provide either the internal ID, such as EnrollmentId, or the public unique value, such as EnrollmentNumber. This must be a valid value in the ZPM_PROGRAM_ENROLLMENTS table.

If during update, you associate the activity with a program enrollment, then you must provide either the internal ID, such as EnrollmentId, or the public unique value, such as EnrollmentNumber.

FundRequestCode

The foreign key to FUND_REQUEST_CODE of the MKT_BDT_FUND_REQUESTS table.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a fund request, you must provide either the internal ID, such as FundRequestId, or the public unique value, such as FundRequestCode. This must be a valid value in the MKT_BDT_FUND_REQUESTS table.

When updating an activity, if you associate the activity with a fund request, you must provide either the internal ID, such as FundRequestId, or the public unique value, such as FundRequestCode. This must be a valid value in the MKT_BDT_FUND_REQUESTS table.

FundRequestId

The internal identifier of the fund request.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a fund request, you must provide either the internal ID, such as FundRequestId, or the public unique value, such as FundRequestCode. This must be a valid value in the MKT_BDT_FUND_REQUESTS table.

When updating an activity, if you associate the activity with a fund request, you must provide either the internal ID, such as FundRequestId, or the public unique value, such as FundRequestCode. This must be a valid value in the MKT_BDT_FUND_REQUESTS table.

LeadId

The internal identifier of the related lead.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a lead, then you must provide either the internal ID, such as LeadId, or the public unique value, such as LeadNumber. Must be valid in the MKL_LM_LEADS table.

If during update, you associate the activity with a lead, then you must provide either the internal ID, such as LeadId, or the public unique value, such as LeadNumber.

LeadNumber

The public unique identifier of the related lead.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a lead, then you must provide either the internal ID, such as LeadId, or the public unique value, such as LeadNumber. Must be valid in the MKL_LM_LEADS table.

If during update, you associate the activity with a lead, then you must provide either the internal ID, such as LeadId, or the public unique value, such as LeadNumber.

ObjectiveId

The internal identifier of the objective.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a sales objective, you must provide either the internal ID, such as ObjectiveId, or the public unique value, such as ObjectiveNumber. It must be a valid value in the ZCA_OBJECTIVES table.

When updating an activity, if you associate the activity with a sales objective, you must provide either the internal ID, such as ObjectiveId, or the public unique value, such as ObjectiveNumber. It must be a valid value in the ZCA_OBJECTIVES table.

ObjectiveNumber

The public unique identifier of the related objective.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a sales objective, you must provide either the internal ID, such as ObjectiveId, or the public unique value, such as ObjectiveNumber. It must be a valid value in the ZCA_OBJECTIVES table.

When updating an activity, if you associate the activity with a sales objective, you must provide either the internal ID, such as ObjectiveId, or the public unique value, such as ObjectiveNumber. It must be a valid value in the ZCA_OBJECTIVES table.

OpportunityId

The internal identifier of the related opportunity.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with an opportunity, you must provide either the internal ID, such as OpportunityId, or the public unique value, such as OpportunityNumber. This must be a valid value in the MOO_OPTY table.

If during update, you associate the activity with an opportunity, then you must provide either the internal ID, such as OpportunityId, or the public unique value, such as OpportunityNumber.

OpportunityNumber

The internal identifier of the related opportunity.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with an opportunity, you must provide either the internal ID, such as OpportunityId, or the public unique value, such as OpportunityNumber. This must be a valid value in the MOO_OPTY table.

If during update, you associate the activity with an opportunity, then you must provide either the internal ID, such as OpportunityId, or the public unique value, such as OpportunityNumber.

OrigEntityCode

The code indicating the original source of the record.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY.

One of the following must be provided while updating an activity:

  • ActivityId

  • ActivityNumber

  • Combination of OrigEntityNumber and OrigEntityCode

OrigEntityNumber

The original unique identifier of the existing task, appointment, or interaction in the source system.

If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL then it's defaulted to the provided value. If no value is provided, the corresponding value from Activity production table is used.

If the internal action code is "INSERT" and OrigEntityNumber and ActivityNumber are NULL, it's defaulted to the provided value.

One of the following must be provided while updating an activity:

  • ActivityId

  • ActivityNumber

  • Combination of OrigEntityNumber and OrigEntityCode

OsrAccountId

The internal identifier (reference number or text) of the account party in the original source system.

The party must exist. You can determine the Original System Reference for the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Optional

When creating an activity, if you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId

If during update, you associate the activity with an account party, then you must provide either the internal ID, such as AccountId, or the public unique value, such as AccountPartyNumber, or the combination of original system and original system reference, such as AccountOrigSystem and OsrAccountId.

OsrDelegatorId

The source system reference to the Delegator ID.

The party must exist. You can determine the Original System Reference for the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Optional

The party must exist. You can determine the Original System Reference for the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Optional

The party must exist. You can determine the Original System Reference for the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

OsrOwnerId

The internal identifier (reference number or text) of the person who owns the activity in the original source system.

The party must exist. You can determine the Original System Reference for party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

One of the following must be provided while creating an activity:

  • OwnerId

  • OwnerResourceNumber

  • Combination of OwnerOrigSystem and OsrOwnerId

The party must exist. You can determine the Original System Reference for the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

OsrPrimaryContactId

The internal identifier (reference number or text) of the contact party in the original source system.

The party must exist. You can determine the Original System Reference for the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Optional

When creating the activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId.

When updating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId.

OsrReferenceCustomerId

The internal identifier (reference number or text) of the customer in the original source system.

The party must exist. You can determine the Original System Reference for the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId.

When updating an activity, if you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId.

OutlookFlag

Indicates whether the activity is created in Outlook. If the value is Y, then the activity is created in Outlook and synchronized.

If no value is provided, the corresponding value from Activity production table is used. If the ActivityFunctionCode is 'APPOINTMENT' and the Action is 'INSERT' then the value is set to 'N'.

If the ActivityFunctionCode is APPOINTMENT and the action is INSERT, the value is set to N. Possible values are Y and N.

Optional

Possible values are Y and N.

OwnerId

The internal identifier of the activity owner. The owner has to be an existing party (person) in system.

The party must exist. You can determine the PartyId of a person by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Provide one of the following while creating an activity:

(OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId)

Optional

Provide one of the following while updating an activity:

(OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId)

OwnerOrigSystem

The code representing the source system for the party (person) who owns the activity.

The party must exist. You can determine the PartyId of a person by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Provide one of the following while creating an activity:

(OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId)

Optional

Provide one of the following while updating an activity:

(OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId)

OwnerResourceNumber

The public unique identifier of the party (person) who owns the activity.

The party must exist. You can determine the PartyId of a person by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Provide one of the following while creating an activity:

(OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId)

Optional

Provide one of the following while updating an activity:

(OwnerId, OwnerResourceNumber, or a combination of OwnerOrigSystem and OsrOwnerId)

ParentActivityId

The related activity identifier and only applicable if the record is a follow up activity.

Conditionally Required only for follow-up activity. One of the following options to identify the parent record must be provided:

  • The unique ID for the ParentActivityId.

  • The parent activity number (ParentActivityNumber)

  • The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode)

A value is required if you're creating a follow-up activity. While creating an activity, choose one of the following options to identify the record:

  • The unique ID for the ParentActivityId.

  • The parent activity number (ParentActivityNumber)

  • The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode)

Optional

While updating an activity, choose one of the following options to identify the record:

The unique ID for the ParentActivityId.

The parent activity number (ParentActivityNumber).

The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode).

ParentActivityNumber

The public unique identifier of the related activity and only applicable if the record is a follow up activity.

Conditionally Required only for follow-up activity. One of the following options to identify the parent record must be provided:

  • The unique ID for the record (ParentActivityId)

  • The parent activity number (ParentActivityNumber)

  • The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode)

A value is required if you're creating a follow-up activity. While creating an activity, choose one of the following options to identify the record:

  • The unique ID for the record (ParentActivityId)

  • The parent activity number (ParentActivityNumber)

  • The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode)

Optional

While updating an activity, choose one of the following options to identify the record:

The unique ID for the record (ParentActivityId).

The parent activity number (ParentActivityNumber).

The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode).

ParentOrigEntityCode

The source of the activity record that indicating whether it's coming from Task entity, Interaction entity, or Appointment entity.

Conditionally Required only for follow-up activity. One of the following options to identify the parent record must be provided:

  • The unique ID for the record (ParentActivityId)

  • The parent activity number (ParentActivityNumber)

  • The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode)

A value is required if you're creating a follow-up activity. While creating an activity, choose one of the following options to identify the record:

  • The unique ID for the record (ParentActivityId)

  • The parent activity number (ParentActivityNumber)

  • The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode)

Optional

While updating an activity, choose one of the following options to identify the record:

The unique ID for the record (ParentActivityId).

The parent activity number (ParentActivityNumber).

The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode)

ParentOrigEntityNumber

The entity number of the parent entity in the original system to which the activity is related

Conditionally Required only for follow-up activity. One of the following options to identify the parent record must be provided:

  • The unique ID for the record (ParentActivityId)

  • The parent activity number (ParentActivityNumber)

  • The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode)

A value is required if you're creating a follow-up activity. While creating an activity, choose one of the following options to identify the record:

  • The unique ID for the record (ParentActivityId)

  • The parent activity number (ParentActivityNumber)

  • The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode)

Optional

While updating an activity, choose one of the following options to identify the record:

The unique ID for the record (ParentActivityId).

The parent activity number (ParentActivityNumber).

The source system code and source reference code (ParentOrigEntityNumber and ParentOrigEntityCode).

PartnerProgramId

The internal identifier of the related partner program.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

For partner programs, export the Program Enrollments object.

When creating an activity, if you associate the activity with a partner program, you must provide either the internal ID, such as PartnerProgramId, or the public unique value, such as PartnerProgramNumber.

When updating an activity, if you associate the activity with a partner program, then you must provide either the internal ID, such as PartnerProgramId, or the public unique value, such as PartnerProgramNumber.

PartnerProgramNumber

The public unique identifier of the related partner program.

You can determine the public unique value of the object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

For Partner programs, export the Program Enrollments object.

When creating an activity, if you associate the activity with a partner program, then you must provide either the internal ID, such as PartnerProgramId, or the public unique value, such as PartnerProgramNumber.

When updating an activity, if you associate the activity with a partner program, then you must provide either the internal ID, such as PartnerProgramId, or the public unique value, such as PartnerProgramNumber.

PrimaryContactId

The internal identifier of the activity contact.

The party must exist. You can determine the PartyId of the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

If no value is provided, the corresponding value from Activity production table is used.

Optional

When creating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId.

When updating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId.

PrimaryContactOrigSystem

The code representing the source system for the activity contact.

The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

Optional

When creating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId.

When updating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId.

PrimaryContactPartyNumber

The public unique identifier of the activity contact.

The party must exist. You can determine the PartyNumber of a party by exporting either the Person object or the Organization object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Optional

When creating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId.

When updating an activity, if you associate the activity with a contact party, then you must provide either the internal ID, such as PrimaryContactId, or the public unique value, such as PrimaryContactPartyNumber, or the combination of original system and original system reference, such as PrimaryContactOrigSystem and OsrPrimaryContactId.

PriorityCode

The priority of the activity. The default value is 2. The possible values are 1, 2, 3.

If no value is provided, the corresponding value from Activity production table is used.

Not required

The default value is 2 (Medium). To change this value during create, you must pass this value. Valid values are 1, 2, and 3

When updating an activity, if you must modify the priority of an Activity, provide a valid value for PriorityCode.

PrivateFlag

Indicates whether the activity is private.

If no value is provided, the corresponding value from Activity production table is used.

Optional

When creating an Activity, if you must mark an Activity as private, set this variable to 'Y'.

When updating an activity, if you must mark an Activity as private, set this variable to 'Y'.

RecurSerOrigEntityNumber

The entity number of the recurring appointment in the original system, to which this activity is related

If no value is provided, the corresponding value from Activity production table is used.

A value is required if you're creating a recurring activity (appointment). While creating an activity, choose one of the following options to identify the record:

  • The unique ID for the record (RecurSeriesId)

  • The recurring series activity number (RecurSeriesActivityNumber)

  • The entity number of the recurring appointment in the original system, to which this activity is related (RecurSerOrigEntityNumber)

Optional

RecurSeriesActivityNumb

The activity number of an instance of a series.

If no value is provided, the corresponding value from Activity production table is used.

A value is required if you're creating a recurring activity (appointment). While creating an activity, choose one of the following options to identify the record:

  • The unique ID for the record (RecurSeriesId)

  • The recurring series activity number (RecurSeriesActivityNumber)

  • The entity number of the recurring appointment in the original system, to which this activity is related (RecurSerOrigEntityNumber)

Optional

RecurSeriesId

The internal identifier for the series that links instances of a series together.

If no value is provided, the corresponding value from Activity production table is used.

A value is required if you're creating a recurring activity (appointment). While creating an activity, choose one of the following options to identify the record:

  • The unique ID for the record (RecurSeriesId)

  • The recurring series activity number (RecurSeriesActivityNumber)

  • The entity number of the recurring appointment in the original system, to which this activity is related (RecurSerOrigEntityNumber)

Optional

RecurWeekday

The activity that recurs on every weekday such as Monday to Sunday, Weekday, Weekend, and so on.

If no value is provided, the corresponding value from Activity production table is used.

Conditionally required for a weekly recurring appointment. Must be a valid value from ZMM_ACTIVITY_RECUR_DAYWEEK_CD lookup.

Conditionally required for a weekly recurring appointment. Must be a valid value from ZMM_ACTIVITY_RECUR_DAYWEEK_CD lookup.

RefCustOrigSystem

The source system code for the reference customer.

The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

When updating an activity, if you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId.

RefCustPartyNumber

The public unique identifier of the reference customer who's associated with the activity.

The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

When updating an activity, if you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId.

ReferenceCustomerId

The internal identifier of the reference customer who's associated with the activity.

The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

The party must exist. Identify the source system code that was used when you imported the party in a prior batch. You can determine existing source system codes and create new ones.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Trading Community Source Systems

When updating an activity, if you associate the activity with a referenced customer party, then you must provide either the internal ID, such as ReferenceCustomerId, or the public unique value, such as RefCustPartyNumber, or the combination of original system and original system reference, such as RefCustOrigSystem and OsrReferenceCustomerId.

SrId

The foreign key to SR_ID in the SVC_SERVICE_REQUESTS table.

You can determine the public unique value of this object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a service request, then you must provide either the internal ID, such as SrId, or the public unique value, such as SrNumber. This must be a valid value in SVC_SERVICE_REQUESTS.

When updating an activity, if you associate the activity with a service request, then you must provide either the internal ID, such as SrId, or the public unique value, such as SrNumber. This must be a valid value in SVC_SERVICE_REQUESTS.

SrNumber

The foreign key to SR_NUMBER in the SVC_SERVICE_REQUESTS table.

You can determine the public unique value of this object by exporting the object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

When creating an activity, if you associate the activity with a service request, then you must provide either the internal ID, such as SrId, or the public unique value, such as SrNumber. This must be a valid value in SVC_SERVICE_REQUESTS.

When updating an activity, if you associate the activity with a service request, then you must provide either the internal ID, such as SrId, or the public unique value, such as SrNumber. This must be a valid value in SVC_SERVICE_REQUESTS.

StatusCode

The status of the activity. The default value is Not Started.

If no value is provided, the default is NOT_STARTED. The lookup Type used is ZMM_ACTIVITY_STATUS_CD.

If no value is provided, the default is NOT_STARTED. The lookup Type used is ZMM_ACTIVITY_STATUS_CD.

Optional

The lookup Type used is ZMM_ACTIVITY_STATUS_CD.

Subject

The unique subject, name, or title of the activity.

No validation

A value is required if you're creating a new activity.

Not Required

SubmittedBy

The user who submitted the call report.

Conditionally required for a call report in Submitted status.

Conditionally required for a call report in Submitted status.

It must be a valid value in the HZ_PARTIES table.

Optional

Conditionally required for a call report in Submitted status.

It must be a valid value in the HZ_PARTIES table.

SubmittedDate

The date and time when the call report was submitted.

None

Conditionally required for a call report in Submitted status. This must be a valid date.

Conditionally required for a call report in Submitted status. This must be a valid date.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the activity 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 Activity 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 activity 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 Activity 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 Activity Assignee Data

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

You can import activity assignee records using these steps:

  1. Map your source activity assignee 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 activity assignee 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 activity assignee 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

If you want to import only a few records, then you can create a single CSV file for all activity assignee 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 activity assignee child objects. Note that you must have imported the CSV file for activity assignee 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 accounts or are updating accounts that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Activity Assignee 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 activity assignee records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task/ Import Validations Creating an Activity Assignee record Updating an Existing Activity Assignee record

ActivityId

The internal identifier of the activity to which the assignee is associated.

Automatically generated by the import process if creating a new activity record.

Optional

A value is required if you're updating an existing activity and you're not providing other values to identify the activity record.

To update an existing activity, choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId)

  • The activity number (ActivityNumber)

  • The source system code and reference (OrigEntityNumber and OrigEntityCode)

ActivityNumber

The public unique identifier of the activity to which the assignee is associated

If a value is provided while creating a new activity, the value must be unique. For update, you can determine the existing unique value of the object by exporting the Activity object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

The table ZMM_ACTY_ACTIVITIES with column ACTIVITY_NUMBER holds the existing value.

A value is required if you're creating a new activity.

A value is required if you're updating an existing activity and you're not providing other values to identify the activity record.

To update an existing activity, choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId)

  • The activity number (ActivityNumber)

  • The source system code and reference (OrigEntityNumber and OrigEntityCode)

AssigneeId

The internal identifier of the HZ_PARTY record having PARTY_USAGE as Resource.

If no value is provided, the corresponding value from Assignee production table is used.

A value is required if you're associating a new assignee to an activity.

One of the following must be provided while creating an assignee:

  • AssigneeId

  • AssigneeResourceNumber

  • Combination of AssigneeOrigSystem and OsrAssigneeId

To update or delete an existing activity assignee you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId, AssigneeId)

  • The activity number (ActivityNumber,AssigneeId)

  • The source system code and reference (OrigEntityNumber and OrigEntityCode)

AssigneeOrigSystem

The source system reference to the assigned resource organization.

None

A value is required if you're associating a new assignee to an activity.

One of the following must be provided while creating an assignee:

  • AssigneeId

  • AssigneeResourceNumber

  • Combination of AssigneeOrigSystem and OsrAssigneeId

Not Required

AssigneeResourceNumber

The resource number associated with an assignee.

None

A value is required if you're associating a new assignee to an activity.

One of the following must be provided while creating an assignee:

  • AssigneeId

  • AssigneeResourceNumber

  • Combination of AssigneeOrigSystem and OsrAssigneeId

Not Required

OrigEntityCode

The code indicating the original source of the activity the activity to which the assignee is associated.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY.

A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record.

To update or delete an existing activity you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId)

  • The activity number (ActivityNumber)

  • The source system code and reference (OrigEntityNumber and OrigEntityCode)

OrigEntityNumber

The original unique identifier of the existing task, appointment, or interaction in the source system.

If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL then it will be defaulted to the provided value. If no value is provided, the corresponding value from Assignee production table is used.

If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL, the value will be set to the value provided by the user. If no value is provided, the corresponding value is used from the Assignee production table.

A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record.

To update or delete an existing activity you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId)

  • The activity number (ActivityNumber)

  • The source system code and reference (OrigEntityNumber and OrigEntityCode)

OsrAssigneeId

The source system reference of the assignee..

The party must exist. You can determine the Original System Reference for the party by exporting the Party object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

A value is required if you're associating a new assignee to an activity. One of the following must be provided while creating an assignee:

  • AssigneeId

  • AssigneeResourceNumber

  • Combination of AssigneeOrigSystem and OsrAssigneeId

Not Required

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the activity assignee 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 Activity Assignee 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 activity assignee 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 Activity Assignee 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 Activity Contact Data

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

You can import activity contact records using these steps:

  1. Map your source activity 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 activity 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

You import activity contact 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

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 activity contacts or are updating activity contacts that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Activity Contact 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 activity contact records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task/ Import Validations Creating an Activity Contact record Updating an Existing Activity Contact record

ActivityId

The internal identifier of the activity to which the contact is associated.

Automatically generated by the import process if creating a new activity record.

The value is generated automatically by the import process if creating a new activity record.

A value is required if you're updating an existing activity and you're not providing other values to identify the activity record.

To update an existing activity, choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId).

  • The activity number (ActivityNumber).

  • The source system code and reference (OrigEntityNumber and OrigEntityCode).

ActivityNumber

The public unique identifier of the activity to which the contact is associated

If a value is provided while creating a new activity, the value must be unique. For update, you can determine the existing unique value of the object by exporting the Activity object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

The table ZMM_ACTY_ACTIVITIES with column ACTIVITY_NUMBER holds the existing value.

A value is required if you're creating a new activity.

A value is required if you're updating an existing activity and you're not providing other values to identify the activity record.

To update an existing activity, choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId).

  • The activity number (ActivityNumber).

  • The source system code and reference (OrigEntityNumber and OrigEntityCode).

ContactId

The party of type person who's involved with this appointment..

If no value is provided, the corresponding value from the Contacts production table is used.

A value is required if you're associating a new contact to an activity. One of the following must be provided while creating a contact:

  • ContactId

  • ContactPartyNumber

  • Combination of ContactOrigSystem and OsrContactId

To update or delete an existing activity contact, select one of the following options to identify the record:

  • The unique ID for the record (ActivityId, ContactId).

  • The activity number (ActivityNumber,ContactId).

  • The source system code and reference (OrigEntityNumber and OrigEntityCode).

ContactOrigSystem

The source system for the activity with which the contact is associated.

No Validation

A value is required if you're associating a new contact to an activity.

One of the following must be provided while creating a contact:

  • ContactId

  • ContactPartyNumber

  • Combination of ContactOrigSystem and OsrContactId

Not Required

ContactPartyNumber

The party number of the contact.

This must be a valid party in the HZ_PARTIES table.

A value is required if you're associating a new contact to an activity.

One of the following must be provided while creating a contact:

  • ContactId

  • ContactPartyNumber

  • Combination of ContactOrigSystem and OsrContactId

This must be a valid party in the HZ_PARTIES table

CorpCurrencyCode

The corporate currency used by the activity to which the contact is associated.

If no value is provided, the corresponding value from the Contacts production table is used.

If no value is provided, the corresponding value is used from the Contacts production table.

If no value is provided, the corresponding value is used from the Contacts production table.

OrigEntityCode

The code indicating the original source of the activity the activity to which the contact is associated.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

Note: If the record was created in the Activity Management component, the value is ACTIVITY.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

Note: If the record was created in the Activity Management component, the value is ACTIVITY.

A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record.

To update or delete an existing activity you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId).

  • The activity number (ActivityNumber).

  • The source system code and reference (OrigEntityNumber and OrigEntityCode).

OrigEntityNumber

The ID that identifies the entity record in the original system..

If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL then it will be defaulted to the provided value. If no value is provided, the corresponding value from Contacts production table is used.

If the internal action code is 'INSERT' and OrigEntityNumber and ActivityNumber are NULL, the value will be set to the value provided by the user. If no value is provided, the corresponding value is used from the Contacts production table.

A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record.

To update or delete an existing activity you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId).

  • The activity number (ActivityNumber).

  • The source system code and reference (OrigEntityNumber and OrigEntityCode).

OsrContactId

The source system reference of the contact..

The contact must exist in system. You can determine the original system reference for the Contact by exporting the Contacts object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

A value is required if you're associating a new contact to an activity. One of the following must be provided while creating an assignee:

  • ContactId

  • ContactPartyNumber

  • Combination of ContactOrigSystem and OsrContactId

The contact must exist in system. You can determine the original system reference for the Contact by exporting the Contacts object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

OsrContactOrgId

The source system reference to the contact organization. It is used to update the RELATIONSHIP_ID in the interface table (ZMM_IMP_ACTY_CONTACTS) based on HZ_PARTIES.

This must be a valid organization type in the HZ_PARTIES table.

This must be a valid organization type in the HZ_PARTIES table.

This must be a valid organization type in the HZ_PARTIES table.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the activity 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 Activity Contact 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 activity 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 Activity 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.

Import Your Activity Objective Data

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

You can import activity objective records using these steps:

  1. Map your source activity objective 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 activity objective 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 activity objective 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

If you want to import only a few records, then you can create a single CSV file for all activity objective 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 activity objective child objects. Note that you must have imported the CSV file for activity objective 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 activity objectives or are updating activity objectives that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Activity Objective 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 activity objective records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task/ Import Validations Creating an Activity Objective record Updating an Existing Activity Objective record

ActionCode

Indicates explicitly the operation to be performed on a row: INSERT to create a new record in the destination tables, UPDATE to update an existing record in the destination table, DELETE to delete the record.

If value isn't provided, record matching is used to determine whether a record is updated (if it already exists) or inserted (if it doesn't exist). The valid values are INSERT, UPDATE, and DELETE.

Optional

To delete a record, you must provide the value as DELETE. It is optional to provide values for insert and update as the framework internally decides the action as INSERT if it's a new record or UPDATE if it's an existing record.

ActivityId

The internal identifier of the activity to which the Objective is associated.

Automatically generated by the import process if creating a new activity record.

A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record.

To update or delete an existing activity you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId)

  • The activity number (ActivityNumber)

  • The source system code and reference (OrigEntityNumber and OrigEntityCode)

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

A value is required if you're updating or deleting an existing activity and you're not providing other values to identify the activity record.

To update or delete an existing activity you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId)

  • The activity number (ActivityNumber)

  • The source system code and reference (OrigEntityNumber and OrigEntityCode)

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

ActivityNumber

The public unique identifier of the activity to which the Objective is associated

If a value is provided while creating a new activity, the value must be unique. For update, you can determine the existing unique value of the object by exporting the Activity object.

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

The table ZMM_ACTY_ACTIVITIES with column ACTIVITY_NUMBER holds the existing value.

A value is required if you're:

  • Creating an activity

  • Updating or deleting an existing activity and you're not providing other values to identify the activity record.

To update or delete an existing activity you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId).

  • The activity number (ActivityNumber).

  • The source system code and reference (OrigEntityNumber and OrigEntityCode).

A value is required if you're updating an existing activity and you're not providing other values to identify the activity record.

To update or delete an existing activity you must choose one of the following options to identify the record:

  • The unique ID for the record (ActivityId).

  • The activity number (ActivityNumber).

  • The source system code and reference (OrigEntityNumber and OrigEntityCode).

ObjectiveCode

The set of predefined objectives defined by the administrator

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

ObjectiveFreefmtText

The objective in free form text as provided by the user.

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

ObjectiveId

The internal identifier of the objective associated with the activity.

If no value is provided, the corresponding value from the Objectives production table is used.

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

A value is required if you're associating a new objective to an activity and you're not providing other values to identify the objective record. You must choose one of the following options to identify the objective record:

  • ObjectiveId

  • Combination of ActivityId and (ObjectiveCode or ObjectiveFreefmtText)

OrigEntityCode

The code indicating the original source of the activity the activity to which the Objective is associated.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY.

OrigEntityNumber

The original unique identifier of the existing task, appointment, or interaction in the source system.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY.

Valid values for upgraded records are TASK, APPOINTMENT, or INTERACTION.

If the record was created in the Activity Management component, the value is ACTIVITY.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the activity objective 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 Activity Objective 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 activity objective 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 Activity Objective 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 Additional Name Data

Use this topic to import Additional Name data into Oracle Applications Cloud. You can use the import functionality to create, update, or delete Additional Name records.

To import Additional Name 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 Additional Name 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.

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

Before You Start

You need to set certain options for some attributes in the application before you can populate them. When importing a child record, ensure that its parent record exists in the database.

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 identify an object record is through 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. 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 Additional Name object, the attributes are NameID and RegistryID.

Required Attributes and Validations

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 Additional Name records, required attributes for updating Additional Name records, prerequisite setup tasks for the attributes, and specific validations, if any, for Additional Name import:

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

NameId

Unique identifier of the address record as the primary key

No Validation

Not required

Optional

Either the NameId or a combination of Source System and Source System Reference can be passed.

StatusFlag

The status of the additional name

Defaults to Y during creation.

Not required

To inactivate an existing active Additional Name record, provide the value as "N".

NameType

Additional Name Type

This must be a valid name type. The name types can be managed in Manage Name Types.

Required

If you don't provide the primary key, provide the existing additional name type.

PartyNumber

The public unique identifier of the party record to which the Additional Name is associated.

The party number should exist.

Conditionally required

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

  • PartyId (internal ID)

  • PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile

  • Party Number (public unique identifier for an organization profile)

Not required

PartySourceSystem

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

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

Conditionally required

Provide one of the following :

  • PartyId (internal ID)

  • PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile

  • Party Number (public unique identifier for an organization profile)

Not required

PartySourceSystemReferenceValue

The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the Additional Name belongs.

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

Conditionally required

Provide one of the following :

  • PartyId (internal ID)

  • PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile

  • Party Number (public unique identifier for an organization profile)

Not required

PartyId

The unique identifier as primary key of the party record to which the additional name is associated.

Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on.

Conditionally required

Provide one of the following :

  • PartyId (internal ID)

  • PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile

  • Party Number (public unique identifier for an organization profile)

Not required

SourceSystem

Name of external source system of the account, contact or household with which the address is associated.

The source system should exist.

You can manage source systems from the Manage Source Systems task.

Optional

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

Not required

SourceSystemReferenceValue

Specifies the identifier in the original source system

No validation

Provide a valid value.

Not required

You can view the Additional Name 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 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. In the Navigator, under Tools, click Import Management.

  2. Click Import Objects tab to open the Import Object Details page.

  3. Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.

  4. Save the template CSV file to a location on your desktop.

You must edit the template CSV file and provide valid values for the required attributes. You can attach different types of files, giving each file a specific description.

PartyNumber NameType AdditionalName

RN_PTY_06_MAR_19_A1

LEGAL

Test_Addname_A1

RN_PTY_06_MAR_19_A2

LEGAL

Test_Addname_A2

RN_PTY_06_MAR_19_A3

LEGAL

Test_Addname_A3

RN_PTY_06_MAR_19_A4

LEGAL

Test_Addname_A4

RN_PTY_06_MAR_19_A5

LEGAL

Test_Addname_A5

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

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 Additional Identifier Data

You can use Import Management to create or update Additional Identifier records.

To import Additional Identifier 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 Additional Identifier 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.

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

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 Additional Identifiers. 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 Additional Identifier object, the attributes are PartyIdentifierID 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 Additional Identifier object, the attribute is PartyNumber.

Required Attributes and Validations for the Additional Identifier 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 Additional Identifier records, required attributes for updating Additional Identifier records, prerequisite setup tasks for the attributes, and specific validations, if any, for Additional Identifier import:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Additional Identifier Record Updating an Existing Additional Identifier Record

PartySourceSystem

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

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

Conditionally required

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

  • PartyId (internal ID)

  • PartySourceSystem and PartySourceSystemReference (source system code and source system reference values) provided when importing the organization profile

  • Party Number (public unique identifier for an organization profile)

Not required

PartySourceSystemReferenceValue

The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the Additional identifier belongs.

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

Conditionally required

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

  • PartyId ( internal ID)

  • PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile

  • Party Number (public unique identifier for an organization profile)

Not required

PartyIdentifierID

Unique identifier of the additional identifier of the party

No validation

Not required

Required

StatusCode

The status of the additional identifier

Not required

This defaults to Y during creation.

Not required

To inactivate existing active Additional Name record, provide the value as N.

PartyIdentifierType

The type of the Additional Identifier import

The Identifier Type must exist. You can manage additional types using the Manage Additional Name Types task.

Required

Not required

PartyIdentifierValue

Value to be imported for the Identifier Type

Mandatory field

Required

Not required

PartyNumber

The public unique identifier of the party record to which the Additional identifier is associated.

The party number should exist.

Conditionally required

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

  • PartyId (internal ID)

  • PartySourceSystem and PartySourceSystemReference (source system code and source system reference values) provided when importing the organization profile

  • Party Number (public unique identifier for an organization profile)

Not required

PartyID

The unique identifier as primary key of the party record to which the additional identifier is associated.

Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on.

Conditionally required

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

  • PartyId (internal ID)

  • PartySourceSystem and PartySourceSystemReference (source system code and source system reference values) provided when importing the organization profile

  • Party Number (public unique identifier for an organization profile)

Not required

SourceSystem

Name of external source system of the account, contact or household with which the Additional identifier is associated.

The source system should exist.

You can manage source systems from the Manage Source Systems task.

Optional

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

Not required

SourceSystemReferenceValue

Specifies the identifier in the original source system.

The combination of Source System and Source System Reference Value should be unique.

Optional

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

Not required

You can view the Additional Identifier 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 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 Additional Identifier 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 Additional Identifier 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.

Import Your Address Data

You can use the import functionality to create, update, or delete address records.

You can import address 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 address 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 address 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 address 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 addresses while importing, to avoid redundant data.

If you want to import only a few records, then you can create a single CSV file for all address 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 address child objects. Note that you must have imported the CSV file for address 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.

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 address or are updating address that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Address 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 address records, prerequisite setup tasks and specific validations, if any:

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

PartyId

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

Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on.

Conditionally Required

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

  • PartyId ( internal ID)

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

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address

Conditionally Required

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

  • PartyId ( internal ID)

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

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address

PartyNumber

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

Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on.

Conditionally Required

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

  • PartyId ( internal ID)

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

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address

Conditionally Required

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

  • PartyId ( internal ID)

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

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address

PartySourceSystem

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

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

Conditionally Required

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

  • PartyId (internal ID)

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

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address

Conditionally Required

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

  • PartyId (internal ID)

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

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address

PartySourceSystemReferenceValue

The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the address belongs.

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

Conditionally Required

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

  • PartyId (CX Sales and B2B Service internal ID)

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

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address

Conditionally Required

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

  • PartyId (CX Sales and B2B Service internal ID)

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

  • Party Number (public unique identifier for an organization profile), which is PARTY_SITE_NUMBER for address

PrimaryFlag

Identifies the primary address for the parent party record.

Only one of the child records can be Primary.

Optional

Optional

Pass Y to set Primary and N to reset an existing primary record.

Status

Indicates the current status of the address record.

Not required

Defaults to A (Active)

Not required

Defaults to A (Active)

Optional

Pass A to set the status to Active and I to set the status to Inactive.

AddressId

Unique identifier of the address record as primary key.

No validation

Not required

Optional

Either the AddressId or the AddressNumber can be passed.

Country

The country code component of the postal address.

Identify valid country codes.

Required

Not required.

LocationId

The unique ID for the existing location record in the destination table.

Identify the LOCATION_ID for an existing location by exporting the Location object.

Optional

Optional

StartDateActive

The address unique identifier that's 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.

The Address record can be updated by passing the Address Number.

AddressNumber

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

None

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

The Address record can be updated by passing the Address Number.

SourceSystem

Name of external source system of the account, contact or household with which the address is associated.

The source system should exist.

You can manage source systems from the Manage Source Systems task.

Optional

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

Not required

SourceSystemReferenceValue

Specifies the identifier in the original source system

Combination of Source System and Source System Reference Value should be unique.

Optional

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

Not required

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the address 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 Address 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 address 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 Address 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 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 Asset Data

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

You can import asset records using these steps:

  1. Map your source asset 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 asset 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 asset 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 asset information, the asset object has the following child objects:

  • Asset Contact

  • Asset Resource

If you want to import only a few records, then you can create a single CSV file for all asset 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 asset child objects. Note that you must have imported the CSV file for asset 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 assets or are updating assets that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Asset 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 asset records, prerequisite setup tasks and specific validations, if any:

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

AssetNumber

The unique ID for the existing asset record in the destination table.

None

Required

Required

AssetOrigSystem

A source system code that identifies the original source system of the asset.

None

Not required

Not required

AssetOrigSystemReference

A source system reference that's the unique ID of the asset in your legacy or external system.

None

Not required

Not required

CustomerId

The unique ID for the existing customer party record in the destination table.

The party must exist.

Required

Not required

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the asset 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 Asset 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 asset 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 Asset 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 Asset Contact Data

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

You can import asset contact records using these steps:

  1. Map your source asset 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 asset 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

You import asset contact data into Oracle Applications Cloud from a CSV file with your source data that's mapped to target 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 asset 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.

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 each attribute in your source data. For example, when using source system reference information to identify your asset records, the source system of the asset object should be enabled for parties in the Manage Trading Community Source Systems task.

  • You have all the parent records in place before importing child records. For example, when importing the asset contact, ensure the asset 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 asset object, the attribute is AssetNumber and shows up in the UI as Asset 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.

Required Attributes and Validations for Asset Contact Object

To import data 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 asset contact records, prerequisite setup tasks for the attributes, and specific validations, if any.

Attribute Description Prerequisite Setup Task/ Import Validations Creating an Asset Contact record Updating an Existing Asset Contact record

ContactPartyId

Unique party identifier representing a contact.

The party must exist.

Required

Required

AssetId

The unique ID for the existing asset record in the destination table.

An asset record with the Asset ID should exist.

Conditionally required when you don't provide the Asset Number.

Conditionally required when you don't provide the Asset Number.

AssetNumber

The unique ID for the existing asset record in the destination table.

An asset record with the Asset Number should exist.

Conditionally required when you don't provide the Asset ID.

Conditionally required when you don't provide the Asset ID.

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 you want to import into Oracle Applications Cloud in a CSV file.

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

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

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

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

AssetNumber ContactPartyId ContactFunctionCode

900546

300000018487543

ORA_ZCM_ASSET_MANAGER

900604

300000018487544

ORA_ZCM_MAINTENANCE_ENGINEEER

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

To create an import activity:

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

  2. Click Create Import Activity button on the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Asset 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. Click Next.

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

  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 Import Activity page. This page has 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. The Import Status column shows the status of the import activity.

  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 Asset Resource Data

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

To import asset resource 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 activity.

How You Map Your Source Data to Target Object Attributes

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

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 Asset Resource information, the Asset Resource object has the following child objects:

  • Address

  • Classification

  • Relationship

  • Sales Team Member

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 Asset Resources or are updating Asset Resources that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for the Asset Resource 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 Asset Resource records, prerequisite setup tasks and specific validations, if any:

Attribute Description Prerequisite Setup Task/ Import Validations Creating an Asset Resource record Updating an Existing Asset Resource record

AssetId

The unique ID for the existing asset record in the destination table.

An asset record with the Asset ID should exist

Conditionally required when you don't provide the Asset Number

Conditionally required when you don't provide the Asset Number

AssetNumber

The unique ID for the existing asset record in the destination table.

An asset record with the Asset Number should exist

Conditionally required when you don't provide the Asset ID

Conditionally required when you don't provide the Asset ID

Resource Party ID

Unique party identifier representing a resource

The party must exist.

Required

Required

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the Asset Resource 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 Asset Resource 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 Asset Resource 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 Asset Resource 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 Attachment Data

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

You can import attachment records using these steps:

  1. Map your source attachment 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 attachment 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 attachment 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 attachment 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.

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 attachment 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 attachments or are updating attachments that have source system reference data, then provide the source system and source system reference values. For attachment object, these are SourceSystem and SourceSystemReferenceValue and show up as Party Source System and Party Source System Reference Value in the UI.

Required Attributes and Validations for Attachment 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 attachment records, prerequisite setup tasks and specific validations, if any:

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

PK!Value

This is the primary key of the record to which the attachment is being associated.

When creating or updating attachments, the parent record to which the attachment is associated must exist in the database.

Either Pk1Value or PUID is mandatory.

Either Pk1Value or PUID is mandatory.

ObjectPUID

This is the public unique identifier of the record to which the attachment is being associated.

When creating or updating attachments, the parent record to which the attachment is associated must exist in the database.

Either Pk1Value or PUID is mandatory.

Either Pk1Value or PUID is mandatory.

Category

Category to which the attachment belongs. If you don't specify a value, the default is considered. For example, the default attachment category for lead is MKL_LEAD_CATEGORY.A source system reference that's the unique ID of the Attachment in your legacy or external system.

If passing the category, it should be a valid category for that object.

Not required

If you don't provide a value, the default is used.

Not required

If you don't provide a value, the default is used.

Description

A brief description of the attachment.

This can be any string of specified length.

Not Required

Not required

FileName

Name of the attachment file in which the attachment is stored.

This can be any string of specified length.

Either the File name or the URL is mandatory.

Either the File name or the URL is mandatory.

PK2 Value

This is the primary key of the record to which the attachment is being associated.

This is useful when the object has a composite primary key.

This is useful when the object has a composite primary key.

This is useful when the object has a composite primary key.

PK3 Value

This is the primary key of the record to which the attachment is being associated.

This is useful when the object has a composite primary key.

This is useful when the object has a composite primary key.

This is useful when the object has a composite primary key.

PK4 Value

This is the primary key of the record to which the attachment is being associated.

This is useful when the object has a composite primary key.

This is useful when the object has a composite primary key.

This is useful when the object has a composite primary key.

PK5 Value

This is the primary key of the record to which the attachment is being associated.

This is useful when the object has a composite primary key.

This is useful when the object has a composite primary key.

This is useful when the object has a composite primary key.

URL

If the attachment type is url, this specifies the url.

The URL format is validated.

Either the file name or the URL is mandatory.

Either the file name or the URL is mandatory.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the attachment 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 Attachment 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 attachment 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 Attachment 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 Business Plan Data

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

You can import business plan records using these steps:

  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 Business Plan 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. For example, when importing the address of an account, ensure the account exists.

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. 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 Business Plan object, this attribute is BusinessPlanId.

  • 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 BusinessPlan object, the attribute is BusinessPlanNumber.

Review Required Attributes and Validations for Business Plan 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 Business Plan records, required attributes for updating Business Plan records, prerequisite setup tasks for the attributes, and specific validations, if any, for Business Plan import:

Attribute Description Data Type Data Length Prerequisite Setup Task/ Import Validations Creating a Business Plan record Updating an Existing Business Plan record

BusinessPlanId

Unique Identifier

Long

18

None

Not required

Required

BusinessPlanNumber

Public Unique Identifier

String

64

None

Not required

A value is required either for BusinessPlanId or for BusinessPlanNumber.

PeriodTypeCode

Period Type such as Year, Quarter, or Period

String

30

Use the Manage Calendar Profile Option task to set a value for ZCA_COMMON_CALENDAR.

Required

Not Required

StatusCode

Status of the BusinessPlan such as ORA_DRAFT, ORA_APPROVED

String

30

None

Required

Not required.

PeriodEndDisplayName

End Period Display Name

String

60

None

Required

Not required.

PeriodStartDisplayName

Start Period Display Name

String

60

None

Required

Not required.

Name

Unique name of the business plan

String

60

Enter a unique value.

Required

Not required.

BusinessPlanClassCode

Class of the business plan such as Account or Partner

String

20

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

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Business Plan Classes

The default value is PARTNER.

Required

Not required.

PartnerId

Internal identifier of the Partner

Long

18

Enter the PartnerId if you select the BusinessPlanClassCode as PARTNER.

A value is required, if you don't specify the PartnerNumber.

Not required

PartnerNumber

Public unique identifier of the Partner

String

30

Enter the PartnerId if you select the BusinessPlanClassCode as PARTNER.

A value is required, if you don't specify the PartnerId.

Not required

CustomerId

Internal identifier of the Account

Long

18

Enter the PartnerId if you select the BusinessPlanClassCode as PARTNER.

A value is required, if you don't specify the CustomerNumber.

Not required

CustomerNumber

Public unique identifier of the Account

String

30

Enter the CustomerId or the CustomerNumber, if you select the BusinessPlanClassCode as ACCOUNT.

A value is required, if you don't specify the CustomerId.

Not required

You can view the Business Plan 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 Contact 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. 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 Business Plan 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 Business Plan SWOT Data

You can use Import Management to create, update, or delete your business plan SWOT data.

To import Business Plan SWOT 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 Business Plan SWOT 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. For example, when importing the address of an account, ensure the account exists.

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. 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 Business Plan SWOT object, this attribute is SWOTId.

  • 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 BusinessPlan SWOT object, the attribute is SWOTNumber.

Required Attributes and Validations for Business Plan SWOT 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 Business Plan SWOT records, required attributes for updating Business Plan SWOT records, prerequisite setup tasks for the attributes, and specific validations, if any, for Business Plan SWOT import:

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

SWOTTypeCode

Identifies one of the four seeded and not extensible SWOT type codes:

  • STRENGTH

  • WEAKNESS

  • OPPORTUNITY

  • THREAT

String

30

None

Required

Not required

SWOTDescription

A brief description of the SWOT types

String

2000

None

Required

Not required

SWOTId

Unique identifier of the SWOT

Long

18

None

Not required

Required

SWOTNumber

A unique number that identifies the SWOT record

String

64

None

Not required

Either the SWOTNumber or the SWOTId is required to update the records.

BusinessPlanId

The primary key of the parent record

Long

18

None

A value is required to define to which business plan this child record of the SWOT belongs.

Not required.

BusinessPlanNumber

A unique number that identifies the business plan

String

64

None

A value is required either for the BusinessPlanId or for the BusinessPlanNumber.

Not required.

You can view the Business Plan SWOT 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. In the Navigator, under Tools, click Import Management.

  2. Click Import Objects tab to open the Import Object Details page.

  3. Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.

  4. Save the template CSV file to a location on your desktop.

You must edit the template CSV file and provide valid values for the required attributes. You can attach different types of files, giving each file a specific description.

Description SWOTTypeCode BusinessPlanNumber

swot description

THREAT

myBP_0173

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. 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 Business Plan SWOT 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.

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 Business Plan Team Data

Use this topic to import Business Plan Team data into Oracle Applications Cloud. You can use the import functionality to create or update Business Plan Team records.

To import Business Plan Team 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 Business Plan Team 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 need to set certain options for some attributes in the application before you can populate them. When importing a child record, ensure that its parent record exists in the database.

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. 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 Business Plan Team object, this attribute is BusinessPlanResourceId.

  • 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 Business Plan Team object, the attribute is BusinessPlanResourceNumber.

Required Attributes and Validations

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 Business Plan Team records, required attributes for updating Business Plan Team records, prerequisite setup tasks for the attributes, and specific validations, if any, for Business Plan Team import:

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

ResourceId

Specifies the resource added to the business team plan

Long

18

None

Required

Not required

BusinessPlanId

Specifies the parent record ID for which this child record is being created

Long

18

None

Required

Not required

BusinessPlanResourceNumber

A unique number that identifies the business plan

String

230

None

Not required

Required

ResourceNumber

A unique identifier that identifies the resource (team member) number

String

30

None

Either the ResourceNumber or the ResourceId is required when creating a record.

Not required.

BusinessPlanResourceId

The unique identifier of the business plan

Long

18

None

Not required

Either the BusinessPlanResourceId or the BusinessPlanResourceNumber is required to update the records.

BusinessPlanNumber

A unique number that identifies the business plan

String

64

None

Either the BusinessPlanResourceId or the BusinessPlanResourceNumber is required to create the records.

Not required.

You can view the Business Plan Team 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. In the Navigator, under Tools, click Import Management.

  2. Click Import Objects tab to open the Import Object Details page.

  3. Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.

  4. Save the template CSV file to a location on your desktop.

You must edit the template CSV file and provide valid values for the required attributes. You can attach different types of files, giving each file a specific description.

MemberFunctionCode ResourceId BusinessPlanNumber

ORA_BUS_DEVELOPMENT

100010032635399

myBP_0173

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. 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 Business Plan Team 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.

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 Classification Data

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

You can import classification records using these steps:

  1. Map your source classification 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 classification 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 classification data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.

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

If you want to import only a few records, then you can create a single CSV file for all classification 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 classification child objects. Note that you must have imported the CSV file for classification 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 classifications or are updating classifications that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Classification 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 classification records, prerequisite setup tasks and specific validations, if any:

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

PartySourceSystem

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

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

Conditionally required

Provide one of the following :

  • PartyId (internal ID)

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

Optional

PartySourceSystemReferenceValue

The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the classification belongs.

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

Conditionally Required

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

  • PartyId ( internal ID)

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

  • Party Number (public unique identifier for an organization profile)

Optional

PrimaryFlag

Identifies primary classification for the parent party record.

Only one of the child records can be Primary.

Optional

Optional

Pass Y to set Primary and N to reset an existing primary record.

CodeAssignmentId

The unique identifier for the customer classification assignment.

It should be a valid existing value.

Not required

Either the Code assignment Id or a combination of Source System and Source System Reference is required.

ClassCategory

The classification category name

The class category must exist. You can manage class categories from the Manage Class Categories task.

Required

A value is required if creating a new classification association record.

Not Required

ClassCode

The classification code, within the classification category, assigned to the party.

The value must be a valid code for the classification category. You can only assign one code if the category definition isn't enabled for multiple code assignments to a party within the same category. The code assignment must not already exist within the same time period. You can obtain classification codes for a classification category.

Conditionally required

A value is required if creating a new classification association record.

Not Required

StartDateActive

The date on which the classification becomes valid.

This should be a valid date.

This defaults to the current date.

Not required

PartyId

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

Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on.

Conditionally required

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

  • PartyId (internal ID)

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

  • Party Number (public unique identifier for an organization profile)

Not required

PartyNumber

The public unique identifier of the party record to which the classification category and classification code are associated.

The party number must exist.

Conditionally Required

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

  • PartyId (internal ID)

  • PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile

  • Party Number (public unique identifier for an organization profile)

Not required

EndDateActive

The date on which the classification code is no longer valid.

This should be a valid date.

Optional

Not required

SourceSystem

Name of external source system of the account, contact or household with which the address is associated.

The source system should exist.

You can manage source systems from the Manage Source Systems task.

Optional

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

Not required

SourceSystemReferenceValue

Specifies the identifier in the original source system

The combination of Source System and Source System Reference Value should be unique.

Optional

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

Not required

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the classification 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 Classification 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 classification 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 Classification 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 Classification Code Data

You can use Import Management to create or update Classification Code records.

To import Classification Code 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 Classification Code 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.

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

Before You Start

You must do some basic checks before starting your import. For example:

  • Complete all the prerequisites for importing each attribute in your source data.

  • Have all parent records in place before importing child records.

Required Attributes and Validations for the Classification Code 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 Classification Code records, prerequisite setup tasks for the attributes, and specific validations, if any, for Classification Code import:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Classification Code Record Updating an Existing Classification Code Record

ClassCategory

User-defined classification category

No validation

Required

You can't update the ClassCategory. However, it's required to identify the existing data.

ClassCode

User defined class codes for the user defined class category

No validation

Required

You can't update the ClassCode. However, it's required to identify the existing data.

Description

Brief description of the classification code

No validation

Required

Required

Meaning

The meaning of the classification code

No validation

Required

Required

ModifyHierarchy

Option to indicate if the parent and child hierarchies of the classification codes are to be modified

No validation

Optional

Not required

ParentClassCode

If there is a hierarchy set between the classification codes, then provide the parent classification code to which the child classification code belongs.

User- defined ClassCategory via the "Manage Classification Categories" UI.

Optional

Not required

You can view the Classification Code 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 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 Classification Code 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 Classification Code 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.

Import Your Competitor Data

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

To import Competitor 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 Competitor 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.

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

Before You Start

You must do some basic checks before starting your import. For example:

  • Complete all the prerequisites for importing each attribute in your source data.

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

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. 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 Competitor object, the attributes are Party Id and Registry Id.

Required Attributes and Validations for the Competitor 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 Competitor records, prerequisite setup tasks for the attributes, and specific validations, if any, for Competitor import:

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

Organization Name

Competitor Name - The name that identifies the competitor object

Not Applicable

Required

Conditionally Required

Name

Competitor Name - The name that identifies the competitor object

Not Applicable

Conditionally Required

Conditionally Required

Party Type

Competitor Party Type -Type of party record

Not Applicable

Conditionally Required

The default value is ORGANIZATION.

Do not provide a value.

Party ID

PartyId -The unique ID for the existing competitor record.

A list of all party IDs is obtained by exporting the Competitor object.

Do not provide a value.

Required

Registry ID

Registry ID (PartyNumber) - The public unique identifier of the Competitor.

Not Applicable

Do not provide a value.

Conditionally Required

You can view the Competitor 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 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 Competitor 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 Competitor 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.

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.

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.

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 Contact Member Data

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

You can import contact member records using these steps:

  1. Map your source contact member 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 member 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 member 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

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 contact members or are updating contact members that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Contact Member 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 member records, prerequisite setup tasks and specific validations, if any:

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

MemberId

The unique ID for the existing member record in the Oracle Fusion destination table.

The unique Id for the existing account Id record in the Oracle Fusion destination table.

Not required

Conditionally required

A value is required if you're updating an existing Member ID and you're not providing the Service Request ID and Party ID.

PartyId

The unique ID for the existing party record in the Oracle Fusion destination table.

Do not provide a value if creating a new party in the same import batch as this additional party name. If you provide the value for an existing party, the value must exist in the HZ_PARTIES table, column PARTY_ID. You can obtain the PARTY_ID for an existing party by exporting the Party object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Manage Bulk Data Export, Schedule Export Processes

Not required

Not required

Relationship Type Code

Indicates relationship with the contact, such as ALTERNATE, FOLLOWER, or THIRD_PARTY.

If providing a value, the value must exist in the FND_LOOKUPS table with LOOKUP_TYPE='ORA_SVC_CONTACT_REL_TYPE_CD'.

Required

Required

Service Request ID

Indicates the service request Id to which the contact member belongs.

No validation

Not required

Conditionally required

A value is required if you're updating an existing contact and you're not providing the SRNumber.

SRNumber

The unique number used to identify a service request. You can configure the service request number to a format that's best suitable to your organizational requirements.

No validation

Conditionally required

A value is required if you're updating an existing record and you're not providing the Service Request ID..

Conditionally required

A value is required if you're updating an existing record and you're not providing the Service Request ID.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the contact member 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 Member 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 contact member 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 Member 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 Contact Point Data

You can use Import Management to create update, or delete Contact Point records.

To import Contact Point 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 Contact Point 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 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 Contact Point 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 Contact Point records, required attributes for updating Contact Point records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contact Point import:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Contact Point Record Updating an Existing Contact Point Record

ContactPointType

Type of the contact point that's imported or updated

This has to be a lookup_code in HZ_LOOKUPS with a lookup_type as COMMUNICATION_TYPE

Provide one of these values:

  • EMAIL, if the email address is to be imported.

  • INSTANT_MESSAGING, if the instant messenger address is to be imported.

  • WEB, if the URL is to be imported.

  • PHONE, if the phone number is to be imported.

Not required

PartyId

The internal ID for the party to which the contact point belongs

No validation

Provide one of the following :

  • PartyId

  • Party Number

  • A combination of Party Source System and Party Source System Reference Value

Not required

PartyNumber

Specifies the PUID of the party

No validation

Provide one of the following :

  • PartyId

  • Party Number

  • A combination of Party Source System and Party Source System Reference Value

Not required

Party Source System

Specifies the original source system of the party

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

Provide one of the following :

  • PartyId

  • Party Number

  • A combination of Party Source System and Party Source System Reference Value

Not required

Party Source System Reference Value

Specifies the party's source system reference in the original source system

No validation

Provide one of the following :

  • PartyId

  • Party Number

  • A combination of Party Source System and Party Source System Reference Value

Not required

SourceSystem

Specifies the original source system name

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

Provide a valid value.

Not required

SourceSystemReferenceValue

Specifies the identifier in the original source system

No validation

Provide a valid value.

Not required

ContactPointId

This is the primary key. It is the unique identifier of the contact point.

No validation

Not required

If you can export the existing contact point, provide this primary key to identify the record for further updates.

ConflictId

The unique identifier of the conflict.

No validation

Not required

Not required

Status

The status of the contact point.

Not required

This defaults to Y during creation.

Not required

To inactivate the existing active contact point record, provide the value "N".

You can view the Contact Point 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 Contact Point 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 Contact Point 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 Deal Product Data

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

To import Deal Product 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 Deal Product 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. For example, when importing the address of an account, ensure the account exists.

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. 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 Deal Product object, this attribute is DealProdId.

  • 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 Deal Product object, the attribute is DealProdNumber.

Review Required Attributes and Validations for Deal Product 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 Deal Product records, required attributes for updating Deal Product records, prerequisite setup tasks for the attributes, and specific validations, if any, for Deal Product import:

Attribute Description Data Type Data Length Prerequisite Setup Task/ Import Validations Creating a Deal Product record Updating an Existing Deal Product record

DealNumber

The public unique identifier value for the deal.

Text

30

You can obtain the Deal Number for an existing deal registration from the Deal Registration work area.

Conditionally required

Provide either the DealId or the DealNumber to identify the deal.

Conditionally required

Provide either the DealId or the DealNumber to identify the deal.

DealId

The unique ID for the existing deal record in the destination table..

Number

18

The deal must exist.

Conditionally required

Provide either the DealId or the DealNumber to identify the deal.

Conditionally required

Provide either the DealId or the DealNumber to identify the deal.

DealProdNumber

The relationship between the deal registration and the deal product.

Text

30

You can obtain the DealProductNumber for an existing deal registration product from the Deal Registration work area.

Required

Conditionally required

Provide either the DealId or the DealNumber to identify the deal.

ProductGroupNumber

The public unique identifier value for the deal registration product group.

You can obtain the ItemNumber for an existing deal registration product from the Deal Registration work area.

Conditionally required

When you import a new deal registration product item (as opposed to a product group), then you must provide either the ProductGroupNumber or the ProductGroupId.

Conditionally required

When you import a new deal registration product item (as opposed to a product group), then you must provide either ProductGroupNumber or ProductGroupId

DealProdId

The unique ID for the existing deal product record in the destination table.

Number

18

The deal product must exist.

Not required

Conditionally required

You must provide either the DealProductId or the DealProductNumber to identify the product.

ItemNumber

The public unique identifier value for the deal registration product item.

Text

30

You can obtain the ItemNumber for an existing deal registration product from the Deal Registration work area.

Conditionally required

When you import a new deal registration product item (as opposed to a product group), then you must provide either the ItemNumber or the InventoryItemId.

Conditionally required

When you update deal registration product item (as opposed to a product group), then you must provide either ItemNumber or InventoryItemId.

InventoryItemId

The unique ID for the existing sales catalog product (item) record in the destination table.

Number

18

You can determine the InventoryItemId by exporting the Product Group Products object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Conditionally required

When you import a new deal registration product item (as opposed to a product group), then you must provide either the ItemNumber or the InventoryItemId.

Conditionally required

When you update deal registration product item (as opposed to a product group), then you must provide either ItemNumber or InventoryItemId.

ProductGroupId

Unique Product Group ID defined in sales product catalog.

Number

18

You can determine the ProdGroupId by exporting the Product Group Products object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Conditionally required

When you import a new deal registration product item (as opposed to a product group), then you must provide either the ItemNumber or the InventoryItemId.

Conditionally required

When you update deal registration product item (as opposed to a product group), then you must provide either ItemNumber or InventoryItemId.

UomCode

Specifies the Unit of measure

Number

None

You can determine the units of measure. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Financials

  • Functional Area: Items

  • Task: Manage Units of Measure Profiles

Conditionally required

A value is required when you import a new deal registration that's associated with product (Items).

Not required

RegisteredPrice

The value for the price of the product item associated to the deal registration.

Number

None

You can obtain the RegisteredPrice for an existing deal registration using the Deal Registration work area.

Not required

Not required

InvOrgId

The unique ID for the existing product item organization's record in the destination table.

Number

18

You can determine the InvOrgId by exporting the Product Group Products object. Navigate to the following in the Setup and Maintenance work area:

  • Offering: Sales

  • Functional Area: Data Import and Export

  • Task: Schedule Export Processes

Conditionally required

A value is required when you import a new deal registration that's associated with product (Items).

Conditionally required

A value is required when you update an existing deal registration that's associated with product (Items), and you don't provide the product's ID (InventoryItemId).

You can view the Deal Product 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 Deal Product 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. 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 Deal Product 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 Deal Registration Data

You can use import management to create or update Deal Registration records.

To import Deal Registration 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 Deal Registration 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.

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 Deal Registrations. 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 Deal Registration object, the attribute is DealID.

  • 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 Deal Registration object, the attributes are:

    • AccountPartyNumber

    • ContactPartyNumber

    • OwnerPartyNumber

    • MatchedAccountPartyNumber

    • MatchedContactPartyNumber

    • OptyNumber

    • LeadNumber

    • PartnerCompanyNumber

    • ProgramEnrollmentNumber

    • DealNumber

Required Attributes and Validations for Deal Registration 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 Deal Registration records, required attributes for updating Deal Registration records, prerequisite setup tasks for the attributes, and specific validations, if any, for Deal Registration import:

Attribute Description Prerequisite Setup Task/ Import Validations Creating a Deal Registration Record Updating an Existing Deal Registration Record

AccountPartyNumber

The public unique identifier of account party on the deal registration

None

Required

Not required

ContactPartyNumber

The public unique identifier of contact party on the deal registration

None

Required

Not required

OwnerPartyNumber

The public unique identifier of owner party on the deal registration

None

Required

Not required

MatchedAccountPartyNumber

The public unique identifier of the matched account party on the deal registration

The deal registration should have the status "Approved".

Not required

Not required

MatchedContactPartyNumber

The public unique identifier of the matched contact party on the deal registration

The deal registration should have the status "Approved".

Not required

Not required

OptyNumber

The public unique identifier of the opportunity associated with the deal registration

The deal registration should have the status "Approved".

Not required

Not required

LeadNumber

The public unique identifier of the lead associated with the deal registration.

The deal registration should have an associated lead.

Not required

Not required

PartnerCompanyNumber

The unique identifier of the partner associated with the deal registration

None

Required

Not required

ProgramEnrollmentNumber

The unique identifier of the partner program enrollment in the context of the deal registration

The partner associated with the deal registration should be enrolled in a program.

Not required

Not required

DealID

The unique identifier of the deal registration.

None

Required

Required

DealNumber

The alternate identifier of the deal registration.

None

Required

Not required

You can view the Deal Registration 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 Deal Registration 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 Deal Registration 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 Deal Resource Data

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

To import Deal Resource 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 Deal Resource 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.

Before You Begin

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. 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 Deal Resource object, this attribute is DealResourceId.

  • Public unique identifiers: If you're creating 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 Deal Resource object, the attribute is DealResourceNumber.

Required Attributes and Validations for Deal Resource 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 Deal Resource records, required attributes for updating Deal Resource records, prerequisite setup tasks for the attributes, and specific validations, if any, for Deal Resource import:

Attribute Description Data Type Data Length Prerequisite Setup Task/ Import Validations Creating a Deal Resource record Updating an Existing Deal Resource record

DealId

The unique ID for the existing deal record in the destination table.

Number

18

The deal must exist.

Conditionally required

Provide either the DealId or the DealNumber to identify the deal.

Conditionally required

Provide either the DealId or the DealNumber to identify the deal.

DealNumber

The public unique identifier value for the deal.

Text

30

You can obtain the Deal Number for an existing deal registration from the Deal Registration work area.

Conditionally required

Provide either the DealId or the DealNumber to identify the deal.

Conditionally required

Provide either the DealId or the DealNumber to identify the deal.

DealResourceNumber

The unique identifier for the relationship between the resource and the deal registration.

Number

18

You can obtain the DealResourceNumber for an existing deal registration product from the Deal Registration work area.

Required

Conditionally required

Provide either the DealResourceId or the DealResourceNumber to identify the resource.

DealResourceId

The unique ID for the existing deal product record in the destination table.

Number

18

The deal resource must exist.

Not required

Conditionally required

You must provide either the DealResourceId or the DealResourceNumber to identify the resource.

ResourcePartyNumber

The public unique identifier value for the resource party record.

Number

18

You can obtain the ResourcePartyNumber for a resource associated with an existing deal registration from the Deal Registration work area.

Conditionally required

You must provide one of the following to identify the resource:

  • ResourcePartyNumber

  • ResourcePartyId

  • combination of ResourcePartyOrigSys and ResourcePartyOrigSysRef.

Conditionally required

You must provide one of the following to identify the resource:

  • ResourcePartyNumber

  • ResourcePartyId

  • combination of ResourcePartyOrigSys and ResourcePartyOrigSysRef.

ResourcePartyId

The unique ID for the existing deal resource record in the destination table.

Number

18

The resource must exist.

Conditionally required

Provide either the ResourcePartyNumber or the ResourcePartyId to identify the resource.

Conditionally required

Provide either the ResourcePartyNumber or the ResourcePartyId to identify the resource.

You can view the Deal Resource 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 Deal Resource 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 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 Deal Resource 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 Eligibility Rule Data

You can use the Import Management to create or update Eligibility Rule records.

To import Eligibility Rule 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 Eligibility Rule 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 options for uniquely identifying 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. 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 Eligibility Rule object, this attribute is EligibilityRuleId.

  • 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 Eligibility Rule Item object, the attributes are ParPGReferenceNumber, ItemNumber, and GeographyCode.

Required Attributes and Validations for Eligibility Rule 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 Eligibility Rule records, required attributes for updating Eligibility Rule records, prerequisite setup tasks for the attributes, and specific validations, if any, for Eligibility Rule import:

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

EligibilityRuleId

Autogenerated Id to update the record.

Long

18

No validation

Not Required

Required

RuleType

This can have only two values -AVAILABLE and NOTAVAILABLE.

String

30

No validation

Required

Not Required

StartDate

The start date of the eligibility rule

Date Time

The StartDate can't be greater than the EndDate

Not Required

Not Required

EndDate

The end date of the eligibility rule

Date Time

No validation

Not Required

Not Required

ProductNumber

Product number against which this eligibility rule is created or updated

String

300

No validation

Required

Required

ProdGroupId

Required if creating a new eligibility rule using the Internal ID

Long

18

No validation

Required

Not Required

ParPGReferenceNumber

Required if creating or updating an existing eligibility rule using the PUID

String

50

No validation

Required

Required

InventoryItemId

Required if creating a new eligibility rule using the Internal ID

Long

18

No validation

Required

Not Required

InvOrgId

Required if creating a new eligibility rule using the Internal ID

Long

18

No validation

Required

Not Required

GeographyId

Required if creating a new eligibility rule using the Internal ID

Long

18

There can't be more than one eligibility rule for the same country.

Required

Not Required

CountryName

Specify value to update the country for an existing eligibility rule using the PUID.

String

No validation

Not Required

Not Required

GeographyCode

Required if creating or updating an existing eligibility rule using the PUID.

String

There can't be more than one eligibility rule for the same country.

Required

To create an Eligibility Rule for all the countries, specify the Geography code value as "ALL". To create an Eligibility Rule for a specific country (for example, USA), specify the Geography code value as "US".

Required

When updating an Eligibility Rule with the PUID, if you update the Geography Code from "ALL" to "US", specify the value of Geography Code as "ALL" in the import CSV file. Specify the value as "United States" for the "CountryName" attribute.

You can view the Eligibility Rule 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 Eligibility Rule 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 Eligibility Rule 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 Geography Data

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

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.

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

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 Geographies. 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 Geography object, the attributes are Batch Id and Interface Row Id.

  • 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 Geography object, the attribute is Import Activity Identifier.

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 valid 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 country structure to check if the structure is defined for this geography name.

Required

RecordTypeCode

Specifies the data that needs to be created

No Validation

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

You can enable high-volume import for the Geography import object in the Manage Import Objects 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 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.

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 Hierarchy Member Data

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

To import Hierarchy Member 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 Member 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 identify an object record is through the 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 Hierarchy Member object, the attributes are:

  • TreeStructureCode

  • TreeCode

  • PartyNumber

  • ParentPartyNumber

  • AsofDate

Required Attributes and Validations for Hierarchy Member 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 Member records, required attributes for updating Hierarchy Member records, prerequisite setup tasks for the attributes, and specific validations, if any, for Hierarchy Member import:

Attribute Description Data Type Data Length Prerequisite Setup Task/ Import Validations Creating a Hierarchy Member Record Updating an Existing Hierarchy Member 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

PartySourceSystem

Original System Id for the party.

An account needs to exist.

Required

Required

PartySourceSystemReference

Original System Reference for the party.

An account needs to exist.

Required

Optional

PartyId

Unique Id for the Party.

Number

18

An account needs to exist.

Required

Required

ParentPartyId

Unique Id for the Parent Party.

Number

18

An account needs to exist.

Required

Required

ParentPartySourceSystem

Original System Id for the parent party.

Varchar2

30

An account needs to exist.

Required

Optional

ParentPartySourceSystemReference

Original System Id for the parent party.

Varchar2

240

An account needs to exist.

Required

Optional

LabelShortName

Label Name based on the position in the tree hierarchy with respect to the child.

Varchar2

80

Seeded data has to exist.

Required

Optional

PartyNumber

Unique identification number for this party.

Varchar2

30

An account needs to exist.

Required

Optional

ParentPartyNumber

Unique identification number for this parent party.

Varchar2

30

An account needs to exist.

Required

Optional

You can view the Hierarchy Member 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 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 Hierarchy Member object in the table and click Download.

You must edit the template CSV file and provide valid values for the required attributes. You can attach different types of files, giving each file a specific description.

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

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 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 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 Incentive Transaction Data

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

To import Incentive Transaction 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 Incentive Transaction 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 through 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 Incentive Transactions. 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 Incentive Transaction object, the attributes are Transaction Number and Transaction Type.

Required Attributes and Validations for Incentive Transaction 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 Incentive Transaction records, required attributes for updating Incentive Transaction records, prerequisite setup tasks for the attributes, and specific validations, if any, for Incentive Transaction import:

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

Business Unit

Name of the business unit

Varchar2

240

To find the business unit:

  1. Navigate to Setup and Maintenance.

  2. Navigate to the Manage Business Units task.

  3. In the Search results region, search for the name and select the name that's displayed.

Note: You can export the results to a spreadsheet and use this information to identify and assign the Business Unit values to the data that you're preparing.

Required

A value is required either for the Business Unit or the Business Unit Id.

Required

A value is required either for the Business Unit or the Business Unit Id.

Business Unit ID

Unique numeric identifier for the Oracle Fusion Incentive Compensation business unit.

Number

18

To find the business unit:

  1. Navigate to Setup and Maintenance.

  2. Navigate to the Manage Business Units task.

  3. In the Search results region, click the View menu and add the Business Unit ID Column.

Note: You can export the results to a spreadsheet and use this information to identify and assign the Business Unit ID values to the data that you're preparing.

Required

A value is required either for the Business Unit or the Business Unit Id.

Required

A value is required either for the Business Unit or the Business Unit Id.

Event Date

When the transaction triggers an incentive event associated with the row, for example, salespeople are compensated when an invoice is booked or an order is posted.

Date

The period must be open before you can collect the transaction into the application.

Required

Required

Transaction Amount

The transaction amount to be evaluated by the credit and earning processes.

Number

If providing a monetary amount, the amount should be in the currency of the source application.

Required

Required

Transaction Number

Unique transaction identifier used in the source application. The combination of Source Transaction Number and Transaction Type values must be unique, and is validated during the Collect Transactions process.

Varchar2

30

Map an identifier that end users recognize and can search. For example, map your source invoice number and invoice line number to this field.

Required

Required

Transaction Type

Defines the type of the transaction. Predefined transaction types are CLAWBACK, CUSTOMER_SATISFACTION, GRP, INVOICE, ITD, MANUAL, ORDER, PAYMENT, and RAM_ADJUSTMENT.

Varchar2

30

The value must be a valid lookup code for lookup type CN_TP_TRANSACTION_TYPE. To define your own transaction types:

  1. In Setup and Maintenance, go to the Manage Incentive Compensation Lookups task.

  2. Search for CN_TP_TRANSACTION_TYPE.

  3. Add your transaction types.

Required

Required

You can view the Incentive Transaction 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 Incentive Transaction 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 Incentive Transaction 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

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 Interaction Data

You can use the Import Management to create or update Interaction records.

To import Interaction 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 Interaction 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 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. 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 Interaction object, this attribute is InteractionId:

  • 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 Interaction object, the attribute is InteractionNumber.

Required Attributes and Validations for Interaction 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 Interaction records, required attributes for updating Interaction records, prerequisite setup tasks for the attributes, and specific validations, if any, for Interaction import:

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

InteractionId

The unique identifier of the interaction

Long

18

None

Not required

Required

InteractionNumber

The Public Unique Identifier of the interaction

Varchar

30

None

Not required

Not required

ChannelId

The unique identifier of the interaction channel

Long

18

The referenced record must exist.

Required

Not Required

StripeCd

The code indicating the stripe of the interaction. A list of valid values is defined in the lookup ORA_SVC_STRIPE_CD.

Varchar2

30

None

Not required

Required

StatusCd

The current status of the interaction. Interactions are either in the ORA_SVC_OPEN or ORA_SVC_CLOSED status.

Varchar

30

Default "ORA_SVC_OPEN"

Not required

Not required

DirectionCd

The code indicating whether the interaction is inbound or outbou