Results for “parts_loop_id”

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

Overview

The view APPS.CSP_AVAILABLE_PARTS_IN_LOOP_V belongs to the Spares Management module (CSP) in Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented purpose is to check the availability of a part within a given parts loop and to return a list of all subinventories associated with that loop. A parts loop is a logical grouping of subinventories used by depot repair and spares operations to define where a spare part may be sourced from or replenished. This view therefore bridges the physical on-hand inventory layer with the loop configuration layer, exposing, per loop, organization, subinventory, and item revision, a computed availability figure for the item.

Its principal role is reporting and integration: it allows users and downstream processes to answer the recurring question "what quantity of this part is available in this loop?" without manually joining loop definitions to on-hand quantities. The user search term available_quantity maps directly to the column produced by this view, which is not stored but derived at query time through a server-side function call.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view references the following documented base objects:

• CSP_PARTS_LOOPS_B (synonym) — the parts loop definition table. It supplies PARTS_LOOP_ID and ORGANIZATION_ID, anchoring the loop context.
• CSP_SEC_INVENTORIES (synonym) — the loop-to-subinventory mapping table. It supplies SECONDARY_INVENTORY_NAME and CONDITION_TYPE, so each row represents one subinventory valid within the loop.
• MTL_ONHAND_SUB_V (view) — the on-hand subinventory aggregation view. It supplies INVENTORY_ITEM_ID, REVISION, and the subinventory code that is joined to the loop's subinventory.
• CSP_VALIDATE_PUB (package) — invoked as CSP_VALIDATE_PUB.GET_AVAIL_QTY(...) to compute the available quantity dynamically. This is the source of the available_quantity value.
• HR_GENERAL and HR_SECURITY (packages) — supporting packages typically referenced for organizational and security context resolution within the CSP validation logic.

The joins are equality-based on ORGANIZATION_ID between the loop, its subinventories, and on-hand records, and on SECONDARY_INVENTORY_NAME = SUBINVENTORY_CODE between the loop mapping and on-hand aggregation.

Key Columns

• PARTS_LOOP_ID — identifier of the parts loop being evaluated.
• ORGANIZATION_ID — inventory organization in which the loop and on-hand are assessed.
• SUBINVENTORY_CODE — the subinventory resolved through the join to on-hand data.
• CONDITION_TYPE — the condition classification of the subinventory within the loop (for example, new or refurbished stock).
• AVAILABLE_QUANTITY — the computed availability of the item, returned by CSP_VALIDATE_PUB.GET_AVAIL_QTY using organization, subinventory, and item identifiers. Because it is function-derived, it is not indexed or stored.
• INVENTORY_ITEM_ID — the inventory item for which availability is evaluated.
• REVISION — the revision of the item present in the subinventory.

Common Use Cases and Queries

Typical uses include checking spare availability across all subinventories in a loop before a repair order is released, feeding availability screens or concurrent reports, and integrating loop-level availability into custom replenishment logic.

SELECT parts_loop_id,
       organization_id,
       subinventory_code,
       condition_type,
       inventory_item_id,
       revision,
       available_quantity
  FROM apps.csp_available_parts_in_loop_v
 WHERE parts_loop_id = :p_loop_id
   AND organization_id = :p_org_id
   AND available_quantity > 0;

A second common pattern aggregates availability per item across a loop:

SELECT inventory_item_id,
       SUM(available_quantity) available_qty
  FROM apps.csp_available_parts_in_loop_v
 WHERE organization_id = :p_org_id
 GROUP BY inventory_item_id;

Because availability is computed per row via a PL/SQL call, performance-sensitive queries should filter aggressively on loop, organization, and item before aggregating.