Results for “ben_loa_rsn_rt_f”

50+ results




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

Overview

BEN_LOA_RSN_RT_F is a date-effective transactional table in the Oracle Advanced Benefits (BEN) module. It stores the rate definitions associated with leave of absence (LOA) reasons, allowing plan administrators to define how absence events map to rate profiles and other benefit-relevant attributes. The table is owned by the BEN schema and is present and valid in both Oracle EBS 12.1.1 and 12.2.2. Because Advanced Benefits drives eligibility, rates, and coverage calculations through effective-dated records, this table serves as the configuration bridge between an absence attendance type, a specific absence reason, and the rate treatment that benefits processing applies when that absence reason is selected.

Under the heuristic Data Vault classification supplied in the ETRM metadata, this table is characterized as standalone; it does not act as a hub, link, or satellite within a strictly modeled Data Vault warehouse. In practice it behaves like a keyed, effective-dated reference/config record whose business identity is anchored by LOA_RSN_RT_ID combined with its effective date range, which aligns with a satellite-style treatment if it were modeled into a Data Vault.

Key Information Stored

The primary key is defined by the unique index BEN_LOA_RSN_RT_F_PK on the composite of LOA_RSN_RT_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. LOA_RSN_RT_ID is the surrogate identifier for each rate-for-LOA-reason record, while the effective date pair provides the standard Oracle DateTrack business-key dimension that allows historical and future-dated versions of the same configuration to coexist.

Note that the metadata documents 47 physical columns; the flexfield attributes (LAR_ATTRIBUTE1 through 30) account for the majority and are not enumerated individually here.

Common Use Cases and Queries

Typical usage centers on verifying which rate profile applies to a given absence reason and attendance type, and on reporting current effective configuration. A representative query joining the table to its lookup parents is:

  • Retrieve the active rate profile for a reason: SELECT a.loa_rsn_rt_id, a.vrbl_rt_prfl_id, a.excld_flag FROM ben.ben_loa_rsn_rt_f a WHERE a.abs_attendance_reason_id = :reason_id AND SYSDATE BETWEEN a.effective_start_date AND a.effective_end_date;
  • Join to PER_ABS_ATTENDANCE_REASONS and PER_ABSENCE_ATTENDANCE_TYPES to resolve human-readable names for reporting.
  • Audit historical configuration changes by comparing EFFECTIVE_START_DATE versions of the same LOA_RSN_RT_ID.
  • Extract DFF values through LAR_ATTRIBUTE_CATEGORY / LAR_ATTRIBUTE1–30 for downstream benefits reporting.

Related Objects

  • PER_ABSENCE_ATTENDANCE_TYPES – parent of ABSENCE_ATTENDANCE_TYPE_ID.
  • PER_ABS_ATTENDANCE_REASONS – parent of ABS_ATTENDANCE_REASON_ID.
  • BEN_VRBL_RT_PRFL_F / variable rate profile tables – referenced by VRBL_RT_PRFL_ID.
  • BEN_LOA_RSN_RT_F_PK – the primary key index enforcing uniqueness.
  • Advanced Benefits rate and eligibility processing logic – consumes this table when computing rates for absence events.