6.4.1.6 LGD Term Structure Type Variable

To define a LGD Term Structure type of variable:

1. Select the variable sub type as PD Term Structure in the Variable Sub Type drop-down menu.
2. Select one of the value types listed.
   Select one of the following options:

   • Percentage
   • Ratio
3. On the Basic Details page, provide the following additional fields:
   1. In the Import field, do either of the following:
      • Select Yes to import an existing LGD Term Structure definition.
      • Select No to create a new one.
   2. In the Hierarchy Type field, select the required hierarchy type from the drop-down menu.
   3. In the Hierarchy field, select the required hierarchy.
   4. In the Term Points field, enter the required term point value.

      Note:

      The Advanced Setup step has been removed from the guided flow for Matrix variables. Hierarchy Type and Hierarchy are now configured directly on the Basic Details page.
4. Click Continue.
   The Map Data Sources screen is displayed.
5. In the Map Data Sources page, do the following:
   1. Map the following required glossaries, which are used to seed scenario data:
      • Hierarchy
      • Term point
      • LGD values
   2. Map the logical reference.
   3. Map one ID glossary to the ID column of the master or support table.

   If Import is No:

   • All required glossaries are displayed.
   • These mappings seed data for both detail and master tables.
   • Some glossaries are optional (as certain columns can be null).
6. Click Continue.

   The Add Source Filters screen is displayed.

   Once mappings are complete, the tables linked to the logical reference are displayed. A drawer opens presenting a 3-step guided workflow:

7. Define the relationship between the detail (input) table and the master (support) table. The system suggests relationships based on primary key / foreign key (PK/FK) constraints. To do so, do either of the following
   • Select a suggested relationship.

     The relationship fields are auto-populated.

   • Manually define the relationship by specifying:
     • Detail table column
     • Master table
     • Master table column
8. Define default values for the detail table columns based on their data types.

   Note:

   The following columns are disabled and cannot be edited:

   • Glossary-mapped columns
   • FICMISDATE

   Defaults may be set for all other columns.

9. In the Market Variable Entry (Master/Support Table) page that opens, do either of the following:
   • If Import is Yes:
     • Only the ID column is enabled and is displayed as a dropdown pre-populated with existing IDs.
     • Select the required ID.

       All other fields auto-populate and become non-editable.

   • If Import is No:
     • The ID column is disabled (the ID is generated automatically by the backend).
     • All other fields are enabled.
     • Some fields are mandatory (corresponding to non-null columns).
10. You can save and close the drawer once all three of the following conditions are met:
    • The relationship between detail and master tables is defined.
    • Default values are set for the required columns in the detail table.
    • An ID is selected (Import = Yes) or fields are populated (Import = No) for the master/support table.

    Note:

    • Hierarchy override (Import = Yes): Selecting an ID in the master/support table may override the Hierarchy Type selected on the Basic Details page, causing the Hierarchy field to reset. During Review & Validate, an alert is displayed if the hierarchy is missing. You must re-enter the hierarchy value on the Basic Details page before submitting.
    • The Name and Description fields are not overridden during import.
    • Only a query for the detail table is generated. No query is generated for the master/support table.
    • Only one input table can currently be mapped to a glossary.