Integration Platform Technologies: Siebel eBusiness Application Integration Volume ll > Integration Objects > About the Structure of Integration Objects >

About Inner Joins and Integration Components

When inner joins are used, records for which the inner joined field is not set are not returned in any query. By default the wizard inactivates such fields. If your business needs require these fields, you need to activate them.

NOTE:  If the inner join has a join specification that is based on a required field, then the wizard will not inactivate the fields that are using that particular join.

For example, assume that Account business component has an inner join to S_PROJ table, with Project Id field being the source field in the join specification, and the Project Name field being based on that join.

If an integration component, with an active Project Name field is mapped to the Account business component, then when this integration component is queried only accounts with Project Id field populated will be considered.

Because Project Id is not a required field in Account business component, not every account in Siebel Database is associated with a project. So, having Project Name active in the integration component would limit the scope of the integration component to only accounts associated with a project. This typically is not desirable, so the wizard inactivates the Project Name field in this example.

If the business requirement is to include the Project Name field, but not to limit the integration component's scope to only accounts with project, then you can change the join to S_PROJ in the Account business component to an outer join. For details on joins, see Using Siebel Tools.

NOTE:  Activating an inner join may cause a query on that integration component to not find existing rows.