Territory Assignment Issue For File Imported Account Records
(Doc ID 2121973.1)
Last updated on DECEMBER 22, 2020
Applies to:Oracle Fusion Sales Cloud Service - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Accounts, Contacts, Households
Territory assignment issue for file imported Account records
We have created a Territory based on Geography, Product and Sales Channel. And when we created an account manually, it was getting assigned to territory properly. But, when we imported some account records via file import, Territory assignment is not happening properly.
Note: We found that, while manually passing account address fields,once you give the Pin code, the related fields (like state, city, zone etc.) are getting auto populated. But, while importing account,even though Pin code field is being passed, the related fields are not getting auto populated.
Territory should have been assigned after running the file import job.
The issue can be reproduced at will with the following steps:
1. Prepare a CSV file.
2. Run a file import job.
3. Validate the address in the UI -> Territory should have been assigned based on the address but it didn't. Account got assigned to the top most territory "Global"
4. Run manual assignment from Actions-> Run Assignment -> Territory assignment still the same.
5. Go to Account Profile-> Change the address to XYZ address and change it back to the same address used in the import.
6. Save the record and then actions -> Run Assignment -> Territory is assigned correctly to the account based on the address.
The issue has the following business impact:
Due to this issue accounts created using file import are not getting assigned correctly to the correct territory.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document