Results for “csi_transactions”

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

Overview

CSI_TRANSACTIONS is the central transaction log table within the CSI (Install Base) product of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It records every transactional event applied against installed base entities — item instances, systems, parties, organizations, assets, accounts, pricing attributes, version labels, and relationships. Rather than storing the current state of an installed base record, CSI_TRANSACTIONS captures the intent and outcome of each create, update, split, merge, or transfer operation, and the child _H history tables reference back to it through TRANSACTION_ID to record the resulting attribute values.

The table is owned by the CSI schema and is documented as VALID in ETRM 12.2.2 with 47 columns. Under a heuristic Data Vault classification derived from its foreign-key structure, CSI_TRANSACTIONS is best modeled as hub-leaning: it carries a single surrogate key (TRANSACTION_ID) that is referenced by numerous satellites and link-style history tables, with only a small number of outbound references of its own. This makes it the natural anchor point for reconstructing the full audit trail of an installed base change.

Key Information Stored

The primary key is TRANSACTION_ID, enforced by CSI_TRANSACTIONS_PK and also by the unique index CSI_TRANSACTIONS_U01. Although CSI_TRANSACTIONS_U01 covers TRANSACTION_ID, the documented column set does not include a separate natural business key; the transaction log is therefore keyed purely by the surrogate identifier, with business context supplied through the columns below.

• TRANSACTION_ID — surrogate primary key; the value propagated into every CSI *_H history table and CSI_TXN_ERRORS.
• TRANSACTION_DATE and SOURCE_TRANSACTION_DATE — the date the transaction was processed versus the date of the originating source event.
• TRANSACTION_TYPE_ID — foreign key to CSI_TXN_TYPES, classifying the operation (for example, create, update, split, merge).
• TXN_SUB_TYPE_ID — finer-grained qualifier of the transaction type.
• SOURCE_GROUP_REF_ID, SOURCE_HEADER_REF_ID, SOURCE_LINE_REF_ID, SOURCE_DIST_REF_ID1, SOURCE_DIST_REF_ID2 — identifiers of the originating source document at group, header, line, and distribution level, paired with their SOURCE_GROUP_REF, SOURCE_HEADER_REF, and SOURCE_LINE_REF display values.
• INV_MATERIAL_TRANSACTION_ID — link to the Oracle Inventory material transaction that triggered the installed base change.
• TRANSACTION_QUANTITY and TRANSACTION_UOM_CODE — quantity and unit of measure affected.
• TRANSACTED_BY — the user or process responsible for the transaction.
• TRANSACTION_STATUS_CODE and TRANSACTION_ACTION_CODE — processing status and the action performed.
• MESSAGE_ID — correlation identifier for the concurrent request or message that produced the transaction.
• SPLIT_REASON_CODE — reason captured when a split operation occurs.
• ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — descriptive flexfield segments.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for multi-tenant data segregation.
• MIGRATED_FLAG, GL_INTERFACE_STATUS_CODE, CONTRACTS_INVOKED — flags indicating migration origin, General Ledger interface state, and whether Contracts logic was invoked.
• OBJECT_VERSION_NUMBER and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — concurrency control and audit metadata.

Common Use Cases and Queries

Typical reporting scenarios include tracing the history of a specific instance, reconciling installed base changes against Inventory or Order Management source documents, and diagnosing failed transactions. A representative query joins the log to its type and to error records:

• Audit trail by instance: join CSI_TRANSACTIONS to CSI_ITEM_INSTANCES_H on TRANSACTION_ID and filter by TRANSACTION_DATE to reconstruct the sequence of changes to a given instance.
• Error analysis: join CSI_TRANSACTIONS to CSI_TXN_ERRORS on TRANSACTION_ID where TRANSACTION_STATUS_CODE indicates failure, to enumerate rejection reasons.
• Source reconciliation: filter on SOURCE_HEADER_REF_ID or INV_MATERIAL_TRANSACTION_ID to tie installed base activity back to the originating order, shipment, or inventory issue.
• Volume and throughput reporting: aggregate counts by TRANSACTION_TYPE_ID and TRANSACTION_DATE to measure installed base activity over time.
• Contracts-linked activity: filter where CONTRACTS_INVOKED is set to isolate service contract-driven transactions.

Related Objects

CSI_TRANSACTIONS sits at the centre of a fan-out of history tables, each of which carries TRANSACTION_ID as a foreign key back to the log:

• CSI_TXN_TYPES — referenced by CSI_TRANSACTIONS.TRANSACTION_TYPE_ID; supplies the transaction classification.
• CSI_ITEM_INSTANCES_H — history of item instance attribute changes, joined on TRANSACTION_ID.
• CSI_SYSTEMS_H — history of system-level changes, joined on TRANSACTION_ID.
• CSI_II_RELATIONSHIPS_H — history of instance-to-instance relationship changes, joined on TRANSACTION_ID.
• CSI_I_PARTIES_H, CSI_I_ORG_ASSIGNMENTS_H, CSI_I_ASSETS_H, CSI_IP_ACCOUNTS_H — party, organization assignment, asset, and account history records, all joined on TRANSACTION_ID.
• CSI_I_PRICING_ATTRIBS_H, CSI_I_VERSION_LABELS_H, CSI_IEA_VALUES_H — pricing attribute, version label, and extended attribute value histories, joined on TRANSACTION_ID.
• CSI_TXN_ERRORS — error log joined on TRANSACTION_ID, capturing failures raised while applying a transaction.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for data access control.

Collectively these relationships establish CSI_TRANSACTIONS as the indispensable join point for any installed base audit, reconciliation, or troubleshooting exercise in Oracle EBS 12.1.1 and 12.2.2.