Allocation Mappings
Allocation Mappings are a core part of our dynamic allocation technology that allows the system to identify which Paths any given instrument should have all of its Transactions allocated via. This is designed in a way you can hook into the functionality to provide custom methods for identifying groups of instruments.
Allocation Mappings Features
Allocation Mappings allow you to associate any given Instrument, or set of Instruments, with a specific Allocation Path.
You can specify each association individually by instrument, which is useful for granular designations, but is impractical as the number Instruments scale. Rather you need a mechanism for identifying large groups of Instruments that you can then all tie to a Path at once.
This provides an easier mechanism maintaining large sets of instruments and mapping them to Paths.
Instrument Set Integration
By integrating with Instrument Sets [more inf] the system provides an easy and powerful mechanism to map large groups of instruments at once. By default Instrument Sets can match on base Instrument information such as currency, owning entity, and the Instrument itself.
The real power of using Instrument Sets comes into play by using our platform to extend the functionality to cover your specific types of instruments with mechanisms to match on all of your relevant attributes. You can then easily create the minimum number of mappings required to associate your unique Instrument Sets with their correct Paths. See Instrument Sets for more information.
Incorrect Mappings
The system has two views, by default shown against Entity Sets [more info], that aid in determining if their are any problems with your Allocation Mappings:
- Unmapped Instruments
This view shows a list of every instrument in the Entity Set that isn't associated with an Allocation Path via an Allocation Mapping. This excludes instruments that are marked as "Allow Unmapped". - Instruments In Multiple Mappings
This view shows every instrument in the Entity Set that has been assigned to multiple Paths through Allocation Mappings.
Instruments should be mapped to one, and only one, Allocation Path. If they are not the system won't be able to allocate any of the transactions against it to the ultimate owners via an Allocation Path.
System Usage
The system uses Allocation Mappings in Transactions, Blend Transactions, Period End processes, and anything else that requires the system to identify the mechanism to allocate transactions for an instrument.
Not all Transactions require mappings, they can have specific Allocations already specified through rules, or have a Path already set against the Transaction itself. Without that the system can dynamically ascertain the Path from these Allocation Mappings and the instrument the Transaction is operating against.
Views
Allocation Mappings are managed through the following views:
