Set Up the System for Entity Builds

You must perform several setup tasks before you can run entity builds. 

Create Entity Build Fields

These fields are utilized and populated within the entity build engine. To do this, from Performance Center's Performance Desk, select the General Reporting workspace. In the reporting studio, within the Components tab (three tab mode), access the Entity Build folder under Fields. Create field Attributes with the Entity Build process.
The build generates position records (to the POSITION_DETAIL table located in the HOLDING database). In addition, if the build is enabled to generate cash activity (CASH_ACTIVITY table in the CASH database), then you also need to create entity build field attributes for cash fields.

For more information, see the examples shown in Engine Maintenance of Position Base and Local Currency Fields (Multicurrency Build).

Define the Entity Build Flag for Entities

The Entity Build Flag determines how to handle cases in which one fund does not have available data for a particular date. You can allow or prevent builds based on partial data. 

For example, a composite contains three portfolios: Portfolio A, Portfolio B, and Portfolio C. During a particular upload, Portfolios A and B have data for that effective date, but Portfolio C does not. The Entity Build Flag provides you with two choices. The composite for that effective date can be built without Portfolio C, or the composite is not created for that date at all.

The Entity Build Flag field is set up in the Inventory of Fields. Assuming that you add it within the field group for the respective policy, you can access it from Portfolio Data Center in the entity's Entity Details section during the setup or editing of an entity. If a value of Y or NULL is present in this field, then the composite is built with the available portfolios. If a value of N is present in this field, then the composite is not built. 

Define the Entity Build Mode of Process System Parameter

An example of Derived Entities is a Composite made up of another Composite. The Entity Build engine expects underlying entity data to exist. Therefore, it is up to you to run the Entity Builds in the correct order to ensure the underlying Composites were built before building the highest level of Composites.

For example:

If COMP A is composed of COMP B, and COMP B is composed of PORT 1 and PORT 2, then you must run the Entity Build for COMP B before you can run it for COMP A.

The Entity Build engine enables you to manage this process. It provides greater ease of use as the structure of an entity universe increases in complexity (COMPS of COMPS of COMPS, and so on). Using the previous example, submitting the build for COMP A builds automatically COMP B in the process.

The system enables you to control the mode in which the Entity Build operates. The control is set at the environment level as a System Parameter. The sys_item for the Entity Build Mode of process is 71 and it is stored in the PACE_SYSTEM table.

If you set the entry to 1, it automatically rebuilds underlying entities. If you set the entry to 0, it does not rebuild underlying entities and just uses the data that already exists for the underlying entities. By default, upgrades of Eagle's data management solution default the value to 1 in order to ensure the engine works as it is currently designed. For more information, see and Manage System Parameters.

Ensure the Entity Build Engine is Enabled

Ensure that the Entity Build Engine (ENTITYENG) on the PACE Server is enabled. Otherwise, contact a DBA for assistance. 

To confirm that the Entity Build Engine is enabled: 

1. In System Management Center, in the left navigation pane, click Environment > Services.
   You see the Services workspace.

2. Double-click the PACE Server row to view all server settings. 
   You see the Details tab for the server.

3. Click the Configuration tab. 

4. In the PACE Server Settings pane, under Engines, locate the Entity Build check box. 
   If the Entity Build check box is selected, the Entity Build Engine on the PACE Server is enabled. Otherwise, if the check box is cleared, the Entity Build Engine on the PACE Server is disabled.

You can additionally check the system settings to confirm whether the Entity Build engine is running on all servers or is running on just the master. 

To confirm whether the Entity Build engine is running on all servers: 

1. In System Management Center, in the left navigation pane, click System Settings > Event Types.
   You see the Event Types workspace.

2. Identify the row with a Name of ENTITYENG and a Description of Entity Build. 

3. Review the Concurrency Flag column value for that row. 
   The column has a value of either All Servers or Master Only.

Review the Uploader Schema

If you plan to kick off the entity build process as part of an Uploader, when you define the Uploader schema you select the Build Type option of Entity. You choose this option for POSITION uploads. This indicates to the system that the existing composite, aggregate, and sub-portfolio entities should be updated with the new positions data, if applicable. 

To create an Uploader schema with a Build Type of Entity:

1. In Automation Center, in the left navigation pane, click Setup > Schemas.
   You see the Schemas workspace.

2. On the Home tab, in the Manage group, click Create New.
   
   You see the Define Schema wizard with the Define page displayed. 

3. In the Option field, click IMPORT.

4. In the Source Interface field, click a value such as Eagle Generic Interfaces. 

5. In the Feed Type field, click a value such as Positions. 

6. In the Build Type list, click Entity. 

7. Complete the remaining options for the wizard.

8. Click Save. 

In the Schemas workspace, you can view the schema for any source uploaders that use the POSITIONS feed type for entity builds. This includes the Options, Limits, Formats, Field Map, Field Attributes, and Map Rules sections.