Create a New Query Report Profile

Creating the query report profile is a one-time action. The administrator can edit the report parameters after the query report profile is created, but changes made by an individual user only affect that user’s query and results. The following procedure summarizes the steps involved in creating a new query report profile. A detailed description of each step of the wizard follows the procedure.

To Create a New Query Report Profile:

From the Performance Center window, click Performance Desk.
In the left navigation pane, click Data Quality Monitor.
You see the Performance Query Tool workspace.
Click the Create link on the toolbar
You see the Step 1 dialog box of the Query Tool wizard.
Define Report Definition by naming the query report profile and selecting the query report view for the query result set. Click Next.
Define Default Profile Parameters such as fields, source rule, frequency, and performance model for the data to be retrieved by the query. Click Next.
Define Profile Access to grant specific Eagle users and/or business groups access to the query report profile. Click Next.
Define Profile Parameters to further define who, among specific Eagle users or business groups with access to the query report profile, has permission to view and edit particular report parameters (for example, fields, source rule, and performance model). These changes do not affect everyone with access to the query report profile. Click Next.
Define Operation Access to define the statistical operations in the query report profile that each user can execute with the data once it is returned.
Click Finish.

On this page

1 Define the Default Report Parameters
2 Define Access to the Query Report Profile
3 Define Access to the Report Parameters
4 Define Access to Query Operations

Step 1 in the Query Tool wizard, allows the administrator to name the query report profile, select a report definition, and enter comments.

To create a query report profile:

In the Profile Name box, enter a name for the query.
In the Select Report Definition area, select the underlying Report Name.
The Report Name defines the view or format of the query result set.
Click Next. You are ready to define the default report parameters for the query report profile.

Query Report Views

There are four possible views for the query results. The following table displays the view parameters.

View	Entities	Fields	Dates	Drill Down	Operations

View	Entities	Fields	Dates	Drill Down	Operations
1	Single	Multiple	Multiple	No	Yes
2	Multiple	Single	Multiple	Yes	No
3	Multiple	Multiple	Single	Yes	Rolling Limits
4	Multiple	Multiple	Single	Yes	Yes

View 1: Single Entity and No Security Level

View 1 allows a single entity only with the results displayed with the time series dates on the vertical axis and the data fields on the horizontal.

Note that you can include benchmarks for an entity by adding a Performance Analysis field set for the desired benchmark, such as Primary Comparison and Secondary Comparison.

View 2: Multiple Dates, Single Field

View 2 allows you to choose multiple entities, multiple dates, and performance model levels down to security for one data field. The results are displayed with the dates on the horizontal axis and the data field grouped by performance model level. No operations are allowed in this view.

View 3: Multiple Entities Single Date

View 3 allows you to choose multiple entities, multiple performance model levels down to security, and multiple fields for a single date. Results of operations are displayed on the horizontal axis. This view is most similar to the Performance Analysis report. Due to the nature of the result set, rolling period operations are limited to one repetition, which is well suited to “to-date” operations like inception-to-date or year-to-date as of the report date.

View 4: Multiple Entities, Dates and Fields

View 4 allows you to choose multiple entities, performance model levels down to security, dates, and fields.

By default, the results are grouped by Entity, each Performance Model level, and the time series of dates. For example, the fund total for each date in the date range, then the Equity Total for each date, then each Equity security for each date. Data and operation fields are displayed on the horizontal axis.

Define the Default Report Parameters

Step 2 in the Query Tool wizard, Define Default Report Parameters, allows the administrator to define the default report parameters for the query report profile. Report parameters specify the performance data that is returned by the query when it is submitted (for example, fields, source rule, performance model, frequency, and so on).

The report parameters are not always known by the analyst or downstream users, so they are set by the administrator as default values. A value is required for all of the default report parameters.

The Define Default Profile Parameters dialog box includes a series of report parameters which you can define. The following sections describe each report parameter.

