Results for “ben_bnft_prvdd_ldgr_v”

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

Overview

BEN_BNFT_PRVDD_LDGR_V is a reporting view owned by the APPS schema within the Advanced Benefits (BEN) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. The view exposes the benefit provided ledger, the transactional record that accumulates monetary and unit values granted to, used by, and forfeited by a participant across a defined activity reference period. Its principal architectural role is to present ledger rows filtered by the effective date of the current application session, so that concurrent programs, forms, and reports retrieve only the ledger versions that are valid as of the session's effective date rather than the full historical set. The user query term "ann_prvdd_val" corresponds directly to the ANN_PRVDD_VAL column exposed by this view, which holds the annualized provided value for the ledger row.

Underlying Base Objects

The view is defined over two referenced objects, both reached through synonyms in the APPS schema:

• BEN_BNFT_PRVDD_LDGR_F — the benefit provided ledger base table. All business columns and descriptive flexfield attributes are sourced from this table.
• FND_SESSIONS — the applications session table, joined to supply the session effective date used for date-tracked row filtering.

The join predicate is SE.SESSION_ID = USERENV('SESSIONID') combined with SE.EFFECTIVE_DATE BETWEEN BPL.EFFECTIVE_START_DATE AND BPL.EFFECTIVE_END_DATE. This pattern is characteristic of date-tracked (datetrack) EBS views: rather than requiring the caller to specify an effective date, the view resolves the currently active row for the logged-in session. The ROWID of the base table row is surfaced as ROW_ID, preserving the ability to identify and update the underlying record.

Key Columns

The column list divides into several functional groups:

• Identity and dating: ROW_ID, BNFT_PRVDD_LDGR_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, BUSINESS_GROUP_ID, OBJECT_VERSION_NUMBER.
• Common (period-independent) amounts: FRFTD_VAL, PRVDD_VAL, USED_VAL, CASH_RECD_VAL, RLD_UP_VAL, PRTT_RO_OF_UNUSD_AMT_FLAG, ACTY_REF_PERD_CD.
• Compensation-period amounts: CMCD_FRFTD_VAL, CMCD_PRVDD_VAL, CMCD_RLD_UP_VAL, CMCD_USED_VAL, CMCD_CASH_RECD_VAL, CMCD_REF_PERD_CD.
• Annualized amounts: ANN_FRFTD_VAL, ANN_PRVDD_VAL, ANN_RLD_UP_VAL, ANN_USED_VAL, ANN_CASH_RECD_VAL. ANN_PRVDD_VAL is the annualized value provided and is the column most frequently referenced by users searching on "ann_prvdd_val".
• Relationships: BNFT_PRVDR_POOL_ID, ACTY_BASE_RT_ID, PRTT_ENRT_RSLT_ID, PER_IN_LER_ID.
• Descriptive flexfield and audit: BPL_ATTRIBUTE_CATEGORY, BPL_ATTRIBUTE1 through BPL_ATTRIBUTE30, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical scenarios include reconciling annualized provided amounts against participant enrollment results, auditing forfeiture and roll-up balances, and feeding downstream benefit accounting extracts.

Retrieve annualized provided values for a participant enrollment result:

• SELECT BNFT_PRVDD_LDGR_ID, PRTT_ENRT_RSLT_ID, ANN_PRVDD_VAL, ANN_USED_VAL, ANN_FRFTD_VAL, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM BEN_BNFT_PRVDD_LDGR_V WHERE PRTT_ENRT_RSLT_ID = :p_enrt_rslt_id;

Aggregate annualized provided value by provider pool:

• SELECT BNFT_PRVDR_POOL_ID, SUM(ANN_PRVDD_VAL) ANN_PROVIDED FROM BEN_BNFT_PRVDD_LDGR_V GROUP BY BNFT_PRVDR_POOL_ID;

Compare provided against used and cash received within an activity reference period:

• SELECT BNFT_PRVDD_LDGR_ID, ANN_PRVDD_VAL, ANN_USED_VAL, ANN_CASH_RECD_VAL FROM BEN_BNFT_PRVDD_LDGR_V WHERE ACTY_REF_PERD_CD = :p_ref_period;

Because the view applies the FND_SESSIONS effective-date filter, results reflect the ledger versions valid for the current session effective date. Callers requiring a specific historical version should query the base table BEN_BNFT_PRVDD_LDGR_F directly with an explicit effective-date predicate.