Configuring Siebel Business Applications > Reusing Predefined Objects > Process of Determining If You Can Reuse a Predefined Object >

Determining If You Can Reuse a Predefined Business Component

Where possible, it is recommended that you reuse a business component in the predefined repository. However, you must only reuse a business component that provides a valid functional and technical fit with your requirements. If no suitable predefined business component exists, then it might be necessary to create a new one. It might also be necessary to customize the database to create a new table.

To determine if you can reuse a predefined business component

1. Make sure the business component does not use a specialized class.

   Instead of using a specialized business component, create a new business component. If you use a business component that references a specialized class for a purpose other than for which it is intended, then the class code might generate problems that are difficult to debug. For example, if you use the eEvents Parent Event business component to store data that is not related to events management, then the specialized code might result in the creation of an undesirable subevent. For more information, see Guidelines for Creating a Business Component That References a Specialized Class.

2. Make sure the business component does not reference the S_PARTY table.

   Never use a business component that references the S_PARTY table for a purpose other than which the business component is intended. A business component that references the S_PARTY table influences other areas, such as access control and Remote visibility.

3. Make sure the business component is licensed.

   You cannot use a predefined business component that is not licensed for your configuration.

4. Make sure the business component is not a repository business component.

   Never customize a repository business component. The name of a repository business component begins with Repository.