Results for “per_budget_versions”

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

Overview

PER_BUDGET_VERSIONS is a Human Resources (PER) module table that identifies specific versions of an HR budget within Oracle E-Business Suite 12.1.1 and 12.2.2. The table resides in the HR schema and is documented as VALID in the ETRM repository. Each row represents a distinct, dated version of a budget, allowing organizations to maintain a historical and auditable record of budget revisions over time. The table sits at the intersection of organizational definitions and budget definitions, linking a budget to the business group that owns it while carrying its own version-level attributes such as effective dates and version numbering.

From a dimensional modeling perspective, the FK structure suggests a satellite-leaning classification. The table carries descriptive and tracking attributes (version number, dates, comments) that hang off the PER_BUDGETS hub and the HR_ALL_ORGANIZATION_UNITS hub. This heuristic should be treated as a modeling suggestion, not a documented fact.

Key Information Stored

The table contains 37 documented columns. The most significant are:

• BUDGET_VERSION_ID — the surrogate primary key, enforced by PER_BUDGET_VERSIONS_PK. It uniquely identifies each budget version.
• BUDGET_ID — foreign key to PER_BUDGETS, identifying the parent budget.
• BUSINESS_GROUP_ID — foreign key to HR_ALL_ORGANIZATION_UNITS, tying the version to an owning business group.
• VERSION_NUMBER — the sequential identifier distinguishing one version from another within the same budget.
• DATE_FROM and DATE_TO — the effective date range during which the version is active.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and request tracking columns indicating how and when the row was created or updated.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the standard EBS descriptive flexfield columns for extensible, customer-defined data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the WHO audit columns.
• COMMENTS — free-text annotation for the version.

The only documented unique index is PER_BUDGET_VERSIONS_PK on BUDGET_VERSION_ID, which serves as the business-key candidate for uniqueness enforcement. No additional unique index on BUDGET_ID combined with VERSION_NUMBER is documented.

Common Use Cases and Queries

Typical usage centers on reporting the current or historical version of a budget and joining version details to element-level amounts. A common query retrieves all versions for a given budget:

SELECT bv.budget_version_id, bv.version_number, bv.date_from, bv.date_to, bv.comments FROM per_budget_versions bv WHERE bv.budget_id = :p_budget_id ORDER BY bv.version_number;

To identify the currently active version, filtering on DATE_FROM and DATE_TO against SYSDATE is standard. Line-level reporting joins to PER_BUDGET_ELEMENTS via BUDGET_VERSION_ID to obtain the elements associated with each version. Audit and troubleshooting queries frequently join to FND_CONCURRENT_REQUESTS using REQUEST_ID to trace the process that created a version. Flexfield consumers read ATTRIBUTE_CATEGORY and the ATTRIBUTE1–20 columns to expose customer-defined fields in reports.

Related Objects

• PER_BUDGETS — parent table; join on PER_BUDGET_VERSIONS.BUDGET_ID = PER_BUDGETS.BUDGET_ID.
• HR_ALL_ORGANIZATION_UNITS — business group owner; join on PER_BUDGET_VERSIONS.BUSINESS_GROUP_ID.
• PER_BUDGET_ELEMENTS — child table referencing this table via BUDGET_VERSION_ID; holds element-level budget detail per version.
• FND_CONCURRENT_REQUESTS — concurrent request audit via REQUEST_ID.
• PER_BUDGET_VERSIONS_PK — the primary key index on BUDGET_VERSION_ID.