Import Your Sales Territory Data

How You Map Your Source Data to Object Attributes

To import your Sales Territory 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 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 setups are done, if applicable.
Understand your options for uniquely identifying the records.
Ensure parent records exist before importing child records.
- When creating a territory, the sales territory import file must be imported before importing the sales territory resource, sales territory coverage, or sales territory line of business import files.
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.
You have created a proposal in the Classic Territories pages, if you want to update territories as part of a proposal. Optionally, you can add territories to update the proposal.

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 option to uniquely identify an object record is through the Public unique identifier. 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 Territory object, the attributes are UniqueTerritoryNumber, ProposalNumber and OwnerResourceNumber.

Required Attributes and Validations for the Sales Territory 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. The following table lists the required attributes for importing new Sales Territory records, required attributes for updating Sales Territory records, required attributes for deleting Sales Territory records, prerequisite setup tasks for the attributes, and specific validations, if any, for Sales Territory import:

Attribute	Description	Data Type	Prerequisite Setup Task/ Import Validations	Creating a Sales Territory Record	Updating a Sales Territory Record	Deleting an Existing Sales Territory Record
UniqueTerritoryNumber	The public unique identifier number of the territory	Text	Not applicable	Optional	Required	Required
ProposalNumber	The public unique identifier number of the proposal	Text	Not applicable	A value is required if you're creating a territory that's part of a proposal.	Not required	Not required
ParentTerritoryUniqueTerritoryNumber	The public unique identifier number of the parent territory	Text	Not applicable	A value is required unless you're creating a top level territory.	A value is required if you're moving a territory under a different parent.	Don't provide a value.
TypeCode	The type of the territory such as PRIME or OVERLAY	Text	Not applicable	Required	Conditionally required if you need to update the territory type	Don't provide a value.
CoverageModel	Coverage Model	Text	Not applicable	Required. The available values are SALES_ACCOUNT_CENTRIC or PARTNER_CENTRIC	Don't provide a value.	Don't provide a value.
StatusCode	The status of the territory, such as FINALIZED.	Text	Not applicable	A value is required if you're creating an active territory. The value is FINALIZED.	Don't provide a value.	Don't provide a value.
TerritoryName	The name that identifies the territory.	Text	Not applicable	Required	Optional	Don't provide a value.
Owner	The name of the owner resource	Text	Not applicable	Don't provide a value.	Don't provide a value.	Don't provide a value.
OwnerResourceNumber	The public unique identifier number of the owner resource	Text	Not applicable	Required	Conditionally required if you need to update the owner	Don't provide a value.

You can view the Sales Territory object 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 Navigator > Tools > Import Management > Import Objects.
Select the Sales Territory 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 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 Territory 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.
- The ParentUniqueTerritoryNumber isn't automatically mapped to the Parent Unique Territory Number. Use the Save As option to create a mapping, name the mapping, and map the Parent Unique Territory Number target attribute to the Source File ParentUniqueTerritoryNumber Attribute, by dragging the target attribute to the Attribute Display Name. Select and apply this new import mapping in the Map Fields page of a future sales territory import activity.
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.