Results for “inst_detail”

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

Overview

APPS.CS_INST_DETAIL_CONTACTS_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema and belonging to the Service (CS) module. It exposes a filtered subset of contact role assignments that are linked specifically to service installation detail records. Internally, the view resolves the generic contact-role association table CS_CONTACTS by restricting rows to those whose SOURCE_OBJECT_CODE equals 'INST_DETAIL' and whose SVC_PROVIDER_FLAG is not 'Y'. The view therefore isolates customer- or party-side contacts attached to an installation, as opposed to service-provider contacts.

The view serves primarily as a denormalized access path for forms, concurrent programs, and downstream integrations that need to resolve the contacts associated with a particular instance or line installation detail. Rather than requiring callers to know the internal SOURCE_OBJECT_CODE convention, the view presents a stable, named interface with a renamed column (SOURCE_OBJECT_ID aliased as LINE_INST_DETAIL_ID) that maps directly to the installation detail primary key. This abstraction is consistent with the ETRM-documented behavior for EBS 12.2.2 and applies identically to the 12.1.1 code line.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: the synonym CS_CONTACTS, which resolves to the underlying CS schema contact-role table. The view is defined with a straightforward SELECT against that object and introduces no joins, unions, or external lookups. As a result, its performance characteristics are essentially those of CS_CONTACTS combined with the filter predicate on SOURCE_OBJECT_CODE and the NVL-based predicate on SVC_PROVIDER_FLAG.

Because the view is owned by APPS and reads through a synonym, it inherits standard EBS security semantics: grants on CS_CONTACTS and on the view itself determine which responsibilities and users may query it. No materialization or partitioning is documented, so the view is evaluated at runtime on each access.

Key Columns

• CS_CONTACT_ID — The primary key of the contact-role association row within CS_CONTACTS; uniquely identifies the relationship between a contact and the installation detail.
• CONTACT_ID — The identifier of the underlying contact party record; joins to the contact or party entities maintained elsewhere in the Trading Community Architecture.
• CONTACT_TYPE — Classifies the role the contact plays in the context of the installation detail.
• LINE_INST_DETAIL_ID — The alias applied to SOURCE_OBJECT_ID. This value corresponds to the installation detail identifier and is the principal join key back to the installation detail entity.
• OBJECT_VERSION_NUMBER — Optimistic concurrency control column used by the EBS framework to detect stale updates during transactional processing.
• CONTACT_CATEGORY — Categorizes the contact assignment, supporting filtering by business-defined groupings.

Notably, the view omits the SVC_PROVIDER_FLAG and SOURCE_OBJECT_CODE columns because both are consumed as filter predicates; every returned row implicitly carries SOURCE_OBJECT_CODE = 'INST_DETAIL' and a service-provider flag of 'N' or NULL.

Common Use Cases and Queries

Typical use cases include installation detail inquiries, contact extraction for field service reporting, and data migration or interface extracts that must distinguish customer contacts from provider contacts on an installation.

A simple retrieval of all contacts for a specific installation detail line:

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

Joining to installation detail to obtain instance context:

• SELECT v.contact_id, v.contact_type, d.instance_id FROM apps.cs_inst_detail_contacts_v v, apps.cs_inst_detail d WHERE v.line_inst_detail_id = d.inst_detail_id;

Aggregating contact counts per category for a reporting extract:

• SELECT contact_category, COUNT(*) FROM apps.cs_inst_detail_contacts_v GROUP BY contact_category;

Because the view performs no joins, queries should index-drive on SOURCE_OBJECT_ID and SOURCE_OBJECT_CODE within CS_CONTACTS to avoid full scans on large installations. All queries should be executed with an appropriate APPS responsibility to satisfy EBS data security.