Search Results cst_projmfg_cmt_stub_v




Overview
Explore in AI Chat

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

Overview

CST_PROJMFG_CMT_STUB_V is a public synonym view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the BOM (Bills of Material) product family and supports the Project Manufacturing cost management integration between Oracle Projects and Oracle Purchasing's Contract Manufacturing (CMT) functionality. Despite its name and its extensive column list, the view is a structural stub: its defining query selects a large sequence of typed NULL literals across roughly seventy columns and filters on WHERE 1=2, guaranteeing that it never returns rows. The view therefore serves as a compile-time placeholder rather than a data-bearing reporting object.

The role of such a stub view in EBS is to reserve a stable interface contract for downstream cost collection, Project Manufacturing costing, and CMT stub processing logic. Callers — typically cost collector programs, MTL/CST transaction processors, and Project Manufacturing cost distribution routines — can be written and validated against a known column shape even where the underlying data source is not active in a given installation. The column named TOT_CMT_QUANTITY, which users frequently search for, is one element of that reserved shape, identifying the total contract manufacturing quantity in the projected cost row.

Underlying Base Objects

The documented definition of the view references a single base object: PA_IMPLEMENTATIONS_ALL, accessed through a synonym in the APPS schema. The FROM PA_IMPLEMENTATIONS_ALL WHERE 1=2 predicate is the classic technique for generating a view whose column definitions (names, data types, and ordering) are fully declared but whose result set is always empty. The view does not join or aggregate any CMT, purchasing, or Projects transaction tables directly.

Because the view is a stub, it is largely disjoint from live Project Manufacturing costing data. Actual contract manufacturing quantities, commitments, and burdens normally reside in the underlying CMT and purchasing distribution tables that the stub's column names mirror, and in the Project Manufacturing cost tables used by the cost collector. Consequently, the view can be queried safely in any environment without performance impact beyond parsing, and it never participates in row-level processing.

Key Columns

Common Use Cases and Queries

The view is most often encountered when users search for TOT_CMT_QUANTITY or inspect the column shape of Project Manufacturing CMT cost interfaces. A typical query attempts to read the stub directly:

  • SELECT project_id, cmt_number, tot_cmt_quantity FROM apps.cst_projmmfg_cmt_stub_v; — returns zero rows; useful only to confirm the view resolves and its columns exist.
  • Validating column definitions: query ALL_TAB_COLUMNS for TABLE_NAME = 'CST_PROJMFG_CMT_STUB_V' to enumerate the declared columns and data types.
  • Locating the view definition: SELECT text FROM all_views WHERE view_name = 'CST_PROJMFG_CMT_STUB_V'; confirms the WHERE 1=2 stub pattern.

For real Project Manufacturing CMT quantity and cost reporting, practitioners should target the live CMT, purchasing distribution, and Project Manufacturing cost tables that these column names mirror rather than this placeholder view.