Search Results new_party_name




Overview
Explore in AI Chat

Overview

APPS.CSI_IPH_DETAILS_V is a reporting view owned by the APPS schema and registered in the FND Design Data repository under the CSI (Complex Service Item / Install Base) product family. In Oracle EBS 12.1.1 and 12.2.2 it exposes the audit history of party relationships attached to install base instances. Every time a relationship between an instance and a party (customer, employee, vendor, group, or team) is created, updated, or end-dated, the Install Base transaction layer records the change in CSI_I_PARTIES_H. This view flattens those historical rows into an old-value / new-value pair of columns so that consumers can compare the state of a relationship both before and after a change on a single row.

The view is classified as Internal Oracle use only. Oracle does not support direct data access outside standard Oracle Applications programs, so it should be treated as a read-only reference for diagnostics, extraction, and reporting rather than as an integration endpoint. This is also the context in which references to NEW_PARTY_TYPE arise: the view carries the NEW_PARTY_ID and its associated party attributes, which resolve to a party type at the HZ_PARTIES level (for example, PARTY_TYPE = 'ORGANIZATION', 'PERSON', or 'GROUP'), enabling historical comparison of how the owning party of an instance relationship changed over time.

Underlying Base Objects

The documented referenced objects are CSI_IPA_RELATION_TYPES, CSI_I_PARTIES, CSI_I_PARTIES_H, CSI_LOOKUPS, HZ_PARTIES, JTF_RS_GROUPS_VL, JTF_RS_TEAMS_VL, PER_ALL_PEOPLE_F, and PO_VENDORS. The transactional history rows are sourced from CSI_I_PARTIES_H, the history table for instance party relationships, while CSI_I_PARTIES supplies current-state relationships. CSI_IPA_RELATION_TYPES and CSI_LOOKUPS decode relationship type codes, including the OLD_RELATIONSHIP_TYPE_CODE and NEW_RELATIONSHIP_TYPE_CODE columns. HZ_PARTIES provides the trading community party being attached or removed. JTF_RS_GROUPS_VL, JTF_RS_TEAMS_VL, PER_ALL_PEOPLE_F, and PO_VENDORS supply descriptive attributes for the resource groups, teams, employees, and suppliers that can act as the party in an instance relationship, which is why the view exposes OLD_PARTY_SOURCE_TABLE and NEW_PARTY_SOURCE_TABLE to identify the origin of each party reference.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing when a customer was replaced on an asset, verifying who owned an instance at a historic date, and reconciling Install Base party changes against transaction history.

SELECT h.instance_id,
       h.new_party_id,
       h.new_party_source_table,
       h.new_relationship_type_code,
       h.new_active_start_date,
       h.new_active_end_date
FROM   apps.csi_iph_details_v h
WHERE  h.instance_id = :p_instance_id
ORDER BY h.instance_party_history_id;

To resolve the new party's type, join to HZ_PARTIES on NEW_PARTY_ID and filter on PARTY_TYPE. Because the object is internal, queries should be limited to read-only reporting and should account for the view's effective-dating columns when reconstructing point-in-time party ownership.