Search Results cun_serialized_items_v

Overview

The CUN_SERIALIZED_ITEMS_V view belongs to the CUN – Network Logistics – NATS product family, a module designated as Obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes attribute-level details of serialized items that are tracked within the Network Logistics (NL) framework, consolidating inventory, asset, project, and vendor context into a single query surface. Rather than requiring downstream reports or interfaces to join the serialized unit table against inventory item definitions, asset records, project structures, and vendor master data individually, the view presents a pre-joined projection suitable for operational and analytical reporting.

The documented implementation note states that the view is not implemented in this database, which is consistent with the obsolete status of the CUN/NATS module. Organizations on 12.1.1 or 12.2.2 that still rely on NATS lineage will typically encounter this view in legacy customizations, historical report definitions, or migration inventories rather than in actively supported flows.

Underlying Base Objects

The view text defines an inner-join base on CUN_SERIALIZED_UNITS (aliased CSU), with outer joins to most of the auxiliary sources. The principal referenced objects are:

• MTL_SYSTEM_ITEMS_KFV — key flexfield view supplying item concatenated segments, description, and organization context.
• HR_ORGANIZATION_UNITS — inventory organization name.
• MTL_ITEM_LOCATIONS_KFV — locator concatenated segments.
• PO_VENDORS — vendor name for the originating supplier.
• PA_PROJECTS_ALL and PA_TASKS — project number and task number.
• CUN_LOCATIONS_V — NL network location code and description.
• FA_DISTRIBUTION_HISTORY and FA_LOCATIONS_KFV — asset distribution history and the asset location flexfield.
• FA_ADDITIONS_V — asset master attributes (asset number, tag, serial, category, manufacturer).
• FND_LOOKUP_VALUES — decoding of the CSU.STATUS column into a meaning and description.

Documented ETRM metadata lists no referenced base objects beyond the view text itself, so the join topology above is the authoritative reference for lineage.

Key Columns

• SERIALIZED_UNIT_ID — primary identifier of the serialized unit record.
• ITEM_ID, INV_ITEM, DESCRIPTION — item identity and descriptive text.
• ORGANIZATION_ID, INV_ORGANIZATION_NAME — owning inventory organization.
• QUANTITY, STATUS, STATUS_NAME, STATUS_DESCRIPTION — quantity on hand and the decoded status meaning via FND_LOOKUP_VALUES.
• SUBINVENTORY, LOCATOR_ID, LOCATOR — storage location detail.
• REVISION, LOT_NUMBER — revision and lot control attributes.
• SERIAL_NUMBER1, VENDOR_SERIAL_NUMBER, NETWORK_NUMBER — serial and NL network identifiers.
• ASSET_ID, ASSET_NUMBER, TAG_NUMBER, ASSET_TYPE, CATEGORY_TYPE, MANUFACTURER_NAME — fixed asset linkage.
• PROJECT_ID, PROJECT_NUMBER, TASK_ID, TASK_NUMBER — project and task associations.
• VENDOR_ID, VENDOR_NAME — source vendor.
• ASSET_GROUPING_ELEMENT1..3, REFERENCE_DATA — NL-specific grouping attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical usage centers on inventory-asset reconciliation, vendor serial tracking, and project-to-serialized-item reporting for NATS-tracked stock.

• Listing all serialized items in a given organization with status decoded and asset linkage.
• Reconciling serialized units against FA_ADDITIONS to detect missing asset creation.
• Reporting serialized units by project and task for capital or program accounting.

Sample query:

SELECT INV_ITEM, SERIAL_NUMBER1, STATUS_NAME, INV_ORGANIZATION_NAME, ASSET_NUMBER, PROJECT_NUMBER, VENDOR_NAME FROM CUN_SERIALIZED_ITEMS_V WHERE ORGANIZATION_ID = :org_id ORDER BY INV_ITEM, SERIAL_NUMBER1;

Because the object is obsolete and documented as not implemented in the reference database, any dependent query should be validated against the specific EBS instance prior to deployment, and migration to supported inventory serialization views (for example, MTL_SERIAL_NUMBERS-based queries) should be considered where possible.