Burden steps (AC/BR/GM) process
Burden steps let you calculate burdens from burden transactions. You can assign steps to burden codes to determine the order in which burden calculations occur during Activity Posting (AC190). This makes it possible to include burden transactions created during Activity Posting as potential source transactions for subsequent burden calculations in the same run.
This table shows potential source transactions for burden codes when no steps are assigned.
| Burden code | Step | Potential source transactions |
|---|---|---|
| GA-A | <blank> | AC190 non-burden transactions |
| GA-B | <blank> | AC190 non-burden transactions |
Burden codes with blank and lower-numbered steps are considered potential source transactions for burden codes with higher steps. This table shows potential source transactions for burden codes when steps are assigned.
| Burden code | Step | Potential source transactions |
|---|---|---|
| GA-A | <blank> | AC190 non-burden transactions |
| GA-B | 1 | AC190 non-burden transactions GA-A burden transactions |
| GA-C | 2 | AC190 non-burden transactions GA-A burden transactions GA-B burden transactions |
| GA-D | 2 | AC190 non-burden transactions GA-A burden transactions GA-B burden transactions |
| GA-E | 3 | AC190 non-burden transactions GA-A burden transactions GA-B burden transactions GA-C burden transactions GA-D burden transactions |
All potential source transactions—including burden transactions—must meet eligibility criteria for burden codes and pools with higher steps. If the transaction does not fall within the criteria defined for the pool driver values, no additional burden will be calculated.
For example, the pool for burden code GA-B is based on the Labor and Equipment account categories, and the account category used in the burden transaction is Overhead. The driver type for burden code GA-C is also account categories. If GA-C's pool driver values do not include the Overhead account category, the burden transaction calculated from burden code GA-B fails to meet the eligibility criteria for the GA-C burden.
Step variances
In the previous example, burden transactions are added as potential source transactions for burdens in each successive step. You can use step variances to modify how burdens are treated for subsequent burden calculations.
The Stand Alone Step variance allows you to ignore burden transactions created for the burden code in subsequent calculations. In this example, burden code GA-B is assigned Step 2 and is identified as a stand alone step. The burdens calculated for GA-B are not eligible source transactions for the burden codes assigned Step 3 or higher.
| Burden code | Step | Step var | Potential source transactions |
|---|---|---|---|
| GA-A | 1 | AC190 non-burden transactions | |
| GA-B | 2 | Stand alone step | AC190 non-burden transactions and GA-A burden transactions |
| GA-C | 3 | AC190 non-burden transactions GA-A burden transactions |
The Applies Only To Burden variance identifies the transactions generated from a specific burden code as the only potential source transactions for the burden. Non-burden transactions and burden transactions generated from other burden codes are not potential source transactions. In the following example, burden code GA-C will be calculated using only burden transactions generated from burden code GA-B as its source transactions.
| Burden code | Step | Step var | Burden code | Potential source transactions |
|---|---|---|---|---|
| GA-A | 1 | AC190 non-burden transactions | ||
| GA-B | 2 | AC190 non-burden transactions and GA-A burden transactions | ||
| GA-C | 3 | Applies only to burden | GA-B | GA-B burden transactions |