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

Determining Functional Fit for Reusing a Predefined Object

This task is a step in Process of Determining If You Can Reuse a Predefined Object.

To determine functional fit for reusing a predefined object

1. Determine if you must reuse the object rather than copy the object.

   For more information, see Reasons to Reuse or Not Reuse a Predefined Object.

2. Determine if you must copy the object rather than reuse the object.

   For more information, see Guidelines for Reusing a Predefined Object.

3. Make sure the original nature and purpose of the Siebel object is compatible with your proposed use.

   For example, storing customer complaints is compatible with the Service Request business component, but not for storing financial transactions.

4. Make sure relationships to other objects are compatible with your requirements.

   However, the fact that an object contains the correct relationships is not sufficient for reuse. For example, you must not use the S_EVT_ACT table as an intersection table only because it contains two of the foreign keys that you require. Doing so can cause the table to overload and result in degraded performance.

5. Determine if the visibility properties of the object are or are not compatible with your requirements.

If the object is not a good functional fit, then reusing the object for that purpose might be inappropriate. The following are examples of improper use:

• Using the S_PARTY table to store a nonparty entity.
• Using an unused table for a custom business component where the table does not possess a relationship to the intended usage of the business component.
• Using an unused table column or business component field that does not possess a relationship to the intended usage of the field.