Search Results cun_transactions_v

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

Overview

CUN_TRANSACTIONS_V is a business view within the Oracle E-Business Suite product line designated CUN – Network Logistics – NATS. It exposes transaction history in a denormalized, human-readable form, joining the core transaction record stored in the CUN transaction table to a wide set of descriptive reference objects spanning inventory, purchasing, receiving, payables, assets, projects, and general ledger distribution data. The view is documented as "Business view of transaction history," indicating its intended role as a reporting and integration surface rather than a transactional entry point.

In Oracle EBS 12.1.1 and 12.2.2, the CUN module is identified in the ETRM metadata as obsolete. That status has two practical consequences. First, the view is not part of a currently supported functional flow, and customers on 12.2.x who have not implemented NATS will find the object absent or unusable. Second, the impact of the 12.1.1 to 12.2.2 upgrade on this specific object is limited, since the online patching editioning model applies to supported modules; an obsolete or non-implemented view carries no editioning view, synonym, or grant maintenance beyond what the original implementation produced.

The ETRM record states explicitly, under Implementation/DBA Data, "Not implemented in this database." This means that in the environment from which the ETRM excerpt was generated, the view does not exist as a deployable database object. The view text below is therefore retained as documentation of a historical definition rather than as an active artifact.

Underlying Base Objects

The documented metadata for this view lists no referenced base objects — "Referenced base objects: none documented." The view name and the absence of an owner field in the ETRM record are consistent with an object that was defined in a legacy or reference database but never migrated into the current environment. The dependencies that can be reconstructed from the view text reveal the alias-to-object mapping:

• CTR — the primary CUN transactions table, supplying TRANSACTION_ID, TRANSACTION_DATE, RELATED_TRANSACTION_ID, LAST_TRANSACTION_ID, and all quantity, status, lot, serial, and grouping columns.
• PER — PER_ALL_PEOPLE_F, for TRANSACTED_BY name resolution.
• FND_LOOK_TXN_TYPE, FND_LOOK_TXN_STATUS, FND_LOOK_STATUS — FND lookup views supplying meaning and description text for the coded transaction type and status columns.
• ITEM — MTL_SYSTEM_ITEMS_VL or equivalent for concatenated inventory item segments.
• INV_ORG — INV_ORGANIZATIONS_V for organization name.
• LOC — MTL_ITEM_LOCATIONS_KFV for locator concatenated segments.
• FA_ADD — FA_ADDITIONS_B for asset number and description.
• CUL — the CUN location table, keyed by CUN_LOCATION_ID.
• POD, PO, RCV_HEAD, AP_INV, AP_INV_DIST, VEND, PROJ, TASK — purchasing distributions, purchase orders, receipt headers, AP invoices and distributions, vendors, projects, and tasks.

Because these joins are constructed with outer joins, CUN_TRANSACTIONS_V is a left-anchored projection of the CUN transaction base table: every transaction row is retained regardless of whether the related purchasing, asset, or payables context exists.

Key Columns

The view exposes more than fifty columns. The most significant for reporting and reconciliation are:

• TRANSACTION_ID — primary key of the CUN transaction record.
• RELATED_TRANSACTION_ID and LAST_TRANSACTION_ID — self-referencing pointers within the CUN transaction table that chain a transaction to a predecessor or related transaction, supporting multi-step lifecycle tracing (for example, receipt followed by put-away or installation). These are the columns most relevant to users who search for relationship lineage.
• TRANSACTION_TYPE, TXN_STATUS_NAME, STATUS_NAME — codes with lookup-derived meanings and descriptions.
• TRANSACTION_QUANTITY and QUANTITY_INVOICED — quantity tracking and invoicing comparison.
• INV_ITEM, INV_ORGANIZATION_NAME, SUBINVENTORY, LOCATOR — inventory context, with locator concatenated segments for readability.
• SERIAL_NUMBER, LOT_NUMBER, REVISION, VENDOR_SERIAL_NUMBER — item instance identification.
• PO_NUMBER, DISTRIBUTION_NUM, SHIPMENT_NUMBER, INVOICE_NUM, VENDOR_NAME — procurement and payables linkage.
• MTL_TRANSACTION_ID, RCV_TRANSACTION_ID, EXPENDITURE_ITEM_ID, AP_INVOICE_DISTRIBUTION_ID — foreign keys to the corresponding Inventory, Receiving, Projects, and Payables records, enabling cross-module reconciliation.
• ASSET_NUMBER, PROJECT_NUMBER, TASK_NUMBER, WORK_ORDER_NUMBER — asset, project, and manufacturing associations.
• NETWORK_NUMBER, MESSAGE_ID, REFERENCE_DATA, ASSET_GROUPING_ELEMENT1–3 — NATS-specific network logistics attributes, generally unused outside the network asset tracking flow.
• Date columns including RECEIPT_DATE, SHIPPED_DATE, INSTALLED_DATE, IN_SERVICE_DATE, EFFECTIVE_DATE, and RETIRED_DATE — asset and receipt lifecycle timestamps.

Common Use Cases and Queries

The view was designed to answer lineage and reconciliation questions in a single query, avoiding the many joins a report developer would otherwise write. A typical use is tracing a serialized item from purchase order through receipt, inventory transaction, and invoice.

The following query returns all CUN transactions tied to a given PO and resolves the related-transaction chain, which is the pattern implied by the search term "related_transaction_id":

• SELECT transaction_id, related_transaction_id, last_transaction_id, transaction_type, txn_status_name, inv_item, serial_number, po_number, receipt_date FROM cun_transactions_v WHERE po_number = :p_po_number ORDER BY transaction_date;

To identify transactions whose related transaction is missing from the current population — a useful integrity check in legacy NATS environments — a self-join or a NOT EXISTS subquery against the view itself can be applied:

• SELECT v.transaction_id, v.related_transaction_id FROM cun_transactions_v v WHERE v.related_transaction_id IS NOT NULL AND NOT EXISTS (SELECT 1 FROM cun_transactions_v r WHERE r.transaction_id = v.related_transaction_id);

Because the ETRM record marks this object as not implemented and the module as obsolete, these queries are appropriate only for historical audits or migration assessments. Before executing them in any 12.1.1 or 12.2.2 environment, verify view existence with SELECT object_name, status FROM all_objects WHERE object_name = 'CUN_TRANSACTIONS_V'; and confirm read grants, particularly if the query runs from a custom reporting schema rather than the CUN application schema.