Results for “ben_asmt_to_use”

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

Overview

APPS.BEN_ELIGY_PRFL_D is a reporting view in the Oracle E-Business Suite Advanced Benefits (Oracle Benefits) module. In Oracle EBS 12.1.1 and 12.2.2 it exposes eligibility profile definitions held in the BEN_ELIGY_PRFL_F base table, joined to descriptive lookup values that translate stored codes into user-readable meanings. Specifically, the view resolves the STAT_CD column against the BEN_STAT lookup type and the ASMT_TO_USE_CD column against the BEN_ASMT_TO_USE lookup type. This makes BEN_ELIGY_PRFL_D the canonical read-only source for consumers that need eligibility profile names, descriptions, status and assessment-type labels without performing their own lookup resolution. It is widely used in BI Publisher reports, custom concurrent programs, extracts and integration interfaces where eligibility profile metadata must be presented or transmitted in decoded form. The "_D" suffix denotes the descriptive variant of the underlying table, consistent with the Oracle Applications naming convention.

Underlying Base Objects

The view is defined entirely over synonyms and views owned by APPS. Its FROM clause references BEN_ELIGY_PRFL_F (SYNONYM), FND_USER (SYNONYM) and HR_LOOKUPS (VIEW). The documented metadata also lists the HR_API (PACKAGE) as a referenced object, reflecting that the eligibility profile table is maintained through the HR API layer rather than by direct DML. Two outer joins to HR_LOOKUPS are present — one for status and one for assessment type — both expressed with the (+) operator. The join to FND_USER is likewise an outer join on LAST_UPDATED_BY. The view preserves the ROWID of BEN_ELIGY_PRFL_F as ROW_ID, which allows downstream tools to identify the source row. Because the view is built on the "_F" (date-tracked) table, each row carries an EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, so historical versions of a profile are visible to the querying user.

Key Columns

• ROW_ID — the ROWID of the underlying BEN_ELIGY_PRFL_F row.
• ELIGY_PRFL_ID — primary identifier of the eligibility profile.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — effective-dating range for the profile version.
• NAME — the eligibility profile name.
• DESCRIPTION — free-text description of the profile.
• STAT.MEANING — decoded status derived from ELP.STAT_CD via lookup type BEN_STAT.
• ASMT.MEANING — decoded assessment type derived from ELP.ASMT_TO_USE_CD via lookup type BEN_ASMT_TO_USE.
• LAST_UPDATE_DATE — audit timestamp of the last change.
• LAST_UPDATED_BY — user identifier from FND_USER.

The two MEANING columns carry the view's principal value, since they expose the translated values for the assessment-to-use code that users search for when locating the term "ben_asmt_to_use".

Common Use Cases and Queries

The view is typically queried to list active eligibility profiles, to audit profile status and assessment configuration, and to feed downstream extracts. A basic listing follows.

• Select ELIGY_PRFL_ID, NAME, ASMT.MEANING, STAT.MEANING, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE from BEN_ELIGY_PRFL_D order by NAME.
• Filter by assessment type using the decoded meaning: WHERE ASMT.MEANING = 'Required'.
• Restrict to currently effective rows: WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE.
• Audit recent changes: WHERE LAST_UPDATE_DATE >= TRUNC(SYSDATE) - 7.

Because the lookup joins are outer joins, profiles with a null STAT_CD or ASMT_TO_USE_CD still return rows with null meanings, which must be handled in report logic. All access should remain read-only; inserts and updates belong to the supported HR_API interfaces.