Search Results ben_dsbld_rt_d




Overview
Explore in AI Chat

Overview

BEN_DSBLD_RT_D is a reporting view owned by the APPS schema within the Oracle Advanced Benefits (BEN) module. It derives its name from the disabled rates entity it exposes, with the "_D" suffix indicating a descriptive (denormalized) presentation of the underlying transactional table. The view surfaces disabled rate configuration records that control how participants who are classified as disabled under a registered disability designation are treated with respect to a variable rate profile.

Functionally, the view transforms the normalized data in the underlying base table into a business-readable format by resolving foreign keys into user-facing values. The numeric disability lookup code is translated through HR_LOOKUPS into its descriptive meaning, the variable rate profile identifier is resolved to the profile name, and the last updated by identifier is resolved to the FND_USER user name. This makes the view suitable for concurrent program reports, data extracts, and integration interfaces where descriptive rather than coded values are required.

Underlying Base Objects

The view is defined over four primary objects joined within its SQL definition:

  • BEN_DSBLD_RT_F — the core disabled rate definition table and the driving table of the join. All effective-dated attributes originate here.
  • BEN_VRBL_RT_PRFL_F — the variable rate profile table, joined via VRBL_RT_PRFL_ID to supply the profile context and name.
  • HR_LOOKUPS — the Oracle HR lookup view, joined on LOOKUP_TYPE = 'REGISTERED_DISABLED' and LOOKUP_CODE = DSBLD_CD to supply the meaningful disability definition.
  • FND_USER — the application user table, outer-joined (via USER_ID(+)) to resolve the LAST_UPDATED_BY identifier to a user name. The outer join ensures rows remain visible even when the updating user has been removed or remains unresolved.

The documented metadata also lists HR_API as a referenced package dependency, reflecting the standard Advanced Benefits pattern in which HR_API handles who-column population during base table maintenance.

Key Columns

  • DSBLD_RT_ID — Primary identifier for the disabled rate record.
  • DSBLD_TYPE — Exposes the MEANING value from HR_LOOKUPS for the registered disabled lookup code, providing the human-readable disability designation.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The effective dating range governing when the rate restriction is valid.
  • ORDR_NUM — Ordering sequence used to determine the precedence of disabled rate rules when multiple records apply.
  • EXCLD_FLAG — Exclusion indicator governing whether the associated configuration excludes or includes the disabled rate condition.
  • VRBL_RT_PRFL_NAME — The name of the associated variable rate profile, sourced from BEN_VRBL_RT_PRFL_F.
  • LAST_UPDATE_DATE, CREATION_DATE — Audit timestamps recorded on the base row.

Common Use Cases and Queries

The view is most often used to report on or audit disabled rate configuration, to verify effective dating and ordering, and to feed downstream extracts requiring descriptive disability and profile values. A representative query follows:

SELECT dsbld_rt_id, dsbld_type, vrbl_rt_prfl_name, effective_start_date, effective_end_date, ordr_num, excld_flag FROM apps.ben_dsbld_rt_d WHERE effective_end_date = hr_api.g_effective_end_date AND vrbl_rt_prfl_name = :profile ORDER BY ordr_num;

Separately, functional analysts commonly query the view directly through a tool such as Discoverer or a BI Publisher data model, filtering on dsbld_type to isolate a specific registered disability designation across the configuration set.