Search Results actual_resolution

Overview

The view CSS_DEF_DEF_UWQ_V is a denormalized defect reporting view within the Oracle E-Business Suite (EBS) CSS – Support module. It is documented in ETRM metadata for both 12.1.1 and 12.2.2 as belonging to the CSS – Support product, which is flagged as obsolete. The view is not implemented in the reference database from which the metadata was extracted, meaning the definition is published for documentation purposes but the object may be absent from certain environments. Functionally, the view consolidates defect header data with resolved lookup names for severity, priority, status, phase, and problem type, and joins to item and party master data to surface readable product, component, sub-component, platform, and customer identifiers. In practice it serves as a flattened reporting layer for defect records, exposing the "sub_component_number" attribute that users search for as a first-class column rather than requiring joins through inventory item tables.

Underlying Base Objects

The view text references the following base objects:

• CSS_DEF_DEFECTS_VL – the source of defect header records (alias DEF), supplying defect identifiers, summary, dates, and foreign keys including SUB_COMPONENT_INV_ITEM_ID.
• CSS_DEF_PHASES_VL, CSS_DEF_PROB_TYPES_VL, CSS_DEF_SEVERITIES_VL, CSS_DEF_PRIORITIES_VL, CSS_DEF_STATUSES_VL – lookup views supplying the human-readable phase, problem type, severity, priority, and status names.
• MTL_SYSTEM_ITEMS_VL (alias PROD) – source for the product's concatenated segments and description.
• HZ_PARTIES (alias HZ) – customer party name and number.
• CSS_LOOKUPS (alias LK) – customer type meaning.
• JTF_OBJECTS_B (alias O) – IEU object function and parameter metadata for integration menus.

Although the metadata records no explicitly documented referenced base objects, the view text confirms these relationships. Component, sub-component, and platform item identifiers are resolved through API calls rather than direct table joins.

Key Columns

• SUB_COMPONENT_NUMBER / SUB_COMP_DESCRIPTION – concatenated item segments and description for the sub-component, resolved via CSS_DEF_MTL_API.GET_ITEM_CONCAT_SEGMENTS and GET_ITEM_DESCRIPTION on SUB_COMPONENT_INV_ITEM_ID. This is the column the user's search targets.
• COMPONENT_NUMBER / COMPONENT_DESCRIPTION – equivalent attributes for the component level.
• PRODUCT_NUMBER / PRODUCT_DESCRIPTION / PRODUCT_VERSION – product segment, description, and revision description.
• PLATFORM_NUMBER / PLATFORM_DESCRIPTION – platform inventory item identifiers.
• SEVERITY_NAME, PRIORITY_NAME, PHASE_NAME, STATUS_NAME, PROBLEM_TYPE_NAME – decoded lookup values.
• DEFECT_ID / DEFECT_NUMBER – primary defect key and user-facing number.
• SUMMARY – defect summary text.
• CUSTOMER_NAME / CUSTOMER_NUMBER / CUSTOMER_TYPE – party and lookup-derived customer attributes.
• DATE_CREATED, LAST_UPDATED, ESTIMATED_RESOLUTION, ACTUAL_RESOLUTION, ESTIMATED_CLOSURE – lifecycle dates.
• IEU_OBJECT_FUNCTION, IEU_OBJECT_PARAMETERS, IEU_PARAM_PK_COL, IEU_PARAM_PK_VALUE – integration metadata driving the IEU (Interaction) framework. IEU_PARAM_PK_VALUE is TO_CHAR(DEFECT_ID).

Common Use Cases and Queries

A typical reporting query retrieves defects associated with a particular sub-component:

• SELECT defect_number, sub_component_number, component_number, customer_name, status_name FROM css_def_def_uwq_v WHERE sub_component_number = :item;
• SELECT defect_number, product_number, severity_name, priority_name, date_created FROM css_def_def_uwq_v WHERE customer_number = :cust;
• SELECT status_name, COUNT(*) FROM css_def_def_uwq_v GROUP BY status_name;

Because the view performs the item and customer resolution itself, it is suited to operational defect dashboards, quality analytics, and feedback integration into the IEU framework. Users should confirm object existence in their environment, as the metadata states it is not implemented in the reference database and CSS – Support is marked obsolete.