Results for “ben_elig_per_wv_pl_typ”

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

Overview

The BEN_ELIG_PER_WV_PL_TYP view is a dated, effective-dated database object in the Oracle E-Business Suite Advanced Benefits (BEN) module. It is owned by the APPS schema and carries a status of VALID. The object is documented in ETRM with the annotation "Retrofitted", indicating that it was introduced or re-created as part of an upgrade or patch retrofitting exercise rather than originating as a primary functional entity. The view exposes eligibility-related processing rules that associate a person eligibility record with a plan type and a waiver configuration type determination. In the context of Oracle EBS 12.1.1 and 12.2.2, BEN_ELIG_PER_WV_PL_TYP serves as a reporting and integration surface over the translated base table, presenting only rows whose effective date range encompasses the current application session date. This design reflects the standard Oracle EBS pattern in which `_F` (translated) tables are wrapped by a view that applies session-level date filtering, thereby returning the record set that is valid as of the user's effective date.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the ETRM metadata:

• BEN_ELIG_PER_WV_PL_TYP_F — the translated base table holding the eligibility, person, waiver plan type, and descriptive flexfield attribute columns. The view aliases this table as ETW.
• FND_SESSIONS — the Oracle EBS session table, referenced in the view's WHERE clause to resolve the effective date for the current session.

The view text selects all functional and attribute columns from BEN_ELIG_PER_WV_PL_TYP_F and applies the following date predicate:

• ETW.EFFECTIVE_START_DATE <= (SELECT SS.EFFECTIVE_DATE FROM FND_SESSIONS SS WHERE SS.SESSION_ID = USERENV('SESSIONID'))
• ETW.EFFECTIVE_END_DATE >= (SELECT SS.EFFECTIVE_DATE FROM FND_SESSIONS SS WHERE SS.SESSION_ID = USERENV('SESSIONID'))

This ensures that only the datetracked row valid for the session's effective date is returned, which is the standard EBS approach for date-effective datetracked entities.

Key Columns

The columns exposed by the view carry the following documented and functional meanings:

• ELIG_PER_WV_PL_TYP_ID — primary identifier for the eligibility/person/waiver plan type record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the datetrack validity window governing when the row applies.
• PL_TYP_ID — foreign key to the plan type to which the eligibility rule applies.
• ELIG_PER_ID — foreign key to the eligibility person record.
• WV_CFTN_TYP_CD — waiver certification type code associated with the rule.
• WV_PRTN_RSN_CD — waiver participation reason code.
• WVD_FLAG — waived flag indicating waiver status.
• BUSINESS_GROUP_ID — the business group (operating unit) that owns the record.
• ETW_ATTRIBUTE_CATEGORY through ETW_ATTRIBUTE30 — descriptive flexfield (DFF) attribute columns for the underlying business object.
• Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER — standard EBS who-columns and optimistic locking support.

Common Use Cases and Queries

This view is typically queried in Advanced Benefits reporting and integration scenarios where the consumer needs the currently effective waiver/eligibility configuration for a plan type without manually applying datetrack logic. Representative uses include reconciliation of eligibility rules, extraction for downstream benefit administration, and verification of waiver processing configurations.

Example query retrieving currently effective eligible-person waiver plan type records for a plan type and business group:

• SELECT ELIG_PER_WV_PL_TYP_ID, PL_TYP_ID, ELIG_PER_ID, WV_CFTN_TYP_CD, WV_PRTN_RSN_CD, WVD_FLAG FROM APPS.BEN_ELIG_PER_WV_PL_TYP WHERE PL_TYP_ID = :p_plan_type_id AND BUSINESS_GROUP_ID = :p_bg_id;

Because the view already applies the FND_SESSIONS effective-date predicate, no additional EFFECTIVE_START_DATE/EFFECTIVE_END_DATE filter is required for "as-of-session" results. Reporting against the base table `BEN_ELIG_PER_WV_PL_TYP_F` directly, by contrast, requires callers to supply their own datetrack predicate.