Field Attributes types include Regular and Derived. Derived field attributes are fields based on Regular field attributes. Field attributes are stored in the RULES database in the FIELD_ATTRIBUTES table by Business Group and User. Use Field Attributes to:
Customize the name of each column where data is displayed.
Link a reference code to the field attribute, so short descriptions can be translated to more descriptive values when they are displayed in a report.
Choose the number of decimal places to display for each numerical field.
Assign field attributes to be available for specific report types.
Use source-specific fields.
| Info |
|---|
Fields with ID numbers between 101—999 are reserved for internal use. |
Field Attributes Explorer
The Field Attributes Explorer is located in the PACE General Reporting module. You create Field Attributes via the Field Attributes Explorer in Component Mode. On the Components tab, open the Fields Folder to display all of the available field types.
On this page
| Table of Contents | ||
|---|---|---|
|
Explorer Layout
You can customize the layout of the Explorer. Select Layout from theField Attributes menu. On the Layout dialog box, you can add or remove individual fields to display in the Field Attributes Explorer.
Fields Attributes Right-Click Menu
The options on the right-click menu are described in the following table. If you do not own the selected field attributes, some of the options described in the table may not appear.
Option | Description |
New | Creates a new field attribute. Type. Select a field type to build. Options include Regular Field, Advanced Field, Entity Build Field and Mutual Fund. |
Edit | Edits an existing Field Attribute. |
Copy | Copies an existing Field Attribute. |
Rename | Renames an existing Field Attribute. |
Transfer Ownership | Transfers ownership of an existing Field Attribute. |
View | Allows you to view the Field Attribute even if you do not have permission to edit it. |
Show History | Displays history of the field, including who last modified it and when it was modified. |
Usage | Displays how and where a field attribute is used throughout PACE. The Usage of Field dialog box displays the Field Rules, Simple Grouping Rules, Range Rules and Filter Grouping Rules where the selected field attribute is used. This dialog box also includes the Custom Fields, Report Profiles, Source Rules, and Classifications sections. The usage function includes information on components from the Best Data, Pricing Center, and Composite Security functions. The following sections may appear in this dialog box: Dependent Custom Fields. Lists any Custom Field that have been built upon and include the selected Field Attribute. For example, if the database field Market Value is selected, this section lists a Rollup field which has been created to give a Sum value of the Market Value field. This section lists Custom Fields of all types if they include the selected Field. Dependent Report Profiles. Lists any PACE Report Profiles that directly include the selected Field Attribute. For example, if a single period Security report was built with criteria defined against the Investment Type Field Attribute, the Usage of Field dialog box for the Investment Type Field Attribute lists the Security report profile in this section. Dependent Source Rules. Lists any Source Rules that include the selected Field Attribute within the Source Override section of the Source Rule. For example, if a Source Rule was created to fetch Bloomberg prices for Equity securities, and JJ Kenny prices for Municipal bonds, and this override was defined using the Investment Type Field Attribute, this section lists this Source Rule when the Investment Type Field Attribute is selected. Dependent Classifications. Lists any Classifications or Dictionaries that were built against the selected Field Attribute. For example, if a Dictionary was built to define a Region and includes the Field Attribute Issue Country in the Dictionary level translation, then this section lists the Region Dictionary. |
Find on Page | Locates a field attribute in the Field Attributes Explorer. |
Lock | Locks columns in the Field Attributes Explorer to make viewing of Field Attribute details easier. |
Layout | Determines the columns to display in the Field Attributes Explorer on the Layout dialog box. The Available Columns section lists the columns that are defined against the RULESDBO.FIELD_ATTRIBUTES table. To customize the selector layout:
|
Map Fields | Maps field attributes to a specific report type. Select the report type for which to view the available fields. The right column displays the Field Types and the left column displays the fields enabled for the report type. You can make certain special, internal field attributes available for reporting purposes. These include iReport Level and iReport Effective Date. These fields can be used in a report if they are added to the report type via Map Fields. |
Map Field Types | Maps field types to a specific report type. |
Prints the field attributes in the selected field type. | |
Migration | Provides access to migration options. |
Create Field Attributes
You can create different kinds of field attributes, including Regular, Advanced, Entity Build and Mutual Fund.
Create a Regular or Advanced Field Attribute
Complete the following procedure to create a new regular field attribute.
In Eagle PACE, open the General Reporting module.
Select the Components tab.
Open the Fields folder, and click New.
You see the New Regular Field dialog box.Select Regular Field or Advanced Field from the Field Type drop down. Complete the following fields and then click OK to save your changes.
Option | Description |
Name | Enter the name of the column as you want it to display in a report. The name is displayed in all reports that include this field attribute. If you use a name that already exists, you are prompted to enter a different name. |
Comment | Enter a comment that appears when you are choosing a field to add to a report. For example, a comment could include a description of the data it points to and a reason for creating the field attribute. These comments are displayed for each field attribute in the Field Rule window during the design phase of a report. |
Precision | Sets the decimal position on Number fields. Select the number of decimal places to display in a report. Precision is set to 2 by default. |
Do not allow others to edit this field | Select this checkbox if you do not want to allow other users to edit this field. |
Underlying Type | |
Underlying Process | |
Benchmark Definition | |
Field Options | The following field options are available for a Regular and Advanced field attribute:
|
Attributes |
|
This example shows the settings and options used to create a character-numeric field that converts numeric ratings to alpha ratings. In this example:
There are two columns used to store ratings in the SECURITY.DBO.RATINGS table: NUMERICAL_RATING and ALPHA_RATING. Eagle usually receives rating data from a vendor as an Alpha character, such as AAA for a Moody Rating. Each uploader takes this value and duplicates it so that there are two fields representing the rating. The original field is sent in its native form and stored in the ALPHA_RATING column. The duplicate is sent through a Code Translation which converts the Rating to a numerical Value (such as AAA converts to 99). The result of the translation is stored in the NUMERICAL_RATING column.
NUMERICAL RATING is a float field used to store the numerical interpretation of a rating. This is used to do any mathematical calculation on ratings, for example, Weighted Average Rating.
ALPHA_RATING is a character field used to store the actual rating, for display purposes only.
To set up a field attribute to be used in a Weighted Average, use the following settings in the New Field dialog box:
Option | Setting |
Name | Enter a name for the field. |
Comment | Enter a descriptive comments for the field. |
Numeric Precision | Leave this field empty. |
Type | Select Database. |
Database | Select SECURITY. |
Table | Select RATINGS. |
Column | Select NUMERICAL_RATING. |
Source | If you set this value, you pull only the ratings represented by the source selected. The Rating component of the Source Rule is ignored. If this value is left as NULL, then the source is determined by the order specified in the Rating category of the Source Rule. |
Field Type | Select Character. |
Translation Code | This is the code in the Eagle PACE source that has the numerical value in the Short Description, and the alpha value in the Long Description. |
Work With Entity Build Field Attributes
Entity Build Field Attributes are required to run the Entity Build Process. These field attributes can be defined against Position level tables as well as Position Detail level tables.
Tables and Fields Supported for Entity Field Attributes
Tables currently supported by the engine are:
Position Level. These tables are driven by Position_id:
POSITION
POSITION_NAV
POSITION_SUMMARY
Position Detail Level. These tables are driven by Position_id and Position_detail_id:
DERIV_POS_DETAIL
POSITION_COST_DETAIL
POSITION_COST_DETAIL_USER
POSITION_DETAIL
POSITION_INCOME_DETAIL
REAL_ESTATE_INCOME_DETAIL
REAL_ESTATE_POSITION_DETAIL
By default, the Entity Build engine populates the following POSITION table fields. Any Entity Build field attributes created against these fields are used instead of the engine default:
POSITION.NUMBER_OF_ISSUES. Stores the count of records in the position_detail table for the position_id being processed.
POSITION.TOTAL_MARKET_VALUE. Stores the sum of values from position_detail.market_value for the position_id being processed.
POSITION.TOTAL_MARKET_VALUE_INCOME. Stores the sum of values from position_detail.market_value_income for the position_id being processed.
POSITION.TOTAL_PAR_VALUE. Stores the sum of values from position_detail.share_par_value for the position_id being processed.
POSITION.TOTAL_LOCAL_MARKET_VALUE. Stores the sum of values from position_detail.local_market_value for the position_id being processed.
POSITION.TOTAL_ACCRUED_INCOME_LOCAL. Stores the sum of values from position_detail.accrued_income_local for the position_id being processed.
POSITION.TOTAL_ACCRUED_INCOME. Stores the sum of values from position_detail.accrued_income for the position_id being processed.
Create a Regular Entity Build Field Attribute
A Regular Entity Build field attribute is used to define fields from Position Detail level tables. To create a new Entity Build field attribute:
In the Field Attributes Explorer, right-click and select New.
You see the New Regular Field dialog box appears.Select Entity Build Field from the Type drop down menu.
You see the New Entity Build Field dialog box.
Complete the following fields in the New Entity Build Field dialog box and click OK to save your changes.
| Info |
|---|
Creating a Regular Entity Build field attribute against a Position level table causes the Entity Build engine to fail. Advanced Entity Build field attributes are required for processing Position level tables. |
Option | Description |
Name | Enter the name of the column as you want it to display in a report. The name is displayed in all reports that include this field attribute. If you use a name that already exists, you are prompted to enter a different name. |
Comment | Enter a comment that appears when you are choosing a field to add to a report. For example, a comment could include a description of the data it points to and a reason for creating the field attribute. These comments are displayed for each field attribute in the Field Rule window during the design phase of a report. |
Precision | Sets the decimal position on Number fields. Select the number of decimal places to display in a report. Precision is set to 2 by default. |
Do not allow others to edit this field | Select this checkbox if you do not want to allow other users to edit this field. |
Field Options | The following field options are available for a Regular and Advanced field attribute:
|
Attributes |
|
Create an Advanced Entity Build Field Attribute
An Advanced Entity Build Field Attribute is used to define fields from Position level tables. These tables are driven by Position_id. To create a new Advanced Entity Build Field Attribute complete the following procedure.
In the Field Attributes Explorer, right-click and select New.
You see the New Regular Field dialog box appears.Select Advanced Field from the Type drop down menu.
You see the New Advanced Field dialog box.
Complete the following fields in the New Advanced Field dialog box and click OK to save your changes.
Option | Description |
Name | Enter the name of the column as you want it to display in a report. The name is displayed in all reports that include this field attribute. If you use a name that already exists, you are prompted to enter a different name. |
Comment | Enter a comment that appears when you are choosing a field to add to a report. For example, a comment could include a description of the data it points to and a reason for creating the field attribute. These comments are displayed for each field attribute in the Field Rule window during the design phase of a report. |
Precision | Sets the decimal position on Number fields. Select the number of decimal places to display in a report. Precision is set to 2 by default. |
Do not allow others to edit this field | Select this checkbox if you do not want to allow other users to edit this field. |
Field Options | The following field options are available for a Regular and Advanced field attribute:
|
Attributes |
|
Create a Mutual Fund Field Attribute
Mutual Fund Field attributes are background fields which support Dynamic Mutual Fund custom fields. Dynamic Mutual Fund fields rely on Regular field attributes from the NAV table and Tax Rate Field attributes. Mutual Fund Field Attributes can only be built off columns in the NAV table on the Holding database. Complete the following procedure to create a New Mutual Fund Field Attribute.
In the Field Attributes Explorer, right-click and select New.
You see the New Regular Field dialog box appears.Select Mutual Fund from the Type drop down menu.
You see the New Mutual Fund Field dialog box.
Complete the following fields in the Mutual Fund Field dialog box and click OK to save your changes.
Option | Description |
Name | Enter the name of the column as you want it to display in a report. The name is displayed in all reports that include this field attribute. If you use a name that already exists, you are prompted to enter a different name. |
Comment | Enter a comment that appears when you are choosing a field to add to a report. For example, a comment could include a description of the data it points to and a reason for creating the field attribute. These comments are displayed for each field attribute in the Field Rule window during the design phase of a report. |
Precision | Sets the decimal position on Number fields. Select the number of decimal places to display in a report. Precision is set to 2 by default. |
Do not allow others to edit this field | Select this checkbox if you do not want to allow other users to edit this field. |
Field Options | The following field options are available for a Regular and Advanced field attribute:
|
Attributes |
|
Work with Field Attributes
You can edit, copy, or delete a field attribute as described in the following table.
Option | Description |
Edit | The System Administrator sets permission to edit your own or other user’s field attributes. To edit a field attribute from the Fields Attribute Explorer:
The Editing Field dialog box appears. Make any necessary changes on this dialog box and click OK. |
Copy | To copy a field attribute from the Field Attributes Explorer window:
|
Delete | To delete a field attribute from the Field Attributes Explorer window:
Click Yes to confirm that you want to delete the field attribute. A warning message appears. Select the Yes, I want to delete the field checkbox and then click OK to delete the field attribute. If the Field Attribute is used in a Field Rule, Simple Grouping Rule, Filter Grouping Rule or Range Grouping Rule you cannot delete the field attribute. |
Rename | Right-click and select Rename to rename an existing field attribute. The Rename Field dialog box appears. Enter the new name in the Rename as field and click OK. |
Transfer Ownership | Assigns a Field Attribute to a user. You can only transfer ownership of a Field Attribute to another user if you own it. To transfer ownership:
|
Maintaining Associations
The relationship between Field Attributes and Business Groups is maintained in the database table GROUP_FIELDS. The structure of this table is described in the following table.
Column | Description |
INSTANCE | Unique record identifier |
PUBLISHED_TO_ID | The GROUP_ID value from the PACE_USER_GROUPS table, or the INSTANCE value from the PACE_USERS table |
FIELD_ID | FIELD_ATTRIBUTE_ID value from the RULESDBO.FIELD_ATTRIBUTES table |
PUBLISH_TYPE | The level at which the Field Attribute has been published. G = Business Group, U = User |
UPDATE_DATE | The date and time that the record was updated |
UPDATE_USER | The User who created/modified the association between the Field Attribute and the Group or User |
The relationship stored in the GROUP_FIELDS table is established when you create or publish field attributes. The Report Rule, Field Rule, Report Profile, Source Rule (which can contain Field Attributes through a Source Override), and Dictionary Publish functions also generate GROUP_FIELDS records.
A GROUP_FIELDS record with a PUBLISHED_TO_ID value of –1 is generated when you create a field attribute. This record indicates that only the field attribute owner has direct access to the field. Other users with privileges to edit other’s field attributes can also see this field. When the field attribute is published to other Users or Business Groups, additional records are generated in the GROUP_FIELDS table.
Field Attributes in Reporting
This section describes how to manage field attributes used in reporting.
Regular Mode Field Selector Buttons
Use the available buttons to edit field attributes. Buttons in the Field Selector in Regular Mode include:
Button | Description |
New | Create a New Field Attribute |
Edit | Edit an Existing Field Attribute |
Copy | Copy a Field Attribute |
Delete | Delete an Existing Field Attribute |
Usage | Check Usage on a Field Attribute |
View | View an Existing Field Attribute |
Find | Find a Field Attribute |
Usage | Customize the layout of the Field selector |
Determine the Data Source for Single-Period Reports
An example of field attributes for Single-Period Reports (one date) is displayed below.
Database fields point directly to the column in the database:
Security Fields from Composite Tables, such as Investment Type or CUSIP. Displays information from either the composite security tables or historical security tables.
Composite Tables. Displays data from these tables if no source is specified in the report.
Historical Tables. Displays data from these tables if a source hierarchy is specified in the report.
Holding Fields, such as Quantity or Market Value. Uses a source hierarchy in the report to specify the source.
Time-Series Security Fields, such as Price. Uses a source hierarchy in the report to specify the source.
Security database fields are source-specific, such as Price-BB or Price-IDC. These fields point directly to a source in the database.
| Info |
|---|
Most fields in a report display information based on the source rule in the report. However, you can create source-specific fields for security, price, ratings, analytics, and issuer information. These fields always use the source specified in the field attribute definition, instead of allowing the user to specify the source in the report. This is useful for comparing similar fields from different sources. |
Create a Field for a Multi-Period Position or Security Report
Position multi-period reports display all of the positions held for the entities selected for the two dates specified. Security multi-period reports display all of the securities information for the securities selected for the two dates specified.
These multi-period reports should contain specific fields for the Start Date and the End Date for each field in the report.
Creating these fields is similar to creating a database field attribute; except these fields are associated with the start date or end date of a report.
Market Value Start Date | Market Value End Date | Quantity Start Date | Quantity for Date | |
Position 1 | $1,000 | $900 | 10 | 10 |
Position 2 | $5,000 | $5,500 | 100 | 100 |
Position 3 | $2,000 | $4,000 | 1,000 | 2,000 |
The Market Value Start Date and the Quantity Start Date display the values as of 12/31/11. The Market Value End Date and Quantity End Date display the values as of 1/31/12.
| Info |
|---|
Multi-period trades reports include all of the data between the dates specified. They use basic database fields, not advanced fields. |
Determine Data Source for Multi-Period Reports
This example shows a field attribute named YI‑Quantity Start Date used in position multi-period reports. It points to the quantity column in the database, but it is also configured to point to the beginning date used in the position multi-period report.
The following example shows Field Attributes for position multi-period or security multi-period reports (display data for two dates instead of one).
Database Fields. These fields point directly to a column in the database
Security Fields from Composite Tables, such as Investment Type or CUSIP. Can display information from either the composite security tables or historical security tables.
Composite Tables. Displays data from these tables if no source is specified in the report.
Historical Tables. Displays data from these tables if a source hierarchy is specified in the report.
Advanced Holding Fields, used in a multi-period position report, such as MV Start, MV End, or Quantity Start. From the Holding database, each field is associated with either the start date or end date of the report.
| Info |
|---|
Use a source hierarchy in the report to specify the source. You can also make these fields source-specific by selecting a source in the definition of the field attribute. However, if a multi-period, source-specific holding field is used in a given report, then all other holding fields in that particular report must be source specific. |
Advanced Security Fields, used in a multi-period security or multi-period position report, such as Price Start or Price End. From the Security database, each field is associated with either the start date or end date of a report. Security fields include core security fields, price fields, ratings fields, or analytic fields.
Advanced Security Fields from Composite Tables, such as Investment Type Start or Cusip Start. May display information from either the composite security tables or historical security tables.
Composite Tables. Displays data from these tables if no source is specified in the report.
Historical Tables. Displays data from these tables if a source hierarchy is specified in the report.
Advanced Security Fields from Time Series Tables, such as Price Start or Ratings End. Uses a source hierarchy in the report to specify the source.
Source-Specific Advanced Security Fields, such as Price Start-BB, Price Start-IDC, Price End-BB, or Price End-IDC. Points directly to source in database.
| Info |
|---|
Most fields in a report display information based on the source rule in the report. You can also create source-specific fields for security, price, ratings, analytics, and issuer information. These fields always use the source specified in the definition of the field attribute, instead of allowing the user to specify the source in the report. This is useful for comparing similar fields from different sources. |
Display Data for Two Dates
To display data for two dates, you set up field attributes for Position Multi-Period or Security Multi-Period Reports.
Database Fields. These fields point directly to column in database, and are set up so that Type is Database, and Source is NULL.
Advanced Holding Fields, used in a multi-period position report. From the Holding database, each field is associated with a start date or end date of the report. Report settings include:
Option | Setting |
Type | Advanced |
Process | Begin Date Holding or Entity to display information associated with start date of report, or End Date Holding or Entity to display information associated with end date of report. |
Indicator | User-defined for all advanced holding fields. |
Source | Select a source to make these fields source-specific. However, if a multi-period, source-specific holding field is used in a given report, then all other holding fields in that particular report must be source-specific. |
Report Settings
Advanced Security Fields, to be used in a multi-period security or multi-period position report. From the Security database; each field is associated with the start date or end date of a report. Security fields include core security fields, price fields, ratings fields, or analytic fields. Report settings include:
Option | Setting |
Type | Advanced |
Process | Begin Date Price, Rating, Analytic, Security (to display information associated with start date of report) or End Date Price, Rating, Analytic, Security (to display information associated with end date of report). |
Indicator | Select the appropriate indicator. |
Advanced Security Fields | Security |
Advanced Price Fields | Price |
Advanced Ratings Fields | Rating |
Advanced Analytic Fields | Analytic |
Source | Select a source to make one or more of these fields source‑specific. |
Create As of Begin and End Dictionary Fields
You can create Dictionary fields that use either the begin or end effective date of the reporting period when included in a multi-period PACE reports. This allows Dictionary fields to consider Security history tables and records, and allows reports to display changes in a Dictionary from one day to the next.
The Classification Field maintenance window includes a Process section. The Begin Date Price, Rating, Analytic, Security or End Date Price, Rating, Analytic, Security setting can be populated to instruct the Dictionary field to be run against the begin or end effective date of the report, respectively. The fields can also be included in single period reports, and the Process definition will not affect the contents of the field.
Any existing Dictionary fields created in earlier versions of PACE default to a Process setting of End Date Price, Rating, Analytic, Security, since the reporting engine defaulted previously to the end date of the report when analyzing a Dictionary field.
Maintaining Detail Calculation Fields
On the Detail Calculation field maintenance window, the keypad and data entry field will now work the same with respect to their treatment of numeric and string values.
If the field compared within the Detail Calculation is a text field, then the entry entered via the keypad or via the data entry window will be saved as a string value within the field definition.
If the field compared within the Detail Calculation is a numeric field, then the entry entered via the keypad or via the data entry window will be saved as a numeric value within the field definition.
Edits are available in the Check feature to make sure the correct data type is being entered to be compared against the selected field. These edits will check for string, numeric and date fields to make sure they are compared to a corresponding value.
The data type of the field result will depend on the data type selected for the custom field. This is chosen from the Change Field Type window, which is available via the Field Options link. The available data types are Decimal, Character, Date, and Character Numeric. If the Detail Calculation is configured to have a data type of Decimal, the Precision of the field can also be selected.