Search Results csi_instance_interface

Overview

CSI_INSTANCE_INTERFACE is the open interface staging table for the CSI (Install Base) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It holds inbound, unprocessed records intended to create or update install base instance records in the CSI_INSTANCE table. External source systems — typically order management, inventory, manufacturing, or third-party asset tracking applications — populate this table, after which a concurrent program validates each row and pushes valid data into the base install base tables. The table therefore operates as a transient loading area rather than a permanent transactional store, with records accumulating until the concurrent import process consumes them.

The physical definition documented in ETRM 12.2.2 lists 245 columns under the CSI schema. Data Vault classification, mined heuristically from the foreign key structure, identifies this object as standalone — it references parent tables but is not itself a parent, suggesting it is best modeled as a staging or link-style entity rather than a true hub. The single documented unique index, CSI_INSTANCE_INTERFACE_U1 on INST_INTERFACE_ID, establishes the surrogate identifier for each interface row.

Key Information Stored

The most significant columns fall into several functional groups:

• INST_INTERFACE_ID — surrogate primary key, defined by the CSI_INSTANCE_INTERFACE_U1 unique index; assigns each staging row a stable identifier.
• SOURCE_SYSTEM_NAME, TRANSACTION_IDENTIFIER, SOURCE_TRANSACTION_DATE, SOURCE_TRANSACTION_TYPE — identify the originating system and transaction, enabling traceability and duplicate detection.
• PROCESS_STATUS, BATCH_NAME, ERROR_TEXT — drive the concurrent import cycle; PROCESS_STATUS indicates whether a row is pending, processed, or errored, while ERROR_TEXT records validation failures.
• INSTANCE_ID, INSTANCE_NUMBER, SERIAL_NUMBER, LOT_NUMBER — the core instance identity attributes passed to CSI_INSTANCE.
• INVENTORY_ITEM_ID, INV_CONCATENATED_SEGMENTS, INVENTORY_REVISION, INV_VLD_ORGANIZATION_ID — link the staged instance to the inventory item and validating organization.
• INSTANCE_STATUS_ID, INSTANCE_CONDITION_ID, OPERATIONAL_STATUS_CODE — foreign-key style references to status and condition lookups; INSTANCE_STATUS_ID is documented as referencing CSI_INSTANCE_STATUSES.
• INSTANCE_OU_ID, OPERATING_UNIT, OPERATING_UNIT_NAME — assign the instance to an operating unit. INSTANCE_OU_ID references CSI_I_ORG_ASSIGNMENTS.
• INSTANCE_ATTRIBUTE1 through INSTANCE_ATTRIBUTE30 — descriptive flexfield segments captured for extensibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns used for reconciliation and cleanup of processed rows.

Common Use Cases and Queries

Typical uses include monitoring interface health, diagnosing errors during import, and reconciling source transactions against resulting instances. Because ROWID-based cleanup is common, the interface table is often purged after successful processing.

A standard error review query filters on PROCESS_STATUS and reads ERROR_TEXT:

SELECT inst_interface_id, source_system_name, serial_number,
       process_status, error_text
FROM   csi.csi_instance_interface
WHERE  process_status IN ('ERROR','REJECTED')
ORDER BY creation_date DESC;

Reconciliation by source system shows pending versus completed volumes:

SELECT source_system_name, process_status, COUNT(*) 
FROM   csi.csi_instance_interface
GROUP BY source_system_name, process_status;

Joining to the parent lookups validates that referenced statuses exist before processing:

SELECT i.inst_interface_id, i.INSTANCE_STATUS_ID, s.status_code
FROM   csi.csi_instance_interface i, csi.csi_instance_statuses s
WHERE  i.INSTANCE_STATUS_ID = s.instance_status_id (+);

Related Objects

The documented foreign keys anchor this table to two parent objects: CSI_INSTANCE_STATUSES (via INSTANCE_STATUS_ID) and CSI_I_ORG_ASSIGNMENTS (via INSTANCE_OU_ID). Beyond those, the natural downstream target is CSI_INSTANCE, where successfully validated rows are loaded, along with its child tables and the concurrent manager program that executes the import. Order management interface tables such as OE_ORDER_LINES_ALL (referenced indirectly through OE_ORDER_LINE_ID) and inventory tables such as MTL_SYSTEM_ITEMS_B (via INVENTORY_ITEM_ID) supply the source context for each staged row.