Search Results ic_ctms_cls_vw




Overview
Explore in AI Chat

Overview

IC_CTMS_CLS_VW is a read-only database view owned by the APPS schema in Oracle E-Business Suite, classified under the GMI — Process Manufacturing Inventory product family. Its documented purpose is to provide backward compatibility for customs classes, meaning it preserves a legacy interface for objects that historically consumed customs class definitions. In this context a "customs class" is a classification used by process manufacturing organizations to group inventory items for customs, excise, or regulatory reporting purposes. The view allows older forms, reports, concurrent programs, or integration interfaces that referenced the original customs class construct to continue functioning after the product migrated its class definitions into the Oracle Inventory category model.

From a reporting and integration standpoint, the view behaves as a compatibility shim. Rather than maintaining customs class data in a dedicated legacy table, the view derives its rows by reading Oracle Inventory category structures and filtering them to those category sets flagged as customs classes. This ensures a single source of truth while shielding dependent code from the underlying schema changes. Because it is a view and not a table, it exposes no DML capabilities; consumers can only select from it.

Underlying Base Objects

According to the documented view metadata, IC_CTMS_CLS_VW is defined over the following referenced base objects:

  • MTL_CATEGORIES_V (VIEW) — the primary source of category rows, supplying concatenated segments, descriptions, identifiers, audit columns, and descriptive flexfield attributes.
  • MTL_CATEGORY_SETS (SYNONYM) — provides the category set definitions, including the structure identifier and validation flag used to join and filter categories.
  • GMI_CATEGORY_SETS (SYNONYM) — the process manufacturing extension that records the OPM class designation; rows where OPM_CLASS equals 'CUSTOMS_CLASS' identify the relevant category sets.
  • MTL_CATEGORY_SET_VALID_CATS (SYNONYM) — the valid category assignments within a category set, referenced in the documented view text to control which categories qualify.

The view text confirms these relationships. It joins MTL_CATEGORIES_V to MTL_CATEGORY_SETS on structure, then to GMI_CATEGORY_SETS on category set identifier, filtering with OCS.OPM_CLASS = 'CUSTOMS_CLASS'. A UNION combines validated and non-validated category rows, distinguished by the CS.VALIDATE_FLAG condition.

Key Columns

The view exposes a fixed set of columns that mirror the historical customs class interface:

  • Customs class code — the first column, derived as the first eight bytes of CATEGORY_CONCAT_SEGS, serving as the short class identifier.
  • CATEGORY_ID — the unique numeric identifier of the underlying category.
  • Class description — the first seventy bytes of the category description.
  • Audit columns — CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
  • Disable indicator — a decoded value (0 or 1) derived from DISABLE_DATE, indicating whether the class is inactive.
  • ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the descriptive flexfield segments carried through from the category record.
  • Placeholder columns — several constants (0) and NULL casts (TO_NUMBER, TO_CHAR) retained solely to satisfy the legacy column layout expected by dependent code.

Common Use Cases and Queries

Typical uses include populating customs class lists in legacy inventory forms, driving customs reporting extracts, and validating item-to-class assignments during data migration. The following query lists active customs classes:

SELECT category_id, description
FROM   apps.ic_ctms_cls_vw
WHERE  disable_flag = 0;

To resolve a specific class by its short code:

SELECT *
FROM   apps.ic_ctms_cls_vw
WHERE  category_concat_segs = 'CUSTOM01';

Because the view is a compatibility artifact, new development should reference the underlying Inventory category tables directly, reserving IC_CTMS_CLS_VW for maintaining existing legacy interfaces.