Search Results sort_sequence




Overview
Explore in AI Chat

Overview

The GMF_COST_CMPNT_CLASS_SLA_V view is a public APPS schema database object belonging to the Process Manufacturing Financials (GMF) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as the underlying source for the Oracle EBS value set named GMF_COST_CMPNT_CLASS_SLA, which is used to drive List of Values (LOV) prompts and validation logic within the costing component class functionality. Because the view is exposed in the APPS schema, it is a supported integration point that reporting tools, custom concurrent programs, and third-party extensions may query directly.

In practical terms, the view presents a clean, filtered list of costing component classes. Rather than exposing every historical or logically deleted row of the base table, it restricts the result set to active records. A distinguishing element of its design is a UNION that appends a single synthetic "zero" row, providing a blank/default entry that value sets frequently require for optional or not-applicable selections. The view is documented as VALID and carries Oracle Proprietary, Confidential Information handling notices per the ETRM repository.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as SYNONYMs:

  • CM_CMPT_MST — the master table holding costing component class definitions. All meaningful business columns in the view are sourced from this table.
  • DUAL — the standard Oracle one-row utility table, used here solely to synthesize the placeholder row appended via UNION.

The core SELECT filters CM_CMPT_MST using WHERE DELETE_MARK = 0, so only non-deleted component classes are surfaced. The second branch of the UNION projects literal constants (0 and empty strings) for every column and returns exactly one row. The relationship between the view and its base table is therefore read-only and one-directional: the view never writes back to CM_CMPT_MST, and any DML against it would be non-updatable given the UNION construct.

Key Columns

  • COST_CMPNTCLS_ID — Primary identifier of the costing component class; returns 0 for the synthetic placeholder row.
  • COST_CMPNTCLS_CODE — The user-facing short code for the component class.
  • COST_CMPNTCLS_DESC — Descriptive text shown in LOVs and reports.
  • SORT_SEQUENCE — Controls ordering of entries in the value set list.
  • USAGE_IND — Flag indicating whether the class is in active use.
  • PRIMARY_CMPNTCLS_ID — Reference to an associated primary component class.
  • PRODUCT_COST_IND, UPDATE_COST_IND, PPV_IND — Indicator flags governing product costing, cost update, and purchase price variance behaviour respectively.
  • CMPNT_GROUP — Grouping attribute for categorising component classes.
  • TEXT_CODE — Free-form text code associated with the class.
  • TRANS_CNT — Transaction count or related counter value.
  • DELETE_MARK — Soft-delete flag from the base table; always 0 in the returned rows, since the WHERE clause excludes any record with a non-zero value.

Common Use Cases and Queries

Typical usage centres on populating LOVs and validating costing component class selections in Process Manufacturing costing screens and custom reports. Analysts commonly join this view to cost rollup or cost detail tables using COST_CMPNTCLS_ID to translate IDs into descriptive codes and descriptions.

A basic lookup returns all active classes, excluding the placeholder:

  • SELECT COST_CMPNTCLS_ID, COST_CMPNTCLS_CODE, COST_CMPNTCLS_DESC FROM APPS.GMF_COST_CMPNT_CLASS_SLA_V WHERE COST_CMPNTCLS_ID > 0 ORDER BY SORT_SEQUENCE, COST_CMPNTCLS_CODE;

To mirror the value set exactly, including the default entry, omit the ID filter and rely on the view's inherent ordering logic. Because the underlying DELETE_MARK filter is already applied, no additional soft-delete predicate is required. For reporting that must display every historical record, query CM_CMPT_MST directly rather than this view, since the view intentionally suppresses logically deleted rows. Given the UNION structure, the view should be treated strictly as a query-only object; attempts to insert, update, or delete through it will fail.