Search Results count_status

Overview

MTL_CYCLE_COUNT_ENTRIES_V is an Oracle E-Business Suite Inventory (INV) view owned by the APPS schema. Its documented description, "10SC ONLY," indicates that the object is restricted to a specific deployment or configuration context within the Oracle applications tier and is not a general-purpose, universally supported interface. In Oracle EBS 12.1.1 and 12.2.2, the view exposes denormalized cycle count entry information, combining the raw cycle count entry rows from the base transaction table with descriptive attributes from item master, lookup, and reason-code sources. Because the view joins multiple master and transactional tables, it presents a reporting-friendly projection of cycle count activity, including count quantities, system quantities, adjustment values, and item control attributes.

The term "count_status" that led to this object is represented in the view primarily through the ENTRY_STATUS_CODE column, which carries the workflow or processing state of an individual cycle count entry. The view therefore serves as a convenient read source for queries that need to filter or report on count status alongside item, subinventory, lot, serial, and adjustment details.

Underlying Base Objects

The documented base objects referenced by MTL_CYCLE_COUNT_ENTRIES_V are:

• MTL_CYCLE_COUNT_ENTRIES — the primary transactional source of count entry rows.
• MTL_CYCLE_COUNT_ITEMS and MTL_CYCLE_COUNT_CLASSES — cycle count definition and class assignment data.
• MTL_SYSTEM_ITEMS — item master attributes such as description, control codes, and UOM.
• MTL_TRANSACTION_REASONS — reason name and description for adjustments.
• MTL_ABC_CLASSES and CST_COST_GROUPS — ABC classification and cost group references.
• MFG_LOOKUPS — lookup meanings, notably APPROVAL_CONDITION_MEANING.
• WMS_LICENSE_PLATE_NUMBERS — license plate data relevant to warehouse-managed environments.

Several of these are synonyms within the APPS schema, and MFG_LOOKUPS is itself a view. The join back to MTL_CYCLE_COUNT_ENTRIES is the anchor; item attributes are joined by INVENTORY_ITEM_ID, reason information by TRANSACTION_REASON_ID, and lookup meaning by APPROVAL_CONDITION.

Key Columns

• ENTRY_STATUS_CODE — the count status of the entry, referenced by searches for "count_status."
• CYCLE_COUNT_ENTRY_ID, CYCLE_COUNT_HEADER_ID — identifiers linking the entry to its header and parent count.
• INVENTORY_ITEM_ID, ITEM_DESCRIPTION, PRIMARY_UOM_CODE — item identity and base UOM.
• COUNT_QUANTITY_FIRST / _CURRENT / _PRIOR and SYSTEM_QUANTITY_FIRST / _CURRENT / _PRIOR — historical and current counted versus system on-hand quantities.
• ADJUSTMENT_QUANTITY, ADJUSTMENT_AMOUNT, NEG_ADJUSTMENT_QUANTITY, NEG_ADJUSTMENT_AMOUNT — adjustment results arising from the count.
• SUBINVENTORY, LOCATOR_ID, LOT_NUMBER, SERIAL_NUMBER, REVISION — inventory location and control dimensions.
• APPROVAL_DATE, APPROVAL_CONDITION, APPROVAL_CONDITION_MEANING, APPROVAL_TYPE — approval workflow state and decoded meaning.
• REASON_NAME, REASON_DESCRIPTION — decoded adjustment reason.
• ORGANIZATION_ID — the inventory organization context.

Common Use Cases and Queries

The view is typically used in operational reporting and status tracing for cycle counts. A representative query filtering by count status:

SELECT cycle_count_entry_id, inventory_item_id, item_description, subinventory, entry_status_code, count_quantity_current, system_quantity_current FROM apps.mtl_cycle_count_entries_v WHERE organization_id = :org_id AND entry_status_code = :status;

Analysts also aggregate adjustments by item or reason, and join the view to approval or workflow reporting for counts awaiting approval. Because the object is documented as "10SC ONLY," its use should be confirmed against the specific environment before relying on it in custom extensions or integration interfaces; where it is unavailable, the base table MTL_CYCLE_COUNT_ENTRIES joined to item and lookup tables provides equivalent results.