Search Results mltry_stat_meaning

Overview

APPS.BEN_ELIG_MLTRY_STAT_CVG_D is a read-only Oracle EBS view owned by the APPS schema and defined within the Advanced Benefits (BEN) product family. It exposes military status coverage eligibility setup data, translating the underlying foreign-key identifiers into user-facing lookup meanings for military status, coverage start, and coverage end. The view is classified as Oracle Internal Use Only; Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs.

Its practical role is to flatten and denormalize the eligibility profile configuration so that military status restrictions tied to dependent coverage eligibility profiles can be reported without repeatedly joining lookup views and lookup types. The column MLTRY_STAT_MEANING, which is the lookup meaning for military service status, is the primary column relevant to the "mltry_stat_meaning" search term. Because a column name in EBS frequently corresponds to a descriptive lookup value rather than a stored code, this view is the correct surface for retrieving the human-readable military status text associated with a coverage eligibility rule.

Underlying Base Objects

The view is documented as referencing the following objects: BEN_DPNT_CVG_ELIGY_PRFL_F, BEN_ELIG_MLTRY_STAT_CVG_F, FF_FORMULAS_F, FND_USER, the HR_API package, and HR_LOOKUPS. The two BEN tables are the core drivers. BEN_ELIG_MLTRY_STAT_CVG_F holds the military status coverage eligibility rows, keyed by ELIG_MLTRY_STAT_CVG_ID, with effective dating via EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. BEN_DPNT_CVG_ELIGY_PRFL_F supplies the dependent coverage eligibility profile and its name, exposed as DPNT_CVG_ELIGY_PRFL_NAME, linking the military status restriction to a named eligibility profile.

FF_FORMULAS_F and HR_API participate in the eligibility processing logic that resolves the criteria, while FND_USER and HR_LOOKUPS support the standard who columns and the lookup meanings respectively. The view does not resolve a lookup code column directly; instead HR_LOOKUPS is joined internally so that MLTRY_STAT_MEANING, CVG_STRT_MEANING, and CVG_THRU_MEANING are returned as descriptive text. The ETRM metadata confirms that BEN_ELIG_MLTRY_STAT_CVG_D is not referenced by any other database object and should therefore be treated strictly as a terminal reporting view.

Key Columns

• ELIG_MLTRY_STAT_CVG_ID — Primary identifier for the military status coverage eligibility record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective range governing when the eligibility rule is valid.
• DPNT_CVG_ELIGY_PRFL_NAME — Name of the dependent coverage eligibility profile to which the military status rule is attached.
• MLTRY_STAT_MEANING — Descriptive lookup meaning for the military service status used in the eligibility criteria; this is the column targeted by the "mltry_stat_meaning" search.
• CVG_STRT_MEANING / CVG_STRT_NAME — Meaning and code identifying when coverage may start.
• CVG_THRU_MEANING / CVG_THRU_NAME — Meaning and code identifying through when coverage is permitted.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — Standard who columns recording the last change and the FND_USER responsible.
• ROW_ID — ROWID pseudo-column for the underlying row.

Common Use Cases and Queries

Typical usage involves auditing which military statuses drive dependent coverage eligibility, verifying the effective windows of those rules, and reconciling lookup meanings to their base codes. The following example retrieves the military status meaning for currently effective eligibility records:

SELECT elig_mltry_stat_cvg_id, dpnt_cvg_eligy_prfl_name, mltry_stat_meaning, effective_start_date, effective_end_date FROM apps.ben_elig_mltry_stat_cvg_d WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

A second pattern narrows to a specific eligibility profile or status text:

SELECT dpnt_cvg_eligy_prfl_name, mltry_stat_meaning, cvg_strt_meaning, cvg_thru_meaning FROM apps.ben_elig_mltry_stat_cvg_d WHERE UPPER(mltry_stat_meaning) LIKE '%ACTIVE%' ORDER BY dpnt_cvg_eligy_prfl_name;

Because the object is date-effective, queries should always constrain on the effective range to avoid returning superseded rows. Access should be limited to read-only reporting and standard Oracle Applications programs, consistent with the Oracle Internal Use Only designation.