Import Your Action Data

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

You can import action records using these steps:

  1. 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.

  2. Create the source CSV file with the action data you want to import.

  3. Kick off an import activity.

  4. Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

You import action 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.

To better manage your action information, the action object has the following child objects:

  • Action Attribute

  • Action Condition

If you want to import only a few records, then you can create a single CSV file for all action attributes. 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:

  • 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 actions or are updating actions that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Action Object

To import data successfully into Oracle Applications Cloud, your .csv file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.

This table lists the required attributes for action records, prerequisite setup tasks and specific validations, if any:

Attribute

Description

Prerequisite Setup Task/ Import Validations

Creating an Action record

Updating an Existing Action record

Action

The name of the action that's associated associated with an action plan template or action plan instance.

None

Required

Not required

Action Id

The unique Id of the existing Action record in the Oracle Fusion destination table.

Identify the Action ID value by exporting the Action object. To export, navigate to Tools > Export Management > Create Export Activity.

Required

A value is required if you're updating an existing Action and you're not providing the Action Number. The Action ID is autogenerated in Oracle Fusion applications, if you don't specify a value.

ActionNumber

The unique ID for the existing Action record in the Oracle Fusion destination table.

None

Optional

A value is required if you're updating an existing Action and you're not providing the Action Id.

Parent Entity Name

The entity name of the object for which the action can be used in an action plan.

None

If providing a value, it must be ServiceRequest.

Conditionally required

A value is required only when you're inserting a parent entity name. However, a value isn't required when you delete or update an existing parent entity name.

Conditionally required

A value is required only when you're inserting a parent entity name. However, a value isn't required when you delete or update an existing parent entity name.

Duration

The estimated time to complete the action.

None

Required

Required

Duration Unit

The unit of measurement for lead time.

None

If you intend to specify a value, select a value from the list of valid values in the lookup type ORA_SVC_AP_LEAD_TIME_UNIT.

Required

Required

Object Entity Name

Entity name of the object on which the action is based.

None

Conditionally required

A value is required only when you're inserting an object entity name. However, a value isn't required when you delete or update an existing object entity name.

Conditionally required

A value is required only when you're inserting an object entity name. However, a value isn't required when you delete or update an existing object entity name.

Original System Reference

Specifies the original system reference if this record was imported.

Identify the original system and system reference values from your source system that were imported when you imported the resource.

Optional

Optional

Object Entity Type

The entity type of the object on which the action is based.

The valid values are ServiceRequest, Task, and Appointment.

Required

Not required

A value is required only when you're inserting an object entity type. However, a value isn't required when you delete or update an existing object entity type.

Visibility

Indicates the visibility level of the action.

If you intend to specify a value, select a value from the list of valid values in the lookup type ORA_SVC_AP_VISIBILITY_CD.

Required

Not required

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

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Action 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 information. To create an import activity:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. On the Manage Imports page, click Create Import Action.

  3. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Action from the Object drop-down list.

  4. Select the CSV file in the File Name field, and click Next.

  5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

    Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues.
  6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

  7. 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:

  1. Go to Navigator > Tools > Import Management > Import Queue.

  2. Click All Imports and search for the import activity that you created earlier.

  3. 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.