Custom Territory Alignment attribute not showing up in Assignment Criteria after 'Run Alignment'
(Doc ID 516640.1)
Last updated on MARCH 01, 2018
Applies to:Siebel Territory Management - Version 8.0  to 22.214.171.124  [Release V8]
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0  Life Sci
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Microsoft Windows 2003 Server SP2
This document was previously published as Siebel SR 38-3394509881.
***Checked for relevance on 20-Nov-2011***
We've added a number of custom conditions to the Contact and Account objects for Territory Alignment. This has been done according to the following section:
Siebel Territory Management Guide > Setting Up and Running Territory Alignments >
Configuring Additional Attributes for Territory Conditions
Our configuration against these steps has been triple-checked, and is 100% configured as documented.
The new attributes show correctly in the Alignment Conditions view, and when we Run Alignment we get no errors.
However, there are no criterion created for these custom attributes. All vanilla attributes appear correctly in the Assignment Rules, but none of the custom ones. We are though, able to add the custom attributes as criterion by doing them manually in the Assignment - Admin view.
This suggests that there is something not correct in the 'background', as both the TM and AM screens work correctly in the UI, but the generation of Rules by TM does not.
It's not clear what logfiles can be generated - the Workflow Process Manager logs show no errors, even with event and SQL logging enabled. There's no errors returned in the UI and the Alignment Status gets set to Run Completed.
Please advise of any missed steps, or actions that can be taken to enable effective investigation.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|