1. User Guide
  2. Application Workflow
  3. Application Configuration
  4. Configure the Seeded Data

Configure the Seeded Data

Perform the following steps to modify the seeded data in the Application Configuration window:
  1. Populate the Application Configuration Form as tabulated.

    Table 4-1 The Application Configuration Form

    Property Name Description
    Fields marked with an * are mandatory
    Application Type*

    Select the Application Type from the drop-down list. Available options are:

    • IFRS17
    • LDTI
    • IFRS17 & LDTI
    Frequency for Retrospective calculation(including net premium ratio) during LDTI Liability calculation run*

    Specify the frequency at which the LDTI calculation run needs to be executed retrospectively for the past data. This must also be provided as an input at the same frequency.

    Select the required frequency from the drop-down list. Available options are:

    • Annually
    • Half Yearly
    • Monthly
    • Quarterly
    Day for Retrospective calculation during LDTI Liability calculation Run, If the value is 25, it means retrospective calculation will be executed if FIC_MIS_DATE is on and after the 25th of the frequency month specified in IIA_RETROSPECTIVE_FREQUENCY* Enter a value in this field.
    IRC Forward Rate Max Term* Enter a value in this field. This is the maximum term until which the Forward Rates are computed.
    Degree of Parallelism for the execution of DT* Enter a value in this field. The degree of parallelism is the number of parallel execution servers associated with a single operation.
    Transition FRA Batch wait time* Enter a value in this field.
    Flag for assumption scenario projection index*

    Specify the frequency at which IFRS17 onerous and onerous/what-if scenario projections need to be executed for onerosity testing.

    Select the required Frequency Flag from the drop-down list. Available options are:

    • Annually
    • Half Yearly
    • Monthly
    • Quarterly
    Transition Date*

    Use this field to specify the transition date that must be used for the Transitionary Balance Computations by using the Transition Calculation Templates

    Click Calendar in this field and select the transition date from the calendar.

    Flag for computing all input variables or input variables that are associated with the template* Select either Yes or No. This flag indicates whether the Discounting Engine must compute all Input Variables (“Yes” option) or only the Input Variables that are referred to in the templates (“No” option) used in the Liability Calculation runs.
    This flag indicates Consolidation Criteria. List of Values are E -> Computation based on Solo data, N -> Consolidated data as Input*

    Depending on the value selected in this field, the default Run Type is displayed in the Aggregation Level window :

    • Consolidated data as Input: If this option is selected, then the new flow of solo or consolidated is executed,where the data for solo or consolidated level cohorts are given as input, and the Run Type under “Level of Aggregation” definition screen should be selected accordingly.

    Solo or Consolidated cohorts are identified based on the value of n_cohort_cons_type in Stg_Ins_Group_Dimension_Map. The value 0 indicates a Solo cohort and the value 1 indicates Consolidated cohorts. If the Run Type is Solo, then only Solo cohorts are selected for computation. If the Run Type is Consolidated then only Consolidated cohorts are selected for computation.

    • Computation based on Solo data: If this option is selected, then the existing flow is executed where the child-level entity-linked cohorts are fetched for the group entity run. The inter-company executions for reinsurance issued and held are netted off.

    The value of n_cohort_cons_type in Stg_Ins_Group_Dimension_Map is not considered when this option is selected.

    Note: In the Aggregation Level screen, when creating a new Level of Aggregation Definition, the default RunType is Solo and this field is disabled. In case the RunType was selected as Consolidated for an LOA, then this field is disabled when you try to modify an LOA.

    Enable Debug Message Logging* Select either Yes or No.
    General Ledger Hierarchy pane
    General Ledger Hierarchy applicable for Subledger*

    This is the Ledger Account Hierarchy that is used by the Subledger Definition

    Select a folder and a property value from the Folder and PropertyValue Columns, respectively.