My Oracle Support Banner

Contacts Activated By A Major Alignments Are Being Dropped By The Recurring Alignments. (Doc ID 1090939.1)

Last updated on JANUARY 30, 2022

Applies to:

Siebel Territory Management - Version 8.0.0.2 SIA [20412] and later
Information in this document applies to any platform.

Symptoms


Territory Manager is incorrectly dropping positions from contacts and accounts in production after recurring alignment runs of workflow process "Alignment - Periodic Runs", when there is an active Major first followed by an active Minor alignment. An example is the following:

There are 4 Territories in the HierarchyABC:

Territory A
Territory B
Territory C
Territory X

Division : DivisionABS

1. Create the Major Alignment:

Major Alignment

Type = Major
Coverage = National
Division = DivisionABS
Hierarchy = HierarchyABC

Geo Zones:

Geo Zone/Territory #/Territory Name/Assignment Object/Affiliation Object/Action

Brick A Territory A Territory A Account Contact Add
Brick B Territory B Territory B Account Contact Add
Brick C Territory C Territory C Account Contact Add

Positions:

Position/Territory #/Territory Name/Action

Position A Territory A Territory A Add
Position B Territory B Territory B Add
Position C Territory C Territory C Add

2. Run Alignment, inspect the result is correct, and Activate Rules to activate the alignment.

3. Create a Minor Alignment to drop Brick C from Territory C, to add Brick A to Territory C.

Minor Alignment

Type = Minor
Coverage = blank
Division = DivisionABS
Hierarchy = HierarchyABC

Geos Zones:

Geo Zone/Territory #/Territory Name/Assignment Object/Affiliation Object/Action

Brick C Territory C Territory C Account Contact Drop

Brick A Territory C Territory C Account Contact Add

Positions:

blank

4. Run Alignment, inspect the results, the result is correct, and Activate Rules to activate the alignment.

5. Create a dummy/recurring  alignment

Type = Minor (the same as the last active alignment's type)
Coverage = blank
Division = DivisionABS
Hierarchy = HierarchyABC
Status = In Progress

Activation Date: later than the last active alignment's Activation Date.

No need to define any rules.

6. Start a workflow process task with the following input parameters:

Workflow Process Name: Alignment - Periodic Runs
Object Id: <the dummy alignment's ROW_ID>

The result is incorrect, the Position B of Territory B aligned by the Major alignment is dropped from contacts and accounts, leaving contacts and accounts aligned with Position A of Territory A and Position C of Territory C.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.