Import Your Case Message Data
You can use Import Management to create update, or delete Case Message records.
To import Case Message records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Case Message 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.
-
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 Case Messages or are updating Case Messages that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Case 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 importing new Case Message records, required attributes for updating Case Message records, prerequisite setup tasks for the attributes, and specific validations, if any, for Case Message import:
Attribute |
Description |
Prerequisite Setup Task/ Import Validations |
Creating a Case Message Record |
Updating an Existing Case Message Record |
---|---|---|---|---|
LastEditedDate |
Indicates the last edited date of the message for the case |
No validation |
Not required |
Not required |
MessageId |
Indicates the case message identifier |
A valid Id for the MessageId row in the destination system |
Not required |
Required |
MessageTypeCd |
Lookup code that indicates the type of message |
A valid unique MessageTypeCd in the destination system |
Required |
Not required |
OriginationDate |
Indicates the date on which the message was posted |
No validation |
Not required |
Not required |
PostedByPartyNumber |
Indicates the party number of the user who posted the message |
A valid PUID for the PostedByPartyNumber in the destination system |
Optional |
Optional |
RichTextFlag |
Indicates whether the message content is in rich text format (Y or N) |
A valid value from the lookup Y_N |
Required |
Optional |
VisibilityCd |
Lookup code that indicates the visibility of a message |
A valid value in the destination system |
Optional The default value is ORA_SVC_INTERNAL. |
Not required |
StatusCd |
Lookup code that indicates the status of the message |
A valid value in the destination system |
Required |
Optional |
CaseId |
Indicates the case to which this message is associated |
A valid CaseId in the destination system |
Not required |
Not required |
CaseNumber |
Indicates the case number to which this message is associated |
A valid CaseNumber in the destination system |
Not required |
Not required |
MessageNumber |
Indicates the reference number of the message ID |
A valid MessageNumber in the destination system |
Not required |
Not required |
You can view the Case Message 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
. -
Select the Case Message object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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
. -
Click Create Import Activity in the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select Case 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
. -
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.