Search Results get_column_data




Overview

HR_GENERAL_UTILITIES is a shared PL/SQL utility package in the Oracle E-Business Suite Human Resources (HR) module. It supplies reusable helper logic that other HR packages, forms, and concurrent programs call to perform common tasks such as retrieving person records, manipulating dates, resolving lookup codes, generating HTML/script output, and dynamically reading column data from database tables. Because it is an OTHER-classified utility package owned by APPS, it is not a public business API but an internal toolkit referenced by approximately twenty other packages. It therefore underpins much of the day-to-day behavior of Oracle HRMS without exposing a formal integration contract.

Key Procedures and Functions

The package exposes forty-one documented procedures and functions. Among the most significant are the following.

Tables Accessed

The package reads and writes a small, focused set of objects:

  • PER_ALL_PEOPLE_F — The date-tracked person table, accessed through GET_PERSON_RECORD and related routines.
  • ALL_TAB_COLUMNS — Used together with DBMS_SQL by GET_COLUMN_DATA to resolve column metadata for dynamic retrieval.
  • DBMS_SQL — The Oracle dynamic SQL package, central to dynamic column access.
  • HTP — The HTML toolkit, used by the script-generating routines.
  • WF_ITEMS and PLITBLM — Supporting Oracle Workflow and PL/SQL table items.

Usage Notes

HR_GENERAL_UTILITIES is invoked internally by other HR packages, Oracle Forms, and concurrent programs to standardize common HR operations. Developers writing custom HR extensions in EBS 12.1.1 or 12.2.2 frequently call GET_COLUMN_DATA when a column name must be resolved dynamically, or the lookup and date helpers for validation and formatting. Because the package is classified as OTHER rather than a supported public API, its signatures are not guaranteed to remain stable across patches or upgrades. Customizations should therefore wrap these calls defensively and avoid assuming fixed parameter lists, relying instead on the documented behavior.