Siebel Developer's Reference > Business Component User Properties > Controlling Records >

Using Literals Instead of Bind Variables When Merging Records

The Use Literals For Merge: table_name user property creates a literal in an SQL statement for predicates that reside on a column that possesses low cardinality. It can contain one of the following values:

• TRUE. Use a literal value instead of a bind variable as criteria in an SQL statement where the predicate resides on a column that is a foreign key to table_name.
• FALSE or the user property does not exist. Use a bind variable instead of a literal value.

table_name identifies the name of a table. The current business component includes a field that is a foreign key column to this table.

For example, assume you add the following user property and set the value for it to TRUE:

Use Literals For Merge:S_BU

In this example, Siebel CRM uses literals instead of bind variables in SQL statements whose predicates reside on a column that is a foreign key to S_BU.

Siebel CRM uses a bind variable for all predicates when it merges records. In some situations, if the cardinality of the column is low, and if using an index is more efficient, then DB2 does table scans.

You add this user property to the business component where Siebel CRM merges records.

You can configure Siebel CRM to modify the value for this user property, create a new instance of it, or deactivate it.