Search Results number_of_counts




Overview
Explore in AI Chat

Overview

APPS.CST_XLA_CYCLE_COUNT_REF_V is a lightweight reference view shipped as part of the Oracle E-Business Suite Cost Management and Subledger Accounting (XLA) integration layer. It exposes a minimal projection of physical inventory cycle count entry data for use by the Subledger Accounting program when it needs to resolve the cycle count entry identifiers and count volumes associated with inventory transactions. The view is documented in ETRM for both release 12.1.1 and 12.2.2, and is owned by the APPS schema, which is consistent with the convention that EBS views intended for cross-module consumption are deployed as APPS-owned database objects.

The view is deliberately narrow. Rather than reproducing the full breadth of cycle count entry attributes, it publishes only two columns — CYCLE_COUNT_ENTRY_ID and NUMBER_OF_COUNTS — so that downstream accounting and reporting logic can link an inventory adjustment back to its originating cycle count entry and, where relevant, quantify how many counts were recorded. This makes it a supporting lookup object rather than a primary analytical source.

Underlying Base Objects

According to the documented view text, CST_XLA_CYCLE_COUNT_REF_V is defined as a simple SELECT over the base table MTL_CYCLE_COUNT_ENTRIES:

  • MTL_CYCLE_COUNT_ENTRIES — the inventory cycle count entry table, referenced through a synonym in the APPS schema. This table stores individual cycle count entry records generated when a cycle count is scheduled and performed against inventory items.

No joins, filters, or aggregations are applied. The view therefore inherits the row cardinality of MTL_CYCLE_COUNT_ENTRIES and performs no transformation of the underlying values beyond column aliasing. Because it is a straightforward select, it does not introduce its own data; it simply makes a subset of the base table available under a naming convention that aligns with the XLA reference-view family (prefixed CST_XLA).

Key Columns

The view exposes two documented columns:

  • CYCLE_COUNT_ENTRY_ID — the unique identifier of the cycle count entry. This is the primary key of the underlying MTL_CYCLE_COUNT_ENTRIES row and the value most frequently used to correlate cycle count adjustments with their accounting entries.
  • NUMBER_OF_COUNTS — the number of counts associated with the cycle count entry, representing how many count occurrences were recorded for that entry.

No other columns are documented. Consumers requiring additional cycle count attributes such as count dates, organization identifiers, or adjustment quantities must query MTL_CYCLE_COUNT_ENTRIES or related cycle count tables directly.

Common Use Cases and Queries

The primary use case is resolving a cycle count entry identifier during Subledger Accounting processing or during diagnostic reporting of inventory count activity. A typical lookup retrieves the count volume for a specific entry:

  • Resolve a single entry: SELECT cycle_count_entry_id, number_of_counts FROM apps.cst_xla_cycle_count_ref_v WHERE cycle_count_entry_id = :entry_id;
  • Enumerate all cycle count entries referenced through the view for reconciliation against XLA accounting lines: SELECT cycle_count_entry_id, number_of_counts FROM apps.cst_xla_cycle_count_ref_v ORDER BY cycle_count_entry_id;

Because the view carries no organization or date filter, it should be joined to MTL_CYCLE_COUNT_HEADERS or MTL_PARAMETERS in production queries where organization-scoped results are required. Given its minimal column set and lack of predicates, the view is inexpensive to query and is suited to point lookups and joins keyed on cycle_count_entry_id, but it is not intended as a general-purpose cycle count reporting view.