Search Results ghr_pa_request_extra_info_s




Overview
Explore in AI Chat

Overview

GHR_REI_INS is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM repository as an "OTHER" API type. The package serves the Oracle HRMS / Advanced Benefits (or related GHR) subsystem responsible for managing "request extra information" records. The name decomposes into GHR (the HRMS module prefix), REI (Request Extra Information), and INS (Insert). As the "INS" suffix indicates, this package body encapsulates the insert-side business logic for the GHR_PA_REQUEST_EXTRA_INFO entity — the table that stores supplementary data attached to a request (for example, extra attributes captured alongside a personnel action or benefit request). The package is the write-side counterpart to the read/query logic exposed elsewhere, and it is a tightly scoped, single-purpose DML wrapper rather than a broad business API.

Key Procedures and Functions

The ETRM metadata documents two procedures/functions within this package body:

  • INS — The primary insert routine. Its purpose is to create a new row in the GHR_PA_REQUEST_EXTRA_INFO table, populating the columns that carry the request's extra information. Consistent with Oracle HRMS API conventions, INS is expected to validate the incoming attribute values, invoke the corresponding business-rule layer (GHR_REI_BUS) to enforce entity-level logic, and then perform the physical insert. No parameter list is documented in the ETRM extract and none should be assumed; the documented fact is that INS is the insert operation supporting the REI entity.
  • The second documented program unit — The metadata reports a total of two procedures/functions. Only "INS" is named explicitly; the remaining unit is an internal helper associated with insert processing. Its role is to support the INS operation (row construction, sequencing, or delegating to the business layer). Rather than speculate on its signature, it is sufficient to note that it exists solely to service the insert path and is not a standalone public entry point.

Because GHR_REI_INS is a "table handler" style body (the INS/RKI/SHD/BUS naming pattern is the standard Oracle HRMS generated-handler family), the procedures are not intended as a rich public API. They are invoked by the generated business layer and by internal HRMS processing rather than by end users directly.

Tables Accessed

The package operates against two documented tables, both reached through APPS synonyms:

  • GHR_PA_REQUEST_EXTRA_INFO — The base table holding extra-information rows for a request. This is the insert target of the INS procedure.
  • GHR_PA_REQUEST_EXTRA_INFO_S — The shadow/sequence-support table conventionally paired with the base table in Oracle HRMS datetrack-style designs, used for primary-key and version tracking during inserts. The user's search term, "ghr_pa_request_extra_info_s", corresponds directly to this dependent object and is the reason this package surfaces in dependency lookups for that table.

In addition, the documented dependency list shows the package calling GHR_REI_BUS (business rules), GHR_REI_RKI (row-key insert / key generation), GHR_REI_SHD (shadow/date-tracked insert), HR_API and HR_UTILITY (shared HRMS utilities), and STANDARD/DUAL for generic SQL plumbing. These are dependencies, not additional table targets.

Usage Notes

GHR_REI_INS is not referenced by any other database object according to the ETRM metadata, meaning nothing in the shipped schema depends on it directly; instead it is a leaf-level handler invoked at runtime by the HRMS infrastructure and by the generated business layer. In practice it is exercised whenever a request's extra information is created — for example during personnel action or benefits processing that writes supplementary request attributes. It is typically called from within other HRMS packages (through GHR_REI_BUS) rather than from a Form or concurrent program directly. Custom code should not call GHR_REI_INS in isolation; the supported integration point is the REI business API. Because the body holds the implementation while the accompanying specification defines the callable interface, any customization should treat both the INS logic and its supporting handler units as Oracle-owned internals. The package status is VALID in both 12.1.1 and 12.2.2, and its documented footprint is small and stable across those releases.