Search Results flm_ekanban_logger

Overview

FLM_EKANBAN_LOGGER is an APPS-owned PL/SQL package within the Oracle E-Business Suite Flow Manufacturing (FLM) module, specifically associated with the eKanban feature set. Its primary business function is to provide a centralized logging utility for eKanban-related processing. Rather than embedding diagnostic and trace statements directly within transactional logic, the eKanban components delegate logging responsibilities to this package, which standardizes how runtime information, errors, and trace messages are captured during execution.

The package is classified as OTHER within the ETRM repository, indicating that it is not a formal public API intended for external integration, but rather an internal support utility. It is documented as VALID in release 12.2.2 and is present in both 12.1.1 and 12.2.2 environments. Its role is consistent with the broader logging framework used across Oracle Manufacturing, where packages such as this wrap FND_LOG calls to produce consistent, level-controlled diagnostics.

Key Procedures and Functions

The package exposes five documented procedures and functions:

• LOG — The core logging routine. It writes a message to the logging destination, typically through the FND_LOG infrastructure, applying the appropriate severity or level. This is the procedure most frequently called by other eKanban programs.
• ENTRYPOINT — Marks the beginning of a logged execution block. It records entry into a routine, capturing context such as the calling program and any relevant identifiers so that subsequent log entries can be correlated.
• ENTRYPOINTNOPARAMS — A variant of ENTRYPOINT intended for routines that accept no parameters. It provides entry-point logging without requiring callers to supply contextual arguments.
• EXITPOINT — Records the completion of a logged execution block. Used symmetrically with ENTRYPOINT, it captures exit status and helps bound the duration and outcome of the logged operation.
• CLEANUP — Releases resources or resets logging state accumulated during a session or processing run, ensuring that subsequent invocations begin from a clean state.

No parameter lists are documented in the ETRM metadata; the descriptions above reflect the evident purpose of each routine based on its name and the package's logging role.

Tables Accessed

The package references the following tables through APPS synonyms:

• WIP_LOGGING_SESSION_S — The logging session sequence, used to generate or track session identifiers for log entries. This ties eKanban log records to a discrete logging session.
• DUAL — The standard Oracle single-row utility table, typically used for simple expression evaluation or sequence value retrieval within PL/SQL.
• PLITBLM — A PL/SQL internal table structure referenced in the package metadata, used in the context of collection or bulk processing support.

The package also depends on APPS.FND_LOG and the SYS.STANDARD package. The FND_LOG dependency confirms that log messages are ultimately routed through the Oracle Application Object Library logging framework.

Usage Notes

FLM_EKANBAN_LOGGER is not intended for direct invocation by end users or external applications. It is invoked internally by other eKanban components. The ETRM metadata documents that it is referenced by FLM_KANBAN_CONFIG_PARAMS and by itself (recursive or internal references). This indicates that configuration parameter processing for Kanban relies on the logger for diagnostics.

Typical invocation occurs during eKanban setup, configuration validation, and runtime processing, where ENTRYPOINT and EXITPOINT bracket logical operations and LOG records intermediate state. The CLEANUP routine is called at the conclusion of processing to release logging state. Because the package depends on FND_LOG, output visibility is governed by FND logging profile options, meaning administrators control verbosity through standard EBS logging configuration rather than through package-level settings. Custom code should not call these routines directly unless extending the eKanban logging model.