Search Results mtl_cc_schedule_requests




Overview
Explore in AI Chat

Overview

The MTL_CC_SCHEDULE_REQUESTS table is a core data object within the Oracle E-Business Suite (EBS) Inventory (INV) module, specifically for versions 12.1.1 and 12.2.2. It serves as the transactional repository for cycle count schedule requests. In the context of inventory management, a cycle count is a periodic audit of a subset of inventory items to ensure record accuracy. This table defines and stores the individual requests generated by the system's scheduling engine, which are based on predefined cycle count headers and their associated criteria. Its primary role is to act as the staging area for pending count entries, linking high-level schedule definitions to the specific items and locations that require physical counting on a given date.

Key Information Stored

The table's structure is designed to capture the essential identifiers that link a schedule request to its parent definitions and target inventory. The primary key is CYCLE_COUNT_SCHEDULE_ID, which uniquely identifies each request record. As indicated by the foreign key relationships, two other columns are critically important: CYCLE_COUNT_HEADER_ID, which links the request to its controlling schedule in MTL_CYCLE_COUNT_HEADERS, and INVENTORY_ITEM_ID, which identifies the specific item to be counted. While the provided metadata does not list all columns, the table typically includes additional attributes such as the organization ID, the specific subinventory and locator for the count, the scheduled count date, and status flags to track the request's progression from generation to execution or cancellation.

Common Use Cases and Queries

The primary use case is the generation and management of pending cycle counts. A common operational report involves listing all open schedule requests for a warehouse team. A typical query would join this table to item and location tables to produce a pick list for counters. Troubleshooting often involves checking for requests that were generated but never acted upon. Sample SQL to find scheduled requests for a specific cycle count header would be:

  • SELECT schedule_req.cycle_count_schedule_id, schedule_req.inventory_item_id, mic.segment1 item_code FROM inv.mtl_cc_schedule_requests schedule_req, inv.mtl_system_items_b mic WHERE schedule_req.cycle_count_header_id = &header_id AND schedule_req.inventory_item_id = mic.inventory_item_id AND schedule_req.organization_id = mic.organization_id ORDER BY schedule_req.cycle_count_schedule_id;

This table is also central to the "Generate Cycle Count Schedules" concurrent request, which populates it, and subsequent processes that consume these requests to create actual count entries (MTL_CYCLE_COUNT_ENTRIES).

Related Objects

MTL_CC_SCHEDULE_REQUESTS is a central hub within the cycle count schema. Its key relationships, as documented, are:

  • MTL_CYCLE_COUNT_HEADERS: The parent table defining the overall schedule policy (frequency, criteria, adjustments). The foreign key on CYCLE_COUNT_HEADER_ID enforces this relationship.
  • MTL_CYCLE_COUNT_ITEMS: Defines which specific items are included in a cycle count. The foreign key relationship uses both CYCLE_COUNT_HEADER_ID and INVENTORY_ITEM_ID.
  • MTL_CC_SCHED_COUNT_XREFS: Likely acts as a cross-reference or journal table, tracking the lifecycle of a schedule request, potentially linking it to the resulting physical count entries.
  • MTL_CYCLE_COUNT_ENTRIES: Although not listed in the provided foreign keys, this is a critical downstream table. The schedule requests in MTL_CC_SCHEDULE_REQUESTS are typically processed to create actual count entries where quantities are recorded.