To increase performance, many of the budget configuration pages are put into a type of memory known as the Budget Flex Server. The following chart shows all tables that are involved in budgeting by their page codes and names along with whether or not they are in memory. Note, not all pages in the budgeting area have a page code as they are navigated to using a link on another page.
Page Code |
Page Name |
Memory |
BUDST |
Budget Structure |
Yes |
|
Budget Structure Update |
Yes |
|
Budget Level Update |
Yes |
|
Allotment Option |
Yes |
BUDSTS |
Budget Structure Summary |
Yes |
BCADM |
Budget Control Administration |
Yes |
BFADM |
Budget Formula Administration |
Yes |
BUDCON |
Budget Controls |
Yes |
BUDFCON |
Budget Fund Controls |
Yes |
BUDLCON |
Budget Level Controls |
Yes |
BUDTAM |
Budget Tracking Amounts |
Yes |
|
Budget Formulas |
Yes |
BUDTYP |
Budget Type |
No |
PBRP |
Parameters for Budget Roll Process |
No |
SBA |
Summarized Budget Activity |
No |
LNKHIST |
Link History |
No |
When a record is changed or added to any of these tables in memory, a warning is issued that a bounce of the application is required before it will take effect.
When an application is brought up, the flex server will initialize upon the first validation of a transaction. The best transaction for this is a budget transaction. If the 'budget flex server is not initialized' error is ever issued, bounce the application and validate a budget transaction. An instance of the flex server exists for every instance (VLS) of the application, thus all must be bounced for any change or addition to one of the tables in memory.