Integration Platform Technologies: Siebel eBusiness Application Integration Volume ll > External Business Components >

Usage and Restrictions for External Business Components

The following usage guidelines and restrictions apply to external business components:

• Creating and populating the external table is the responsibility of the customer. Consult your database administrator for the appropriate method to use.
• External business components cannot be docked, so they do not apply to mobile users on the Siebel Mobile Web Client. Siebel Remote is not supported.
• External business components support many-to-many relationships with the limitation that for such relationships the intersection table needs to be from the same data source as the child business component.
• External business components cannot be loaded using Enterprise Integration Manager.
• Siebel Server components other than an Object Manager (for example Assignment Manager, Workflow Policies, Incentive Compensation, and so on) cannot utilize external business components.
• The Id field must be mapped to an underlying column in the external table in order to support insert, update, delete, and query operations.
• For external business components that contain multi-value groups, if a primary join is enabled, then both the parent and the child business components need to be from the same data source. Multi-value groups are also supported as long as such configuration does not require that a distributed join or a subquery be performed.
• Siebel visibility control (for example ViewMode) is not supported for external business components.
• An external join alias must have the same name as the name used for the external table.

NOTE:  Significant configuration effort and changes may be required if you choose to reconfigure a standard Siebel business component on an external table. For example, existing join and link definitions are unlikely to function, because the source fields and underlying columns may not exist in the external table.