Results for “cs_inst_contact_dtls_v”

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

Overview

CS_INST_CONTACT_DTLS_V is an APPS-owned database view in the Oracle E-Business Suite Service (CS) product family. In Oracle EBS 12.1.1 and 12.2.2 it presents the contact details associated with installation detail records, giving report writers and integration developers a denormalized, human-readable picture of who is linked to a given installed asset or installation line. Where the underlying contact association tables store only coded values and numeric identifiers, this view resolves those codes into lookup meanings and joins to the trading community party model to return the contact's name.

The view is a reporting and integration convenience object. It is not a base table and holds no data of its own; every query executes against the underlying installation-contact view and the party and lookup objects. It is most commonly consumed by service reporting, customer self-service inquiries, field service integrations, and any interface that must print or transmit a contact name alongside an installation detail rather than a party ID. The presence of OBJECT_VERSION_NUMBER also makes it suitable for use in contexts that require optimistic locking awareness, though the view itself is read-only.

Underlying Base Objects

The documented base objects referenced by the view are:

• CS_INST_DETAIL_CONTACTS_V (VIEW) — the primary source, aliased IDC, supplying the installation detail identifier, the contact type code, the contact/party identifier, the CS contact identifier, the contact category, and the version number.
• CS_LOOKUPS (VIEW) — aliased CSLK, restricted to LOOKUP_TYPE = 'CS_CONTACT_TYPE', providing the translated meaning for the stored contact type code.
• HZ_PARTIES (SYNONYM) — aliased P, the trading community party record, joined on CONTACT_ID = PARTY_ID and supplying first and last name.
• FND_GLOBAL (PACKAGE) — referenced for the standard EBS session context (responsibility, user, organization) used in multi-org and security-enabled querying.

The joins are inner joins in all cases, so a row is returned only when a matching party and a matching CS_CONTACT_TYPE lookup both exist. The name is assembled as PERSON_FIRST_NAME concatenated with a space and PERSON_LAST_NAME.

Key Columns

• LINE_INST_DETAIL_ID — identifier of the installation detail line to which the contact is attached; the principal join key back to installation data.
• CONTACT_TYPE_CODE — the stored contact type code as held on the installation contact record; this is the value users search for when they query on "contact_type_code".
• CONTACT_TYPE — the decoded meaning of the contact type, derived from CS_LOOKUPS where LOOKUP_TYPE = 'CS_CONTACT_TYPE'. This is the display-friendly equivalent of CONTACT_TYPE_CODE.
• CONTACT_NAME — the concatenated full name of the contact, formed from the party's first and last name.
• CONT_FIRST_NAME / CONT_LAST_NAME — the individual name components, useful where reporting requires separate first and last name fields.
• CONTACT_ID — the HZ_PARTIES party identifier of the contact.
• CS_CONTACT_ID — the Service-specific contact identifier, distinct from the party ID and relevant for CS-native processing.
• CONTACT_CATEGORY — categorizes the contact relationship for the installation detail.
• OBJECT_VERSION_NUMBER — the row version stamp carried from the underlying record.

Common Use Cases and Queries

The most frequent requirement is resolving which contacts are associated with an installation detail and what role each plays. Because the view exposes both the code and its meaning, reports can filter on the code while displaying the meaning.

Contact type filtering, matching the search term "contact_type_code":

• SELECT line_inst_detail_id, contact_type_code, contact_type, contact_name FROM cs_inst_contact_dtls_v WHERE contact_type_code = :p_contact_type;

Listing all contacts for a specific installation detail:

• SELECT contact_name, contact_type, contact_category FROM cs_inst_contact_dtls_v WHERE line_inst_detail_id = :p_detail_id ORDER BY contact_type;

Producing a distinct inventory of contact types present in the data:

• SELECT contact_type_code, contact_type, COUNT(*) FROM cs_inst_contact_dtls_v GROUP BY contact_type_code, contact_type;

Because the view is built from inner joins, rows whose contact party record is missing from HZ_PARTIES, or whose contact type code has no active entry in CS_LOOKUPS for lookup type CS_CONTACT_TYPE, will not appear. Reports requiring every installation contact record should therefore reconcile against CS_INST_DETAIL_CONTACTS_V directly. All queries run under standard APPS security and respect the FND_GLOBAL session context.