Search Results usage_ind




Overview
Explore in AI Chat

Overview

APPS.GMF_COST_CMPNT_CLASS_SLA_V is a subledger accounting (SLA) supporting view in the Oracle E-Business Suite Process Manufacturing (OPM) cost management schema. It exposes the cost component class master definition, allowing Subledger Accounting, costing engines, and downstream reporting tools to resolve a COST_CMPNTCLS_CODE and its attributes without directly querying the underlying OPM master table. The view is owned by APPS, the standard application schema through which EBS responsibilities and SLA rules access data.

The view is defined as a UNION of two queries. The first selects all active rows from the base cost component class master table where DELETE_MARK = 0. The second selects a single synthetic "all zeros" row from DUAL, producing a placeholder record with a numeric key of 0, blank descriptive fields, and zeroed flags. This dummy row is a standard OPM/SLA convention that supplies a default, null-equivalent value for lookup and left-join operations, ensuring that no join inadvertently drops a transaction line when no cost component class is assigned.

Underlying Base Objects

The view is defined over two referenced objects, both resolved through synonyms in the APPS schema:

  • CM_CMPT_MST — the cost component class master table in Process Manufacturing. It holds one row per cost component class and the flags that govern how that class participates in product costing, update costing, and purchase price variance handling. The view reads this table in full, filtered only by the soft-delete column.
  • DUAL — the Oracle-supplied single-row pseudo-table, used here solely to generate the synthetic zero row via the second branch of the UNION.

Because the view is a straightforward projection with no joins, aggregation, or analytic functions, it is inexpensive to query and remains consistent with the base table except for the enforced DELETE_MARK = 0 filter and the appended placeholder row.

Key Columns

  • COST_CMPNTCLS_ID — primary surrogate key of the cost component class. Value 0 identifies the synthetic placeholder row.
  • COST_CMPNTCLS_CODE — the user-visible code used throughout OPM and SLA setups; this is the value users search for when locating a class.
  • COST_CMPNTCLS_DESC — descriptive name of the cost component class.
  • SORT_SEQUENCE — display/ordering sequence for the class.
  • USAGE_IND — usage indicator controlling whether and how the class is applied.
  • PRIMARY_CMPNTCLS_ID — reference to the primary component class from which this class is derived.
  • PRODUCT_COST_IND, UPDATE_COST_IND, PPV_IND — flags governing inclusion in product costing, cost update, and purchase price variance calculations respectively.
  • CMPNT_GROUP — grouping classification for the component class.
  • TEXT_CODE — code referring to extended descriptive text.
  • TRANS_CNT — transaction counter used for concurrency control.
  • DELETE_MARK — soft-delete flag; rows returned by the view are always 0.

Common Use Cases and Queries

The view is typically used to present a validated cost component class list in SLA and costing lookups, and to join transaction or cost detail lines to their component class attributes. A common pattern is to list active classes ordered for display:

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 resolve a specific class by the code users search on:

SELECT *
FROM   apps.gmf_cost_cmpnt_class_sla_v
WHERE  cost_cmpntcls_code = :p_code
AND    cost_cmpntcls_id > 0;

To identify product-costed classes with PPV enabled:

SELECT cost_cmpntcls_code, cost_cmpntcls_desc
FROM   apps.gmf_cost_cmpnt_class_sla_v
WHERE  product_cost_ind = 1
AND    ppv_ind = 1
AND    cost_cmpntcls_id > 0;

When joining transactional data, the placeholder row (ID 0) allows an outer join to succeed even when no class is assigned, avoiding dropped rows in reports. Because the object is APPS-owned and largely read-only in nature, it is safe for custom concurrent programs, BI Publisher data templates, and ad hoc queries without affecting base OPM data.