Results for “ben_comp_typ”

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

Overview

BEN_PL_TYP_D is a documented Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data namespace BEN.BEN_PL_TYP_D. In ETRM 12.2.2 the object carries a VALID status and an "Oracle Internal Use Only" designation, meaning Oracle Corporation does not support direct customer access except through standard Oracle Applications programs. The view presents a denormalized, reporting-oriented projection of the plan type definition entity in the Benefits (BEN) module. Rather than exposing raw foreign-key identifiers for every lookup-backed attribute, it resolves coded values into their translated meaning strings, which makes it suitable for read-only reporting, data extraction, and integration scenarios where human-readable plan type attributes are required.

The view is particularly relevant to the search term "no_mn_enrl_num_dfnd_meaning". The column NO_MN_ENRL_NUM_DFND_MEANING (VARCHAR2, 80) is exposed directly by this view and answers the question of whether a minimum enrollment number has been defined for the plan type, expressed as a translated meaning rather than a code. Its counterpart, NO_MX_ENRL_NUM_DFND_MEANING (VARCHAR2, 80), covers the maximum enrollment side.

Underlying Base Objects

The documented dependency list identifies the following base objects:

• BEN_PL_TYP_F (referenced as a SYNONYM) — the primary base table holding the plan type definition rows, including effective-dated records.
• HR_LOOKUPS (VIEW) — the source of the translated meaning values, joined to resolve lookup codes into meaning strings such as PL_TYP_STAT_MEANING, OPT_TYP_MEANING, OPT_DSPLY_FMT_MEANING, and COMP_TYP_MEANING.
• FND_USER (SYNONYM) — used for the standard WHO column attribution (LAST_UPDATED_BY).
• HR_API (PACKAGE) — a reference from the view's dependent code, typically for date/effective-dating or security logic.

The view therefore functions as a semantic layer over BEN_PL_TYP_F, translating stored lookup codes into meanings while preserving the effective-dated structure of the underlying plan type rows.

Key Columns

• ROW_ID / PL_TYP_ID — the unique row and the plan type identifier.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window of the plan type definition.
• NAME, SHORT_NAME, SHORT_CODE — descriptive identifiers for the plan type.
• MX_ENRL_ALWD_NUM / MN_ENRL_RQD_NUM — numeric maximum allowed and minimum required enrollment counts.
• NO_MX_ENRL_NUM_DFND_MEANING / NO_MN_ENRL_NUM_DFND_MEANING — translated indicators of whether maximum/minimum enrollment numbers are defined; NO_MN_ENRL_NUM_DFND_MEANING is the column most directly associated with the user's search term.
• PL_TYP_STAT_MEANING, OPT_TYP_MEANING, OPT_DSPLY_FMT_MEANING, COMP_TYP_MEANING — meanings for plan type status, option type, display format, and compensation type.
• LEGISLATION_CODE / LEGISLATION_SUBGROUP — the legislative context of the plan type.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes Benefits configuration reporting, plan type reconciliation between environments, and integration extracts that must present plan type attributes in business language.

To identify plan types where the minimum enrollment number is not defined:

• SELECT PL_TYP_ID, NAME, NO_MN_ENRL_NUM_DFND_MEANING FROM APPS.BEN_PL_TYP_D WHERE NO_MN_ENRL_NUM_DFND_MEANING IS NOT NULL;

To list current effective plan types with their status and enrollment limits:

• SELECT PL_TYP_ID, NAME, PL_TYP_STAT_MEANING, MX_ENRL_ALWD_NUM, MN_ENRL_RQD_NUM FROM APPS.BEN_PL_TYP_D WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;

Because the object is flagged Oracle Internal Use Only, queries should be treated as read-only diagnostic or reporting access, and production integrations should preferably rely on supported Benefits APIs.