Search Results ben_lvg_rsn_rt_f




Overview
Explore in AI Chat

Overview

BEN_LVG_RSN_RT_F is a table within the BEN (Advanced Benefits) product module of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. Its description is concise and functional: rate attributable to a leaving reason. In practical terms, the table stores configuration rows that associate a compensation or calculation rate with a specific leaving reason code, allowing an organization to vary the rate applied when a participant terminates or leaves a plan based on the reason recorded for that departure. This supports benefit and compensation scenarios where the treatment of a terminated participant — for example, a payout, accrual, or adjustment — depends on whether the leaving reason was voluntary, involuntary, retirement, or another categorised cause.

The metadata classifies the object heuristically as standalone under the Data Vault model, meaning no foreign-key relationships were mined from the documented schema. As a modeling suggestion, this points toward treatment as a hub or independent reference table rather than a dependent satellite or link. The table carries the standard Oracle EBS effective-dating pattern, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE forming part of the primary key, so rows represent rate definitions valid over a defined date range.

Key Information Stored

The documented physical schema contains 45 columns. The most significant are:

  • LVG_RSN_RT_ID — the surrogate identifier for a leaving-reason rate record, and the leading column of the primary key.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the effective-dating boundaries; together with LVG_RSN_RT_ID they form the composite primary key BEN_LVG_RSN_RT_F_PK, which is also the sole documented unique index and therefore the business-key candidate for this table.
  • LVG_RSN_CD — the leaving reason code, the business attribute that determines which departure circumstance the rate applies to.
  • VRBL_RT_PRFL_ID — reference to the variable rate profile that supplies the rate value associated with the leaving reason.
  • EXCLD_FLAG — indicates whether the record is excluded from processing, a standard Oracle EBS inclusion/exclusion control.
  • ORDR_NUM — sequence or ordering value used when multiple rows apply.
  • BUSINESS_GROUP_ID — the business group owning the configuration row, supporting multi-organisation separation.
  • OBJECT_VERSION_NUMBER — optimistic locking token used by the OAF/BC4J framework.
  • LRN_ATTRIBUTE_CATEGORY and LRN_ATTRIBUTE1 through LRN_ATTRIBUTE30 — the descriptive flexfield segment columns, providing thirty attribute slots for customer-specific extensions.
  • Standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE.

The surrogate key LVG_RSN_RT_ID identifies a row uniquely across time; the effective dates distinguish successive versions of the same logical definition.

Common Use Cases and Queries

This table is typically queried during benefit calculation and eligibility processing to resolve the rate applicable to a participant's leaving reason as of a given date. A common pattern retrieves the currently effective row for a code:

  • Filter on LVG_RSN_CD = :p_code and TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE.
  • Restrict to EXCLD_FLAG = 'N' to exclude disabled configuration rows.
  • Order by ORDR_NUM when more than one qualifying row exists.
  • Join to the variable rate profile via VRBL_RT_PRFL_ID to obtain the resolved rate value.
  • Constrain by BUSINESS_GROUP_ID in multi-group environments.

Reporting uses include auditing leaving-reason rate configuration across effective periods, comparing rate assignments between business groups, and identifying codes with no currently effective rate. Date-effective joins should always be used rather than equating on the ID alone, since historical versions remain in the table.

Related Objects

The documented schema exposes no foreign keys, so relationships are functional rather than enforced. The most significant related objects are:

  • BEN_VRBL_RT_PRFL_F — the variable rate profile referenced through VRBL_RT_PRFL_ID, supplying the underlying rate definition.
  • BEN_LVG_RSN — the leaving reason reference table corresponding to LVG_RSN_CD.
  • BEN_LVG_RSN_RT_F_PK — the primary key index enforcing uniqueness on LVG_RSN_RT_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE.
  • BEN_LVG_RSN_RT and related date-tracked views — the interface layer typically used by forms and concurrent programs to read effective rows.
  • BEN_BNFT_RSLT_F — the benefits result table where resolved rates are consumed during processing.
  • Payroll and compensation extract programs in the BEN module that consume leaving-reason rates during termination processing.

Because the object is classified as standalone, integration is driven by business attributes such as LVG_RSN_CD and VRBL_RT_PRFL_ID rather than declarative foreign keys, and implementers should validate these relationships in configuration data.