Search Results csi_i_party_interface
Overview
CSI_I_PARTY_INTERFACE is an open interface table in the Oracle E-Business Suite Install Base (CSI) module. It serves as the inbound staging area for party information associated with install base instances, allowing external source systems, legacy conversions, and third-party applications to load party, contact, and account relationship data before it is validated and transferred into the production Install Base tables. In release 12.1.1 and 12.2.2 the table is owned by the CSI schema and is documented as VALID, containing 111 columns.
From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests the table is best treated as an independent staging or interface entity rather than as a conventional hub, link, or satellite. It does not participate in a dense network of referential constraints; its single documented foreign key points to CSI_I_PARTIES, meaning the interface record carries a reference to the target instance party while remaining a self-contained load unit.
Key Information Stored
The table's surrogate primary key is IP_INTERFACE_ID, which is also the sole documented unique index (CSI_I_PARTY_INTERFACE_U1) and therefore the primary business-key candidate for row-level identification during interface processing. The most significant columns include:
- IP_INTERFACE_ID – Unique interface row identifier; the primary key and the column typically used to track a specific staged record.
- INST_INTERFACE_ID – Links the party interface row to its parent instance interface batch, enabling coordinated processing across the Install Base open interface.
- INSTANCE_PARTY_ID – Foreign key to CSI_I_PARTIES; identifies the target instance party record once the row is validated and loaded.
- PARTY_ID / PARTY_NUMBER / PARTY_NAME – Core party identification attributes used to match or create the trading partner.
- PARTY_RELATIONSHIP_TYPE_CODE – Defines the role the party plays relative to the instance (for example, owner, lessee, or operator).
- PARTY_START_DATE / PARTY_END_DATE – Effective dating for the party relationship.
- CONTACT_FLAG and CONTACT_* columns – Flag and carry the associated contact party number, name, and relationship type.
- PARTY_ATTRIBUTE1 through PARTY_ATTRIBUTE15 – Descriptive flexfield segments for extensible party context.
- IP_ACCOUNT1_ID, IP_ACCOUNT2_ID, IP_ACCOUNT3_ID – Account relationship identifiers supporting up to three accounts per party row.
- PARTY_ACCOUNT*_NUMBER and ACCT*_RELATIONSHIP_TYPE_CODE – Account numbers and the relationship type connecting each account to the party.
- BILL_TO_ADDRESS* / SHIP_TO_ADDRESS* – Address references captured for each of the three account slots.
- ERROR_TEXT – Populated when interface validation fails, giving the rejection reason for troubleshooting.
- PARALLEL_WORKER_ID – Supports multi-threaded concurrent processing of large interface volumes.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard audit columns.
Common Use Cases and Queries
Typical scenarios include legacy data conversion of customer party relationships into Install Base, integration from external CRM or billing systems, and bulk maintenance of account relationships tied to installed assets. Common SQL patterns select unconsumed or errored rows:
- Identifying failed rows:
SELECT ip_interface_id, party_name, error_text FROM csi_i_party_interface WHERE error_text IS NOT NULL; - Reviewing staged data by batch:
SELECT * FROM csi_i_party_interface WHERE inst_interface_id = :batch_id; - Checking load progress by parallel worker:
SELECT parallel_worker_id, COUNT(*) FROM csi_i_party_interface GROUP BY parallel_worker_id; - Joining to the target party table to confirm successful linkage on INSTANCE_PARTY_ID to CSI_I_PARTIES.
Reporting use cases center on interface reconciliation, validation error analysis, and audit of party relationship effective dates before committing data to production.
Related Objects
- CSI_I_PARTIES – Referenced through the documented foreign key INSTANCE_PARTY_ID; the production party relationship table populated after interface processing.
- CSI_I_PARTY_INTERFACE child batch sources via INST_INTERFACE_ID (the instance-level open interface tables) – governs the parent instance interface grouping.
- Install Base open interface concurrent programs – the standard request set that reads this table, validates rows, and writes results into CSI_I_PARTIES.
- HZ_PARTIES and related Trading Community Architecture tables – supply and validate party identity referenced by PARTY_ID, PARTY_NUMBER, and PARTY_NAME.
- HZ_CUST_ACCOUNTS – resolves the account numbers and account relationship types staged in the IP_ACCOUNT*_ID and PARTY_ACCOUNT*_ID columns.
-
Table: CSI_I_PARTY_INTERFACE
12.2.2
owner:CSI, object_type:TABLE, fnd_design_data:CSI.CSI_I_PARTY_INTERFACE, object_name:CSI_I_PARTY_INTERFACE, status:VALID, product: CSI - Install Base , description: Open Interface Party Information , implementation_dba_data: CSI.CSI_I_PARTY_INTERFACE ,
-
Table: CSI_I_PARTY_INTERFACE
12.1.1
owner:CSI, object_type:TABLE, fnd_design_data:CSI.CSI_I_PARTY_INTERFACE, object_name:CSI_I_PARTY_INTERFACE, status:VALID, product: CSI - Install Base , description: Open Interface Party Information , implementation_dba_data: CSI.CSI_I_PARTY_INTERFACE ,
-
APPS.CSI_ML_UTIL_PVT SQL Statements
12.1.1
-
APPS.CSI_ML_UTIL_PVT SQL Statements
12.2.2
-
SYNONYM: APPS.CSI_I_PARTY_INTERFACE
12.2.2
owner:APPS, object_type:SYNONYM, object_name:CSI_I_PARTY_INTERFACE, status:VALID,
-
SYNONYM: APPS.CSI_I_PARTY_INTERFACE
12.1.1
owner:APPS, object_type:SYNONYM, object_name:CSI_I_PARTY_INTERFACE, status:VALID,
-
VIEW: CSI.CSI_I_PARTY_INTERFACE#
12.2.2
owner:CSI, object_type:VIEW, object_name:CSI_I_PARTY_INTERFACE#, status:VALID,
-
APPS.CSI_ML_CREATE_PVT SQL Statements
12.2.2
-
PACKAGE BODY: APPS.CSI_ML_REPLACE_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_REPLACE_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSI_ML_UPDATE_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_UPDATE_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSI_ML_UPDATE_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_UPDATE_PVT, status:VALID,
-
APPS.CSI_ML_CREATE_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.CSI_ML_UTIL_PVT
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.CSI_ML_CREATE_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_CREATE_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSI_ML_INTERFACE_TXN_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_INTERFACE_TXN_PVT, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.CSI_ML_UTIL_PVT
12.2.2
-
PACKAGE BODY: APPS.CSI_ML_REPLACE_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_REPLACE_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSI_ML_CREATE_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_CREATE_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSI_ML_PROGRAM_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_PROGRAM_PUB, status:VALID,
-
PACKAGE BODY: APPS.CSI_ML_PROGRAM_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_PROGRAM_PUB, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.CSI_ML_UTIL_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_UTIL_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSI_ML_UTIL_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_UTIL_PVT, status:VALID,
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.CSI_ML_INTERFACE_TXN_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSI_ML_INTERFACE_TXN_PVT, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
APPS.CSI_ML_INTERFACE_TXN_PVT SQL Statements
12.2.2
-
APPS.CSI_ML_INTERFACE_TXN_PVT SQL Statements
12.1.1
-
VIEW: CSI.CSI_I_PARTY_INTERFACE#
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
TABLE: CSI.CSI_I_PARTY_INTERFACE
12.1.1
owner:CSI, object_type:TABLE, fnd_design_data:CSI.CSI_I_PARTY_INTERFACE, object_name:CSI_I_PARTY_INTERFACE, status:VALID,
-
TABLE: CSI.CSI_I_PARTY_INTERFACE
12.2.2
owner:CSI, object_type:TABLE, fnd_design_data:CSI.CSI_I_PARTY_INTERFACE, object_name:CSI_I_PARTY_INTERFACE, status:VALID,
-
APPS.CSI_ML_PROGRAM_PUB SQL Statements
12.1.1
-
APPS.CSI_ML_PROGRAM_PUB SQL Statements
12.2.2
-
APPS.CSI_ML_UPDATE_PVT dependencies on CSI_I_PARTY_INTERFACE
12.1.1
-
APPS.CSI_ML_INTERFACE_TXN_PVT dependencies on CSI_I_PARTY_INTERFACE
12.1.1
-
APPS.CSI_ML_REPLACE_PVT dependencies on CSI_I_PARTY_INTERFACE
12.2.2
-
APPS.CSI_ML_CREATE_PVT dependencies on CSI_I_PARTY_INTERFACE
12.1.1
-
APPS.CSI_ML_PROGRAM_PUB dependencies on CSI_I_PARTY_INTERFACE
12.2.2
-
APPS.CSI_ML_CREATE_PVT dependencies on CSI_I_PARTY_INTERFACE
12.2.2
-
APPS.CSI_ML_REPLACE_PVT dependencies on CSI_I_PARTY_INTERFACE
12.1.1
-
APPS.CSI_ML_UTIL_PVT dependencies on CSI_I_PARTY_INTERFACE
12.2.2
-
APPS.CSI_ML_INTERFACE_TXN_PVT dependencies on CSI_I_PARTY_INTERFACE
12.2.2
-
APPS.CSI_ML_UPDATE_PVT dependencies on CSI_I_PARTY_INTERFACE
12.2.2