Import Your Sales Territory Coverage Data
You can use Import Management to create or delete Sales Territory Coverage records.
To import Sales Territory Coverage 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 Object Attributes
To import your Sales Territory Coverage 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.
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 the appropriate user-friendly public
unique identifiers (attributes denoted with 'Number' and usually visible
in the business object's UI). For the Sales Territory Coverage object,
the attributes are UniqueTerritoryNumber, CoverageTypeCode and DimensionCode.
If you delete a sales territory resource record, you can use a combination
of the UniqueTerritoryNumber and CoverageNumber attributes to identify
the record. Oracle recommends that you don't update the Sales Territory
Coverage object. For example, to update the AddressCity of the Addr
(DimensionCode) coverage record, delete
the record and create a new record with the correct AddressCity value.
Required Attributes and Validations for Sales Territory Coverage 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 Coverage records, required attributes for deleting Sales Territory Coverage records, prerequisite setup tasks for the attributes, and specific validations, if any, for Sales Territory Coverage import:
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
UniqueTerritoryNumber |
The public unique identifier number of the territory |
Text |
Not applicable |
Required |
CoverageNumber |
The public unique identifier number of the territory coverage |
Text |
Not applicable |
Don't provide a value. |
CoverageTypeCode |
The code of the territory coverage type |
Text |
Not applicable |
Required Values are REGULAR, INCLUSION, and EXCLUSION |
TerrDimensionCode |
The code of the dimension |
Text |
Not applicable |
Required if passing the related dimension member information. The values are:
don't provide a value, if creating a dimensional coverage of Any (for every dimension including Address) |
Depending on the dimension coverage there may be additional required attributes for importing new Sales Territory Coverage records. The following tables list the required attributes for importing new Sales Territory Coverage records, prerequisite setup tasks for the attributes, and specific validations, if any, for Sales Territory Coverage import:
If the DimensionCode = Acct
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
RegistryId |
The public unique identifier number of the account |
Text |
Not applicable |
Either the RegistryID or the OriginalReference is Required. |
OriginalReference |
The original system / original system reference of the account. |
Text |
Not applicable |
Either the RegistryID or the OriginalReference is Required. |
CoverageTypeCode |
The code of the territory coverage type |
Text |
Not applicable |
Required Values are REGULAR, INCLUSION, and EXCLUSION |
IncludeHierarchyFlag |
An indicator of whether the account hierarchy is included |
Text |
Not applicable |
Optional. Applicable values Y or N. |
If the DimensionCode = Geo
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
GeographyName |
The geography name including the hierarchy |
Text |
Not applicable |
Required |
GeographyHighName |
The upper level of the geography name range including the hierarchy |
Text |
Not applicable |
Required only if defining a range of geography dimension members |
If the DimensionCode = Addr
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
AddressCountry |
The code of the address country |
Text |
Not applicable |
Required |
AddressState |
The address state |
Text |
Not applicable |
Optional |
AddressProvince |
The address province |
Text |
Not applicable |
Optional |
AddressCounty |
The address county |
Text |
Not applicable |
Optional |
AddressCity |
The address city |
Text |
Not applicable |
Optional |
AddressPostalCode |
The address postal code |
Text |
Not applicable |
Optional |
AddressElementAttribute1 |
The additional address element 1 |
Text |
Not applicable |
Optional |
AddressElementAttribute2 |
The additional address element 2 |
Text |
Not applicable |
Optional |
AddressElementAttribute3 |
The additional address element 3 |
Text |
Not applicable |
Optional |
AddressElementAttribute4 |
The additional address element 4 |
Text |
Not applicable |
Optional |
AddressElementAttribute5 |
The additional address element 5 |
Text |
Not applicable |
Optional |
If the DimensionCode = OrgTp
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
OrganizationTypeCode |
The code of the organization type |
Text |
Not applicable |
Required |
If the DimensionCode = Indst
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
IndustryCode |
The code of the industry |
Text |
Not applicable |
Required |
If the DimensionCode = Csize
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
CustomerSizeCode |
The code of the customer size |
Text |
Not applicable |
Required |
If the DimensionCode = AcTyp
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
AccountTypeCode |
The named account code |
Text |
Not applicable |
Required |
If the DimensionCode = Prod
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
ProductGroupNumber |
The public unique identifier number of the product group |
Text |
Not applicable |
Required if creating a sales territory coverage for a product group |
ItemNumber |
The public unique identifier number of the item |
Text |
Not applicable |
Required if creating a sales territory coverage for an item |
InventoryOrgId |
The identifier of the inventory organization |
Number |
Not applicable |
Required if creating a sales territory coverage for an item, but only when the value is different from the default inventory organization identifier specified in the profile option QSC_SALES_PRODUCTS_INVENTORY_ORG_ID. |
If the DimensionCode = BUnit
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
BusinessUnitName |
The name of the business unit |
Text |
Not applicable |
Required |
If the DimensionCode = Aux1
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
Auxiliary1Code |
The code of the auxiliary classification 1 |
Text |
Not applicable |
Required |
If the DimensionCode = Aux2
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
Auxiliary2Code |
The code of the auxiliary classification 2 |
Text |
Not applicable |
Required |
If the DimensionCode = Aux3
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
Auxiliary3Code |
The code of the auxiliary classification 3 |
Text |
Not applicable |
Required |
If the DimensionCode = Schnl
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
SalesChannelCode |
The code of the sales channel |
Text |
Not applicable |
Required |
SubSalesChannelCode |
The code of the sub sales channel |
Text |
Not applicable |
Optional |
If the DimensionCode = Prtnr
Attribute |
Description |
Data Type |
Prerequisite Setup Task/ Import Validations |
Creating a Sales Territory Coverage Record |
---|---|---|---|---|
PartnerNumber |
The public unique identifier number (or company number) of the partner |
Text |
Not applicable |
Required |
You can view the Sales Territory Coverage 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.
Required Attributes and Validations for Deleting Sales Territory Coverage Object
You can delete a sales territory coverage record using Unique Territory Number, Dimension Code and other attributes or Unique Territory Number and Coverage Number.
Delete a Sales Territory Coverage using Attribute and Dimension Code
- Unique territory number (UniqueTerritoryNumber): The public unique identifier number of the territory
- Coverage type code (CoverageTypeCode): The coverage type code. Possible values are REGULAR, INCLUSION, or EXCLUSION
- Dimension code (TerrDimensionCode) : The possible values are listed in the table below:
Dimension | Dimension Code | Dimension Field |
---|---|---|
Sales Channel | Either SalesChannelCode or SubSalesChannelCode | |
Product | Prod | ProductGroupNumber or ProductGroupId OR ItemNumber or InventoryItemId |
Account Type | AccTp | AccountTypeCode |
Address | Addr | AddressCountry and (optionally) one or more of the following:
|
Auxiliary 3 | Aux3 | Auiliary3Code |
Auxiliary 1 | Aux1 | Auiliary1Code |
Auxiliary 2 | Aux2 | Auiliary2Code |
Business Unit | BUnit | BusinessUnitName or BusinessUnitId |
Customer Size | CSize | CustomerSizeCode |
Geography | Geo |
GeographyId or GeographyName (the full path needs to be provided e.g. >United States>CA or ~Global~North America) For Geo ranges, also provide GeographyHighId or GeoHighName - the full path needs to be provided (optional) |
Industry | Indst | IndustryCode |
Organization Size | OrgTp | OrganizationTypeCode |
Partner | Prtnr | PartnerNumber or PartnerId |
Account | Acct | RegistryId or OriginalReference or AccountId |
Delete a Sales Territory Coverage using Unique Territory Number and Coverage Number
A Sales Territory Coverage record can be deleted using the Unique Territory Number and Coverage Number.
Attribute | Description | Data Type | Prerequisite Setup Task/ Import Validations | Deleting an Existing Sales Territory Coverage Record |
---|---|---|---|---|
UniqueTerritoryNumber | The public unique identifier number of the territory. | Text | Not applicable | Required |
CoverageNumber | The public unique identifier number of the territory coverage. | Text | Not applicable | Required |
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 Standard Text 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
After you have the CSV file ready, create an import activity to import the information. To create an import activity:
-
Go to
. -
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 Coverage from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.
-
Under Advanced options, select the Import Mode as Create records or Delete Records.
-
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
. -
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.