Saturday, April 14, 2012

Types of Value Sets


You can define several types of value sets depending on how you need your values to be checked. All value sets perform minimal checking; some value sets also check against the actual values, if you have provided any.




Navigation Path: System Administrator->Application->Validation->Set/Values

None - A value set of the type None has no list of approved values associated with it. A None value set performs only minimal checking of, for example, data type and length. Examples of such values include credit card numbers, street addresses, and phone numbers.

Independent - Use the validation type Independent when you know the allowable values ahead of time. Independent type value sets perform basic checking but also check a value entered against the list of approved values you define.


Dependent
- A Dependent value set is also associated with a list of approved values. In this case however, the values on the list can be grouped into subsets of values. Each subset of values is then associated with a value from an Independent value set. Once a value from the Independent value set has been specified, the list of values for the Dependent value set displays only the values that are approved for the value selected from the Independent value set.


In below picture, once a value from the Category value set has been specified, only the appropriate values from the Item value set are displayed.

Table - Table value sets obtain their lists of approved values from existing application tables. When defining your table value set, you specify a SQL query to retrieve all the approved values from the table.


Special - This specialized value set provides another flexfield as a value set for a single segment. Special value sets can accept an entire key flexfield as a segment value in a descriptive flexfield or report parameter.

Pair - This specialized value set provides a range flexfield as a value set for a pair of segments.

Translatable Independent - Translatable Independent value sets are similar to Independent value sets except that translated values can be displayed to the user. Translatable Independent value sets enable you to use hidden values and displayed (translated) values in your value sets. In this way your users can see a value in their preferred languages, yet the values will be validated against a hidden value that is not translated. A Translatable Independent value set can have only Translatable Dependent value sets dependent on it.

See Example: Appliances and Furniture can be displayed in two languages (Gerate and Mobel) or (Appareils and Meubles).

Translatable Dependent -Translatable Dependent value sets are similar to Dependent value sets except that translated values can be displayed to the user. Translatable Dependent value sets enable you to use hidden values and displayed (translated) values in your value sets. In this way your users can see a value in their preferred languages, yet the values will be validated against a hidden value that is not translated. Translatable Dependent value sets must be dependent on a Translatable Independent value set.
See Example: Appliances and Furniture can be displayed in two languages (Gerate and Mobel) or (Appareils and Meubles).  Microwave can be displayed in Mikrowellenherd or Four a micro-ondes.

Significance of $FLEX$

$FLEX$: enables to match the prior segment with either value set name or segment name. Let v2 be the value set definition of 2nd parameter and v1 be the value set definition for the first parameter then:

In the value set definition of v2 = value $FLEX$.v1

Changes You Should Never Make

You should never make these types of changes (old value set to new value set) because you will corrupt your existing key flex-field combinations data:

  1. Independent to Dependent
  2. Dependent to Independent
  3. None to Dependent
  4. Dependent to Table
  5. Table to Dependent
  6. Translatable Independent to Translatable Dependent
  7. Translatable Dependent to Translatable Independent
  8. None to Translatable Dependent
  9. Translatable Dependent to Table
  10. Table to Translatable Dependent

No comments:

Post a Comment