Results for “ben_pgm”

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

Overview

BEN_PGM is a seeded APPS view in the Oracle E-Business Suite Advanced Benefits (BEN) module. Its stated ETRM description is "- Retrofitted", indicating that it was introduced or reapplied as part of the underlying table's evolution, most likely to wrap the _F table with a session-aware or effective-dated filter. The view presents program-level setup data for benefits plans — that is, the attributes and rules that determine how a benefits program is defined, offered, and administered. It therefore acts as a reporting and integration access point for the configuration that drives eligibility, enrollment, and pricing behavior across a benefits offering. In 12.1.1 and 12.2.2 the object remains VALID in the APPS schema.

Its fields are not user-data transactions; they are configuration control flags (for example, flags governing automatic and default enrollment, dependent designation requirements, and rate derivation). Because they are setup metadata, the view is typically consumed by configuration reports, data conversions, and validation extracts. The PGM prefix denotes the Program entity within BEN.

Underlying Base Objects

Per the documented metadata, BEN_PGM is defined over two referenced base objects: BEN_PGM_F and FND_SESSIONS, both exposed to APPS as synonyms. BEN_PGM_F is the base (non-translated) program definition table; the view's text selects from an alias PGM that resolves to that base object. FND_SESSIONS is joined to enforce the user's session, business group, or language context, ensuring the caller sees only the data rows appropriate to the active session — a standard pattern for multi-tenant, multi-lingual EBS views.

The view is a thin projection: it exposes PGM_ID, effective dates, name, and the full set of program attribute columns without modification. Any insert, update, or delete must target the underlying _F table, not this view.

Key Columns

• PGM_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — the primary identity and date-effective key of a program version.
• NAME, PGM_DESC, PGM_TYP_CD, PGM_GRP_CD, PGM_STAT_CD — descriptive and lifecycle attributes.
• AUTO_ENRT_MTHD_RL, ENRT_MTHD_CD, ENRT_CD, ENRT_RL, POE_LVL_CD — enrollment method, reason, and period-of-enrollment rules.
• DPNT_* flags and levels (e.g., DPNT_ADRS_RQD_FLAG, DPNT_DOB_RQD_FLAG, DPNT_DSGN_CD, DPNT_DSGN_LVL_CD) — dependent designation requirements.
• ELIG_APLS_FLAG, PGM_USE_ALL_ASNTS_ELIG_FLAG, derivable-factor flags — eligibility application behavior.
• RT_*, ACTY_REF_PERD_CD, MX_DPNT_PCT_PRTT_LF_AMT, MX_SPS_PCT_PRTT_LF_AMT, PGM_UOM — rate, activity, and coverage amount controls.
• BUSINESS_GROUP_ID — the owning business group.
• PGM_ATTRIBUTE_CATEGORY and PGM_ATTRIBUTE1..30 — the descriptive flexfield segments.

Common Use Cases and Queries

Typical uses include configuration reporting, comparing program definitions across business groups, and resolving program attributes during conversions or interfaces.

• List active programs: SELECT pgm_id, name, pgm_typ_cd, Effective_start_date, effective_end_date FROM apps.ben_pgm WHERE sysdate BETWEEN effective_start_date AND NVL(effective_end_date, sysdate);
• Filter to a business group: append WHERE business_group_id = :bg.
• Inspect automatic enrollment settings: SELECT pgm_id, auto_enrt_mthd_rl, enrt_mthd_cd FROM apps.ben_pgm;
• Report dependent designation requirements using the DPNT_* flags.

Because the view joins FND_SESSIONS, session context must be initialised before querying; otherwise rows may be filtered out unexpectedly.