Search Results csi_location_id




Overview
Explore in AI Chat

Overview

The APPS.AHL_UNIT_INSTALLED_DETAILS_V view belongs to the AHL – Complex Maintenance Repair and Overhaul product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a denormalized reporting view whose stated purpose is to retrieve Install Base item instance details. The view consolidates data from Oracle Install Base (CSI), Inventory (MTL), Work in Process (WIP), Purchasing (PO), and Application Object Library (FND) so that consumers can obtain a single-row-per-item-instance representation enriched with item descriptions, statuses, owner party information, and location details. Because it is registered as a VALID view under the APPS schema, it is available to any responsibilities and concurrent programs that have been granted access to the APPS schema, which is the standard convention for Oracle seed reporting views.

The view is especially relevant when a user searches on csi_location_id, since the view explicitly exposes CSI.LOCATION_ID as the column alias CSI_LOCATION_ID. This makes the view a natural starting point for queries that need to join Install Base instances back to their owning location without navigating the underlying CSI_ITEM_INSTANCES table directly.

Underlying Base Objects

ETRM metadata records the following referenced objects for this view: AHL_UTIL_UC_PKG (package), CSI_INST_EXTEND_ATTRIB_V (view), CSI_INST_PARTY_DETAILS_V (view), CSI_ITEM_INSTANCES (synonym), CSI_LOOKUPS (view), FND_GLOBAL (package), FND_LOOKUPS (view), MTL_MATERIAL_STATUSES (synonym), MTL_PARAMETERS (synonym), MTL_SYSTEM_ITEMS_KFV (synonym), MTL_SYSTEM_ITEMS_TL (synonym), and WIP_ENTITIES (synonym).

  • CSI_ITEM_INSTANCES is the primary driving table, supplying instance identity, quantity, serial number, revision, lot, install date, and the location columns.
  • MTL_SYSTEM_ITEMS_KFV and MTL_SYSTEM_ITEMS_TL provide the concatenated item number and translated item description.
  • MTL_MATERIAL_STATUSES supplies the instance condition description, joined via INSTANCE_CONDITION_ID = STATUS_ID (+).
  • CSI_LOOKUPS and FND_LOOKUPS resolve lookup meanings for instance usage and serial-number tag codes.
  • CSI_INST_PARTY_DETAILS_V contributes owner party type, party number, and party name.
  • CSI_INST_EXTEND_ATTRIB_V is referenced twice (aliases CIEA1, CIEA2) to pull manufacturing date and serial number tag attributes.
  • WIP_ENTITIES resolves WIP job entity names for instances whose location type is 'WIP'.
  • AHL_UTIL_UC_PKG supplies the GETCSI_LOCATIONDESC and GETCSI_LOCATIONCODE PL/SQL functions used to derive the location description and owner site number. FND_GLOBAL is referenced for session context.

Key Columns

Common Use Cases and Queries

Typical uses include Install Base reporting, asset tracking dashboards, MRO work order preparation, and integration extracts. A common scenario is retrieving all instances tied to a specific location:

  • SELECT csi_item_instance_id, csi_instance_number, inventory_item_id, item_number, csi_location_id, location_description, status FROM ahl_unit_installed_details_v WHERE csi_location_id = :p_location_id;
  • SELECT csi_instance_number, serial_number, item_number, owner_name, install_date FROM ahl_unit_installed_details_v WHERE inventory_org_id = :p_org_id AND status = 'INSTALLED';
  • SELECT csi_location_id, location_description, COUNT(*) FROM ahl_unit_installed_details_v GROUP BY csi_location_id, location_description ORDER BY 3 DESC;

Because the view invokes PL/SQL functions in its SELECT list, performance-sensitive queries should filter on indexed CSI columns such as CSI_ITEM_INSTANCE_ID, INVENTORY_ITEM_ID, or INSTANCE_NUMBER rather than on derived columns like LOCATION_DESCRIPTION or OWNER_SITE_NUMBER.