Error adding new TM Condition- Account Organisation (Doc ID 501587.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Territory Management - Version 7.8.2.3 SIA [19221] and later
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0.0.1 [20408] Life Sci
Database: Oracle 10.2.0.3
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Microsoft Windows 2003 Server SP2

***Checked for relevance on 22-Feb-2012***

This document was previously published as Siebel SR 38-3508211823.


Symptoms


Customer wanted to add Account Organization as a new condition to Territory Manager. They followed the exact config setup in the bookshelf but could not get it to work. The custom attribute is based on the Account Business Component, Primary Organization field. The steps to customizing the attribute is documented in the Siebel Bookshelf as follows :

Siebel Territory Management Guide > Setting Up and Running Territory Alignments >
Configuring Additional Attributes for Territory Conditions

The workflow process manager aborted while running an alignment with the custom attribute under the Alignment Condition.

When I run the alignment the workflow processes that get created by the TM process fail with the error:

SBL-SRB-00061: Process WfProcMgr on Siebel Server terminated

and the alignment gets to the status of "Identifying Affected Objects" but doesn't go any further.

Customer checked his config against bookshelf and it looks to be correct.  After making their changes, customer's TM conditions that previously worked (for example the Vanilla Account Status) fail also with the same error.

Cause

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