Search Results fetch_noa_spec_extra_info




Overview
Explore in AI Chat

Overview

APPS.GHR_NON_SF52_EXTRA_INFO is an Oracle E-Business Suite PL/SQL package that supports the Nature of Action (NOA) processing framework within Oracle Human Resources. Its central business function is to populate, refresh, and maintain NOA-specific extra information held against Human Resources personnel action requests. The package is declared with AUTHID CURRENT_USER, meaning its database objects are resolved using the privileges of the invoking schema rather than the definer, a characteristic common to Oracle EBS APIs that are executed from multiple entry points under the APPS schema.

The source header indicates the package is internal-use-only and carries a revision from the 12.1/12.2 development stream (ghddfdef.pkh, revision 120.2.12020000.2). The behaviour is identical across Oracle EBS 12.1.1 and 12.2.2, as no online patching-specific logic is present in the documented body. The package's primary responsibility is to keep the extra information associated with an HR personnel action request synchronized with the first and second Nature of Action, the affected person, assignment, position, and the request effective date. It also determines whether previously stored extra information has become irrelevant and must be removed. The documented API classification is OTHER, denoting a supporting utility rather than a standalone public interface.

Key Procedures and Functions

The package exposes ten documented procedures and functions:

  • POPULATE_NOA_SPEC_EXTRA_INFO — The primary driver procedure. It populates or updates the extra information table based on the first NOA, second NOA, position, person, and effective date, and determines whether existing extra information should be deleted when it is no longer relevant to the current request. It accepts a refresh flag that defaults to 'Y'.
  • FETCH_NOA_SPEC_EXTRA_INFO — Retrieves NOA-specific extra information for a given NOA code. This is the routine referenced by the search term fetch_noa_spec_extra_info.
  • FETCH_GENERIC_EXTRA_INFO — Retrieves extra information that is not tied to a specific Nature of Action.
  • GET_INFORMATION_TYPE — Resolves the information type applicable to the extra information being processed.
  • DETERMINE_OPERATION — Establishes which operation (insert, update, or delete) is required for the extra information records under consideration.
  • GENERIC_POPULATE_EXTRA_INFO — Performs the equivalent of the NOA-specific populate routine for generic (non-NOA-specific) extra information.
  • SET_EI — Sets an individual extra information value.
  • DUAL_EXTRA_INFO_REFRESH — Handles refresh behaviour for the dual (first and second NOA) extra information scenario.
  • SET_DUAL_EI — Sets extra information values specifically for the dual NOA case.
  • DELETE_EXTRA_INFO_REC — Removes extra information records that are no longer valid for the request.

Tables Accessed

Access occurs through APPS synonyms. The core HR tables are GHR_PA_REQUESTS (the personnel action request header), GHR_NATURE_OF_ACTIONS (NOA definitions), GHR_PA_REQUEST_EXTRA_INFO and its shadow table GHR_PA_REQUEST_EI_SHADOW (the extra information store), and GHR_PA_REQUEST_INFO_TYPES (which information types apply to a request). Context and configuration data are drawn from GHR_FAMILIES, GHR_NOA_FAMILIES, and GHR_PAY_PLANS. Payroll element structures are read from PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F, and PAY_USER_TABLES, allowing NOA extra information to be derived from element entry values. FND_APPLICATION and FND_RESPONSIBILITY supply application and responsibility context. Person, assignment, and position data are referenced through standard HR tables such as PER_PEOPLE_F, PER_ASSIGNMENTS_F, and PER_POSITIONS.

Usage Notes

GHR_NON_SF52_EXTRA_INFO is an internal supporting package and is not intended as a public API. It is invoked by the HR forms and business logic that create and maintain personnel action requests, particularly where NOAs require additional descriptive fields beyond the standard request attributes. Five other packages within the ETRM documentation reference this package, indicating it is called from the higher-level NOA and extra information processing layers rather than directly by end users.

Typical invocation occurs when a personnel action request is created, updated, or refreshed, at which point POPULATE_NOA_SPEC_EXTRA_INFO is called to align stored extra information with the current first and second NOA and effective date. Customizations should avoid calling the package directly unless absolutely necessary, because its behaviour depends on the internal state of the request and the configuration of information types. Where custom code must interact with NOA extra information, the documented procedures should be used in the same sequence and with the same effective-date and refresh-flag conventions as the standard HR flows.