Search Results cun_asset_units_v

Overview

CUN_ASSET_UNITS_V is a reporting view belonging to the CUN (Network Logistics – NATS) product family, which is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2. The view presents asset unit information, consolidating inventory item attributes, fixed asset attributes, and transaction history into a single denormalized record per unit. Its principal purpose is to give operational and reporting users a unified picture of each asset unit — what it is, where it resides, which fixed asset it relates to, its current status, and the most recent transaction associated with it.

A significant design characteristic, noted in the object documentation dated 27 July 2000, is that valid unit STATUS values are not hard-coded. Instead, the view joins to FND_LOOKUP_VALUES for the lookup type CUN_UNIT_STATUS so that any newly added status codes defined in the lookup are automatically considered. The commented-out predicate STATUS IN ('IN_SERVICE','OUT_OF_SERVICE','RETIRED','IN_INV_DEPR','ISSUED','INSTALLED') illustrates the values that were previously frozen into the query before the lookup-driven approach was adopted.

This view is not implemented in the reference database shipped with the documentation, meaning it exists only in environments where the CUN/NATS schema objects were installed. Any adoption should therefore begin with a data dictionary check. Its role is primarily read-only reporting and integration rather than transactional processing.

Underlying Base Objects

The view text is defined over three objects:

• CUN_ITEMS_V — the driving view supplying item, inventory organization, locator, serial, asset, project, vendor, and grouping element columns. Aliased as CIV.
• CUN_TRANSACTIONS_V — supplies service, retirement, transaction, installation, and effective dates plus the work order number. Aliased as CTV.
• FND_LOOKUP_VALUES — the standard Oracle Application Object Library lookup table, joined on lookup type CUN_UNIT_STATUS and the unit status code. Aliased as FLV.

The join between items and transactions is an outer join on CIV.LAST_TRANSACTION_ID = CTV.TRANSACTION_ID (+), so a unit with no recorded last transaction is still returned. The lookup join is likewise outer (FLV.LOOKUP_TYPE(+) and FLV.LOOKUP_CODE(+)), constrained by FLV.LANGUAGE = USERENV('LANG'), ensuring only the session-language lookup row is matched. No base tables are documented as directly referenced; the view is layered entirely on the two CUN views and the lookup table.

Key Columns

Columns fall into four logical groups:

• Unit and item identity: UNIT_ID, INV_ITEM_ID, INV_ITEM, DESCRIPTION, SERIAL_NUMBER, VENDOR_SERIAL_NUMBER, REVISION, LOT_NUMBER.
• Inventory placement: INVENTORY_ORG_ID, INV_ORGANIZATION_NAME, SUBINVENTORY, LOCATOR_ID, LOCATOR, QUANTITY.
• Status: STATUS (the code joined to CUN_UNIT_STATUS), INV_STATUS_NAME, and STATUS_DESCRIPTION.
• Fixed asset and financial linkage: FA_DISTRIBUTION_ID, FA_DIST_LOCATION_ID, FIXED_ASSET_LOCATION, ASSET_ID, ASSET_NUMBER, ASSET_DESCRIPTION, ASSET_TAG_NUMBER, ASSET_SERIAL_NUMBER, ASSET_TYPE, CURRENT_UNITS, CATEGORY_TYPE, ASSET_MANUFACTURER_NAME.
• Location, project, and vendor: HZ_LOCATION_ID, CLLI_CODE, LOC_DESCRIPTION, PROJECT_ID, PROJECT_NUMBER, PROJECT_TASK_ID, TASK_NUMBER, NETWORK_NUMBER, VENDOR_ID, VENDOR_NAME, plus grouping elements 1–3.
• Transaction dates: IN_SERVICE_DATE, ASSET_RETIREMENT_DATE, TRANSACTION_DATE, INSTALLED_DATE, EFFECTIVE_DATE, and WORK_ORDER_NUMBER.
• Audit: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and REFERENCE_DATA.

Common Use Cases and Queries

Typical uses include asset unit registers by organization, status-based operational dashboards, reconciliation between inventory units and fixed assets, and project or network asset tracking.

Listing active units within an inventory organization:

• SELECT unit_id, inv_item, serial_number, status, inv_organization_name FROM cun_asset_units_v WHERE status = 'IN_SERVICE' AND inventory_org_id = :org_id;

Reconciling units to fixed assets without a tag number:

• SELECT unit_id, inv_item, asset_number FROM cun_asset_units_v WHERE asset_number IS NOT NULL AND asset_tag_number IS NULL;

Reporting transaction and service dates:

• SELECT unit_id, work_order_number, transaction_date, in_service_date, asset_retirement_date FROM cun_asset_units_v ORDER BY transaction_date DESC;

Because status values are drawn from the CUN_UNIT_STATUS lookup, queries should be validated against that lookup rather than assuming the historical hard-coded list. As the CUN/NATS module is obsolete, users on 12.1.1 or 12.2.2 should confirm object existence in their instance before relying on the view for production reporting.