Results for “ben_elig_asnt_set_prte_x”

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

Overview

The BEN_ELIG_ASNT_SET_PRTE_X view is a public, date-filtered reporting object within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the APPS schema and exposes the "eligibility assignment set prerequisite" data used to determine whether a participant meets the assignment-set criteria associated with an eligibility profile. The "_X" suffix follows the standard EBS convention for a translated or date-effective view whose "_F" counterpart retains the full, unfiltered dataset.

Because the view restricts output to rows whose effective date range spans the current system date, it presents only currently valid records. This makes it well suited to real-time eligibility evaluation, integration interfaces, and operational reporting where historical or future-dated rows are irrelevant. It is also the object surfaced when users investigate the descriptive flexfield segment ean_attribute_category, which appears on many eligibility assignment prerequisites and drives the segment's flexfield context.

Underlying Base Objects

The view is defined entirely over a single documented base object, BEN_ELIG_ASNT_SET_PRTE_F, referenced through an APPS synonym. In ETRM 12.2.2 the referenced base object is listed as BEN_ELIG_ASNT_SET_PRTE_F (SYNONYM). The "_F" table stores the physical, date-effective records for eligibility assignment-set prerequisites, including the primary key, effective start and end dates, ordering, exclusion flag, assignment set, eligibility profile, business group, and the full complement of descriptive flexfield columns.

The view applies no joins, aggregates, or derivations. It simply projects the columns of the base table and appends the predicate TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE. This tight relationship means column semantics, datatypes, and flexfield behavior are inherited unchanged from BEN_ELIG_ASNT_SET_PRTE_F.

Key Columns

• ELIG_ASNT_SET_PRTE_ID — Primary key uniquely identifying each eligibility assignment-set prerequisite record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-effective range; only rows spanning the current date are returned.
• ORDR_NUM — Sequence controlling the order in which prerequisites are evaluated.
• EXCLD_FLAG — Indicates whether the assignment set is included (include) or excluded (exclude) from the eligibility logic.
• ASSIGNMENT_SET_ID — Foreign key to the assignment set referenced by the prerequisite.
• ELIGY_PRFL_ID — Foreign key to the eligibility profile to which the assignment set prerequisite belongs.
• BUSINESS_GROUP_ID — Operating unit or business group that owns the record.
• EAN_ATTRIBUTE_CATEGORY — The descriptive flexfield context (the ean_attribute_category the user searched for), which determines which of the numbered attribute segments below are active and how they are labeled.
• EAN_ATTRIBUTE1 through EAN_ATTRIBUTE30 — Thirty descriptive flexfield segments whose meaning is determined by the applicable context set in EAN_ATTRIBUTE_CATEGORY.
• Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER — Standard EBS concurrency and audit tracking attributes.

Common Use Cases and Queries

Typical uses include verifying which assignment sets currently gate a given eligibility profile, reporting on flexfield context values, and feeding downstream integration extracts. The following query lists all active prerequisites for a profile, ordered by evaluation sequence:

• SELECT elig_asnt_set_prte_id, eligy_prfl_id, assignment_set_id, ordr_num, excld_flag, ean_attribute_category FROM ben_elig_asnt_set_prte_x WHERE eligy_prfl_id = :p_profile_id ORDER BY ordr_num;

To examine the flexfield context the user searched for, filtering by category isolates records using a specific descriptive flexfield structure:

• SELECT elig_asnt_set_prte_id, business_group_id, ean_attribute_category, ean_attribute1, ean_attribute2 FROM ben_elig_asnt_set_prte_x WHERE ean_attribute_category = :p_category;

Because the view already enforces date-effectivity, no additional effective-date predicate is needed in these queries. Developers requiring historical or future-dated rows should query the base table BEN_ELIG_ASNT_SET_PRTE_F directly and supply explicit effective-date criteria.