Currency Conversion

Select a target currency from the list to convert Query Tool values from the entity’s base currency to the specified target currency.

Performance Status Flag

Select a value to show only the performance data that has the status or statuses specified in this field. Options include:

All Records, the default value
Preliminary Only
Final Only
Preliminary Or Final
Not Preliminary Or Final

Fields

Click the ellipsis to the right of Fields to select the fields you want to display on the report. The first field to select, for all report views except view 2, is a field attribute that is pointed to the column Performance end date on the PERF_SUMMARY table in the PERFORM database, as shown in the following figure. In the following figure, the field attribute is named Perf End Date. This field attribute has different names in different environments, but should be found in the Performance folder.

As a general rule, aside from the Performance end date, do not add PERFORM database fields to the report. Instead, add Performance Analysis fields that point to the underlying PERFORM database fields. If you do not see any Performance Analysis fields in the field selector, go to the Map Fields function in the General Reporting area and make these fields available to the performance report. If you do this and still do not see any Performance Analysis fields, select the Show me all Fields option at the top of the field selector.

Next, select the Performance Analysis fields that point to the data you want returned in the query report, as shown in the following figure. Performance Analysis fields are found under the Custom category and are designed to retrieve the single-period data that is stored in the PERFORM database. It is not necessary to select Performance Link Analysis fields because Operations such as linking are done on the fly in the Query Tool. See “Performance Analysis Fields Supported in the Query Tool” for more details on functionality.

Source Rule

The source rules are created in the General Reporting area of PACE, as shown in the following figure. The source rule determines the hierarchy of sources to use when selecting performance data from the database. This means the source used to commit or load the performance data needs to be listed in the Performance category of the Source Rule.

Performance Model

Select a performance model, also known as the performance dictionary. See the following figure. Performance models are created either when you calculate returns in Eagle Performance or via an uploader. The performance model represents the grouping structure of the performance data, such as Fund/Country/Sector or Fund/Coupon Range. If fund and benchmark returns are stored in different models, the default dictionary functionality can retrieve the benchmark returns from a different model.

Frequency

Select the frequency of the single-period returns being queried by select a value from the Frequency list. Options include:

Annual
Daily
Monthly
Quarterly
Weekly
Subperiod (for subperiod returns generated by Significant Cash Flow processing)

Performance Model Level

The Performance Model Levels Selection dialog box displays all the nodes of the Performance model chosen and allows you to choose any combination of nodes that you wish for the query to extract. To include other nodes, for example, Investment Type, select the corresponding Selection check box. The Performance Model Detail button allows you to choose specific levels within the chosen nodes. For example, you can select the Equity returns only within this Entity/Investment Type model.

Entities

Select the default entities for the report. The analyst can be given the ability to override and select their own entities.

Query Date Range

Specify the dates you want used to retrieve the overall time series data from the database.

By default, the query returns the fields requested from the fund inception date to the current date. You can accept or override this default. You can override the default dates in several ways. The following table describes the options in the Date Range Selection dialog box.

Option	Description

