Entity Analytics Source Rule

The Entity Analytics Source Rule contains the sources for Entity Analytics and Entity Membership feed types as shown in the following figure.

Open

On this page

• 1 Entity Analytics Source Rule
  • 1.1 Entity Analytics Field Attributes
  • 1.2 Create a New Entity Membership Field Attribute
  • 1.3 Create an OLAP Report
  • 1.4 Validate Data in PACE and Data Mart 

Entity Analytics Field Attributes

Peer Group Reporting supports the following types of field attributes:

• Entity Analytics. This field attribute type allows you to select either: Database = RULES, or Table = (taken from PACE Inventory of Tables where the table Indicator is EA for Entity Analytics). This field attribute type handles these three tables:

  • ENTITY_ANALYTICS

  • ENTITY_PEER_GRP_ANALYTICS

  • ENTITY_RATINGS

• Entity Peer Group Rankings. This field attribute type handles only table ENTITY_PEER_GRP_RANKINGS. This field attribute type allows you to select either: Database = RULES, or Table = (taken from PACE Inventory of Tables where the table indicator is EM for Entity Membership).

To create a Peer Group reporting field attribute:

1. In Reporting Center, from the left navigation, select Data Management Reports > OLAP Reporting > General Reporting.
   You see the General Reporting workspace.

2. In the Components tab, expand the Fields folder and select Entity Analytics.
   You see a list of fields for the respective type.

3. Click New. 
   You see the New Regular Field dialog box.
   

4. In the Name box, enter a name for the field.

5. In the Comments box, provide comments about the field, if required.

6. Click Table to select a table from the dropdown list.
   After you select a table, the Related Entity Types dropdown appears.

7. Click Related Entity Type to choose whether this field attribute pertains to a fund, to the fund's peer group or to its benchmark.
   If you selected Peer Group or Benchmark in Related Entity Type, a prompt field for Peer Group Definition, or Benchmark Definition appears.

8. In Peer Group Definition or Benchmark Definition, enter the appropriate selection to define the field as pertaining to the right related entity for the portfolio being reported.
   NOTE: These fields appear if you set the Related Entity Type option to value other than <none>.

9. Complete the fields on the dialog box as required and click OK to save the regular field.

Create a New Entity Membership Field Attribute

You can create new entity membership field attribute in General Reporting.

To create a new entity membership field:

1. In Reporting Center, from the left navigation, select Data Management Reports > OLAP Reporting > General Reporting.
   You see the General Reporting workspace.

2. In the Components tab, expand the Fields folder and select Entity Membership.
   You see a list of fields for the respective type.

3. click New.
   You see the New Regular Field dialog box.
   

4. In the Name box, enter a name for the field.

5. In the Comments box, provide comments about the field, if required.

6. Click Table to select a table from the dropdown list.
   After you select a table, the Related Entity Types dropdown appears.

7. Click Related Entity Type to choose whether this field attribute pertains to a fund, to the fund's peer group or to its benchmark.
   If you selected Peer Group in Related Entity Type, a prompt field for Peer Group Definition appears.

8. In Peer Group Definition, select Primary Peer Group or Secondary Peer Group option.
   NOTE: These fields appear if you set the Related Entity Type option to value other than <none>.

9. Complete the fields on the dialog box as required and click OK to save the field.
   NOTE: PACE supports a Detail Calc or an Inference field based on the previous 2 field attributes.

Create an OLAP Report

To create an OLAP report based on Peer Group fields, first create a Report Rule.

To create a report rule:

1. In Reporting Center, from the left navigation, select Data Management Reports > OLAP Reporting > General Reporting.
   You see the General Reporting window.

2. On the Components tab, select the Report Rules folder.

3. Open the Entity and Client sub-folder.

4. Select Range.
   You see all the available report rules for the selected type.

5. Right-click and select New.
   You see the New Report Rule window.

6. Type the Report Rule name and select Grouping.

7. Click Choose an existing Source Rule. Select the Source Rule.

8. Select the field attributes for the rule and save the rule.
   Next, complete the following procedure to create the OLAP Range report.

To create an OLAP Range report:

1. In Reporting Center, from the left navigation, select Data Management Reports > OLAP Reporting > General Reporting.
   You see the General Reporting window.

2. Click the Reports tab and open the Entity and Client folder.
   You see all the available reports for the selected type.

3. Right-click in the list of available reports, and select New.
   You see the Creating an Entity Client Report dialog box. 

4. Complete any necessary fields on the dialog box, and click Next.
   You see the Entity Client Report Scheduling dialog box.

5. Select how you want to schedule the report, and click Finish.
   Run the report to fetch the Peer Group data that was loaded to the warehouse.

Validate Data in PACE and Data Mart 

OLAP report allows you to validate the data between PACE and Data Mart. It helps you to triage, when the Data Mart fails or the Data Mart value differs from the expected value.

To validate the data, follow the below steps:

• Build an OLAP report with the same field attributes as the Data Mart with the same set of entities and effective date.

• Submit the report and validate the data generated via OLAP report matches with the Data Mart.

• If the data matches, then the Data Mart data is valid. If not, compare the Model Manager log and the OLAP log. In some cases, any specific settings at Report or Data Mart level is the reason for the data mismatch.

• If both the OLAP report and Data Mart fails, then you can confirm, the issue is not pertained to Data Mart but overall a PACE issue.

• You need to create a Performance Analysis report for Performance type of Data Mart models or when performance fields are used in Fund Summary model.