Results for “cs_inst_detail_contacts_v”

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

Overview

CS_INST_DETAIL_CONTACTS_V is a reporting and integration view in the Oracle E-Business Suite Service (CS) module, owned by the APPS schema and marked VALID in the ETRM repository for releases 12.1.1 and 12.2.2. The view exposes the contact information associated with Installation Details records, which represent the installed-base assets and configurations tracked against a customer's products or services. Its purpose is to present a filtered, denormalized projection of service contacts so that downstream reporting, concurrent programs, and external integrations can retrieve the parties linked to a specific installation detail without navigating the full range of contact relationships held in the base table.

Because the view applies internal filtering logic at the database level, consumers are shielded from rows that are irrelevant to installation detail reporting—specifically contacts flagged as service providers and contacts whose source object is not INST_DETAIL. This makes it a stable, purpose-built access point for installed-base contact enquiries.

Underlying Base Objects

The view is defined over a single documented base object: the CS_CONTACTS table, referenced through an APPS synonym. CS_CONTACTS stores the association between service objects in the CS schema and contact parties (typically HZ_PARTIES / HZ_ORG_CONTACTS records identified by CONTACT_ID), along with the type, category, and source object of each association.

The view is not a simple pass-through: it embeds two predicates in its defining query. First, it restricts to rows where NVL(SVC_PROVIDER_FLAG, 'N') = 'N', excluding contacts designated as service providers, with NULLs treated as non-providers. Second, it restricts to SOURCE_OBJECT_CODE = 'INST_DETAIL', so only contact links that originate from an installation detail record are returned. The view also renames SOURCE_OBJECT_ID to LINE_INST_DETAIL_ID via a column alias, aligning the key with the installation detail line identifier used elsewhere in the CS data model.

Key Columns

• CS_CONTACT_ID — The primary key of the underlying CS_CONTACTS row; uniquely identifies the contact association within the CS schema.
• CONTACT_ID — The identifier of the contact party itself, joining to the trading community (HZ) contact tables to resolve name, phone, and email.
• CONTACT_TYPE — Classifies the contact in the context of the service object, distinguishing the role the party plays. Users searching for "cs_contact_id" frequently need this column alongside CONTACT_ID to disambiguate CS contact rows from HZ contact rows.
• LINE_INST_DETAIL_ID — The aliased SOURCE_OBJECT_ID, identifying the installation detail line to which the contact is attached. This is the join key back to the installation details entity.
• OBJECT_VERSION_NUMBER — The optimistic locking / concurrency version token, preserved for consistency with the base record.
• CONTACT_CATEGORY — Categorises the contact association, providing a further classification dimension for reporting.

Common Use Cases and Queries

Typical scenarios include listing the contacts attached to a given installation detail, resolving contact names for an installed-base report, and feeding service or field-service integrations with the correct contact for a specific asset.

To retrieve all contacts for a known installation detail line:

• SELECT cs_contact_id, contact_id, contact_type, contact_category FROM cs_inst_detail_contacts_v WHERE line_inst_detail_id = :p_inst_detail_id;

To resolve contact party details for an installation detail by joining to the trading community tables:

• SELECT v.line_inst_detail_id, v.cs_contact_id, v.contact_id, v.contact_type FROM cs_inst_detail_contacts_v v WHERE v.contact_id = :p_contact_id;

Because the view exposes CS_CONTACT_ID and CONTACT_ID, queries that search on "cs_contact_id" should use the CS_CONTACT_ID column to reference the CS association row, reserving CONTACT_ID for joins to HZ contact data. The view is read-only by construction; DML must be performed against CS_CONTACTS directly, respecting the same SVC_PROVIDER_FLAG and SOURCE_OBJECT_CODE predicates.