Results for “cun_serialized_units”

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

Overview

CUN_SERIALIZED_UNITS is a table within the CUN (Network Logistics – NATS) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, CUN is flagged as obsolete, and this table is explicitly marked "Not implemented in this database." Its documented purpose is to hold serialized unit data — the individual, uniquely identifiable instances of items tracked through a network logistics or asset distribution context. In the NATS model, a serialized unit represents a discrete tracked entity whose identity, current location, and last-known transaction are recorded as attributes rather than derived on the fly.

The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. In Data Vault terms, a satellite stores descriptive attributes and context about a business key, changing over time, and typically hangs off a hub or link. Because CUN_SERIALIZED_UNITS carries the descriptive state of a serialized unit (location, last transaction, distribution history, item/organization context) while referencing multiple external hubs, it is best modeled as a satellite attached to a serialized-unit hub rather than as an independent hub or a pure associative link. This is a modeling suggestion, not a documented Oracle classification.

Key Information Stored

The primary key is CUN_SERIALIZED_UNITS_PK, defined on the surrogate column SERIALIZED_UNIT_ID. This is the technical row identifier and should not be treated as a business key; no alternate unique index is documented in the supplied metadata, so any business-key candidates would need to be confirmed against the physical schema. The most significant documented columns are:

• SERIALIZED_UNIT_ID — surrogate primary key uniquely identifying each serialized unit row.
• HZ_LOCATION_ID — foreign key to CUN_LOCATIONS, indicating the current or associated location of the unit.
• LAST_TRANSACTION_ID — foreign key to CUN_TRANSACTIONS, capturing the most recent transaction affecting the unit.
• FA_DISTRIBUTION_ID — foreign key to FA_DISTRIBUTION_HISTORY, linking the unit to fixed-asset distribution records.
• ITEM_ID — foreign key to MTL_SYSTEM_ITEMS_B, identifying the inventory item definition the serialized unit instantiates.
• ORGANIZATION_ID — foreign key to MTL_SYSTEM_ITEMS_B (composite with ITEM_ID), supplying the inventory organization context.

Because the table is not implemented, no additional descriptive column names can be asserted from the ETRM excerpt; any further attributes should be verified directly against the CUN schema should it exist in a legacy environment.

Common Use Cases and Queries

Typical reporting scenarios center on tracing a serialized unit's identity, location, and transaction history, and on reconciling units to item/organization master data. A representative join pattern:

• Resolve item context: SELECT su.serialized_unit_id, msi.segment1, msi.description FROM cun_serialized_units su JOIN mtl_system_items_b msi ON su.item_id = msi.inventory_item_id AND su.organization_id = msi.organization_id;
• Resolve current location: join HZ_LOCATION_ID to CUN_LOCATIONS to report each unit's location.
• Trace last movement: join LAST_TRANSACTION_ID to CUN_TRANSACTIONS to surface the latest activity per unit.
• Audit changes: reverse-join CUN_REDO_LOG.CUN_UNIT_ID to compare logged redo entries against current unit state.
• Asset linkage: join FA_DISTRIBUTION_ID to FA_DISTRIBUTION_HISTORY to reconcile units with fixed-asset distribution events.

Related Objects

• CUN_LOCATIONS — referenced via HZ_LOCATION_ID; supplies unit location context.
• CUN_TRANSACTIONS — referenced via LAST_TRANSACTION_ID; supplies the unit's most recent transaction.
• FA_DISTRIBUTION_HISTORY — referenced via FA_DISTRIBUTION_ID; links units to asset distribution history.
• MTL_SYSTEM_ITEMS_B — referenced via ITEM_ID and ORGANIZATION_ID; the item master definition.
• CUN_REDO_LOG — references this table via CUN_UNIT_ID, recording redo/audit entries against serialized units.

Given the obsolete status, any implementation should confirm whether CUN objects were ever deployed in the target instance before relying on these relationships.