Implicit Joins

June 14, 2007 at 9:17 am

In a many-to-many relationship, it’s possible in the child business component to retrieve and set data on the current intersection record through an implicit join to the intersection table. In Siebel 7 you can see an example of this in action in the Opportunity: Contacts view: the Contact has a ‘Role’ on the Opportunity and this is displayed in the list of Contacts. Examining the config in Tools, this role actually sits on the intersection record between the Opportunity and Contact, yet there’s no S_OPTY_CON join defined for Contact. Unlike most joined fields, the UI also allows the Role field to be edited, automatically saving data back to the intersection. The joys of implicit joins.

This behaviour is supported everywhere there’s a many-to-many parent-child relationship. When defining a new field, the Join property is bound to the list of joins defined for the business component. So the trick is to create a basic join to the intersection table – no need to specify a join spec or any details – then you can define your new fields and, when you’re done, delete the join. Siebel will recognise it as an implicit join and pick up data from the intersection record used to retrieve the child.

Advertisements

Entry filed under: Configuration, Siebel.

URL Controls More Siebel Web Resources


Feeds


%d bloggers like this: