Search Results csi_ii_relation_interface_u1

Overview

CSI.CSI_II_RELATION_INTERFACE is the open interface (staging) table used by the Oracle E-Business Suite Install Base Open Interface to load instance-to-instance relationships. It is a public, active database object owned by the CSI (Installed Base/Customer Support Intelligence) schema and resides in the APPS_TS_INTERFACE tablespace, the standard staging area for inbound interface data. Records inserted here describe relationships such as "CONNECTED-TO" between two item instances before they are validated and transferred to the base Install Base relationship tables.

The table is documented in ETRM 12.2.2 with 41 columns. Because the SUBJECT_INTERFACE_ID and OBJECT_INTERFACE_ID columns carry the INST_INTERFACE_ID values that are staged in CSI_INSTANCE_INTERFACE, this table acts as a dependent staging object that is only meaningful when processed alongside the instance interface rows. From a modeling standpoint, the metadata classifies this object as a standalone data set; in Data Vault terms it would more naturally be considered a link candidate, since each row associates two instance-interface business keys through a typed relationship. That classification is a modeling suggestion, not a documented constraint.

Key Information Stored

The most operationally significant columns are:

• REL_INTERFACE_ID — surrogate primary key for the staging row and the column behind the unique index CSI_II_RELATION_INTERFACE_U1.
• SUBJECT_INTERFACE_ID and OBJECT_INTERFACE_ID — foreign references to staged instance rows (INST_INTERFACE_ID in CSI_INSTANCE_INTERFACE); they define the two endpoints of the relationship.
• SUBJECT_ID and OBJECT_ID — persisted instance identifiers used after interface resolution; note the documented foreign key from SUBJECT_ID to IGS_UC_COM_EBL_SUBJ.
• RELATIONSHIP_TYPE_CODE — VARCHAR2(30) relationship type, for example CONNECTED-TO.
• RELATIONSHIP_START_DATE and RELATIONSHIP_END_DATE — active date range of the relationship.
• RELATIONSHIP_DIRECTION, POSITION_REFERENCE, DISPLAY_ORDER and MANDATORY_FLAG — presentation and directional semantics of the relationship.
• PROCESS_STATUS and ERROR_TEXT — interface processing state and validation failure messages.
• SOURCE_SYSTEM_NAME, SOURCE_TRANSACTION_DATE, SOURCE_TRANSACTION_TYPE and TRANSACTION_IDENTIFIER — source system attribution and idempotency keys.
• PARALLEL_WORKER_ID — worker assignment when instances and relationships are created through the parallel worker process.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• CONFIG_ROOT_NODE — flags the configuration root node in a related configuration hierarchy.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — the standard EBS descriptive flexfield (DFF) container.

Common Use Cases and Queries

Typical usage centers on loading, monitoring, and reprocessing interface batches. Analysts query rows by process status to find pending or errored relationships:

• SELECT rel_interface_id, subject_interface_id, object_interface_id, relationship_type_code FROM csi.csi_ii_relation_interface WHERE process_status = 'ERROR';
• SELECT error_text FROM csi.csi_ii_relation_interface WHERE source_system_name = 'MY_SYSTEM' AND transaction_identifier = 'TXN123';
• Join to instance staging to resolve endpoints: SELECT r.relationship_type_code, s.* FROM csi.csi_ii_relation_interface r JOIN csi.csi_instance_interface s ON s.inst_interface_id = r.subject_interface_id.

Reporting use cases include reconciliation of source-system load volumes by SOURCE_TRANSACTION_DATE and SOURCE_SYSTEM_NAME, verification of relationship date ranges, and identification of parallel-worker assignment drift. Interface rows are normally purged after successful transfer, so historical reporting should target the base relationship tables rather than this interface object.

Related Objects

• CSI.CSI_INSTANCE_INTERFACE — parent staging table; SUBJECT_INTERFACE_ID and OBJECT_INTERFACE_ID map to its INST_INTERFACE_ID column.
• CSI.CSI_II_RELATIONSHIPS (base Install Base relationship table) — target of the concurrent transfer program after validation.
• CSI.CSI_ITEM_INSTANCE — the business entity into which instance rows and relationships are ultimately materialized.
• CSI_INSTANCE_PUB / CSI_II_RELATIONSHIP_PUB PL/SQL APIs — programmatic entry points that validate and migrate interface rows.
• IGS_UC_COM_EBL_SUBJ — documented FK target for SUBJECT_ID.
• FND_CONCURRENT_PROGRAMS / concurrent manager logs — trace the process_status transitions during interface import.