First, create a new Performance Analysis Report Rule and set the grouping rule and source rules, as shown in the following figure. The grouping rule for a Performance Analysis report should always include an entity field like entity name, followed by a performance model.
The performance models determine how the returns are presented. For example, the performance model used in the sample report shown in the following figure reports performance according to the GICS classification scheme. Double-click the model name to view the drill-down levels.
The performance model determines the grouping. You do not have to select security master fields to create the grouping structure. The report extracts the single-period returns for each level from the database. They are not calculated by the report while it is running. The report takes the single-period returns and derives multi-period returns like the month to date, 1-year, or inception to date return.
...
You can use the Entity Hierarchy functionality in Performance Analysis reports to drill through the top level composite to the position level performance of the portfolio constituents. The following figure demonstrates the hierarchy for a typical Composite-of-Composites structure.
| Anchor | ||||
|---|---|---|---|---|
|
...
- Create Hierarchy Levels by setting up Code Values within Codes (ELEVEL - iEntity Level) under the Eagle PACE source. If you are creating entity levels for more than one use (such as composite-of-composite analysis, firm analysis, and multi-manager attribution analysis), Eagle recommends that you choose generic names for the levels. For example, Level 1, Level 2.
In the prior example, the two levels required are Total Level Composite ('ACOM') and Constituent Composite Member (ACOM Constituent 1 and 2). In the following figure, the Code Values represent the level numbers of each composite in the structure.
- Create Custom Entity Hierarchy Field Attributes that reference each of the Hierarchy Levels, as shown in the following figure. Additionally, as shown in the following figure, the field that the Entity Hierarchy Fields should be based on is Entity ID.
| Info |
|---|
| If you are creating field attributes for more than one use (such as composite-of-composite analysis, firm analysis, and multi-manager attribution analysis), you can choose analysis-related names for the field attributes. For example, Plan, Strategy. |
...
By leveraging this functionality and joining it with the appropriate Performance Calculation Rule, you can create the required hierarchy structure and generate Performance Analysis reports with the desired drilldown capabilities.
In the following, the total number of levels is three (Total Level Composite, Composite Constituent, and Portfolio Constituent). Building on that example, the Grouping Rule displayed in the following figure, is created with each of the levels in the hierarchy followed by the Performance Model (shown in the following figure).
Now, based on the Grouping Rule displayed in the previous figure the report displays the report hierarchy and the output results on a Performance Analysis Report shown in the following figure.
This methodology also supports cases where the same entity exists as a constituent within multiple composites. Additionally, it supports cases where multiple composites selected with different hierarchy levels can be displayed accurately in the same report.
...
To enable this, create a Custom Entity Hierarchy Field attribute that references Submitted Entity (internal field). Additionally, select the field that the Entity Hierarchy Field should be based on. As shown in the following figure, this is the Entity ID.
Once you create the Entity Hierarchy Field with Submitted Entity is created, you can use it in conjunction with a Performance Model in the Grouping Rule of Performance Analysis reports. In the following figure displays the report hierarchy and the output results on a Performance Analysis report using Submitted Entity.
