- 1 Minute to read
- Print
- DarkLight
- PDF
Behavior When Data Calculation Exceptions are Defined
- 1 Minute to read
- Print
- DarkLight
- PDF
Lets say you don't want the system to behave as it does by default. You want the system to assume account values based on account type and the type of data you load from your source system. In order to make this happen, you must define data calculation exceptions.
For example, you have an income statement account and a sales return is posted to the account for January. But, in February, nothing is posted to the account. The account is not zero; there was just no activity for the month of February and you want the account to show the balance from the previous month (January). To make this happen, define a data calculation exception.
In the Income Statement example below, there is no activity to the account for May through December, but a data calculation exception is defined so that the balance is carried forward from May onward.
Assume MTD Activity = 0 | |||||||||||||||
Source | Load Type | Account | Measure | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
DLR | MTD | Flow | MTD | 10 | 10 | 0 | 10 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
|
|
| YTD | 10 | 20 | 20 | 30 | 30 | 30 | 30 | 30 | 30 | 30 | 30 | 30 |
In the Balance Sheet account example below, you want the bank account to post balances for the account each month even when there is a zero balance for a period.
Assume YTD Activity = 0 | |||||||||||||||
Source | Load Type | Account | Measure | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
DLR | MTD | Flow | MTD | 10 | 10 | -20 | 10 | -10 |
|
|
|
|
|
|
|
|
|
| YTD | 10 | 20 | 0 | 10 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |