Results for “budget_unit1_percent”

50+ results




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

Overview

PQH_BUDGET_PERIODS is a Public Sector HR (PQH) table in the Oracle E-Business Suite database, owned by the HR schema. It stores period-level detail records that subdivide a budget definition across one or more Oracle HR time periods. Where PQH_BUDGET_DETAILS captures the parent budget line, PQH_BUDGET_PERIODS records the effective date range — expressed as a start time period and an end time period — over which that budget line applies, together with the associated percentage, value, and availability figures for up to three budget units.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries a surrogate primary key and descriptive measures that change over time and depend on parent entities, which is characteristic of satellite behavior rather than that of a pure hub or link. This classification is a heuristic suggestion derived from the FK topology, not an enforced EBS constraint.

The table is central to the budget periodization feature in Public Sector HR, enabling budgets to be spread, apportioned, or tracked across defined time periods and then consumed by higher-level budget set constructs.

Key Information Stored

The table exposes 22 documented columns. The most significant are:

Standard EBS audit columns such as LAST_UPDATE_DATE, CREATED_BY, and OBJECT_VERSION_NUMBER support concurrent update control and change tracking.

Common Use Cases and Queries

The most frequent access pattern is retrieving all period breakdowns for a given budget detail, or resolving a specific period row through the END_TIME_PERIOD_ID foreign key — the term most often associated with searches against this table. A representative query joining the parent budget detail and the time period definition is:

  • SELECT bp.budget_period_id, bp.start_time_period_id, bp.end_time_period_id, bp.budget_unit1_percent, bp.budget_unit1_value FROM pqh_budget_periods bp WHERE bp.budget_detail_id = :p_detail_id ORDER BY bp.start_time_period_id;
  • Reporting on budget allocation across time, aggregating BUDGET_UNIT*_VALUE by BUDGET_DETAIL_ID and period range.
  • Availability reporting that compares BUDGET_UNIT*_AVAILABLE against the allocated value to flag exhausted or over-allocated periods.
  • Integration extracts that feed downstream budget set or funding processes, keyed on BUDGET_PERIOD_ID.

Related Objects

  • PQH_BUDGET_DETAILS — parent budget line; joined on PQH_BUDGET_PERIODS.BUDGET_DETAIL_ID = PQH_BUDGET_DETAILS.BUDGET_DETAIL_ID.
  • PER_TIME_PERIODS — referenced twice, via START_TIME_PERIOD_ID and END_TIME_PERIOD_ID, supplying the period definition and dates.
  • PQH_BUDGET_SETS — child table referencing this table; PQH_BUDGET_SETS.BUDGET_PERIOD_ID points to PQH_BUDGET_PERIODS.BUDGET_PERIOD_ID.
  • PQH_BUDGET_PERIODS_PK and PQH_BUDGET_PERIODS_UK — the primary and unique indexes that enforce row uniqueness and the business key.

These relationships establish PQH_BUDGET_PERIODS as the connective layer between budget definitions, time periods, and budget sets within Public Sector HR.