Search Results set_debug_flag

Overview

APPS.GMD_EDR_STANDARD is a Process Manufacturing (OPM / "GMD") package body that provides a standardized entry point for raising Oracle Workflow business events from the EDR (Enterprise Data Repository / event-driven rules) area of the application. Its principal purpose, as evidenced by the package header comment, is to encapsulate the call to the Workflow event API so that OPM and EDR components do not need to invoke WF_EVENT.RAISE directly and can instead pass a consistent set of named parameters. The body is documented under ETRM with an API classification of OTHER, and it is referenced by one other package, confirming its role as a shared utility rather than a standalone business process.

The package also carries a private diagnostic helper, set_debug_flag, which is relevant to the search term provided. This function is declared as a forward declaration and then implemented within the body. It tests the session's current runtime logging level against FND_LOG.LEVEL_PROCEDURE and returns a single-character flag, documented internally as 'Y' when the runtime level is at or above procedure level and 'N' otherwise. Because it is declared in the package body only, set_debug_flag is not part of the public API; it is a private package-level construct used to control diagnostic behavior inside GMD_EDR_STANDARD, and it demonstrates the standard Oracle EBS practice of gating debug output through the FND logging framework rather than through a custom profile option.

Key Procedures and Functions

• RAISE_EVENT — The single documented public procedure. It is the package's event-emission routine, responsible for invoking the Oracle Workflow raise event operation. As shown in the source synopsis, it is designed to accept an event name, an event key, and a sequence of paired parameter name/value arguments (the body defines slots for up to ten such pairs), allowing a caller to pass arbitrary event context to subscribers. The procedure internally declares tables and record types drawn from EDR_ERES_EVENT_PUB (erecord_id_tbl_type and eres_event_rec_type) together with standard message count, message data, and return status variables, indicating that it assembles the event payload and delegates the actual raise to the EDR/ERES event publication layer.
• set_debug_flag (private) — A package-body-only function returning VARCHAR2. It inspects the FND logging runtime level and returns a debug indicator used internally by the package. It is not exposed for external invocation.

Tables Accessed

The ETRM metadata lists no directly referenced tables via APPS synonyms for this package body. This is consistent with its design: GMD_EDR_STANDARD operates primarily against PL/SQL APIs, specifically the Workflow event API and the EDR event publication package EDR_ERES_EVENT_PUB. Any persistent storage of event subscriptions, event data, or runtime logging configuration is handled by those underlying components (for example, the FND logging tables behind FND_LOG) rather than by direct DML issued from this package. Implementers should therefore not expect to find business data manipulation here; the package is a thin orchestration layer.

Usage Notes

GMD_EDR_STANDARD is invoked programmatically. Typical callers are other OPM/EDR PL/SQL packages, workflow-enabled business logic, or custom extensions that need to signal a business event — for example, an operation status change — using the documented raise_event('oracle.apps.gmd.operation.sts', ...) pattern. It is not associated with a concurrent program or a form-level trigger in the metadata. Because the event parameter interface is positional and limited to ten name/value pairs, custom code should call the procedure with exactly the parameters required by the event definition and rely on Workflow subscriptions to consume the payload. The presence of the private set_debug_flag function means diagnostic tracing for this package is governed by the standard FND log runtime level, which administrators can raise through the usual Logging setup when troubleshooting event delivery in EBS 12.1.1 or 12.2.2.