Search Results mtl_cc_sched_count_xrefs_pk

Overview

The MTL_CC_SCHED_COUNT_XREFS table is a core transactional table within the Oracle E-Business Suite Inventory (INV) module, specifically for the Cycle Counting functionality. Its primary role is to establish and maintain a cross-reference relationship between a scheduled count request and the actual count entries generated from it. This table acts as a critical junction, ensuring traceability and auditability in the cycle counting process by linking the planning phase (the schedule) to the execution phase (the physical count entries). It is essential for reconciling what was planned to be counted with what was actually counted, a fundamental requirement for inventory accuracy and control in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is defined by its composite primary key, which consists of two foreign key columns. This design enforces the one-to-many relationship between a schedule request and its resulting entries. The key columns are:

• CYCLE_COUNT_SCHEDULE_ID: References a unique schedule request in the MTL_CC_SCHEDULE_REQUESTS table. This identifies the specific cycle counting plan or task.
• CYCLE_COUNT_ENTRY_ID: References a unique count transaction in the MTL_CYCLE_COUNT_ENTRIES table. This identifies an individual physical count record performed for the referenced schedule.

Each row in this table represents a single instance where a specific count entry was created as a direct result of a specific schedule request.

Common Use Cases and Queries

This table is pivotal for operational reporting and troubleshooting within the cycle counting process. A common use case is identifying all count entries that originated from a particular schedule, which is crucial for reviewing the completeness of a scheduled count. Conversely, it is used to trace the source schedule for a given count entry during discrepancy analysis. Database administrators and functional consultants may query this table to diagnose orphaned records or validate data integrity. A typical reporting query would join this cross-reference table to both the schedule and entry tables to provide a consolidated view of scheduled versus executed counts.

SELECT s.schedule_name, e.entry_id, e.item_id, e.count_date
FROM mtl_cc_sched_count_xrefs x,
     mtl_cc_schedule_requests s,
     mtl_cycle_count_entries e
WHERE x.cycle_count_schedule_id = s.schedule_id
  AND x.cycle_count_entry_id = e.entry_id
  AND s.organization_id = :org_id;

Related Objects

The MTL_CC_SCHED_COUNT_XREFS table is centrally linked to two primary transactional tables via foreign key constraints, as documented in the ETRM metadata:

• MTL_CC_SCHEDULE_REQUESTS: The foreign key on column CYCLE_COUNT_SCHEDULE_ID links to this table, which stores the definition and status of cycle count schedules.
• MTL_CYCLE_COUNT_ENTRIES: The foreign key on column CYCLE_COUNT_ENTRY_ID links to this table, which holds the detailed records of each physical count performed, including item, quantity, and location.

These relationships are enforced by the primary key constraint MTL_CC_SCHED_COUNT_XREFS_PK, ensuring data consistency. The table is integral to the underlying logic of the Cycle Counting APIs and user interfaces.