Results for “per_assignment_budget_values_x”

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

Overview

The PER_ASSIGNMENT_BUDGET_VALUES_X view is a date-effective (or "X") view owned by the APPS schema and delivered as part of the PER — Human Resources product in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary role is to expose only the currently effective rows of assignment budget value records, filtering out historical and future-dated rows so that reporting, integration, and inquiry functions return the state of budget data as of the current system date. The "_X" suffix is the standard Oracle EBS convention for a date-tracked view layered over an "_F" (date-effective) base table.

Budget values captured at the assignment level (via ASSIGNMENT_BUDGET_VALUE_ID) support workforce budgeting, position control, and compensation planning. Consumers querying this view gain a business-date-safe view of budget allocations without having to write their own effective-date predicates, which reduces the risk of returning duplicate or stale rows across the assignment's effective history.

Underlying Base Objects

The view is defined over a single documented base object, the synonym PER_ASSIGNMENT_BUDGET_VALUES_F (which resolves to the APPS date-effective table of the same name). The relationship is a straight effective-dated filter: only rows whose EFFECTIVE_START_DATE is on or before TRUNC(SYSDATE) and whose EFFECTIVE_END_DATE is on or after TRUNC(SYSDATE) are surfaced. No joins, unions, or aggregations are applied, so cardinality between the view and the base table is a one-to-one subset.

Because the predicate is evaluated against SYSDATE at query time, the result set is dynamic: as time advances, rows transition in and out of the view independently of any data change. All columns of the base table are exposed unchanged; the view performs no column renaming or type conversion.

Key Columns

• ASSIGNMENT_BUDGET_VALUE_ID — Primary key of the budget value record; the identifier most users search for and the join key to related tables.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-effectivity range defining the row's validity. Only the row bracketing the current date is returned by this view.
• ASSIGNMENT_ID — Foreign key to the assignment (assignment record) the budget value belongs to.
• BUSINESS_GROUP_ID — The business group that owns the record; relevant for multi-organization security and partitioning.
• UNIT — The unit of measure in which the budget VALUE is expressed (for example, currency or FTE).
• VALUE — The budget amount for the assignment in the stated UNIT.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO (audit) columns.
• PROGRAM_UPDATE_DATE, PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID — Concurrent program context identifying the process that last touched the row.

Common Use Cases and Queries

Typical uses include point-in-time budget reporting, validation of current assignment budget allocations, and integration extracts that must reflect only active effectivity. A representative query returns current budget values for a given assignment:

• SELECT assignment_budget_value_id, assignment_id, unit, value, effective_start_date, effective_end_date FROM apps.per_assignment_budget_values_x WHERE assignment_id = :p_assignment_id;
• Filtering by business group: WHERE business_group_id = :p_bg_id to scope results within organization security.
• Joining to assignment tables on ASSIGNMENT_ID and to other budget-detail objects on ASSIGNMENT_BUDGET_VALUE_ID.
• Driving concurrent extracts by LAST_UPDATE_DATE for incremental integrations.

Because the view hard-codes the TRUNC(SYSDATE) predicate, it cannot return historical or future-dated rows; consumers requiring date-versioned history must query the base table PER_ASSIGNMENT_BUDGET_VALUES_F directly with their own effective-date parameters.