How do I import activity contact data?

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 Sales and Fusion 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:

Go to Navigator > Tools > Import Management > Import Objects.
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:

Go to Navigator > Tools > Import Management > Import Queue.
Click Create Import Activity in the Manage Imports page.
In the Enter Import Options page, provide a name for the import activity, and select Activity Contact from the Object drop-down list.
Select the CSV file in the File Name field, and click Next.
You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.
Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.
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:

Go to Navigator > Tools > Import Management > Import Queue.
Click All Imports and search for the import activity that you created earlier.
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.