Search Results csi_txn_sub_types




Overview
Explore in AI Chat

Overview

CSI_TXN_SUB_TYPES is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is delivered as part of the CSI – Install Base (Enterprise Asset Management / Install Base) product family and exposes the association between source transaction types and Install Base transaction types. In functional terms, the view answers the question: for a given Install Base sub-type and source transaction type combination, which Install Base transaction type applies, and what validation behaviour (source reference, owner change, status, return, revision) is required during the transaction?

Because it joins configuration metadata rather than transactional data, CSI_TXN_SUB_TYPES is primarily used for reporting, integration, and diagnostic purposes. It allows technical consultants to interrogate how the Install Base transaction framework has been configured without navigating multiple setup forms. The object carries a status of VALID in the ETRM repository and its text is centrally maintained by Oracle, so customers should not modify it.

Underlying Base Objects

The view is defined over four documented base objects:

  • CSI_IB_TXN_TYPES (synonym) – the core Install Base transaction type definition, providing sub-type, IB transaction type code, CS transaction type identifier, and the various SRC_/NON_SRC_/PARENT_ requirement flags.
  • CSI_SOURCE_IB_TYPES (synonym) – the relationship between source transaction types and Install Base sub-types, supplying TRANSACTION_TYPE_ID, DEFAULT_FLAG, and UPDATE_IB_FLAG.
  • CSI_LOOKUPS (view) – the seeded lookup view supplying MEANING and DESCRIPTION for IB transaction type codes under the lookup type 'CSI_IB_TXN_TYPE_CODE'.
  • CS_TRANSACTION_TYPES (synonym) – the Service (CS) transaction type table, supplying NAME and DESCRIPTION when a CS transaction type identifier is present.

The join is driven from CSI_IB_TXN_TYPES to CSI_SOURCE_IB_TYPES on SUB_TYPE_ID. Both the CSI_LOOKUPS and CS_TRANSACTION_TYPES joins are outer joins (indicated by the (+) operator), meaning rows are retained even where no matching lookup or CS transaction type exists. A DECODE expression resolves the NAME and DESCRIPTION columns, preferring the CS transaction type details when CS_TRANSACTION_TYPE_ID is populated, and falling back to the lookup meaning otherwise.

Key Columns

  • TRANSACTION_TYPE_ID – the source transaction type identifier from CSI_SOURCE_IB_TYPES.
  • SUB_TYPE_ID – the Install Base sub-type linking the two configuration tables.
  • CS_TRANSACTION_TYPE_ID – the Service transaction type identifier, where applicable.
  • IB_TXN_TYPE_CODE – the Install Base transaction type lookup code.
  • NAME / DESCRIPTION – resolved descriptively via DECODE, drawing from either the CS transaction type or the CSI_LOOKUPS meaning.
  • SRC_* columns (SRC_REFERENCE_REQD, SRC_CHANGE_OWNER, SRC_STATUS_ID, SRC_RETURN_REQD, SRC_REVISION_REQD) – behavioural requirements applying when a source transaction is present.
  • NON_SRC_* columns – equivalent requirements when no source transaction exists.
  • PARENT_* columns (PARENT_REFERENCE_REQD, PARENT_STATUS_ID, PARENT_REVISION_REQD) – requirements relating to parent instance references.
  • SEEDED_FLAG / FREEZE_FLAG – indicate Oracle-seeded versus user-defined configuration and whether the record is protected from change.
  • DEFAULT_FLAG / UPDATE_IB_FLAG – from the relationship table, indicating default selection and whether the Install Base record is updated.
  • OBJECT_VERSION_NUMBER – optimistic locking column inherited from the base transaction type table.

Common Use Cases and Queries

Typical use cases include auditing Install Base transaction setup, validating integration payloads that reference transaction types, and troubleshooting why a transaction validation fails because a required reference or owner change was not supplied.

Listing all configured combinations:

  • SELECT transaction_type_id, sub_type_id, ib_txn_type_code, name, default_flag FROM csi_txn_sub_types ORDER BY sub_type_id;

Isolating requirement flags for a specific transaction type:

  • SELECT name, src_reference_reqd, src_change_owner, non_src_reference_reqd, parent_reference_reqd FROM csi_txn_sub_types WHERE ib_txn_type_code = :code;

Identifying Oracle-seeded versus custom configuration:

  • SELECT sub_type_id, ib_txn_type_code, name, seeded_flag, freeze_flag FROM csi_txn_sub_types WHERE seeded_flag = 'N';

Because the view is a metadata join rather than a high-volume transactional source, queries typically require no special performance tuning; standard indexes on the underlying configuration tables are sufficient.