Search Results unit_meaning




Overview
Explore in AI Chat

Overview

APPS.PER_BUDGETS_V is a reporting and integration view in Oracle E-Business Suite that exposes budget definitions maintained in the Oracle HRMS (Human Resources Management System) module. It is defined over the PER_BUDGETS base entity and enriches each budget record with calendar and lookup information. The view is owned by the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2, where it supports budget-related inquiries, concurrent reporting, and downstream integrations that require a single flattened source of budget metadata.

In the HRMS budgeting model, a budget represents a named container for monetary or non-monetary allocations tied to a period set and a business group. The view surfaces the budget identifier, descriptive attributes, flexfield (DDF) segments, audit columns, and the period set name, along with derived descriptive fields. Notably, it resolves the cryptic UNIT lookup code into a human-readable value via UNIT_MEANING, which is the column users most frequently search for. Because budgets feed budgeted position and budgeted assignment calculations, this view is a convenient, denormalized entry point for any process that needs budget header information without joining PER_BUDGETS to lookup tables manually.

Underlying Base Objects

The view is defined with the following FROM clause, which reveals the documented base objects:

  • PER_BUDGETS (synonym) — the driving table, aliased BUD, supplying all core budget columns including BUDGET_ID, NAME, UNIT, budget type, and audit fields.
  • PAY_CALENDARS (synonym) — aliased CAL, joined on PERIOD_SET_NAME to return ACTUAL_PERIOD_TYPE and validate the period set associated with the budget.
  • HR_LOOKUPS (view) — aliased LK, outer-joined on UNIT = LOOKUP_CODE with LOOKUP_TYPE = 'BUDGET_MEASUREMENT_TYPE', which supplies the MEANING value projected as UNIT_MEANING.
  • HR_API (package) — documented as a referenced object, typically involved in the maintaining forms and validation logic that populate the underlying tables.

The join to PAY_CALENDARS is an equijoin, so a budget with a period set name not present in the calendar hierarchy would be excluded. The lookup join is an outer join (note the (+) operator), meaning budgets whose UNIT code has no matching lookup row still appear, with UNIT_MEANING returned as null.

Key Columns

  • ROW_ID — the BUD.ROWID of the underlying PER_BUDGETS row, useful for locking or row-level references.
  • BUDGET_ID — the unique surrogate key for the budget.
  • NAME — the user-defined budget name.
  • BUSINESS_GROUP_ID — returned as BUD.BUSINESS_GROUP_ID + 0, the standard HRMS idiom that prevents index use on this column and enforces a positive numeric value.
  • UNIT / UNIT_MEANING — UNIT holds the lookup code (for example, the measurement type such as monetary or hours); UNIT_MEANING is the translated, user-facing description drawn from HR_LOOKUPS for lookup type BUDGET_MEASUREMENT_TYPE. This is the descriptive value most frequently requested by report authors.
  • BUDGET_TYPE_CODE — classifies the budget, typically distinguishing budgeted and non-budgeted varieties.
  • PERIOD_SET_NAME / ACTUAL_PERIOD_TYPE — the accounting calendar and its period type, resolved from PAY_CALENDARS.
  • COMMENTS — free-text description of the budget.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the developer descriptive flexfield (DDF) segments.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, plus the concurrent manager columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include LOV populations in budget entry forms, period-set validation reports, budget-to-assignment reconciliation extracts, and listing all budgets with their measurement types for HRMS reporting. Because the view already resolves UNIT to UNIT_MEANING, it eliminates the need for callers to hard-code the BUDGET_MEASUREMENT_TYPE lookup join. A representative query selecting the most commonly requested columns is:

SELECT b.budget_id,
       b.name,
       b.unit,
       b.unit_meaning,
       b.budget_type_code,
       b.period_set_name,
       b.actual_period_type
FROM   apps.per_budgets_v b
WHERE  b.unit_meaning IS NOT NULL
ORDER  BY b.name;

To filter by business group, add WHERE b.business_group_id = :p_business_group_id. To identify budgets whose unit does not resolve to a lookup meaning, query WHERE b.unit_meaning IS NULL, which returns outer-join misses. When joining to budget lines or budgeted position detail, use BUDGET_ID as the foreign key and restrict by PERIOD_SET_NAME to limit the result set to the relevant calendar. Reports should generally filter on PERIOD_SET_NAME and BUSINESS_GROUP_ID to avoid full scans, as the view itself contains no WHERE predicates beyond the joins and cannot be tuned with a predicate pushdown on the outer-joined lookup. Always query it through the APPS schema to honor synonym resolution and secured access in a multi-org deployment.