Results for “ben_bnft_prvdd_ldgr_f_efc_n1”

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

Overview

BEN.BEN_BNFT_PRVDD_LDGR_F_EFC is a date-tracked child table in the Oracle E-Business Suite Benefits (BEN) schema. It stores the effective-dated, action-versioned detail rows of the provided benefit ledger, capturing the monetary and unit-of-measure values that describe how a benefit was provided to a participant over a given effective period. The _EFC suffix indicates that the table is maintained through Oracle's Effective Date Controlled (EFC) framework: rows carry EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and EFC_ACTION_ID so that corrections and retroactive changes are preserved as independent, auditable versions rather than destructive updates. The table is classified in the application tablespace APPS_TS_TX_DATA with a PCT Free of 10, and it is a VALID, shipped Oracle Applications object.

Per the heuristic Data Vault classification mined from its foreign-key structure, this object is best modeled as a standalone construct — it is not a pure hub, link, or satellite, but rather a keyed transactional detail table whose identity is defined by the combination of the parent ledger identifier and the EFC temporal triple. Treating it as a satellite-like structure keyed on the parent ledger is a reasonable analytical suggestion, but the documented schema should be respected as the authoritative shape.

Key Information Stored

The primary key, BEN_BNFT_PRVDD_LDGR_F_EFC_PK, is composed of four columns and eliminates duplicate versions at the physical level:

• BNFT_PRVDD_LDGR_ID — a NUMBER(15) foreign key to BEN_BNFT_PRVDD_LDGR_F, identifying the parent provided benefit ledger row. This is the dominant business-key candidate.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the DATE pair delimiting the effective period of the version.
• EFC_ACTION_ID — a NUMBER(15) foreign key to HR_EFC_ACTIONS, identifying the change action that produced the version.

The unique index BEN_BNFT_PRVDD_LDGR_F_EFC_N1 — the object the user searched for — is a NORMAL UNIQUE index in APPS_TS_TX_IDX over exactly the same four columns as the primary key, providing the primary access path for point lookups by ledger identifier and effective date.

The table's 21 documented columns divide into three value families. The current-period values are FRFTD_VAL (forfeited), PRVDD_VAL (provided), RLD_UP_VAL (rolled up), USED_VAL, and CASH_RECD_VAL, together with the unit qualifiers PGM_UOM and NIP_PL_UOM. Two annualized families mirror the same measures: ANN_CASH_RECD_VAL, ANN_FRFTD_VAL, ANN_PRVDD_VAL, ANN_RLD_UP_VAL, and ANN_USED_VAL; and a committed-versus-current-due family comprising CMCD_CASH_RECD_VAL, CMCD_FRFTD_VAL, CMCD_PRVDD_VAL, CMCD_RLD_UP_VAL, and CMCD_USED_VAL. The ANN_ and CMCD_ columns carry no individual comments in the metadata and inherit their definitions from the base table BEN_BNFT_PRVDD_LDGR_F.

Common Use Cases and Queries

Typical reporting is either as-of-date (which version was active?) or full-history (what changed and when?). Both patterns filter exclusively on the leading columns of BEN_BNFT_PRVDD_LDGR_F_EFC_N1:

• As-of lookup: WHERE BNFT_PRVDD_LDGR_ID = :p_id AND :as_of BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE
• Audit trail across actions: WHERE BNFT_PRVDD_LDGR_ID = :p_id ORDER BY EFFECTIVE_START_DATE, EFC_ACTION_ID
• Period aggregation of provided versus used value: group by ledger identifier and sum PRVDD_VAL and USED_VAL over a selected effective range.
• Reconciliation with HR_EFC_ACTIONS to attribute every value change to a named, authorized user action.

Because the table is flagged Oracle Internal Use Only, extraction should occur through standard Oracle Benefits programs or approved concurrent requests rather than direct ad-hoc DML. Read-only SQL against the columns listed in the documented query text is the supported reporting pattern.

Related Objects

• BEN.BEN_BNFT_PRVDD_LDGR_F — the base provided benefit ledger table; joined on BNFT_PRVDD_LDGR_ID. This is the primary parent and the source of the inherited column definitions.
• HR.HR_EFC_ACTIONS — the Effective Date Controlled action registry; joined on EFC_ACTION_ID to describe who changed the record and why.
• BEN.BEN_BNFT_PRVDD_LDGR_F_EFC_PK — the composite primary key (BNFT_PRVDD_LDGR_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, EFC_ACTION_ID) enforcing version uniqueness.
• BEN.BEN_BNFT_PRVDD_LDGR_F_EFC_N1 — the unique normal index (search term) supporting all date-effective access paths.
• Oracle Benefits setup UI and concurrent programs that maintain EFC-enabled benefit ledger records, which insert, end-date, and re-insert rows in this table as actions are applied.