About Submit Build Box Detail Options

This section describes the Detail options in the Submit Build box that you use to run an entity build. These options apply to running an entity build for entities with entity types such as aggregates and sub-portfolios. Different options appear if you manually submit an entity build for other types of entities such as custom benchmarks or GIPS composites. 

WRITERS: other entity types that see this box? COMP? 

Define Date Criteria

In the Date section of the Submit Build box, you can determine the effective date used by the entity build. 

You can determine the Date used by the Entity Build in a variety of ways depending on how you submit it. Some examples follow:

• Single Date. You can manually select a single date from the Calendar Selector.
• Existing Date. You can manually select a single date from a List of dates. The list displays all effective_dates that exist in the holdings database for the underlying entities of the entity being submitted.
• Date Range. You can manually select a date range from the Calendar Selector. 
• Date Rule / Build for Date Rule's End Date. You can manually select a Date Rule to run for the single date as configured in the rule.
• Date Rule / Build for Date Rule's Range. You can manually select a Date Rule to run for the range of dates as configured in the rule. See "Running a Build for Date Ranges" on page 112.

You can submit an Entity Build for a Single Date chosen from a calendar selector or a Single Date from using a Date Rule. However, the date was always for the Single Date as configured in the date rule. The system allows you to submit the the Entity Build for a range of dates as specified manually or as defined by the date rule. The Entity Build Submit Build box, accessible from the Portfolio Data Center or Performance Center,, allows you to pick an available Date Rule and determine if it will be submitted for the Single Date as configured in the rule or submitted for the Entire Date Range represented by the start and end dates of the rule.

An example of the Submit Build window used to submit the entity build for a date range related to a Date Rule follows.

You can also schedule Entity Build events to run for a range of dates from the Events workspace when you maintain an event, as shown in the following figure.

When you submit an Entity Build for a date range, the Entity Build engine submits the initial engine as the master (parent) process. This engine evaluates the date rule and submits nnumber of child engine processes, one engine per date in the range for the entity submitted. The master engine then monitors the child processes and completes when all child builds have finished. Any dependent events defined do not run until the master process completes.

All child Entity Build engines are linked to the parent Entity Build engine and can be seen in the DataSteward: Event Queue window when expanding the parent event. 
WRITERS NOTE: Re,pve prior paragraph. location was DataSteward Event Queue? I am removing the screenshot. Is the following paragraph accurate? 

All child Entity Build engines are linked to the parent Entity Build engine. You can view the child Entity Build engines in Automation Center's Monitor workspace by clicking Jobs/Events, entering searching criteria, and selecting the Include Child Events in Search check box. 

How Entity Build Evaluates the Date Rule Range

The Entity Build evaluates the date range for the date rule in one of two methods.

• If the Date Rule does not use a Business Calendar, the date range is the entire set of dates from the start date to the end date.
• If the Date Rule uses a Business Calendar, the date range is only those dates that have been flagged as a Daily, Month End, Quarter End, or Year End date.

The ability to evaluate a Date Rule in any PACE engine in order to process a range of dates is available. This logic in the Entity Build does not provide the ability to define a specific Business Calendar flag (that is, Month End) to use when submitting for a date range.

The Entity Build engine is not able to take into account each Entity's Inception Date when using the Fund Inception Date or Fund Fiscal dates configured in the Date Rule. The engine may submit for dates prior to the inception date, but no Holding data would exist for those dates and therefore the net result is that no build occurs for that entity.

About Entity Build Sources

There are a number of ways to specify sources for your composite and the underlying entities that are in the Composite. There is a main composite source that is stored on the ENTITY table for the Composite record. In general, this is the primary source for the composite and its underlying entities. The Fund source overrides the main composite source and allows you to build a composite with multiple sources. The Fund source can be found on the ENTITY_DETAIL_HIST table. The method in which you kick off the entity build further affects the way these sources interact.

When the entity build is Scheduled or run Adhoc for All Entities, or it is Uploader Driven, you see the results shown in the following table. The Comp A source drives the process when it is specified. Otherwise the Run source becomes the default.

Position records build for Comp A with Source Y (Comp Source)

Position records build for Comp B with Source X (Run Source)

For Comp A:

• Finds Port A data using Source Y (Comp Source)
• Finds Port B data using Source Z (Port Source)

For Comp B:

• Finds Port A data using Source X (Run Source)
• Finds Port B data using Source Z (Port Source)

When the entity build is Scheduled or run Adhoc for a specific entity or it manually submitted from the Entity Explorer, you see the results shown in the following table. The Comp A source never drives the process when it is specified. The Run source becomes the default.

Position records build for Comp A with Source Y (Run Source)

Position records build for Comp B with Source X (Run Source)

For Comp A:

• Finds Port A data using Source Y (Run Source)
• Finds Port B data using Source Z (Port Source)

For Comp B:

• Finds Port A data using Source X (Run Source)
• Finds Port B data using Source Z (Port Source)

Modify the Security Override Source

The system provides a script to modify the Inventory of Fields record for the following column:

RULESDBO.CLIENT_OVERRIDES.SECURITY_OVERRIDE_SOURCE

The script modifies this record to make it an optional (that is, not required) field. This table was created initially as a required field. Users who choose to use this feature and would like this field to remain required can skip execution of this script during upgrades.

WRITERS NOTE: is this still valid? what is the purpose of this security source?

Submit the Build for a Specified Log Level

In the Submit Build box, you can use the Log Level field to submit the build for any log level.

Thef default value for the field is Default Log Level. When you leave the log level as Default, the engine runs at the level configured at the PACE Server level.