Search Results csi_source_ib_types




Overview
Explore in AI Chat

Overview

CSI_SOURCE_IB_TYPES is a reference and association table within the Oracle E-Business Suite Install Base (CSI) module. Its documented purpose is to define the relationship between source transaction types and the Install Base transaction types that are applicable to them. In practice, this table acts as the mapping layer that tells the Install Base application which inbound source transactions (for example, those originating from Order Management, Purchasing, or Manufacturing) are permitted to drive which Install Base transaction types and sub-types.

The object is owned by the CSI schema and is marked VALID in the ETRM 12.2.2 registry, with a documented physical schema of 14 columns. The heuristic Data Vault classification mined from the foreign key structure is standalone, suggesting that no parent hub or link dependency is enforced beyond the security group reference. From a modeling perspective, this table is best treated as a configuration or cross-reference entity whose composite key binds a source transaction type to an applicable Install Base transaction type.

Key Information Stored

The table is keyed by a composite unique index, CSI_SOURCE_IB_TYPES_U01, defined over TRANSACTION_TYPE_ID, SUB_TYPE_ID, and ZD_EDITION_NAME. This triple forms the business-key candidate for the row. The two leading columns, TRANSACTION_TYPE_ID and SUB_TYPE_ID, together constitute the documented primary key of CSI_SOURCE_IB_TYPES, and they identify the specific Install Base transaction type and sub-type combination being configured.

The most significant remaining columns carry the operational semantics of the association:

Note that the surrogate identity in this design is the composite (TRANSACTION_TYPE_ID, SUB_TYPE_ID); there is no single-column sequence primary key. ZD_EDITION_NAME extends the unique constraint to support edition-based configuration variants.

Common Use Cases and Queries

Typical use cases include diagnosing why an inbound source transaction failed to create or update an Install Base instance, and reporting on the configured source-to-IB mappings for a given operating unit. A representative query retrieves all applicable IB transaction types for a source type, honoring security:

  • SELECT transaction_type_id, sub_type_id, default_flag, update_ib_flag FROM csi_source_ib_types WHERE security_group_id = :sgid;
  • Filter on SEEDED_FLAG = 'Y' to isolate Oracle-delivered mappings, or MIGRATED_FLAG = 'Y' to isolate migrated configurations.
  • Join to the transaction type definition tables on TRANSACTION_TYPE_ID and SUB_TYPE_ID to resolve descriptive names for reporting.

Administrators and support analysts also consult this table when troubleshooting Install Base transaction processing, since the DEFAULT_FLAG and UPDATE_IB_FLAG settings directly influence runtime behavior.

Related Objects

The documented foreign key relationship ties CSI_SOURCE_IB_TYPES.SECURITY_GROUP_ID to FND_SECURITY_GROUPS, so any query requiring security context joins these two. Beyond that, the composite key columns TRANSACTION_TYPE_ID and SUB_TYPE_ID imply joins to the CSI transaction type definition and sub-type tables that describe the Install Base transaction catalog. The table is referenced during Install Base transaction processing by the CSI transaction APIs. Related reporting frequently draws on CSI_ITEM_INSTANCES and the Install Base transaction history tables to correlate configured mappings with actual instance updates, and on the Order Management and Purchasing source tables whose transaction types are mapped here.