Results for “ben_elig_mrtl_sts_prte_x”

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

Overview

BEN_ELIG_MRTL_STS_PRTE_X is a reportable (deterministic) view in the APPS schema belonging to the BEN – Advanced Benefits product family. It exposes the marital-status eligibility rule criteria configured against an eligibility profile in Oracle EBS Advanced Benefits. The "_X" suffix denotes a translation-independent reporting view rather than a base table; the view presents currently effective rows from the underlying "_F" table by filtering on the system date.

The view is frequently discovered by implementers searching for emp_attribute_category, because it surfaces the descriptive-flexfield context and all thirty descriptive-flexfield segments (EMP_ATTRIBUTE1 through EMP_ATTRIBUTE30) that qualification plans reference when a marital-status rule is further restricted by employee attribute values. In practice it is used for eligibility diagnostics, data extracts, and integration payloads where marital-status participation criteria must be read without the effectivity complexity of the base table.

Underlying Base Objects

The view is defined exclusively over BEN_ELIG_MRTL_STS_PRTE_F, referenced in the ETRM metadata as a synonym. The definition selects the identifying and descriptive columns from that base object and applies a system-date predicate:

• Base object: BEN_ELIG_MRTL_STS_PRTE_F — the date-tracked (effective-dated) table storing marital-status eligibility rule rows.
• Filter: TRUNC(SYSDATE) BETWEEN EMP.EFFECTIVE_START_DATE AND EMP.EFFECTIVE_END_DATE, so only the row effective today is returned.
• No joins: the view performs no lookup to PER_ALL_PEOPLE_F or FND_FLEX_VALUES; flexfield meaning resolution is left to the calling query.

Because the view inherits date-tracked behavior from the _F table while suppressing historical and future-dated rows, it is suitable for point-in-time reporting but not for retroactive analysis. Users requiring full history should query BEN_ELIG_MRTL_STS_PRTE_F directly.

Key Columns

• ELIG_MRTL_STS_PRTE_ID — Primary key of the marital-status eligibility rule.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-tracked validity range used by the SYSDATE filter.
• BUSINESS_GROUP_ID — Operating unit/legislative business group owning the rule.
• ELIGY_PROFILE_ID — Foreign key to the eligibility profile the rule belongs to.
• EXCLD_FLAG — Indicates whether the criterion includes or excludes matching persons.
• MARITAL_STATUS — The marital-status lookup value evaluated by the rule.
• EMP_ATTRIBUTE_CATEGORY — Descriptive-flexfield structure name qualifying the employee attribute segments.
• EMP_ATTRIBUTE1–EMP_ATTRIBUTE30 — Thirty descriptive-flexfield segments that further constrain the rule.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — Standard audit and optimistic-locking columns.

Common Use Cases and Queries

Typical scenarios include auditing which marital-status rules restrict a given eligibility profile, and extracting attribute-category-based criteria for reconciliation against plan design documents.

• List all active marital-status criteria for a profile, including flexfield context:

  SELECT elig_mrtl_sts_prte_id,
         eligy_prfl_id,
         marital_status,
         excld_flag,
         emp_attribute_category
  FROM   apps.ben_elig_mrtl_sts_prte_x
  WHERE  eligy_prfl_id = :p_profile_id;

• Find rules that use descriptive flexfield attributes at all:

  SELECT elig_mrtl_sts_prte_id, emp_attribute_category
  FROM   apps.ben_elig_mrtl_sts_prte_x
  WHERE  emp_attribute_category IS NOT NULL;

• Include or exclude checks by flag:

  SELECT marital_status, excld_flag
  FROM   apps.ben_elig_mrtl_sts_prte_x
  WHERE  business_group_id = :p_bg_id;

Because the view already restricts rows by SYSDATE, no additional date predicate is required for current-state reporting.