Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Dictionaries represent the grouping structure of the performance data created by Eagle Performance. They control the way in which Eagle Performance groups and sorts the information that is displayed in reports. The terms dictionary, rollup model, and performance model are used interchangeably.

For information about viewing and editing performance models, see Work with Performance Models (Dictionaries).

If you plan to use the Performance Analysis report to generate results in languages in addition to English, you may also need to load multi-lingual data for Code Values that describe performance model nodes. For more information, see the Performance Analysis and Reporting User Guide.

On this page

Dictionary information is stored in the RULES database which contains the following tables: DICTIONARY, DICTIONARY_FORMAT, DICTIONARY_DETAIL, and BUSINESS_CALENDAR.

DICTIONARIES Table

This table stores the segment definition of the performance model. It contains biographic information, such as the name, owner, source, and type. Performance models all have a type of "P." The following table lists the fields that are used for performance calculations.

Column

Description

DICTIONARY_ID

Stores a unique segment model ID used in the PERF_SUMMARY table.

DICTIONARY_NAME

Stores the name of the segment model.

DICTIONARY_TYPE

Stores the dictionary type. Values include "P," which represents a performance segment model. Otherwise, it is NULL.

Caption name
The following figure shows the DICTIONARIES table.

Dictionaries Table

When the system creates an entry for a performance model in the DICTIONARIES table, it sets the DICTIONARY_OWNER column and the DICTIONARY_OWNER_ID column to a lower case value of either pace_masterdbo (if you use Oracle) or a value of sa (if you use SQL). It assigns these values when it generates a new performance model through running a Performance Calculation report or using the generic Performance data uploader.

The following specific dictionary data tables are used in performance calculations.

DICTIONARY_FORMAT Table

This table stores the performance model segment levels, for example fund, country, sector. The following table lists the key fields that are used in performance calculations.

Column

Description

DICTIONARY_ID

Stores the performance model ID, which joins to the DICTIONARIES table.

DICTIONARY_LEVEL

Stores the dictionary level. Level ID 1 represents the Total Fund level for a performance model. Each row defines the next level of the performance model.

DICTIONARY_LEVEL_DESC

Stores the level description.

The following figure shows the DICTIONARY_FORMAT table.

Dictionary Format Table

DICTIONARY_DETAIL Table

This table provides the detail for each node in the performance model. The following table lists the key fields that are used in performance calculations.

Column

Description

DICTIONARY_ID

Stores the dictionary ID, which links to the PERF_SUMMARY table.

DICT_L1_CODE_VALUE–DICT_L8_CODE_VALUE

Defines each layer of the model.

DICTIONARY_DETAIL_ID

Stores the dictionary detail ID, which is a unique instance.

The following figure shows the DICTIONARY_DETAIL table.

Dictionary Detail Table
 

BUSINESS_CALENDAR Table

This table defines the business days, month, quarter and year-end. The following table lists data for this table.

Column

Description

BUSINESS_DATE

Stores the calendar date.

DAILY_FLAG

Stores the daily flag. Values include:
1 – If the date is business day.
0 – If the date is not.

MONTH_END_FLAG

Stores the month end flag. Values include:
1 – If the date is a month-end.
0 – If the date is not.

QTR_END_FLAG

Stores the quarter end flag. Values include:
1 – If the date is a quarter-end.
0 – If the date is not.

YEAR_END_FLAG

Stores the year end flag. Values include:
1 – If the date is a year-end.
0 – If the date is not.

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.