Results for “cun_non_serialized_items_v”

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

Overview

CUN_NON_SERIALIZED_ITEMS_V is a reporting view belonging to the CUN — Network Logistics — NATS product family within Oracle E-Business Suite. Its documented purpose is to select details of non-serialized Network Logistics (NL) tracked items. In environments where NATS is deployed, this view exposes the inventory, project, vendor, and fixed-asset attributes associated with non-serialized units recorded in the CUN_NON_SERIALIZED_UNITS table, presenting them in a denormalized form that is convenient for reporting, reconciliation, and downstream integration.

It should be noted that the CUN — Network Logistics — NATS module is flagged as obsolete in the ETRM metadata. In typical Oracle EBS 12.1.1 and 12.2.2 installations the view is not implemented in the database, meaning the definition exists for reference and historical purposes but the object may not be physically present unless the NATS product was specifically installed and configured. Consultants should verify object existence in the target instance via ALL_VIEWS or DBA_VIEWS before relying on it in custom code.

Underlying Base Objects

The view is defined over a single primary driving table and a series of joined reference and descriptive tables. The documented base objects include:

• CUN_NON_SERIALIZED_UNITS (CNSU) — the primary table holding non-serialized unit records, including item, organization, quantity, status, and network attributes.
• MTL_SYSTEM_ITEMS_KFV (ITEM) — key flexfield view supplying the concatenated item segment and description.
• HR_ORGANIZATION_UNITS (INV_ORG) — inventory organization name.
• MTL_ITEM_LOCATIONS_KFV (LOC) — locator concatenated segments.
• PO_VENDORS (VEND) — vendor name data.
• PA_TASKS (TASK) and PA_PROJECTS_ALL (PROJ) — project and task context.
• CUN_LOCATIONS_V (CUL) — NL network location code and description.
• FA_DISTRIBUTION_HISTORY (FA_DIST_HIST), FA_ADDITIONS_V (FA_ADD), and FA_LOCATIONS_KFV (FA) — fixed asset distribution, addition, and location attributes.
• FND_LOOKUP_VALUES (FND_LOOK) — supplies the decoded status meaning and description.

Joins are predominantly outer joins (denoted by the (+) operator) against inventory organization, locator, and other ancillary tables, ensuring that records appear even where peripheral data is absent.

Key Columns

• NON_SERIALIZED_UNIT_ID, ITEM_ID, ORGANIZATION_ID — core identifying keys for the unit and item context.
• INV_ITEM, DESCRIPTION — item concatenated segments and description.
• QUANTITY, STATUS, STATUS_NAME — unit quantity and the decoded lookup meaning of the status code.
• SUBINVENTORY, LOCATOR_ID, LOCATOR, REVISION, LOT_NUMBER — inventory placement and control attributes.
• CONCATENATED_SEGMENTS, ASSET_NUMBER, ASSET_DESCRIPTION, TAG_NUMBER — fixed asset identification and account combination output.
• NETWORK_NUMBER, VENDOR_NAME, HZ_LOCATION_ID, NETWORK_LOCATION_CODE — NL network and vendor context.
• PROJECT_NUMBER, TASK_NUMBER — project and task references.
• SERIAL_NUMBER, VENDOR_SERIAL_NUMBER — explicitly returned as NULL, reflecting the non-serialized nature of the tracked items.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical usages include inventory status reporting for non-serialized NL items, reconciliation between CUN units and fixed asset additions, and project/task-based asset tracking extracts. A representative query is:

SELECT v.inv_item, v.description, v.quantity, v.status_name,
  v.inv_organization_name, v.locator, v.asset_number
FROM cun_non_serialized_items_v v
WHERE v.organization_id = :p_org_id
  AND v.project_number = :p_project
ORDER BY v.inv_item;

Because the view is documented as obsolete and frequently not implemented, the recommended practice is to confirm its presence in the specific instance, and where absent, replicate the required columns through a custom query against CUN_NON_SERIALIZED_UNITS and its associated master tables.