...
Since OLAP reports are specialized by field type, such as position, performance, or transaction, it may take four or more OLAP reports to provide the necessary fields for a fund level or group level table. You have the option of defining table extensions for the Fund Summary and Detail models. A table extension stores a subset of the model's fields in a separate physical table that has a key structure identical to the main table, but is populated by its own OLAP reports.
...
By default, Data Mart builds one daily version of your business information according to a single data source hierarchy known as a source rule in PACE. With Data Mart's snapshot feature, you can build and save your information more than once per day, and use more than once source rule in the build process. For example, suppose your organization runs a pension fund, and you maintain both a custodian source and a manager source of the same accounting data.
You can create one snapshot that looks at fund activity from a custodian's view point and another snapshot that looks at fund activity from a manager's view point. You can also use snapshots to report on the same portfolios in different accounting bases. Separate snapshots can also save separate builds done at different times of the day, allowing you to make intra-day comparisons of data values.
...
Execution logs provide information on scheduled and ad hoc (manual) model submissions.
You can view Execution Logs at the following levels:
- Data Mart Manager Engine. Displays each model submission for a distinct effective date.
- Model Manager Engine. Displays an individual model submission.
- Concentration Engine. Displays the OLAP process contents within the model.
The PACE Application Server Log provides information about the application server on which Data Mart processes are executed.
...
You can also view the contents of Data Mart tables, refresh data changes, explode group levels, and export, print, and configure data columns on a number of windows.
Using the Query Expert feature, you can create and copy SQL code that retrieves Data Mart data. You can then paste the SQL code into an external reporting application for reporting purposes.
The remaining sections of this guide provide details on navigating the Data Mart user interface, configuring the Data Mart environment, creating and editing models, submitting and managing models, working with processing logs, and viewing data in the Data Mart.
Refer Guidelines for Configuring Models for high level details on configuring models and using Mart data in third party reports.