Search Results registered_disabled




Overview
Explore in AI Chat

Overview

APPS.BEN_DSBLD_RT_D is a reporting and inquiry view within the Oracle E-Business Suite Advanced Benefits (OAB) module. It presents the disability registration rules that determine how a participant may qualify for a registered disabled status and what associated rates, coverage, or eligibility outcomes apply. The view is defined over the disability rate rule base table BEN_DSBLD_RT_F and enriches the underlying rows with descriptive lookup values, variable rate profile names, and audit information for the user who last modified the record.

Because disability rules are effective-dated and version-controlled, this view is frequently used by HR and benefits administrators when reviewing the configuration of registered disabled processing. The user search term "registered_disabled" corresponds directly to the HR_LOOKUPS lookup type referenced within the view definition, making this view the primary reporting surface for that lookup-driven configuration.

Underlying Base Objects

The view is defined over a join of four referenced objects, three of which are synonyms and one a lookup view, with the HR_API package recorded as an additional dependency:

  • BEN_DSBLD_RT_F — the disability rate rule base table, aliased DBR. It supplies the core rule identifiers, effective dates, ordering and exclusion flags, and the disability lookup code.
  • BEN_VRBL_RT_PRFL_F — the variable rate profile base table, aliased VPR. It contributes the profile NAME and the effective-date bounds used to match the rule to the correct profile version.
  • FND_USER — aliased FUSER, supplying USER_NAME for the LAST_UPDATED_BY column via an outer join.
  • HR_LOOKUPS — the lookup values view, aliased HL, filtered to LOOKUP_TYPE = 'REGISTERED_DISABLED'. This join resolves DSBLD_CD to its display MEANING.
  • HR_API — the HR API package recorded as a dependency, typically invoked indirectly through logic on the underlying base entities.

The relationship is rule-to-profile driven: each disability rate rule points at a variable rate profile, and the rule's effective start date is constrained to fall within the profile's effective period, ensuring only contemporaneously valid profile names are returned.

Key Columns

  • DSBLD_RT_ID — unique identifier of the disability rate rule record.
  • MEANING — the decoded display value for the registered disabled lookup code (DSBLD_CD), derived from HR_LOOKUPS.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range during which the rule is active.
  • ORDR_NUM — the sequence number controlling evaluation order when multiple rules apply.
  • EXCLD_FLAG — indicates whether the rule excludes a participant from the associated benefit treatment.
  • NAME — the variable rate profile name linked to the rule.
  • LAST_UPDATE_DATE / USER_NAME — audit information recording when the rule was last changed and by which application user.
  • CREATION_DATE — the date the rule record was originally created.

Common Use Cases and Queries

Typical usage includes configuration review of registered disabled rules, audit of rule ownership and change history, and troubleshooting why a participant was or was not treated as registered disabled. A representative query lists all active rules with their decoded disability meaning:

SELECT dsbld_rt_id, meaning, effective_start_date, effective_end_date, excl_flag, name, user_name FROM apps.ben_dsbld_rt_d WHERE SYSDATE BETWEEN effective_start_date AND effective_end_date ORDER BY ordr_num;

To trace rules attached to a specific variable rate profile:

  • Filter on the NAME column to isolate all disability rules associated with a given profile.
  • Filter on MEANING to report on a specific registered disabled category.
  • Use EFFECTIVE_START_DATE to audit which rules were in force on a historical date.

Because the view applies outer joins to FND_USER and to the profile effective dates, it remains usable even where audit user records or matching profile versions are absent, though join results for those columns may be null.