Search Results l_type




Overview

APPS.PER_QH_TIMELINE is a PL/SQL package body belonging to the Oracle Human Resources (PER) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name derives from "PER" (Human Resources) and "QH" (Questionnaire/HR timeline), reflecting its role in supporting the chronological ("timeline") presentation of person and assignment data within the HR datetrack framework. The package exposes a set of date-navigation utilities that allow a calling form or process to step through date-effective records — determining the first, previous, next, and last valid dates associated with a given field, person, or assignment. The package is classified by ETRM as OTHER, indicating it is an internal supporting utility rather than a formally published public API. The header comment (peqhtmln.pkb 120.1.12010000.2) confirms its lineage as a core HR object shipped with the EBS 12.1 code line and carried forward into 12.2.

Key Procedures and Functions

The package body documents five procedures, all centered on date resolution for date-tracked HR entities:

  • GET_DATES — The primary workhorse. It resolves the column, table, and datatype associated with a requested field, then assembles and executes a dynamic SQL statement to return a collection of relevant date records. It takes a field identifier (for example, a maintain-style screen field such as MAINTAIN.PERSON_TYPE), security mode, effective date, datetrack date, person identifier, assignment identifier, and business group identifier, returning a date table. Internally it uses a REF CURSOR and a local variable named l_type (a VARCHAR2(2)) to hold a type code — 'N' for numeric and 'V' for varchar — which governs how the selected value is interpreted and formatted.
  • GET_FIRST_DATE — Returns the earliest date in the timeline for the given field and entity context.
  • GET_PREVIOUS_DATE — Returns the date immediately preceding a supplied reference date within the same timeline.
  • GET_NEXT_DATE — Returns the date immediately following a supplied reference date within the same timeline.
  • GET_LAST_DATE — Returns the latest (most recent) date in the timeline for the field and entity context.

Tables Accessed

The ETRM metadata records a single referenced table via APPS synonym: PLITBLM. In the EBS data model, PLITBLM is the PL/SQL "who" table — a generic, name-value store (EMP_NAME and EMP_VALUE columns) used to persist small pieces of session or cache state. The package's dynamic date logic additionally queries the date-tracked HR base tables identified at runtime inside GET_DATES, including PER_PERSON_TYPE_USAGES_F, PER_ALL_PEOPLE_F, PER_PERSON_TYPES_TL, and lookup tables such as HR_LOOKUPS. These are resolved dynamically according to the requested field (for example, PERSON_TYPE_ID against PER_PERSON_TYPE_USAGES_F, or BACKGROUND_CHK_STATATUS against PER_ALL_PEOPLE_F), which is why the static table list is minimal.

Usage Notes

PER_QH_TIMELINE is an internal utility rather than a standalone concurrent program. It is typically invoked by HR forms and related timeline display logic to populate date-selection lists and navigation controls, especially where users browse date-effective person or assignment records. The package is not referenced by any other documented package (referenced-by count of zero), so its callers live in the form layer or in ad hoc custom code rather than in the packaged API stack. Developers extending HR self-service or custom timeline screens may call these procedures directly, supplying a valid field token, security mode, effective and datetrack dates, and the person/assignment/business group context. Because GET_DATES builds SQL dynamically from field-to-column mappings, callers must use only recognized field tokens; unrecognized values will not resolve to a table and column, and no timeline rows will be returned.