Search Results csi_object_version_number




Overview
Explore in AI Chat

Overview

The AHL_UNIT_HEADER_DETAILS_V view in the APPS schema belongs to the Oracle Complex Maintenance Repair and Overhaul (AHL) product family and is delivered as a VALID database object in both Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the query used to retrieve valid Unit Configuration header details. A unit configuration represents a tracked, serialized asset instance whose maintenance history, structure, and ownership are managed through the AHL module; this view consolidates that header-level information into a single denormalized, read-only projection.

The view is oriented toward reporting, inquiry, and integration rather than transactional data entry. By joining unit configuration headers to item instance records, party (owner) details, master configuration headers and relationships, item master descriptions, WIP entities, and lookup meanings, it delivers a business-friendly result set suitable for concurrent programs, OAF pages, BI Publisher reports, and inbound/outbound interface logic that must resolve a unit configuration to its owning party and defining item.

Underlying Base Objects

The view is defined over the following documented base objects:

  • AHL_UNIT_CONFIG_HEADERS (SYNONYM) — the primary driving table, supplying the unit configuration header identifier, status, name, master configuration reference, and item instance linkage.
  • CSI_ITEM_INSTANCES (SYNONYM) — the Install Base instance record, providing object version, serial number, location, and inventory context.
  • CSI_INST_PARTY_DETAILS_V (VIEW) — resolves the party associated with the instance for the relationship type of OWNER.
  • AHL_MC_HEADERS_VL (VIEW) and AHL_MC_RELATIONSHIPS (SYNONYM) — supply master configuration name, revision, description, and root position reference.
  • MTL_SYSTEM_ITEMS_KFV (SYNONYM) — supplies concatenated item segments and item description.
  • WIP_ENTITIES (SYNONYM) — resolves WIP job names when the owner location type is WIP.
  • FND_LOOKUPS (VIEW) — outer-joined for configuration status and position reference meanings.
  • AHL_UTIL_UC_PKG (PACKAGE) and FND_GLOBAL (PACKAGE) — invoked for location code/description resolution and environment context.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all active units owned by a party, resolving a serial number to its master configuration and item, and retrieving object version numbers for integration or optimistic concurrency checks.

  • Retrieve owner units for a party:
SELECT UNIT_CONFIG_HEADER_ID, NAME, SERIAL_NUMBER, ITEM_NUMBER,
       OWNER_NAME, STATUS_MEANING
FROM   APPS.AHL_UNIT_HEADER_DETAILS_V
WHERE  OWNER_ID = :p_party_id;
  • Resolve a serialized item to its configuration:
SELECT MASTER_CONFIG_NAME, MASTER_CONFIG_REVISION, ITEM_NUMBER,
       CSI_OBJECT_VERSION_NUMBER
FROM   APPS.AHL_UNIT_HEADER_DETAILS_V
WHERE  SERIAL_NUMBER = :p_serial;
  • Extract object version tokens for an integration feed:
SELECT UNIT_CONFIG_HEADER_ID, OBJECT_VERSION_NUMBER,
       CSI_OBJECT_VERSION_NUMBER, CSI_PARTY_OBJECT_VERSION_NUM
FROM   APPS.AHL_UNIT_HEADER_DETAILS_V;

Because the view joins multiple Install Base and AHL objects, queries should filter on indexed columns such as UNIT_CONFIG_HEADER_ID, CSI_ITEM_INSTANCE_ID, SERIAL_NUMBER, or OWNER_ID to avoid full scans.