This section describes how to use more advanced settings with custom fields.
Create As Of Field Attributes
You can create As Of time sensitive field attributes for security, ratings, price, analytic, entity and holding field attributes.
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
Source-specific fields are intended for reconciliation purposes. You can create source-specific field attributes that assigns a specific source to a field attribute used in a report. You can create source-specific field attributes for security, analytics, ratings, price, and holding fields.
To create source-specific security, analytics, ratings or price fields create the field attribute and attach a 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.
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
Report Results for Positions Single Period Report 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.
Custom Sorting on Code Value Sets
You create custom sort orders on code value data sets. This allows you to set up custom sort orders more easily based on code values and dictionary classifications. Complete the following procedure to set up a custom sort order.
In a report rule, add a field that is configured with a translation code.
New Regular Field - Add Field with Translation Code
Change the sort from default to custom.
Workspace - Sort For Code Value
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.
0 Comments