Search Results serialized_unit_id

Overview

The CUN_SERIALIZED_UNITS table is a core data object within the Oracle E-Business Suite (EBS) module CUN - Network Logistics - NATS. As indicated by its description, it serves as the master repository for serialized unit records. This table is critical for tracking individual, uniquely identifiable physical assets or items throughout their lifecycle within the logistics network. It is important to note that the ETRM metadata explicitly states this module is marked as "obsolete" and, for the specific database instance documented, the table was "Not implemented." This indicates that while the table's structure is defined, it may not be populated or actively used in all EBS deployments, particularly in later versions or specific configurations.

Key Information Stored

While the provided metadata does not list individual columns beyond the foreign keys, the table's primary purpose is to store attributes for each serialized unit. The primary key, SERIALIZED_UNIT_ID, uniquely identifies each record. Based on the documented foreign key relationships, the table logically stores critical linking information, including the unit's associated inventory ITEM_ID and ORGANIZATION_ID (from MTL_SYSTEM_ITEMS_B), its physical HZ_LOCATION_ID (from CUN_LOCATIONS), a reference to its LAST_TRANSACTION_ID (from CUN_TRANSACTIONS) for tracking the most recent activity, and a link to fixed asset accounting details via FA_DISTRIBUTION_ID.

Common Use Cases and Queries

In an active implementation, this table would be central to serialized inventory and asset tracking. Common operational and reporting use cases would include generating unit history reports, reconciling physical asset counts, and supporting audit trails. A typical query might join this table to item and location master data to list all serialized units of a specific type at a given location. For example:

• SELECT csu.serialized_unit_id, msib.segment1 item_code, hl.location_code
FROM cun_serialized_units csu,
    mtl_system_items_b msib,
    cun_locations hl
WHERE csu.item_id = msib.inventory_item_id
AND csu.organization_id = msib.organization_id
AND csu.hz_location_id = hl.location_id
AND msib.segment1 = '<ITEM>';

Another critical query would involve joining to CUN_TRANSACTIONS via LAST_TRANSACTION_ID to understand the most recent status or movement of each unit.

Related Objects

The ETRM metadata clearly defines the table's integration points within the EBS data model. The documented relationships are as follows:

• Primary Key: CUN_SERIALIZED_UNITS_PK on column SERIALIZED_UNIT_ID.
• Foreign Keys (Referenced by CUN_SERIALIZED_UNITS):
  • CUN_SERIALIZED_UNITS.HZ_LOCATION_ID references CUN_LOCATIONS.
  • CUN_SERIALIZED_UNITS.LAST_TRANSACTION_ID references CUN_TRANSACTIONS.
  • CUN_SERIALIZED_UNITS.FA_DISTRIBUTION_ID references FA_DISTRIBUTION_HISTORY.
  • CUN_SERIALIZED_UNITS.ITEM_ID and ORGANIZATION_ID reference MTL_SYSTEM_ITEMS_B.
• Foreign Key (Referencing CUN_SERIALIZED_UNITS):
  • CUN_REDO_LOG.CUN_UNIT_ID references CUN_SERIALIZED_UNITS.SERIALIZED_UNIT_ID. This suggests a logging or audit mechanism where changes to serialized units are recorded.