Constraining the Siebel PickList

By amol | March 4, 2008

This post has been contributed by Amol Tondon.

In this post we will discuss about constraining a Pick List. As it is quite clear from the title that we are trying restrict the values in a pick list based on certain constraints. It is best to explain with the help of a requirement.

Requirement:

Two fields having 2 Picklists
Country and State
Based on country selected in country Picklist, only state corresponding to that country should be displayed in state Picklist

For example
Country = US then State Picklist should display only Ohio, Georgia, Texas
Country = India then State Picklist should display M.P, U.P, A.P, Delhi etc

This post assumes that you have already created two Picklists and configured them properly. Coverage of Picklist configuration is not in scope of this post but if you need let me know I will be more than happy to include in my next posts

Solution:

Query for the BC in which you Picklist Field is created
2. Select the Field to which you have mapped your Picklist
Expand its child PickMap
There should already be one record with the values shown below that you created during you configuration of Picklist
Field: State
Picklist Field: Value
Add another record in PickMap as shown below
Field: Country
Constraint: TRUE
Picklist Field: Description
Compile the Business Component you have changed.
Open the Siebel Client Application
Goto Administration – Data> List of Values
Query for the LOV_TYPE containing the State Picklist values.
Update the name of country corresponding to state in description Field as shown below
Click on Clear Cache

Your configuration of constraint Picklist is not complete you should be able to state values based on country field.

(1 votes, average: 5 out of 5)

Loading ...

Categories: Configuration |

6 Responses to “Constraining the Siebel PickList”

Amogh Gupta Says:
March 4th, 2008 at 4:28 am

Thanx alot dude , u have mailed me the right post , to the precision, but i have one doubt instead of adding description value to the pickmap i had added subtype as the value & it was working fine. can u throw some light on this doubt in ur next post. By the way i should thank you again for such a superb reply , keep mailing me i would be rally obliged to you.
Amol Tandon Says:
March 4th, 2008 at 11:06 pm

Yes Amogh you can use subtype also but while configuring the picklist in pickmap object type you have select subtype as the picklist field instead of description.
Logic is no matter which field you are using just you have specify it in the pick map.
for more specification I will write one post on pickmap please wait for that.
For timing there are two type of pickmap copy pickmap and constrain pickmap. constrain pickmap are use for constraining the picklist and copy is to have values in other fields.
shree Says:
April 1st, 2008 at 1:21 am

Hi

This post is nice..thanks Amol..have a query regarding PickList not really sure if its related to this post,hope you can help me with this.. How different is Hierarchy PickList from Constraint PickList
venkatesh Says:
May 30th, 2008 at 5:34 am

I have one more scenario that once this constrain is done it should also diplay all the State Values (Indian States as well USA States) while clicking the State field alone.Is it Possible?
Vijayapandian Says:
June 5th, 2008 at 6:17 am

good
Keith Says:
July 24th, 2008 at 10:14 pm

Well really this is a bad example of pickmap constraints.

The more correct scenario is constraining what contacts of an account once you have selected the account for an Opportunity.

Amol, you have muddied the waters between what is hierarchical picklists as what the scenario above is really about and simply using the pickmap constrain to constrain the list!