Late trades and security data vendor corrections are examples of events that can create stale data in your Mart. Using the Business Process Manager, you can automate the process of re-populating the Mart as warehouse data changes make this necessary.
Process Manager can be set up to detect changes to the update_date field value in each of several different warehouse table. Since a change of update_date on a given row indicates a change to table data for the row’s entity on that date, your Data Mart should be rebuilt for that entity and effective date for all tables containing data of that type. Such a change detection rule is known as a Dynamic Process Initiator.
A Dynamic Process Initiator can then trigger a Process Workflow, which is an event or series of events required to be started when the initiator is activated. For Data Mart, an event is a Schedule. You can set up a Schedule to re-populate each table that must be brought into sync after a change to each type of Warehouse table covered by your Business Process Manager workflows.
Using 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.
Add Comment