Set Up the System for Entity Builds

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

Ensure Entity Build Engine is Enabled

Ensure that the Entity Build Engine (ENTITYENG) on the PACE Server is enabled. Otherwise, contact a DBA for assistance. 
writers note: Confirm whether you need to check System Management Center > System Settings >Event Types for ENTITYENG instance and confirm that Process Manager column is Enabled? If not, then what?

Review Uploader Schema

Choose the Build Type of Entity within the Import/Export Feed button in the Administrator during the setup of the Uploader schema.

This is chosen 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.

WRITERS NOTE: confirm with Dima whether you need to take some action. Is this related to Automation Center > Setup > Schemas, where you can view the schema for a row with a Feed Type of ENTITY BUILD?

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 "Working with Entity Build Field Attributes" section of the General Reporting Reference Guide 2015. Also 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.