Results for “per_budget_values”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PER_BUDGET_VALUES is a Human Resources (PER) product table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the planned HR budget values associated with specific budget elements over defined time periods. Within the Oracle HRMS budgeting model, this table represents the transactional fact layer where budget amounts and associated descriptive flexfield information are persisted against a budget element and a time period, scoped to a business group.

The table is documented with 76 columns and a single unique index, PER_BUDGET_VALUES_PK, defined on BUDGET_VALUE_ID. Three foreign keys anchor each row: BUSINESS_GROUP_ID references HR_ALL_ORGANIZATION_UNITS, BUDGET_ELEMENT_ID references PER_BUDGET_ELEMENTS, and TIME_PERIOD_ID references PER_TIME_PERIODS. From a heuristic Data Vault modeling perspective, PER_BUDGET_VALUES classifies as a link — it connects a budget element, a time period, and a business group while carrying descriptive and numeric measures. This classification is a modeling suggestion derived from the FK topology, not a declarative EBS construct.

Key Information Stored

The surrogate primary key is BUDGET_VALUE_ID, the sole column of the unique index PER_BUDGET_VALUES_PK. The most significant business and descriptive columns include:

• BUDGET_VALUE_ID — Surrogate primary key uniquely identifying each budget value row.
• BUSINESS_GROUP_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS, scoping the budget value to a business group.
• BUDGET_ELEMENT_ID — Foreign key to PER_BUDGET_ELEMENTS, identifying the budgeted element.
• TIME_PERIOD_ID — Foreign key to PER_TIME_PERIODS, identifying the period to which the value applies.
• VALUE — The planned numeric budget amount for the element and period.
• INFORMATION_CATEGORY — Classifies the type of budget information recorded against the row.
• BUDGET_INFORMATION1 through BUDGET_INFORMATION30 — A wide descriptive flexfield segment area capturing category-specific budget attributes.
• ATTRIBUTE_CATEGORY — Context for the standard descriptive flexfield.
• ATTRIBUTE1 through ATTRIBUTE30 — Standard DFF segments for client-specific extensions.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program and request audit context for rows created by batch processes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking row creation and modification.

Common Use Cases and Queries

Typical usage centers on budget planning and variance reporting. Analysts join PER_BUDGET_VALUES to PER_BUDGET_ELEMENTS and PER_TIME_PERIODS to produce budget-versus-actual comparisons, and to HR_ALL_ORGANIZATION_UNITS to roll values up by business group.

A representative query retrieves budget values for a business group and period:

• SELECT bv.budget_value_id, be.name, tp.period_name, bv.value FROM per_budget_values bv, per_budget_elements be, per_time_periods tp WHERE bv.budget_element_id = be.budget_element_id AND bv.time_period_id = tp.time_period_id AND bv.business_group_id = :p_bg_id;

Aggregation by element supports annualized budget rollups, while filtering on REQUEST_ID or PROGRAM_ID isolates rows produced by a specific concurrent request for reconciliation after a batch load. Queries against INFORMATION_CATEGORY and the BUDGET_INFORMATION flexfield segments support category-specific reporting where standard columns are insufficient.

Related Objects

The following objects are most directly related through documented foreign keys and the surrounding budgeting model:

• PER_BUDGET_ELEMENTS — Referenced via BUDGET_ELEMENT_ID; defines the budget element each value quantifies.
• PER_TIME_PERIODS — Referenced via TIME_PERIOD_ID; supplies the period against which values are planned.
• HR_ALL_ORGANIZATION_UNITS — Referenced via BUSINESS_GROUP_ID; provides the business group and organizational context.
• PER_BUDGET_VALUES_PK — The unique index enforcing BUDGET_VALUE_ID and serving as the access path for single-row lookups.
• FND_CONCURRENT_REQUESTS — Correlates REQUEST_ID and PROGRAM_APPLICATION_ID to the concurrent process that populated rows.
• FND_APPLICATION — Resolves PROGRAM_APPLICATION_ID to the owning application.

Collectively these relationships position PER_BUDGET_VALUES as the central transactional store for planned HR budget amounts, linking budget definitions, calendar periods, and organizational units within the PER schema.