Option	Description
Begin Date Options
Offset from End Date	Determines the begin date based on a specified number of periods calculated back from the end date. You can enter a number value and select one of the following options: The Query Tool retrieves the profile entities' and benchmarks' specific entity level business calendar source, if available. Otherwise, it uses the Eagle PACE business calendar. It determines the correct benchmark based on the Use Benchmark History setting in the Query Tool view, along with the portfolio's benchmark Process Across Changes setting. It then goes back the number of days or months depending on the report's frequency based on the business calendar business days or month ends. It uses the earliest effective date of that set of observations as the report’s begin date. The Query Tool retrieves the profile entities' and benchmarks' specific entity level business calendar source, if available. Otherwise, it uses the Eagle PACE business calendar. It determines the correct benchmark while applying the Use Benchmark History setting and the portfolio's Process Across Changes setting. The profile then goes back the requested business days in each business calendar to arrive at the earliest begin effective date. The Query Tool retrieves the profile entities' and benchmarks' specific entity level business calendar source. Otherwise, it uses the Eagle PACE business calendar. It determines the correct benchmark while applying the Use Benchmark History setting and the portfolio's Process Across Changes setting. The profile then goes back the requested month ends on each business calendar to arrive at the earliest begin effective date. The Query Tool retrieves the profile entities' and benchmarks' specific entity level business calendar source. Otherwise, it uses the Eagle PACE business calendar. It determines the correct benchmark while applying the Use Benchmark History setting and the portfolio's Process Across Changes setting. The profile then goes back the requested quarter ends on each business calendar to arrive at the earliest begin effective date. The Query Tool retrieves the profile entities' and benchmarks' specific entity level business calendar source. Otherwise, it uses the Eagle PACE business calendar. It determines the correct benchmark while applying the Use Benchmark History setting and the portfolio's Process Across Changes setting. The profile then goes back the requested year ends on each business calendar to arrive at the earliest begin effective date.
Begin Date	Determines the begin date based on the specified date.
Predefined Date	Determines the begin date based on a predefined date that uses a Range Type and a specified entity date field. Range Type options include: Inception to Date. If the report includes only Performance Analysis fields for the fund, the Query Tool uses the earliest fund inception date. However, if the report includes benchmark Performance Analysis fields, the Query Tool determines the correct benchmark based on the Use Benchmark History setting in the Query Tool view, and identifies the portfolio's benchmark Process Across Changes setting to determine the inception date, as follows. If the: Use Benchmark History check box is selected and the Process Across Changes check box is selected, the report uses the earliest fund inception date as the report’s begin date. Use Benchmark History check box is selected and the Process Across Changes check box is cleared, the report identifies the earliest fund inception date and the report end date benchmark’s inception date. It uses the earliest date as the report’s begin date. Use Benchmark History check box is cleared and the Process Across Changes check box is either selected or cleared, the report identifies the earliest fund inception date and the current date benchmark’s inception date. It uses the earliest date as the report’s begin date. Fiscal Year to Date. The Query Tool uses the entity level business calendars for each portfolio and benchmark for the previous fiscal year end. It uses the earliest effective date as the report's begin date. Year to Date. The Query Tool uses the entity level business calendars for each portfolio and benchmark for the previous year end. It uses the earliest effective date as the report's begin date. Quarter to Date. The Query Tool uses the entity level business calendars for each portfolio and benchmark for the previous quarter end. It uses the earliest effective date as the report's begin date. Month to Date. The Query Tool uses the entity level business calendars for each portfolio and benchmark for the previous month end. It uses the earliest effective date as the report's begin date.
End Date Options
Date Rule	Determines the end date based on the specified Date Rule.
End Date	Determines the end date based on the specified date.
Entity Termination Date	Determines the end date based on the specified entity termination date field.

Remember that this range defines the outer limits of the query and provides all the raw data required for subsequent operations, such as linking. For example, if you are always going to want the last 12, 6, and 3 months of returns linked, the Query Date Range needs to encompass the 12-month period and the individual operations define each of the linking subperiods. Note the Query Tool is designed for quick analysis. It is not designed to handle large volumes.

If you are defining the query date range for View 3, a single date view, ensure that the begin date and end date are the same. You can use a time range or a single date.

Show Business Days Only

The Show Business Days Only check box determines whether the query only displays returns for dates marked as business days in the Business Calendar applied or if the query shows all committed performance within the query’s date range, including both business and non business days. This option is selected by default, but you can clear it. If the check box is:

Selected: The query shows results for all business days, even when no performance is committed for those days. This option is selected by default, and provides backwards compatibility. The Query Tool uses the entity level business calendar for the profile portfolio or benchmark, if available, to identify business days. Otherwise it uses the Eagle PACE business calendar.

