Search Results ghr_dut_upd




Overview
Explore in AI Chat

Overview

GHR_DUT_UPD is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM as an "OTHER" API object. Its name follows Oracle's Human Resources (GHR) naming conventions and denotes a Duty Station update utility. Within the Oracle HRMS enterprise structure, duty stations represent the physical or organizational locations to which employees and applicants are assigned, and they form part of the legislative and business-group driven setup data that HR administrators maintain over time. The package encapsulates the logic required to modify existing duty station definitions in a controlled, API-consistent manner rather than through direct table manipulation. In Oracle EBS releases 12.1.1 and 12.2.2, the object is reported as VALID, confirming that both the package specification and body are compiled and available in the database. Its role is to centralize update processing for duty station records so that dependent entities — duty station APIs, validation routines, and any concurrent processes that consume duty station data — receive consistent results.

Key Procedures and Functions

ETRM documents a single procedure or function entry for this package, identified as UPD. The abbreviated name is consistent with Oracle's convention of naming the update operation within a CRUD-focused package.

  • UPD — The documented update routine. Its purpose is to apply changes to an existing duty station record. Because it is the only documented entry point, it functions as the primary interface through which callers commit modifications to duty station attributes. ETRM does not publish the parameter list for this procedure, so implementers should inspect the package specification in the target environment before invoking it from custom code.

Although the metadata lists only UPD, the package spec and body may contain additional private or supporting subprograms used internally; however, only UPD is formally documented in the ETRM excerpt.

Tables Accessed

The documented table reference for this package is GHR_DUTY_STATIONS_F, accessed through an APPS synonym. This is the base (F) table holding duty station definitions. The _F suffix indicates a date-tracked entity, meaning records carry effective start and end dates and are typically paired with a corresponding _TL translation table and possibly _VL views for multilingual attribute handling. GHR_DUT_UPD reads and writes GHR_DUTY_STATIONS_F to locate the target record by its primary key and to persist the updated column values, including any effective-dating changes. Because effective-dated HR tables use Datetrack validation, the update logic must respect date range overlaps and referential integrity before committing, which explains why the package depends on HR_API.

Usage Notes

The ETRM dependency data shows that GHR_DUT_UPD depends on APPS.GHR_DUT_SHD, APPS.HR_API, and SYS.STANDARD. GHR_DUT_SHD is a shadow (history) package used for audit tracking of changes to duty station data; HR_API supplies the standard Datetrack and HR utility routines. GHR_DUT_UPD is itself referenced by one other package, APPS.GHR_DUTY_STATION_API, which acts as the outward-facing business API and delegates to this update package. The package is therefore most commonly invoked indirectly: Oracle HRMS forms or the duty station business API call GHR_DUTY_STATION_API, which in turn calls GHR_DUT_UPD to perform the physical update. Direct invocation from custom concurrent programs, interfaces, or migration scripts is possible but should be treated cautiously, since bypassing the higher-level API may skip validation and audit shadowing performed in GHR_DUTY_STATION_API. Implementers should call the documented API entry point where one exists, and reserve GHR_DUT_UPD for controlled, well-tested extension scenarios.