Create Reports

Report Components

A report is made up of the following components shown below.

• Report Profile. A report profile is the combination of entities, dates and a report rule created to generate report results.

• Report Rule. The report rule defines the structure of the report. The individual components of the report rule are the source rule, field rule, and grouping rule. These components define a report by specifying where the data originates, which data to display and how.

• Source Rule. The source rule determines which sources, such as holding or trade, provide the data for each field type in the report.

• Field Rule. The field rule defines the data included in the report.

• Grouping Rule. The grouping rule determines how data in the report is organized.

• Report Packages. A collection of reports you can distribute to selected users. You select which profiles are included in the package. When the package is submitted to the server, it runs once and then copies of results are sent to the selected recipients. This allows report profiles in the package to be run once, instead of multiple times, on the server.

Report Types

There are two different types of reports in PACE Reporting:

Server-based report with report rule. These reports are sent to the server with a report rule defining their structure. You build these reports via the workspace.

Server-based report without report rule. You build these reports using wizards. These reports do not have a report rule associated with them. The following reports fit into this category:

• Lot Level Reconciliation

• Net Asset Value

• Position Reconciliation

• Trade Reconciliation

Create a Report in Build Reports Mode

Complete the following procedure to create a report in Build Reports mode.

1. In the Reporting Center, in the left navigation pane, click PACE Reporting > General Reporting > General Reporting.
   You see the General Reporting module.

2. The currently selected mode is displayed next to the Components or Reports tab. If you are not in Build Reports mode, select Change Mode from the Configure menu.

3. Open the Reports folder and select Compose.
   You see the Building a new Report window.

   

4. Select the Report Type from the list of available reports.
   If there are any subtypes available for the report, they appear in the Pick a type of Report section of the window.

5. Select the report subtype and click Next.

6. Select existing report components or build new components as you create your report.
   You see the Report workspace.

   

7. In the Report Workspace, click Choose an existing Field Rule to add a field rule to the report. If you do not have access to create database field attributes, this link does not appear. The field rule allows you to select the data or columns to be displayed in the report.
   You see the Existing Field Rules window.

   

8. Filter the field rules to display only your field rules, or all of the field rules owned by your business group. You can also display field according to Name, Owner, Date or Comments.

9. Double-click the field rule you want to add to the report.

10. Select Make a Copy of the Field Rule to ensure that any changes you make to the field rule do not affect the original rule. If you make a copy of the field rule, you are the owner and can alter the field rule as needed. The report inherits the name of the report with the letters FR appended to the end of the name.
    The field automatically populates the columns in the workspace.

11. To add a new field to a report, scroll to the New Field option, and click New Field.
    You see the Adding Field Attributes window.

12. Filter field attributes to display only your fields or all fields. You can display Field Attributes according to Field Name or Comments.

13. To add multiple field attributes to a report, select the check box next to the Field Name. Click Done to populate the columns in the workspace with the specified field attributes.

14. Next, select Choose an existing Source Rule to assign source rules to field types. You can filter source rules to display only your source rules, or all of the source rules. You can sort source rules according to Name, Date, Owner or Comments.
    You see the Choose an Existing Source Rule window.

15. To add an existing source rule to a report, double‑click the source rule you want to add.

16. Select Make a Copy of the Source Rule to ensure that any changes you make to the source rule do not affect the original rule. If you make a copy of the source rule, you are the owner and can alter the rule as needed. The report inherits the name of the report with the letters SR appended to the end of the name. The sources populate the field types selected in the report design. Note that the field rule must be defined for the report before you add the source rule.
    You see field types populated with the source rules.

    

17. Click Show me all Sources to add sources to the report.
    You see the View all sources dialog box.

18. Select sources for all field types, independent of the selected fields, and select OK.
    The selected sources are applied to the fields.

19. Select Specify mandatory Sources for this report to display the field types and available sources that are required for each report type. For example, a holding source is required for position reports. Before saving a report, you must define sources for most field types. If appropriate sources were not defined, you are prompted for the sources.
    You see the Specify the Required Sources dialog box. Refer to the Report Types table below for a list of report types and sources.

20. Select the required sources for the report, and click OK.

21. To add entities and dates to the report, select Choose Entities and Dates for this report.
    You see the Editing an Entity Client Report dialog box.

22. Complete the options on the dialog box as described in the following table and click OK to save your changes.

Report Types

The following table lists report types and required sources.

Add Comments to a Report

You can add comments up to 100 character long to a report on the workspace. Comments are stored in the Comments column on the REPORT_PROFILES table in the PACE_MASTER database. Type comments in the Type your comments here section of the workspace. The report comments are displayed in the Reports Explorer window.

Report Package Comments

Report Package details are displayed on the right. You can drill down into the package to display the underlying reports that make up the package. When working with Report Packages, you can view custom comments in the Report Explorer. You enter custom comments in the Editing the Report Package dialog box.

Add Sources On the Fly

