Results for “party_source_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CSI_T_PARTY_DETAILS is a transactional interface table owned by the CSI (Install Base) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the association between an instance (an installed asset tracked in the Install Base) and one or more parties (customers, contacts, or other trading partners) as captured during an Install Base transaction. Rows in this table represent the staging-level, transaction-scoped view of party relationships before they are committed to the permanent instance-party model.
The table is documented as "Transaction Details: Instance-Party Associations," which places it in the transaction-processing layer of the Install Base architecture. Its foreign key topology links it upward to transaction line details (CSI_T_TXN_LINE_DETAILS), laterally to instance parties (CSI_I_PARTIES) and Oracle Trading Community parties (HZ_PARTIES), and downward to party account detail (CSI_T_PARTY_ACCOUNTS). Based on the mined foreign key structure, the heuristic Data Vault classification for this object is satellite-leaning. In a Data Vault model it would function as a satellite attached to the transaction line detail hub and the instance-party link, capturing descriptive and temporal attributes of each party association rather than acting as an independent business hub.
Key Information Stored
The table contains 37 documented columns. The most significant are summarized below.
- TXN_PARTY_DETAIL_ID — Surrogate primary key (
CSI_T_PARTY_DETAILS_PK) and the column referenced by the user's search term. - TXN_LINE_DETAIL_ID — Foreign key to
CSI_T_TXN_LINE_DETAILS; ties the party association to a specific transaction line, establishing the operational context of the record. - INSTANCE_PARTY_ID — Foreign key to
CSI_I_PARTIES; identifies the permanent instance-party association being staged or promoted. - PARTY_SOURCE_TABLE and PARTY_SOURCE_ID — Identify the originating entity and its primary key;
PARTY_SOURCE_IDjoins toHZ_PARTIESfor Trading Community party resolution. - RELATIONSHIP_TYPE_CODE — Foreign key to
CSI_IPA_RELATION_TYPES; defines the semantic role of the party (e.g., owner, contact, operator) relative to the instance. - CONTACT_PARTY_ID — Self-referencing foreign key identifying the contact party linked to the primary association.
- CONTACT_FLAG, PREFERRED_FLAG, PRIMARY_FLAG — Boolean indicators designating whether the row represents a contact, the preferred party, or the primary party for the association.
- ACTIVE_START_DATE / ACTIVE_END_DATE — Effective-dating columns that scope the association's validity window.
- PRESERVE_DETAIL_FLAG and MIGRATED_FLAG — Control flags governing retention behavior and migration status of the transaction detail.
- SECURITY_GROUP_ID — Foreign key to
FND_SECURITY_GROUPSenforcing multi-tenant data isolation. - Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) plus CONTEXT and 15 ATTRIBUTEn flex columns for extensibility.
Unique index CSI_T_PARTY_DETAILS_U01 on TXN_PARTY_DETAIL_ID confirms it as the sole documented business-key candidate; no other natural business key is enumerated.
Common Use Cases and Queries
Typical usage involves reconciling transactional party assignments against the permanent Install Base model and auditing which party relationships were created during a given transaction.
- Retrieving all party associations for a transaction line:
SELECT txn_party_detail_id, instance_party_id, party_source_id, relationship_type_code, contact_flag, primary_flag FROM csi.csi_t_party_details WHERE txn_line_detail_id = :line_detail_id; - Resolving party names by joining to
HZ_PARTIESonPARTY_SOURCE_ID. - Identifying primary or preferred parties per instance using
PRIMARY_FLAG/PREFERRED_FLAG. - Auditing effective-dating windows via
ACTIVE_START_DATEandACTIVE_END_DATE. - Locating records that have not yet been promoted to
CSI_I_PARTIESby comparingINSTANCE_PARTY_IDvalues. - Filtering by
MIGRATED_FLAGto isolate legacy-converted association data.
Related Objects
- CSI_T_TXN_LINE_DETAILS — Referenced via
TXN_LINE_DETAIL_ID; parent transaction line context. - CSI_I_PARTIES — Referenced via
INSTANCE_PARTY_ID; the permanent instance-party link. - CSI_IPA_RELATION_TYPES — Referenced via
RELATIONSHIP_TYPE_CODE; relationship type lookup. - HZ_PARTIES — Referenced via
PARTY_SOURCE_ID; Trading Community party master. - FND_SECURITY_GROUPS — Referenced via
SECURITY_GROUP_ID; multi-tenant enforcement. - CSI_T_PARTY_ACCOUNTS — Child table referencing
TXN_PARTY_DETAIL_ID; holds account-level detail for each party association. - CSI_T_PARTY_DETAILS (self) — Recursive reference through
CONTACT_PARTY_ID.
-
Transaction Details : Instance-Party Associations.
-
Transaction Details : Instance-Party Associations.
-
PACKAGE: APPS.CSI_DEBUG_PKG 12.2.2
-
PACKAGE: APPS.CSI_DEBUG_PKG 12.1.1