Results for “component_id”

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

Overview

The PER_PAY_PROPOSAL_COMPONENT_EFC table is a Payroll (PAY) module object residing in the HR schema of the Oracle E-Business Suite. It functions as an administrative or configuration data store associated with salary and pay proposal processing. The "EFC" suffix in Oracle EBS naming conventions typically denotes an "Extra Functionality Component" or supplementary control table that supports the core pay proposal engine. In the payroll business flow, pay proposals represent suggested changes to an employee's compensation — such as salary increases, bonus allocations, or grade adjustments — and their individual monetary components are captured and itemized through structures such as this one.

The ETRM metadata classifies this object, via heuristic mining of its foreign-key structure, as standalone from a Data Vault modeling perspective. This indicates that the table does not display strong hub or link characteristics; it is best regarded as a reference or supporting detail structure that is invoked during the processing of a parent pay proposal action, rather than as an independent business entity. Where modeling suggestions are applied, it is closest in behavior to a dependent satellite, tied to the pay proposal action through the composite key components.

Key Information Stored

The documented physical schema exposes four columns, with the primary key being PER_PAY_PROPOSAL_COMPON_EFC_PK, a composite key comprising COMPONENT_ID and EFC_ACTION_ID. Because no separate single-column surrogate key is used, the composite business key itself serves as the unique row identifier.

• COMPONENT_ID — The primary identifier for the pay proposal component record; part of the composite primary key and the principal business-key candidate.
• EFC_ACTION_ID — The second element of the composite primary key, linking the component to its associated EFC action context.
• CHANGE_AMOUNT_N — A numeric column capturing the monetary change amount associated with the component, such as the value of a proposed adjustment.
• INPUT_CURRENCY_CODE — The currency in which the change amount is entered and stored, enabling multi-currency pay proposal scenarios.

Together, the four-column structure supports a narrowly scoped purpose: recording the amount and currency of a proposed compensation component against an identifiable action and component reference. There is no documented single-column surrogate key, so downstream integrations must rely on the composite primary key for uniqueness.

Common Use Cases and Queries

Typical applications include reconciliation of proposed salary adjustments, auditing of change amounts by currency, and integration of pay proposal components into downstream compensation reporting. A representative query joining component details to their action context:

• Retrieve all components for a specific action: SELECT component_id, change_amount_n, input_currency_code FROM hr.per_pay_proposal_component_efc WHERE efc_action_id = :action_id;
• Aggregate total proposed change by currency: SELECT input_currency_code, SUM(change_amount_n) FROM hr.per_pay_proposal_component_efc GROUP BY input_currency_code;
• Look up a specific component via the composite key: SELECT * FROM hr.per_pay_proposal_component_efc WHERE component_id = :cid AND efc_action_id = :aid;

These patterns support audit trails, approval workflows, and reporting extracts within the payroll cycle.

Related Objects

Given the standalone classification and limited FK exposure, the most significant referenced objects are those reached through the composite key columns:

• PER_PAY_PROPOSAL_COMPONENTS — joined on COMPONENT_ID.
• PER_PAY_PROPOSAL_ACTIONS — joined on EFC_ACTION_ID.
• PER_PAY_PROPOSALS — parent proposal header reached via the action linkage.
• FND_CURRENCIES — joined on INPUT_CURRENCY_CODE.
• PAY_ELEMENT_ENTRIES / PAY_RUN_RESULTS — invoked during payroll processing of approved components.

These dependencies underscore the table's role as a focused detail structure supporting the broader pay proposal and payroll processing chain.