Search Results cun_transactions

Overview

The CUN_TRANSACTIONS table is a transaction history table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases. It belongs to the CUN (Network Logistics - NATS) product family, which is documented as obsolete. This table serves as a central ledger for recording transactional events, likely pertaining to the movement or status changes of logistical units within the now-deprecated NATS (Network Asset Tracking System) module. Its primary role was to maintain a historical audit trail, enabling traceability and state management for serialized and non-serialized inventory or assets tracked by the system.

Key Information Stored

While the provided metadata does not list specific columns beyond key identifiers, the table's structure is defined by its primary and foreign key relationships. The core identifier is the TRANSACTION_ID, which serves as the primary key (CUN_TRANSACTIONS_PK). Crucially, the table employs a self-referencing design to link transactions in a chain or hierarchy. This is implemented through the RELATED_TRANSACTION_ID and LAST_TRANSACTION_ID columns, which are foreign keys referencing the TRANSACTION_ID within the same CUN_TRANSACTIONS table. These columns are essential for understanding the sequence of events and the relationship between different transactional steps for a given logistical unit.

Common Use Cases and Queries

Given its function as a history table, primary use cases involve auditing and reconstructing the lifecycle of a unit. Common reporting would trace all transactions for a specific serialized or non-serialized unit by joining through the CUN_SERIALIZED_UNITS or CUN_NON_SERIALIZED_UNITS tables. A typical query pattern would retrieve a chronological transaction chain for a unit using the self-referencing foreign keys. For example, to find the complete history stemming from an initial transaction, one might use a hierarchical query (CONNECT BY) on the RELATED_TRANSACTION_ID or LAST_TRANSACTION_ID columns. Analytical reporting would also aggregate transaction counts or types over a period to assess logistical activity. As the module is obsolete, these queries are most relevant for historical data migration, archival reporting, or supporting legacy business processes still running on the deprecated functionality.

Related Objects

The CUN_TRANSACTIONS table has documented foreign key relationships with several other tables in the obsolete CUN module, forming the core of its data model:

• CUN_TRANSACTIONS (Self-Referencing): The table references itself twice. The column CUN_TRANSACTIONS.RELATED_TRANSACTION_ID is a foreign key to CUN_TRANSACTIONS.TRANSACTION_ID, and the column CUN_TRANSACTIONS.LAST_TRANSACTION_ID is also a foreign key to CUN_TRANSACTIONS.TRANSACTION_ID. This creates a linked list or tree structure for transaction sequences.
• CUN_NON_SERIALIZED_UNITS: This table references CUN_TRANSACTIONS via its LAST_TRANSACTION_ID column (foreign key to CUN_TRANSACTIONS.TRANSACTION_ID), linking a unit to its most recent state-changing transaction.
• CUN_SERIALIZED_UNITS: Similarly, this table references CUN_TRANSACTIONS via its LAST_TRANSACTION_ID column (foreign key to CUN_TRANSACTIONS.TRANSACTION_ID), linking a serialized asset to its latest transaction.

It is critical to note the ETRM metadata explicitly states this table is "Not implemented in this database," indicating it may not be present in a standard installation and its use was likely confined to specific, now-discontinued implementations of the NATS module.