Results for “per_bf_payment_details_efc”

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

Overview

PER_BF_PAYMENT_DETAILS_EFC is a standard Oracle E-Business Suite table residing in the HR schema and belonging to the PER (Human Resources) product family. It is part of the Enterprise Foundation Component (EFC) architecture used by Oracle Human Resources to support high-volume, transactional processing across HR and payroll-related flows. The table stores payment detail records that are associated with an EFC action, acting as a dependent child of the HR_EFC_ACTIONS table through a foreign key relationship on EFC_ACTION_ID.

In Data Vault modeling terms, the heuristic classification of this object is satellite-leaning. This reflects the presence of descriptive attributes (AMOUNT, CURRENCY_CODE) that qualify a parent business entity (the EFC action), consistent with a satellite attached to a hub or link. The composite primary key supports the satellite interpretation, as it ties each payment detail record to a specific action context rather than acting as an independent hub.

Key Information Stored

The documented physical schema for 12.2.2 contains four columns. The most important are:

• PAYMENT_DETAIL_ID — The surrogate identifier for the payment detail record and a component of the composite primary key (PER_BF_PAYMENT_DETAILS_EFC_PK). It uniquely distinguishes each payment detail entry within the table.
• EFC_ACTION_ID — The second component of the primary key and the foreign key to HR_EFC_ACTIONS. This column links the payment detail to the originating EFC action, providing the contextual parent reference.
• AMOUNT — The monetary value associated with the payment detail.
• CURRENCY_CODE — The currency in which AMOUNT is denominated.

The unique index PER_BF_PAYMENT_DETAILS_EFC_PK on (PAYMENT_DETAIL_ID, EFC_ACTION_ID) is the documented business-key candidate, ensuring no duplicate detail rows exist for the same action and detail combination. In practice, PAYMENT_DETAIL_ID functions as the primary surrogate key while the combination with EFC_ACTION_ID enforces the parent-child integrity constraint.

Common Use Cases and Queries

Typical usage involves retrieving payment details for a given EFC action or aggregating amounts by currency. A representative join pattern is:

• Retrieve payment details for a specific action: SELECT p.PAYMENT_DETAIL_ID, p.AMOUNT, p.CURRENCY_CODE FROM PER_BF_PAYMENT_DETAILS_EFC p WHERE p.EFC_ACTION_ID = :action_id;
• Aggregate amounts by currency across actions: SELECT p.CURRENCY_CODE, SUM(p.AMOUNT) FROM PER_BF_PAYMENT_DETAILS_EFC p GROUP BY p.CURRENCY_CODE;
• Join to the parent action table to enrich reporting: SELECT a.*, p.AMOUNT, p.CURRENCY_CODE FROM HR_EFC_ACTIONS a, PER_BF_PAYMENT_DETAILS_EFC p WHERE a.EFC_ACTION_ID = p.EFC_ACTION_ID;

These queries are common in reconciliation reports, payroll payment audits, and EFC processing diagnostics within HR and payroll implementations.

Related Objects

• HR_EFC_ACTIONS — The parent table referenced by the EFC_ACTION_ID foreign key. This is the primary dependency and provides the action context for each payment detail.
• PER_BF_PAYMENT_DETAILS_EFC_PK — The unique index enforcing the composite key on PAYMENT_DETAIL_ID and EFC_ACTION_ID.
• PER_BF_* EFC tables — Sibling EFC-related tables in the HR schema that participate in the same processing framework and reference HR_EFC_ACTIONS.
• PER_BF_EFC_ACTIONS or equivalent action views — Reporting views built over HR_EFC_ACTIONS that frequently join to payment detail records for consolidated EFC reporting.

Because the metadata documents only the parent foreign key, the primary integration surface remains HR_EFC_ACTIONS; any additional dependents should be confirmed against the specific 12.1.1 or 12.2.2 patch level in use.