Search Results is_cyc_count_enabled

Overview

The APPS.WMS_OPP_CYC_COUNT package belongs to the Oracle Warehouse Management System (WMS) module and supports opportunistic cycle counting operations within Oracle E-Business Suite 12.1.1 and 12.2.2. Opportunistic cycle counting allows warehouse operators to perform ad hoc or unscheduled inventory counts at the moment a discrepancy, damage, or unexpected condition is observed during normal warehouse activity, rather than waiting for a scheduled cycle count. This package encapsulates the business logic that validates whether cycle counting is enabled for a given organization, subinventory, locator, and item, and then records count entries and summary results into the underlying inventory and WMS tables.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer. The header comment indicates it is a non-shipped (noship) internal object with a last modification date of 2010, consistent with its presence across the 12.1.1 and 12.2.2 releases. It is classified as an OTHER API in the ETRM documentation and is not referenced by any other package, indicating it functions primarily as a boundary API invoked directly by WMS mobile pages or concurrent processes rather than as a shared library.

Key Procedures and Functions

Three documented program units comprise the public interface:

• IS_CYC_COUNT_ENABLED — A function returning a NUMBER. It accepts organization, subinventory, locator, and inventory item identifiers and determines whether opportunistic cycle counting is permitted for that combination. Callers use the return value to gate entry into the counting flow, ensuring counts are only captured where the warehouse configuration allows them.
• PROCESS_ENTRY — The primary procedure for recording a single opportunistic count. Its parameter list is extensive, covering cycle count header, organization, subinventory, locator, parent LPN, item, revision, lot, serial number range, system quantity, counted quantity and UOM, unscheduled count flag, user, cost group, and secondary UOM and quantity. This breadth reflects the need to capture counts at the most granular level, including serial and lot controlled items and dual-unit-of-measure scenarios commonly encountered in 12.2.2.
• PROCESS_SUMMARY — A procedure that consolidates the outcome of opportunistic count entries for a cycle count header, organization, subinventory, locator, parent LPN, and item. It records summary-level results and the unscheduled count indicator, associating them with the performing user.

Tables Accessed

The package reads and writes through APPS synonyms across inventory and WMS schemas:

• MTL_CYCLE_COUNT_ENTRIES and MTL_CYCLE_COUNT_ITEMS — Core cycle count tables receiving the individual entry and item-level records produced by PROCESS_ENTRY and PROCESS_SUMMARY.
• MTL_ONHAND_QUANTITIES_DETAIL — Supplies the system on-hand quantity for comparison against the counted quantity.
• MTL_SERIAL_NUMBERS and MTL_SERIAL_NUMBERS_TEMP — Support serial-controlled item counting and staging of serial number ranges.
• MTL_TRANSACTION_LOTS_TEMP and MTL_SYSTEM_ITEMS — Provide lot and item attribute validation during entry.
• MTL_MATERIAL_TRANSACTIONS_TEMP — Holds pending transaction records generated as a consequence of count discrepancies.
• MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES — Supply organization and subinventory configuration.
• WMS_LICENSE_PLATE_NUMBERS, WMS_LPN_CONTENTS, and WMS_DISPATCHED_TASKS — Resolve LPN hierarchy and confirm that the count is not in conflict with an in-flight warehouse task.

Usage Notes

Because the package is not referenced by other PL/SQL units, invocation occurs from outside the database library layer. Typical callers include WMS mobile radio-frequency (RF) pages and Java-based WMS servlets that submit count entries during receiving, picking, or put-away transactions. Custom code and extension points may call IS_CYC_COUNT_ENABLED as a guard before invoking PROCESS_ENTRY, and subsequently PROCESS_SUMMARY to finalize a count group. All procedures require a valid p_user_id, and the secondary UOM parameters are optional and defaulted, preserving backward compatibility with 12.1.1 environments where dual UOM capture was less prevalent. Developers should not treat this as a formally published public API; it is an internal WMS object subject to change between patches.