Results for “zero_count_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_CC_SCHEDULE_REQUESTS is an Oracle Inventory (INV) table that defines and stores cycle count schedule requests within Oracle E-Business Suite 12.1.1 and 12.2.2. Cycle counting is the process by which organizations periodically count selected inventory items in specific subinventories or locators rather than performing full physical inventories. The schedule requests recorded in this table act as the operational bridge between a cycle count header definition and the individual item-level count records that warehouse personnel execute. Each row represents a scheduled request to count a designated item, providing the dates, statuses, and control flags that govern when and how the count is generated and completed.

Under a heuristic Data Vault classification, this table is satellite-leaning. It carries descriptive state attributes — schedule dates, statuses, count generation flags, and item context — that qualify and track a business event driven by its parent cycle count header. The primary key CYCLE_COUNT_SCHEDULE_ID provides the unique surrogate identifier for each schedule request row.

Key Information Stored

Each row is uniquely identified by the surrogate primary key CYCLE_COUNT_SCHEDULE_ID (enforced by index MTL_CC_SCHEDULE_REQUESTS_PK). The documented unique index MTL_CC_SCHEDULE_REQUESTS_U2 on CYCLE_COUNT_HEADER_ID and CYCLE_COUNT_SCHEDULE_ID serves as a business-key candidate linking the request back to its governing cycle count definition.

• CYCLE_COUNT_HEADER_ID — foreign key to the parent cycle count header that owns this schedule request.
• INVENTORY_ITEM_ID — the item to be counted.
• SUBINVENTORY and LOCATOR_ID — the storage location targeted by the count.
• REVISION, LOT_NUMBER, and SERIAL_NUMBER — the revision, lot, and serial context for controlled items.
• REQUEST_SOURCE_TYPE — indicates how the schedule request originated.
• SCHEDULE_DATE and COUNT_DUE_DATE — when the count is planned and its due date.
• SCHEDULE_STATUS and SCHEDULE_COMPLETION_DATE — current lifecycle state and completion timestamp.
• COUNT_REQUESTS_GENERATED_FLAG and ZERO_COUNT_FLAG — control flags for whether count entries have been produced and whether zero-on-hand counts apply.
• REQUEST_ID plus the concatenated PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — concurrent program context that created or last processed the row.
• PROCESS_FLAG — internal processing indicator.
• Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and ATTRIBUTE_CATEGORY with ATTRIBUTE1–ATTRIBUTE15 for extensibility.

Common Use Cases and Queries

The table supports scheduling reports, count backlog monitoring, and reconciliation between planned and generated counts. Typical reporting includes open schedule requests, overdue counts, and item-level traceability.

• List pending schedule requests with their due dates:
• SELECT CYCLE_COUNT_SCHEDULE_ID, CYCLE_COUNT_HEADER_ID, INVENTORY_ITEM_ID, SCHEDULE_DATE, COUNT_DUE_DATE FROM MTL_CC_SCHEDULE_REQUESTS WHERE SCHEDULE_STATUS = 'PENDING';
• Identify requests where count entries have not yet been generated:
• ... WHERE COUNT_REQUESTS_GENERATED_FLAG = 'N';
• Detect overdue counts by comparing COUNT_DUE_DATE to SYSDATE.

Related Objects

The following objects are most significant in the relationship graph:

• MTL_CYCLE_COUNT_HEADERS — joined via CYCLE_COUNT_HEADER_ID; the parent definition that drives schedule requests.
• MTL_CYCLE_COUNT_ITEMS — also referenced through CYCLE_COUNT_HEADER_ID and INVENTORY_ITEM_ID; the item membership of a cycle count.
• MTL_CC_SCHED_COUNT_XREFS — child table referencing CYCLE_COUNT_SCHEDULE_ID; correlates schedule requests with generated counts.
• MTL_SYSTEM_ITEMS_B — resolves INVENTORY_ITEM_ID to descriptive item attributes.
• MTL_ITEM_LOCATIONS — resolves LOCATOR_ID to physical bin information.
• MTL_SECONDARY_INVENTORIES — resolves SUBINVENTORY to subinventory definitions.