Siebel Remote: Time Filtering does not apply for Dock Object 'Party'
Last updated on JULY 11, 2017
Applies to:Siebel CRM - Version 184.108.40.206 [IP2014] and later
Information in this document applies to any platform.
Siebel Remote / Replication / Anywhere - on version: 220.127.116.11.6 [IP2014]
On a Development environment, a copy of Production DB was used. When trying to extract the Local Databases for developers, this fails due to huge amount of data extracted.
As a next step, Time Filters were applied on some of the Dock Objects that were responsible for bringing into Local DBFs too much data - this helped reducing the Local DBF size.
Based on suggestions from <Document 735454.1>, the goal would be to have the DBF under 1 GB.
But it was found that still a lot of Party records were extracted - so a time filter was added for this Dock Object as well.
But after performing again a re-extract and restart of Transaction Router (TxnRoute) comp, the amount of data for Party was not decreasing.
Time filters were expected to work to reduce the amount of data extracted - as this worked for other Dock Object / data entities extracted.
The issue can be reproduced at will with the following steps:
1. Define a new Time Filter on Dock Object 'Party' and set a Cutoff date in the past for that
2. Re-extract the developer's database and restart TxnRoute comp
3. Check and compare the amount of records extracted for Party Dock Object.
The issue has the following business impact:
Due to this issue, users cannot initialize a Local DBF with manageable size
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