Import Your Sales Lead Product Data

You can use the Import Management to create, update, or delete sales lead product records.

You can import sales lead product records using these steps:

Map your source sales lead product 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 sales lead product 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

To import your sales lead product data into Oracle Applications Cloud, you must populate a .csv file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

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

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

Required Attributes and Validations for Sales Lead 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 sales lead product records, prerequisite setup tasks and specific validations, if any:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Sales Lead Product record	Updating an Existing Sales Lead Product record
ItemId	The unique ID for the existing sales catalog product (item) record in the destination table	The value provided must match the value in the INVENTORY_ITEM_ID column of the EGP_SYSTEM_ITEMS_B table.	Conditionally required, when you don't provide the ProductName and ProductGroupId/ProductGroupName	Conditionally required, when you don't provide the ProductName and ProductGroupId/ProductGroupName
ItemNumber	The unique ID for the existing sales catalog product (item number) record in the destination table	The value provided must match the value in the ITEM_NUMBER column of the EGP_SYSTEM_ITEMS_B table.	Conditionally required, when you don't provide the ProductName and ProductGroupId/ProductGroupName	Conditionally required, when you don't provide the ProductName and ProductGroupId/ProductGroupName
LeadNumber	Leads Public Unique Identifier value	The value provided must match the value in the LEAD_NUMBER column of the MKL_LM_LEADS table.	Conditionally required, when you don't provide the LeadId	Conditionally required, when you don't provide the LeadId
PrimaryFlag	Indicates whether the product or product group is the primary product of interest for the lead	The value must be either Y or N.	Conditionally required, as at least one product or product group for a lead has this value set to Y	Conditionally required, as at least one product or product group for a lead has this value set to Y
ProductGroupInternalName	Internal name for the sales catalog product group	The value provided must match the value in the INTERNAL_NAME column of the QSC_PROD_GROUPS_B table.	Conditionally required, when you don't provide the ProductGroupId and ItemId/ProductName	Conditionally required, when you don't provide the ProductGroupId and ItemId/ProductName
ProductGroupId	The unique ID for the existing product group record in the destination table	The value provided must match the value in the PROD_GROUP_ID column of the QSC_PROD_GROUPS_B table.	Conditionally required, when you don't provide the ProductGroupName and ItemId/ProductName	Conditionally required, when you don't provide the ProductGroupName and ItemId/ProductName
ProductGroupName	The internal name for the sales catalog product group	The value provided must match the value in the INTERNAL_NAME column of the QSC_PROD_GROUPS_B table.	Conditionally required, when you don't provide ProductGroupId and ItemId/ProductName	Conditionally required, when you don't provide ProductGroupId and ItemId/ProductName
ProductName	The internal name for the sales catalog product	The value provided must be defined for the sales catalog specified for the QSC_SALES_PRODUCTS_INVENTORY_ORG_ID profile.	Conditionally required, when you don't provide the ItemId and ProductGroupId/ProductGroupName	Conditionally required, when you don't provide the ItemId and ProductGroupId/ProductGroupName

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

Go to Navigator > Tools > Import Management > Import Objects.
Select the Sales Lead Product 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 sales lead product 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 Enter Import Options page, provide a name for the import activity, and select Sales Lead Product 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.