Results for “vrbl_rt_add_on_calc_rl”

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

Overview

BEN_ACTL_PREM_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the BEN (Advanced Benefits) product module. The view exposes rows from the actual premium entity, filtered by the effective date context of the current user session. Its documented status is VALID at release levels 12.1.1 and 12.2.2, and the ETRM metadata annotates the object as "Retrofitted," indicating that the view was carried forward into the current release line to preserve compatibility with pre-existing customizations and downstream reports. The view is registered under APPS.BEN_ACTL_PREM_V and is not a base table; it is a definition-only object whose contents are derived at runtime from the underlying premium table.

Because the view incorporates a session-based date predicate rather than a caller-supplied parameter, it returns only the rows effective on the date associated with the user's application session. This makes it a convenient source for concurrent programs, Oracle Reports, OBIEE extracts, and ad hoc queries that must respect the effective-dating conventions of Oracle Advanced Benefits without requiring the developer to code the BETWEEN predicate explicitly.

Underlying Base Objects

The view is defined over two referenced objects, both resolved through APPS synonyms:

• BEN_ACTL_PREM_F — the actual premium base table, aliased as APR in the view text. This is the effective-dated datetrack table holding premium definitions, and it supplies every column projected by the view.
• FND_SESSIONS — the application session table, aliased as SE. It is joined to provide the session effective date used to constrain the premium rows.

The join condition is SE.SESSION_ID = USERENV('SESSIONID') combined with SE.EFFECTIVE_DATE BETWEEN APR.EFFECTIVE_START_DATE AND APR.EFFECTIVE_END_DATE. This pattern is the standard Oracle Forms/HTML session-aware effective date filter used throughout EBS. The ROWID of the base row is exposed as ROW_ID, which allows the view to serve as an update-capable construct in certain Oracle Forms blocks, although it is most commonly used read-only.

Key Columns

The projection list is broad and covers the full premium definition structure. Columns of particular interest include:

• ACTL_PREM_ID — primary key identifier of the actual premium record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the datetrack effective range controlling which session dates see the row.
• ACTL_PREM_TYP_CD — the actual premium type code, the column most frequently used to classify premium records by category.
• NAME, UOM, VAL — descriptive name, unit of measure, and the premium value or rate amount.
• RT_TYP_CD and BNFT_RT_TYP_CD — rate type and benefit rate type indicators governing how VAL is interpreted.
• PREM_ASNMT_CD and PREM_ASNMT_LVL_CD — premium assignment code and assignment level, defining who or what the premium attaches to.
• PREM_PYR_CD — premium payer code identifying the responsible party.
• UPR_LMT_VAL / LWR_LMT_VAL and their CALC_RL counterparts — upper and lower limits with the calculation rules that derive them.
• ORGANIZATION_ID, OIPL_ID, PL_ID, COMP_LVL_FCTR_ID, BUSINESS_GROUP_ID — organizational and plan linkage keys.
• CR_LKBK_VAL, CR_LKBK_UOM, CR_LKBK_CRNT_PY_ONLY_FLAG — credit lookback value, unit, and current-pay-only indicator.
• APR_ATTRIBUTE1 through APR_ATTRIBUTE30 — the descriptive flexfield attribute columns for customer-defined extensions.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, CREATED_BY and related audit columns — standard EBS concurrency and audit trail fields.

Common Use Cases and Queries

The most frequent application is retrieving the currently effective premium definition for a given benefit plan or premium type. Because the session filter is built in, a query simply selects from the view and adds business criteria. For example, a report listing premiums by type:

• SELECT actl_prem_id, name, actl_prem_typ_cd, val, uom FROM apps.ben_actl_prem_v WHERE actl_prem_typ_cd = :p_type ORDER BY name;

Retrieving a specific premium by identifier:

• SELECT * FROM apps.ben_actl_prem_v WHERE actl_prem_id = :p_id;

Joining the view to plan and organization data to build a premium-by-plan extract:

• SELECT v.name, v.actl_prem_typ_cd, v.val, v.pl_id, v.organization_id FROM apps.ben_actl_prem_v v WHERE v.business_group_id = :p_bg AND v.pl_id IS NOT NULL;

Filtering on the upper and lower limit rules to audit premium bounds:

• SELECT actl_prem_id, name, upr_lmt_val, lwr_lmt_val FROM apps.ben_actl_prem_v WHERE upr_lmt_val IS NOT NULL OR lwr_lmt_val IS NOT NULL;

Two cautions apply. First, since the effective date comes from FND_SESSIONS rather than a bind variable, results change according to the session context; queries executed from tools that do not populate FND_SESSIONS for the current session may return no rows or an unexpected datetrack slice. Second, the view is a compatibility object labeled "Retrofitted," so new development should prefer the current released view or direct access to BEN_ACTL_PREM_F with an explicit effective date predicate where the session context is not required.