Import Your Asset Resource Data

You can use Import Management to create, update, or delete your Asset Resource data.

To import asset resource records, perform the following tasks:

  1. Map your source data to Oracle Applications Cloud object attributes.

  2. Create source Comma Separated Values (.csv) file for import.

  3. Create the import activity.

  4. Review the import activity.

How You Map Your Source Data to Target Object Attributes

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

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

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

  • Address

  • Classification

  • Relationship

  • Sales Team Member

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

Required Attributes and Validations for the Asset Resource 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 Asset Resource records, prerequisite setup tasks and specific validations, if any:

Attribute

Description

Prerequisite Setup Task/ Import Validations

Creating an Asset Resource record

Updating an Existing Asset Resource record

AssetId

The unique ID for the existing asset record in the destination table.

An asset record with the Asset ID should exist

Conditionally required when you don't provide the Asset Number

Conditionally required when you don't provide the Asset Number

AssetNumber

The unique ID for the existing asset record in the destination table.

An asset record with the Asset Number should exist

Conditionally required when you don't provide the Asset ID

Conditionally required when you don't provide the Asset ID

Resource Party ID

Unique party identifier representing a resource

The party must exist.

Required

Required

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the Asset Resource 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 Asset Resource 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 Asset Resource information. To create an import activity:

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

  2. Click Create Import Activity in the Manage Imports page.

  3. In the Enter Import Options page, provide a name for the import activity, and select Asset Resource 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.

  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.