Configuring Siebel eBusiness Applications > Creating and Administering Lists of Values >

MLOV Configuration and Coding Guidelines

The following guidelines should be followed when MLOVs are enabled in your environment.

• LookupName and LookUpValue functions. These functions can only be used in calculated fields or search specification expressions. They cannot be used with Siebel scripting.
• Pre/Post default values for fields with LOV picklists. Always use the LookupValue function with Expr: in front of it. The first argument is the LOV Type and the second is the LIC. The function returns the language-specific Display Value. For example:

  Expr: "LookupValue (""FS_PROD_ALLOC_RULES"", ""Default"")"

• Dynamic drilldowns and toggle applets. These are usually based on a field that has an LOV value. For example, a dynamic drilldown might navigate the user to a Credit Card screen if the account type is equal to Credit Card or to a Savings screen if the account type is equal to Savings. Do not hard-code the drilldown or toggle conditions. Rather, use the LookupValue function (as described in the previous bullet).
• Search specs for business components, links, applets, and picklists. Always use the LookupValue function. For example:

  [Invoice Code] = LookupValue('FS_INVOICE_CODE', 'Auction')

• VB functionality. VB does not offer a function to retrieve the language-specific Display Value. However, the Display Value must never be hard-coded; you should use the language-independent code instead. To write VB code using the language-independent code only, you must create calculated fields that hold the language-specific translation for a language-independent code.
• Language and ResourceLanguage parameters. Set these parameters only in the configuration file, for example, Language =<lang>, ResourceLanguage = ENU. If you do not set these parameters only in the configuration file, for example, when /L=<language>and ResourceLanguage = ENU, you will intermittently receive error 2009.