If the report identifies business days for benchmarks, the Query Tool determines the correct benchmark based on the Use Benchmark History setting in the Query Tool view, and identifies the portfolio's benchmark Process Across Changes setting, as follows. If the:

Use Benchmark History check box is selected and the Process Across Changes check box is selected, the report uses the entity level business calendar for each profile portfolio, if available, to provide the business days. Otherwise it uses the Eagle PACE business calendar. In addition, it chooses the historical benchmarks for each time frame within the report period and then chooses the correct business days for each benchmark, using the appropriate entity level business calendar, if available. Otherwise, if no entity level business calendar is available for the benchmark, the Query Tool uses the Eagle PACE business calendar to provide business days for that assignment’s time period. It then combines these historical benchmarks’ business days with the portfolios’ business days for the total range of business days. Note that for View 3, a single date report; the date shown is the closest business day prior to the report end date, if the report end date is not a business day.

Use Benchmark History check box is selected and the Process Across Changes check box is cleared, the report’s benchmarks are the assignments as of the end date of the report time range. The Query Tool uses the entity level business calendar for each profile portfolio and benchmark, if available, to provide the business days. Otherwise it uses the Eagle PACE business calendar. The results reflect all the days.
Use Benchmark History check box is cleared and the Process Across Changes check box is either selected or cleared, the report uses the current day assignments for the entity and benchmarks. The Query Tool uses the entity level business calendar for each profile portfolio and benchmark, if available, to provide the business days. Otherwise it uses the Eagle PACE business calendar. It displays the combination of these days on the view's results.

Cleared: The query returns results for all days with performance data committed in the selected date range within the given parameters of the report. This process does not use business calendars. It includes business days for both profile entities and benchmarks. You can use this option to help identify scenarios whether returns were committed in error to a particular day.

The following table describes how the Show Business Days Only check box setting you choose affects your query results for each available Query Tool view.

View	Results Display	Show Business Days Only Check Box Selected (Default)	Show Business Days Only Check Box Cleared

View	Results Display	Show Business Days Only Check Box Selected (Default)	Show Business Days Only Check Box Cleared
1	Multiple dates	Displays all business dates in date range. For dates with no performance, displays a blank row.	Displays all dates with performance in date range, including business days and non business days. For dates with no performance, returns no results.
2	Multiple dates	Displays all business dates in date range. For dates with no performance, displays a blank column.	Displays all dates with performance for all entities in date range, including business days and non business days. For entities with no performance on a date, displays a blank.
3	One date	If you define View 3, a single date view, and define the query date range with a: Single date, the Query Tool checks each portfolio and benchmark to determine if the single date occurs on any of the entity level business calendars, if available, associated with the portfolios or benchmarks. Otherwise it uses the Eagle PACE business calendar. It the single date is present on any of the business calendars, the report shows a row for any data from that effective date. If the single date is not a business date, the report displays an error. Date range, the Query Tool checks each portfolio and benchmark to determine if the end date of the date range occurs on any of the entity level business calendars, if available, associated with the portfolios or benchmarks. Otherwise, it uses the Eagle PACE business calendar. If the end date of the date range is not present on any business calendars, the report goes backwards one day (or one month, if you use that frequency) at a time until it finds a business day in any of the relevant business calendars. It displays that effective date in the view results.	Displays one date. If the end date of the query’s date range has performance, displays results for that day. If the end date of the query’s date range has no performance, displays a blank row for that day.
4	Multiple dates	Displays all business dates in date range. For dates with no performance, displays a blank row.	Displays all dates with performance in date range, including business days and non business days. For dates with no performance, returns no results.

Use Benchmark History

The Use Benchmark History check box determines whether Performance Analysis fields in the query that report on benchmarks reflect changes in the entity’s benchmark assignments over time. This option is cleared by default, but you can select it. If the check box is:

