Search Results emp_disability_update




Overview
Explore in AI Chat

Overview

APPS.PER_IN_DISABILITY_LEG_HOOK is a legislative hook package within the Oracle E-Business Suite Human Resources (PER) product family. Its name follows the standard Oracle EBS legislative hook naming convention: the "PER_IN" prefix identifies the Oracle HRMS (People) module and the legislative context (India), while "DISABILITY_LEG_HOOK" indicates that the package is intended to encapsulate localization-specific (legislative) business rules governing the recording and maintenance of employee disability information. In Oracle EBS 12.1.1 and 12.2.2, such hook packages provide a formally defined extension point where country-specific statutory requirements — for example, the categories, statuses, and degree-of-disability values mandated by local law — can be enforced or augmented without modifying the core HRMS disability schema or the standard disability maintenance forms.

The package serves as a programmatic boundary between the generic Oracle HRMS disability data model and the legislative rules that apply when disability records are entered or changed. The header comment identifies it as a shell ("noship") hook dating from 2005, indicating that it defines a stable interface that customer or Oracle localization code may implement.

Key Procedures and Functions

The package exposes two documented procedures, both defined in the package specification and therefore callable by external code:

  • EMP_DISABILITY_CREATE — Handles the create-time business logic for an employee disability record. It accepts the effective date of the operation, the person identifier, the disability category, status, degree, and a descriptive information attribute. The procedure is the designated entry point for legislative validation or derivation when a new disability row is created for a person.
  • EMP_DISABILITY_UPDATE — Handles the corresponding update-time logic. Instead of a person identifier, it receives the disability identifier (p_disability_id), which uniquely identifies the existing disability record being modified, together with the same category, status, degree, and information parameters.

The split between create and update reflects the two distinct DML events in the disability lifecycle. The specification deliberately omits a delete procedure, so removal of disability records is not routed through this hook.

Tables Accessed

The package is documented as referencing PER_DISABILITIES_F via an APPS synonym. This is the core Oracle HRMS disability table, an effective-dated ("_F" denotes the date-tracked table) repository of employee disability information keyed by person. The hook reads and/or writes this table to persist or validate the category, status, degree, and informational attributes passed into the two procedures. Because PER_DISABILITIES_F is date-effective, the p_effective_date parameter is essential for correct row resolution and for maintaining the integrity of the date-tracked history.

Usage Notes

Legislative hook packages of this type are normally invoked from the standard Oracle HRMS disability maintenance user interface — the "Disability" tab or window within the Person form — and from any other code path that creates or modifies rows in PER_DISABILITIES_F. Rather than being called directly by end users, the package is invoked by the framework at the appropriate point in the create or update transaction so that legislative rules are applied consistently regardless of the entry point.

The package is also referenced by two other packages in the ETRM inventory, confirming that it participates in a wider call chain within the HRMS disability processing logic. Customers extending disability handling for India should treat the documented parameter signatures as the supported contract and implement additional validation or derivation inside these procedures, avoiding direct modification of the standard form or core tables. Because both procedures are defined in the package specification, custom code may also invoke them explicitly when processing disability data through interfaces, conversions, or batch loads.