 |
 |
|
|
This view gives a simple cross product of clients owning time or fees ledger accounts and ledger periods. It can thus be used to drive other processing that must return something for every account/period combination
Many of the totals records on ledgers only come into existence when the first contributory posting is written. If an account is not active every period then there will be gaps in the coverage if the totals records are used as the prime driver.
Low level views do not make any special attempt to deal with this, they just return the information that is there and rely on the user of the view to infer what is required if a particular row is not present. Higher level views, however, sometimes need to be driven so that there are no gaps. This view acts as a common driver for these cases.
This view equates time ledger periods to fees ledger periods. It therefore only makes sense if the periods on the two ledgers are aligned (i.e. the same number of periods per year on each and the start and end dates of the periods corresponding)
Type = Amalgamation view - cartesian product to give all combinations of clients and periods - suitable for advanced end user use
| ClientObjectType | The object type of the client owning a time or fees account |
| ClientInternalId | The internal identifier of the client owning a time or fees account. |
| Year | The ledger year - see notes |
| Period | The ledger period - see notes |