Results for “worksheet_detail_id”

50+ results




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

Overview

PQH_WORKSHEET_DETAILS_EFC is a table owned by the HR schema within the Public Sector HR (PQH) product family in Oracle EBS 12.1.1 and 12.2.2. It is described in the ETRM metadata as a copy of the PQH_WORKSHEET_DETAILS table, populated by the EFC (Euro as Functional Currency) process. The table exists to preserve worksheet budget detail rows in a euro-denominated or EFC-converted form, which allows Public Sector HR customers operating under euro functional currency requirements to retain historical and parallel representations of worksheet data without mutating the primary transactional worksheet records. The EFC process writes into this table, and the data is therefore best treated as a derived, process-populated copy rather than a primary source of truth.

From a Data Vault modeling perspective, the provided heuristic classification labels this object as satellite-leaning. This is consistent with its structure: it holds descriptive and quantitative attributes tied to a parent worksheet detail and to an EFC action event, rather than serving as a pure hub of business keys or as a link between two independent hubs. Modelers should treat it as a satellite keyed by a composite of the worksheet detail identifier and the EFC action identifier.

Key Information Stored

The table contains nine documented columns. The most consequential are the following:

  • WORKSHEET_DETAIL_ID — the identifier that ties each row back to a worksheet detail record. It participates in the composite primary key and is the column most commonly used in queries and joins.
  • EFC_ACTION_ID — the identifier of the EFC action that produced the row. It is the second component of the composite primary key and the sole foreign key column documented for this table.
  • CURRENCY_CODE — the currency in which the recorded amounts are expressed, typically reflecting the euro functional currency context of the EFC process.
  • BUDGET_UNIT1_VALUE, BUDGET_UNIT2_VALUE, BUDGET_UNIT3_VALUE — the budgeted amounts for each of the three budget units associated with the worksheet detail.
  • BUDGET_UNIT1_AVAILABLE, BUDGET_UNIT2_AVAILABLE, BUDGET_UNIT3_AVAILABLE — the available (remaining) budget amounts for the same three units, allowing comparison of budgeted versus available balances.

The surrogate primary key is defined by the constraint PQH_WORKSHEET_DETAILS_EFC_PK over the column pair (WORKSHEET_DETAIL_ID, EFC_ACTION_ID). Because EFC_ACTION_ID is itself a foreign key to the EFC actions table, WORKSHEET_DETAIL_ID functions as the principal business-key candidate, while the pair uniquely identifies a versioned row per EFC action.

Common Use Cases and Queries

Typical usage centers on reconciliation and reporting of euro-converted worksheet budget data. A common pattern joins the EFC copy to its source rows to compare converted values against the original worksheet detail amounts.

  • Retrieving all EFC rows for a given worksheet detail: SELECT * FROM hr.pqh_worksheet_details_efc WHERE worksheet_detail_id = :p_detail_id;
  • Joining to the EFC action to identify which run produced the row: SELECT e.worksheet_detail_id, e.currency_code, a.* FROM hr.pqh_worksheet_details_efc e, hr.hr_efc_actions a WHERE e.efc_action_id = a.efc_action_id;
  • Comparing budgeted versus available amounts across the three budget units for a reporting period.
  • Auditing the EFC conversion history by listing all EFC action identifiers associated with a worksheet detail.

Reporting consumers should note that the table is populated by a background process; as a result, queries should not assume that a row exists for every worksheet detail until the EFC process has completed for the relevant action.

Related Objects

The most significant relationships documented for this object are:

  • HR_EFC_ACTIONS — referenced through PQH_WORKSHEET_DETAILS_EFC.EFC_ACTION_ID. This is the only foreign key documented and establishes the parent action context for each row.
  • PQH_WORKSHEET_DETAILS — the source table from which this EFC copy is derived, sharing the WORKSHEET_DETAIL_ID business key.
  • PQH_WORKSHEET_DETAILS_EFC_PK — the primary key constraint over (WORKSHEET_DETAIL_ID, EFC_ACTION_ID), which constrains uniqueness and indexes the access path used by most queries.
  • Budget unit and worksheet header objects within the PQH module that participate in budget worksheet processing and are logically related through WORKSHEET_DETAIL_ID.

Together, these objects place PQH_WORKSHEET_DETAILS_EFC within the EFC conversion chain spanning the worksheet detail source, the EFC action, and dependent reporting.