Results for “csi_inst_transactions_v”

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

Overview

CSI_INST_TRANSACTIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSI – Install Base product. It presents instance transaction activity drawn from the Install Base transaction table and enriches it with descriptive attributes from the associated item instance, inventory item, and application user records. The view is registered as VALID and functions as a denormalized read-only layer over the transactional core of Install Base.

Its principal role is to support reporting, inquiry, and integration use cases in which consumers need transaction context—such as transaction type, source references, quantity, and instance identifiers—without joining multiple Install Base and inventory tables manually. Because the view resolves the item instance context for each transaction row, it is a natural starting point for reporting on moves, splits, merges, and other lifecycle events that affect installed assets. The view is available in both Oracle EBS 12.1.1 and 12.2.2; the 12.2.2 documented definition additionally references the "_H" history synonyms used by the Install Base history/audit framework.

Underlying Base Objects

The view is defined over CSI_TRANSACTIONS as the primary transactional source, aliased as T. The transaction_id column is projected directly from this table. The remaining objects supply descriptive context:

• CSI_ITEM_INSTANCES (alias CII) — supplies instance_number and internal instance_id for the affected item instance.
• MTL_SYSTEM_ITEMS (alias MSI) — supplies the item description.
• MTL_SYSTEM_ITEMS_KFV — supplies concatenated_segments for the item's key flexfield.
• FND_USER (alias FU) — supplies user_name for the transacting user, projected as TXN_USER_NAME.
• CSI_ITEM_INSTANCES_H — the history synonym, used in the 12.2.2 documented definition alongside CSI_ITEM_INSTANCES.

The documented ETRM base object list also names the CSI history and detail synonyms, including CSI_IEA_VALUES(_H), CSI_II_RELATIONSHIPS(_H), CSI_IP_ACCOUNTS(_H), CSI_I_ASSETS(_H), CSI_I_ORG_ASSIGNMENTS(_H), CSI_I_PARTIES(_H), CSI_I_PRICING_ATTRIBS(_H), and CSI_I_VERSION_LABELS(_H). These support the instance-level attributes exposed through the view and its history-aware resolution logic.

Key Columns

The most frequently referenced column is TRANSACTION_ID, which uniquely identifies the Install Base transaction and is the value most users search for. Other significant columns include:

• INSTANCE_ID / INSTANCE_NUMBER — internal identifier and user-facing number of the affected item instance.
• TRANSACTION_DATE and SOURCE_TRANSACTION_DATE — the effective date of the transaction and the date of the originating source event. The projected alias is spelled TRASACTION_DATE.
• TRANSACTION_TYPE_ID and TXN_SUB_TYPE_ID — classify the transaction.
• SOURCE_GROUP_REF_ID / SOURCE_GROUP_REF, SOURCE_HEADER_REF_ID / SOURCE_HEADER_REF, SOURCE_LINE_REF_ID / SOURCE_LINE_REF — link the transaction back to the originating document hierarchy.
• INV_MATERIAL_TRANSACTION_ID — ties the Install Base transaction to the corresponding Inventory material movement.
• TRANSACTION_QUANTITY and TRANSACTION_UOM_CODE — quantity and unit of measure moved.
• TRANSACTION_STATUS_CODE, TRANSACTION_ACTION_CODE, and SPLIT_REASON_CODE — status, action, and split rationale.
• OBJECT_VERSION_NUMBER and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — record concurrency and audit information.
• ATTRIBUTE1–15 and CONTEXT — the descriptive flexfield segments.
• DESCRIPTION, CONCATENATED_SEGMENTS, TXN_USER_NAME — item and user descriptors joined from the base objects.

Common Use Cases and Queries

Typical usage includes audit reporting on instance movements, reconciliation between Install Base and Inventory transactions, and extracting transaction detail for downstream interfaces. A common starting query retrieves a transaction by its identifier:

• SELECT transaction_id, instance_number, transaction_type_id, transaction_date, transaction_quantity FROM csi_inst_transactions_v WHERE transaction_id = :p_transaction_id;
• SELECT instance_number, transaction_date, source_header_ref, source_line_ref, source_group_ref FROM csi_inst_transactions_v WHERE instance_id = :p_instance_id ORDER BY transaction_date;
• SELECT t.transaction_id, t.inv_material_transaction_id, t.transaction_status_code FROM csi_inst_transactions_v t WHERE t.inv_material_transaction_id IS NOT NULL;

These patterns align directly with the columns projected by the view and are supported by the documented base object joins.