Results for “per_assignment_budget_values_f”

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

Overview

PER_ASSIGNMENT_BUDGET_VALUES_F is a Human Resources (PER) table residing in the HR schema of Oracle E-Business Suite. It stores budget values associated with an assignment, allowing organizations to associate monetary or unit-based budget allocations directly to specific employee assignments. This supports workforce budgeting, position control, and cost-planning processes where an assignment is funded against a defined budget envelope. The table is date-tracked, employing effective start and end dates to preserve historical budget records, consistent with the datetracked design pattern used throughout Oracle HRMS.

From a Data Vault modeling perspective, the mined FK structure suggests this object is satellite-leaning. This classification is offered as a suggestion rather than a definitive model: the table attaches descriptive, time-variant attributes (budget values) to a parent assignment business key, which is characteristic of satellite behavior rather than an independent hub or a relationship link.

Key Information Stored

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

• ASSIGNMENT_BUDGET_VALUE_ID — Surrogate primary key column, forming part of the unique index PER_ASSIGNMENT_BUDGET_VALU_PK.
• ASSIGNMENT_ID — Identifies the assignment to which the budget value applies; part of the UK2 unique index.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-tracking columns delimiting the validity of each budget row; present in both unique indexes.
• UNIT — The budget unit identifier; part of the UK2 business-key candidate (ASSIGNMENT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, UNIT).
• VALUE — The monetary or numeric budget value allocated to the assignment for the given unit.
• BUSINESS_GROUP_ID — The business group context; carries a foreign key to HR_ALL_ORGANIZATION_UNITS.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program and audit metadata recording the process that last modified the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns.
• OBJECT_VERSION_NUMBER — Optimistic locking support for concurrent updates.

The surrogate key (ASSIGNMENT_BUDGET_VALUE_ID with dates) differs from the business-key candidates captured by UK2, which enforce uniqueness across assignment, date range, and unit.

Common Use Cases and Queries

Typical uses include assignment-level budget reporting, cost allocation validation, and integration with Oracle Grants or Project Costing. A common pattern retrieves the currently effective budget for an assignment:

• Filter by ASSIGNMENT_ID and a SYSDATE between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to obtain the active budget value.
• Join to HR_ALL_ORGANIZATION_UNITS on BUSINESS_GROUP_ID to resolve the business group name.
• Aggregate VALUE by UNIT or ASSIGNMENT_ID for total budget allocation reports.
• Query historical rows by relaxing the effective-date predicate to trace budget changes over time.

Sample SQL: SELECT assignment_id, unit, value FROM per_assignment_budget_values_f WHERE assignment_id = :p_assignment_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Related Objects

• HR_ALL_ORGANIZATION_UNITS — Referenced via BUSINESS_GROUP_ID; resolves the business group owning the budget record.
• PER_ASSIGNMENTS_F — Parent assignment entity keyed by ASSIGNMENT_ID; provides assignment and person context.
• PER_ALL_PEOPLE_F — Person-level details reachable through the assignment relationship for reporting.
• PER_ASSIGNMENT_BUDGET_VALUES — The date-tracked view (non-_F) exposing the same data through the datetrack framework.
• PA / GL integration tables — Downstream cost and budget consumers that may reference assignment budget values through assignment identifiers.

Because the table is datetracked, queries should always consider effective dates to avoid returning superseded budget rows.