Search Results cst_xla_cycle_count_ref_v




Overview

In the Oracle E-Business Suite Release 12.1.1 and 12.2.2 technical repository, CST_XLA_CYCLE_COUNT_REF_V is a substitution-variable view owned by the APPS schema and catalogued under the Bills of Material (BOM) product family. It is a thin projection layer rather than a complex reporting object. Its purpose is to expose a minimal, two-column reference set from the cycle counting tables so that other components — most notably Subledger Accounting (XLA) definition metadata held in the XLA reference structures — can resolve a cycle count entry and its associated count quantity without querying the underlying inventory table directly.

The view is reported as VALID in the data dictionary, indicating that its defining query compiles cleanly against the APPS synonym for the underlying base table. Because the identifier prefix is CST (Cost Management) while the product is catalogued as BOM (Bills of Material), the view sits at the intersection of costing, inventory, and subledger accounting functionality. It is not intended for ad hoc end-user reporting; rather, it serves as a supporting reference object for XLA event and journal line definition logic.

Underlying Base Objects

The documented view metadata identifies a single referenced base object: MTL_CYCLE_COUNT_ENTRIES, accessed through a SYNONYM. The defining SQL text is:

No joins, filters, aggregations, or functions are applied. Consequently, the view is a direct row-for-row projection of the two named columns from MTL_CYCLE_COUNT_ENTRIES. MTL_CYCLE_COUNT_ENTRIES is the Oracle Inventory base table that stores physical cycle count entry records, each linked to a scheduled cycle count header, an inventory item, and a revision. Because the view performs no filtering, it inherits the complete row population of the base table, including entries in any status. In a 12.2.2 environment the referenced object resolves through the standard APPS synonym to the INV schema table, which is consistent across both 12.1.1 and 12.2.2 configurations.

Key Columns

The view exposes only two columns:

  • CYCLE_COUNT_ENTRY_ID — The surrogate primary key of the cycle count entry. It is a NUMBER column that uniquely identifies a single count transaction record and is the join key used by downstream XLA and costing logic to associate a subledger event or journal line with the originating count entry.
  • NUMBER_OF_COUNTS — The count quantity recorded against the cycle count entry. It preserves the base table column name and data type; it represents the quantity counted on that entry record.

Because the view adds no aliases beyond the underlying column names (aside from the positional re-listing in the SELECT clause), consumers can rely on the exact same column names and semantics as MTL_CYCLE_COUNT_ENTRIES for these two attributes. All other descriptive columns of the base table — such as item, revision, subinventory, or locator context — are deliberately omitted.

Common Use Cases and Queries

The primary use case is XLA reference resolution: subledger accounting definitions can reference this view to obtain the cycle count entry identifier and count quantity needed when constructing accounting events or journal line references. A typical diagnostic query verifies that the view returns the expected population and can be joined back to its base table:

  • SELECT CYCLE_COUNT_ENTRY_ID, NUMBER_OF_COUNTS FROM APPS.CST_XLA_CYCLE_COUNT_REF_V WHERE CYCLE_COUNT_ENTRY_ID = :entry_id;
  • SELECT v.CYCLE_COUNT_ENTRY_ID, v.NUMBER_OF_COUNTS, e.ORGANIZATION_ID FROM APPS.CST_XLA_CYCLE_COUNT_REF_V v, APPS.MTL_CYCLE_COUNT_ENTRIES e WHERE v.CYCLE_COUNT_ENTRY_ID = e.CYCLE_COUNT_ENTRY_ID;

Consultants commonly use such statements to confirm that a custom or seeded accounting definition can locate the required count reference, and to validate the view after patching or cloning. Because no filtering is present, queries should always constrain by CYCLE_COUNT_ENTRY_ID or join to a narrower driving set to avoid full scans of the cycle count table.