TM Batch Assignment Transactions
(Doc ID 498584.1)
Last updated on NOVEMBER 22, 2019
Applies to:Siebel Territory Management - Version 7.8.2 SIA  and later
z*OBSOLETE: Microsoft Windows Server 2003
Version: 7.8.2  Life Sci
Database: Oracle 22.214.171.124
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP 9000 Series HP-UX
This document was previously published as Siebel SR 38-3114903291.
We have remote clients that are receiving accessive transactions. We found that the transactions mainly updates to the ASGN_DT column on the S_CONTACT AND S_ORG_EXT. These transactions are generated by a nightly assignement batch runs. These batch runs are running territory alignment rules. The batch parameter "Log txn only on change" is set to TRUE, however the transactions are still being generated.
Can you please provide some assistance to stop this behaviour. I have added txn_data.zip onto the ftp site, that contains the transactions for a few days. These have been made readable and show that a contact (1-EO-367 or 1-FO-131) can be found in multiple batch even on different days. I have also added log files for the assignment batch with the appropriate logging on the ftp site in the asgn_batch_logs folder.
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