Import Your Action Plan Action Relation Data
You can use Import Management to create or update Action Plan Action Relation records.
To import Action Plan Action Relation 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 Action Plan Action Relation 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 action plan action relations or are updating action plan action relations that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Action Plan Action Relation 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 Action Plan Action Relation records, required attributes for updating Action Plan Action Relation records, prerequisite setup tasks for the attributes, and specific validations, if any, for Action Plan Action Relation import:
Attribute |
Description |
Prerequisite Setup Task/ Import Validations |
Creating a Action Plan Action Relation Record |
Updating an Existing Action Plan Action Relation Record |
---|---|---|---|---|
DeletedFlag |
Contains the values, Yes or No. If Yes is used, then the dependency record is deleted. If No is used, then the then the dependency record isn't deleted. |
A valid value from the YES_NO lookup. |
Optional |
Optional |
RelationId |
The relation identifier between actions in an action plan. |
A valid primary key for the action plan action relation record in the destination system is required. |
Not Required |
Required |
DepActionPlanActionNumber |
The relation identifier between action plan action rows for an action plan. |
A valid action plan action PUID in the destination system is required. The combination of ActionPlanActionNumber and DepActionPlanActionNumber should be unique for a Action Plan. |
Optional A Null value is accepted. |
Optional A Null value is accepted. |
DepActionPlanActionId |
The dependent action identifier of an action plan. |
A valid primary key for the action plan action record in the destination system is required. Either the DepActionPlanActionId or the DepActionPlanActionNumber is required. If both are present, then the DepActionPlanActionId is preferred. |
Optional A Null value is accepted. Either DepActionPlanActionNumber or DepActionPlanActionId is required to locate a ActionPlanAction row. |
Optional A Null value is accepted. |
ActionPlanActionId |
The action identifier of the action plan. |
A valid primary key for the action plan action record in the destination system is required. Either the ActionPlanActionNumber or the ActionPlanActionId is required. If both are present, then the ActionPlanActionId is preferred. |
Optional Either ActionPlanActionNumber or ActionPlanActionId is required to locate a Action Plan Action row. |
Optional |
ActionPlanActionNumber |
The reference number of the action plan action object. |
A valid action plan action PUID in the destination system. |
Required |
Optional |
You can view the Action Plan Action Relation 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 Action Plan Action Relation 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 Action Plan Action Relation 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.