If you do not want to use an existing source, complete the following procedure to add a source on the fly.

1. Select the source under the appropriate field type.
   You see the Sources window.

2. Click the arrow to display a list of holding sources.
   You see a list of holding sources.

3. The Sources window displays all of the available sources for the selected field type, such as holdings. You can select multiple sources for the report to create a hierarchy.

4. Click Done when you are finished selecting sources.

Add Grouping to a Report

Complete the following procedure to add grouping to a report.

1. Click the dropdown next to New Group.
   You see the Grouping window.

2. Add a Simple grouping level, a Range Rule, a Filter Rule or a Classification level to your report on the Grouping window.

Work With Existing Reports

Filter Reports

You can view only the reports you own, or all reports. Complete the following procedure to filter the reports displayed on the Reports tab.

1. From the drop-down list at the far left, select Show me all reports to view all reports.
   You see your reports listed in black and all others are in blue.

2. Below the drop-down list, click the Filter icon to set or remove a filter.
   You see the Filter dialog box.

3. Complete the following fields on the Filter box and click OK to save your changes.

Edit a Report

You can edit existing reports from the Reports Explorer by double-clicking on the report, or by selecting Edit from the right-click or Compose menu. You can edit your own or other user’s reports if permissions have been set up for you to do so in Eagle User Manager.

Copy a Report

You can copy reports from the Reports Explorer by highlighting the report and then selecting Copy from the right-click or Compose menu. All report components are copied, including the underlying rules, scheduling information, and report filters. When you copy a report, you are the owner of the new report even if you did not own or create the original report.

Delete a Report

You can delete reports from the Reports Explorer by selecting Delete from the right-click or Compose menu. You can also highlight the report and click Delete. You can only delete a report if you own it. A warning message appears to confirm that you want to delete the report.

Before deleting the report, PACE runs an impact analysis to ensure the underlying rules are not being used in other Reports. If the underlying rules are used in other reports, the report cannot be deleted.

Rename a Report

You can rename a report from the Reports Explorer by selecting Rename from the right-click or Compose menu. PACE displays a warning message if the new name already exists.

Check Usage of Report Rules

Right-click and select Usage to see an analysis of where the report rule, report profile, field rule and source rule are used. Reports that use range or filter grouping rules also display the report rules to which those grouping rules belong. You can also right-click and edit the component on the fly. This is useful if you need to remove duplicate field attributes.

The Usage of Report dialog box contains the following options.

Additional Entity Options

When working with entities, depending on the report, there are more options available on the Additional Options menu.

Use Entity History

Five tables support Entity History:

• ENTITY_DETAIL_HISTORY

• ENTITY_HIST

• ENTITY_CHARACTERISTICS_HIST

• ENTITY_EXTENSION_HIST

• ENTITY_EXTENSION_DETAIL_HIST

These tables maintain a time series of the data contained in the entity tables. The effective dates for the entity are stored the same way as effective dates are stored for security history. That is, the entity table contains the most recent effective date for the entity while the entity_hist table contains a history of all the data, including effective dates, pertinent to the entity. The Entity Maintenance windows populate these tables whenever changes are made to the entity information.

The reporting engine pulls data from the history tables when reporting from these tables. There is a Show Entity History check box on all profiles that runs this logic. The reporting engine figures out the entities that are in a list based on the history tables if this check box is selected when running for a List. If the check box is not selected, then the ENTITY and ENTITY_CHARACTERITICS tables are used to figure the entities in the List.

Use Entity History to Return NULL Values

You can display NULL values from Entity History records by selecting the Always use most recent data for all Entities checkbox. Select the report rule settings to always use the most recent values for entity data. When you select this option, reports retrieve NULL data to display from the Entity History OLAP tables. If you do not select this option, then data is retrieved from Entity tables that store current data.

Use Entity History to View a Report

You can view an entity’s history through a server-based report, when submitting a report with an override or from Entity Details. Select Use Entity History to run a report using historical data for entities.

• If you run a single period positions report with an effective date of January 1, 2005 and select Use Entity History, the report returns entity data that reflects the entity and entity characteristics as they were on January 1, 2005.

• If you run a report for a specific date and the data for a field in that report is NULL, then PACE finds the next history record where there is data for that field.

• For multi periods reports, as a default, historical entity data reflects the end date. However, you can create an As of Begin Date fields for entity details and entity characteristics. As of Begin Date fields show the historical data on the entity for the begin date of the multi period report.

The other major component of Entity History is the definition of underlying entities in Derived Entities, such as Composites, Aggregates, and Sub-Portfolios. This information is stored in the ENTITY_DETAIL and ENTITY_DETAIL_HISTORY tables. The ENTITY_DETAIL_HISTORY table is used in two major areas:

The Entity Build process uses the ENTITY_DETAIL_HISTORY table to determine the Portfolios to build the Composite as of the Effective Date of the Build.

