Results for “ben_acty_base_rt_d”

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

Overview

BEN_ACTY_BASE_RT_D is an APPS-owned, VALID database view within the BEN (Advanced Benefits) product module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It presents a user-facing, descriptive representation of activity base rates, which are records that define how benefit rates are calculated and applied against activities such as enrollment, eligibility, and costing processes. The object carries a "Retrofitted" designation in the ETRM metadata, indicating that the trailing "_D" denotes a decoded or descriptive view rather than a physical table; the underlying data resides in the "_F" (fact/base) table.

The view's principal role is to translate raw coded values stored in the base table into human-readable meanings using the HR_GENERAL.DECODE_LOOKUP function. Codes such as rate types, transaction types, parent/child relationships, and various YES/NO flags are surfaced as their lookup meanings. This makes the view particularly suitable for reporting, data extraction, and integration scenarios where downstream consumers require readable attribute values rather than internal codes, and it is the object most commonly returned when the term "ben_rt_typ" is searched, since rate type decoding is a core part of its projection.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through synonyms in the APPS schema:

• BEN_ACTY_BASE_RT_F — the primary base table holding the activity base rate records. The view aliases this as ABR and derives every business column from it, including the ROWID, which is exposed as ROW_ID.
• FND_USER — joined via an outer join (FUSER.USER_ID (+) = ABR.LAST_UPDATED_BY) to resolve the identity of the user who last updated each rate record.
• HR_GENERAL — a PL/SQL package rather than a table, invoked repeatedly in the SELECT list to decode stored lookup codes into their descriptive meanings.

Because BEN_ACTY_BASE_RT_F is an effective-dated table, the view inherits its EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns, and consumers must supply date-bounded predicates to obtain point-in-time results.

Key Columns

• ROW_ID — the ROWID of the underlying base table row, useful for direct row addressing.
• ACTY_BASE_RT_ID — the primary key of the activity base rate record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range during which the record is valid.
• ACTY_TYP_MEANING — decoded activity type from the BEN_ACTY_TYP lookup.
• NAME — the descriptive name of the activity base rate.
• RT_TYP_MEANING / BNFT_RT_TYP_MEANING — decoded rate type and benefit rate type values from the BEN_RT_TYP lookup; these are the columns most directly associated with searches for "ben_rt_typ".
• TX_TYP_MEANING — decoded transaction type from BEN_TX_TYP.
• Flag columns — USE_TO_CALC_NET_FLX_CR_MEANING, ASN_ON_ENRT_MEANING, ABV_MX_ELCN_VAL_ALWD_MEANING, BLW_MN_ELCN_ALWD_MEANING, DSPLY_ON_ENRT_FLAG meanings, and several additional YES_NO flags controlling calculation, enrollment display, and default processing behavior.
• PARNT_CHLD_MEANING — decoded parent/child relationship from BEN_PRNT_CHLD.
• RT_MLT_MEANING — decoded rate multiplier from BEN_MLT.
• RCRRG_MEANING, ALWS_CHG_MEANING, ELE_ENTRY_VAL_MEANING — decoded recurrence, allowance/charge, and element entry value codes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — audit columns, with the latter resolved against FND_USER.
• PAY_RATE_GRADE_RULE_ID — reference to the associated pay rate grade rule.

Common Use Cases and Queries

Typical scenarios include auditing benefit rate configurations, validating effective-dated rate definitions, and feeding decoded rate attributes into downstream reporting or integration layers.

Sample query for rate type analysis:

• SELECT ACTY_BASE_RT_ID, NAME, RT_TYP_MEANING, BNFT_RT_TYP_MEANING, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM BEN_ACTY_BASE_RT_D WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;
• SELECT ACTY_BASE_RT_ID, NAME, RT_TYP_MEANING FROM BEN_ACTY_BASE_RT_D WHERE RT_TYP_MEANING = 'Flat Amount';
• SELECT d.NAME, d.USE_CALC_ACTY_BS_RT_MEANING, u.USER_NAME FROM BEN_ACTY_BASE_RT_D d, FND_USER u WHERE d.LAST_UPDATED_BY = u.USER_ID;

All queries should apply effective date filters, since the view returns historical as well as current rows.