...
From the General Reporting module, select the report type you want to use in the Grouping Rules folder in tree view.
Right-click and select New.
You see the New Range Grouping Rule dialog box.In the Name field, enter a name for the rule.
In the Comments field, enter an optional comment about the rule.
Click to populate the field details with the Quartile Rank field.
Double-click the text box under Range Title, and enter Rank 1
Double-click the text box under Range, select the = operator and enter the value 1.
Repeat steps 6 and 7 for the remaining three ranks, Rank 2, Rank 3, and Rank 4.
You see the Edit Range Grouping dialog box displaying the new range grouping rule.
The following example shows a sample report with range grouping in place.
...
From any Eagle window, click the Eagle Navigator button to access the Eagle Navigator.
Enter Codes in the Start Search text box.
Click the Codes(System Management Center) link to access the Codes window.
You see the Codes window.From the Codes module, select the Field Category Code and add new code values. The short description holds a number and the long description holds the actual description, as follows:
Short description of 1 = Long description of “Accounting Data”
Short description of 2 = Long description of “Performance Measurement Data”
Short description of 3 = Long description of “Holdings Data”
Short description of 4 = Long description of “Security Master Data”
Short description of 5 = Long description of “Shared Data”Open the Field Attributes module, under the Metadata category.
Assign a category to each field attribute. From the workspace, select just one grouping, or create a tree so that one grouping is designated as a main category and then one or more other categories are added as subgroups.
...
To customize the display, click Customize.
...
Field Selector With Customize Option
You see the Customize Field Grouping dialog box.
...
Select as many groupings as you want to create the grouping tree. Click OK
...
to save your changes.
The resulting view is displayed in all other field rules until it is changed. If a field attribute is not assigned to a category, it appears under the category Unknown.The field rule view is saved in the registry in the section HKEY_CURRENT_USER > Software > EagleSystems > Clients > EaglePACE > Settings > FieldsCtrlGroups. Category=Setting of 1, Indicator=Setting of 3, Database=Setting of 2 and Table=Setting of 4. This registry setting applies to the user.
Benchmark Comparison Fields
...
You can set benchmark definitions on the Holding Field Attribute and Entity Field Attribute Maintenance windows, using the Benchmark Definition option.
...
Editing Regular Field Dialog Box Benchmark Definitions
...
Use the Benchmark Definition setting to create a field attribute that retrieves data from the benchmark entity associated with the entity that is selected in the report that contains this field.
This setting lists the long descriptions of the code values that exist for the internal code IBMARKDEF.
This setting also lists the option Profile Portfolio, which is the default setting.
When Profile Portfolio is selected, the field retrieves data from the entity selected in the report profile.
When a value other than Profile Portfolio is selected, the field retrieves data from the corresponding benchmark that is associated with the entity selected in the report profile.
If a benchmark is selected and the entity in the report does not have a corresponding benchmark, then the field returns a NULL value.
Rollup and inference fields, as well as other custom field types, can be defined against fields with the Benchmark Definition setting populated.
This setting is also available for advanced holding field attributes.
Allow Benchmark Override
You can override a benchmark when submitting position and entity range reports.
...
If the report is submitted for a composite entity, then consideration needs to be given to which benchmark is retrieved in the report:
If the Enumerate Composites setting is not enabled, then the benchmark associated with the selected composite entity is retrieved by the report.
If the Enumerate Composites setting is enabled, then the benchmark associated with the underlying entities is retrieved by the report.
Currency Conversion
If a field attribute has both a currency process and a benchmark definition defined, then the currency value of the associated benchmark is used for the currency conversion process.
As in current currency conversion processing, if the associated benchmark does not have a Base Currency defined, then the value is not converted.
Reports Submitted for Clients
...
As of field attributes are advanced field attributes and require that a process be defined. In the following example, the process is End Date Holding or Entity.
...
Create Source-Specific Fields
...
To create source-specific security, analytics, ratings or price fields create the field attribute and attach a source.
...
...
Source
...
Source-Specific Holding Fields
You can select a specific source for any holding fields you want to display in a position or lot level position report. When you include source-specific holding fields in a report, the queries run to retrieve data for the report are altered. For reports using regular holding fields, the matrix fetch to retrieve position data uses the source rule you have assigned to the report. For Source-specific fields, the matrix fetch does not use the source rule, but instead uses the sources selected for the source specific fields to retrieve position data. All holding fields must be source specific. However, other field types do not have to be source specific. Therefore, a report can have the field attribute Market Value from Bloomberg and the field attribute Market Value from IDC, but the same report should not have the field attribute Market Value without an assigned source. PACE optimizes the matrix fetch process in the Concentration engine.
Source-specific holding fields can be used in derived fields, such as detailed calculation fields and in grouping rules, as well as in a field rule. Complete the following procedure to create source specific holding fields.
Select the Database (Holding).
Select the appropriate Holding table and the column on which the field attribute is to be based.
For fields used in single period reports, set the Process field to End Date Holding or Entity.
For fields used in multi period reports, assign the appropriate process, either Begin Date Holding or Entity or End Date Holding or Entity.
Set the Field Indicator field to user defined.
...
Source-Specific Field Example for Holdings
Create any custom field attributes, such as detail calculation fields, based on source-specific fields.
...
Source-Specific Detail Calculation Field
All holding field attributes must be source specific to create a report using source-specific holding field attributes. Even though sources have been selected for the field attributes, you must also specify a mandatory holding source for the report, which is a dummy source.
...
Workspace Positions Single Period Using Source Specific Holding Fields
...
...
Source-Specific and Relation Fields
You can run single period position reports related to source-specific fields used with Relation fields. If a single security was held long on one source and short in a second source, the positions yield two separate holdings in the reports results.
...
In a report rule, add a field that is configured with a translation code.
Change the sort from default to custom.
...
Select the values in the order you want. You can reorder them at any time using drag and drop.
Click Done.
...
Custom sorting is now set. To make changes to the order, double-click on the Custom cell.
Use the Sort column in the grouping rule to configure custom sorting for a translation code enabled field placed in a grouping rule.
Create Entity Cross Reference Fields
...
Complete the following procedure to create Entity Cross Reference fields.
Create a new custom field attribute from the Entity XReference category. Enter a name in Name field, and any comment in the Comment field. Select 0 from the Precision drop down list.
...
Entity XReference Field Dialog Box
Click Field Options and select the field options such as publishing and report mapping.
Enter a value for the Column and the Entity XReference Type.
Create an Entity Hierarchy
...
You do not have to run the entity build process for the composites on which they choose to report, they simply must include the composites in the report. You must select the option enumerate composites for the entity hierarchy functionality to work in a report.
Level 1: Company Level | Level 2: Branch Level | Level 3: Group Level | Level 4: Portfolio Level |
Composite 1: All Composite | |||
Composite 2: US Branch | |||
Composite 4: US Equities | |||
US Fund 1US Fund 2 | |||
Composite 5: US Fixed Income | |||
US Fund 3US Fund 4 | |||
Composite 6: US Balanced | |||
US Fund 1 | |||
Composite 3: European Branch | |||
Composite 7: European Equities | |||
EU Fund 1 EU Fund 2 | |||
Composite 8: European Fixed Income | |||
EU Fund 3 EU Fund 4 |
...
Set Up the Entity Hierarchy Function
Before using Entity Hierarchy functionality, you must complete the procedure explained in this section. An internal code is added through the installation and upgrade scripts. The code has a short description of ELEVEL and a long description of IENTITY LEVEL. The code instance for this internal code is 10051. First, you must create code values to reference the level number of each composite:
Create code values under the Eagle PACE source. The code values must reflect the appropriate level. The short description is the level number. The long description is a descriptive name.
...
...
After creating the codes and code values, you create entity hierarchy fields.
...
Return to General Reporting, and select Compose.
Select the report type you want to create.
From the Fields toolbox, select Entity Hierarchy Field.
...
You see the Entity Hierarchy Field dialog box
...
.
...
Entity Hierarchy Field Dialog Box
Complete the fields on the Entity Hierarchy Field dialog box as
...
described in the following table.
Name. Enter a unique name.
...