Search Results mtl_cycle_count_headers

Overview

The MTL_CYCLE_COUNT_HEADERS table is a core data object within the Oracle E-Business Suite Inventory (INV) module, specifically for releases 12.1.1 and 12.2.2. It serves as the master definition table for cycle counting, a critical inventory accuracy process where subsets of items are counted on a recurring schedule. Each record in this table represents a unique, named cycle count schedule or plan for a specific inventory organization. The header defines the overarching rules, parameters, and controls that govern the execution of physical counts, acting as the parent entity for all related count entries, schedules, and assignments.

Key Information Stored

The table stores the fundamental configuration for a cycle count. The primary identifier is the system-generated CYCLE_COUNT_HEADER_ID. The unique combination of CYCLE_COUNT_HEADER_NAME and ORGANIZATION_ID ensures each schedule name is unique per organization. Key foreign key columns define critical operational parameters: ORGANIZATION_ID links to MTL_PARAMETERS, ABC_ASSIGNMENT_GROUP_ID links to MTL_ABC_ASSIGNMENT_GROUPS for ABC-based scheduling, and CYCLE_COUNT_CALENDAR links to BOM_CALENDARS to define valid working days. The INVENTORY_ADJUSTMENT_ACCOUNT references GL_CODE_COMBINATIONS to specify the general ledger account for posting count variances. Additional columns (implied by standard functionality but not explicitly listed in the provided metadata) typically control approval hierarchies, tolerance percentages, automatic schedule generation, and count frequency.

Common Use Cases and Queries

This table is central to cycle count administration and reporting. Common operational scenarios include auditing active count schedules, identifying schedules by name or organization, and analyzing setup parameters. A typical query retrieves header information for a specific organization:

• SELECT cycle_count_header_name, description, inventory_adjustment_account FROM inv.mtl_cycle_count_headers WHERE organization_id = :org_id ORDER BY 1;

For integration or data fix scenarios, developers often join this table to its child entities to analyze the full count lifecycle. Reporting use cases frequently involve aggregating data from child tables like MTL_CYCLE_COUNT_ENTRIES back to the header to measure schedule performance, such as the total number of items scheduled, counted, or adjusted per cycle count plan.

Related Objects

As indicated by the foreign key relationships, MTL_CYCLE_COUNT_HEADERS is the central hub for all cycle count data. Key dependent child tables include MTL_CYCLE_COUNT_ENTRIES (individual count transactions), MTL_CYCLE_COUNT_ITEMS (specific item assignments), MTL_CYCLE_COUNT_CLASSES (item class assignments), and MTL_CC_SUBINVENTORIES (subinventory assignments). The MTL_CC_ENTRIES_INTERFACE and MTL_CC_SCHEDULE_REQUESTS tables interface with the header for importing count data and generating schedules, respectively. It is also referenced by foundational setup tables like MTL_PARAMETERS and GL_CODE_COMBINATIONS. The primary APIs for programmatically creating and managing cycle count setups, such as INV_CYCLE_COUNT_PUB, internally manipulate this table.