Search Results g_add_errors_to_fnd_stack

Overview

FLM_EKB_CUSTOM_HEALTH is an Oracle Application Object Library (APPS) package body delivered under the ETRM (Enterprise Resource Transaction Model) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to provide custom health-check logic for pull sequences managed within the ETRM environment. The package encapsulates a single public procedure, HEALTH_FOR_PS, which is designed to return status indicators for a given pull sequence, expressed through good-health and bad-health counters returned to the caller.

The package header declares a small set of package-level globals that are initialized at load time from FND_GLOBAL: G_REQUEST_ID, G_PROGAM_APPLICATION_ID, G_PROGAM_ID, G_USER_NAME, G_USER_ID, and G_LOGIN_ID. These values give the package access to the current concurrent request context, program identity, and the authenticated user. Additional globals such as G_CURRENT_USER_ID, G_CURRENT_LOGIN_ID, G_ADD_ERRORS_TO_FND_STACK, G_APPLICATION_CONTEXT, and the date-format constant G_DATE_FORMAT ('SYYYY-MM-DD HH24:MI:SS') support runtime context tracking and standardized timestamp formatting. The source header identifies the file as FLMKBCHB.pls, version 120.1.12020000.1, dated 2012/07/13, and marked "noship," indicating it is a non-shipped or custom extension component rather than part of the base certified EBS code line.

Key Procedures and Functions

The package exposes exactly one documented procedure:

• HEALTH_FOR_PS — Accepts a pull sequence identifier as input and returns a return status, an error code, and two numeric health counters (good health and bad health). Its role is to evaluate the health of a specific pull sequence and report the outcome through these OUT parameters. In the documented source, the executable body is effectively a stub: the implementation contains commented-out DBMS_OUTPUT calls and a NULL statement, meaning the procedure currently performs no substantive evaluation logic in this version.

Despite the minimal body, the procedure's signature establishes the interface expected by callers that wish to assess pull sequence health and receive structured status information.

Tables Accessed

The documented metadata identifies one table referenced through an APPS synonym:

• FND_USER — The Oracle EBS foundation table of application users. The package declares G_USER_NAME as FND_USER.USER_NAME%TYPE, anchoring the global variable to the column definition. This reference is used to capture and validate the current user's name from FND_GLOBAL.USER_NAME at package initialization.

No other base tables, interface tables, or ETRM transaction tables are documented as referenced by this package. Any pull sequence data manipulation would occur outside the currently documented implementation, given the stub body.

Usage Notes

Because HEALTH_FOR_PS is a PUBLIC-style procedure within an APPS package body, it is intended to be invoked from PL/SQL callers rather than through a dedicated form or concurrent program in the documented metadata. Typical invocation patterns include:

• Custom concurrent programs or request sets that require a health indicator for ETRM pull sequences.
• Custom PL/SQL packages or database triggers that need to evaluate and branch on pull sequence health.
• Diagnostic or monitoring routines where good-health and bad-health counts are aggregated for reporting.

The presence of G_REQUEST_ID, G_PROGAM_ID, and related FND_GLOBAL constants suggests the package is frequently run inside a concurrent manager context, where request-level attribution and program identity matter for error logging. The G_ADD_ERRORS_TO_FND_STACK global is associated with the common EBS convention of conditionally pushing error messages onto the FND message stack (via FND_MESSAGE or FND_STACK). This is the identifier most relevant to the user's search term "g_add_errors_to_fnd_stack," which appears as a declared global governing whether errors are propagated to the FND stack. The package references no other documented packages, so dependency impact is limited. The "noship" flag and custom prefix indicate the object is customer-specific and may be overwritten or absent in a base installation; deployments should verify its presence before relying on HEALTH_FOR_PS.