Results for “svc_provider_flag”

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

Overview

CS_CONTACTS is a Service (CS) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the CS schema. Per the ETRM documentation, it stores "Party and employee information related to an entity." In practice, CS_CONTACTS functions as the association table that links a source object — typically a customer product or installed base instance — to a contact record representing a party (customer contact) or an employee (service resource). This enables service organizations to identify who is responsible for, affected by, or assigned to a given serviceable item, and to designate primary, preferred, and service-provider contacts.

The table carries a documented Data Vault classification of satellite-leaning, mined heuristically from its foreign key structure. This suggests that modelers treating CS_CONTACTS as a satellite would attach its descriptive attributes (flags, effective dates, category, and audit columns) to a hub or link centered on CS_CONTACT_ID or the source-object/contact business key, rather than treating the table as an independent hub.

Key Information Stored

The surrogate primary key is CS_CONTACT_ID, enforced by the constraint CS_CONTACTS_PK and mirrored by the unique index CS_CONTACTS_U1. Two composite unique indexes serve as business-key candidates: CS_CONTACTS_U2 covers SOURCE_OBJECT_ID, SOURCE_OBJECT_CODE, CONTACT_ID, and CONTACT_TYPE.

• CS_CONTACT_ID — surrogate primary key uniquely identifying each contact association.
• SOURCE_OBJECT_ID / SOURCE_OBJECT_CODE — identify the entity (installed base instance or customer product) to which the contact is related.
• CONTACT_ID — the referenced party or resource, joining to JTF_RS_RESOURCE_EXTNS.
• CONTACT_TYPE — classifies the contact role in the association.
• PRIMARY_FLAG / PREFERRED_FLAG — designate the primary and preferred contact for the entity.
• SVC_PROVIDER_FLAG — indicates whether the contact acts as a service provider.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective-dating range for the association.
• CONTACT_CATEGORY — categorizes the contact assignment.
• SECURITY_GROUP_ID — supports multi-org/security group access control.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent updates.
• UPGRADED_STATUS_FLAG / MIGRATED_STATUS_FLAG — track data conversion and upgrade state.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY — standard audit columns.

Fifteen ATTRIBUTE columns plus CONTEXT provide the standard Oracle EBS descriptive-flexfield extension area.

Common Use Cases and Queries

Typical uses include identifying the primary contact for an installed base instance, producing service-dispatch contact lists, and reporting on party-versus-employee coverage of serviceable items. A representative query retrieves all active primary contacts for a given source object:

SELECT c.cs_contact_id, c.contact_id, c.contact_type, c.primary_flag
FROM cs.cs_contacts c
WHERE c.source_object_id = :object_id
AND c.primary_flag = 'Y'
AND SYSDATE BETWEEN c.start_date_active AND NVL(c.end_date_active, SYSDATE);

To resolve the contact to a resource record, join to JTF_RS_RESOURCE_EXTNS on CONTACT_ID. Analysts also use CS_CONTACTS_U2 to detect duplicate or conflicting contact assignments for the same object, contact, and type combination, and rely on CONTACT_CATEGORY and SVC_PROVIDER_FLAG for segmentation reporting.

Related Objects

• JTF_RS_RESOURCE_EXTNS — joined via CS_CONTACTS.CONTACT_ID to resolve employee/resource details.
• CS_CUSTOMER_PRODUCTS_ALL — joined via CS_CONTACTS.SOURCE_OBJECT_ID to identify the customer product or installed base instance.
• FND_SECURITY_GROUPS — joined via CS_CONTACTS.SECURITY_GROUP_ID for security-group authorization.
• CS_CP_PARTIES_AUDIT — references CS_CONTACTS.CP_PARTY_ID, providing audit history for contact parties.

These relationships confirm CS_CONTACTS as the junction between serviceable entities and their associated party or resource contacts, with audit and security dependencies extending its footprint across the CS and FND schemas.