Results for “loc_last_schedule_date”

14 results




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

Overview

The MTL_CC_SUBINVENTORIES_ALL_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the INV (Inventory) product family. Its ETRM description is limited to the notation "10SC ONLY," indicating that the object is restricted to a specific deployment or localization context rather than being a general-purpose, globally supported view. Functionally, the view exposes subinventory-level cycle count scheduling configuration. Each row associates a subinventory with a cycle count header, a count frequency, and scheduling attributes, making the view useful for reporting on how cycle counting is configured across a warehouse organization.

Because the view selects directly from MTL_CC_SUBINVENTORIES with no joins, filtering, or aggregation, it is structurally a straight projection of the underlying table. This means it carries no derived logic of its own, and its role in reporting and integration is essentially that of a read-only presentation layer. The literal search term "cycle_count_header_id" corresponds precisely to the first column of the view, confirming that users querying this view are typically interested in cycle count definitions at the subinventory level.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the view references a single base object: MTL_CC_SUBINVENTORIES, exposed to APPS through a synonym. The view text is a direct SELECT of eleven named columns from that table, with no WHERE clause, no UNION, and no function calls applied to the projected columns. As a result, the view returns one row for every row in MTL_CC_SUBINVENTORIES, subject only to any database-level privileges and synonyms that govern access.

This one-to-one relationship has practical implications. The view does not enforce organization security, operating unit filtering, or role-based data restriction beyond what the underlying table and synonym already provide. It is therefore best treated as a naming convenience rather than as a controlled access mechanism. In 12.1.1 and 12.2.2, the underlying table belongs to the Inventory module's cycle counting feature set and stores the schedule definitions used by the cycle count scheduler.

Key Columns

  • CYCLE_COUNT_HEADER_ID — Identifier that links the subinventory configuration to its cycle count header definition. It is the primary key component used to join this view to cycle count header tables.
  • SUBINVENTORY — The subinventory code to which the cycle count schedule applies.
  • DISABLE_FLAG — Indicator of whether the cycle count schedule for the subinventory is disabled.
  • NUM_COUNTS_PER_YEAR — The number of counts scheduled per year, effectively the counting frequency.
  • LOC_LAST_SCHEDULE_DATE — The last date on which scheduling was performed for the location.
  • SCHEDULE_ORDER — Ordering value governing the sequence in which schedules are processed.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard EBS audit and concurrency context.

Common Use Cases and Queries

The most direct use case is retrieving the cycle count configuration for a given header or subinventory. For example, to find all subinventories tied to a specific header identifier:

SELECT subinventory, num_counts_per_year, disable_flag, loc_last_schedule_date FROM mtl_cc_subinventories_all_v WHERE cycle_count_header_id = :p_header_id;

A second scenario is auditing which subinventories have cycle counting disabled or configured below a desired threshold:

SELECT subinventory, num_counts_per_year, schedule_order FROM mtl_cc_subinventories_all_v WHERE disable_flag = 'Y' OR num_counts_per_year < 12 ORDER BY schedule_order;

A third use is joining the view to cycle count header and definition tables to build reports on scheduled versus completed counts, using CYCLE_COUNT_HEADER_ID as the join key. Given the "10SC ONLY" designation, implementers should verify availability in their specific instance before relying on the view in custom code or integrations, and should favor the base table MTL_CC_SUBINVENTORIES where broader support is required.