Search Results cs_sr_contacts_ext

Overview

CS_SR_CONTACTS_EXT is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores Party Role Extensible Attribute records. In the EBS data model, the Service Request (SR) framework links contacts and parties to service incidents through a related-contacts structure; the _EXT suffix in this case denotes a storage location for extensible attribute data associated with that party role, allowing customer-specific or additional descriptive attributes to be captured alongside the base contact relationship.

The ETRM metadata records that this table is not implemented in the referenced database and carries a primary key constraint, CS_SR_CONTACTS_EXT_PK, defined on the EXTENSION_ID column. A single foreign key relationship is documented: INCIDENT_ID references CS_INCIDENTS_ALL_B, tying each extensible attribute record back to a service incident. The heuristic Data Vault classification derived from the foreign-key structure is satellite-leaning. Interpreted as a modeling suggestion, this indicates the table behaves less like an independent business entity (hub) and more like a dependent set of descriptive attributes attached to a parent transaction — consistent with its role as an extension store hanging off the incident and contact relationship.

Key Information Stored

The documented metadata identifies a limited set of columns, and the description emphasizes extensible attribute storage rather than a fixed business schema. The columns that can be named from the supplied metadata are:

• EXTENSION_ID — the surrogate primary key column; uniquely identified by the CS_SR_CONTACTS_EXT_PK constraint. As the sole documented primary key component, it is the join and lookup anchor for individual extension records.
• INCIDENT_ID — the foreign key column referencing CS_INCIDENTS_ALL_B; this is the principal business-key candidate linking an extension row to its owning service incident.

Because the table is described as storing "Party Role Extensible Attribute records," the remaining columns are expected to hold attribute-name/attribute-value pairs and the party-role context (the contact or party role to which the attributes apply), but these are not enumerated in the documented metadata. The extension design implies the physical column set is script-driven and may vary by implementation. No additional unique indexes beyond the primary key are documented.

Common Use Cases and Queries

The primary practical role of CS_SR_CONTACTS_EXT is to surface extended attributes recorded against a contact role on a service request. Typical scenarios include retrieving custom attributes for a specific incident, validating that extension data exists before downstream processing, and reporting on extended fields captured at service-request entry.

A common retrieval pattern joins the extension table to the base incident table on INCIDENT_ID:

• SELECT c.extension_id, c.incident_id, ... FROM cs_sr_contacts_ext c WHERE c.incident_id = :incident_id;
• SELECT i.incident_number, c.* FROM cs_sr_contacts_ext c JOIN cs_incidents_all_b i ON i.incident_id = c.incident_id WHERE i.incident_number = :sr_number;
• Existence check: SELECT COUNT(*) FROM cs_sr_contacts_ext WHERE incident_id = :incident_id;

Reporting use cases include extracting custom contact attributes per service request, auditing extension data completeness, and feeding extended SR contact information into downstream integrations. Because the table is not implemented in the reference database, queries should be validated against the target instance before deployment.

Related Objects

The following objects are the most significant to consider in relation to CS_SR_CONTACTS_EXT, based on the documented foreign-key relationship and the surrounding Service Request data model:

• CS_INCIDENTS_ALL_B — the parent base table for service incidents; joined on CS_SR_CONTACTS_EXT.INCIDENT_ID = CS_INCIDENTS_ALL_B.INCIDENT_ID. This is the documented foreign-key relationship and the principal parent object.
• CS_INCIDENTS_ALL_TL — the translation table for incident descriptive fields, commonly joined to CS_INCIDENTS_ALL_B for reporting.
• CS_SR_CONTACTS — the base party-role contact table for service requests, of which the extension table is the attribute counterpart.
• CS_INCIDENT_CONTACTS (where present in a given release) — related contact linkage for incidents, complementing the extension data.
• HZ_PARTIES / HZ_PARTY_SITES — Trading Community Architecture party entities that resolve the party role referenced by the extension record.
• JTF_RS_RESOURCE_EXTNS — a comparable extension table pattern illustrating how EBS stores extensible resource attributes, useful as a design reference.
• Service Request public APIs (for example, the CS Service Request API) — used to create and maintain incident and contact data that the extension table supplements.

Consumers should treat CS_SR_CONTACTS_EXT as a satellite of the service-incident parent, joining exclusively through INCIDENT_ID unless the implementation defines additional business keys.