Search Results notification_condition_meaning

Overview

CSS_DEF_DEF_CONTACTS_V is a reporting view in the Oracle E-Business Suite CSS (Support) product family. As reflected in the ETRM metadata, CSS is designated an obsolete module in Oracle EBS 12.1.1 and 12.2.2, meaning it is retained for backward compatibility rather than active functional use. The view exposes defect contact records — the associations between defect records and the individuals or resources notified about them. Its business purpose is to resolve the technical foreign keys and lookup codes stored on the defect contact entity into human-readable values for reporting and integration.

The view performs substantial denormalization. Rather than returning raw IDs and codes, it derives an object name, lookup meanings for the primary flag, notification method, and notification condition, and, for resource-based contacts, the corresponding e-mail address and telephone number. It also joins upward to CSS_DEF_DEFECTS_B to surface the defect number. This makes the view suitable for defect notification auditing, contact rosters, and downstream integrations that require display-ready contact data.

Underlying Base Objects

Two base objects are joined in the view text. The driving table is CSS_DEF_DEF_CONTACTS, aliased DCO, which stores one row per defect contact with its identifiers, object references, notification attributes, and descriptive flexfield columns. The second is CSS_DEF_DEFECTS_B, aliased DEF, which supplies the defect header. The join condition is DCO.DEFECT_ID = DEF.DEFECT_ID, so every returned row corresponds to a contact whose parent defect exists in the defect base table.

The view also invokes several CSS PL/SQL utilities at query time: CSS_DEF_ADV_SEARCH_PVT.GET_OBJECT_NAME, CSS_DEF_UTIL_PVT.GET_LOOKUP_MEANING (called three times, for the YES_NO, CSS_DEF_NOTIFICATION_METHOD, and CSS_DEF_NOTIFICATION_CONDITION lookups), CSS_DEF_RESOURCE_UTIL_PVT.GET_RESOURCE_EMAIL, and CSS_DEF_RESOURCE_UTIL_PVT.GET_RESOURCE_PHONE. These functions translate stored codes into meanings and contact details.

Key Columns

• DEF_CONTACT_ID — Primary identifier of the defect contact row.
• DEFECT_ID / DEFECT_NUMBER — Foreign key to the defect and its business-facing number from CSS_DEF_DEFECTS_B.
• OBJECT_ID / OBJECT_CODE — Polymorphic reference to the contact party (for example, a resource identified by an RS_ code prefix).
• OBJECT_NAME — Resolved display name of the contact, via GET_OBJECT_NAME.
• PRIMARY_FLAG / PRIMARY_MEANING — Indicates whether the contact is the primary notification recipient, with the YES_NO meaning resolved.
• NOTIFICATION_METHOD_CODE / NOTIFICATION_METHOD_MEANING — How the contact is notified, looked up against CSS_DEF_NOTIFICATION_METHOD.
• NOTIFICATION_CONDITION_CODE / NOTIFICATION_CONDITION_MEANING — The condition under which the contact is notified, looked up against CSS_DEF_NOTIFICATION_CONDITION. This is the column most frequently referenced by users searching on notification_condition_code.
• EMAIL / PHONE — Resolved from the resource utilities when the object code begins with RS_; otherwise NULL.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — Descriptive flexfield segments.
• OBJECT_VERSION_NUMBER — Optimistic locking version for the row.

Common Use Cases and Queries

Typical reporting scenarios include listing all contacts for a defect, identifying primary recipients, and filtering by notification condition. The following query returns contacts whose notification condition code matches a given value:

SELECT defect_number, object_name, notification_method_meaning, notification_condition_meaning, email, phone FROM css_def_def_contacts_v WHERE notification_condition_code = :condition_code;

To report the primary contact for each defect:

SELECT defect_number, object_name, notification_method_meaning FROM css_def_def_contacts_v WHERE primary_flag = 'Y' ORDER BY defect_number;

Because CSS is obsolete in 12.1.1 and 12.2.2, use of this view should be limited to legacy reporting or data migration. The ETRM metadata records no owner or documented referenced base objects beyond those in the view text, and the view is noted as not implemented in the database instance referenced by that metadata. Deployments should verify the view's presence and the availability of the CSS_DEF_UTIL_PVT, CSS_DEF_ADV_SEARCH_PVT, and CSS_DEF_RESOURCE_UTIL_PVT APIs before relying on it, since query-time function calls introduce runtime overhead and failure points.