Results for “ben_schedd_enrt_rl_f”

50+ results




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

Overview

The BEN_SCHEDD_ENRT_RL_F table is a foundational configuration object within the Oracle E-Business Suite Advanced Benefits (BEN) module. It stores scheduled enrollment rules, which define the timing logic that governs when employees become eligible to enroll in, or are automatically processed through, a benefits offering. In Oracle EBS 12.1.1 and 12.2.2, this table belongs to the BEN schema and is classified as VALID, indicating it is an active, supported repository object used by the benefits engine during scheduled enrollment processing.

Each row in the table represents a ruleset that determines the schedule of enrollment activity — for example, when a life event or open enrollment period should trigger enrollment eligibility. Because the table carries a surrogate identifier (SCHEDD_ENRT_RL_ID), effective dating columns, and a foreign key to BEN_ENRT_PERD, the ETRM metadata classifies its data-vault role heuristically as satellite-leaning. This suggests the table behaves primarily as an attribute-bearing structure that hangs off the enrollment period entity, capturing descriptive rule configuration over time rather than serving as a pure hub or transactional link.

The table is date-tracked. Every record carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, and the primary key BEN_SCHEDD_ENRT_RL_F_PK is composed of the surrogate identifier plus both effective dates. This design enables rules to be versioned over time, so that the benefits engine can resolve the rule version that was valid as of any given enrollment date.

Key Information Stored

The most important columns in BEN_SCHEDD_ENRT_RL_F are:

  • SCHEDD_ENRT_RL_ID — the surrogate primary key of the scheduled enrollment rule. It uniquely identifies the rule definition and is the first component of BEN_SCHEDD_ENRT_RL_F_PK.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective range columns that, together with SCHEDD_ENRT_RL_ID, form the full primary key and provide version history for the rule.
  • ENRT_PERD_ID — foreign key referencing BEN_ENRT_PERD, linking the scheduled enrollment rule to its parent enrollment period. This is the sole documented outbound foreign key relationship.
  • FORMULA_ID — references the formula that implements the rule logic, connecting the rule to the business rules engine.
  • BUSINESS_GROUP_ID — identifies the business group (HR organization) that owns the rule, supporting multi-tenant separation.
  • SER_ATTRIBUTE_CATEGORY and SER_ATTRIBUTE1 through SER_ATTRIBUTE30 — a descriptive flexfield (DFF) structure used to capture additional customer-defined rule attributes.
  • ORDR_TO_APLY_NUM — controls the order in which multiple scheduled enrollment rules are applied, allowing deterministic evaluation sequencing.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns.
  • OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.

The business-key candidate is defined by the unique index BEN_SCHEDD_ENRT_RL_F_PK over (SCHEDD_ENRT_RL_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE); the remaining 40-plus columns are attribute payload.

Common Use Cases and Queries

Typical scenarios involve diagnosing why a scheduled enrollment did not fire, auditing rule version history, or reporting on rules attached to specific enrollment periods. A common query joins the rule to its enrollment period parent:

SELECT r.SCHEDD_ENRT_RL_ID, r.ENRT_PERD_ID, r.FORMULA_ID, r.ORDR_TO_APLY_NUM
FROM   BEN.BEN_SCHEDD_ENRT_RL_F r
WHERE  r.EFFECTIVE_START_DATE <= SYSDATE
AND   (r.EFFECTIVE_END_DATE IS NULL OR r.EFFECTIVE_END_DATE >= SYSDATE)
AND    r.BUSINESS_GROUP_ID = :p_business_group_id;

Date-effective resolution is the most frequent access pattern. Analysts also extract DFF attributes (SER_ATTRIBUTE1–30) for custom reporting, or correlate FORMULA_ID to the FF_FORMULAS table to review rule logic. Audit queries compare OBJECT_VERSION_NUMBER or LAST_UPDATE_DATE to track configuration drift.

Related Objects

  • BEN_ENRT_PERD — the parent enrollment period; joined via ENRT_PERD_ID.
  • BEN_SCHEDD_ENRT_RL_F_PK — the unique index enforcing the primary key.
  • FF_FORMULAS / FF_FORMULA_FUNCTIONS — resolve FORMULA_ID to executable rule logic.
  • BEN_ENRT_RT_RL_F — related enrollment rule family members that share similar date-effective configuration patterns.
  • PER_BUSINESS_GROUPS — resolves BUSINESS_GROUP_ID to the owning organization.
  • Benefits enrollment engine concurrent programs (e.g., scheduled enrollment processing) consume these rules at runtime.