My Oracle Support Banner

Implicit Joins (Doc ID 475503.1)

Last updated on DECEMBER 10, 2018

Applies to:

Siebel Tools - Version 8.0 [20405] and later
Information in this document applies to any platform.
Area(s):Configuration - General
Release(s): V7 (Enterprise), V8 (Enterprise)
Database(s):Other
Latest release tested against:V7 (Enterprise), V8 (Enterprise)
Keywords:Implicit, join

This document was previously published as Siebel Technical Note 63.

Checked for Relevance on 10-December-2018

Purpose

Usually, if a business component contains fields that come from a different database table than the primary table of the business component itself, a join is used to include the other tables into the business component. This technical note describes two exceptions to this rule: Extension Tables and Intersection Tables. In both of these cases, the join is implied and should not be specified explicitly.

Scope

This document is informational and intended for any user.

Details

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
Purpose
Scope
Details
 Two Exceptions

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.