Import Your Conversation Message Recipient Data

You can use Import Management to create, update, or delete Conversation Message Recipient records.

To import Conversation Message Recipient 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 Conversation Message Recipient 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.

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

• Ensure parent records exist before importing child records.

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

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

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Conversation Message Recipient Record	Updating an Existing Conversation Message Recipient Record	Deleting an Existing Conversation Message Recipient Record
MessagesId	The unique identifier of the message.	Must be a valid Conversation Message Identifier.	Conditionally Required. Provide value if the MessagesNumber isn't provided.	Not Required	Not Required
MessagesNumber	The public unique identifier of the message.	Must be a valid Conversation Message PUID.	Conditionally Required. Provide value if the MessagesId isn't provided.	Not Required	Not Required
RecipientId	The unique identifier of the message recipient record.	Must be a valid RecipientId when updating a message recipient.	Not Required	Conditionally Required. Provide value if the RecipientNumber isn't provided.	Conditionally Required. Provide value if the RecipientNumber isn't provided.
RecipientNumber	The public unique identifier of the message recipient record.	Must be a valid RecipientNumber when updating a message recipient.	Not Required	Conditionally Required. Provide value if the RecipientId isn't provided.	Conditionally Required. Provide value if the RecipientId isn't provided.
RecipientPartyId	The party identifier of the message recipient.	Must be a valid party identifier.	Not Required. Recommend to pass one of RecipientPartyId, RecipientPartyNumber, or FreeFormAddress.	Not Required	Not Required
RecipientPartyNumber	The public unique identifier of the message recipient.	Must be a valid Party PUID.	Not Required. Recommend to pass one of RecipientPartyId, RecipientPartyNumber, or FreeFormAddress.	Not Required	Not Required
RecipientTypeCd	The type of the message recipient, such as TO, CC, BCC.	Valid values are: ORA_SVC_BCC, ORA_SVC_CC, ORA_SVC_FROM, ORA_SVC_TO.	Not Required. If not passed, it will be defaulted to ORA_SVC_TO.	Not Required	Not Required
FreeFormAddress	The free form address of the recipient such as email address.	None	Not Required. Recommend to pass one of RecipientPartyId, RecipientPartyNumber, or FreeFormAddress.	Not Required	Not Required

You can view the Conversation Message Recipient object and its attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on 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:

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

2. Select the Conversation Message Recipient 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 Conversation Message Recipient from the Object drop-down list.

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

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

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