Page Comparison

Submission Mode

Regular Submission

Indicates a regular Ad Hoc submission.

Supply Defaults from this Data Mart Schedule

Defines a submission based on the contents of a schedule. When you select this option, a list of Data Mart schedules becomes available in the dropdown list. When you select a schedule, the information from that schedule is used to fill in fields on the Data Mart Model Submission dialog box. You can override any of the automatically filled in fields. Fields filled in include:

• Snapshot
• Date Rule
• Model(s)
• Fields (Build all or selective build)
• Entities

As of

Snapshot

Allows you to choose a snapshot to use when building your data. See Create Multiple Snapshots of Your Data for details.

As of Date

Allows you to select an effective date to store the Mart data. Choose an as of date to build data with a single effective date.

Date in this Business Calendar

You can build data for one date or a range of dates. To build data for a range of dates, select a date range and a business calendar.
Options include:

• Business calendar. Defines a business calendar to indicate which As Of dates within the specified date range are valid for use as effective dates. You may want to create a business calendar for a special purpose and designate only the run dates you want as business days. You can then submit the models for a date range that includes your entire date span.
• Daily or monthly frequency. Specifies use of a daily or month end column of the selected business calendar to determine valid dates. The option you select determines if data is built monthly or daily.
• Process Dates Concurrently. When you select concurrent processing and submit models for a specified date range, the system launches multiple processes at the same time, one to handle each day's build. If the system encounters a problem that causes this set of events to end before all models are completed, you have a subset of the total numbers of days populated in random order, not chronological order. When you do your rerun, you may have to run several different periods to close all the gaps.
• Process Dates Sequentially. When you select this option and submit models for a specified date range, the system processes each day's build in chronological order. If the system encounters a problem that causes this set of events to end before all models are completed, you have a subset of the total numbers of days populated in chronological order. When you do your rerun, you can run the un-populated dates in the original date range. System performance may be slower, depending upon how many days you submit and what is the longest-running engine launched for each date. The next day's processing must wait for the longest-running individual engine of the previous date.

Date Rules

Ad hoc

Specifies a date rule which contains begin and end dates, the PACE Concentration Engines used to calculate values. These are relative dates, such as month end, that depend on the dates selected in the As Of section.
See About Date Rules for additional information.

From Schedules

Allows you to use the same date rule in your ad hoc submit as you use in a particular Data Mart schedule, for consistency.
For example, if you select a schedule from this dropdown list, Data Mart uses its date rule in your ad hoc submit.

Specific to Data Types

Allows you to create a date rule for a specific data type, such as holdings, performance, cash flows, transactions, and ledger data.

Holdings

If you enter a date rule here, the end date defined by the rule defines the effective date of holdings data selected by the underlying OLAP process.

See About Date Rules  or additional information.

Performance

If you enter a date rule here, the end date defined by the rule defines the effective date of performance data selected by the underlying OLAP process.

See  for additional information.

Cash Flows

If you enter a date rule here, begin and end date defined by the rule define the range of effective dates of cash activity data selected by the underlying OLAP process.

See About Date Rules for additional information.

Transactions

If you enter a date rule here, begin and end date defined by the rule define the range of effective dates of transaction data selected by the underlying OLAP process.

See About Date Rules for additional information.

Ledger

If you enter a date rule here, begin and end date defined by the rule define the range of effective dates of ledger data selected by the underlying OLAP process.

See About Date Rules for additional information.

Business Dates

If you enter a date rule here, begin and end date defined by the rule will define the range of effective dates of business calendar data built.

See About Date Rules for additional information.

Models

Submit All Models

Specifies all models for submission at one time.

Select Models to Submit

Allows you to select a subset of models and limit the data populated in the Data Mart. Click Add to display the Data Mart Model Selection dialog box. Enable the check box of each model that you want to submit and click OK.

If you configured a model that maps details to a group model through the Filters tab, the details are not calculated when the group model is submitted. You must submit each detail model that you want to populate in this or another submission.

When you submit a detail model, the Security Details and Issuer Details models are automatically selected for submission by default. This is because security and issuer information is usually a necessary supplement to Position, Performance, and other detail data. However, you may use the Remove link to remove Security Details and Issuer Details for submission. This may be an appropriate and time-saving step, especially if you are rebuilding detail data for just a few entities using Process Manager.

However, you can use the Remove link to avoid submitting Security and Issuer Details. Avoiding those submits speeds up the rest of the build and can be appropriate in some circumstances. However, exercise caution when you do this. If you have added positions or trades in any new securities since last building Security Details, and you build Position Details or Trade Details, you will be missing the necessary companion security data for the positions or trades.

Fields

Build All Fields

Populates all fields.

Build Selected Fields

Populates fields selectively. Click Select Fields to display the Data Mart Model Submission Fields Selection dialog box.

Click a column name to sort the fields. To search, right-click and select Find from the pop-up menu. You see the Find dialog box. Select find criteria and click Find Next. To filter, right-click and select Filter. You see the Filter dialog box. Select filter criteria and click OK.

Select the check box of any field you want to populate with this submission. Each model submitted that contains a given field is populated according to your selections.

For information on Fields Selection dialog box, refer to Working with the Fields Selection Dialog Box.

See About Build Selective Fields for additional details.

Funds

Submit All Funds Selected for the Model

Allows you to submit all entities defined in the submitted models.

Languages

Submit All Languages Selected for the Model(s)

Selected by default. Allows you to submit the mart for all the languages in the Model definition.

Select Specific Languages to Submit

Allows you to submit the mart for the selected languages only. Click Select Languages. You see the Available Languages dialog box. Select the languages to use when you submit the mart, and click OK.

Currencies

Submit All Currencies Selected for the Model(s)

Selected by default. Allows you to submit the mart for all the currencies selected in the Model definition.

Select Specific Currencies to Submit

Allows you to submit the mart for the selected currencies only. Click Select Currencies. You see the Available Currencies dialog box. Select the currencies to use when you submit the mart, and click OK. 

If you submit more than one model, the Submission dialog box displays all the currencies and languages selected in those model definitions. If a model is not set up to use the selected languages and currencies, that model is not built.

Select Specific Funds to Submit

Allows you to select a subset of the entities defined in the submitted models and limit the data populated in the Data Mart.

Click Add to display the Entity Selector dialog box. Click Load to populate the dialog box with all available funds. If you used the dialog box before performing this step and set up a filter in the selector, only those funds that meet the existing filter criteria are displayed.

Select one or more funds in the top part of the dialog box and click Add. The selected entities are listed in the bottom part of the dialog box. Click OK to submit the selected entities.

Additional Options

Displays the Additional Options dialog box, which allows you to set more controls for submission. Options include:

• Set Fund Approval Status As. Select a status to assign to this build. See the section Manage Mart Data Status for details.
• Save Diagnostics. Includes diagnostic details in the execution log.
• Run at log level. Sets the execution log level for the submit process.
• Save temporary tables. If you are populating data into an Oracle database and need Eagle's help with troubleshooting a build error, check this box to save data into temporary database tables which assist Eagle with its diagnosis.
  If you set the status of a submission to a particular value, you affect the status of all data from every model associated with all combinations of Fund, As Of date, and snapshot in the current submission, including models not selected for submission.
  For example, suppose a user set the status as Preliminary and submitted Fund ABC, effective December 10, 2013, for the Country and Industry models. An hour later, another user set the status as Final and submitted the Trade Details model for ABC for December 10. The result is that the status of the Country and Industry models is now set as Final. The same is true of the Fund Summary and any detail level tables that had data rows for this fund and effective date.