Results for “mtl_cycle_count_items_all_v”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MTL_CYCLE_COUNT_ITEMS_ALL_V is an Oracle E-Business Suite view owned by the APPS schema within the INV (Inventory) product module. According to the ETRM metadata, the object carries the status VALID and is documented with the description "10SC ONLY," indicating that the view is restricted to a specific deployment or configuration context rather than being a general-purpose inventory object. Functionally, the view presents the row-level detail of cycle count item scheduling, exposing the association between a cycle count header, an inventory item, and the sequence in which that item is scheduled for counting.
The object name includes the "_ALL_V" suffix, which conventionally denotes a view in Oracle EBS that consolidates or projects data for consumption by reports, concurrent programs, and integration interfaces without applying organization-specific filtering at the database view layer. In practice, the view serves as an access point for cycle count scheduling and approval tolerance data that downstream reports, custom concurrent programs, and external integrations query directly. The SCHEDULE_ORDER column is of particular interest to users who search for this object, since it drives the ordering logic used by cycle count generation and printed count sheets.
Underlying Base Objects
The view is defined over a single documented base object: MTL_CYCLE_COUNT_ITEMS, referenced through a synonym in the APPS schema. The view text is a straightforward projection, selecting an explicit list of columns from that base table rather than joining additional entities. Because the definition performs no filtering, aggregation, or join expansion, the view is structurally equivalent to a column-subset of MTL_CYCLE_COUNT_ITEMS and inherits all of its row- and column-level behavior.
The relationship between the view and its base object is therefore one-to-one at the row level. Any insert, update, or delete applied through the base table is immediately reflected in the view, subject to the usual EBS security and grants. The view does not introduce DML capability of its own; it is intended for read access, and applications that require modification must target the base table through the supported Inventory APIs.
Key Columns
- CYCLE_COUNT_HEADER_ID – Identifier of the parent cycle count header, linking each item row to its cycle count definition.
- INVENTORY_ITEM_ID – The inventory item subject to the count schedule.
- ABC_CLASS_ID – ABC classification assigned to the item, which typically influences count frequency.
- ITEM_LAST_SCHEDULE_DATE – Date on which the item was last scheduled for counting.
- SCHEDULE_ORDER – Sequence value controlling the order in which items are scheduled or presented for counting.
- APPROVAL_TOLERANCE_POSITIVE / APPROVAL_TOLERANCE_NEGATIVE – Positive and negative quantity tolerances within which a count variance is auto-approved.
- CONTROL_GROUP_FLAG – Indicates whether the item participates in a control group count.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – Standard concurrent program audit columns identifying the process that created or last updated the row.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – The standard EBS descriptive flexfield columns for extensible, customer-defined data.
Common Use Cases and Queries
The most frequent use of this view is to retrieve the scheduling sequence and tolerance settings for items attached to a cycle count. A representative query lists scheduled items in count order for a given header:
SELECT CYCLE_COUNT_HEADER_ID, INVENTORY_ITEM_ID, SCHEDULE_ORDER, ITEM_LAST_SCHEDULE_DATE FROM APPS.MTL_CYCLE_COUNT_ITEMS_ALL_V WHERE CYCLE_COUNT_HEADER_ID = :p_header_id ORDER BY SCHEDULE_ORDER;SELECT INVENTORY_ITEM_ID, ABC_CLASS_ID, CONTROL_GROUP_FLAG, APPROVAL_TOLERANCE_POSITIVE, APPROVAL_TOLERANCE_NEGATIVE FROM APPS.MTL_CYCLE_COUNT_ITEMS_ALL_V WHERE CYCLE_COUNT_HEADER_ID = :p_header_id;
These queries are commonly embedded in custom count sheet reports, interface extracts, and reconciliation scripts. Because the view performs no filtering, queries should always constrain on CYCLE_COUNT_HEADER_ID or INVENTORY_ITEM_ID to avoid full scans of the underlying table.
-
10SC ONLY
APPS.MTL_CYCLE_COUNT_ITEMS_ALL_V·↳ MTL_CYCLE_COUNT_ITEMS·Explore INV module →
-
10SC ONLY
APPS.MTL_CYCLE_COUNT_ITEMS_ALL_V·↳ MTL_CYCLE_COUNT_ITEMS·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.2.2
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2