Search Results contact_flag




Overview
Explore in AI Chat

Overview

CSI_INST_PARTY_DETAILS_V is an APPS-owned database view in the Oracle E-Business Suite Install Base (CSI) module. It consolidates party (customer, vendor, contact, and related party) information associated with installed base instances into a single queryable structure. The view resolves the relationships between an instance and the external parties tied to it, enriching raw identifiers with descriptive attributes such as party name, party number, relationship name, and party type meaning. In Oracle EBS 12.1.1 and 12.2.2, the object is registered as VALID and is typically consumed by Install Base forms, concurrent programs, and custom reporting or integration layers that need a denormalized, human-readable representation of instance-to-party relationships without executing multiple joins manually. Because it presents descriptive labels alongside keys, it is well suited for operational reports, service dashboards, and data extracts that must display who is associated with a given installed asset.

Underlying Base Objects

The view is defined over several base objects documented in ETRM 12.2.2: CSI_I_PARTIES (synonym), PO_VENDORS (view), CSI_IPA_RELATION_TYPES (synonym), CSI_LOOKUPS (view), along with HZ_PARTIES (synonym), PER_ALL_PEOPLE_F (synonym), JTF_RS_GROUPS_VL (view), and JTF_RS_TEAMS_VL (view). The core driver is CSI_I_PARTIES, which stores instance-party associations. It is joined to PO_VENDORS on PARTY_ID = VENDOR_ID where PARTY_SOURCE_TABLE equals 'PO_VENDORS', to CSI_IPA_RELATION_TYPES on RELATIONSHIP_TYPE_CODE = IPA_RELATION_TYPE_CODE (restricted to PARTY_USE_FLAG = 'Y'), and to CSI_LOOKUPS for the 'CSI_PARTY_SOURCE_TABLE' lookup to derive the party type meaning. The view text uses a UNION ALL structure, indicating it unifies multiple party-source branches—vendors, HZ parties, and resource parties (people, groups, teams)—each resolving PARTY_ID against its appropriate source object. This design allows one view to serve heterogeneous party sources while preserving a consistent column layout.

Key Columns

Common Use Cases and Queries

Typical scenarios include retrieving all parties tied to an instance, identifying the primary or preferred party, and filtering by active date range. A representative query follows:

SELECT instance_party_id, instance_id, party_name, party_number, party_type, relationship_name, primary_flag FROM csi_inst_party_details_v WHERE instance_id = :p_instance_id AND (active_end_date IS NULL OR active_end_date >= SYSDATE);

Because PARTY_SOURCE_TABLE varies across UNION ALL branches, reports should filter explicitly on this column when only vendor or HZ party records are required. Date-range predicates on ACTIVE_START_DATE and ACTIVE_END_DATE enforce temporal accuracy, and joining INSTANCE_ID back to CSI_ITEM_INSTANCES links party details to asset context.