Results for “elig_fl_tm_pt_tm_prte_id”

50+ results




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

Overview

The view APPS.BEN_ELIG_FL_TM_PT_TM_PRTE_D is a denormalized, presentation-oriented database view within the Oracle Advanced Benefits (BEN) module. It surfaces configuration data defining eligibility participation rules that use the "Full-Time / Part-Time" (FL_TM_PT_TM) criteria and an exclusion indicator. These rules are a component of an eligibility profile, which governors whether a person or assignment qualifies for a benefit program, plan, or option. The "_D" suffix and the "Retrofitted" description indicate this object is an older, form-supporting descriptive view that was retrofitted from an earlier EBS release into the current data model, retaining its original column aliasing and outer-join semantics.

The view's role in reporting and integration is to flatten a normalized, multi-table participation-rule structure into a single readable row set. It resolves foreign-key codes into their human-readable meanings and joins to the parent eligibility profile header, so that report authors and integration developers need not re-implement the lookup joins. The FL_TM_PT_TM_CD lookup referenced by the user corresponds to the FL_TM_PT_TM_MEANING column exposed by this view.

Underlying Base Objects

The view is defined over the documented base objects below:

  • BEN_ELIG_FL_TM_PT_TM_PRTE_F — the primary table holding eligibility participation criteria for full-time/part-time classifications. It supplies the foreign key ELIG_FL_TM_PT_TM_PRTE_ID, effective dates, ordering, the FL_TM_PT_TM_CD lookup code, and the EXCLD_FLAG.
  • BEN_ELIGY_PRFL_F — the eligibility profile definition, supplying NAME as ELIGY_PRFL_NAME.
  • FND_USER — resolves LAST_UPDATED_BY to the application user who last modified the rule.
  • HR_LOOKUPS — referenced twice via outer joins: once for lookup type 'EMP_CAT' (the FL_TM_PT_TM code meaning) and once for lookup type 'YES_NO' (the exclusion flag meaning).
  • HR_API — a packaged API referenced by the view metadata, used historically for lookup/validation support.

All joins to the descriptive tables are outer joins ((+)), ensuring a rule row is returned even when a lookup or parent profile row is missing, which preserves data completeness in extracts.

Key Columns

  • ROW_ID — the row identifier of the base participation-rule row, useful as a unique key in extracts and for troubleshooting.
  • ELIG_FL_TM_PT_TM_PRTE_ID — surrogate primary key linking back to the participation-rule table.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective window governing when the rule is in force.
  • ELIGY_PRFL_NAME — the name of the parent eligibility profile to which the rule belongs.
  • ORDR_NUM — the evaluation order or sequence of the rule.
  • FL_TM_PT_TM_MEANING — the descriptive meaning of the full-time/part-time code (originally FL_TM_PT_TM_CD), resolved through HR_LOOKUPS for the EMP_CAT lookup type.
  • EXCLD_MEANING — the Yes/No meaning indicating whether the rule is used as an exclusion (inclusion/exclusion behavior).
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns showing when and by whom the rule was last changed.

Common Use Cases and Queries

Typical scenarios include auditing which eligibility profiles depend on full-time/part-time status, extracting rule configurations for migration or reconciliation, and troubleshooting why a person was or was not deemed eligible. The following query retrieves rule definitions for a given profile name:

SELECT ELIGY_PRFL_NAME,
       ORDR_NUM,
       FL_TM_PT_TM_MEANING,
       EXCLD_MEANING,
       EFFECTIVE_START_DATE,
       EFFECTIVE_END_DATE
  FROM APPS.BEN_ELIG_FL_TM_PT_TM_PRTE_D
 WHERE ELIGY_PRFL_NAME = :p_profile_name
 ORDER BY ORDR_NUM;

A second use case searches for all participation rules that employ a specific full-time/part-time classification:

SELECT ELIGY_PRFL_NAME,
       FL_TM_PT_TM_MEANING,
       EXCLD_MEANING
  FROM APPS.BEN_ELIG_FL_TM_PT_TM_PRTE_D
 WHERE FL_TM_PT_TM_MEANING = :p_meaning;

Because the object is a view, queries are read-only and should be used for inspection, reporting, and integration extracts rather than for transactional updates.