Siebel Limitations
- Siebel Business Components fields with the same names but differing cases are handled by
leaving the first occurrence unchanged, while appending all subsequent occurrences with
_PB_
and an increasing numeral value.For example, fields like
DeDup Token
,Dedup Token
, andDEdup Token
in a Siebel business component are renamed toDeDup Token
,Dedup Token_PB_1
, andDEdup Token_PB_2
respectively. - If a field name contains a dot (.) in a Siebel schema, the dots are removed from the field name for use in Spectrumâ„¢ Technology Platform.
- While creating a physical model from a Siebel connection, links between any two Siebel Business
Components are displayed only if the link name matches the Business Component name in the
Siebel schema.
For example, in a Siebel schema, if a link is defined between the Business Components
Account
andContact
, while another Business ComponentContact Custom
uses the links ofCustom
, then in the physical model created for this Siebel connection, no link is displayed betweenAccount
andContact Custom
. Links are displayed only betweenAccount
andContact
, as the original link is between these two in the Siebel schema. - Fields of a Business Component which are marked as inactive in the Siebel schema are not displayed in physical model, logical model, and model store.