Search Results per_budgets_v




Overview
Explore in AI Chat

Overview

PER_BUDGETS_V is a valid, APPS-owned database view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that belongs to the PER (Human Resources) product family. According to the ETRM documentation metadata, the view is designated as "Used to support user interface," indicating that it exists primarily as an OA Framework or Forms presentation-layer construct rather than as a standalone reporting entity. It presents budget records defined in the Human Resources module, enriching them with calendar and lookup information so that the user interface can render meaningful descriptive values in place of raw coded identifiers.

Because the view is a UI-support object, Oracle does not document it as a supported public API or a formal integration interface. Nevertheless, its underlying structure makes it useful for custom reporting and for developers who need to understand how HR budget data is exposed to the EBS front end. The view is defined with a simple join across three source objects, projecting a wide set of columns that mirror the base table plus a small number of derived columns.

Underlying Base Objects

The documented base objects referenced by the view are HR_API (PACKAGE), HR_LOOKUPS (VIEW), PAY_CALENDARS (SYNONYM), and PER_BUDGETS (SYNONYM). The view text itself confirms three of these directly:

HR_API is listed as a referenced package in the 12.2.2 metadata, although the visible view text does not call it directly; it is commonly associated with the PER_BUDGETS domain for budget validation logic.

Key Columns

The view exposes the full PER_BUDGETS column set plus derived columns. Notable columns include:

  • ROW_ID — the ROWID of the underlying PER_BUDGETS row, useful for direct row addressing.
  • BUDGET_ID — the primary identifier of the budget record.
  • BUSINESS_GROUP_ID — the HR business group that owns the budget; note the view text applies "+ 0" to force numeric handling.
  • NAME — the user-defined budget name.
  • UNIT and UNIT_MEANING — the budget measurement unit code and its decoded lookup meaning.
  • BUDGET_TYPE_CODE — classification of the budget.
  • PERIOD_SET_NAME and ACTUAL_PERIOD_TYPE — the accounting calendar and its period type.
  • ATTRIBUTE1–ATTRIBUTE20, ATTRIBUTE_CATEGORY — descriptive flexfield segments.
  • Audit and concurrent columns — WHO columns and the request/program columns used for concurrent program traceability.

Common Use Cases and Queries

Typical scenarios include reporting on HR budget definitions with decoded units and calendar types, and investigating how the UI resolves budget descriptions. A representative query is:

  • SELECT budget_id, name, unit_meaning, budget_type_code, period_set_name, actual_period_type FROM per_budgets_v WHERE business_group_id = :p_bg_id;
  • Joining to PER_BUDGETS or PER_BUDGET_TYPES on BUDGET_ID or BUDGET_TYPE_CODE for extended analysis.
  • Filtering by NAME for ad hoc operational reporting.

Because this is a UI-support view, treat its columns as subject to change across patches and avoid building permanent integrations upon it without confirming support status.