Search Results css_def_defects_all_v

Overview

IEU_UWQ_DEFECTS_V is a reporting view in the Oracle E-Business Suite Universal Work Queue (IEU) module. It is documented in ETRM as the view used for the UWQ selector SpreadTable, meaning it supplies the tabular data set that the Universal Work Queue presents to agents when surfacing defect records in a work queue. The view consolidates defect header attributes from the defect tracking tables into a flat, selector-friendly shape, adding UWQ-specific routing and identification columns such as IEU_OBJECT_FUNCTION, IEU_OBJECT_PARAMETERS, IEU_PARAM_PK_COL, IEU_PARAM_PK_VALUE, RESOURCE_ID, and RESOURCE_TYPE. Because it is a view rather than a table, it carries no independent storage and is not implemented as a database object in every environment; the ETRM record notes "Not implemented in this database" for the documented instance.

Underlying Base Objects

The view text defines two reference sources. The primary source is CSS_DEF_DEFECTS_ALL_V, aliased as A, which supplies the defect attributes. The second is JTF_OBJECTS_VL, aliased as O, which supplies the object function and parameter metadata used by Universal Work Queue to identify the underlying object. The join is driven by a constant condition: O.OBJECT_CODE = 'DF', aligning the defect object code with the JTF object registry. The documented ETRM metadata lists no referenced base objects, so the underlying tables must be derived from the view text and the naming conventions of the defect and JTF object models. The view filters rows to open, non-deleted defects using A.OPEN_FLAG = 'O' and NVL(A.DELETED_FLAG, 'N') = 'N'.

Key Columns

• IEU_PARAM_PK_COL — Literal value 'DEFECT_NUMBER', identifying the primary key column name passed to the UWQ framework.
• IEU_PARAM_PK_VALUE — TO_CHAR(A.DEFECT_NUMBER), the character form of the defect number used as the selector key.
• DEFECT_ID — The internal identifier of the defect record.
• SEVERITY_NAME — The severity assigned to the defect, exposed for queue display and filtering.
• STATUS_NAME / PRIORITY_NAME — Status and priority labels for triage.
• RESOURCE_ID / RESOURCE_TYPE — A.PHASE_OWNER_ID with the literal 'RS_INDIVIDUAL', defining the owning resource for routing.
• SUMMARY, PRODUCT_DESCRIPTION, COMPONENT_DESCRIPTION, SUB_COMP_DESCRIPTION — Descriptive defect context.
• FILER_NAME, FILED_DATE — Originator and creation date.
• ESCALATION_LEVEL_CODE, FIX_BY_REVISION_DESC, DEV_OWNER_ID, PHASE_NAME — Escalation and ownership attributes.

Common Use Cases and Queries

Typical usage centers on populating a UWQ selector or building ad hoc defect reports. A severity-based query would filter on SEVERITY_NAME and group by resource.

SELECT defect_id, defect_number, severity_name, status_name, summary
FROM   ieu_uwq_defects_v
WHERE  severity_name = :p_severity
ORDER  BY filed_date DESC;

Because the view already restricts to open, non-deleted defects, it is suitable for agent workload views that join defect severity against the assigned phase owner. Report developers should confirm with the DBA whether the view exists in the target instance, since ETRM documents it as not implemented in the reference database.