Search Results csi_source_ib_types_u01

Overview

CSI.CSI_SOURCE_IB_TYPES is a seed data table in the Customer Intelligence (CSI) schema of Oracle E-Business Suite. It functions as a cross-reference or mapping table that defines which Installed Base (IB) transaction types are applicable to each CSI Source Transaction type. In practical terms, it answers the question: "When a source transaction of type X is processed, which Installed Base transaction types may be selected, and which of those is the system default?"

The table resides in the APPS_TS_SEED tablespace, confirming its role as reference/seed configuration rather than high-volume transactional data. From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone; it is best treated as a reference or mapping entity rather than a classic hub, link, or satellite, since it defines permissible pairings between transaction types rather than the transactions themselves. Its composite primary key (TRANSACTION_TYPE_ID, SUB_TYPE_ID) makes it a natural mapping construct.

Key Information Stored

The table contains fourteen documented columns. The most significant are:

• TRANSACTION_TYPE_ID — The CSI Source Transaction Type identifier; the driving FK in the mapping.
• SUB_TYPE_ID — The Installed Base Transaction Type identifier that is applicable to the source transaction.
• DEFAULT_FLAG — Indicates whether the paired IB transaction type is the default for the given source transaction type.
• UPDATE_IB_FLAG — Controls whether Installed Base is updated when this mapping is exercised.
• MIGRATED_FLAG — Marks rows created as part of a data migration.
• SEEDED_FLAG — Indicates whether the row is seeded by Oracle versus user-defined.
• OBJECT_VERSION_NUMBER — Optimistic locking column for concurrent updates.
• SECURITY_GROUP_ID — Security Group identifier, linked to FND_SECURITY_GROUPS.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ZD_EDITION_NAME — Editioning column used in the 12.2 Online Patching (adop) infrastructure.

Primary Key: The logical primary key is CSI_SOURCE_IB_TYPES (TRANSACTION_TYPE_ID, SUB_TYPE_ID). The unique index CSI_SOURCE_IB_TYPES_U01 — the object the user searched for — enforces this uniqueness in 12.2.2 under the editioning variant (TRANSACTION_TYPE_ID, SUB_TYPE_ID, ZD_EDITION_NAME). This index is the business-key candidate; TRANSACTION_TYPE_ID and SUB_TYPE_ID are foreign-key-style references to source and IB transaction type definitions.

Common Use Cases and Queries

Typical scenarios include determining the default IB transaction type for a given source transaction, restricting which IB transaction types are selectable in a transaction form, and validating migration/replication of seed data. Common SQL patterns include:

• Find the default IB transaction type for a source type:
  SELECT SUB_TYPE_ID FROM CSI.CSI_SOURCE_IB_TYPES WHERE TRANSACTION_TYPE_ID = :p_txn_type AND DEFAULT_FLAG = 'Y';
• List all applicable IB types for a source type:
  SELECT SUB_TYPE_ID, DEFAULT_FLAG, UPDATE_IB_FLAG FROM CSI.CSI_SOURCE_IB_TYPES WHERE TRANSACTION_TYPE_ID = :p_txn_type;
• Audit seeded versus migrated rows:
  SELECT SEEDED_FLAG, MIGRATED_FLAG, COUNT(*) FROM CSI.CSI_SOURCE_IB_TYPES GROUP BY SEEDED_FLAG, MIGRATED_FLAG;

Because it is seed-driven, change control against CSI_SOURCE_IB_TYPES should be avoided where possible, and edits are best tracked through WHO columns.

Related Objects

The table is largely self-contained but carries an FK from SECURITY_GROUP_ID to FND_SECURITY_GROUPS. The most significant related objects include:

• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for security grouping.
• CSI_SOURCE_IB_TYPES — the APPS synonym exposing this table to the applications layer.
• Source transaction type definitions in the CSI schema (referenced by TRANSACTION_TYPE_ID).
• Installed Base transaction type definitions (referenced by SUB_TYPE_ID).
• CSI transactional processing and validation programs that read the mapping during IB updates.

Because the object is standalone with limited outgoing references, its principal dependency is the APPS synonym and the seed data it carries.