Slow Performance when using Multi Value Link using intersection table as 1:m table with join
(Doc ID 2515312.1)
Last updated on NOVEMBER 12, 2019
Applies to:Siebel eService - Version 15.18 [IP2015] and later
Information in this document applies to any platform.
Slow performance in Business Component using custom Multi Value Link.
Behavior can be reproduced with the following steps
- Create child Business Component based on intersection table
- Use the foreign key (e.g. Contact Id) to join data from one of its child tables (e.g. S_CONTACT)
- Create link between parent and child Business Component referencing the foreign key in the intersection table
- Create Multi Value Link using Business Component based on intersection table as child
- Reference a Primary Id
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