1.1 List of Values

This topic provides an overview of the List of Values.

Oracle FLEXCUBE Development Workbench provides the developer with a user-friendly console for defining LOV’s of FCUBS handling the high volume data with the following parameters. The following are the parameters/features for handling such LOVs:
  • Exact Fetch
  • Is Mandatory
  • Minimum number of Search Character

Exact Fetch

In the Block Field Properties screen, if the field Display Type is of LOV, then the developer can select the Exact Fetch parameter for search optimization (in High Volume).

Figure 1-1 Block Field Properties_Exact Fetch



If the Exact Fetch parameter is selected, the user has to provide the exact values of the field as it is present in the Database; otherwise, the system will throw the error message as an invalid value. Wildcard Searches are not permitted.

For Example: Entering 98712 in the Account Number field will fetch value only if an account with that particular number exists. In the Normal case, all account numbers beginning with the search pattern would be retrieved.

Figure 1-2 Information Message on Exact Fetch



Is Mandatory

This parameter should be specified during the definition of LOV in ODT. If this parameter is selected, then total wild card search (by providing blank or % in reduction fields) won’t be allowed on fields where the particular LOV is attached.

In the LOV definition screen, Is Mandatory option would be enabled for all Reduction Fields. This feature is not available for Global LOVs.

Minimum Search Character Length

If Is Mandatory is selected as Yes for any reduction field, ODT will ask for minimum search character length. By default, the value is 3.

If the fields Is Mandatory and Minimum Number of Search Character is given as n, then while searching, the user has to enter a minimum of n characters to search a particular value otherwise the system will show an error message.

Any value less than 3 (Default value) will not be accepted. ODT will show an alert message in case of any rule violation. This feature is not available for Global LOVs.

Example: Customer LOV should allow searches based on Is Mandatory and Minimum Number of Search Character fields only and total wildcard search should not be allowed.

The figure below illustrates Is Mandatory and Minimum Number of Search Character fields in ODT.

Figure 1-3 Is Mandatory and Minimum Number of Search Character