Search Results check_configuration

Overview

The APPS.WMS_WCS_DIAGNOSTICS package is a diagnostic and configuration-verification utility within the Oracle Warehouse Management System (WMS) module of Oracle E-Business Suite. Its name — Warehouse Control System Diagnostics — reflects its primary role: providing warehouse administrators and implementation consultants with a structured set of health checks that validate the integrity and readiness of the WMS integration environment, particularly the communication path between Oracle WMS and the material-handling equipment controlled through the Warehouse Control System (WCS). The package provides a single entry point, RUN, that orchestrates a series of individually callable diagnostic routines. These routines inspect configuration data, verify that required integration objects and privileges exist, confirm that scheduled background jobs are present, and allow controlled test task injection. The package is documented under API classification OTHER, indicating it is a technical/support utility rather than a public business API. Its header revision (120.0, dated 2005) confirms it is a long-standing component carried forward through the 12.1.1 and 12.2.2 releases without signature changes.

Key Procedures and Functions

The package exposes the following documented procedures:

• RUN — The master driver procedure. It sequentially invokes the individual diagnostic checks and produces consolidated output, typically via DBMS_OUTPUT, giving the operator a single-command health report.
• CHECK_WMS_INTEGRATION — Validates that the WMS-to-WCS integration is correctly configured and operational, verifying the components that carry tasks and directives between the two systems.
• CHECK_CONFIGURATION — The routine directly relevant to the user's search. It examines WMS carousel and equipment configuration records to confirm that required setup data is present and internally consistent. This is the procedure typically executed first when troubleshooting carousel behavior or WCS task flow.
• CHECK_JOBS — Confirms that expected concurrent/background jobs (interrogated through ALL_JOBS) are scheduled and active, since the WCS interface depends on recurring job execution to poll and dispatch tasks.
• UPDATE_HASH_VALUE — Recomputes and stores a hash value used to detect drift in configuration or source definitions, supporting change-detection and integrity checks.
• EXPORT_CONFIGURATION — Documented as a commented-out prototype in the header; it was intended to export configuration by device type and zone. Treated here as a documented (though not active) signature and should not be relied upon in its current form.
• TEST_TASK — Injects a synthetic task into the directive queue to exercise the end-to-end task flow from WMS to WCS. Documented defaults include directive 'GO', task type 10, quantity 123, business event 10, and LPN 'TestLPN', intended for non-production validation.

Tables Accessed

The package operates against a focused set of tables and resources:

• WMS_CAROUSEL_CONFIGURATION — Declared as a %ROWTYPE cursor variable at package level; supplies the configuration data inspected by CHECK_CONFIGURATION.
• WMS_CAROUSEL_DIRECTIVE_QUEUE — The queue into which TEST_TASK writes synthetic directives and from which task processing is verified.
• ALL_JOBS — Queried by CHECK_JOBS to confirm scheduled job existence and status.
• USER_SOURCE — Used to inspect stored source, supporting the hash/integrity verification logic.
• DBMS_OUTPUT and DBMS_PIPE — PL/SQL-supplied infrastructure for diagnostic reporting and, in the case of DBMS_PIPE, inter-process signalling associated with the WCS interface.

Usage Notes

This package is a support and troubleshooting tool. It is not referenced by any other package (referenced-by count: 0), so it is invoked directly rather than through an API chain. Typical invocation paths are: from SQL*Plus or another PL/SQL client by a DBA or implementation consultant calling WMS_WCS_DIAGNOSTICS.RUN with server output enabled; from custom diagnostic scripts during implementation or post-patch verification; and manually during incident resolution to isolate configuration, job, or integration faults. Because TEST_TASK inserts directives into the WCS queue, its use should be confined to test or controlled environments. UPDATE_HASH_VALUE should be executed only when configuration changes are intentional and the operator wishes to rebaseline the stored hash. The EXPORT_CONFIGURATION routine is commented out in the shipped source and must not be assumed available in 12.1.1 or 12.2.2.