13.9.10 Aggregate Instrument Table

The Aggregate Instrument Table functionality allows you to avoid writing multiple rules, where the rule logic is essentially identical except for the specification of the Instrument Table.

Select the “Portfolio” table as the Source table, Driver table, or Output table in any allocation rule that is capable of operating against the instrument level (that is, not including Constant rules or Leaf rules). After selecting the “Portfolio” table, the columns available in the column drop-down list box include all the columns that have the Portfolio property, that is, all columns that are by definition found in every instrument table. The allocation engine can determine the table or tables that are relevant given the Source, Driver, or other constraints of Output tabs.

You can aggregate instrument-level data into tables other than Management Ledger that have instrument-like qualities, such as, many balances and attributes per row, very high row counts. The aggregate instrument tables or “super-instrument tables” are intended to facilitate both processing and, eventually, reporting on the customer, household, relationship manager, and so on.

• Support the flexible methods for aggregating the instrument level data via the allocation engine. The types of aggregation include by Customer, by Household, or by Relationship Manager.
• Support the ability to aggregate up from instrument tables to aggregate instrument tables; to push down from aggregate instrument tables to normal instrument tables, push down from Management Ledger to aggregate instrument tables.
• Support the ability to aggregate up from Transaction Summary tables to Aggregate Instrument tables. This is a less important objective and can be dropped in Function or Technical designs.
• Support the ability to load aggregated instrument tables from Staging.
• Support bulk aggregations via T2T rule or other Infrastructure capabilities, if possible.
• Support the ability to aggregate instrument data – one column at a time – using a MERGE function so that rows are INSERTED where they do not already exist, and updated where they do exist.
• Support both Static Table Driver rules and Lookup Table Driver rules. For Static Table Driver rules, support Target Leaf functionality.
• Support the ability to UNDO allocations to the Aggregate Instrument table level using the same paradigm as is used for UNDO against Instrument tables or Transaction Summary tables (such as using IDENTITY-CODE-CHG).