How do I import sales team member data?

You can use Import Management to create or update sales team member records.

You can import sales team member records using these steps:

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.
Create the source CSV file with the sales team member 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

You import sales team member 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 sales team member 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.
Ensure that you don't insert duplicate sales team member while importing, to avoid redundant data.

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. Also ensure that the parent records, such as accounts, are in active status.

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

Required Attributes and Validations for Sales Team Member 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 team member records, prerequisite setup tasks and specific validations, if any:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Sales Team Member record	Updating an Existing Sales Team Member record
TeamMemberId	Sales Team Member ID. This is the primary key.	N/A	N/A	If available, provide this to update other attributes.
SalesProfileID	Sales Profile ID	Active SalesProfileID to have been created already.	Conditionally required To be provided if none of the following are available: PartyID PartyNumber Combination of PartySourceSystem and PartySourceSystemReferenceValue	Conditionally required To be provided if TeamMemberID isn't available. To be provided along with ResourceID or ResourcePartyNumber or ResourceEmailAddress.
PartyID	Sales Account ID	N/A	Conditionally required To be provided if SalesProfileID isn't available.	Conditionally required To be provided if TeamMemberID or SalesProfileID isn't available. To be provided along with ResourceID or ResourcePartyNumber or ResourceEmailAddress.
PartySourceSystem	Party source system of the Sales account	N/A	Conditionally required To be provided if SalesProfileID isn't available. To be provided along with PartySourceSystemReferenceValue.	Conditionally required To be provided if TeamMemberID or SalesProfileID or PartyID isn't available. To be provided along with ResourceID or ResourcePartyNumber or ResourceEmailAddress.
PartySourceSystemReferenceValue	Party source system reference of the Sales account	N/A	Conditionally required To be provided if SalesProfileID isn't available. To be provided with PartySourceSystem.	Conditionally required To be provided if TeamMemberID or SalesProfileID or PartyID isn't available. To be provided along with ResourceID or ResourcePartyNumber or ResourceEmailAddress.
PartyNumber	Party number of the sales account/PUID	N/A	Conditionally required To be provided if SalesProfileID isn't available	Conditionally required To be provided if TeamMemberID or SalesProfileID or PartyID isn't available. To be provided along with ResourceID or ResourcePartyNumber or ResourceEmailAddress.
ResourceID	Resource identifier	Active ResourceID to have been created already.	Conditionally required To be provided if ResourcePartyNumber or ResourceEmailAddress isn't available.	Conditionally required To be provided if TeamMemberID isn't available. To be provided along with SalesProfileID or PartyID or PartyNumber or PartySourceSystem along with PartySourceSystemReference.
ResourcePartyNumber	Resource party number/PUID	N/A	Conditionally required To be provided if ResourceID isn't available.	Conditionally required To be provided if TeamMemberID or ResourceID isn't available. To be provided along with SalesProfileID or PartyID or PartyNumber or PartySourceSystem along with PartySourceSystemReference.
ResourceEmailAddress	Resource email address	N/A	Conditionally required To be provided if ResourceID isn't available	Conditionally required To be provided if TeamMemberID or ResourceID or ResourcePartyNumber isn't available. To be provided along with SalesProfileID or PartyID or PartyNumber or PartySourceSystem along with PartySourceSystemReference.

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

Go to Navigator > Tools > Import Management > Import Queue.
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 Sales Team Member 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 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.