Results for “link_meaning”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSS_DEF_DEFECT_LINKS_V is a reporting view within the Oracle EBS CSS (Customer Support/Service) module that exposes relationship information among defects. In the EBS data model, defects are not isolated records; they can be linked to one another to express dependency, duplication, blocking, or resolution relationships. The CSS_DEF_DEFECT_LINKS_V view flattens those relationships into a single denormalized result set, resolving the internal foreign key identifiers of both the source and the target defect into their human-readable defect numbers.

The view is documented as part of the CSS – Support module, which Oracle classifies as obsolete in release 12.1.1 and 12.2.2. The ETRM record explicitly notes "Not implemented in this database," meaning the view may not exist in every environment. When present, its role is primarily analytical and integration-oriented: downstream reports, extracts, and interfaces can consume defect-to-defect relationships without having to perform a self-join against the defect base tables. Because the view resolves defect numbers, it is directly usable in end-user diagnostics, quality dashboards, and data migration packages without additional lookup logic.

Underlying Base Objects

The view is defined over two documented base objects: CSS_DEF_DEFECT_LINKS and CSS_DEF_DEFECTS_B. The link table supplies the relationship records (LINK_ID, FROM_ID, TO_ID, LINK_TYPE, the descriptive attributes, and the context/versioning columns), while the defect base table is referenced twice — once as FRM and once as DTO — to resolve the two endpoints of each link into defect numbers.

The join is a straightforward equi-join: LNK.FROM_ID = FRM.DEFECT_ID and LNK.TO_ID = DTO.DEFECT_ID. This means the view returns only links whose both endpoints resolve to existing defect records. A dangling link (one whose FROM_ID or TO_ID does not exist in CSS_DEF_DEFECTS_B) is silently excluded. The ETRM metadata documents no additional referenced base objects, so the view does not touch organization, inventory, or party tables.

Key Columns

• LINK_ID — Primary identifier of the relationship record.
• FROM_ID — Internal defect ID of the source (originating) defect.
• FROM_NUMBER — The defect number of the source defect, aliased from FRM.DEFECT_NUMBER. This is the column returned when the search term "from_number" is used.
• TO_ID — Internal defect ID of the target defect.
• TO_NUMBER — The defect number of the target defect, aliased from DTO.DEFECT_NUMBER.
• LINK_TYPE — The lookup code identifying the relationship category.
• LINK_MEANING — The decoded link type, derived via CSS_DEF_UTIL_PVT.GET_LOOKUP_MEANING for the lookup type CSS_DEF_LINK_TYPE, truncated to 80 characters.
• ATTRIBUTE1 … ATTRIBUTE15 — Descriptor Flexfield (DFF) columns carried from the link record.
• CONTEXT — The DFF context value governing the attribute columns.
• OBJECT_VERSION_NUMBER — Optimistic locking/versioning column from the link table.

Note that the ETRM column listing names FROM_DEFECT_NUMBER and TO_DEFECT_NUMBER, while the underlying SQL aliases the same projections as FROM_NUMBER and TO_NUMBER. This discrepancy reflects how the view's column list is registered versus the aliases written in the view text.

Common Use Cases and Queries

The most common scenario is tracing the relationships surrounding a specific defect. To list every link originating from a given defect number, filtering on the from_number projection:

SELECT from_number, to_number, link_meaning
FROM   css_def_defect_links_v
WHERE  from_number = :defect_number;

To trace inbound relationships — that is, which defects point at a given defect — query the to_number column instead:

SELECT to_number, from_number, link_meaning
FROM   css_def_defect_links_v
WHERE  to_number = :defect_number;

For duplicate-defect analysis, restrict output to the relevant link type using the decoded meaning:

SELECT from_number, to_number
FROM   css_def_defect_links_v
WHERE  link_meaning = 'Duplicate';

Because the view resolves both endpoints, it also serves as a convenient source for graph-style extracts, defect dependency reports, and denormalized feeds into external quality systems. Any query should be preceded by a verification that the view exists in the target environment, given the "Not implemented in this database" note in the ETRM record.