This section assumes you are familiar with the creation of OLAP report rules. It provides hints and suggestions specific to mutual fund performance applications. For detailed information on report rules, refer to the PACE Reporting Reference Guide.
The name of the report rule becomes the name of the performance dictionary once returns are committed.
The grouping rule must be set to use an entity attribute that is unique. Best Practices dictates the use of Entity ID field as the sole grouping.
The field rule portion can contain numerous fields (dynamic mutual fund, rollup calculation, rollup inference). Consider that the main purpose of the eventual report is to push results to the database. Therefore, Best Practices dictates (but does not require) that the field rule only include fields that are committed or used as a reference check.
Be sure to set the source hierarchy for the dynamic mutual fund fields. If you want scrubbed data to be included, choose Eagle PACE as the primary source for NAV component data. If you do not want scrub records to be included in the return calculation, do not choose the Eagle PACE source. Note that you can identify the source if you load fund accounting data using the NAV default stream.
An example of a Dynamic NAV Returns report rule follows.
