1. How do I set up position budgeting?
  2. Tips for Configuring Position Budgeting

Tips for Configuring Position Budgeting

Here are some tips for configuring position budgeting:

  • Allocate By on enterprise can’t be changed if budget definitions already exist.

  • When the ORA_PER_POSITION_BUDGETING_ENABLED profile option is set to No, you can't load the budget data using HDL.

  • When the ORA_PER_POSITION_BUDGETING_ENABLED profile option is set to Yes, you can load the budget data using HDL only if budget data doesn't exist already for the provided budget period.
  • A budget period is currently for one calendar year.

  • Budgetary Year will be an input in the HDL file and will be used along with the Budget Period Start Day and Budget Period Start Month segments on the enterprise to identify and populate the Budget Period Start Date.

  • Budget Period End Date is always one calendar year after the Budget Period Start Date.

  • If you update your budget definition in between the budget period, then only the allocations can be modified.
  • The current budget period’s budget definition won't be rolled over automatically to the next calendar year.

  • Budget definition data for a maximum of 2 budget periods can exist in the table at any given point in time - Past and Current, Current and Future, or only Current.

  • If the budget table has data for 2 budget periods at a given point of time, then you need to delete the budget data for one period in order to load the third period’s budget definitions.

  • Budget Amount Currency on the position will be defaulted from the Budget Amount Currency specified at the enterprise level, and it won’t be editable.

  • If Budgeted Position is enabled on the position and Allocate By includes Location, then the Location field on the position will be required.

  • For calculating the remaining budget values, only those active and budgeted positions will be considered, which have an approved hiring status or a frozen hiring status with at least 1 incumbent as of the budget period end date. While calculating the remaining balance, the position type isn’t considered, irrespective of whether the type is Single, Shared, or Pooled.

  • Validation will be applicable on all Redwood and responsive position pages.

  • Validations and calculations of remaining allocations will take place only if a budget definition is present for the calendar year in which the current date falls.

  • The Remaining Budget, Remaining FTE, and Remaining Headcount attributes are available only on the position details section of Redwood UIs.

  • If the allocation for the next budget period is less than what you're already utilizing in the current budget period, then once the next budget period starts, you will start seeing the warnings or errors while creating or editing the positions. For example: In FY 2022-23, the allocation for FTE is 200 and you have utilized 150. In the next FY 2023-24, if the new allocation for FTE is 120, then the FTE will be over budget by 30. So, you will see warnings or errors while creating or editing positions.
  • Approval notifications will always display the remaining balance percentage for the proposed changes of FTE, Headcount, or Budget Amount.
  • Enterprise configuration related to budgeting is also migrated when you migrate your enterprise configuration using the Functional Setup Manager (FSM) export and import functionality.

  • Position budget data isn't migrated using the export and import functionality in Functional Setup Manager (FSM).

  • Database Items (DBI) and User Entities (UE) aren't yet available for position budget data.