Import Your Service Request Message Communication Data

You can use the Import Management to create Service Request (SR) message communication records.

You can import message communication records using these steps:

Map your source message data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
Create the source CSV file with the message communication data you want to import.
Create the import activity.
Review the import results.

How You Map Your Source Data to Target Object Attributes

To import your message communication 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. Make sure that you have imported SR and SR Messages before importing the message communication 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.

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

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Message Communication record
MessageNumber	The public unique identifier of the service request message.	None	Conditionally Required. Either pass value for MessageNumber of ObjectId.
ChannelId	The unique identifier of the channel.	None	Required
Object ID	ID of the object (such as Note, Defect, Other SR) referencing the service request or referenced by the service request.	No validation	Conditionally required. Provide value for either ChannelId or ChannelShortName.
ChannelShortName	The public unique identifier of the channel.	No validation	Conditionally required. Provide value for either ChannelId or ChannelShortName.
PartyId	The unique party identifier of the person being communicated with.	No Validation	Conditionally required. Either pass PartyId or PartyNumber if you want to capture the message recipient or sender.
PartyNumber	The public unique identifier of the contact associated with the service request message.	No validation	Conditionally required. Either pass PartyId or PartyNumber if you want to capture the message recipient or sender.
PartyViaEndPoint	The endpoint used to communicate with the customer contact. For example Primarily used for Email.	No validation	Conditionally required. Provide value if you want to capture the email address of the message recipient.
RoutingCd	The code indicating how the message was routed through the endpoint.	No Validation	Conditionally required if you want to capture the sender or recipient of the message. Valid values are: ORA_SVC_BCC, ORA_SVC_CC, ORA_SVC_FROM, ORA_SVC_TO
ObjectId	The unique identifier of the object.	No validation	Conditionally Required. Either pass value for MessageNumber of ObjectId.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the message communication 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 Service Request Message Communication 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 message communication 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 Service Request Message Communication 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.