Results for “ben_age_rt_x”

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

Overview

BEN_AGE_RT_X is a read-only view owned by the APPS schema within the BEN (Advanced Benefits) product family of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. It is flagged as "Retrofitted" in the metadata, indicating it was regenerated to the current base-table lineage following an upgrade of the underlying date-tracked entity. The view exposes the current effective row of the age rate rule entity and is therefore the operational interface used by concurrent processes, forms, and integrations that must resolve an age rate rule as of the system date without supplying explicit effective range predicates.

The defining predicate TRUNC(SYSDATE) BETWEEN ART.EFFECTIVE_START_DATE AND ART.EFFECTIVE_END_DATE constrains output to rules that are active on the current day. The inclusion of TRUNC removes the time component, which is significant because EBS date-tracked tables commonly store effective end dates with a time portion (for example, 23:59:59 on the final day). This view is intended for "as of today" lookups only; historical and future-dated rule evaluation must query the base table BEN_AGE_RT_F directly.

Underlying Base Objects

ETRM documents a single referenced base object: BEN_AGE_RT_F, accessed through the APPS synonym. BEN_AGE_RT_F is the date-tracked ("_F") table holding all effective-dated versions of age rate rule records, and the view projects every column of that table without joining any other entity. The relationship is strictly one-to-many from base to view output over time: many versions may exist in BEN_AGE_RT_F, but at most one survives the current-date filter per unique AGE_RT_ID, assuming correctly maintained, non-overlapping date ranges. No aggregation, joining, or derivation occurs in the view text; it is a filtered projection that preserves the object version number and audit columns of the underlying row.

Key Columns

• AGE_RT_ID — Primary identifier of the age rate rule record, inherited from BEN_AGE_RT_F.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-track range; the view returns only the row where the system date falls inside this range.
• BUSINESS_GROUP_ID — Business group owning the rule; essential for multi-organization and security filtering.
• VRBL_RT_PRFL_ID — Variable rate profile to which the age rate rule belongs, linking the rule to its rates and eligibility configuration.
• AGE_FCTR_ID — Age factor used to derive the age band applied against the variable rate profile.
• ORDR_NUM — Sequencing value that determines evaluation order when multiple age factor rules apply.
• EXCLD_FLAG — Indicates whether the rule is excluded from evaluation.
• ART_ATTRIBUTE_CATEGORY and ART_ATTRIBUTE1 … ART_ATTRIBUTE30 — Descriptive flexfield context and segments for the age rate rule.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — Standard audit and optimistic locking columns.

The user's search term "art_attribute_category" corresponds directly to ART_ATTRIBUTE_CATEGORY, the DFF context column exposed by this view, which confirms the view is the correct source when the attribute category must be read for the currently effective rule.

Common Use Cases and Queries

Typical uses include verification of currently active age rate rules, reporting on attribute category usage, and extraction feeds that require only the effective-today configuration. Because no date parameters can be passed, the view suits "as of now" logic; other effective dates require the base table.

• List active age rate rules for a business group:

  SELECT age_rt_id, vrbl_rt_prfl_id, age_fctr_id, ordr_num, ex cld_flag FROM apps.ben_age_rt_x WHERE business_group_id = :p_bg_id ORDER BY ordr_num;

• Find rules classified under a specific descriptive flexfield context:

  SELECT age_rt_id, art_attribute_category, art_attribute1 FROM apps.ben_age_rt_x WHERE art_attribute_category = :p_category;

• Detect excluded rules prior to rate processing:

  SELECT age_rt_id, ex cld_flag FROM apps.ben_age_rt_x WHERE NVL(ex cld_flag,'N') = 'Y';

All queries should be schema-qualified with APPS and executed with the appropriate business group or security profile context to avoid cross-organization data exposure.