1.8.1 Population of UDF Values at the Contract Level

The defaulted or derived values of the UDF linked at the product level are populated in the Contract Input screen at the time of processing contracts under a particular product. Similarly, the values of the UDF’s linked to a Function Id are populated in the Function Id screen. The UDF’s linked to a particular product are available when a contract is processed under that product.

Specify the User ID and Password, and login to Homepage.

From the Homepage, navigate to Loan and Commitment-Contract Input screen.

1. On Loan and Commitment-Contract Input screen, click UDF tab.
   The Fields screen is displayed.

   Figure 1-9 Fields

   
   

   
   Description of "Figure 1-9 Fields"

   
   
2. In this screen, all the user defined fields associated with the product under which you are processing the contract are displayed.
3. According to your specifications at the time of defining the user defined fields, system may derive the values of the UDF from:
   • Derivation Logic: When you click Fields button, system derives and displays the values of the fields for which derivation rules are written. The value description is also displayed alongside.
   • Static List of Values: If the validation type of the UDF that is associated with the contract is List of Values (LoV), system displays the static values, along with the value description. If you have indicated a default value for the LoV, the default value and its description is displayed. When a user selects the value from the LoV, the system displays the description on the screen.
   • Method of derivation for cube entity fields: If a UDF is of type Cube Entity, system populates the values in a LoV. The values are derived from the specified Oracle Lending table (if the cube entity type is Static) or from the query written by the user (if the cube entity type is Dynamic)
4. You are not allowed to change the values of the fields for which you have not allowed amendment (if the option Amendable is deselected at the time of defining an UDF) and derivation is allowed (Option Derivation Allowed is selected).
5. Enter the values for the fields, for which the values are not derived by the system.
6. You can change the value of a UDF after the system has derived the value from the derivation logic. But it might so happen that the derivation logic of another UDF might use the value of the UDF that you have changed. Consequently, if you change the value of the UDF whose value is used in another UDF, the value of that UDF also changes.

   For example, let us assume that you have defined a user defined field UDF1 to display the Euro equivalent of the contract currency.

   The derivation logic of another user defined field (UDF2) utilizes the values of UDF1 to arrive at the value of UDF2. Assume that in the derivation logic written for UDF2, you have specified that the value of UDF2= 2 UDF1.

   At the contract level, system converts the contract currency into Euro equivalent and displays the value of UDF1, as 220.00. According to this value of UDF2 is 444.00. However, if you change the value of UDF1 to 250.00, it effects on the value of UDF2 also (it becomes 500.00).

7. If the change in the UDF value has effected any other UDF, system displays an override informing you about the UDF whose value is changed. Select Ok button if you want the system to re-calculate the value of the UDF based on the modified UDF value.