Results for “ben_elig_dsbld_prte_v”

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

Overview

The view BEN_ELIG_DSBLD_PRTE_V resides in the APPS schema and belongs to the BEN — Advanced Benefits product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes rows describing disabled participation eligibility rules that are attached to an eligibility profile. In Advanced Benefits, an eligibility profile (ELIGY_PRFL_ID) is a reusable container of criteria; one class of criteria is the "disabled participation" rule, which allows the profile to exclude (or include) persons based on whether they are already participating in, or have been disabled from, a given benefit. The view provides a session-aware, effective-dated projection of those rules.

Its principal role in reporting and integration is to present the base table BEN_ELIG_DSBLD_PRTE_F filtered to the currently effective date of the user's session. This makes it suitable for concurrent programs, BI Publisher data templates, and inbound/outbound interfaces that must reflect only currently valid disabled-participation criteria, without embedding the effective-date logic in each query. The inclusion of the EDB_ATTRIBUTE_CATEGORY and thirty EDB_ATTRIBUTE1..30 columns supports the descriptive flexfield (DFF) associated with this criteria type, enabling customers to store and extract user-defined attributes.

Underlying Base Objects

The view is defined over two synonym-resolved base objects:

• BEN_ELIG_DSBLD_PRTE_F — the _F (date-tracked) table that persists disabled-participation criteria. It supplies every business column in the view and is the target for DML via the underlying entity.
• FND_SESSIONS — the Applications session table, joined to enforce the effective-date window.

The join predicate is SE.SESSION_ID = USERENV('SESSIONID') combined with SE.EFFECTIVE_DATE BETWEEN EDB.EFFECTIVE_START_DATE AND EDB.EFFECTIVE_END_DATE. This means the view returns only the row set whose effective range contains the session effective date, giving a "current record" perspective for each logical criterion. Because the effective dates are resolved from the session rather than SYSDATE, dated or simulated sessions are honoured — a deliberate design for date-tracked Benefits data.

Key Columns

• ROW_ID / ROWID — row identifier exposed for direct row addressing (the view exposes EDB.ROWID).
• ELIG_DSBLD_PRTE_ID — surrogate primary key of the disabled-participation criterion.
• DSBLD_CD — the disabled code identifying which participation/benefit the rule references.
• EXCLD_FLAG — indicates whether the criterion excludes (Y) or includes the affected population.
• ELIGY_PROFILE_ID — the eligibility profile to which the criterion belongs.
• BUSINESS_GROUP_ID — the HR business group owning the row.
• CRITERIA_SCORE / CRITERIA_WEIGHT — scoring inputs used when multiple criteria are combined.
• EDB_ATTRIBUTE_CATEGORY / EDB_ATTRIBUTE1..30 — the descriptive flexfield context and segments.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window.
• ORDR_NUM, OBJECT_VERSION_NUMBER and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) support sequencing, concurrency control and audit.

Common Use Cases and Queries

Typical uses include resolving which criteria a profile uses, auditing DFF values stored on the criteria, and feeding eligibility validation logic. Because the view filters by session effective date, queries are naturally scoped to the current record.

• List all disabled-participation criteria for a profile:

  SELECT ELIG_DSBLD_PRTE_ID, DSBLD_CD, EXCLD_FLAG, CRITERIA_SCORE, CRITERIA_WEIGHT
  FROM   APPS.BEN_ELIG_DSBLD_PRTE_V
  WHERE  ELIGY_PROFILE_ID = :p_profile_id
  ORDER  BY ORDR_NUM;

• Extract DFF context and segments for integration:

  SELECT ELIG_DSBLD_PRTE_ID, EDB_ATTRIBUTE_CATEGORY,
         EDB_ATTRIBUTE1, EDB_ATTRIBUTE2
  FROM   APPS.BEN_ELIG_DSBLD_PRTE_V
  WHERE  EDB_ATTRIBUTE_CATEGORY IS NOT NULL;

• Confirm exclusion rules for a business group:

  SELECT DSBLD_CD, COUNT(*)
  FROM   APPS.BEN_ELIG_DSBLD_PRTE_V
  WHERE  BUSINESS_GROUP_ID = :p_bg_id
  AND    EXCLD_FLAG = 'Y'
  GROUP  BY DSBLD_CD;

When joining the view to BEN_ELIGY_PRFL or benefit lookups, developers should remember the row is already effective-dated, so additional date predicates are usually unnecessary and can produce empty results.