Results for “cs_contact_type”

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

Overview

APPS.CS_INST_CONTACT_DTLS_V is an Oracle E-Business Suite internal database view owned by the APPS schema and registered in FND Design Data as CS.CS_INST_CONTACT_DTLS_V. It exposes the contact-level detail records associated with installed base instance details, presenting party, contact-type, and name information in a single flattened result set. The view is part of the TeleService / Field Service (CS) product family and, per Oracle's standard notice, is marked for Oracle Internal Use Only. Oracle does not support direct access to application data through this object except from standard Oracle Applications programs. Its primary role is to serve as a presentation and integration layer for contact information tied to installed base configurations, allowing application forms, concurrent programs, and dependent views to retrieve contact details without re-implementing the joins to the underlying contact and party tables.

Underlying Base Objects

The view is not defined over base tables directly; it resolves through a short chain of documented dependencies that ultimately reach the trading community and lookup model:

• CS_INST_DETAIL_CONTACTS_V (VIEW) — the principal source of contact-to-instance-detail associations and the primary driver of the result set.
• CS_LOOKUPS (VIEW) — supplies the decoded contact type, translating the stored CONTACT_TYPE_CODE into a meaningful CONTACT_TYPE description through the Service lookup definitions.
• HZ_PARTIES (SYNONYM) — provides party-level attributes from the Trading Community Architecture model, including the name components of the associated contact.
• FND_GLOBAL (PACKAGE) — used at query time to resolve session context such as the effective user and login, which influences row filtering and multilingual (MLS) name resolution.

Because the view sits on top of other views rather than normalized base tables, its performance profile depends on the cost of expanding the underlying CS and HZ view logic. The final dependency list confirms that no other database object in the EBS schema references CS_INST_CONTACT_DTLS_V, so it functions as a leaf reporting object rather than a building block for further composition within the dictionary.

Key Columns

The view returns ten columns, of which the following carry the most functional weight:

• LINE_INST_DETAIL_ID (NUMBER) — identifier of the line-level instance detail to which the contact record is attached; this is the join key back to the installed base detail hierarchy.
• CONTACT_ID (NUMBER(15)) — the contact identifier, linking the row to the originating contact record.
• CS_CONTACT_ID (NUMBER) — the primary record identifier for the contact as maintained by the CS schema.
• CONTACT_TYPE_CODE (VARCHAR2(30)) and CONTACT_TYPE (VARCHAR2(80)) — the coded value and its decoded, user-facing description as resolved through CS_LOOKUPS.
• CONTACT_NAME (VARCHAR2(301)), CONT_FIRST_NAME (VARCHAR2(150)), and CONT_LAST_NAME (VARCHAR2(150)) — the formatted full name and its component parts, derived from the party definition.
• CONTACT_CATEGORY (VARCHAR2(30)) — the category classification applied to the contact.
• OBJECT_VERSION_NUMBER (NUMBER) — the sequential locking token used by the framework to detect concurrent modifications.

Common Use Cases and Queries

The view is typically queried by support and service reporting logic that needs to list or validate the contacts associated with a given installed base detail line. A straightforward retrieval of all contact columns for a specific instance detail line is shown below.

SELECT line_inst_detail_id, contact_type, contact_name, cont_last_name, contact_id, contact_category FROM apps.cs_inst_contact_dtls_v WHERE line_inst_detail_id = :detail_id ORDER BY cont_last_name, cont_first_name;

A common variation filters on the name components when the search term is a surname, matching the typical lookup pattern for "cont_last_name":

SELECT line_inst_detail_id, contact_name, cont_first_name, cont_last_name FROM apps.cs_inst_contact_dtls_v WHERE UPPER(cont_last_name) LIKE UPPER(:surname || '%');

Because the object is documented as Oracle Internal Use Only, any custom query should be treated as read-only and reviewed against Oracle's support policy before being embedded in a production interface. Where possible, standard Oracle Applications programs should be used instead of direct SQL against this view.