Collections Territory Assignment By Customer Name Range Not Working With 'Contains' Operator
(Doc ID 3055316.1)
Last updated on OCTOBER 23, 2024
Applies to:
Oracle Territory Management - Version 12.2.13 and laterInformation in this document applies to any platform.
Symptoms
When a customer name range is specified in the Territory Management settings,
the system should automatically assign all customers within that name range.
However, the collections territory assignment is not working when using
'Customer Name Range' matching attribute and 'Contains' operator.
Steps To Reproduce
The issue can be reproduced at will with the following steps:
1. Login with Territory Management User responsibility.
2. Setup Territory Management for Collections.
3. Navigate to Update Territory: Add Matching Criteria page
Add Matching Attribute "Customer Name Range"
Condition: Contains, Value 1: ABCDE
Condition: Contains, Value 1: LMNOP
4. Run Territory Assignment
5. Result: Nothing updates. Customers are not assigned.
Cause
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
Symptoms |
Cause |
Solution |
References |