Results for “ben_fl_tm_pt_tm_rt_f”

50+ results




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

Overview

BEN_FL_TM_PT_TM_RT_F is a dated, entity-owned table within the BEN (Advanced Benefits) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the rates applicable to full time / part time assignment, meaning the compensation or rate values an organization applies to an assignment depending on whether that assignment is treated as full time or part time. The table is date-tracked through the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns, and it carries the standard EBS WHO columns plus a 30-column FTR_ATTRIBUTE flexfield block for customer-defined descriptive data.

The metadata classifies this object heuristically as standalone in Data Vault terms. That is a modeling suggestion rather than a schema fact: the mined foreign-key structure does not expose a hub or link relationship to a parent reference table, so the object is best treated as a self-contained reference or rate table. Where integration is required, the linking key is the surrogate identifier FL_TM_PT_TM_RT_ID rather than a documented foreign key.

Key Information Stored

The surrogate key is FL_TM_PT_TM_RT_ID. The business-key candidate, as documented in the unique index BEN_FL_TM_PT_TM_RT_F_PK, is the composite (FL_TM_PT_TM_RT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE); in practice this means a single rate identity may hold multiple effective-dated versions.

Common Use Cases and Queries

The table is queried most often to resolve the rate that applies to an assignment as of a given date, and to audit historical rate changes. Typical access patterns filter on the assignment's full time / part time code within a business group and constrain on the effective dates.

  • Point-in-time rate lookup: SELECT fl_tm_pt_tm_rt_id, fl_tm_pt_tm_cd, ordr_num FROM ben_fl_tm_pt_tm_rt_f WHERE business_group_id = :p_bg AND fl_tm_pt_tm_cd = :p_code AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
  • Current-row extraction for a specific surrogate key: WHERE fl_tm_pt_tm_rt_id = :p_id AND SYSDATE BETWEEN effective_start_date AND effective_end_date.
  • Change history for auditing: omit the date predicate and order by effective_start_date DESC.
  • Ordered presentation: use ORDER BY ordr_num to reproduce the sequence expected by the benefits engine.

Related Objects

The mined relationship data identifies this object as standalone, so no foreign keys to parent reference tables are documented. The practical associations available from the schema are:

  • BEN.BEN_FL_TM_PT_TM_RT_F_PK — the unique index enforcing the composite business key (FL_TM_PT_TM_RT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE).
  • VRBL_RT_PRFL_ID — the join column to the variable rate profile that references these rates.
  • BUSINESS_GROUP_ID — the join column to the business group / organization definition that scopes the data.
  • FL_TM_PT_TM_CD — the join column to the full time / part time lookup or code used in assignment classification.

Because the table is standalone, implementers should treat FL_TM_PT_TM_RT_ID as the anchor identifier when correlating it with benefits eligibility, rate, and assignment processing logic in custom reports and interfaces.