Task Based UI @ Siebel 7.8 | Next Tip »Home

How to create Hierarchical Picklist?

OkAvarageGoodVery GoodExcellent (17 votes, average: 4.76 out of 5)
Loading ... Loading ...

I know there aren’t many articles on this website related to basic configuration and a lot of you have asked for it.
So,  as the saying goes “better late than never”,  I am starting with an article on Hierarchical Picklist.

Let’s start with the most basic question:

What is Hierarchical Picklist?

A Hierarchical Picklist is a Picklist that has constrained values based on values of a different Picklist, best example to explain Hierarchical Picklist is Country and State.

Problem Statement.

When I select value in Country field and I should see only see its related States in State Field.

Solution:

To solve this we need to create a Hierarchical Picklist so lets get on with solution

First create two different LOV Type PARENT_LOV and CHILD_LOV with values as shown below:
listofvaluesscreenshot

Create 2 Picklist objects for the above-created LOV Type:

parentchildpicklist

Now we have to do the usual configuration of creating business components fields and associate the above created Picklist as shown below:

parentfieldconfiguration

childfieldconfiguration

After this configuration we will have two fields that are independent of each other showing values as shown below.

parentpicklistvalues childpicklistvalues

Now we need to convert them in Hierarchical Picklist.

To do that, go the List of Values View and query for CHILD_LOV Type and in the Description Field enter Respective Parent LOV Display value. For Simplicity sake I have take LOV names Parent 1 and Child 1 as it child name. Your Child LOV type should look like the picture below:

childpicklistconstraint

Now, go to Tools and for State Field create the record in Pick Map object with following details

Field: Country
Constraint: Y
Picklist Field: Description

childpickmapconstraint

Compile BC and you are done. You have now State Hierarchical Picklist which is constrained on Country Field Value as shown below:

finalhierarchialpicklist

Now, this post might raise a few eyebrows as bookshelf says that to create Hierarchical Picklist we need to have the BC for Picklist record as Picklist Hierarchical but I have chosen it as Picklist Generic. Also there is one more problem: if I change the parent value after choosing child value doesn’t change the Child Picklist (State field in this case) still shows same old value.

I will discuss reason why Picklist Generic BC also works and also the solution of the above mentioned problem  in follow up post.

  • Share/Bookmark

Related Posts


Article by neel

Authors bio is coming up shortly. neel tagged this post with: , Read 387 articles by neel
  • DileepG
    Usually for creating Hierarchial Picklist we are using same LOV types,but in your explanation you mentioned that for creating Hierarchial picklist we need to create different LOV types(Picklists).
    You have explained about Constrained picklist not about hierarchial..
    Please correct me if anything is wrong from my side.
  • Ramesh V
    Hi,

    Nice article.

    Would like to see the next post which deals with the issue you have mentioned at the bottom.

    If it is already available. Kindly add the link to this post.
  • Hi ,

    Using "Parent LIC column" in STATE LOV would be better then using "Description" column.Because Siebel suggests to use "Parent LIC column" for Dependent Pick List . So better use "Parent LIC column" for identifying Parent LOV.Otherwies Oracle Report on SRF can show you warning in RED.

    Danish
    "When you focus on giving you will never be at a loss !"
  • Hi ,
    This is very nice article for dependent picklist.But i would like to add here , we need to make True "Immmidiate change post " property of BC Field:'Country'also.
    Danish
blog comments powered by Disqus

Polls

Do you like the new Comment System and new look to Site?

View Results

Loading ... Loading ...