Results for “ghr_rei_shd”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GHR_REI_SHD is the package specification (header) for the Oracle E-Business Suite server-side PL/SQL package APPS.GHR_REI_SHD. The name decomposes as GHR (the product short name historically associated with Oracle Human Resources / iRecruitment-family schema objects), REI (Request Extra Information), and SHD (a header or shadow specification module generated by Oracle's standard table-handler code generator). Its primary business function is to define the global record type and the public interface used to manipulate request extra information records — the flexible descriptive-flexfield style data attached to purchase or iRecruitment requests through the GHR_PA_REQUEST_EXTRA_INFO entity.

The package specification exposes a single global PL/SQL record type, G_REC_TYPE, which mirrors the column layout of the underlying request extra information table. This record includes the surrogate key columns PA_REQUEST_EXTRA_INFO_ID and PA_REQUEST_ID, a descriptive INFORMATION_TYPE column, a REI_ATTRIBUTE_CATEGORY with twenty REI_ATTRIBUTE1 through REI_ATTRIBUTE20 flexfield columns of VARCHAR2(150), and a parallel REI_INFORMATION_CATEGORY with REI_INFORMATION1 through REI_INFORMATION20 or more context columns. By publishing this record type in the specification, the package allows other PL/SQL units, forms, and concurrent programs to pass entire request-extra-information rows as a single strongly typed variable rather than as long positional parameter lists. The header carries the standard EBS version banner ($Header: ghreirhi.pkh 120.1.12010000.1), confirming it is a released 12.1.1/12.2.2 file maintained by Oracle development.

Key Procedures and Functions

The ETRM metadata documents four program units in this package. Their names and purposes are as follows:

• CONSTRAINT_ERROR — A utility routine used to signal or handle constraint violations raised while manipulating request extra information rows. It centralises the error-raising behaviour so that callers receive consistent Oracle error messages when integrity rules on the extra-information table are breached.
• API_UPDATING — A status or gating function that indicates whether an API-driven update is currently in progress. This is a common EBS pattern used to prevent recursive or conflicting modifications when the same record is being touched by both the base table handler and a calling API.
• LCK — The locking routine. It obtains the appropriate row-level lock on the target request extra information record before an update, ensuring serialized access and preventing lost updates in a multi-user environment.
• CONVERT_ARGS — A helper that converts an incoming argument or record representation into the internal format expected by the table handler. It bridges the caller's parameter structure and the global G_REC_TYPE record, normalising values before insert or update processing.

No parameter lists are documented in the available metadata, and none should be assumed; each routine is described solely by its role in the generated table-handler pattern.

Tables Accessed

Two tables are referenced through APPS synonyms. GHR_PA_REQUEST_EXTRA_INFO is the primary base table: it stores the request extra information rows whose columns are reflected in the G_REC_TYPE record, and read, insert, update, and delete operations against it flow through this package. ALL_CONSTRAINTS is the Oracle data dictionary view used by the constraint-handling logic to inspect and validate constraint definitions — typically within CONSTRAINT_ERROR — so that violations are detected and reported accurately. The use of ALL_CONSTRAINTS rather than a user-specific view indicates the package dynamically examines constraint metadata at runtime.

Usage Notes

As a shadow/header module in Oracle's generated table-handler framework, GHR_REI_SHD is not normally invoked directly by end users. It is called by the corresponding body package, GHR_REI_SHB, and by higher-level business APIs that persist request extra information. Within Oracle EBS 12.1.1 and 12.2.2, such calls originate from OA Framework pages, Oracle Forms, or concurrent programs that capture and save flexible request attributes on purchase requisitions and related request objects. The ETRM metadata records that this package is referenced by six other packages, confirming its role as a shared interface layer. Customisations should avoid direct DML on GHR_PA_REQUEST_EXTRA_INFO and instead route through the documented API entry points, preserving the locking, validation, and constraint-handling behaviour implemented by LCK, API_UPDATING, CONVERT_ARGS, and CONSTRAINT_ERROR.