Results for “ben_plip”

22 results




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

Overview

BEN_PLIP is an Oracle E-Business Suite Advanced Benefits (BEN) view owned by the APPS schema. In the ETRM 12.2.2 documentation the object is marked VALID and its description is recorded simply as "Retrofitted," indicating that the view was introduced or repositioned as part of the multi-release retrofit effort that aligned the Advanced Benefits data model between EBS 12.1.1 and 12.2.2. The view exposes plan-in-program (PLIP) configuration data — that is, the rules that govern how a particular compensation object or plan is offered within a benefits program, including enrollment methods, coverage effective and end dates, eligibility application flags, and minimum/maximum coverage amounts.

Functionally, BEN_PLIP presents the PLIP entity for reporting, concurrent processing, and integration consumption. Where the underlying base table holds current-row and date-tracked records, BEN_PLIP surfaces the columns most commonly required by downstream extracts such as benefits enrollment listings, plan configuration audits, and interface files consumed by payroll or third-party administrators.

Underlying Base Objects

According to the documented ETRM metadata, BEN_PLIP is defined over the following referenced base objects:

  • BEN_PLIP_F (SYNONYM) — the primary base table for plan-in-program definitions. The "_F" suffix conventionally denotes the "frozen" or non-date-tracked presentation of the entity within the BEN schema's multi-table date-tracking architecture.
  • FND_SESSIONS (SYNONYM) — the Oracle Application Object Library session table, referenced in the view definition to supply runtime session context (for example the effective session date) used to constrain which date-tracked rows are visible.

The view text confirms this dependency by selecting every major attribute of the plan-in-program record, prefixed in the SQL as CPP.*. The direct relationship is therefore a one-to-one projection: BEN_PLIP does not aggregate or join across the full benefits configuration hierarchy, but rather flattens BEN_PLIP_F into a reporting-friendly interface while applying session-derived filters. Because the synonyms resolve to APPS-owned objects, the view is queryable by any application user with SELECT privilege on APPS.BEN_PLIP.

Key Columns

The column list defines the PLIP contract. Significant columns include:

Common Use Cases and Queries

Typical uses include auditing which PLIPs are active for a program, driving enrollment interface extracts, and troubleshooting status-related issues surfaced by the "plip_stat_cd" search. A representative query listing active PLIPs with their plans and programs is:

  • SELECT plip_id, pl_id, pgm_id, plip_stat_cd, enrt_cd, enrt_mthd_cd, effective_start_date, effective_end_date FROM apps.ben_plip WHERE plip_stat_cd = 'A' ORDER BY pgm_id, pl_id;
  • SELECT plip_id, dflt_enrt_cd, enrt_cvg_strt_dt_cd, elig_apls_flag FROM apps.ben_plip WHERE pgm_id = :p_program_id AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
  • Joining to BEN_PL_F and BEN_PGM_F to resolve plan and program names for user-facing reports.

Because the view applies session context from FND_SESSIONS, users should confirm the active session's effective date before interpreting date-tracked results, particularly during enrollment windows.