Results for “budget_id”

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

Overview

HR.PQH_BUDGETS_EFC is a table in the Oracle E-Business Suite 12.1.1 / 12.2.2 database, residing in the HR schema and belonging to the PQH – Public Sector HR product family. Per the ETRM documentation, it is a copy of the PQH_BUDGETS table that is populated by the EFC (Euro as Functional Currency) process. Its purpose is to hold a parallel set of budget rows whose monetary amounts have been restated into the euro, so that public-sector organizations operating under the euro-as-functional-currency model can report and reconcile budget data without altering the operational budget records in PQH_BUDGETS.

From a heuristic Data Vault modeling perspective, the object is classified as satellite-leaning. This reflects its structure: it carries a composite primary key that is also a foreign-key reference to an action/process table, and it stores descriptive, process-generated attributes rather than acting as an independent business hub. A Data Vault practitioner would therefore treat it as a satellite attached to HR_EFC_ACTIONS (and logically to the underlying budget entity), capturing the currency-restated state produced by each EFC run.

Key Information Stored

The ETRM metadata documents three physical columns for the 12.2.2 schema. The essential elements are:

• BUDGET_ID — The identifier of the budget record. Together with EFC_ACTION_ID it forms the composite primary key PQH_BUDGETS_EFC_PK. It correlates each restated row back to the originating budget in PQH_BUDGETS.
• EFC_ACTION_ID — The identifier of the EFC action (process run) that produced the row. It is a foreign key to HR_EFC_ACTIONS.EFC_ACTION_ID and distinguishes successive restatement executions, so the same budget can appear multiple times across different EFC runs.
• CURRENCY_CODE — The currency in which the copied budget amounts are expressed. In the context of this table it typically reflects the euro (EFC) currency designation applied by the conversion process.

Documentation does not identify any unique business-key index separate from the composite primary key; BUDGET_ID plus EFC_ACTION_ID is the sole documented uniqueness constraint. No additional descriptive attributes appear in the ETRM extract, so the table is intentionally narrow, functioning as a keyed restatement mapping alongside columns inherited from PQH_BUDGETS.

Common Use Cases and Queries

Typical scenarios involve reconciling euro-restated budgets against their source rows and reporting on specific EFC runs. Representative query patterns include:

• Isolating all restated rows created by a particular EFC action:

SELECT b.budget_id, b.currency_code
FROM   hr.pqh_budgets_efc b
WHERE  b.efc_action_id = :p_action_id;

• Comparing original and restated budgets for the same budget identifier, joining back to PQH_BUDGETS on BUDGET_ID.
• Auditing EFC history by joining HR_EFC_ACTIONS to determine when and by which run each row was generated.
• Feeding public-sector budget reports that must be expressed in the euro functional currency, restricted by CURRENCY_CODE.

Related Objects

The FK and PK metadata identifies the following significant relationships:

• HR_EFC_ACTIONS — Referenced via PQH_BUDGETS_EFC.EFC_ACTION_ID → HR_EFC_ACTIONS; the parent action/process record for each restatement run.
• PQH_BUDGETS — The source table whose rows are copied and restated; joined on BUDGET_ID.
• PQH_BUDGETS_EFC_PK — The composite primary key constraint (BUDGET_ID, EFC_ACTION_ID) enforcing row uniqueness.
• Other EFC-suffixed copies in the PQH family (for example budget line and budget detail counterparts) that follow the same action-keyed restatement pattern.

Because the schema is deliberately minimal, most meaningful reporting requires joining to PQH_BUDGETS and HR_EFC_ACTIONS rather than relying on this table alone.