Using Alternate Methods to Set Up Drivers
Activity-Based Management uses drivers as the basis for sustainable models; therefore, you do not need to set up drivers every time you run the Activity-Based Management engine. Drivers pick up costs from operational warehouse - enriched (OWE) tables and assign them between resources, activities, and cost objects.
Special circumstances occasionally require you to hard code driver values—for example, to prototype some quantities. If you need this functionality, you can use the Driver Quantity pages to hard code the values.
Warning! To avoid using hard-coded values for drivers that may have a negative effect on your models, ensure that you thoroughly understand how using them impacts your system.
Pages Used to Set Up Drivers Using Alternate Methods
Page Name |
Definition Name |
Navigation |
Usage |
---|---|---|---|
Driver Quantities 1 |
DRIVER_QTY_TBL1 |
|
Enter quantities for drivers associated with activities in case you do not have system-generated data. |
Driver Quantities 2 |
DRIVER_QTY_TBL2 |
|
Enter driver quantities according to object ID. |
Driver Quantities 1 Page
Use the Driver Quantities 1 page (DRIVER_QTY_TBL1) to enter quantities for drivers associated with activities in case you do not have system-generated data.
Warning! This method requires a considerable amount of maintenance and can easily result in long-term sustainability problems for your models if used extensively.