Search Results insert_maintain_data




Overview

APPS.PER_QH_MAINTAIN_UPDATE is a PL/SQL package body belonging to the Oracle E-Business Suite HRMS (Human Resources Management System) schema. Its name derives from the "PER_QH" prefix associated with Oracle Quality/HR datetrack maintenance utilities, and its stated purpose is to maintain person and assignment records within the PER_ALL_PEOPLE_F and related datetrack-enabled entities. In ETRM metadata the object is classified as OTHER rather than a public API, indicating that it is an internal utility package rather than a formally published interface. The package carries the internal header revision peqhmnti.pkb 120.13.12020000.4, dated 27 March 2013, confirming compatibility across the 12.1.1 and 12.2.2 release families. The package exposes a package-level variable g_package used for error-stack identification, a common convention in Oracle HRMS PL/SQL for recording the originating package name in raised exceptions.

Key Procedures and Functions

The documented interface comprises three procedures. Each is oriented toward the maintenance lifecycle of a person record rather than ad-hoc querying.

  • INSERT_MAINTAIN_DATA — Creates a new person and associated datetracked records. It accepts an effective date and business group as inputs, and returns identifiers and date ranges (person ID, validation start/end dates) along with person type, name, applicant, background check, hire date, and related attributes. Many parameters are declared IN OUT NOCOPY, allowing the procedure to echo or adjust values such as applicant number, hire date, and placement date. This is the entry point that the searched term "insert_maintain_data" refers to.
  • UPDATE_MAINTAIN_DATA — Applies datetracked corrections or amendments to an existing person and dependent records, preserving the effective dating semantics of PER_ALL_PEOPLE_F.
  • LOCK_MAINTAIN_DATA — Acquires the row-level or datetrack locks required before an update or insert can be safely committed, preventing concurrent maintenance from corrupting date-tracked history.

Tables Accessed

The package reads and writes a broad set of HRMS tables via APPS synonyms. Person-level attributes are stored in PER_ALL_PEOPLE_F, while employment spans are held in PER_PERIODS_OF_SERVICE and placement data in PER_PERIODS_OF_PLACEMENT. Assignments are maintained in PER_ALL_ASSIGNMENTS_F, with status definitions in PER_ASSIGNMENT_STATUS_TYPES. Person classification relies on PER_PERSON_TYPES. Supplementary person data is captured in PER_ADDRESSES, PER_PHONES, PER_APPLICATIONS, PER_CHECKLIST_ITEMS, PER_DEPLOYMENT_FACTORS, and PER_PAY_PROPOSALS. Organizational and legislative context is provided by PAY_PEOPLE_GROUPS, PAY_GRADE_RULES_F, and HR_SOFT_CODING_KEYFLEX.

Usage Notes

As an internal maintenance package, PER_QH_MAINTAIN_UPDATE is typically invoked from HRMS forms, concurrent programs, and other server-side packages rather than called directly by end users. ETRM records it as referenced by one other package, confirming it sits beneath a higher-level caller in the HRMS call stack. Because its classification is OTHER, Oracle does not guarantee backward compatibility of its signature; custom code should avoid direct invocation and instead use supported public APIs. The heavy use of NOCOPY OUT parameters and datetrack validation dates indicates it is designed for batch or form-driven maintenance where effective dating must remain consistent.