Use History

Data Mart allows you to use or omit the use of history tables for entity and security data.  Using history increases build time for the Data Mart, since additional queries must be made against history tables.  However, if you are building data for past dates, you will need to build with history tables in use. Eagle’s best practice is to always use history when running models.  This accomplished by using source rules where a source hierarchy is set for Security related fields and/or source specific fields are used in the models. Entity History is accomplished via the configuration screens.

If entity build is not used and the Always Composite Holdings setting is selected in the Configuration dialog box, PACE will enumerate holdings and populate the positions of all composite members in the Position Details table. These may then be rolled up to the security level within the reporting tool to create composite level positions.