Results for “pqh_budgets_v”

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

Overview

PQH_BUDGETS_V is an APPS-owned database view within the Oracle E-Business Suite Public Sector HR (PQH) product. It exposes budget definition data maintained by the Position Control and budgeting features of Public Sector HR, presenting a denormalized, business-friendly projection of the underlying PQH_BUDGETS base entity. The view resolves internal coded values into descriptive lookups and joins organizational, calendar, and ledger reference data, so that reporting tools, concurrent programs, and integration interfaces can consume budget information without replicating decode logic.

The view is validated in both Oracle EBS 12.1.1 and 12.2.2. Its principal role is to provide a stable read interface over budget records that participates in the transfer of budget amounts to Oracle General Ledger through the TRANSFER_TO_GL_FLAG and GL_SET_OF_BOOKS_ID columns. Because budgets must ultimately map to a ledger, the view's exposure of the GL set of books identifier is central to financial reconciliation and to any query that links HR budgeting to GL accounting data.

Underlying Base Objects

The documented base objects for PQH_BUDGETS_V are:

• PQH_BUDGETS (synonym) — the driving table containing budget definitions and the GL_SET_OF_BOOKS_ID column.
• GL_SETS_OF_BOOKS (view) — source of the ledger name exposed as GL_SOB_NAME.
• PAY_CALENDARS_V (view) — provides the period set and actual period type used for budget periods.
• PER_ORGANIZATION_STRUCTURES and PER_ORG_STRUCTURE_VERSIONS (synonyms) — supply organization structure name and version number.
• PER_SHARED_TYPES_VL (view) — resolves the three budget unit definitions (BUDGET_UNIT1/2/3).
• PQH_DFLT_BUDGET_SETS (synonym) — supports default budget set logic.
• HR_GENERAL and PQH_UTILITY (packages) — supply DECODE_LOOKUP, DECODE_ORGANIZATION, and related PL/SQL functions used to translate codes into meanings.

The view therefore joins transactional budget data with HR organizational and payroll calendar reference data, and with General Ledger ledger definitions.

Key Columns

• BUDGET_ID / BUDGET_NAME — primary identifier and user-facing name of the budget.
• GL_SET_OF_BOOKS_ID / GL_SOB_NAME — the ledger identifier and its resolved name; the pivot column for GL integration and the object of the "gl_set_of_books_id" search.
• TRANSFER_TO_GL_FLAG — indicates whether budget amounts are transferred to General Ledger.
• STATUS — workflow or lifecycle status of the budget record.
• PERIOD_SET_NAME / PERIOD_TYPE / BUDGET_START_DATE / BUDGET_END_DATE — calendar and effective dating of the budget.
• BUDGETED_ENTITY / BUDGETED_ENTITY_CD, BUDGET_STYLE / BUDGET_STYLE_CD — decoded lookup values describing budget scope and style.
• ORG_STRUCTURE / VERSION / START_ORGANIZATION / START_ORGANIZATION_ID — organizational context of the budget.
• CURRENCY_CODE — currency in which budget amounts are held.
• BUDGET_UNIT1/2/3 and their _ID and _AGGREGATE columns — configurable budget unit definitions and aggregation descriptions.
• POSITION_CONTROL_FLAG — indicates positional control applicability.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support auditing and optimistic locking.

Common Use Cases and Queries

A frequent requirement is listing budgets and their associated General Ledger ledger, typically filtered by ledger to reconcile HR budgeting with GL. The following query demonstrates filtering on GL_SET_OF_BOOKS_ID:

• SELECT budget_id, budget_name, gl_set_of_books_id, gl_sob_name, status FROM apps.pqh_budgets_v WHERE gl_set_of_books_id = :p_sob_id;
• SELECT budget_name, period_set_name, budget_start_date, budget_end_date, currency_code FROM apps.pqh_budgets_v WHERE transfer_to_gl_flag = 'Y' AND status = 'ACTIVE';
• SELECT b.budget_name, b.org_structure, o.version, b.start_organization FROM apps.pqh_budgets_v b WHERE b.business_group_id = :p_bg_id ORDER BY b.budget_name;

These patterns support budget reconciliation reports, GL transfer monitoring, and integration extracts. Because the view encapsulates decode logic and joins, it is preferable to direct queries against the base PQH_BUDGETS table for reporting, ensuring consistent and business-meaningful output.