Import Your Interaction Data

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 outbound. The default value is ORA_SVC_INBOUND, indicating inbound interactions. The value is ORA_SVC_OUTBOUND for outbound interactions.	Varchar	30	Default "ORA_SVC_INBOUND"	Not required	Not required
ParentInteractionId	The unique identifier of the parent interaction.	Long	18	The referenced record must exist, if included.	Not required	Not required
Description	The brief description of the interaction	Long	1000	None	Not required	Not required
AccountPartyId	The unique identifier of the account associated with the interaction	Long	18	The referenced record must exist, if included.	Not required	Not required
ContactPartyId	The unique identifier of the contact associated with the interaction	Long	18	The referenced record must exist, if included.	Not required	Not required
OwnerResourceId	The unique identifier of the owner of the interaction	Long	18	The referenced record must exist, if included.	Not required	Not required
MediaItemId	The unique identifier for the media item	Long	18	The referenced record must exist, if included.	Not required	Not required
StartTime	The time when the interaction becomes active	Date Time	None	None	Required	Not required
EndTime	The time when the interaction becomes inactive	Date Time	None	None	A value is required if the status is "ORA_SVC_CLOSED".	Not required
OriginalSystemReference	The system reference used by the interaction	Varchar	255	None	Not required	Not required
SubStatusCd	The code indicating the sub-status of the interaction. A list of valid values is defined in the lookup ORA_SVC_IM_CLOSED_SUBSTATUS_CD.	Varchar	30	None	Not required	Not required
QueueId	The unique identifier of the interaction queue	Long	18	The referenced record must exist, if included.	Not required	Not required
AgentHTTPSessionId	The HTTP session Id of the agent	Varchar	100	None	Not required	Not required

You can view the Interaction 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 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 Interaction 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:

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