Results for “mtl_cycle_count_headers”

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

Overview

MTL_CYCLE_COUNT_HEADERS is the master definition table for cycle counting in the Oracle Inventory (INV) module. Each row represents a named cycle count header that controls how a specific inventory organization performs periodic physical counts of on-hand material. The header consolidates the scheduling rules, tolerance thresholds, approval options, and accounting defaults that drive the entire cycle count process — from generating count schedules through entering counts, performing recounts, and posting adjustments back to inventory and the general ledger.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies MTL_CYCLE_COUNT_HEADERS as a hub. This is consistent with its role: CYCLE_COUNT_HEADER_ID is the immutable surrogate primary key (MTL_CYCLE_COUNT_HEADERS_PK), and the table acts as the central anchor to which subordinate cycle count facts — entries, classes, items, subinventories, and schedule requests — all attach. A functional hub-and-satellite split would separate the descriptive attributes (tolerances, flags, schedules) into a satellite keyed to CYCLE_COUNT_HEADER_ID.

Key Information Stored

The primary key is CYCLE_COUNT_HEADER_ID, a system-generated surrogate. A documented unique index (MTL_CYCLE_COUNT_HEADERS_UK1) defines the business key as CYCLE_COUNT_HEADER_NAME within an OPERATION_ID context, making the header name plus organization combination the human-recognizable identifier. A secondary unique index (MTL_CYCLE_COUNT_HEADERS_U2) covers ORGANIZATION_ID and CYCLE_COUNT_HEADER_ID.

• CYCLE_COUNT_HEADER_NAME — the user-defined name identifying the cycle count definition.
• ORGANIZATION_ID — the inventory organization to which the header belongs; foreign key to MTL_PARAMETERS.
• ABC_ASSIGNMENT_GROUP_ID — links the header to an ABC assignment group governing count frequency by class.
• CYCLE_COUNT_CALENDAR and CALENDAR_EXCEPTION_SET — drive when counts are generated and which exception dates are honored.
• AUTOSCHEDULE_ENABLED_FLAG, SCHEDULE_INTERVAL_TIME, HEADER_LAST_SCHEDULE_DATE, HEADER_NEXT_SCHEDULE_DATE — automatic scheduling parameters.
• APPROVAL_OPTION_CODE, APPROVAL_TOLERANCE_POSITIVE/NEGATIVE — count approval and variance thresholds.
• COST_TOLERANCE_POSITIVE/NEGATIVE and HIT_MISS_TOLERANCE_POSITIVE/NEGATIVE — hit/miss and valuation thresholds.
• INVENTORY_ADJUSTMENT_ACCOUNT — the GL account (foreign key to GL_CODE_COMBINATIONS) used for adjustment postings.
• MAXIMUM_AUTO_RECOUNTS, AUTOMATIC_RECOUNT_FLAG, CYCLE_COUNT_TYPE — recount behavior and count type.
• ZERO_COUNT_FLAG, SERIAL_COUNT_OPTION, CONTAINER_ENABLED_FLAG — count scope and item/lot control flags.

Common Use Cases and Queries

Typical uses include identifying active headers per organization, reviewing tolerance settings, and joining entries for variance reporting.

• List all headers for an organization: SELECT cycle_count_header_id, cycle_count_header_name FROM mtl_cycle_count_headers WHERE organization_id = :org_id;
• Find headers due for their next schedule: SELECT * FROM mtl_cycle_count_headers WHERE header_next_schedule_date <= SYSDATE AND disable_date IS NULL;
• Join to entries for count status: SELECT h.cycle_count_header_name, e.* FROM mtl_cycle_count_headers h, mtl_cycle_count_entries e WHERE h.cycle_count_header_id = e.cycle_count_header_id;
• Reporting on tolerance configuration and ABC groups for audit or SOX compliance reviews.

Related Objects

The header is referenced by the following child tables via CYCLE_COUNT_HEADER_ID:

• MTL_CYCLE_COUNT_ENTRIES — individual count entry lines.
• MTL_CYCLE_COUNT_ITEMS — items eligible within the header.
• MTL_CYCLE_COUNT_CLASSES — ABC class definitions per header.
• MTL_CC_SUBINVENTORIES — subinventory scope.
• MTL_CC_SCHEDULE_REQUESTS and MTL_CC_ENTRIES_INTERFACE — scheduling and interface staging.
• Parent lookups: MTL_PARAMETERS, MTL_ABC_ASSIGNMENT_GROUPS, BOM_CALENDARS, BOM_EXCEPTION_SETS, GL_CODE_COMBINATIONS.

These relationships confirm the header's position as the hub of the cycle count transactional model.