Search Results ann_rld_up_val




Overview
Explore in AI Chat

Overview

The BEN.BEN_BNFT_PRVDD_LDGR_F_EFC table is a date-tracked benefits ledger in Oracle Advanced Benefits (BEN). It is documented as a copy of the BEN_BNFT_PRVDD_LDGER_F table populated by the EFC (Euro as Functional Currency) process. Its purpose is to preserve a converted or parallel view of benefit provided-ledger balances when the functional currency environment requires a separate EFC representation, ensuring that monetary benefits calculations remain consistent and auditable alongside the base ledger.

The object is classified by the supplied metadata as standalone under heuristic Data Vault mining. In Data Vault modeling terms this implies the table behaves as a self-contained construct — neither a true hub nor a conventional link — because no foreign-key relationships to other objects were mined. The four-part primary key (BNFT_PRVDD_LDGR_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, EFC_ACTION_ID) suggests it functions as a satellite-like ledger snapshot, keyed by a benefits ledger identifier, a date range, and an EFC action, and best modeled as a satellite whose parent hub key is implicitly BNFT_PRVDD_LDGR_ID.

Key Information Stored

The table records 21 columns. The most significant for reporting and integration are:

  • BNFT_PRVDD_LDGR_ID — the surrogate benefit provided-ledger identifier and leading component of the primary key; this is the column most commonly queried by name.
  • EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the date-tracked validity window, essential for point-in-time and current-row queries.
  • EFC_ACTION_ID — the EFC process action that produced the row, completing the composite key.
  • PRVDD_VAL — the provided (credited) value for the period, the core monetary measure.
  • FRFTD_VAL — the forfeited value.
  • RLD_UP_VAL — the rolled-up value.
  • USED_VAL — the value used against the benefit.
  • CASH_RECD_VAL — cash received.
  • PGM_UOM and NIP_PL_UOM — program and non-cash plan unit-of-measure indicators.
  • The annual and common-currency variants — ANN_PRVDD_VAL, ANN_FRFTD_VAL, ANN_USED_VAL, ANN_RLD_UP_VAL, ANN_CASH_RECD_VAL, and the CMCD_* equivalents — provide annualized and common-currency roll-ups for cross-period and cross-currency comparison.

The unique index BEN_BNFT_PRVDD_LDGR_F_EFC_N1 mirrors the primary key columns, confirming that the business key is the ledger identifier combined with its effective date range and EFC action.

Common Use Cases and Queries

Typical uses include EFC reconciliation, benefits ledger reporting, and audit of currency-converted balances.

  • Retrieve the current effective row for a ledger: 
    SELECT * FROM ben.ben_bnft_prvdd_ldgr_f_efc
WHERE bnft_prvdd_ldgr_id = :ledger_id
AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date
AND efc_action_id = :action_id;
  • Compare base and EFC ledgers for a period by joining on BNFT_PRVDD_LDGR_ID and the effective dates.
  • Aggregate annualized provided values: SUM(ANN_PRVDD_VAL) grouped by program or period.
  • Audit EFC runs by filtering on EFC_ACTION_ID and reviewing PRVDD_VAL against FRFTD_VAL and USED_VAL.

Related Objects

The metadata notes no mined foreign keys, so relationships are inferred from the ledger identity and EFC process:

  • BEN_BNFT_PRVDD_LDGR_F — the source table of which this is a copy.
  • BEN_BNFT_PRVDD_LDGR_F_EFC_N1 — the unique index enforcing the business key.
  • BEN_BNFT_PRVDD_LDGR_F_EFC_PK — the primary-key constraint.
  • BEN_BNFT_PRVDD_LDGR_F_* associated ledger tables and the EFC action entities referenced through EFC_ACTION_ID.
  • BEN benefits plan and program tables joined via BNFT_PRVDD_LDGR_ID for name and enrollment context.