Results for “csi_src_txn_sub_types”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.CSI_SRC_TXN_SUB_TYPES view belongs to the CSI - Install Base (Oracle Installed Base) product family and exposes the relationship between transaction sources and the Installed Base transaction sub-types that apply to them. In Oracle EBS 12.1.1 and 12.2.2, Installed Base tracks customer assets, configurations, and the transactional events that create, modify, move, or terminate them. Each inbound transaction (for example, an Order Management sales order line, a shipping confirmation, or a service work order) is classified by a transaction type, and each transaction type is in turn associated with one or more Installed Base transaction sub-types. This view flattens that two-level structure into a single reporting surface, joining the transaction type master data to its corresponding sub-type mappings.

Because it presents a denormalized, read-only projection of configuration data, the view is primarily used for reporting, diagnostics, and integration. It allows developers and analysts to determine, for a given source application and source transaction, which Installed Base sub-types are valid, which sub-type is the default, and whether the transaction is inbound or outbound. This makes it a convenient lookup source for interfaces that must validate or default transaction sub-types during Installed Base processing.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• CSI_TXN_TYPES — the transaction type definition table. It provides the transaction type identifier, source application, source transaction type, descriptive attributes, the source object code, and the inbound/outbound indicator.
• CSI_SOURCE_IB_TYPES — the mapping table that links each transaction type to the Installed Base sub-types that apply to it, including default and update flags.

The two objects are joined on TRANSACTION_TYPE_ID, so the view returns one row per transaction-type/sub-type combination. This cardinality is important: a single transaction type may appear on multiple rows when it maps to more than one sub-type. The view is owned by APPS and reports a VALID status in the ETRM repository.

Key Columns

The view exposes sixteen columns. The most significant for the query term in scope are described below.

• TRANSACTION_TYPE_ID — primary join key linking the transaction type to its sub-type mappings.
• SOURCE_APPLICATION_ID — identifies the application that originates the transaction (for example, Order Management or Service).
• SOURCE_TRANSACTION_TYPE and SOURCE_TXN_TYPE_NAME — the internal code and user-facing name of the source transaction.
• DESCRIPTION and SOURCE_OBJECT_CODE — descriptive text and the originating object identifier.
• IN_OUT_FLAG — the inbound/outbound indicator. This is the column most relevant to the search term in_out_flag. It classifies whether the transaction brings an item into Installed Base (inbound, such as a shipment or receipt) or removes/updates it (outbound, such as a return or termination). Values are typically represented by single-character codes.
• SUB_TYPE_ID — the Installed Base transaction sub-type associated with the transaction type.
• DEFAULT_FLAG — indicates whether the associated sub-type is the default for the transaction type.
• UPDATE_IB_FLAG — indicates whether the transaction updates Installed Base records.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — support change tracking and optimistic locking.

Common Use Cases and Queries

Typical scenarios include identifying all Installed Base sub-types valid for a given source transaction, isolating inbound versus outbound transactions, and locating the default sub-type for interface defaulting logic.

Retrieve all sub-type mappings for a specific source transaction:

• SELECT transaction_type_id, source_transaction_type, sub_type_id, default_flag, update_ib_flag FROM csi_src_txn_sub_types WHERE source_transaction_type = :p_txn_type;

Filter by direction using the searched column:

• SELECT transaction_type_id, source_txn_type_name, sub_type_id, in_out_flag FROM csi_src_txn_sub_types WHERE in_out_flag = 'IN';

Locate the default sub-type for an integration defaulting routine:

• SELECT sub_type_id FROM csi_src_txn_sub_types WHERE transaction_type_id = :p_id AND default_flag = 'Y';

Because the view is read-only and based solely on the two documented base objects, it is safe to query directly from reports, concurrent programs, and interface validation logic without affecting Installed Base processing.