Search Results hr_qualification_type_api




Overview
Explore in AI Chat

Overview

HR_QUALIFICATION_TYPE_API is a public PL/SQL API in the APPS schema that provides the supported programmatic interface for creating, maintaining, and removing qualification type definitions within Oracle Human Resources. Qualification types are the top-level classification records that group individual qualifications tracked for employees, applicants, and other person records managed in Oracle EBS. In Release 12.1.1 and 12.2.2, this package belongs to the HR Foundation layer and is classified as an API, meaning that Oracle supports direct invocation of its procedures for controlled data manipulation, unlike the underlying base tables.

The package encapsulates the business logic, validation, and multi-lingual (translated) handling required to keep qualification type data consistent. Because it wraps the base tables rather than exposing them directly, it ensures that surrogate keys, system-name identifiers, date-tracked columns, and language-dependent descriptions are populated correctly, and that the correct WHO columns and audit attributes are applied. Direct DML against the underlying tables is therefore discouraged in favour of this API.

Key Procedures and Functions

The documented API exposes three procedures, all of which operate on the qualification type entity:

  • CREATE_QUALIFICATION_TYPE — Inserts a new qualification type record. It generates and validates the internal identifiers, establishes the translated description rows, and applies the standard HR validation and audit conventions for a newly defined qualification type.
  • UPDATE_QUALIFICATION_TYPE — Modifies an existing qualification type. It supports changes to the descriptive and translated attributes of an existing record while preserving the relationships between the base qualification type row and its language-specific rows.
  • DELETE_QUALIFICATION_TYPE — Removes a qualification type. It manages the deletion of both the base row and its associated translated (TL) rows, subject to the standard HR referential and validation rules applied by the API.

Each procedure is designed to be called within the standard HR API calling convention, in which the caller supplies a business-group-aware parameter set and receives a success/failure status together with an error message. Parameter lists are not reproduced here; refer to the packaged specification in the database for the authoritative signature.

Tables Accessed

The package operates against two documented base tables, accessed through APPS synonyms:

  • PER_QUALIFICATION_TYPES — The base (non-translated) table holding the qualification type definition, its identifying columns, and its system-name attribute. CREATE, UPDATE and DELETE all read and write this table.
  • PER_QUALIFICATION_TYPES_TL — The translation table storing the language-specific description and name for each qualification type. This table is populated and maintained alongside the base row so that qualification types display correctly in each installed language.

The dependency on APPS.HR_API indicates that the package reuses the shared HR API utility layer for common validation, WHO column population, and message handling rather than re-implementing that logic.

Usage Notes

HR_QUALIFICATION_TYPE_API is the recommended entry point whenever qualification type data must be inserted or changed programmatically. It is typically invoked from custom PL/SQL, data-conversion or migration scripts, and from integration code loading HR setup data. The documented dependency list shows that the package is referenced by HRDPP_CREATE_QUALIFICATION_TYP and HRDPP_UPDATE_QUALIFICATION_TYP, indicating that the HR data-pump / setup-copy utilities for qualification types build on this API rather than performing direct table maintenance. HR_NO_QUALIFICATION_TYPE_API, the North America (NO) localisation variant, also references it, reflecting the standard localisation pattern in which a country-specific package delegates to the core API.

Because the API is a supported public interface, customisations that must create or maintain qualification types should call CREATE_QUALIFICATION_TYPE, UPDATE_QUALIFICATION_TYPE, and DELETE_QUALIFICATION_TYPE rather than issuing DML against PER_QUALIFICATION_TYPES or PER_QUALIFICATION_TYPES_TL directly. This preserves multi-lingual integrity and ensures future upgrades of the HR foundation layer continue to handle the records correctly.