Results for “vep_attribute1”

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

Overview

The BEN_VRBL_RT_ELIG_PRFL_V view is a public, VALID database object owned by the APPS schema within the Oracle Advanced Benefits (BEN) product module. It functions as a date-effective, session-aware reporting and integration layer over the variable rate eligibility profile configuration stored in the Benefits transactional tables. In Oracle EBS 12.1.1 and 12.2.2, the view is exposed to report developers, concurrent programs, and integration interfaces that require a read-only projection of variable rate eligibility profile records without directly querying the underlying foundation table.

Its principal role is to present only those rows that are effective as of the current application session date. This is accomplished by joining the base table to FND_SESSIONS and filtering on the session effective date. The view therefore centralizes effective-dating logic and provides a stable, denormalized surface for downstream consumers. It also exposes the complete set of descriptive flexfield (DFF) attribute columns, enabling clients to read user-defined configuration values alongside the standard key columns.

Underlying Base Objects

The documented ETRM metadata identifies two referenced base objects, both accessed through synonyms in the APPS schema:

• BEN_VRBL_RT_ELIG_PRFL_F — the foundation table holding variable rate eligibility profile definitions, aliased as VEP. It supplies all business columns, including the primary key VRBL_RT_ELIG_PRFL_ID, the date-effective range, the business group, and the DFF segment values.
• FND_SESSIONS — the standard EBS session table, joined to enforce effective-date filtering. The predicate SE.SESSION_ID = USERENV('SESSIONID') restricts to the current session, and SE.EFFECTIVE_DATE BETWEEN VEP.EFFECTIVE_START_DATE AND VEP.EFFECTIVE_END_DATE yields only currently effective rows.

Because the source is a date-effective (_F) table, the view respects the standard Oracle HRMS effective-dating model rather than returning all historical or future-dated versions of a profile.

Key Columns

• ROW_ID — the physical row identifier of the underlying foundation record.
• VRBL_RT_ELIG_PRFL_ID — the surrogate primary key uniquely identifying the variable rate eligibility profile.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the effective-dating boundaries governing when the record is valid.
• BUSINESS_GROUP_ID — the business group scoping the record for multi-organization installations.
• VRBL_RT_PRFL_ID — foreign key to the variable rate profile to which the eligibility rule applies.
• ELIGY_PRFL_ID — foreign key to the eligibility profile that determines participant qualification.
• MNDTRY_FLAG — indicates whether the associated eligibility profile is mandatory for the variable rate profile.
• VEP_ATTRIBUTE_CATEGORY / VEP_ATTRIBUTE1 … VEP_ATTRIBUTE30 — the descriptive flexfield context and segment values. This is the column family users target when searching for vep_attribute30, the thirtieth DFF segment.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns supporting concurrency control and audit reporting.

Common Use Cases and Queries

The view is typically consumed to report which eligibility profiles are linked to variable rate profiles and to extract flexfield customizations. A representative query retrieving the thirtieth flexfield segment is:

• SELECT vep.VRBL_RT_ELIG_PRFL_ID, vep.VRBL_RT_PRFL_ID, vep.ELIGY_PRFL_ID, vep.MNDTRY_FLAG, vep.VEP_ATTRIBUTE_CATEGORY, vep.VEP_ATTRIBUTE30 FROM apps.BEN_VRBL_RT_ELIG_PRFL_V vep;

Other common scenarios include joining to variable rate profile and eligibility profile views to produce configuration listings, extracting DFF data for data-migration or conversion scripts, and validating mandatory-flag settings before benefits processing runs. Because effective-date filtering is embedded, developers need not reapply date predicates, simplifying report SQL and reducing the risk of returning inactive or future-dated rows.