You can create composites of composites. When you create composites of composites, composite entities consisting of either composites or of portfolio entities are created. You can also enumerate composites. This allows you to direct the Reporting engine to look through the composites selected for a report, drilling through one composite to the underlying report composites. PACE supports the storing of hierarchy of entities as it stores the relationships between entities, which can be nested to any degree.
...
You do not have to run the entity build process for the composites on which they choose to report, they simply must include the composites in the report. You must select the option enumerate composites for the entity hierarchy functionality to work in a report.
Level 1: | Level 2: | Level 3: | Level 4: |
Composite 1: |
|
|
|
| Composite 2: |
|
|
|
| Composite 4: |
|
|
|
| US Fund 1 |
|
| Composite 5: |
|
|
|
| US Fund 3 |
|
| Composite 6: |
|
|
|
| US Fund 1 |
| Composite 3: |
|
|
|
| Composite 7: |
|
|
|
| EU Fund 1 |
|
| Composite 8: |
|
|
|
| EU Fund 3 |
Entity Hierarchy
Set Up the Entity Hierarchy Function
...
Create code values under the Eagle PACE source. The code values must reflect the appropriate level. The short description is the level number. The long description is a descriptive name.
Entity Hierarchy Code Values
After creating the codes and code values, you create entity hierarchy fields as explained starting in step 2.
Return to General Reporting, and select Compose.
Select the report type you want to create.
From the Fields toolbox, select Entity Hierarchy Field.
...
You see the Entity Hierarchy Field dialog box
...
.
...
Complete the fields on the Entity Hierarchy Field dialog box as follows:
...
Name. Enter a unique name.
...
Comments. Enter a descriptive comment.
...
Hierarchy Level. Select a Branch, Country or Group hierarchy level. Codes values created in the Data Steward are available in this list.
...
Field Name. Select an Entity Field on which to base the Entity Hierarchy field.
Entity Hierarchy Fields
You create Entity Hierarchy fields based on entity fields from the Entity Table or on fields from the Entity Extension tables. You cannot create Entity Hierarchy fields based on fields from the Entity Characteristics table of the Rules database.
...
You must create rollup fields of the field attributes in the field rule to see data for the composites at the top level. In the option Choose Entities and Dates, select Enumerate Composites.Entity Hierarchy Workspace
...
You can run the report for the lowest or highest level of the hierarchy. The data returned is based on which entities the report is run. If you run the report for a portfolio, and the entity hierarchy fields are included in the report, then that entity hierarchy relationship is displayed in the result set.Example Entity Hierarchy Grouping
...
The above example shows the entity hierarchy fields used to group the report. The top level of the report is the Company Entity ID, next is the Branch Entity ID, followed by the last level of composite, the Group Entity ID. Finally, you can drill down to the Entity ID of the portfolio and to the security level. You can see values returned at the composite level because there are rollup sums on the field attributes. The Entity Build process was not run for these composites.
...
If a fund (portfolio) is held by more than one composite, the data for the fund is duplicated for each relationship it has with other entities. For example, in Figure 119 on page 131, if US Fund 1 belonged to both US Equities and US Balanced the data for US Fund 1 would be displayed twice in the report.
...
If relationship information does not exist on a particular level, then the relationship information is labeled Unknown. This functionality does not support fetching details from the Entity Details table, such as percent of ownership and is intended only for composites. Entity hierarchy fields are used as the grouping rule. The option Enumerate Composites is selected.
...
The following table contains an example of hierarchy Entity IDs.
Level 1: Country | Level 2: Branch | Level 3: Group | Portfolio Level: |
Composite 1: EPDC1 |
|
|
|
| Composite 2: EPDB1 |
|
|
|
| Composite 4: EPDG1 |
|
|
|
| Portfolio 1: |
|
| Composite 5: |
|
|
|
| Portfolio 3: |
| Composite 3: EPDB2 |
|
|
|
| Composite 6: EPDG3 |
|
|
|
| Portfolio 5: |
...
For all example reports in this section, the Enumerate Composites option is on. The only items that change in these examples are the entities for which the report is run. All of the appropriate fields in the field rule were rolled up to show data at the composite level. The entity build process was not run for these composites. The reports are set up as shown in Figure 120below.Example Hierarchy Reports Setup
...
This example shows a report run for EPDC1. This report receives data for EPDC1, EPDB1, EPDG1, EPDP1, EPDP2, EPDG2, EPDP3, EPDP4, EPDB2, EPDG3, EPDP5, and EPDP6.
The Company Level is Company Entity ID, the Branch Level is Branch Entity Id, and the Group Level is Group Entity ID
Example EPDC1 Report
Example EPDB1 Report
...
This example shows a report run for EPDG1. This report receives data for EPDC1, EPDB1, EPDG1, EPDP1, and EPDP2.
Example EPDG1 Report
This example shows a report run for EPDP1. This report receives data for EPDC1, EPDB1, EPDG1, and EPDP1.
Example EPDP1 Report
...
Other examples result in the following:§
Run a report for EPDB2 – This report receives data for EPDC1, EPDB2, EPDG3, EPDP5, and EPDP6.
...
Run a report for EPDG2 – This report receives data for EPDC1, EPDB1, EPDG2, EPDP3, and EPDP4.
...
Run a report for EPDG3 – This report receives data for EPDC1, EPDB2, EPDG3, EPDP5, and EPDP6.
...
Run a report for EPDP1, EPDP2, EPDP3, EPDP4, EPDP5, and EPDP6 – This report receives data for EPDC1, EPDB1, EPDG1, EPDP1, EPDP2, EPDG2, EPDP3, EPDP4, EPDB2, EPDG3, EPDP5, and EPDP6.
...
Run a report for EPDC1, EPDB1, EPDB2, EPDG1, EPDG2, and EPDG3 – This report receives data for EPDC1, EPDB1, EPDG1, EPDP1, EPDP2, EPDG2, EPDP3, EPDP4, EPDB2, EPDG3, EPDP5, and EPDP6.