Import Your Product Data
You can use the Import Management functionality to create or update Product records.
To import Product 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 Product 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 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.
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
To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Applications Cloud.
The preferred options to uniquely identify an object record are as follows:
-
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 Product object, the attributes are OrganizationId and InventoryItemId.
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Product object, the attribute is ItemNumber.
Required Attributes and Validations for Product 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 Product records, required attributes for updating Product records, prerequisite setup tasks for the attributes, and specific validations, if any, for Product import:
Attribute |
Description |
Data Type |
Data Length |
Prerequisite Setup Task/ Import Validations |
Creating a Product Record |
Updating an Existing Product Record |
---|---|---|---|---|---|---|
OrganizationId |
A value that uniquely identifies the organization |
Long |
18 |
|
Don't specify a value. The value is auto populated. |
Not required |
Name |
Name of the product |
String |
240 |
No validation |
Required |
Required |
DefaultUOMCode |
The default unit of measure (UOM) code for the product |
String |
3 |
SCM setup to UOM, mandatory for creating products. This is a standard DCL field. |
Required |
Not required |
DefaultUOM |
The default unit of measure (UOM) for the product |
String |
25 |
Either the UOMCode or the UOM is mandatory. It is validated against the UOM DCL. |
Required only when the Default UOMCode isn't specified |
Not required |
ProductType |
Specifies the Sales Product Type |
String |
80 |
No validation |
Not required |
Not required |
EligibleToSell |
Indicates whether the item can be sold |
String |
80 |
No validation |
Not required |
Not required |
InventoryItemId |
A unique identifier for the inventory item |
Long |
18 |
No validation |
Don't specify a value. The value is auto populated. |
Required |
ItemNumber |
Unique system generated ID of the product |
String |
300 |
This has to be unique. If you don't specify a value, it will be auto generated. You can't update this value. |
Required A value is auto generated, if not specified. Ensure that you provide a unique value. |
Required |
ItemCatalogGroupId |
A unique value that provides metadata common to all items that share the category |
Long |
18 |
No validation |
Not required |
Optional |
Description |
Brief description of the product |
String |
4000 |
No validation |
Not required |
Optional |
ProductTypeCode |
Specifies the code of the product type |
String |
30 |
Select a value from the drop down list. |
Not required |
Optional |
SalesProductLookup |
The lookup type for the sales product type |
String |
80 |
No validation |
Not required |
Optional |
ModelConfigAttributes |
Model attributes |
String |
4000 |
No validation |
Not required |
Optional |
ModelName |
Name of the model |
String |
1000 |
No validation |
Not required |
Optional |
InventoryItemStatusCode |
Specifies the status code of the inventory item |
String |
10 |
Defaults to Active status |
Required The value is auto populated to Active. |
Optional |
EligibleToSellFlag |
Indicates whether the item can be sold |
String |
1 |
This can be either Y or N. |
Required The default value is Y. |
Optional |
EligibleForService |
Indicates whether the item is enabled for service |
String |
This can be Y only when the sales product type is either empty or has any of the following values:
|
Not required |
Optional |
|
AttachmentEntityName |
Name of the attachment entity |
String |
No validation |
Not required |
Optional |
|
CSSEnabled |
Enable Customer Self-Service |
String |
1 |
This can be either Y or N. |
Not required |
Optional |
You can view the Product 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 Product 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
To import data into Oracle Applications Cloud, you need to create an import activity and provide the CSV file as an input to the activity.
To create an import activity, do the following:
-
In the Navigator, under Tools, click Import Management.
-
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Product from the Object drop-down list.
-
In File Name, browse and upload the required .CSV file, and click Next.
-
In the Create Import Activity: Map Fields page edit the attribute mappings if required, and click Next.
Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues. -
In the Create Import Activity: Review and Submit page, click Submit.
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.