Search Results ghr_duty_station_api




Overview
Explore in AI Chat

Overview

The APPS.GHR_DUTY_STATION_API package body is a public application programming interface within the Oracle E-Business Suite HRMS (Human Resources Management System) schema. Its business function is to provide a controlled, programmatic means of maintaining the duty station records that underpin the Global HR (GHR) data model. A duty station represents the geographic location to which an employee is assigned for payroll, tax, and regulatory purposes, and it is a fundamental reference entity in the assignment and payroll hierarchies of Oracle HRMS.

As an API-classified object, the package encapsulates the business logic and validation rules governing duty station maintenance, exposing a stable interface while insulating calling code from the underlying table structures and business rules. By routing all inserts, updates, and deletes through this API, Oracle preserves data integrity, enforces validation, and ensures that all mandated GHR processing is applied consistently. The package body is documented as VALID in the ETRM repository for both the 12.1.1 and 12.2.2 releases, confirming it is a supported, current component of the GHR feature set.

Key Procedures and Functions

The package body documents three public procedures, corresponding directly to the standard create, update, and delete lifecycle operations for a duty station record:

  • CREATE_DUTY_STATION — Inserts a new duty station record into the GHR duty station entity. This procedure is the supported entry point for defining a new duty station and for applying the associated validation and derivation logic required before the record can be used by assignment and payroll processing.
  • UPDATE_DUTY_STATION — Modifies an existing duty station record. It is used to maintain current descriptive and effective-dated attributes of a duty station already known to the system, preserving the integrity of historical data.
  • DELETE_DUTY_STATION — Removes a duty station record, subject to the referential and business-rule checks enforced by the API.

Each procedure is a documented public entry point. Internally, the package body delegates to the supporting business logic units (GHR_DUT_INS, GHR_DUT_UPD, GHR_DUT_DEL) and to well-known HRMS infrastructure packages, including HR_API for error handling and API plumbing and HR_UTILITY for common HRMS utility operations.

Tables Accessed

The package body operates against the GHR_DUTY_STATIONS_F table, referenced through the APPS synonym. This is the base (or "_F" formatted) table that physically stores duty station definitions. The CREATE_DUTY_STATION procedure writes new rows to this table; UPDATE_DUTY_STATION modifies existing rows; and DELETE_DUTY_STATION removes rows. All access is performed indirectly through the internal business logic units, which apply the appropriate validation and multi-org / security predicates before committing changes. Because the table is "_F" (formatted), it is the current, supported storage location for duty station data in the GHR model.

Usage Notes

This API is typically invoked from Oracle EBS forms, concurrent programs, and custom PL/SQL code that need to create, change, or remove duty stations without bypassing GHR validation. In the standard product, the Duty Stations maintenance form calls this API rather than issuing direct DML against GHR_DUTY_STATIONS_F. Customers extending GHR functionality—for example, loading duty station data from an external system or synchronizing records across business groups—should call the documented CREATE, UPDATE, and DELETE procedures instead of writing directly to the table, thereby preserving data integrity and forward compatibility across 12.1.1 and 12.2.2.

The dependency metadata confirms that APPS.GHR_DUTY_STATION_API is not referenced by any other database object; it is a leaf-level public API, consumable by external callers but not depended upon internally. Any custom code migrating duty station data should therefore treat these three procedures as the only supported interface and avoid referencing the internal helper packages (GHR_DUT_INS, GHR_DUT_UPD, GHR_DUT_DEL, and the GHR_DUTY_STATION_BK1 through BK3 units), which are implementation details.