My Oracle Support Banner

Support of Hierarchical Multilingual List of Values (Doc ID 473813.1)

Last updated on AUGUST 10, 2020

Applies to:

Siebel Tools - Version 7.5.3 [16131] to SIA [23021] [Release V7 to V8]
Information in this document applies to any platform.
Area(s):Configuration - General
Release(s):V7 (Professional), V7 (MidMarket), V7 (Enterprise)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
Keywords:hierarchic, hierarchy, multi-lingual, multilingual, LOV, HMLOV, LOV_TYPE, picklist, pick list

This document was previously published as Siebel Technical Note 632.


Hierarchical LOVs (H-LOVs) and picklists are a supported feature in Siebel Business Applications. Hierarchical picklists are dependent on or constrained by values in another picklist.  For example, on the Service Request business component, the Area and Subarea fields use H-LOVs so that the values available in the Subarea picklist are dependent on the value picked for Area. In this example, the Area and Subarea fields both use picklists that are based on the List of Values table and which use the same LOV_TYPE. Hierarchical picklists set the SUB_TYPE (Parent LIC) field in the child or dependent LOV to the name of the parent LOV.  If SUB_TYPE (Parent LIC) is NULL, the picklist is not hierarchical.
Multilingual LOVs (MLOVs) are also supported and are frequently used in global deployments.
Some customers require a combination of these two features, called hierarchical multilingual list of values (H-M-LOVs), or, in Siebel 7.7 and later, the ability to combine hierarchical, multilingual, and multi-organizational LOVs. <Bug 10453191> has been logged as an enhancement request for this functionality. It is resolved with the publication of this technical note.
This technical note announces full support for:
Due to the inherent complexity of the setup, H-M-LOV or H-M-O-LOV enabling requires that Siebel Solution Support Engineering are involved in the following activities:
NOTE: Siebel Solution Support Engineering must review the H-M-LOV or H-M-O-LOV enabling process. Customers will need to submit a Non Standard Change Request (NSCR) with Solution Support Engineering. Please contact your Siebel Technical Account Manager (TAM), Customer Account Manager (CAM) or  Sales Representative to schedule this request.
No software updates or extra products are needed to use H-M-LOVs or H-M-O-LOV’s in supported Siebel application versions.  However, the following limitations apply:

Technical Support Implications

To ensure that product warranties are not invalidated, and that a customer configuration is not excluded from Siebel maintenance services, Siebel Solution Support Engineering' involvement in configuring and upgrading H-M-LOVs and H-M-O-LOVs must be documented with the customer in the form of either a signed Statement of Work (SOW), or a Non-Standard Change Request (NSCR). This must be done before any Siebel application upgrade occurs.  This will usually be a billable engagement.
Conversely, if Solution Support Engineering is not engaged for configuring and upgrading H-M-LOVs and H-M-O-LOVs, Siebel Systems may exclude any Service Requests which involve such functionality from the normal maintenance services and product warranties. This could have a wide impact, as picklists and their values are often included in queries and other functionality within the Siebel application, even when not directly visible to the end user.


This document is informational and intended for any user.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Technical Support Implications
 LOV Administration Guidelines
 Recommended H-LOV implementation Approach
 Challenges of Enabling H-M-LOVs and Recommended Workarounds

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.