Results for “css_def_def_contacts”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CSS_DEF_DEF_CONTACTS is a Support module table within Oracle E-Business Suite (documented across 12.1.1 and 12.2.2), belonging to the legacy CSS – Support product area, which is now marked obsolete. The table models the many-to-many association between defect or enhancement records and the contacts (resources, groups, or teams) responsible for or associated with them. As stated in the object definition, a defect or enhancement may have multiple contacts, but must always retain exactly one primary contact. This constraint makes CSS_DEF_DEF_CONTACTS an assignment or resolution-link object rather than an independent entity.
Based on the heuristic Data Vault classification mined from the foreign key structure, CSS_DEF_DEF_CONTACTS is best modeled as a link table. It carries no descriptive attributes of its own beyond role and priority indicators; instead, it connects a defect hub (via DEFECT_ID) to resource, group, or team hubs (via OBJECT_ID). Analysts designing a Data Vault or dimensional representation should treat DEF_CONTACT_ID purely as a surrogate row identifier for the link, not as a business key.
Key Information Stored
The table's documented structure centers on the following significant columns:
- DEF_CONTACT_ID – the surrogate primary key, uniquely identifying each occurrence of the table. It is enforced by the CSS_DEF_DEF_CONTACTS_PK constraint and is the column most commonly sought when users search for "def_contact_id".
- DEFECT_ID – the foreign key to CSS_DEF_DEFECTS_B, identifying the defect or enhancement to which the contact row belongs. Together with the contact reference, this forms the principal business-key candidate for the association.
- OBJECT_ID – a polymorphic foreign key resolving to one of three JTF resource entities: JTF_RS_RESOURCE_EXTNS (individual resources), JTF_RS_GROUPS_B (resource groups), or JTF_RS_TEAMS_B (resource teams). The referenced table implied by the row determines the contact type.
Additional supporting columns govern the role of the contact and flag the single mandatory primary contact per defect, but the three columns above constitute the essential data footprint documented in the ETRM metadata.
Common Use Cases and Queries
The primary operational use is resolving "who is associated with this defect," and the inverse "which defects does this person or team support." A representative query joining the defects base table to the contact assignments is:
SELECT c.def_contact_id, c.defect_id, c.object_id FROM css_def_def_contacts c WHERE c.defect_id = :p_defect_id;
To identify the primary contact, filter on the primary flag alongside the defect identifier. Reporting use cases include building a defect-to-owner matrix for support dashboards, auditing defects that carry more than one contact, and verifying that every defect row satisfies the mandatory single-primary-contact rule. Because the product is obsolete, such queries are typically historical in nature, executed against archived or pre-upgrade data sets.
Related Objects
The following objects are most tightly coupled to CSS_DEF_DEF_CONTACTS through its documented foreign keys:
- CSS_DEF_DEFECTS_B – joined on CSS_DEF_DEF_CONTACTS.DEFECT_ID = CSS_DEF_DEFECTS_B.DEFECT_ID; the parent entity for every contact row.
- JTF_RS_RESOURCE_EXTNS – joined on OBJECT_ID when the contact is an individual resource.
- JTF_RS_GROUPS_B – joined on OBJECT_ID when the contact is a resource group.
- JTF_RS_TEAMS_B – joined on OBJECT_ID when the contact is a resource team.
Because OBJECT_ID serves three foreign keys, any join must be resolved by the intended contact type, and the descriptive attributes of each contact reside in the corresponding JTF_RS tables rather than in CSS_DEF_DEF_CONTACTS itself. No database implementation exists in this instance, so these relationships are documented for reference rather than for live querying.
-
Table: CSS_DEF_DEF_CONTACTS 12.2.2
A Defect or an Enhancement may have multiple contacts associated with it. A defect or enhancement must always have one primary contact.
Not implemented in this database·Explore CSS module →
-
Table: CSS_DEF_DEF_CONTACTS 12.1.1
A Defect or an Enhancement may have multiple contacts associated with it. A defect or enhancement must always have one primary contact.
Not implemented in this database·Explore CSS module →
-
Table: CSS_DEF_DEFECTS_B 12.2.2
Not implemented in this database·Explore CSS module →
-
Table: CSS_DEF_DEFECTS_B 12.1.1
Not implemented in this database·Explore CSS module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
View: CSS_DEF_DEF_CONTACTS_V 12.1.1
Defect contacts
Not implemented in this database·Explore CSS module →
-
View: CSS_DEF_DEF_CONTACTS_V 12.2.2
Defect contacts
Not implemented in this database·Explore CSS module →