Territory Assignment Behavior
If the setting SET049 (Module: OptiMax > Submodule: Dispatch Calculations) is set to True and a set of territory match rules are defined in the org, the following might be the expected behavior.
Consider the following data setup for example.
Territory Match rule criteria: Priority= High
|
Scenario
|
Territory Assignment Behavior
|
||
|---|---|---|---|
|
Territory coverage is not defined in the territory level.
|
In this scenario, if the user manually provides the primary territory in the work order with Priority = High when creating the work order, the Primary Territory value provided will be retained after the work order creation given by the user in the Primary Territory field of the work order. Also, the Dispatch Process will not be stamped in the work order.
The OptiMax Error Text field will be populated as follows:
“Primary territory for this work order could not be calculated. This could be because either no territory matching rules were defined, this work order did not match any territory match rules, or a matching territory rule did not yield any territories for this work order.”
|
||
|
Territory coverage is not defined in the Territory level.
|
In this scenario, if the user manually provides the Primary Territory in the work order with Priority = Low when creating the work order, the Primary Territory value will not be retained after the work order creation given by the user in the Primary Territory field of the work order. Also, the Dispatch Process will not be stamped in the work order.
The OptiMax Error Text field will be populated as follows:
“This work order does not match the entry criteria for any dispatch process or the matching dispatch process is deactivated.”
|
||
|
|||