The query reads the benchmark history for the report time period. This enables the query to link data across any benchmark changes during the date range. This behavior, called Processing Across Changes, eliminates the need to maintain a Linked Custom Benchmark to splice benchmark changes across performance history.

Additional setup for entities is needed when you use this approach. If the Process Across Changes check box is selected for that benchmark assignment, then benchmark changes throughout the report’s date range are used for the applicable period in which it was assigned. If the Process Across Changes check box is not selected, then the system uses only the benchmark assignment from the report’s end date for the entire date range. For more information, see “Benchmark Assignment History Support.”

(Default) The query uses the current benchmark assigned to the entity and applies only that benchmark’s data to the entire date range of the report regardless of benchmark assignment changes.

All of the default report parameters are required. If you do not specify values for one or more of the report parameters, an error message appears when you click Next. You can grant users the ability to override the defaults via subsequent dialog boxes in the Wizard. Click Next to define access to the query report profile.

Define Access to the Query Report Profile

Step 3 in the Query Tool wizard, Define Profile Access, allows the administrator to grant PACE users or business groups access to the query report profile, as shown in the following figure. Only users granted access are able to view the query report profile when they log into PACE. This step is most like publishing a report profile in the General Reporting area of PACE.

There are two sections on this dialog: Users and Business Groups. In the Users section, you can grant access to all users by selecting the DEFAULT_USER. Or select individual users and entire business groups. Click Next to define access to the report parameters.

Define Access to the Report Parameters

Step 4 of the Query Tool wizard, Define Profile Parameters, allows the administrator to grant PACE users and business groups access to view and edit report parameters.

By default, all users who are granted access to the query report profile have access to view and edit the following report parameters: Entities (select from any funds they have access to) and the Query Date Range.

You can change the default using the following options:

Select All. This option allows all users with query report profile access the privilege of viewing and editing all of the report parameters.
Clear All. This option removes access to report parameters for all users with query report profile access.

To edit a report parameter for one or all of the users with access to the query report profile, click the ellipsis next to the report parameter. This allows you to assign different privileges to several groups and individuals. You can also remove report parameters that might not be familiar or cause the users confusion. For example, if you do not grant a user access to the source rule, it does not appear for that user.

It is not necessary to grant a user access to the Query Date Range parameter in order for them to specify the time period for an operation. For example, if the Query Date Range is inception-to-date, the user can take a series of monthly returns and create an inception-to-date return and quarterly returns. If the Query Date Range is year-to-date, the user can define the time periods within the year. The Query Date Range parameter defines the overall time period for the data series on which the operations are performed.

You do not have to grant users the ability to view or edit any of the report parameters. The query runs as defined by the defaults every time. After defining access to the report parameters, click Next to define what the user can do with the data once it is returned in the report.

Define Access to Query Operations

Step 5 of the Query Tool wizard, Define Operation Access, allows the administrator to define access to certain operations such as geometric compound rolling and standard deviation. In the previous step, the administrator gave the user access to submit the query report profile with its default settings, which includes the ability to edit the entities and date range of the query. By default, the Query Tool is going to return two time series, one for each of the fields selected, Fund and BR.

The Define Operation Access dialog lets you specify which operations each user can perform on the query results. Specifying this access allows the users to define the operations themselves. The operations do not appear in the result set the first time the query is submitted.

By default, users do not have access to any operations. The Select All option grants access to all of the operations listed to all of the users with access to the report query profile. If you select a check box such as Rolling Operations or Series Derivation Operations, you can grant all users with query report profile access the ability to perform all Rolling or Series Derivation Operations in a single click. Otherwise, you can grant access to any one operation to all users and groups by selecting the check box in the Access column.

By clicking the ellipsis next to any operation, you can allow one or more individuals or business groups access to that operation. In this way, you can give different access to many users and groups in one dialog. Enabling or securing access to the operations is the last step in setting up a new query report profile. Click Finish to create the query and make it visible to all users with access when they log into PACE.