Results for “ben_stat”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.BEN_DPNT_CVG_ELIGY_PRFL_D is an Oracle EBS Advanced Benefits (BEN) view that exposes translated, descriptive information about dependent coverage eligibility profiles. It is the "_D" (description/translation) companion to the base entity, providing language-dependent meaning columns such as NAME, DCE_DESC, and, most notably, DPNT_CVG_ELIGY_PRFL_STAT_MEAN. This view is a standard Oracle Applications object owned by the APPS schema and is documented in ETRM with FND Design Data under BEN.BEN_DPNT_CVG_ELIGY_PRFL_D. Its status is VALID, and the view type is designated Internal. The metadata carries the explicit Oracle Internal Use Only warning, meaning the object is not a supported public interface for direct data access except from standard Oracle Applications programs. This is significant because the column the user searched for, DPNT_CVG_ELIGY_PRFL_STAT_MEAN, is present in this view. In practice, the view resolves the eligibility profile's state/meaning through translated lookups, surfacing a human-readable status meaning that reporting and integration layers can present without exercising the display logic themselves.

Underlying Base Objects

The documented dependency metadata lists the following base objects from which this view is defined:

  • BEN_DPNT_CVG_ELIGY_PRFL_F — the underlying base table (referenced via a synonym), supplying the core eligibility profile rows.
  • FF_FORMULAS_F — the formula definition table (synonym), used to resolve eligibility determination logic.
  • FND_GLOBAL — the Oracle Applications global context package, used to derive the current session's language, user, and application context.
  • FND_USER — the standard user table (synonym), joined to translate the LAST_UPDATED_BY value.
  • HR_API — the Human Resources API package, which supplies supported business logic for HR-related derivations.
  • HR_LOOKUPS — the lookups view, providing the lookup meaning values that populate translated status and description columns.

The view is documented as referenced by PUBLIC, indicating it is exposed to the PUBLIC synonym layer. Dependencies are read from the base _F table and lookups, with descriptive text derived through join and decode logic.

Key Columns

  • ROW_ID (ROWID, 10) — the unique row identifier for the view row.
  • DPNT_CVG_ELIGY_PRFL_ID (NUMBER, 15) — the primary surrogate identifier of the dependent coverage eligibility profile.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE (DATE) — the date-effective range governing when the profile row is valid.
  • NAME (VARCHAR2, 240) — the translated name of the dependent coverage eligibility profile.
  • DPNT_CVG_ELIGY_PRFL_STAT_MEAN (VARCHAR2, 80) — the translated meaning of the profile status; the column at the center of the user's search.
  • DCE_DESC (VARCHAR2, 240) — the descriptive text associated with the dependent coverage eligibility profile.
  • DPNT_CVG_ELIG_DET_NAME (VARCHAR2, 80) — the name of the related eligibility determination.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — standard Who columns recording the last update timestamp and the updating user (foreign key to FND_USER.USER_ID).

Common Use Cases and Queries

This view is typically consumed for reporting on dependent coverage eligibility profiles, integration extracts that must publish human-readable status meanings, and root-cause analysis of eligibility outcomes. A baseline extraction is:

  • SELECT DPNT_CVG_ELIGY_PRFL_ID, NAME, DPNT_CVG_ELIGY_PRFL_STAT_MEAN, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM APPS.BEN_DPNT_CVG_ELIGY_PRFL_D;
  • Filtering to active rows: WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND NVL(EFFECTIVE_END_DATE, SYSDATE);
  • Reporting by status meaning: SELECT DPNT_CVG_ELIGY_PRFL_STAT_MEAN, COUNT(*) FROM APPS.BEN_DPNT_CVG_ELIGY_PRFL_D GROUP BY DPNT_CVG_ELIGY_PRFL_STAT_MEAN;
  • Tracing the determination: SELECT DPNT_CVG_ELIG_DET_NAME, NAME, DCE_DESC FROM APPS.BEN_DPNT_CVG_ELIGY_PRFL_D ORDER BY NAME.

Because of the Internal Use Only designation, direct SQL should be limited to read-only diagnostics and reporting, and production integrations should prefer standard Oracle Benefits programs and APIs.