Search Results comp_rev

Overview

The view CSS_BRM_3D_DEFECT_V is a denormalized reporting object belonging to the CSS – Support product family, which is classified as obsolete within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to present "3D defect" data as consumed by the Business Rule Monitor (BRM) diagnostic framework. In practical terms, the view flattens defect header attributes together with their associated lookup descriptions — problem category, problem type, phase, status, severity, and priority — along with product, revision, and component hierarchy details, so that the Business Rule Monitor can evaluate defect records against rule conditions without repeatedly joining the underlying lookup and inventory tables.

Because CSS – Support is marked obsolete and the object is documented as "Not implemented in this database," the view should be regarded primarily as a historical or diagnostic artifact. It remains relevant for understanding BRM rule evaluation logic, for tracing legacy support schemas, and for interpreting extracted defect snapshots in pre-upgrade environments.

Underlying Base Objects

The ETRM metadata lists no documented referenced base objects; however, the embedded view text reveals the operative tables. The core defect table is aliased DEA (a defect entity carrying DEFECT_ID, DEFECT_NUMBER, TERRITORY_ID, and foreign keys to category, type, phase, status, severity, and priority). A derived audit aggregate aliased AUD supplies MAX_AUDIT_HISTORY_ID, which is compared to DEA.AUDIT_HISTORY_ID to classify each row. Lookup tables aliased PCA, PTY, PHA, STA, SEV, and PRI provide the descriptive names for each coded attribute. Product and revision context is sourced from an inventory organization table (PROD) and revision tables (PROD_REV, FFI_REV, COMP_REV), while component and sub-component items are drawn from aliases COMP and SCOM. Since the base objects are undocumented, join semantics must be inferred from the view text itself.

Key Columns

• RECORD_STATUS – DECODE over the audit aggregate, yielding PRESENT for the current audit history row and HISTORIC otherwise.
• OBJECT_TYPE – Literal 'CSS_BRM_3D_DEFECT_V', useful when unioning multiple BRM source views.
• OBJECT_ID / DEFECT_ID / DEFECT_NUMBER – Defect identifiers.
• PROBLEM_CATEGORY_ID and PROBLEM_CATEGORY_NAME – The category code and its decoded description; the latter is the specific column targeted by the search term problem_category_name.
• PROBLEM_TYPE_ID / PROBLEM_TYPE_NAME, PHASE_NAME, STATUS_NAME, SEVERITY_NAME, PRIORITY_NAME – Decoded defect classification attributes.
• INV_ORGANIZATION_ID, PRODUCT_INV_ITEM_ID, PRODUCT_DESCRIPTION, PRODUCT_REVISION, PRODUCT_REVISION_DESC – Product and revision context.
• FIRST_FOUND_IN_*, COMPONENT_*, and SUB_COMP_* columns – First-found, component, and sub-component identifiers, descriptions, and revision descriptions.
• RESOLUTION_CODE / RESOLUTION_MEANING – Hard-coded NULL in this view.

Common Use Cases and Queries

The typical use case is supporting Business Rule Monitor diagnostics and defect trend reporting. A straightforward filter on the decoded category name, matching the user's search, might read:

• SELECT defect_number, problem_category_name, problem_type_name, status_name, severity_name FROM css_brm_3d_defect_v WHERE problem_category_name = '&category';
• Historic versus present analysis: SELECT record_status, COUNT(*) FROM css_brm_3d_defect_v GROUP BY record_status;
• Component attribution: SELECT component_description, COUNT(*) FROM css_brm_3d_defect_v GROUP BY component_description;

Given the obsolete status and absent implementation, these queries are best applied to archived or extracted datasets rather than a live 12.2.2 instance.