Results for “ben_acty_base_rt_f”

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

Overview

BEN_ACTY_BASE_RT_F is a transactional table in the BEN (Advanced Benefits) product schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the values, rates, limits, and calculation rules that drive activities within benefit plans or plan options. In EBS Advanced Benefits, an "activity" represents a discrete processing step—such as computing an eligibility result, deriving an enrollment value, or applying a rate—and this table supplies the base rate and control parameters those activities consume at runtime.

The table is date-tracked through EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, and in the 12.2.2 schema it also carries ZD_EDITION_NAME, indicating support for the editioning model introduced with Online Patching. The documented physical schema lists 142 columns, reflecting the breadth of configuration possible for rate and value definition. Under a heuristic Data Vault classification mined from its foreign-key structure, this object is best modeled as a link, since it resolves relationships among compensation-level factors, cost-allocation key flexfields, plan/option hierarchy identifiers, and input values rather than acting as a pure reference hub or a dependent satellite.

Key Information Stored

The primary key is a surrogate composite defined by BEN_ACTY_BASE_RT_F_PK, built on ACTY_BASE_RT_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. The documented 12.2.2 unique index additionally includes ZD_EDITION_NAME, making that combination the business-key candidate for edition-aware lookups. ACTY_BASE_RT_ID is the surrogate identifier that uniquely tags each activity base rate record across its date-effective versions.

The most significant descriptive and control columns include:

• NAME — user-facing name of the activity base rate definition.
• ACTY_TYP_CD, SUB_ACTY_TYP_CD — classify the activity and its subtype, governing which calculation path applies.
• RT_TYP_CD, BNFT_RT_TYP_CD, TX_TYP_CD, RT_USG_CD, RT_MLT_CD, RNDG_CD, RNDG_RL — define the rate type, benefit/tax treatment, usage, multiplier, and rounding behaviour.
• VAL, DFLT_VAL, MN_ELCN_VAL, MX_ELCN_VAL, INCRMT_ELCN_VAL, LWR_LMT_VAL, UPR_LMT_VAL — the underlying value and election boundary controls.
• VAL_CALC_RL, INPUT_VA_CALC_RL, MN_MX_ELCN_RL, RATE_PERIODIZATION_RL — formula and rule references used during calculation.
• COMP_LVL_FCTR_ID, TTL_COMP_LVL_FCTR_ID, PTD_COMP_LVL_FCTR_ID, CLM_COMP_LVL_FCTR_ID — compensation-level factor references for rate derivation.
• COST_ALLOCATION_KEYFLEX_ID — links the activity to a payroll cost-allocation key flexfield.
• PGM_ID, PL_ID, OIPL_ID, PLIP_ID, OPT_ID, PTIP_ID — scope the record to specific programs, plans, and options.
• ACTY_BASE_RT_STAT_CD, BUSINESS_GROUP_ID, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER — status, operating unit scoping, and concurrency/audit control.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include tracing which activity base rate values apply to a given plan option, auditing changes to rate limits and rounding rules, and extracting configuration for a benefit plan migration or clone.

• Current effective rates for a plan: filter on PLAN identifiers and the effective range, e.g. WHERE PL_ID = :p_plan AND TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE.
• Value and limit audit: select ACTY_BASE_RT_ID, NAME, MN_ELCN_VAL, MX_ELCN_VAL, LWR_LMT_VAL, UPR_LMT_VAL, and LAST_UPDATE_DATE ordered by ACTY_BASE_RT_ID and EFFECTIVE_START_DATE to review history.
• Rounding and calculation review: join RNDG_CD/RNDG_RL and VAL_CALC_RL to confirm how benefit amounts are derived before enrichment testing.
• Child activity traversal: use PARNT_ACTY_BASE_RT_ID and PARNT_CHLD_CD to reconstruct hierarchical activity-to-activity dependencies.

Because the table is date-effective, queries should always constrain the effective date range or use a current-row view (for example, an _F to _V or _UVL synonym) to avoid duplicate historical rows.

Related Objects

Documented foreign keys establish the primary dependencies for this table:

• BEN_COMP_LVL_FCTR — referenced twice, via BEN_ACTY_BASE_RT_F.COMP_LVL_FCTR_ID and TTL_COMP_LVL_FCTR_ID, providing compensation-level factor values used in rate computation.
• PAY_COST_ALLOCATION_KEYFLEX — referenced via COST_ALLOCATION_KEYFLEX_ID, tying the activity to payroll cost-allocation flexfield structures.

Additional related objects derived from the column set include BEN_PGM_F, BEN_PL_F, BEN_PLIP_F, BEN_OIPL_F, BEN_PTIP_F, and BEN_OPT_F for plan, option, and plan-in-program hierarchy resolution. The parent-child self-reference on PARNT_ACTY_BASE_RT_ID links rows within this same table, and the associated BEN_ACTY_BASE_RT definition and validation entities in the BEN schema govern setup and processing of these activity base rate records.