To constrain the list of values of a picklist field (Eg: ‘Status’) based on another picklist (Eg: ‘Type’) field value of business component (Eg: ‘Contact’) in multi organization environment.

• Consider there are two organizations ‘Org1’ and ‘Org2’.
• Org1 has no constrained on ‘Status’ field in Contact. It is normal pick list based on ‘Picklist Generic’ business component.
• Org2 needs to have constrained on ‘Status’ field based on values ‘Type1’ or ‘Type2’ of ‘Type’ field in Contact.
• Create new picklist based on ‘Picklist Hierarchical’ based on LOV Type, same as the existing pick list mapped to ‘Status’ and map it to ‘Status’ field.

Approach:
Normally, whenever a field value have to be constrained on another field, both the fields have to be mapped to hierarchical pick lists and pick maps will be configured so as to constrain the values. Following is alternate approach that can be followed using UpdOnlyIfNulls object definition of Pickmap
 Configuration Steps:

Business Component: Contact
As Mentioned below, create new calculated fields which will have value based on Organization and ‘Type’ field value

Map the new hierarchical picklist to ‘Status’ field as follows:
Field:

Pickmaps:
Create following pick map for ‘Status’ field

Pickmap UpdOnlyIfNulls:
Create following for pickmap ‘Type Calc’ created above

NOTE: ‘UpdOnlyIfNulls’ is to disable the constraint when the constraining field value is null, using a calculated field as the field for the constraint pick map.

The list of values in Data Administration à List of Values setup can be made as below: