Results for “ben_fl_tm_pt_tm”

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

Overview

APPS.BEN_FL_TM_PT_TM_RT_D is a database view owned by the APPS schema and registered within the Oracle E-Business Suite as part of the Advanced Benefits (BEN) module. It is identified in the ETRM metadata with the FND Design Data reference BEN.BEN_FL_TM_PT_TM_RT_D and carries a status of VALID. The view belongs to the family of "D" (denormalized/descriptive) views that Oracle Benefits exposes over its core date-tracked rule tables, and it is marked internally as View Type "Internal," accompanied by the standard Oracle notice that the object is for internal use only and is not supported for direct customer access except through standard Oracle Applications programs.

Functionally, BEN_FL_TM_PT_TM_RT_D presents the relationship between a variable rate profile and the time period (or time meaning) that governs when that rate profile becomes effective for a given benefit plan or program. A user searching for the term "fl_tm_pt_tm_meaning" is typically looking for the friendly, translated value corresponding to the FL_TM_PT_TM_MEANING column, which is the meaning text resolved for the time-period reference used in a variable rate rule. Because the view shields callers from having to join lookups and date-tracked rows manually, it is used by Benefit configuration screens, self-service pages, and data extraction routines to display a human-readable time period rather than a raw lookup code.

Underlying Base Objects

The view is defined over four documented referenced objects within the APPS schema. Two are synonyms pointing at the underlying date-tracked base tables: BEN_FL_TM_PT_TM_RT_F, which holds the effective-dated rows for the time-period-to-time-meaning rate relationship (the "F" table following Oracle's date-tracked table naming convention), and BEN_VRBL_RT_PRFL_F, which holds the variable rate profile definitions themselves and supplies VRBL_RT_PRFL_NAME. Two further objects supply supporting semantics: HR_LOOKUPS is the view used to resolve lookup meanings, and FND_USER is referenced for the standard who columns. The PL/SQL package HR_API is also referenced in the dependency chain, indicating that business rules or validation logic are applied when the descriptive view is materialized or refreshed.

The view surfaces the primary key FL_TM_PT_TM_RT_ID along with the date-track columns EFTIVE_START_DATE and EFFECTIVE_END_DATE, and adds the ROW_ID (ROWID), the raw lookup EXCLD_MEANING, the ordering column ORDR_NUM, the resolved FL_TM_PT_TM_MEANING, VRBL_RT_PRFL_NAME, and the standard LAST_UPDATE_DATE and LAST_UPDATED_BY who columns.

Key Columns

• ROW_ID — Physical ROWID of the underlying date-tracked row; useful for direct row addressing in maintenance scripts.
• FL_TM_PT_TM_RT_ID — Surrogate primary key tying the time-period/time-meaning rule to its variable rate profile.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-track window defining when the configuration row is valid; these drive the "as-of" filtering that Benefits requires.
• FL_TM_PT_TM_MEANING — The translated meaning of the time-period lookup, i.e., the user-facing value that answers the "fl_tm_pt_tm_meaning" lookup. This is the column most commonly requested by report writers.
• EXCLD_MEANING — Text describing excluded periods or conditions applicable to the rate rule.
• ORDR_NUM — Sequence number controlling display or evaluation order of the rows.
• VRBL_RT_PRFL_NAME — Name of the variable rate profile to which the time-period rule applies.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — Standard audit columns identifying when and by whom the row was last changed.

Common Use Cases and Queries

Typical uses include confirming which time period meanings are configured for a variable rate profile, resolving the display text behind a stored lookup code, and building extraction feeds for downstream rate calculation engines. All queries should apply effective-date filtering because the underlying "F" table is date-tracked.

SELECT FL_TM_PT_TM_RT_ID,
       VRBL_RT_PRFL_NAME,
       FL_TM_PT_TM_MEANING,
       EXCLD_MEANING,
       EFFective_START_DATE,
       EFFECTIVE_END_DATE,
       ORDR_NUM
  FROM APPS.BEN_FL_TM_PT_TM_RT_D
 WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE
 ORDER BY ORDR_NUM;

To target a specific profile, restrict on VRBL_RT_PRFL_NAME. To audit recently changed configuration, filter on LAST_UPDATE_DATE and join LAST_UPDATED_BY to FND_USER for the user name. Because the view is flagged internal and unsupported for direct access, production integrations should prefer calling the supported Benefits APIs rather than embedding these queries in custom code.