 |
 |
|
|
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.
Views that combine fees and WIP information on a period basis only make sense if the periods on the time and fees ledger are aligned (for example, there are the same number of periods per year on the two ledgers and the start and end dates of the periods on the two ledgers are the same).
For the variants of such views that are restricted by period (for example, current, latest closed and so on) it is the TIME ledger period status that is used. Thus, if the time ledger period has been closed, but the corresponding fees ledger one has not, the information presented will be the current information for that fees period.
You should also note that the information is associated with periods according to the individual postings on the ledgers. For example, if you post an invoice to period 2 on the fees ledger, but it actually writes out to period 3 on the time ledger, the fees invoicing details will appear under period 2 and the billed totals for WIP under period 3.
There are several ways that this can happen, for example:
Because the time ledger period was closed and the write out had to be redirected to a later period
Because the fees ledger options say to write out on the basis of the invoice date, and the date does not lie within the actual fees period
Because the fees ledger options say to always write out to the current time ledger period irrespective of the fees ledger period or invoice date
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 |