Results for “cvg_pndg_flag”

50+ results




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

Overview

BEN_ELIG_CVRD_DPNT_D is a view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the BEN product family — Oracle Advanced Benefits — and carries a VALID status in the data dictionary. The view presents covered dependent eligibility data recorded against the BEN_ELIG_CVRD_DPNT_F table, exposing both the surrogate primary key and the effective-dating attributes that govern how the underlying records are dated and versioned.

Its role in reporting and integration is to provide a read-only, presentation-friendly projection of covered dependent eligibility rows. Rather than querying the transactional base table directly, external reports, extracts, and interface programs can consume the view, which resolves the LAST_UPDATED_BY identifier into a human-readable user name. The view is enumerated in the ETRM data dictionary and is therefore a documented object for release 12.2.2 metadata purposes, with the same definition applying in 12.1.1.

Underlying Base Objects

The view is defined over two documented objects:

  • BEN_ELIG_CVRD_DPNT_F (referenced as a SYNONYM) — the base table that stores covered dependent eligibility information. It is an _F (date-tracked) table, meaning each row carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns that record the effective-dating window for that record version.
  • FND_USER_VIEW (VIEW) — the Applications user directory view, joined to supply the user name of the person who last updated the row.

The join between the two objects is an outer join on the user identifier: FUSER.USER_ID (+) = PDP.LAST_UPDATED_BY. Because the join is outer, rows in which LAST_UPDATED_BY does not resolve to a valid FND_USER record are still returned, with a null user name. The view itself exposes no filtering predicate, so all rows of the base table are visible to any caller with suitable privileges.

Key Columns

The view projects the following columns:

  • ROW_ID — the ROWID of the underlying BEN_ELIG_CVRD_DPNT_F row, useful for uniquely identifying and locking the base record.
  • ELIG_CVRD_DPNT_ID — the primary key of the covered dependent eligibility record.
  • EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the effective-dating boundaries of the row version.
  • CVG_STRT_DT — the coverage start date, indicating when coverage for the covered dependent begins. This is the column most commonly referenced by users searching on "cvg_strt_dt".
  • CVG_THRU_DT — the coverage through (end) date for the dependent's coverage.
  • CVG_PNDG_FLAG — a flag indicating whether the coverage is still pending rather than confirmed.
  • LAST_UPDATE_DATE — the audit timestamp of the most recent modification.
  • LAST_UPDATED_BY — the numeric user identifier of the last updater; the view also exposes the resolved name indirectly through the join, conventionally surfaced as USER_NAME.

Common Use Cases and Queries

The view is typically used to report on dependent coverage start and end dates, to audit who last changed a covered dependent record, and to feed downstream extracts. A representative query retrieves current coverage information for a dependent:

  • Reporting coverage start dates for a population of covered dependents.
  • Auditing rows where CVG_PNDG_FLAG indicates pending coverage.
  • Joining to other BEN eligibility tables on ELIG_CVRD_DPNT_ID.

Sample SQL:

SELECT ecpd.elig_cvrd_dpnt_id,
       ecpd.cvg_strt_dt,
       ecpd.cvg_thru_dt,
       ecpd.cvg_pndg_flag,
       ecpd.last_update_date,
       ecpd.user_name
FROM   apps.ben_elig_cvrd_dpnt_d ecpd
WHERE  ecpd.effective_end_date = TO_DATE('4712-12-31','YYYY-MM-DD')
  AND  ecpd.cvg_strt_dt >= :p_start_date
ORDER BY ecpd.cvg_strt_dt;

Because the view returns all effective-dated versions, queries that require the current row should filter on the highest EFFECTIVE_END_DATE or use application-provided date-tracked criteria. As with all APPS views, callers should respect row-level security and the effective-dating conventions of the BEN schema.