Results for “mtl_cycle_count_classes_all_v”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view APPS.MTL_CYCLE_COUNT_CLASSES_ALL_V is an Inventory (INV) module dictionary object that exposes ABC class definitions used by Oracle's cycle counting engine. In Oracle EBS 12.1.1 and 12.2.2 it is documented in the E-Business Suite Technical Reference Manual (ETRM) with the description "10SC ONLY," indicating it was originally created to support the 10SC (a legacy/vertical Inventory configuration) code line and remains present in the shipped schema as a valid, queryable object. The view presents the ABC assignment group and cycle count class rules that drive how items are selected for recurring cycle counts and how count tolerances are evaluated.
Because the view is defined as a simple projection over a single base table, it carries no independent business logic. Its role in reporting and integration is therefore to provide a stable, read-only interface for external reports, custom concurrent programs, and interface extracts that need cycle count class configuration without touching the underlying table directly. The presence of standard WHO columns and concurrent program audit columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) confirms it is intended for use in report and interface contexts.
Underlying Base Objects
Per the documented ETRM metadata, the view is defined over a single synonym: MTL_CYCLE_COUNT_CLASSES. The view text selects the full column list from that source with no joins, filters, or WHERE clause, making it a straightforward 1:1 projection. This has two consequences. First, every row returned by the view corresponds to exactly one row in MTL_CYCLE_COUNT_CLASSES; no aggregation or de-duplication occurs. Second, all DML restrictions applicable to the base table apply conceptually to the view, and any change to the base table structure requires the view to be recompiled.
The synonym MTL_CYCLE_COUNT_CLASSES resolves to the APPS-owned cycle count classes entity, which stores one record per ABC class defined against a cycle count header and organization. The view does not expose header-level descriptive columns such as names or descriptions; those reside on the cycle count header and ABC class entities and must be joined separately if required in reporting.
Key Columns
- ABC_ASSIGNMENT_GROUP_ID — the identifier of the ABC assignment group to which the cycle count class rows belong; this is the column referenced by the user search term and is the primary grouping key for reporting by ABC compilation group.
- ABC_CLASS_ID — identifies the ABC class (for example A, B, or C valuation band) associated with the row.
- CYCLE_COUNT_HEADER_ID — links the class definition to its cycle count header, which carries the count name, description, and status.
- ORGANIZATION_ID — the inventory organization in which the class definition applies; essential for multi-org reporting.
- NUM_COUNTS_PER_YEAR — the number of cycle counts scheduled annually for the class, driving count frequency calculations.
- APPROVAL_TOLERANCE_POSITIVE / APPROVAL_TOLERANCE_NEGATIVE — quantity variance thresholds governing automatic approval of count adjustments.
- COST_TOLERANCE_POSITIVE / COST_TOLERANCE_NEGATIVE — value-based thresholds used when approval is driven by extended cost variance.
- HIT_MISS_TOLERANCE_POSITIVE / HIT_MISS_TOLERANCE_NEGATIVE — thresholds applied to hit/miss accuracy analysis for the class.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns recording the last process that inserted or updated the row.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
Common Use Cases and Queries
Typical use cases include auditing cycle count class configuration, extracting tolerance settings for reconciliation, and driving custom ABC analysis reports. A representative query joining the view to the cycle count header for a specific organization is shown below.
- List classes by ABC assignment group:
SELECT abc_assignment_group_id, abc_class_id, num_counts_per_year, organization_id FROM apps.mtl_cycle_count_classes_all_v WHERE abc_assignment_group_id = :p_group_id ORDER BY abc_class_id; - Review tolerances for an organization:
SELECT abc_class_id, approval_tolerance_positive, approval_tolerance_negative, cost_tolerance_positive, cost_tolerance_negative FROM apps.mtl_cycle_count_classes_all_v WHERE organization_id = :p_org_id; - Trace the last concurrent program update:
SELECT abc_class_id, request_id, program_id, program_update_date FROM apps.mtl_cycle_count_classes_all_v WHERE last_update_date > SYSDATE - 7;
Because the view performs no filtering, queries should always constrain at least ORGANIZATION_ID or ABC_ASSIGNMENT_GROUP_ID to avoid full-table scans across all organizations.
-
10SC ONLY
APPS.MTL_CYCLE_COUNT_CLASSES_ALL_V·↳ MTL_CYCLE_COUNT_CLASSES·Explore INV module →
-
10SC ONLY
APPS.MTL_CYCLE_COUNT_CLASSES_ALL_V·↳ MTL_CYCLE_COUNT_CLASSES·Explore INV module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2