Siebel Limitations

  1. 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, and DEdup Token in a Siebel business component are renamed to DeDup Token, Dedup Token_PB_1, and DEdup Token_PB_2 respectively.

  2. 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.
  3. 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 and Contact, while another Business Component Contact Custom uses the links of Custom, then in the physical model created for this Siebel connection, no link is displayed between Account and Contact Custom. Links are displayed only between Account and Contact, as the original link is between these two in the Siebel schema.

  4. 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.