Results for “object_version_number”
50+ results
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.
-
This view lists the contact information pertaining to the Installation Details
APPS.CS_INST_DETAIL_CONTACTS_V·↳ CS_CONTACTS·Explore CS module →
-
This view lists the contact information pertaining to the Installation Details
APPS.CS_INST_DETAIL_CONTACTS_V·↳ CS_CONTACTS·Explore CS module →
-
This view is created for backward compatibility for CS_HZ_SR_CONTACT_POINTS table.
APPS.CS_HZ_SR_CONTACT_POINTS_V·↳ CS_HZ_SR_CONTACT_POINTS·Explore CS module →
-
This table stores information about the criteria group, which is a grouping of one or more search criteria.
-
View: CS_INST_CONTACT_DTLS_V 12.1.1
This view lists the details of the contacts pertaining to Installation Details
APPS.CS_INST_CONTACT_DTLS_V·↳ CS_INST_DETAIL_CONTACTS_V·↳ CS_LOOKUPS·↳ FND_GLOBAL·Explore CS module →
-
Store any type of objects to responsibility association. Each object type is identified by an unique object type.
-
Store any type of objects to responsibility association. Each object type is identified by an unique object type.
-
This table stores information about the Saved Search result columns.
-
Stores information about the allowable statutes for a status rule.
-
This table stores SR Type access information when service security is turned on.
-
This table stores translated information about service request type category.
-
This table stores information about the criteria values used in search criteria.
-
This table stores information about the HTML Service saved search.
-
This table stores sorting information for a search in CS_CSZ_SEARCHES table.
-
This table stores folders that belong to users. It has a foreign key pointing to FND_USER.
-
This view is created for backward compatibility for CS_HZ_SR_CONTACT_POINTS table.
APPS.CS_HZ_SR_CONTACT_POINTS_V·↳ CS_HZ_SR_CONTACT_POINTS·Explore CS module →
-
This table stores the instances of individual filters that belong to folders. The combination of USER_FOLDER_ID and FUNCTION_FILER_ID is unique.
-
The sequence in which a template group has to be searched would be defined in this table.
-
This table stores information about the criteria values used in search criteria.
-
This table stores folders that belong to users. It has a foreign key pointing to FND_USER.
-
Knowlegde Base AutoLink Usages
-
This table stores information about the criteria in Saved Search.
-
This table stores mappings between Party Role Groups and Party Roles.
-
View: CS_INST_CONTACT_DTLS_V 12.2.2
This view lists the details of the contacts pertaining to Installation Details
APPS.CS_INST_CONTACT_DTLS_V·↳ CS_INST_DETAIL_CONTACTS_V·↳ CS_LOOKUPS·↳ FND_GLOBAL·Explore CS module →
-
View: CS_SR_LINK_TYPES_VL 12.2.2
View has information of service request relationship types. This view is based on CS_SR_LINK_TYPES_B and _TL and is used to select the translated name and description. New for 1159.
APPS.CS_SR_LINK_TYPES_VL·↳ CS_SR_LINK_TYPES_B·↳ CS_SR_LINK_TYPES_TL·Explore CS module →
-
This table stores information about the criteria group, which is a grouping of one or more search criteria.
-
This table stores information about the criteria in Saved Search.
-
It stores the relationship between functions and filters. The table has a foreign key to both the table CS_QM_FILTERS and FND_FORM_FUNCTIONS.
-
Stores information about the allowable statutes for a status rule.
-
This table stores information about the Saved Search result columns.
-
This table stores the mapping information, between the service request type and type category.
-
This table stores SR Type access information when service security is turned on.
-
This table stores translated information about service request type category.
-
The sequence in which a template group has to be searched would be defined in this table.
-
This table is used to store the basic search columns and values in the service request saved searches module.
-
This table is used to store the basic search columns and values in the service request saved searches module.
-
This table stores the mapping information, between the service request type and type category.
-
This table lists the pages available for each flow type.
-
Base table for all event definitions.
-
This table lists the pages available for each flow type.
-
Stores the possible contexts that can be associated with each source.
-
This table stores the instances of individual filters that belong to folders. The combination of USER_FOLDER_ID and FUNCTION_FILER_ID is unique.
-
Knowlegde Base AutoLink Usages
-
This table stores mappings between Party Role Groups and Party Roles.
-
Tale defines valid event-action associations.
-
This table stores sorting information for a search in CS_CSZ_SEARCHES table.