Search Results can_fulfill_electronic_flag




Overview
Explore in AI Chat

Overview

AST_COLL_REVIEW_KITS_V is a TeleSales (AST) reporting view owned by the APPS schema. It presents a consolidated, kit-level picture of deliverable kits that are composed of individual deliverables, joining kit definitions to their component deliverables and to on-hand inventory availability. The view is designed to support collection/review workflows in TeleSales, allowing the application to determine, for each kit, which deliverable items are stocked and how they may be fulfilled (electronic or physical). It exposes descriptive kit names alongside their constituent part identifiers, inventory item segment, unit of measure, organization, and on-hand quantity.

Because the view resolves availability from a specific organization and item, it functions as an integration and reporting layer between the deliverable/kit definition model (AMS_DELIVERABLES_VL, AMS_DELIV_KIT_ITEMS) and the inventory model (MTL_SYSTEM_ITEMS, MTL_ONHAND_QUANTITIES). It is a read-only construct and does not store data.

Underlying Base Objects

The view is defined over four referenced objects:

  • AMS_DELIVERABLES_VL (VIEW) — the base deliverable definition, referenced twice in the view text as aliases D1 and D2. D1 supplies the parent kit deliverable name; D2 supplies the component deliverable name, status filtering, and the electronic/physical fulfillment flags.
  • AMS_DELIV_KIT_ITEMS (SYNONYM) — the kit-item association, aliased B, linking deliverable_kit_part_id to deliverable_kit_id and carrying the kit item identifier.
  • MTL_SYSTEM_ITEMS (SYNONYM) — the inventory item master, aliased I, providing the item segment (SEGMENT1), primary UOM (PRIMARY_UOM_CODE), and ORGANIZATION_ID, joined to the deliverable via INVENTORY_ITEM_ID.
  • MTL_ONHAND_QUANTITIES (VIEW) — the on-hand quantity source, aliased C, joined to MTL_SYSTEM_ITEMS with an outer join on both inventory_item_id and organization_id, and its TRANSACTION_QUANTITY is exposed as QUANTITY via NVL(...,0).

Because the on-hand join is outer (+), kits whose components have no on-hand records still appear, with QUANTITY defaulting to zero. Note that the query includes a predicate restricting component deliverables to D2.STATUS_CODE = 'AVAILABLE'.

Key Columns

Common Use Cases and Queries

The view is typically used to report on kit composition and availability, to validate whether kit components can be fulfilled, and to drive review/collection screens in TeleSales. A representative query follows:

SELECT deliverable_kit_id, kit_name, deliverable_name,
       inventory_item, quantity, chargeback_uom,
       can_fulfill_electronic_flag, can_fulfill_physical_flag,
       organization_id
FROM   apps.ast_coll_review_kits_v
WHERE  deliverable_kit_id = :p_kit_id
ORDER  BY deliverable_name;

Common scenarios include:

  • Kit availability review — filtering on QUANTITY > 0 to identify kits whose component items are in stock.
  • Fulfillment capability checks — selecting items where CAN_FULFILL_ELECTRONIC_FLAG = 'Y' or CAN_FULFILL_PHYSICAL_FLAG = 'Y'.
  • Organization-specific reporting — constraining by ORGANIZATION_ID to scope results to a single inventory organization.
  • Item reconciliation — joining INVENTORY_ITEM to MTL_SYSTEM_ITEMS for extended item attributes.

Because name fields originate from AMS_DELIVERABLES_VL, the view honors the current-language (VL) naming of deliverables, making it suitable for multilingual reporting.