Budget structures consist of one to many budget levels that correspond to increasingly more detailed levels of budgeting in the structure. Information about budget structures can be seen on the Budget Structure (BUDST) page and under the Budget Structure Update link on that page. Only those budget structure parameters that can be configured online are editable. Those that have a design impact are protected.
Structure ID - A required unique number is assigned to each budget structure when developed. That ID is protected because it is used by the application to determine the correct database tables to update.
Structure Name - A required text field exists for a descriptive name of the budget structure that would be used for reporting purposes. The name is editable on the Budget Structure Update page.
Budget Type - A required choice of different budget types -Managerial, Program, Statutory, and Reimbursable - exists to mark a particular budget structure as such for reporting purposes. The type is editable on the Budget Structure Update page.
Expense/Revenue - Each budget structure has this attribute to indicate whether the budget should support expense or revenue budgets or both. As this required choice impacts the layout of a budget structure, it is not determined online. For example, an expense budget will be built with different budget buckets than a revenue budget, so an online change would not produce the desired change.
Central/Decentral - The required distinction of central or decentral for a budget structure is used for reporting purposes.
Inheritance Rules - As later sections of this guide will describe, there are many locations at which budget controls can be defined. When evaluating these controls after an update, the Budget Posting Routine has to determine which location’s error level will apply to a control when multiple locations contain the same control. Each choice of an Inheritance Rule contains multiple locations and the Budget Posting Routine will consider a control found in a location listed to the right over one listed to the left. The rule is editable on the Budget Structure Update page.
Active - The Active flag denotes a structure as being one that is currently being used in an application. The Budget Posting Routine will attempt to find a match on every level of every active budget structure of the type that should be updated according to the posting code being used on an accounting transaction. Structures not being used should be deactivated on the Budget Structure Update page.
Effective From / Effective To - Currently, these dates do not have a function within the application. Later use will enable the application to transition from using one budget structure to another with these dates.
Last Modified By / Last Modified Date - These fields track online changes made to a budget structure through the Budget Structure Update page.
Budget Fiscal Year Driven - This flag indicates whether the budget structure is budget fiscal year driven. When a budget structure is to be defined yearly, the Budget Fiscal Year (BFY) must be built into the database tables for that structure. Those budget structures that are not defined yearly are useful as 'no year' budgets, and do not have a BFY in their database tables. Cost Accounting budgets for reimbursement are of this no year type. As the BFY will need to be a key to a budget line on a BFY driven budget structure, changing of this flag online is not permitted.