| | Documentation - Tables | Page 1 of 5 | Thursday, April 17, 2003 |
| Name | | Briefing Book Codes |
| Description | Briefing Book Codes contains comments to be place at bottom of Breifing Book report. |
| Name | | Budget Codes |
| Description | Category of Budget, ex: Initital Budget (1), In-year Budget (2) , Forecast Budget (3) |
| | Revenues are be represented here as Initital Revenue (4), etc. |
| | Expenditures are represented here too, because the user may have to alter actual expenditures to include |
| | more than just Corporate expenditures, i.e. programs taken over by other ministries/companies. |
| | Controls freeze for year and budget phase. |
| | Budget Codes is not just about budgets but about revenues and expenditures. |
| | Revenues are represented under its own set of Bufget Codes. |
| | Expenditures are represented under its own set of Bufget Codes. |
| Name | | Budget Non-Production |
| Description | Budget Scenarios. Contain budget data for Cost Centres. |
| | |
| | |
| | User Scenario Budget Modifications: |
| | |
| | For non-Budget Office/Officers users all changes/additions for budget details must be entered under a |
| | scenario number. Only Budget Office/Officers user can alter the Budget Production. |
| | The scenario numbers used are passed from users to branch controllers, to division controllers, and then to |
| | Budget Office/Officers for final examination, before making any changes production. The modification |
| | items already in production are replaced by the scenario modifications, if a corresponding items exists in |
| | production, otherwise the |
| | play scenario is appended to the Budget Production. The complete Budget Production Table is archived prior |
| | to this move by the system into the Budget Production Archive table for data recovery. |
| | Budget Office/Officers assigns a next production number to this process, along with comments. |
| | Budget Office/Officers can instigate this backup copy whenever it deems necessary. |
| | Since all modification items are monthly calenderized, whether the item has or has not been dittoed, the |
| | user must properly calanderize the amounts (a even 12 month spreading default is provided.) |
| | |
| | Before moving into production in cases where a scenario row will replace a production row, the system first |
| | compares the "production modified date" in the Budget Scenario with the Budget Production row to insure |
| | that the user is not updating a row that has changed since |
| | he worked on it. If so, the user is given the current problem and can re-sync with production for the row he |
| | wishes to alter. |
| Name | | Budget Production |
| Description | A Cost Centre (not having children) has budget modification transactions.Various budget stages (Rolled-up |
| | to parents.) |
| | A production number is indicated. |
| | The modification item and budget phase (budget code) for in-year, forecast, or initial year is indicated. |
| | Revenues are represented under its own set of Bufget Codes. |
| | Expenditures are represented under its own set of Bufget Codes. |
| Name | | Budget Production Archives |
| Description | Budget Production backups by production number. |
| | Production control users will be able to recover from past production version using this |
| | table. |
| |
| | Contain production budget data for Cost Centres. |
| Name | | Budget Production Tracking |
| Description | Record changes tracking for budget production. |
| Name | | Capital Codes |
| Description | For reporting instead of having an activity classed as capital or operating, this allows more than just 2 |
| | classifications of cost centres. |
| | |
| | |
| | |
| | Only Budget Office/Officers should have write access to these tables. Most will not change from year to |