Oracle Assets Budgeting
Tags:
Oracle Assets Budgeting Introduction
Oracle Assets provides a few capital budgeting tools. Budget information can be entered manually by using the professional interface or uploaded from some external system through the
budget interface. Since budgets aren't usually created at the asset level, you create a budget book and enter budget assets there. You can run reports and project depreciation for the budget book. You can have many budget books.
Budget assets within a book are organized by category. The category provides depreciation rules for the budget asset depreciation projection calculations. You can enter budget assets at the major category level or for a full category flexfield combination. You can create budget assets (in the budget book) for categories and general ledger depreciation expense accounts. The date placed in service is the period specified for the budget amount.
The budget book is associated with a corporate book and shares the same calendar. Depreciation projections for the budget book will be calculated to the detail entered.
Several reports are available. The
Budget to Actual report compares actual to budgeted spending to plan by category and cost center for each balancing segment. The
Capital Spending report uses full category flexfield combinations. If you only budget at the major category level, depreciation projection rules are taken from the category flexfield definition for the major category where the other flexfield segments have a value of NONE. You may need to set up these NONE segment values and dummy flexfield combinations just for budgeting.
The
Upload Capital Budget window controls most of the budget transaction activities. From this window you can delete and existing budget, upload a budget from the budget interface, or create budget assets.
Budget Interface
The budget interface uses the FA_BUDGET_INTERFACE table in the database and Oracle assumes that you will use the SQL*Loader utility to move budget data from where you developed it to the interface table. The SQL*Loader utility is a technical tool and may require the assistance of the IT department. Since it is a database utility that can load data into the database, users who develop asset budgets are seldom given permission to use the utility. Oracle Corporation has published a sample SQL*Loader script in the Capital Budgeting chapter of the
Assets User Guide (file name is 120faug.pdf).
The budget process is as follows:
- Develop the budget (use a spreadsheet or some other budgeting software).
- Export the budget data out of the development system and move it to a file system where it can be loaded into Oracle Assets.
- Use SQL*Loader to insert the budget data into the FA_BUDGET_INTERFACE table.
- Use the Upload Capital Budget window to load the budget from the interface to the budget worksheet.
- Use the Upload Capital Budget window to attach the budget to a budget book.
As interfaces go, the FA_budget_interface table is quite simple. For ease of use, the external system where you develop the budget should correspond to the columns in the budget interface table. These columns include:
- Name of the budget book
- Period amounts (from the book's calendar up to twelve periods)
- Columns for each individual segment of the key accounting flexfield
- Columns for each individual segment of the asset category flexfield
Comments
Links
This Topic Is Referenced By These Topics:
Related Links: AssetBudgeting,
AssetDepreciation,
AssetSetUp,
FA12BudgetEnter,
FA12BudgetUpload,
OracleAssets,
WebStatistics
Was This Topic Useful to You?
Others rated this topic as shown. Please include your rating.
Collaborating Authors and Reviewers: BillDaley,
JimCrum