Understand Joins to S_CON_ADDR and S_DEDUP_RESULT in Select Statement Generated when Querying Account Business Component
(Doc ID 3031072.1)
Last updated on JUNE 30, 2024
Applies to:
Siebel CRM - Version 23.2 and laterInformation in this document applies to any platform.
Goal
The Account business component is configured to have joins to S_CON_ADDR and S_DEDUP_RESULT.
There is no Force Active fields for these joins and those fields are not expose in applets. However, they are still included in the underlying query that should return 1 account record.
Why is the Account business component configured to add this unnecessary overhead. We are having to fetch 3,888 records when 1 record should be returned.
Solution
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
Goal |
Solution |
References |