Search Results wip_logger




Overview
Explore in AI Chat

Overview

APPS.WIP_LOGGER is a diagnostic support package body in the Oracle E-Business Suite Work in Process (WIP) module. Its business function is to provide a centralized, structured logging facility for WIP run-time processing, capturing execution traces, informational messages, warnings, and error conditions generated during discrete manufacturing transactions. Rather than allowing individual WIP packages to write ad hoc diagnostics, WIP_LOGGER consolidates logging behavior so that debug output is consistent, controllable, and traceable across the many WIP APIs and concurrent programs that execute against the same application schema.

The package is classified as OTHER in the ETRM documentation, meaning it is an internal infrastructure utility rather than a user-invocable business API. It is deployed in the APPS schema and is marked VALID in Oracle EBS 12.1.1 and 12.2.2. Its importance in the technical architecture is underscored by the fact that it is referenced by 61 other database objects within the WIP family, making it a shared cornerstone of WIP diagnostic behavior.

The presence of the user search term wip_logging_session_s is explained by the package's tight coupling to that sequence, which supplies session identifiers for each logging run.

Key Procedures and Functions

The documented package exposes four procedures/functions:

  • LOG: The core logging routine. It writes a single log entry at a caller-specified severity or message level, associating the entry with the current logging session and the calling program context. This is the procedure most frequently invoked by other WIP packages to record diagnostic detail.
  • ENTRYPOINT: Marks the beginning of a logging session. It establishes session context, so that subsequent LOG calls are grouped under a single identifiable execution and can be correlated across nested procedure calls.
  • EXITPOINT: Marks the termination of a logging session. It closes out the session opened by ENTRYPOINT, typically after flushing or finalizing the accumulated log records.
  • CLEANUP: Performs housekeeping on logging data, removing or resetting session artifacts so that stale log records do not accumulate indefinitely.

Parameter lists are not documented in the available ETRM metadata and should be confirmed by inspecting the package specification in the target environment.

Tables Accessed

WIP_LOGGER references a small, focused set of database objects through APPS synonyms:

  • WIP_LOGGING_SESSION_S: The sequence that generates unique session identifiers. Each ENTRYPOINT invocation consumes a value from this sequence to stamp the log records for that run.
  • DUAL: Used for simple single-row SQL operations, typically to fetch the next session number or to evaluate expressions without referencing an application table.
  • PLITBLM: A PL/SQL index-by table type used for in-memory buffering of log messages prior to persistence or display.

Usage Notes

WIP_LOGGER is invoked programmatically rather than from a user-facing form or concurrent program parameter screen. It is called from within other WIP PL/SQL packages, including transactional APIs and their supporting utilities, which is consistent with the 61 inbound references documented in the ETRM. In practice, a calling program wraps its logic with ENTRYPOINT and EXITPOINT to bracket a logging session, issues LOG calls at key processing milestones, and relies on CLEANUP to remove or age session data. The package also depends on FND_API, FND_LOG, FND_MSG_PUB, and WIP_CONSTANTS, indicating that it integrates with the standard EBS logging and message frameworks and uses WIP-defined constants for log levels or message tokens. Custom code should treat WIP_LOGGER as an internal dependency and avoid direct modification, since changes may affect the many dependent WIP objects.