Import Your Sales Lead Data

Use this topic to import Sales Lead data into Oracle Applications Cloud. You can use the import functionality to create, update, or delete Sales Lead records.

To import Sales Lead records, perform the following tasks:

Map your source sales lead data to Oracle Applications Cloud object attributes.
Create source Comma Separated Values (CSV) file for import.
Create the import activity.
Review the import results.

Use the Contact time zone field to save the preferred time zone of a contact pursued on your sales lead. The contact time zone is based on the contact address and helps you know the preferred time to call or email a prospect or customer. You can also use the functional "who" columns to save the record history of a sales lead. The columns let you accurately report on sales leads that are imported from other systems.

Other sales lead management features help to align marketing and sales objectives from sales lead generation to sales lead execution. Sales Lead information is generated from a variety of sources and obtained from:

A company's existing contacts
Marketing campaigns

All sales leads then undergo the qualification and assessment process and are qualified either manually by a salesperson or automatically based on predefined rules. Finally, qualified sales leads are converted into opportunities.

How You Map Your Source Data to Target Object Attributes

To import your sales lead 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

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

Sales Lead Contact
Sales Lead Product
Sales Lead Resource

If you want to import only a few records, then you can create a single CSV file for all sales lead 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 sales lead child objects. Note that you must have imported the CSV file for sales lead 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

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 Sales Lead object, this attribute is LeadId.
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 Sales Lead object, the attribute is LeadNumber.

Required Attributes and Validations for Sales Lead 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 Sales Lead records, required attributes for updating Sales Lead records, prerequisite setup tasks for the attributes, and specific validations, if any, for Sales Lead import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Sales Lead record	Updating an Existing Sales Lead record
AcceptedDate	The date the recommended lead generated by the Sales Prediction engine was accepted by a sales person or lead qualifier to pursue	No validation	A value is required if you specify the value for LeadAcceptedFlag as Y.	Not required
ActionCode	Indicates explicitly the operation to be performed on a row: INSERT to create a new record in the destination tables, UPDATE to update an existing record in the destination table, DELETE to delete the record.	If no value is provided, the record is updated if it already exists. Else, it's inserted	Not required	Not required
ConvertedTm	The date when the lead was converted to an opportunity	No validation	A value is required if you specify the value for Lead StatusCd as CONVERTED.	Not required
LeadName	The name that identifies the lead	No validation	A value is required if you're creating a new lead.	Not required
LeadNumber	The Lead's public unique identifier value	If providing a value to update an existing lead, the value must exist in the column LEAD_NUMBER.of the MKL_LM_LEADS table.	If providing a value and creating a new lead, the value must be unique.	A value is required, if updating an existing lead and you're not providing the unique ID of the lead (ObjectKey)
ObjectKey	The unique ID for the existing lead record in the destination table	Automatically generated by the import process if creating new record. If updating an existing record and providing the LEAD_NUMBER, the import process defaults the LEAD_ID.	Do not provide a value if creating a new lead.	A value is required, if updating an existing lead and you're not providing the LeadNumber.
OwnerId	The unique ID for the existing resource party in the destination table. The owner must also be an internal resource included as a member of the lead's sales team	If providing a value, the value must exist in the column PARTY_ID of the HZ_PARTIES table, The value must also exist in the column PARTY_ID of the JTF_RS_RESOURCE_PROFILES table. The identified party must be assigned as a sales team resource for the existing lead or included in the resources imported in the same batch as this record.	A value is required, if creating a new lead and you don't provide the owner's source system code and reference (OwnerOrigSystem and OwnerOrigSystemReference)	Not required
QualifiedDate	The date when the lead was qualified	No validation	A value is required, if you optionally provide the lead status (StatusCd) value as QUALIFIED, indicating that the lead is qualified.	Not required
RejectedTm	The date when the lead was rejected	No validation	A value is required, if you optionally provide the lead registration status (ApprovalStatus) value as REJECTED, indicating that the lead is rejected.	Not required
RetiredTm	The date when the lead was retired	No validation	A value is required, if you optionally provide the lead status (StatusCd) value as RETIRED, indicating that the lead is retired.	Not required

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