Search Results asset_retirement_date




Overview

CUN_ASSET_ADDITIONS_UNITS_V is a reporting view belonging to the CUN – Network Logistics – NATS product family, a module that Oracle has classified as obsolete within the EBS 12.1.1 and 12.2.2 release streams. The view consolidates Fixed Asset information, exposing a flattened, denormalized projection that joins asset unit data with fixed asset additions and distribution history. Its purpose is to provide a single query surface for reporting on capitalized assets together with their associated inventory unit records, including status, serial number, manufacturer, and depreciation book assignment.

The view carries significant diagnostic value for the user term "asset_status." The column ASSET_STATUS is surfaced directly from the underlying CUN_ASSET_UNITS_V source, meaning any query filtering or grouping by asset status will resolve against that column. Because the object is documented as not implemented in the reference database, deployments must confirm its existence before relying on it in custom reports or interfaces.

Underlying Base Objects

The view text defines three physical sources. The primary driver is CUN_ASSET_UNITS_V, aliased CAU, which contributes asset identity, description, type, status, serial number, unit quantity, tag number, category, retirement date, manufacturer, in-service date, and the key identifiers ASSET_UNIT_ID, ASSET_ID, INV_ITEM_ID, and INVENTORY_ORG_ID. FA_DISTRIBUTION_HISTORY, aliased FA_DIST, is joined on the equality condition CAU.FA_DISTRIBUTION_ID = FA_DIST.DISTRIBUTION_ID and supplies BOOK_TYPE_CODE. FA_ADDITIONS_V, aliased FAV, is outer-joined on CAU.ASSET_ID = FAV.ASSET_ID, contributing model number, parent asset, lease number, and lessor.

Note that the documented metadata lists no referenced base objects, and the view is recorded as not implemented in the source database. The join structure nonetheless reveals a hard dependency on the distribution history table and an outer dependency on the additions view, so a strict inner-join requirement is imposed by FA_DISTRIBUTION_HISTORY while FA_ADDITIONS_V information may be null where no addition record exists.

Key Columns

Common Use Cases and Queries

Typical usage involves asset status reporting, inventory-to-fixed-asset reconciliation, and lease or parent-asset analysis. Because the view is obsolete, it should be treated as a legacy reporting object and validated against the target instance before inclusion in concurrent programs or integrations.

A representative query retrieving assets by status with their book assignment:

  • SELECT asset_number, description, asset_status, asset_tag_number, book_type_code FROM cun_asset_additions_units_v WHERE asset_status = 'IN SERVICE';
  • SELECT asset_category, COUNT(*) FROM cun_asset_additions_units_v GROUP BY asset_category;
  • SELECT asset_number, quantity, in_service_date FROM cun_asset_additions_units_v WHERE in_service_date >= :p_start_date;

These patterns illustrate the view's role as a convenience layer over unit, addition, and distribution data, with ASSET_STATUS serving as the principal selection predicate.