The 'Primary Contact' Flag Does not Work When Using Resource Type of 'Group Resource' in the Territory Setup

(Doc ID 2290730.1)

Last updated on JULY 26, 2017

Applies to:

Oracle Territory Management - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

On : 12.1.3 version, Territory Assignment

The 'Primary Contact' flag is not working when using resource type as 'Group'. Is this the expected functionality?

As per Doc ID 789227.1, For a Territory, one specific employee resources can be pre-defined as the primary contact. This resource will then be allocated to a task. This allocation is controlled by the Primary Contact flag (Primary_contact_flag) on the Resources tab of the Territory Definition form.  When this flag is set (for one, and only one Employee Resource within a Territory), the primary resource will be assigned ownership of a Task. If
the Primary Contact flag is not set, then the application picks the resource from territory with the minimum terr_rsc_id, and makes the assignment. In the case of more than one qualifying territory being identified, the
territory:resource will be assigned based on the terr_id:terr_rsc_id.

So the issue is that the UI lets you select the Primary Contact Flag for a group even though that value won't be honored when territory management does the assignments.

Also, as per Note: What Defines The Order In Which Resources Are Picked From A Territory (Doc ID 789227.1)

This functionality works with resource types of 'Employee' - we would also like this for resource type 'Group' OR to remove the flag when Group resource is chosen so that it doesn't appear as though we can designate a  Primary Group as this is incredibly confusing and causes questions on assignments.


 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms