Results for “edc_attribute30”

44 results




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

Overview

BEN_ELIG_DSBLD_STAT_CVG is an APPS-owned database view within the Oracle E-Business Suite Advanced Benefits (BEN) module. Its documented status is VALID and it is described in the ETRM metadata as "Retrofitted," indicating that the object was introduced or re-implemented to conform to the multi-organization and date-effective (date-tracked) conventions used throughout Oracle EBS 12.1.1 and 12.2.2. The view exposes eligibility rules that associate a disabled status with a dependent coverage eligibility profile, presented to the calling session as of the effective date held in FND_SESSIONS.

The view plays a reporting and integration role rather than a transaction-capture role. It provides a read-only, session-filtered projection of the disabled-status coverage eligibility configuration, allowing concurrent programs, PL/SQL packages, and external integrations to retrieve only the rows that are effective for the current user session without issuing explicit date predicates. This is the standard Oracle EBS pattern by which date-effective configuration data is surfaced in a session-consistent manner.

Underlying Base Objects

BEN_ELIG_DSBLD_STAT_CVG is defined over two referenced objects, both accessed through synonyms in the APPS schema:

  • BEN_ELIG_DSBLD_STAT_CVG_F — the date-effective base table that stores the disabled-status coverage eligibility records. The view selects all of its business columns from this table, aliased as EDC in the view text.
  • FND_SESSIONS — the concurrent-manager and forms session table, interrogated in the view's WHERE clause via a subquery on USERENV('SESSIONID'). This supplies the effective date used to filter the base table.

The view therefore relates to its base table on a one-to-one basis at any point in time, but it returns only the single date-effective version of each record that is current for the active session. No joins to descriptive or lookup tables are performed inside the view, so code values such as DSBLD_CD and CVG_STRT_CD are exposed in raw form and must be resolved against their respective lookup types by the consumer.

Key Columns

Common Use Cases and Queries

Typical usages include validating that a disabled dependant qualifies for a coverage start or through rule, reporting eligibility setup for a business group, and auditing which disabled-status coverage rules are effective as of today. Because the view is already session-filtered, queries need no explicit date predicate.

List the effective disabled-status coverage rules for a dependent coverage eligibility profile:

SELECT edc.elig_dsbld_stat_cvg_id,
       edc.ds bld_cd,
       edc.cvg_strt_cd,
       edc.cvg_strt_rl,
       edc.cvg_thru_cd,
       edc.cvg_thru_rl
FROM   apps.ben_elig_dsbld_stat_cvg edc
WHERE  edc.dpnt_cvg_eligy_prfl_id = :p_profile_id
ORDER  BY edc.effective_start_date DESC;

Count configuration rows per business group for setup auditing:

SELECT edc.business_group_id,
       COUNT(*) effective_rules
FROM   apps.ben_elig_dsbld_stat_cvg edc
GROUP  BY edc.business_group_id;

Resolve the disabled-status and coverage codes to their lookup meanings:

SELECT edc.elig_dsbld_stat_cvg_id,
       fl.meaning disabled_status
FROM   apps.ben_elig_dsbld_stat_cvg edc,
       apps.fnd_lookup_values fl
WHERE  fl.lookup_type = 'BEN_DSBLD_STAT'
AND    fl.lookup_code = edc.dsbld_cd
AND    SYSDATE BETWEEN fl.start_date_active AND NVL(fl.end_date_active, SYSDATE + 1);

Because the view derives its effective date from FND_SESSIONS, results are stable within a session but may differ across sessions following a date change. Integrations that require a fixed "as of" date should query the base table BEN_ELIG_DSBLD_STAT_CVG_F directly and supply their own effective-date predicate rather than relying on the session-derived filter.