Search Results ghr_nfc_notif_seq_s

Overview

APPS.GHR_WF is a PL/SQL package body in the Oracle E-Business Suite Applications schema, classified under the ETRM registry as an OTHER API and holding VALID status in both 12.1.1 and 12.2.2 environments. The package provides the workflow integration layer for the Oracle Advanced Benefits / Benefits Extracts framework, specifically the GHR (HRMS) product family. Its central business function is to initiate Oracle Workflow notifications against benefit-extract processing results, allowing a customer-defined extract run to raise a notification to a designated user or role — typically for the purposes of advising an administrator that an extract completed, failed, or produced output requiring review. The package also performs user-existence validation before a notification is dispatched, preventing workflow errors caused by invalid or unresolvable recipients. Because it is a workflow-facing utility, GHR_WF depends on Oracle Workflow's engine and directory objects rather than on any user interface or form of its own.

Key Procedures and Functions

• INITIATE_NOTIFICATION — The primary entry point of the package. It assembles and launches an Oracle Workflow notification using the Workflow engine, resolving the recipient and populating notification content from the benefits-extract context. It is the routine invoked when an external caller, such as a benefits extract concurrent program or a supporting package, determines that a notification event must be raised.
• CHECK_USER_EXIST — A validation routine that confirms whether the intended notification recipient exists and is resolvable within the Workflow directory (WF_ROLES / WF_USER_ROLES) before the notification is submitted. It is used defensively so that INITIATE_NOTIFICATION does not fail or generate an orphaned notification when a recipient name is misspelled, inactive, or absent from the directory.

Two documented procedures are exposed in total. Parameter lists are not documented in the ETRM metadata and are therefore intentionally not reproduced here.

Tables Accessed

The package reads the benefits-extract tables BEN_EXT_DFN (extract definition), BEN_EXT_RCD_IN_FILE (records staged in the extract file), BEN_EXT_RSLT (extract run results), and BEN_EXT_RSLT_DTL (result detail lines) to build the notification payload and to identify which extract run triggered the event. GHR_NFC_NOTIF_SEQ_S — the object the user searched for — is the sequence referenced by GHR_WF, and it supplies the surrogate key used when a notification record is generated. DUAL is used for single-row scalar evaluations. On the Workflow side, the package references WF_ENGINE to initiate the notification, and WF_ROLES plus WF_USER_ROLES to resolve and verify the recipient identity. BEN_EXT_THREAD also appears in the dependency list, reflecting the threaded extract-processing model that contextualizes the notification.

Usage Notes

GHR_WF is not referenced by any other database object, so it is effectively a top-level utility reached from outside the PL/SQL dependency graph — most commonly from the Oracle Advanced Benefits extract concurrent programs, from Workflow notification activities configured against the extract, or from customer-written code that wishes to signal an extract outcome. Because it writes no application data beyond the notification and sequence artifacts, invocation is safe during normal extract processing. Integrators extending benefits extracts should call INITIATE_NOTIFICATION rather than inserting into Workflow tables directly, and should treat CHECK_USER_EXIST as the prerequisite gate for any recipient supplied from external or configuration-driven input. The package's VALID status confirms it is compiled and usable in 12.1.1 and 12.2.2, with no ETRM-documented signature changes between those releases.