Search Results csi_ii_relation_interface




Overview
Explore in AI Chat

Overview

CSI_II_RELATION_INTERFACE is the Oracle E-Business Suite Install Base (CSI) open interface staging table that holds inbound relationships between install base instances prior to validation and import into the production relationship tables. In Release 12.1.1 and 12.2.2, it functions as the receiving area for external systems, legacy migrations, and third-party applications that supply parent-child, component-to-system, or peer relationships among instances. Each row represents a single relationship to be processed, supplied with a relationship type, effective dates, direction, and the surrogate identifiers of the subject and object instance interface records. The table is populated by external loading processes and consumed by concurrent programs such as the Install Base Interface (CSIIMPT) that validate the staged data and write accepted rows into the base CSI relationship tables.

From a Data Vault modeling perspective, the table can be characterized as a link satellite candidate: it captures an association between two instance references (subject and object) together with descriptive and control attributes such as relationship type, dates, and processing status. Treated heuristically, SUBJECT_INTERFACE_ID and OBJECT_INTERFACE_ID form the participating business keys of the link, while the remaining descriptive columns behave as satellite attributes. This classification is a modeling suggestion only; the physical implementation in EBS is a conventional open interface table.

Key Information Stored

The documented physical schema contains 41 columns in schema CSI. The surrogate primary key is REL_INTERFACE_ID, which is also the sole unique index (CSI_II_RELATION_INTERFACE_U1) and therefore the principal business-key candidate. The central business columns are:

Common Use Cases and Queries

Typical use cases include bulk migration of legacy asset hierarchies, loading relationships from external inventory or maintenance systems, and reconciliation of rejected relationship rows. A common monitoring query examines processing outcomes:

  • SELECT process_status, COUNT(*) FROM csi.csi_ii_relation_interface GROUP BY process_status;
  • SELECT rel_interface_id, error_text FROM csi.csi_ii_relation_interface WHERE process_status = 'ERROR';
  • SELECT r.rel_interface_id, r.relationship_type_code, r.relationship_start_date FROM csi.csi_ii_relation_interface r WHERE r.sub_source_system_name = :source;

Reporting queries join staged rows to the instance interface table on SUBJECT_INTERFACE_ID and OBJECT_INTERFACE_ID to present human-readable instance names, and filter on SOURCE_TRANSACTION_DATE to isolate a load batch. Rows with populated ERROR_TEXT are extracted to a correction file, corrected, and re-staged.

Related Objects

  • IGS_UC_COM_EBL_SUBJ — referenced by the documented foreign key on SUBJECT_ID; joins on subject identifier.
  • CSI_II_INSTANCE_INTERFACE — the companion instance open interface table; join via SUBJECT_INTERFACE_ID and OBJECT_INTERFACE_ID.
  • CSI_INSTANCE_RELATIONSHIPS — the base relationship table that receives validated rows from this interface.
  • CSI_ITEM_INSTANCES — resolved via OBJECT_ID / SUBJECT_ID for instance-level reporting.
  • CSI_RELATIONSHIP_TYPES — supplies valid values for RELATIONSHIP_TYPE_CODE validation.
  • Install Base Interface concurrent program (CSIIMPT) — the processing routine that consumes and clears this staging table.