Turn controls that will be used from Not Selected to No Action on BUDCON and check the allowed action flags that should be choices at other areas of control management.
Insert guidelines needed on BUDLCON at the upper levels (never the lowest level or an optional level) with the proper default violation and any allowed action flags that should be choices at other levels.
Insert constraints on BUDLCON for the lowest required budget level of a structure when a guideline is in place that will prevent more budget authority at the lowest required level than at levels above. To have constraints at the upper levels in such a situation would only issue duplicate errors with just a different budget level.
Insert constraints on BUDLCON for all required budget levels necessary to control if guidelines preventing more authority at lower levels are not in place.
Controls that ensure stand alone budget amounts do not go below zero should only be set at the lowest required budget level of an applicable structure on BUDLCON. To have these at other levels would be redundant.
When exceptions to the rule exist, set those default violation actions at the budget line level or fund level.
Use the Allow Action flags at upper levels in the inheritance hierarchy to enable or disable controls at lower levels as only one record has to be changed instead of multiple ones.
Ensure that constraint #29 is inserted on BUDLCON for the each level in a reimbursement budget structure with a default violation of Reject with none of the Allow flags checked.
The action of Load Constraints is a securable action that should not be given freely. If restricted, then if Allow Override, Allow Warning, or Allow No Action flags are checked, it will allow a modification of the default violation at the budget line level to process a document that would not normally accept and then another modification to set it back.
With the introduction of the performance enhancement of incremental updates to budget lines in the Advantage 3.3 release, changing certain fields on the BUDCON table after budget lines have been created will involve a batch program. Once a budget line is created that a control would apply to, a record is created in an offline tracking table that stores the LHS and RHS amounts calculated from that budget line for that control. If a control was not activated (that is, marked as any other default violation other than No Action) initially for that budget line, then when that control is activated, a record will be missing in the offline table for that budget line. The running of the Calculate Budget Control Amounts batch job will need to be run to update the offline table.
As mentioned earlier, certain changes to the BCADM table can require the same batch job to be run before the application should be used. There are two other tables that changes to will cause the offline records of control amounts to become incorrect. One is the Formula table, where formulas for calculated amount fields are stored. Changing how an amount in a control is calculated would naturally make the amounts stored for a control to be incorrect. The other is the Budget Tracking Amount (BUDTAM) table. This table can cause incorrect control records in two ways. The first is the formula for a calculated bucket being changed to another formula. The second is selecting or deselecting one or more of the include pending amount flags. The first of these two changes on BUDTAM and the change to the Formula table will have an impact beyond the stored control amounts: the budget inquiry tables will not reflect the current amounts until the application has performed a save to the budget line.