Reports (Performance Calculations, Trades, Cash, Lot reports) that are run for a Composite run for the underlying Portfolios. When the Show Entity History check box is selected, the ENTITY_DETAIL_HISTORY table is used to find the Portfolios.

History by Entity Details

Complete the following procedure to view history by entity details.

1. From any Eagle window, click the Eagle Navigator button to access the Eagle Navigator.

2. Enter Entities in the Start Search text box.

3. Click the Entities (PACE) (Portfolio Data Center) link to access the Portfolio Data Center.
   You see a list of existing entities.

4. From the list, double click the entity you want to view.
   You see the Editing Entity dialog box.

   

5. Select the Entity Details tab. You can manually insert a date or choose a date from the calendar. The calendar is only active if there is historical data for that entity.

Auto Add Benchmarks

Select this option to automatically add associated benchmark entities to reports. Benchmark entities are predefined entities used to compare existing entities to the benchmark. When a benchmark entity is created, it is associated with existing entities. The associated benchmark is included in the report if you include an existing entity in a report with Auto Add Benchmark selected.

Example Report With Benchmarks Automatically Added

In this example, the EPDP1 portfolio and Auto Add Benchmark option are selected. Therefore, EPDP1 and its associated Benchmark are both included in the report.

Enumerate Composites

You can select Enumerate Composites when a Composite entity is selected for a report. You can explode the composite into its individual underlying entities or run the Composite as a single, unified entity. If you select Enumerating Composites, the report breaks out each underlying fund in the chosen composite and displays it using the selected grouping rule.

PACE supports composite enumeration to the bottom level. For example, if you have a composite of a composite comprised of portfolios, the top-level composite is exploded to the bottom (portfolio) level.

Example Reports with Composites Enumerated

Composite of Composite in the example below is a composite entity that owns another composite, Comp1. In turn, Comp1 owns four portfolios EPDP1, EPDP2, EPDP3 and EPDP4.

The report result displays the data for the lowest level entities—the portfolios.

Treat Clients As Contacts

If you select Treat Clients as Contacts, and then submit a PACE report, the report retrieves information for all entities owned by all clients related to the selected client. If you do not select this option, then the PACE report is run only for entities owned by the client selected in the PACE report profile.

Using List Entity Enumeration

PACE reporting includes business group security logic in the list entity enumeration process. A PACE report that is run for a list entity enumerates the list to determine the entities which meet the specified criteria, and matches those entities against your business group to determine the final set of entities included in the PACE report.

For example, User A in compound Business Group A creates a list entity (List A) and defines the criteria as all entities with an entity type value of Portfolio. User B, who is part of regular Business Group B, runs a report for List A. User B’s report enumerates List A to include all portfolios which are contained in Business Group B. When User A runs this same report, List A is enumerated to include all portfolios that are contained with Business Group A.

This logic applies to reports submitted through PACE or through the Portal, via a report package, and via a codeless exporter.

The List Entity Enumeration function is optimized to improve processing of the list enumeration process when the list falls into specific categories. When a dynamic list entity is built to use entity history and contains criteria from only one database table, or when a dynamic list entity is built with criteria using only database fields (as opposed to entity characteristics), the enumeration process builds a simple SQL statement to resolve the entities contained in the list.

Dynamic lists that are built either with criteria using entity characteristics or that use entity history and contain criteria from more than one database table continue to use the previously existing enumeration process.

Currency Conversion Date Configuration

You can specify which date field are used to retrieve the foreign exchange rates when a PACE report is configured with currency conversion. This applies to multi period reports and trades.

When working with a multi period report or trade report, the Options dialog box displays a Specify Date Types tab which contains different settings based on the PACE report type being edited.

Multi-Multi Period cash activity, multi period cash balance, and multi period positions reports all contain the setting FX Conversion for Cash As Of, which lists all of the field attributes that are defined against the CASH_ACTIVITY, CASH_BAL, and CASH_FLOW_PROJECTION tables. This setting does include internal field attributes that exist for these tables.

Multi period trades and multi period positions reports each contain the setting FX Conversion for Trades As Of, which lists all of the field attributes that are defined against the TRADE table. This setting does include internal field attributes that exist for this table as well.

When either of these settings is populated, and the report is configured to perform currency conversion, the selected date field is used in the currency conversion process. The date returned by the selected field for each record is the date used in the conversion rate fetch against the FX_RATES table. In this way, each record returned by the PACE report could use a separate exchange rate in the conversion process.

Multi Period positions reports that have either of these settings enabled only have adjustment field results impacted. If the report has the FX Conversion for Cash As Of setting enabled, then the results of any Cash Adjustment field use the selected date for its currency conversion. Similarly, if the report has the FX Conversion for Trades As Of setting enabled, then the results of any Trade Adjustment field uses the selected date for its currency conversion. Neither of these settings impacts the results of holdings fields included in the report.

Example Currency Conversion Date Configuration

In the following example the transaction records listed in the table exist for a given account.

The foreign exchange rate records listed in the following table exist in the database.