Access MPC Fields

The MPC fields are accessible only from the MPC Field dialog box, and they determine which columns in PERF_SEC_RETURNS must be queried and updated during the calculation process. The following figure shows the Multiperiod Performance Calculator Field Dialog Box.


The parameters for each field are listed in the following table.

Parameter

Description

Parameter

Description

Operation Type

Determines the operation to perform and then store in the Result field. Examples are a geometric linked return or sum. Options include:

  • Average

  • Percent Return

  • Sum

  • Unit Value Calculation

Percent Return

Geometrically links single-period returns to form a cumulative or annualized to-date return. This field links the starting period frequency returns for the specified period option. The return at the beginning of the operation period equals the current day's return. For example, a month-to-date operation on the first day of the month the value equals the first day return value.
If the annualize option is selected, the cumulative return must be annualized based on the actual number of days, not business days, in the period.
If a primer record is set up in the period, and the result field is not null, the value in the result field should be used as the first return, with subsequent returns linked to it. If the annualize option is used, the primer record's return should be annualized based on the actual number of days in the period that it represents.

Unit Value Calculation

Geometrically links single-period returns to form a cumulative or annualized unit value return. This field links the starting period frequency returns for the specified period option and then multiplies it by the base value. The unit value at the beginning of the operation period equals the current day's return times the base value. For example, a month-to-date operation on the first day of the month the value equals the first day return value times the base value.
If the annualize option is selected, the cumulative return must be annualized based on the actual number of days, not business days, in the period prior to being multiplied by the annualized return.
If a primer record is set up in the period, and the result field is not null, the value in the result field should be used as the first unit value with subsequent returns linked to it. If the annualize option is used, the primer record's unit value should be annualized based on the actual number of days in the period that it represents.

Sum

Sums the values in the column over the period. This field sums the starting day's value for the specified period option. The sum at the beginning of the operation period equals the current day's value. For example, a month-to-date operation on the first day of the month the value equals the first day's value.
If a primer record is set up in the period, and the result field is not null, the value in the result field is used as the first value with subsequent values added to it.

Average

Averages the values in the column over the period. This field sums the starting day's values and divide by the number of data points accumulated. The average at the beginning of the operation period equals the current day's value. For example, a month-to-date operation on the first day of the month the value equals the first day's value.
Primer records are not be supported and are ignored by the average operation.

Base Field

The performance field attribute pointing to a column in PERF_SEC_RETURNS used as the source of the returns or values used as an input when computing the derived operations.

Result Field

The performance field attribute pointing to a column in PERF_SEC_RETURNS to store the calculated value.

Base Value

Enabled only for the Unit Value operation, this value identifies the starting unit value, for example 100 or 1000.

Use Business Calendar

Determines whether the calculator checks the business calendar prior to updating a record. For example, if a "D" frequency record is being processed and the day is not in the business calendar, it is bypassed and not updated. Options include:

  • Selected (Check mark). Eagle Performance uses the entity level business calendar for the entity, if it is available; otherwise, it uses the Eagle PACE business calendar. This ensures that all the business days have data for the calculation.

  • Cleared (No check mark). Default. The business calendar is not used.

    Also determines whether the field operations checks to ensure that the data is available for all business days in the specified period option. If all data is not available a null value is stored in the derived frequency's Base field.
    This option supports the ability to null partial period returns. For example, a month-to-date return is null for the first month if the first day of activity is in the middle of the month.
    Set this option consistently across all fields in the rule. For example, if a rule includes a mix of business calendar fields, some fields may be updated on all "D" records while others may be updated on "D" records that have an entry in the business calendar.

I want to calculate (Operation Period)

The period, which the operation represents. This includes weektodate (WTD), month-to-date (MTD), quarter-to-date (QTD), year-to-date (YTD), fiscal-year-to-date (FYTD), or inception-to-date (ITD). When using fiscal-year-to-date or inception-to-date, the date field attribute is selectable.

Annualize

Determines if the operation should annualize the results.