Search Results commitment_meaning

Overview

CSS_DEF_DEFECTS_ALL_NO_RES_V is a legacy Oracle EBS support (CSS) view that exposes defect records from the support schema with all resource-related attributes deliberately omitted. The view is catalogued in ETRM under the CSS – Support product, which is flagged as obsolete, and its implementation status is recorded as "Not implemented in this database" for the documented release. The view name encodes its purpose plainly: it returns defect information from the DEFECTS_ALL family while suppressing resource assignment data, producing a narrower projection suitable for reporting scenarios in which resource attribution is irrelevant or restricted.

The view was introduced in the Oracle 11.5.x support applications and was superseded as the support data model evolved through 11.5.4 and later. Columns such as ORG_ID carry explicit comments marking them as obsoleted at 11.5.4, while REASON_ID, REASON_NAME, STATUS_REASON_ID, and DESC_STATUS_REASON are annotated as obsoleted at 11.5.3 and above. These annotations confirm that the view is a backward-compatibility construct retained to preserve dependent reports and interfaces. In Oracle EBS 12.1.1 and 12.2.2 environments, the view designation "ALL" indicates an org-stripped projection, meaning multi-org security predicates are not applied; callers must impose their own organizational filtering. Because the underlying support schema is obsolete, the view is typically absent or non-functional in current 12.2.2 instances, but it remains relevant to migration and code-remediation analysis.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, so the definitive source of lineage is the view text itself. The FROM and join clauses reference the defect entity DEF (the CSS defect/change record), joined to territory (TER), problem category (PCA), problem type (PTY), phase (PHA), and problem-type-phase (PTP) lookup tables, along with status (STA), severity (SEV), and priority (PRI) lookups. Product context is supplied through the inventory product and revision tables (aliased PROD and PROD_REV). Resource tables present in the full DEFECTS_ALL view are absent by design here, which is the defining characteristic separating this projection from its companion views.

The view also calls the helper function CSS_DEF_UTIL_PVT.GET_LOOKUP_MEANING to resolve the YES_NO lookup meaning for the open flag. This dependency means the view cannot be compiled or queried unless the CSS_DEF_UTIL_PVT package specification and body are valid in the calling schema. Because ETRM records no base objects, any dependency audit should be performed against ALL_DEPENDENCIES and DBA_VIEWS rather than relying on the documented metadata.

Key Columns

The exposed column list is broad and mirrors the defect record plus its denormalised descriptive lookups. Principal columns include:

• DEFECT_ID and OBJECT_VERSION_NUMBER — primary identifier and optimistic locking token for each defect.
• DEFECT_NUMBER — the user-facing defect reference.
• ORG_ID — always returns NULL via TO_NUMBER(NULL); retained only for interface compatibility and marked obsolete at 11.5.4.
• TERRITORY_ID and TERRITORY_NAME — territory classification of the defect.
• CATEGORY_TYPE, PROBLEM_CATEGORY_ID/NAME, PROBLEM_TYPE_ID/NAME, PHASE_ID/NAME, and PROBLEM_TYPE_PHASE_ID — the categorisation hierarchy used to route and analyse defects.
• STATUS_ID/STATUS_NAME, OPEN_FLAG, and OPEN_MEANING — defect lifecycle state; the meaning is resolved through the YES_NO lookup.
• SEVERITY_ID/NAME and PRIORITY_ID/NAME — impact and scheduling attributes.
• INV_ORGANIZATION_ID, PRODUCT_INV_ITEM_ID, PRODUCT_DESCRIPTION, PRODUCT_CONC_SEGMENTS, PRODUCT_REVISION, and PRODUCT_REVISION_DESC — the affected product and revision, with revision description resolution.
• FIRST_FOUND_IN_* columns — the product and revision in which the defect was first observed, resolved conditionally from either the revision or the free-text description.

Notably absent are all resource identifiers, resource names, and assignment attributes, which is the view's distinguishing feature relative to the standard defect views.

Common Use Cases and Queries

Because the view omits resource data, it is most useful for defect metrics, product quality reporting, and integration extracts that must not disclose resource assignment. A representative query enumerates open defects by severity and product:

• SELECT defect_number, STATUS_NAME, SEVERITY_NAME, PRODUCT_CONC_SEGMENTS, TERRITORY_NAME FROM CSS_DEF_DEFECTS_ALL_NO_RES_V WHERE OPEN_FLAG = 'Y' ORDER BY SEVERITY_NAME, DEFECT_NUMBER;
• Trend analysis by problem category: SELECT PROBLEM_CATEGORY_NAME, COUNT(*) FROM CSS_DEF_DEFECTS_ALL_NO_RES_V GROUP BY PROBLEM_CATEGORY_NAME;
• Revision-level first-found analysis: SELECT FIRST_FOUND_IN_CONC_SEGMENTS, FIRST_FOUND_IN_REVISION, COUNT(*) FROM CSS_DEF_DEFECTS_ALL_NO_RES_V GROUP BY FIRST_FOUND_IN_CONC_SEGMENTS, FIRST_FOUND_IN_REVISION;

Given the obsolete status and the "not implemented" ETRM notation, these queries should be validated against the target database before use; where the view is unavailable, equivalent projections must be built from the current support tables or from the surviving companion defect views.