Eagle Performance provides a way to override certain system settings and default processes.
| Anchor | ||||
|---|---|---|---|---|
|
As noted earlier, there is a system setting that controls the accrual methodology used by the Performance engine. A setting of M is for monthly accrual processing while D constitutes a daily accrual. The system setting is applied to all gross return fields for all funds. However, Eagle Performance allows you to override the accrual methodology on an entity by entity basis. For example while the system may be set to use the monthly accrual methodology, you can configure specific funds to use the daily methodology.
The easiest way to maintain a fund accrual methodology override is to use the Portfolio Data Center and set the value within the application.
To override the accrual methodology:
...
Eagle Performance looks for accrual method overrides on the MFP_GR_ACCRUAL column (found on the ENTITY_EXTENSION_HIST table; ENTITY_EXTENSION if the report is not using entity history).
Note: | Once the field is built and the inventory of fields is set accordingly, you can set the override as necessary using the respective Fund Policy in Portfolio Data Center. Performance reports use entity history by default. Be careful to set the override as of the effective date you want the override to be effective. Best practices include setting the override as of the fund's inception date (assumes the override is to always be applied for this fund). |
| Anchor | ||||
|---|---|---|---|---|
|
As noted earlier, Eagle Performance grosses up the return using the annual ratio stored on the MFP_EXP_RATIO column (found in the ENTITY_EXTENSION_HIST table or ENTITY_EXTENSION if the report is not using entity history.)
Eagle Performance allows you to override the use of this default location and gross up a return based on any ratio you store in the system. You can choose to use another value by applying a field-level override within the dynamic mutual fund performance field. The field must be a numeric value stored on either the ENTITY_HIST or ENTITY_EXTENSION_HIST tables (or ENTITY or ENTITY_EXTENSION if you choose not to use the entity history option in a report.)
For example, assume there is an alternate expense ratio being stored in the ENTITY table on USER_FLOAT5. First, you must set up a field attribute pointing to the alternate expense ratio. Once this is done, that field is available as a Value Override on the dynamic Mutual Fund Performance field.
To override the expense ratio:
...
In the following figure, note the lower portion of the field display. The Advanced tab has been selected to display the area where overrides can be applied. The expense ratio override can be found on the Values tab.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Expense waivers are similar to the expense ratios noted above. By default, Eagle Performance always uses the value stored on the MFP_ANN_EXPWAIVER column in the ENTITY_EXTENSION_HIST table (or ENTITY_EXTENSION if the report is not using entity history) when netting down a return for expense waivers.
Eagle Performance allows you to override the use of this value. You can choose to use another value by applying a field level override within the Dynamic Mutual Fund Performance field. The field must be a numeric value stored in either the ENTITY_HIST or ENTITY_EXTENSION_HIST table.
The expense waiver override can be maintained on the Values tab within a dynamic mutual fund field.
For example, assume there is an alternate expense waiver ratio being stored in the ENTITY table on USER_FLOAT6. First, you must set up a field attribute pointing to the alternate expense waiver ratio. See the following figure. Once this is done, that field is available as a Values on the Dynamic Mutual Fund Performance field.
To override the expense waiver:
...