Search Results chk_information_type

Overview

The APPS.PQH_PTI_BUS package body is a server-side PL/SQL business logic handler within the Oracle E-Business Suite Human Resources (HRMS) product family, specifically the Budgeting component represented by the PQH module prefix. The PTI element identifies the package as the business-layer handler for the Information Type entity — the table PQH_PTX_INFO_TYPES. This table stores the classification records that determine what kinds of information structures HR budgeting and position-related transactions may use.

The package follows the standard EBS "Table Handler" (TBI) generator pattern, in which a _BUS body houses validation and constraint logic, a _SHD shadow package holds the old-record cache and API state flags, and a _API package exposes the public DML surface. The header comment ($Header: pqptirhi.pkb 120.2 2005/10/12) indicates the body was last shipped in the 11i maintenance stream and remains unchanged through 12.1.1 and 12.2.2 — a common characteristic of stable reference-data handlers.

The package is classified as an OTHER type in the ETRM metadata, meaning it is neither a public API package nor a pure utility; it is an internal validation layer invoked exclusively by the generated API tier.

Key Procedures and Functions

Three procedures are documented for this object. Each corresponds to one DML operation on the underlying Information Type row.

• INSERT_VALIDATE — Executes the pre-insert validation logic. It confirms that mandatory columns are present, that the primary key value is not pre-populated when the row is being created, and that business rules governing information type codes and their relationships are satisfied before the row is committed.
• UPDATE_VALIDATE — Executes the pre-update validation logic. This routine is responsible for the check embodied by chk_information_type: it verifies that the primary key has not been altered by the update, raising a constraint error against PQH_PTX_INFO_TYPES_PK if the primary key has changed. It also validates the object version number for optimistic locking.
• DELETE_VALIDATE — Executes the pre-delete validation logic. It determines whether the Information Type row is eligible for removal, typically by checking for dependent child records in HR budgeting and position structures that would be orphaned by the deletion.

The private helper chk_information_type is not part of the public documented surface but is central to the package's operation. It accepts the information type identifier and object version number, calls pqh_pti_shd.api_updating to determine operation mode, and thereafter either raises constraint_error('PQH_PTX_INFO_TYPES_PK') when the primary key has drifted from pqh_pti_shd.g_old_rec.information_type, or checks for a null primary key during insert.

Tables Accessed

The package operates against PQH_PTX_INFO_TYPES, resolved through the APPS synonym layer, and maintains a cached copy of the pre-update row image in the shadow package global g_old_rec. No additional tables are enumerated in the documented metadata, which is consistent with a pure table-handler body: referential integrity and cross-entity validation are delegated to the _API tier and the database constraints on the table itself.

Usage Notes

PQH_PTI_BUS is never called directly by end users or custom code. It is invoked by the generated PQH_PTI_API package, which is itself called by the HRMS Budgeting forms (such as the Information Type setup form) and by concurrent processes that administer budgeting reference data. Because the package is marked "Internal table handler use only," customer extensions should target the API tier instead. Custom integrations that insert into PQH_PTX_INFO_TYPES directly bypass these validations and risk violating the primary key and version-number invariants enforced here. The package is referenced by three other packages in the ETRM dependency graph, all of which reside within the same generated handler family.