Results for “cun_transactions”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CUN_TRANSACTIONS is a transaction history table belonging to the CUN – Network Logistics – NATS product family within Oracle E-Business Suite. The metadata explicitly classifies this module as obsolete and confirms that the object is not implemented in the current database. It therefore does not represent a live, supported structure in EBS 12.1.1 or 12.2.2, and any reference to it should be treated as historical or documentation-only. The table was designed to record the transactional activity of serialized and non-serialized network units, capturing both the current transaction and the chain of prior and related transactions affecting each unit.
From a Data Vault modeling perspective, the mined FK structure suggests this table is hub-leaning. Its primary key, TRANSACTION_ID, is a surrogate key, while the self-referencing foreign keys to RELATED_TRANSACTION_ID and LAST_TRANSACTION_ID behave more like intra-hub links than attributes of a dependent satellite. This heuristic indicates that CUN_TRANSACTIONS served as a central anchor for transaction identities, with other unit tables referencing it as the authoritative source of the latest transaction state.
Key Information Stored
The metadata documents a limited but meaningful set of columns. The most important are:
- TRANSACTION_ID — the surrogate primary key (CUN_TRANSACTIONS_PK), uniquely identifying each transaction record.
- RELATED_TRANSACTION_ID — a self-referencing foreign key pointing back to CUN_TRANSACTIONS, used to associate transactions that are logically connected (for example, a reversal, correction, or paired movement).
- LAST_TRANSACTION_ID — a self-referencing foreign key that identifies the preceding transaction for the same logical entity, forming an in-table chain of transaction history.
No unique business-key indexes are documented in the supplied metadata; TRANSACTION_ID is the only confirmed unique identifier. Additional descriptive columns (such as unit identifiers, transaction types, dates, or statuses) are not enumerated in the source excerpt and should not be assumed. The table's essential role is to store the transaction identity and the relational pointers that link transactions into historical sequences.
Common Use Cases and Queries
In a network logistics context, this table supported reconstruction of a unit's movement or status history. Typical queries would resolve the latest transaction for a serialized or non-serialized unit, or walk the self-referencing chain to audit prior activity:
- Latest transaction lookup — join CUN_SERIALIZED_UNITS or CUN_NON_SERIALIZED_UNITS to CUN_TRANSACTIONS on LAST_TRANSACTION_ID to retrieve the most recent transaction for each unit.
- Transaction chain traversal — use a hierarchical or recursive query on LAST_TRANSACTION_ID to walk backward through history.
- Related transaction analysis — filter on RELATED_TRANSACTION_ID to identify reversals, corrections, or paired movements.
Because the object is not implemented in the database, these patterns apply only to historical or legacy implementations and cannot be executed against a standard EBS 12.1.1 or 12.2.2 instance.
Related Objects
The FK relationship data identifies the following significant dependencies:
- CUN_SERIALIZED_UNITS — references CUN_TRANSACTIONS via LAST_TRANSACTION_ID, linking serialized units to their latest transaction.
- CUN_NON_SERIALIZED_UNITS — references CUN_TRANSACTIONS via LAST_TRANSACTION_ID, performing the same role for non-serialized units.
- CUN_TRANSACTIONS (self-reference) — RELATED_TRANSACTION_ID and LAST_TRANSACTION_ID both reference the same table, creating the internal transaction history chain.
These four relationships constitute the documented object graph. No views, PL/SQL APIs, or additional dependent tables are specified in the supplied metadata, and given the obsolete status of the module, none should be assumed to exist in a supported Oracle EBS release.
-
Table: CUN_TRANSACTIONS 12.2.2
Transaction history table
Not implemented in this database·Explore CUN module →
-
Table: CUN_TRANSACTIONS 12.1.1
Transaction history table
Not implemented in this database·Explore CUN module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
View: CUN_TRANSACTION_HIST_V 12.1.1
Business view of the transaction history for transaction type 'ISSUE_TO_PROJECT'
Not implemented in this database·Explore CUN module →
-
Table: CUN_SERIALIZED_UNITS 12.1.1
Serialized unit table
Not implemented in this database·Explore CUN module →
-
Table: CUN_SERIALIZED_UNITS 12.2.2
Serialized unit table
Not implemented in this database·Explore CUN module →
-
Non-serialized unit table
Not implemented in this database·Explore CUN module →
-
Non-serialized unit table
Not implemented in this database·Explore CUN module →
-
View: CUN_TRANSACTION_HIST_V 12.2.2
Business view of the transaction history for transaction type 'ISSUE_TO_PROJECT'
Not implemented in this database·Explore CUN module →
-
View: CUN_AP_PA_INVOICES_V 12.1.1
AP Invoices for NL tracked items to Oracle Projects
Not implemented in this database·Explore CUN module →
-
View: CUN_AP_PA_INVOICES_V 12.2.2
AP Invoices for NL tracked items to Oracle Projects
Not implemented in this database·Explore CUN module →
-
View: CUN_TRANSACTIONS_V 12.1.1
Business view of transaction history
Not implemented in this database·Explore CUN module →
-
View: CUN_TRANSACTIONS_V 12.2.2
Business view of transaction history
Not implemented in this database·Explore CUN module →