|Bookshelf Home | Contents | Index | PDF|
To increase performance when there are many records and multiple languages, you can use [Fieldname.TransCode] in the business component search specification. This function retrieves the (untranslated) language-independent code (LIC) from a column in the base table, rather than returning the display value in the current language.
For example, in the Service Request business component, the Status field maps to the SR_STAT_ID column. This column stores the LIC value "Open," but when MLOVs are configured, a query on the Status field always brings back the display value for "Open" in the current language (as set with the Language Parameter), such as "Offen" if the language is DEU.
which on a DEU object manager would add a join to S_LST_OF_VAL in the resulting SQL to find the DEU display value for the LIC value "Open" and compare that to the LIC in column SR_STAT_ID. This makes the query complex and not easily index supportable.
Therefore, using [Fieldname.TransCode] improves the performance for queries on MLOV-enabled columns, particularly if the query or search spec includes other columns from the same base table, because a combined index including the MLOV column can now be used. This typically is not the case when using LookupValue() or querying directly on MLOVs.
Alternatively, you can use the [
|Siebel Developer's Reference||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|