Results for “cun_redo_log”

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

Overview

CUN_REDO_LOG is a table historically associated with the CUN — Network Logistics — NATS product family within Oracle E-Business Suite. Its documented description is simply "Redo log table," indicating that it was designed to record redo-style transaction or change entries generated during NATS network logistics processing. Critically, the ETRM metadata marks CUN as "obsolete," and the implementation note for this specific table states "Not implemented in this database." Practitioners encountering the name cun_redo_log in a 12.1.1 or 12.2.2 environment should therefore treat it as a legacy or dormant object rather than an active repository. Its presence in the data dictionary does not imply that it holds current transactional data.

From a modeling perspective, the metadata provides a heuristic Data Vault classification of link. This suggestion reflects the table's structure: a surrogate primary key combined with a foreign key column (CUN_UNIT_ID) that resolves to two different parent tables, which is characteristic of an associative or relationship entity. The link classification should be regarded as a modeling heuristic mined from the foreign key structure, not as a formal Data Vault design assertion.

Key Information Stored

The documented metadata exposes only a small, high-value subset of columns. The principal attributes are:

• REDO_LOG_ID — the surrogate primary key, backed by the constraint CR_PK. This column uniquely identifies each redo log entry and is the definitive row identifier.
• CUN_UNIT_ID — the foreign key column referencing unit records in the CUN unit tables. This column defines the associative relationship that drives the table's link classification.

Because the ETRM excerpt does not enumerate the full column list, no additional field names can be asserted from documented evidence. The primary key CR_PK (REDO_LOG_ID) is the surrogate; the metadata does not document any unique business-key index on this table, so no alternate business key can be confirmed. REDO_LOG_ID should not be confused with a business identifier — it is a system-generated surrogate. CUN_UNIT_ID is the meaningful relationship attribute, but it is not unique per row by construction, since a single unit may be referenced by multiple redo log entries.

Common Use Cases and Queries

In an active NATS deployment, a redo log table of this shape would support audit and recovery reporting: identifying which units were touched, tracing change sequences, and reconciling logistics transactions. On 12.1.1 and 12.2.2, however, the table is documented as not implemented, so the principal use case is impact analysis and legacy discovery rather than operational querying. A representative diagnostic query follows:

• SELECT REDO_LOG_ID, CUN_UNIT_ID FROM CUN_REDO_LOG WHERE CUN_UNIT_ID = :unit_id; — retrieve all redo entries associated with a specific unit.
• SELECT COUNT(*) FROM CUN_REDO_LOG; — confirm whether the obsolete table contains any residual rows.
• Join patterns to the two parent unit tables using CUN_UNIT_ID to determine whether a log entry points to a serialized or non-serialized unit.

These patterns are most useful when validating upgrade impact or confirming that no custom code still references the obsolete object.

Related Objects

The documented foreign key relationships identify the tables that CUN_REDO_LOG depends upon:

• CUN_SERIALIZED_UNITS — referenced via CUN_REDO_LOG.CUN_UNIT_ID.
• CUN_NON_SERIALIZED_UNITS — also referenced via CUN_REDO_LOG.CUN_UNIT_ID, indicating that unit identifiers are drawn from both serialized and non-serialized unit populations.

The dual reference to two parent tables through a single column is the structural signature that supports the link classification. Beyond these two documented relationships, no additional dependent views or APIs are evidenced in the supplied metadata.