Results for “rcl_attribute1”

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

Overview

BEN_RLTD_PER_CHG_CS_LER_X is an Oracle EBS Advanced Benefits (BEN) view owned by the APPS schema. Its name follows the standard EBS convention for a date-effective "extract" or "listing" view: the trailing "_X" denotes a view whose WHERE clause restricts rows to the current effective date, and the prefix BEN_RLTD_PER_CHG_CS_LER identifies the underlying entity — the related person change "CS LER" (Life Event Reason) definition. In Advanced Benefits, LER records drive life-event processing, and this structure captures the set of related person changes that qualify or trigger a life-event reason and its associated rule configuration.

Because it appends a TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE predicate, the view always returns only the currently active definition rows, which is the form most commonly required by reports, concurrent program extracts, and integration interfaces that must not see historical or future-dated versions. Its role is therefore to provide a stable, denormalized read surface for the effective row of the base entity, including both the standard descriptive columns and the full RCL_ATTRIBUTE1 through RCL_ATTRIBUTE30 descriptive flexfield (DFF) column set.

Underlying Base Objects

The view is defined with a single source: BEN_RLTD_PER_CHG_CS_LER_F, referenced through a synonym in the APPS schema. The "_F" suffix identifies the base table as the date-effective (F = "From/effective") entity table, holding multiple effective-dated versions of each LER row. The view applies no joins; its entire transformation is the effective-date filter:

SELECT ... FROM BEN_RLTD_PER_CHG_CS_LER_F RCL WHERE TRUNC(SYSDATE) BETWEEN RCL.EFFECTIVE_START_DATE AND RCL.EFFECTIVE_END_DATE

Consequently, the column set of the view mirrors the base table exactly, including audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE) and OBJECT_VERSION_NUMBER, which supports optimistic locking in the underlying PL/SQL APIs.

Key Columns

• RLTD_PER_CHG_CS_LER_ID — Primary key / surrogate identifier for the related person change CS LER row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective range that governs visibility through this view.
• NAME — User-facing name of the LER / related person change definition.
• WHATIF_LBL_TXT — Label text presented in "what-if" life-event simulations.
• OLD_VAL / NEW_VAL — The prior and new values compared to detect the qualifying change.
• SOURCE_COLUMN / SOURCE_TABLE — Identifies the database column and table monitored to detect the change.
• RLTD_PER_CHG_CS_LER_RL — Relationship/foreign-key linking column.
• BUSINESS_GROUP_ID — Multi-tenant (business group) discriminator, essential in any query to isolate the correct enterprise.
• RCL_ATTRIBUTE_CATEGORY and RCL_ATTRIBUTE1 … RCL_ATTRIBUTE30 — Descriptive flexfield context and segment columns. RCL_ATTRIBUTE1, the column named in the user's search, is the first DFF segment and is the most frequently used for customer-specific extensions.
• RULE_OVERRIDES_FLAG — Indicates whether rule overrides apply to the definition.

Common Use Cases and Queries

The principal use case is reporting on the currently effective related person change LER definitions, including any flexfield data stored on RCL_ATTRIBUTE1. A typical query filters by business group and selects the relevant DFF segment:

SELECT RLTD_PER_CHG_CS_LER_ID, NAME, WHATIF_LBL_TXT, SOURCE_TABLE, SOURCE_COLUMN, RCL_ATTRIBUTE1
FROM APPS.BEN_RLTD_PER_CHG_CS_LER_X
WHERE BUSINESS_GROUP_ID = :p_business_group_id;

Because the view already enforces the effective-date predicate, no additional date filter is required for current-row reporting. A second common scenario is a value-set or lookup query in an Oracle Forms/ADF DFF segment that lists valid LER definitions for a business group, ordering by NAME. Note that the view returns only active rows; if historical or future-dated LER versions are needed, the base table BEN_RLTD_PER_CHG_CS_LER_F must be queried directly with an explicit date range. Queries should always include BUSINESS_GROUP_ID to satisfy multi-tenant correctness.