Siebel Configuration Best Practices : Part 2

Siebel Configuration Best Practices. 

The following are Siebel configuration best practices that you need to follow when creating or modifying calculated fields on Business Components.

1. Be very careful and try to avoid setting Force Active = TRUE or Link Specification = TRUE as because this will result in the calculated field always being evaluated whenever the BC is instantiated. As such, this will in turn results in any dependent fields being evaluated hence causing additional database calls resulting in performance issues.
2. Try to avoid using InvokeServiceMethod in Siebel calculated fields. More so in situations, avoid setting Force Active = TRUE or Link Specification = TRUE for InvokeServiceMethod calculated fields. When the calculated field is active, it will make a BS call, the business service will be repeatedly called for each record in the current instance context. This in turn will becomes exponentially worse if there are one or more queries within the business service as additional db calls are made each time the business service is invoked. This may result in significant issue in performance.
3. If there is a requirement that InvokeServiceMethod must be used in calculated fields then try to assess whether the business service can be cached (In Siebel Tools > Business Service, set Cache = Y), this way the business service will not have to be repeatedly instantiated, thereby performance is not impacted.
4. Try to void using calculated fields with database functions like SUM and COUNT. Using the SUM and COUNT functions in calculated fields will result in an additional query generated for each record in the current instance resulting in performance degradation. Avoid setting Force Active = TRUE or Link Specification = TRUE for these aggregate function calculated fields as the additional query will be generated for every record whenever the BC is instantiated and queried. If you are using the COUNT or SUM function to determine if child BC records exist for a particular parent record then use the EXISTS function instead, EXISTS will result in much better performance. 
5. Avoid using calculated fields in search specifications or search expressions. This may result in Siebel firstly querying on the search specification/expression without the calculated field first and then again filter against this result set in memory against the calculated field. This may give rise to potential performance problems in the Siebel application.

Related Posts