Search Results customs_class




Overview

APPS.IC_CTMS_CLS_VW is a compatibility view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model that exposes material classification data specifically filtered to the customs class category set. It presents a normalized projection of category information so that downstream Oracle Process Manufacturing (OPM) and ETRM (Enterprise Trade and Regulatory Management) components can consume customs classification records through a single, stable interface. The view is owned by the APPS schema and is typically queried by reporting layers, integrations, and API validation routines that must resolve a customs class code to its underlying category identifier, description, and descriptive flexfield attributes.

The "IC_CTMS" prefix indicates its association with Inventory and Customs/Compliance classification structures. Because customs classification data in EBS is stored within the generic category framework rather than a dedicated table, this view acts as a semantic filter, mapping the OPM-specific GMI_CATEGORY_SETS.OPM_CLASS value of CUSTOMS_CLASS onto the shared MTL category model.

Underlying Base Objects

The documented metadata lists four referenced objects: GMI_CATEGORY_SETS (SYNONYM), MTL_CATEGORIES_V (VIEW), MTL_CATEGORY_SETS (SYNONYM), and MTL_CATEGORY_SET_VALID_CATS (SYNONYM). The view is defined as a UNION of two branches that differ only in how validity is enforced.

  • GMI_CATEGORY_SETS — provides the OPM class definition; the filter ocs.OPM_CLASS = 'CUSTOMS_CLASS' restricts rows to the customs class category set.
  • MTL_CATEGORY_SETS — supplies the STRUCTURE_ID that links the OPM category set to the base category structure.
  • MTL_CATEGORIES_V — the primary source of category concatenated segments, category ID, description, audit columns, and the ATTRIBUTE1 through ATTRIBUTE15 flexfield columns.
  • MTL_CATEGORY_SET_VALID_CATS — used in the second UNION branch to include categories that are explicitly listed as valid members of a validated category set (where validate_flag = 'Y').

The join path across both branches is ocs.CATEGORY_SET_ID = cs.CATEGORY_SET_ID and cs.STRUCTURE_ID = c.STRUCTURE_ID. The first branch additionally filters cs.validate_flag <> 'Y' and constrains the concatenated segment to its uppercase eight-character prefix.

Key Columns

Common Use Cases and Queries

Typical usage includes resolving a customs class code during trade compliance validation, populating LOVs in customs documentation, and extracting categories for interface staging tables.

  • Lookup a customs class by code: SELECT category_id, description FROM apps.ic_ctms_cls_vw WHERE category_concat_segs = 'XXXX';
  • List all active customs classes: SELECT category_concat_segs, description FROM apps.ic_ctms_cls_vw WHERE disable_flag = 0 ORDER BY category_concat_segs;
  • Extract flexfield attributes for integration: SELECT category_id, attribute1, attribute_category FROM apps.ic_ctms_cls_vw;

Because the view performs a UNION and applies uppercase filtering on the concatenated segments, queries should supply uppercase literal values and account for the eight-character truncation when matching customs class codes.