Search Results get_config_parameter




Overview
Explore in AI Chat

Overview

WMS_WCS_DIAGNOSTICS is a diagnostics and configuration-validation utility within the Oracle E-Business Suite Warehouse Management System (WMS) module. It operates in the context of the Warehouse Control System (WCS) carousel integration, providing the tooling required to inspect, verify, and tune the configuration records that drive carousel device communication and directive processing. The package is owned by APPS and is classified as OTHER, indicating that it is a support-level internal utility rather than a public application programming interface. Its primary purpose is to enable implementers and support personnel to rapidly establish whether the integration between EBS and a warehouse carousel controller has been configured correctly, whether the required database jobs are scheduled and running, and whether configuration parameters hold the expected values.

The package body follows a diagnostic-runner design. A single entry point, RUN, orchestrates a sequence of targeted checks, each encapsulated in its own procedure. Output is emitted through DBMS_OUTPUT and, in parallel, persisted through the private LOG procedure, which writes autonomously to the WMS carousel logging infrastructure. The autonomous transaction pragma on LOG ensures diagnostic records survive regardless of the outcome of the calling session.

Key Procedures and Functions

  • RUN — The main entry point. It enables a large DBMS_OUTPUT buffer (200,000 bytes) and invokes each diagnostic check in turn. In the shipped source the object and privilege checks are commented out, leaving the WMS integration, configuration, and job checks active.
  • CHECK_WMS_INTEGRATION — Verifies that the WMS-side integration objects and linkages required by the carousel interface are present and correctly installed.
  • CHECK_CONFIGURATION — Validates the carousel configuration records, confirming that required parameters exist, are active, and carry valid values.
  • CHECK_JOBS — Inspects the scheduled concurrent jobs that drive carousel processing and reports on their existence and state.
  • UPDATE_HASH_VALUE — Maintains the stored hash value associated with carousel configuration. This is the routine most closely related to the search term "get_hash_value", which is the underlying database function used to compute a numeric hash of configuration content for change detection and cache-invalidation purposes.
  • EXPORT_CONFIGURATION — Emits the current carousel configuration in a portable form, supporting comparison between environments or preservation before changes.
  • TEST_TASK — Exercises an individual carousel task end to end, allowing an operator to confirm that directive dispatch and acknowledgment behave as expected.

A private helper, GET_CONFIG_PARAMETER, reads a single configuration value by name and optional sequence ID, returning NULL when no active row is found.

Tables Accessed

The package references WMS_CAROUSEL_CONFIGURATION, the master repository of carousel parameters from which configuration values are read and hash values updated. It also reads WMS_CAROUSEL_DIRECTIVE_QUEUE, the work queue of carousel directives examined during task testing and integration validation. Job diagnostics query ALL_JOBS to determine whether the required scheduled programs exist and are enabled. DBMS_OUTPUT supplies the session-level reporting channel, DBMS_PIPE supports inter-process diagnostic signaling, and USER_SOURCE is used to introspect package source when validating installed code versions.

Usage Notes

WMS_WCS_DIAGNOSTICS is normally invoked manually, either from a SQL*Plus session with SERVEROUTPUT enabled or through a diagnostic concurrent program, after the carousel integration has been configured or when directives fail to process. Because DBMS_OUTPUT is enabled internally, callers need only ensure the output is displayed to capture the full report. The package is not referenced by any other package, confirming its role as a standalone support tool. Its use is recommended during implementation validation, after applying patches that affect WMS carousel objects, and as a first-line triage step when carousel communication appears stalled.