Import Your Action Condition Data

You can use the import functionality to create, update, or delete your action condition data.

You can import action condition records using these steps:

Map your source 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 action condition 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

You import action condition data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.

Before you create the source data file, you should:

Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the action import object.
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
Know how you can uniquely identify the records.
Check the target object attributes required in the CSV file for a successful import.

If you want to import only a few records, then you can create a single CSV file for all action conditions. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the action child objects. Note that you must have imported the CSV file for action object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.

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:

The preferred option to uniquely identify an object record is through the 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 Action Condition Object, the attributes are Action ConditionId and ActionId:

Required Attributes and Validations for Action Condition 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 action condition records, prerequisite setup tasks and specific validations, if any:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating an Action Condition record	Updating an Existing Action Condition record
ActionCode	Indicates the operation to be performed on a row, such as insert, update, and so on	If a value isn't provided, records are matched to determine if a record is updated (if it already exists) or inserted (if it doesn't exist).	Not required	A value is required, if you're deleting an action condition.
Action ConditionId	The unique Id of the existing Action Condition record in the Oracle Fusion destination table.	Identify the Action Condition ID value by exporting the Action object. To export, navigate to Tools > Export Management > Create Export Activity.	Not required	A value is required if you're updating an existing Action Condition attribute and you're not providing the Action source system (original system)
Action Id	Specifies the foreign key that references the Action ID to which the action is assigned.	Identify the Action ID value by exporting the Action object. To export, navigate to Tools > Export Management > Create Export Activity.	Not required	A value is required, if you're updating an existing Action Id and you're not providing the Action Id source system code and reference Action OSR.
ActionStatus	Indicates the status to set an action if the condition is met.	Valid values provided by the lookup type ORA_SVC_AP_STATUS_CD.	Required	Not required
ActionNumber	Specifies the action original system reference, if the record was imported.	Identify the original system and system reference values from your source system which were imported when you imported the resource.	Required	A value is required only if you're not specifying the Action ID.

You can view the Action Condition 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 Action Condition 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 action condition 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 Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Action Condition 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.