Search Results per_budgets




Overview
Explore in AI Chat

Overview

The PER_BUDGETS table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically in versions 12.1.1 and 12.2.2. It serves as the master definition table for all HR budgets created within the system. A budget in this context is a financial plan for human resource costs, typically defined for a specific organizational unit and time period. The table's primary role is to store the high-level, static attributes of a budget, such as its name, type, and associated business group. It acts as a parent record, with detailed financial versions and values stored in related child tables. This structure is fundamental for workforce cost planning, forecasting, and analysis within Oracle HRMS.

Key Information Stored

The table stores the foundational metadata for each budget definition. Key columns, as indicated by the provided metadata, include the system-generated primary key BUDGET_ID and the unique composite key formed by NAME and BUSINESS_GROUP_ID, ensuring budget names are unique within a business group. Other critical columns, inferred from standard HR budget functionality, typically include BUDGET_TYPE (e.g., headcount, salary), START_DATE, END_DATE, CURRENCY_CODE, and STATUS. The foreign key column PERIOD_SET_NAME links the budget to a specific accounting calendar in the PAY_CALENDARS table, defining its fiscal time periods. The BUSINESS_GROUP_ID foreign key anchors the budget to a specific organizational entity within HR_ALL_ORGANIZATION_UNITS.

Common Use Cases and Queries

This table is central to queries that list, audit, or report on budget definitions. Common scenarios include generating a master list of all active budgets for a business group or validating budget setups. A typical reporting query would join PER_BUDGETS with HR_ALL_ORGANIZATION_UNITS to display the business group name and with PAY_CALENDARS for the calendar details. For example:

  • Listing Budgets: SELECT pb.name, pb.budget_type, hou.name business_group, pc.period_set_name FROM per_budgets pb, hr_all_organization_units hou, pay_calendars pc WHERE pb.business_group_id = hou.organization_id AND pb.period_set_name = pc.period_set_name AND pb.business_group_id = :p_bg_id;
  • Data Integrity Checks: Queries often validate that all budgets have a valid business group and calendar, or identify budgets without any associated versions in the PER_BUDGET_VERSIONS table.

Related Objects

As per the documented foreign keys, PER_BUDGETS has critical relationships with several other EBS objects. It is a parent table to PER_BUDGET_VERSIONS, which stores different iterations or snapshots (e.g., original, revised) of the budget's financial figures. It references HR_ALL_ORGANIZATION_UNITS for the business group context and PAY_CALENDARS for the time period structure. In practical implementation, it is also commonly related to tables like PER_BUDGET_VALUES (storing actual line-item values) and is accessed via standard Oracle HRMS APIs for budget creation and maintenance, ensuring data integrity and business rule enforcement.