If your enterprise maintained budgets in Oracle HRMS prior to Release 11i, you can migrate existing budgets to the new budget tables. Migrating an existing budget saves you data entry time when the components of a budget vary little from year to year.
As a prerequisite to migrating a budget, you must define the default budget set that you want to associate with this budget. Budget sets let you map a budget by fiscal period to HRMS elements and cost allocation flexfields.
See: Defining Budget Sets
Once you migrate a budget, you use the Budget Worksheet to copy and edit a new version of the budget.
You run the Migrate Budget Data process from the Submit Requests window. Alternatively, you can migrate budgets using the Budget Migration module available from the Navigator.
Select the Migrate Budget Data batch process in the Name field.
Click in the Parameters field to open the Parameters window.
Optional: select the Budget Name of the budget you are migrating.
Note: The budget migration process migrates all legacy budgets if you do not select a specific budget name.
Select the default budget set associated with this budget in the Budget Set Name field.
Choose OK.
Complete the batch process request and choose Submit.
Note: You can view any errors encountered during the batch process in the Process Log Navigator window.
Query the budget by name in the Budget Characteristics window.
You can now modify the properties of the migrated budget and create a new budget worksheet based on the values in the old budget.
Note: The application treats migrated budget data as pre-approved. You cannot route a migrated budget for workflow approval. Since migrated budgets have a primary entity of Open, you cannot use a migrated budget for purposes of position control.