Import Your Message Data

You can use the Import Management to create, update, or delete service request message records.

You can import message 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 data you want to import.
Kick off an import activity.
Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

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

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 records, prerequisite setup tasks and specific validations, if any:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Message record	Updating an Existing Message record
Message Content	Content of the message that's not an attachment.	None	Required	Required
Message Type Code	Indicates the type of message. If providing a value, it must be one of the following: ORA_SVC_CUSTOMER_ENTRY ORA_SVC_RESPONSE ORA_SVC_INTERNAL_NOTE ORA_SVC_SYSTEM_NOTE	If providing a value, it must be one of the following: ORA_SVC_CUSTOMER_ENTRY ORA_SVC_FORWARD ORA_SVC_CHAT_TRANSCRIPT ORA_SVC_INTERNAL_NOTE ORA_SVC_RESPONSE ORA_SVC_SYSTEM_NOTE ORA_SVC_SYSTEM_RESPONSE ORA_SVC_WRAP_UP	Required	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	Do not pass if the Message Type Code = ORA_SVC_INTERNAL_NOTE	Do not pass if the Message Type Code = ORA_SVC_INTERNAL_NOTE
Object Type Code	Lookup code that indicates the object type based on the OBJECT_ID table, such as SVC_SR_MESSAGES.	No validation	Do not pass if the Message Type Code = ORA_SVC_INTERNAL_NOTE	Do not pass if the Message Type Code = ORA_SVC_INTERNAL_NOTE
Posted By ID	The Party Id of the person who posted the message. This person can be an internal resource or a customer contact.	No Validation	Not required	Conditionally required A value is required if you're updating an existing Posted By ID and you're not providing the party Id which is obtained from the table HZ_IMP_PARTIES_T.
Service Request ID	Specifies the service request to which the message belongs.	No validation	Not required	Conditionally required A value is required if you're updating an existing record and you're not providing the SRNumber.
SR Number	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..
Status Code	Indicates the status of the message, such as DRAFT, COMMITTED, and CORRECTED.	If providing a value, it must be one of the following: ORA_SVC_DRAFT ORA_SVC_COMMITTED ORA_SVC_CORRECTED	Required	Required
Notification Processing Status Code	The notification processing status code.	No validation	Do not pass if the Message Type Code = ORA_SVC_INTERNAL_NOTE	Do not pass if the Message Type Code = ORA_SVC_INTERNAL_NOTE
Notification Retry Count	The notification retry count.	No Validation	Do not pass if the Message Type Code = ORA_SVC_INTERNAL_NOTE	Do not pass if the Message Type Code = ORA_SVC_INTERNAL_NOTE

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