Search Results date_created




Overview

The view CSS_DEF_ENH_UWQ_V belongs to the CSS – Support product family, a module that Oracle has since designated obsolete in the EBS 12.1.1 and 12.2.2 release streams. Its name reflects its purpose: an "enhanced" defect view (CSS_DEF_ENH) surfaced for the Universal Work Queue (UWQ), the framework that routes and displays work items for agent-facing applications. The view consolidates a defect record together with the descriptive attributes an agent needs at a glance, and adds the routing metadata columns (IEU_OBJECT_FUNCTION, IEU_OBJECT_PARAMETERS, IEU_PARAM_PK_COL, IEU_PARAM_PK_VALUE) that the interaction/telephony and work-queue infrastructure requires to launch the correct object from a queued row.

Because defects in CSS are stored with numeric foreign keys to phases, problem types, severities, priorities, and statuses, plus inventory item identifiers for the product, component, and sub-component, the view performs all of the required joins and API calls so that consumers receive human-readable values. It is therefore a reporting and integration surface rather than a transactional one; no DML is expected against it. The ETRM record notes that the view is not implemented in the current database, confirming its obsolete status in the shipped 12.2.2 environment.

Underlying Base Objects

The view is defined over a set of CSS lookup and transaction tables joined to shared EBS master data. The documented sources are:

In addition, the view calls three functions in the CSS_DEF_MTL_API package — GET_REVISION_DESCRIPTION, GET_ITEM_DESCRIPTION, and GET_ITEM_CONCAT_SEGMENTS — to resolve product revision, component, and sub-component descriptions on the fly, and uses GET_INV_ORGANIZATION_ID as a bind in the join to MTL_SYSTEM_ITEMS_VL.

Key Columns

The column most relevant to the searched term product_number is derived from PROD.CONCATENATED_SEGMENTS. It presents the full concatenated inventory segment string for the defective product, and pairs with PRODUCT_DESCRIPTION and PRODUCT_VERSION (the revision description) to fully identify what failed. The defect itself is identified by DEFECT_ID and DEFECT_NUMBER.

Structural attributes include COMPONENT_NUMBER, COMPONENT_DESCRIPTION, SUB_COMPONENT_NUMBER, and SUB_COMP_DESCRIPTION, each resolved through the MTL API. Classification is provided by PHASE_NAME, STATUS_NAME, PROBLEM_TYPE_NAME, PRIORITY_NAME, and SEVERITY_NAME. Customer context comes from CUSTOMER_NAME, CUSTOMER_NUMBER, and CUSTOMER_TYPE. Audit columns include DATE_CREATED (FILED_DATE) and LAST_UPDATED (UPDATED_DATE), while ownership is tracked through RESOURCE_ID and RESOURCE_TYPE. The IEU_* columns carry the work-queue routing payload.

Common Use Cases and Queries

Typical uses include agent work-queue listings, defect aging reports, and customer-impact analysis filtered by product. A representative query is:

  • SELECT defect_number, product_number, product_description, severity_name, status_name, customer_name FROM css_def_enh_uwq_v WHERE product_number LIKE :item_prefix ORDER BY last_updated DESC;
  • Aggregating open defects by product and severity for quality dashboards.
  • Feeding the Universal Work Queue by selecting the defect ID and IEU parameter columns for a given resource.

Because the module is obsolete and the view is undocumented in the 12.2.2 base objects list, consumers should treat it as unsupported and migrate to the current defect reporting views where available.