Results for “cun_non_serialized_units”

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

Overview

CUN_NON_SERIALIZED_UNITS is a transactional data object belonging to the CUN – Network Logistics – NATS product family within Oracle E-Business Suite. The ETRM metadata explicitly designates this module as obsolete, and the object itself is documented as "Not implemented in this database." Consequently, the table is encountered most often during upgrade, migration, or archival analysis of legacy NATS-enabled environments rather than in active production installations running release 12.1.1 or 12.2.2.

Functionally, the table represents non-serialized inventory units tracked within the Network Logistics NATS framework. Unlike serial-controlled items, which are individually identified, non-serialized units are managed at the quantity or lot level while still retaining unit-level attributions such as location, distribution history, and last transaction. This makes the table a historical record of unit movement and distribution state.

Applying a heuristic Data Vault classification drawn from the foreign-key structure, CUN_NON_SERIALIZED_UNITS leans toward a satellite: it carries descriptive and transactional context (location, item, last transaction, distribution history) keyed by its own surrogate identifier, referencing multiple hub-like dimension tables. This classification is a modeling suggestion only and should be validated against the actual column cardinality and business rules in a given implementation.

Key Information Stored

The table is anchored by the primary key constraint CUN_NON_SERIALIZED_UNITS_PK, defined on the column NON_SERIALIZED_UNIT_ID. This surrogate identifier is the documented key for the unit record and is the column referenced by dependent tables. The most significant columns documented in the ETRM metadata are:

• NON_SERIALIZED_UNIT_ID — surrogate primary key uniquely identifying each non-serialized unit record.
• HZ_LOCATION_ID — foreign key to CUN_LOCATIONS, identifying the location associated with the unit.
• LAST_TRANSACTION_ID — foreign key to CUN_TRANSACTIONS, capturing the most recent transaction applied to the unit.
• FA_DISTRIBUTION_ID — foreign key to FA_DISTRIBUTION_HISTORY, linking the unit to fixed asset distribution history.
• ITEM_ID — foreign key to MTL_SYSTEM_ITEMS_B, identifying the inventory item the unit represents.
• ORGANIZATION_ID — foreign key to MTL_SYSTEM_ITEMS_B, identifying the inventory organization context.

No alternate unique indexes or distinct business-key candidates are documented in the supplied metadata; NON_SERIALIZED_UNIT_ID is the sole documented unique identifier. Business semantics are therefore derived through the referenced foreign entities rather than through a natural key embedded in this table.

Common Use Cases and Queries

Because the table is obsolete and unimplemented, use cases are primarily historical and analytical. Typical scenarios include reconstructing unit-level movement for audit, reconciling non-serialized inventory against item master definitions, and tracing distribution history tied to fixed assets. A representative join pattern follows:

• Join CUN_NON_SERIALIZED_UNITS to MTL_SYSTEM_ITEMS_B on ITEM_ID and ORGANIZATION_ID to resolve item description and organization context.
• Join to CUN_LOCATIONS on HZ_LOCATION_ID to resolve location attributes.
• Join to CUN_TRANSACTIONS on LAST_TRANSACTION_ID to retrieve the last transaction type and date.
• Left join to FA_DISTRIBUTION_HISTORY on FA_DISTRIBUTION_ID for asset distribution lineage.
• Aggregate counts by ITEM_ID and ORGANIZATION_ID to profile non-serialized unit populations.

Before running any query, confirm the table exists in the target database; the metadata states it is "Not implemented in this database," meaning queries will fail unless the legacy schema has been deliberately retained.

Related Objects

The most significant related objects derive from the documented foreign-key relationships:

• CUN_LOCATIONS — referenced via HZ_LOCATION_ID; supplies location context.
• CUN_TRANSACTIONS — referenced via LAST_TRANSACTION_ID; supplies last transaction detail.
• FA_DISTRIBUTION_HISTORY — referenced via FA_DISTRIBUTION_ID; supplies fixed asset distribution history.
• MTL_SYSTEM_ITEMS_B — referenced via ITEM_ID and ORGANIZATION_ID; supplies item and organization definitions.
• CUN_REDO_LOG — references CUN_NON_SERIALIZED_UNITS through CUN_UNIT_ID, indicating a downstream logging or redo dependency.

Together these objects form the legacy NATS non-serialized unit chain: item and organization definitions, location and transaction context, distribution history, and redo logging around the central unit record.