Search Results delete_qualification_type




Overview
Explore in AI Chat

Overview

The APPS.HR_QUALIFICATION_TYPE_API package body is a public Oracle E-Business Suite API responsible for the creation, maintenance, and removal of qualification type definitions within the Oracle Human Resources (PER) schema. Qualification types represent the categories of credentials, licenses, degrees, certifications, and competencies that an enterprise tracks against its workforce — for example "Bachelor of Science," "Professional Engineer License," or "Forklift Operator Certification." Each type is defined once at the business-group level and subsequently referenced by employee qualifications, applicant qualifications, and competency-related processes.

The package encapsulates the business rules, validation logic, and multi-language handling required to keep the underlying PER_QUALIFICATION_TYPES entity and its translation table consistent. Because it is classified as a public API, it constitutes the supported interface through which both Oracle-delivered forms and customer extensions are expected to manipulate qualification type data, insulating callers from the physical column layout and from the surrogate-key and object-version mechanics maintained internally by the HR datetrack framework. The header comment in the source file ($Header: peeqtapi.pkb 115.2) confirms this is a long-standing, stable component of the HR foundation layer that has been shipped with EBS releases since the 11i era and carried forward unchanged into 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented interface exposes three procedures, forming a complete create-read-update-delete surface for the qualification type entity:

  • CREATE_QUALIFICATION_TYPE — Inserts a new qualification type and its associated translated name row. It accepts the effective date, the language code, the qualification type name and category, an optional rank used for ordering, and the standard descriptive flexfield and developer (DFF/Information) attribute columns. As with other HR APIs, an effective date governs the datetracked insert, and the language code determines the PER_QUALIFICATION_TYPES_TL row that carries the user-visible name.
  • UPDATE_QUALIFICATION_TYPE — Modifies an existing qualification type with datetracked update semantics, applying changes effective as of a supplied date. This is the procedure most frequently targeted by the search term update_qualification_type, since it is the sanctioned entry point for renaming a type, changing its category or rank, or correcting flexfield attribute values without directly writing to the base tables. The procedure enforces the same validation rules as creation and writes a new datetracked version of the row rather than overwriting historical data.
  • DELETE_QUALIFICATION_TYPE — Logically removes a qualification type by terminating its datetracked validity, preserving referential integrity with any employee or applicant qualification records that already reference the type.

All three procedures share the convention of a p_validate parameter, allowing callers to execute the full validation path without committing changes — essential for interactive forms that must report errors before the user saves.

Tables Accessed

The package operates against two tables accessed through APPS synonyms:

  • PER_QUALIFICATION_TYPES — The base datetracked entity table holding the qualification type identifier, category, rank, effective start and end dates, business group, and the descriptive flexfield attribute columns.
  • PER_QUALIFICATION_TYPES_TL — The translation table holding the language-specific NAME (and description) for each qualification type, keyed by language and source language, enabling multilingual display.

Rows in the TL table are created, updated, or end-dated in lockstep with the base row so that the two remain synchronized across every datetracked operation.

Usage Notes

This API is invoked primarily from the Oracle HRMS qualification type maintenance forms, and it is referenced by three other packages within the application, indicating reuse by higher-level HR setup or qualification-processing logic. Customers and integrators should call HR_QUALIFICATION_TYPE_API rather than performing direct DML on the underlying tables, because the API enforces datetrack rules, translation consistency, flexfield validation, and business-group security. Typical custom usage includes bulk loading of qualification catalogs from legacy systems, synchronizing external certification registries, and wrapping the procedures in concurrent programs or BPEL/interface tables for inbound integrations.

Callers must supply a valid effective date and, for creation, a language code (defaulting to the session language). Because operations are datetracked, back-dated changes should be issued with care and always in the context of the correct business group, since the API derives the business group from the HR session environment. When p_validate is set to true, the routine performs all checks and raises the standard HR API exceptions without persisting any data, making it suitable for pre-submission validation in custom user interfaces.