Results for “cun_unit_id”

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

Overview

The view CUN_REDO_LOG_V belongs to the CUN product family — Network Logistics / NATS — within Oracle E-Business Suite. The CUN module is documented as obsolete in the ETRM reference for both 12.1.1 and 12.2.2, and this view is explicitly not implemented in the reference database. Its documented description is "Redo log infromation," indicating that it was designed to expose entries from a redo log table used by the NATS processing framework to track message transactions and their associated unit identifiers.

In its operational context, such a view served diagnostic and reconciliation purposes rather than mainstream transactional reporting. It joined a message header table (XNP_MSGS) to a redo log table (CUN_REDO_LOG) so that a redo log entry could be reported alongside the textual body of the message it referenced. Where NATS message traffic needed to be replayed or audited, this view supplied the linkage between a transaction, a message, an organizational unit, and the message payload. Because the module is obsolete, the view should be treated as legacy metadata; it will not exist in a standard, current EBS installation unless a historical CUN deployment introduced it.

Underlying Base Objects

The documented ETRM metadata records no owner and no referenced base objects; however, the view text provided in the same documentation source identifies its two underlying objects:

• CUN_REDO_LOG — the driving table, aliased C, supplying the redo log identity, transaction identifiers, audit columns, and the CUN_UNIT_ID column.
• XNP_MSGS — aliased X, supplying BODY_TEXT, the message payload.

The two are related by an outer join on the message identifier: X.MSG_ID (+) = C.MESSAGE_ID. The (+) operator makes XNP_MSGS the optional side, so every redo log row is returned even when no matching message exists. This is significant for diagnostics, since a redo log entry whose message has been purged will still appear, with a null body text. The absence of documented referenced base objects in the ETRM record is consistent with the view never having been created in the reference environment.

Key Columns

• REDO_LOG_ID — primary identifier of the redo log entry.
• TRANSACTION_ID — the transaction with which the redo entry is associated.
• MESSAGE_ID — foreign key to XNP_MSGS.MSG_ID; the join key of the view.
• CREATION_DATE, CREATED_BY — standard WHO creation audit columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO update audit columns.
• CUN_UNIT_ID — the organizational or inventory unit identifier relevant to the redo entry. This is the column most frequently searched, reflecting its role in filtering redo activity by unit.
• REDO_MESSAGE — listed among the documented columns; in the view text it is realized through X.BODY_TEXT, the message payload, returned as BODY_TEXT.

Common Use Cases and Queries

Typical usage centres on tracing redo activity for a given unit or transaction, and on identifying redo entries whose underlying message no longer exists.

• Redo activity for a specific unit: SELECT redo_log_id, transaction_id, message_id, cun_unit_id, creation_date FROM cun_redo_log_v WHERE cun_unit_id = :unit_id ORDER BY creation_date DESC;
• Redo entries for a transaction: SELECT * FROM cun_redo_log_v WHERE transaction_id = :txn_id;
• Orphaned redo entries (no matching message, exposed by the outer join): SELECT r.redo_log_id, r.message_id, r.cun_unit_id FROM cun_redo_log_v r WHERE r.body_text IS NULL;
• Audit of who generated redo entries within a date range: SELECT created_by, COUNT(*) FROM cun_redo_log_v WHERE creation_date BETWEEN :from_date AND :to_date GROUP BY created_by;

Because the CUN module is obsolete and the view is not implemented in the reference database, these queries are only meaningful against historical NATS installations. Confirm object existence in ALL_VIEWS before relying on the view in any environment.