Results for “fl_tm_pt_tm”

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

Overview

APPS.BEN_ELIG_FL_TM_PT_TM_PRTE_D is a reporting view within the Oracle E-Business Suite Advanced Benefits (BEN) module. It exposes the configuration of eligibility profile participation criteria based on "full-time / part-time" employment category rules, presenting the denormalized, user-readable form of the BEN_ELIG_FL_TM_PT_TM_PRTE_F base table. The view derives its name from the fl_tm_pt_tm (full-time / part-time) criteria column it centers on, and is a sibling of other eligibility criteria views such as BEN_ELIG_FL_TM_PT_TM_PRTE.

In EBS 12.1.1 and 12.2.2, this view fulfills the classic "D" (descriptive) role: rather than returning meaningless lookup codes and numeric foreign keys, it resolves them to descriptive meanings and user names. It is used by Oracle Forms, OAF pages, and concurrent/reporting programs that display eligibility profile participation criteria, and by integration or diagnostic queries that need human-readable eligibility configuration without joining multiple lookup and profile tables.

Underlying Base Objects

The view is defined over the following documented base objects:

• BEN_ELIG_FL_TM_PT_TM_PRTE_F — the primary driving table (aliased efp); its row is the criterion record and its ROWID is exposed as row_id.
• BEN_ELIGY_PRFL_F — the eligibility profile header (aliased eligy_prfl); joined by eligy_prfl_id to provide the profile name and effective dates.
• HR_LOOKUPS — referenced twice: once for the full-time/part-time code (lookup_type = 'EMP_CAT') and once for the exclusion flag (lookup_type = 'YES_NO').
• FND_USER — supplies user_name for the last updater.
• HR_API — a package referenced by the view, consistent with Benefits' use of HR date-tracking and security APIs.

All joins to BEN_ELIGY_PRFL_F, HR_LOOKUPS, and FND_USER are outer joins (+), so criteria rows are never lost when reference data is missing. The profile join additionally restricts on effective date range: efp.effective_start_date BETWEEN eligy_prfl.effective_start_date(+) AND eligy_prfl.effective_end_date(+).

Key Columns

• row_id — ROWID of the base criterion record, used as the forms row identifier.
• elig_fl_tm_pt_tm_prte_id — primary key of the criterion.
• effective_start_date / effective_end_date — date-tracked validity of the criterion.
• name — name of the parent eligibility profile.
• ordr_num — display order of the criterion within the profile.
• meaning (aliased from fl_tm_pt_tm) — descriptive meaning of the full-time/part-time employment category code.
• meaning (aliased from excld) — Yes/No meaning indicating whether the criterion is an exclusion.
• criteria_weight, criteria_score — weighting and scoring used when the profile evaluates criteria.
• last_update_date, user_name — audit tracking.

Common Use Cases and Queries

Typical uses include verifying that a plan's eligibility profile correctly includes or excludes full-time vs. part-time employees, auditing exclusions, and feeding integration extracts. A representative query follows:

SELECT name, ordr_num, meaning, excld_meaning,
       criteria_weight, criteria_score, user_name
FROM   apps.ben_elig_fl_tm_pt_tm_prte_d
WHERE  TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date
ORDER  BY name, ordr_num;

Because the view already resolves EMP_CAT and YES_NO lookups, it is well suited for report display; perform any additional filtering (for example, by profile name) directly against the exposed columns.