Results for “end_time_period_id”

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

Overview

PQH_WORKSHEET_PERIODS is a table in the HR schema owned by the Public Sector HR (PQH) module of Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. It stores period-wise details of transaction data for a budget version, acting as the finest-grained time-sliced representation within the Public Sector budgeting worksheets model. Where a worksheet detail defines a line of budget or transaction activity, this table anchors that line to discrete start and end time periods from the enterprise calendar and captures the budget unit amounts, percentages, and availability facts applicable to each interval.

The table carries 23 documented columns and is classified heuristically — based on its foreign key topology — as satellite-leaning in a Data Vault modelling sense. It is not a hub or link: it hangs off PQH_WORKSHEET_DETAILS (its parent), carries descriptive and measured attributes, and is itself referenced by PQH_WORKSHEET_BUDGET_SETS. This satellite role reflects its purpose: periodic quantitative attributes attached to a stable worksheet detail key.

Key Information Stored

• WORKSHEET_PERIOD_ID — the system-generated surrogate primary key (PQH_WORKSHEET_PERIODS_PK) uniquely identifying each period row.
• WORKSHEET_DETAIL_ID — foreign key to PQH_WORKSHEET_DETAILS, tying the period row to its parent worksheet line.
• START_TIME_PERIOD_ID and END_TIME_PERIOD_ID — foreign keys to PER_TIME_PERIODS, defining the start and end of the effective period.
• BUDGET_PERIOD_ID — the budget period associated with the row.
• BUDGET_UNIT1_PERCENT / UNIT2_PERCENT / UNIT3_PERCENT — the percentage split for each of up to three budget units.
• BUDGET_UNIT1_VALUE / UNIT2_VALUE / UNIT3_VALUE — the monetary or numeric value assigned to each budget unit.
• BUDGET_UNIT1_VALUE_TYPE_CD / UNIT2_ / UNIT3_ — coded value types describing how each unit value is interpreted.
• BUDGET_UNIT1_AVAILABLE / UNIT2_ / UNIT3_ — availability indicators for each budget unit.
• Standard WHO/audit columns — OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

The unique business-key candidate PQH_WORKSHEET_PERIODS_UK spans START_TIME_PERIOD_ID, END_TIME_PERIOD_ID, and WORKSHEET_DETAIL_ID, guaranteeing that a given worksheet detail cannot repeat the same effective period.

Common Use Cases and Queries

Typical scenarios include budget-versus-availability reporting per period, reconstructing budget version timelines, and reconciling budget sets against worksheet periods. A representative join returns period rows alongside their worksheet detail and calendar boundaries:

• SELECT p.WORKSHEET_PERIOD_ID, p.WORKSHEET_DETAIL_ID, p.START_TIME_PERIOD_ID, p.END_TIME_PERIOD_ID, p.BUDGET_UNIT1_VALUE, p.BUDGET_UNIT1_PERCENT FROM HR.PQH_WORKSHEET_PERIODS p WHERE p.WORKSHEET_DETAIL_ID = :detail_id ORDER BY p.START_TIME_PERIOD_ID;
• Join to PER_TIME_PERIODS on both START_TIME_PERIOD_ID and END_TIME_PERIOD_ID to resolve calendar dates for period-over-period analysis.
• Join to PQH_WORKSHEET_BUDGET_SETS via WORKSHEET_PERIOD_ID to report budget set composition.
• Aggregate BUDGET_UNIT*_VALUE and BUDGET_UNIT*_AVAILABLE to produce availability roll-ups by period for a budget version.

Related Objects

• PQH_WORKSHEET_DETAILS — parent table; join on WORKSHEET_DETAIL_ID.
• PER_TIME_PERIODS — calendar periods; join on START_TIME_PERIOD_ID and END_TIME_PERIOD_ID.
• PQH_WORKSHEET_BUDGET_SETS — child table referencing WORKSHEET_PERIOD_ID.
• Related PQH worksheet and budget version objects that consume worksheet detail and period data for Public Sector budgeting flows.