Results for “csi_txn_temp”

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

Overview

CSI_TXN_TEMP is a table owned by the CSI schema within the Oracle E-Business Suite Install Base module. Its two-column structure and naming convention indicate that it functions as a transient working table rather than a permanent transactional store. It is populated and consumed during the processing of counter group activity, most likely serving as a staging area where newly generated transaction identifiers are correlated to a counter group log entry before being committed to the canonical Install Base tables. Tables of this kind are typically purged or overwritten in each processing cycle and should not be treated as an authoritative system of record.

From a Data Vault modeling perspective, the ETRM heuristic classifies this object as standalone. Because no hub, link, or satellite characteristics dominate its structure, it is best modeled as a technical staging object outside the core Data Vault model, or as a link if the parent processing semantics are treated as a relationship between a counter group log event and a generated transaction.

Key Information Stored

The documented physical schema for 12.2.2 contains only two columns, so the substantive content is correspondingly narrow:

• COUNTER_GRP_LOG_ID — The foreign key to CS_COUNTER_GRP_LOG and, simultaneously, the single column of the primary key PK_CSI_TXN_TEMP. It identifies the counter group log entry to which the temporary row belongs.
• NEW_TRANSACTION_ID — The identifier of a transaction generated during counter group processing. This is the payload of the temporary row, held pending assignment or further validation.

Because COUNTER_GRP_LOG_ID is both the surrogate primary key and the sole unique index column, the table enforces a one-row-per-counter-group-log-entry constraint for the duration of processing. Business-key interpretation is therefore limited to the counter group log identifier itself; there is no independent business key on the transaction side. Consumers should treat the pairing as transient and expect rows to be removed once reconciliation against the permanent transaction table completes.

Common Use Cases and Queries

Diagnostic and reconciliation activity is the primary practical use of this table. Support engineers typically inspect it when counter group processing appears stalled or when transaction identifiers appear not to have propagated into the main Install Base transaction tables.

A representative query joining the temporary rows back to their controlling log entry:

• SELECT t.counter_grp_log_id, t.new_transaction_id, l.* FROM csi.csi_txn_temp t, cs.cs_counter_grp_log l WHERE t.counter_grp_log_id = l.counter_grp_log_id;

Other recurring patterns include detecting orphaned temporary rows whose parent log identifier does not resolve in CS_COUNTER_GRP_LOG, and counting pending rows per log entry to detect batch jobs that terminated before purge. Reporting against this table should always be time-bounded and treated as operational monitoring, not as history; because rows are transient, any trend reporting requires periodic snapshots into a persistent staging schema.

Related Objects

• CS_COUNTER_GRP_LOG — The parent table referenced by the single foreign key CSI_TXN_TEMP.COUNTER_GRP_LOG_ID. This is the controlling object for counter group processing and the only documented FK relationship.
• CSI_TXN_TEMP primary key (PK_CSI_TXN_TEMP) — The unique index on COUNTER_GRP_LOG_ID that enforces one row per log entry.
• CSI_INSTALLED_BASE / transaction tables — The eventual destination of the generated transaction identifiers; reconciliation between NEW_TRANSACTION_ID values and permanent transaction records is the standard validation step.
• CS_COUNTER_GRP / CS_COUNTER_VALUES — The counter group definition and value tables that drive the log entries referenced here.
• CSI_ITEM_INSTANCES — The installed base entity affected by the transactions generated during processing.
• Concurrent programs in the CSI and CS modules — The batch jobs that populate, consume, and purge this temporary table.