Results for “pgm_attribute1”

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

Overview

The BEN_PGM_X view is a public-interface database object in the Oracle Advanced Benefits (BEN) module, owned by the APPS schema. In Oracle EBS 12.1.1 and 12.2.2 it is registered as a valid view and is documented as a retrofitted object, meaning its definition was regenerated through the standard EBS view-generation process rather than being maintained manually. The view exposes program-level configuration data for benefit programs — the highest-level container in the Advanced Benefits hierarchy beneath which plans, options, and eligibility profiles are organized.

A benefit program record establishes how a set of plans is offered, whether enrollment is automatic, what dependent and participant designations apply, and the effective-dated period during which the program is available. BEN_PGM_X presents this information in a flattened, query-friendly form suitable for reporting, data conversion, and integration. Its role in EBS reporting is to provide a stable, release-independent read surface over the underlying program entity without requiring consumers to reference internal columns directly.

Underlying Base Objects

The documented base object for this view is BEN_PGM_F, referenced through a synonym. The _F suffix identifies BEN_PGM_F as the program table holding the current, effective-dated row for each program; the corresponding historical table in the BEN datetrack model is BEN_PGM_F's date-tracked counterpart used for past and future versions. BEN_PGM_X is therefore a thin projection over BEN_PGM_F, exposing the program's descriptive, behavioral, and descriptive-flexfield columns through a single SELECT statement aliased as PGM.

Because the view is retrofitted, its column list tracks the columns defined on the base table at generation time. The view text selects PGM.ROWID AS ROW_ID, all primary keys and date-track columns, the functional attributes, and the complete descriptive flexfield block (PGM_ATTRIBUTE_CATEGORY through PGM_ATTRIBUTE30). The presence of ROW_ID makes the view update-capable for tools that rely on the base table row identifier.

Key Columns

• PGM_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — primary key and date-track columns identifying the program and its validity period.
• NAME, PGM_DESC, PGM_TYP_CD, PGM_GRP_CD, PGM_UOM — descriptive attributes, program type, and grouping.
• PGM_STAT_CD — program status (for example active or inactive).
• ELIG_APLS_FLAG, PGM_USE_ALL_ASNTS_ELIG_FLAG — eligibility application controls.
• AUTO_ENRT_MTHD_RL, ENRT_MTHD_CD, ENRT_CD, ALWS_UNRSTRCTD_ENRT_FLAG, PGM_PRVDS_NO_AUTO_ENRT_FLAG, PGM_PRVDS_NO_DFLT_ENRT_FLAG — enrollment behavior.
• DPNT_ADRS_RQD_FLAG, DPNT_DOB_RQD_FLAG, DPNT_LEGV_ID_RQD_FLAG, DPNT_DSGN_CD, DPNT_DSGN_LVL_CD — dependent designation requirements.
• MX_DPNT_PCT_PRTT_LF_AMT, MX_SPS_PCT_PRTT_LF_AMT — maximum dependent and spouse percentage of participant life amount.
• ENRT_CVG_STRT_DT_RL/_CD, ENRT_CVG_END_DT_RL/_CD, DPNT_CVG_STRT_DT_RL/_CD, RT_STRT_DT_RL/_CD, RT_END_DT_RL/_CD — date rule and code pairs governing coverage and rate periods.
• BUSINESS_GROUP_ID — the business group owning the program.
• PGM_ATTRIBUTE_CATEGORY and PGM_ATTRIBUTE1–PGM_ATTRIBUTE30 — descriptive flexfield segments. The user search term pgm_attribute_category maps directly to PGM_ATTRIBUTE_CATEGORY, the context column that determines which flexfield segments are meaningful for a given row.

Common Use Cases and Queries

Typical uses include benefit program catalogs, migration extracts that carry descriptive flexfield values, and diagnostic checks for enrollment configuration.

• Listing active programs for a business group.
• Reporting programs by descriptive flexfield context.
• Verifying enrollment and dependent-designation flags before a data conversion.

Sample queries:

• SELECT pgm_id, name, pgm_stat_cd, effective_start_date, effective_end_date FROM apps.ben_pgm_x WHERE business_group_id = :p_bg_id AND effective_end_date = fnd_date.canonical_to_date('4712/12/31') ORDER BY name;
• SELECT pgm_id, name, pgm_attribute_category, pgm_attribute1, pgm_attribute2 FROM apps.ben_pgm_x WHERE pgm_attribute_category IS NOT NULL ORDER BY name;
• SELECT p.pgm_id, p.name, p.enrt_mthd_cd, p.auto_enrt_mthd_rl, p.alws_unrstrctd_enrt_flag FROM apps.ben_pgm_x p WHERE p.pgm_attribute_category = :p_category;

All queries should be schema-qualified to APPS and filtered on the effective-dated row appropriate to the reporting date, since the underlying BEN_PGM_F table maintains multiple versions of each program.