Hierarchical PickList in siebel

Siebel Support Web For Complete Siebel Reference

Hierarchical PickList

19 January 2010 1,421 views 5 Comments

Picklist is used to restrict or constraint the values of child Picklist based on the value of parent. Hierarchical Picklist shows all the values including child Picklist values.

Steps to configure Hierarchical PickList

1. Configure a parent and a child PickList

Configure a parent and a child PickList both the PickList have same Type Value ie LOV Type (STATUS_SWATI in this example).

Set the Business Component property of the parent PickList to “PickList Hierarchical”.
Set the Business Component property of the child PickList to “PickList Hierarchical Sub-Area”.

Hierarchical PickList 1

2. Go to the Business Component

Go to the BC that contains the fields that we want to associate the Hierarchical PickList with.

In this example,

BC = Service Request

Fields = Status and Sub-Status

Set the PickList property of the parent field (here “Status”) to the parent PickList. Set the “Immediate Post Changes” of the parent field to “TRUE”.
Set the PickList property of the child field (here “Sub-Status”) to the child PickList.

Hierarchical PickList 2

3. Define the Pick Maps for the fields

Pick Map values for the parent field is given as shown.

Hierarchical PickList 3

Pick Map values for the child field is given as shown.

Hierarchical PickList 4

The values in various fields of the Pick Map objects are given as-

Field PickList Field Constrain

Name of the Parent Field (Status) parent True

Name of the Child Field (Sub-Status) value

4. Define the value in LOV Explorer

Define the Type “STATUS_SWATI” in LOV Explorer as shown below.

Hierarchical PickList 5

Define the LOV values in list of Values as shown.

(Values considered here are for example)

Hierarchical PickList 6

Here “Active” and “Inactive” are the parents and rest all values are child.

5 Comments »

Rajat said:

Swati, Nice description. Your article are well formatted and please dont mind if i use them in my training documents.

# 21 January 2010 at 2:06 am

Swati Pawar (author) said:

Hey Rajat.
Thanks.
Reusing
These are copyright of http://www.siebeloracle.com ….. sorry

# 22 January 2010 at 8:08 am

kiran said:

Hi,

I have one question, you can do this configuration using Picklist Hirearchial BC for both parent and child. This will work without any errors.
The parent child relation can be obtain by using Picklist Generic BC for both parent and child. In pick map, instead of parent we need to specify Description, where in List of Values we give parent value in descritpion field of child.

My question is when we are able to achieve parent child relation by using the above mentioned ways, why we should have these many picklist bc’s in Siebel?

# 21 February 2010 at 12:12 am

Arvind Pandey said:

Swati, Can u tell me Which is better approach Constraint picklist or Hierarchical picklist

# 11 April 2010 at 12:46 pm

Ashish Kumar said:

Hi Arvind,
The approach will depend on the requirement. The difference between Constraint picklist or Hierarchical picklist will help you to understand which will be best approach for an implementation.

http://www.siebeloracle.com/hierarchical-and-constraint-picklist/

Feel free to share any query.

Regrads,
Ashish

# 11 April 2010 at 6:43 pm