Search Results primary_interest_code




Overview

AST_INV_ITEM_LOV_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined under the AST (TeleSales) product family. It serves as the inventory item list of values (LOV) source for the TeleSales application, presenting a filtered and pre-joined result set of inventory items that are eligible for selection within TeleSales flows. Rather than querying MTL_SYSTEM_ITEMS directly, TeleSales forms and concurrent programs reference this view so that only items belonging to active, purchase-related product hierarchy categories are returned. The view is documented as VALID in ETRM 12.2.2 and is available in both 12.1.1 and 12.2.2 environments since its underlying objects are core inventory and TeleSales schema objects common to both releases.

Underlying Base Objects

The view is defined over four documented base objects:

The joins are driven by inventory item, organization, category, and category set identifiers, with language filtering applied through USERENV('LANG') on both translated and hierarchy sources. The PURCHASE_INTEREST = 'Y' predicate and the DISABLE_DATE check restrict the result set to currently valid, purchase-interested category parents. A FIRST_ROWS hint with ORDERED join order and an ORDER BY on the uppercased concatenated item segments support efficient LOV presentation.

Key Columns

Common Use Cases and Queries

TeleSales developers and integrators use this view as the item LOV query source, typically joining back to the inventory item master for additional attributes. A representative query is:

  • SELECT inventory_item_id, organization_id, concatenated_segments, item_description FROM apps.ast_inv_item_lov_v WHERE UPPER(concatenated_segments) LIKE :search ORDER BY concatenated_segments;

Because the requested search term "primary_interest_code" corresponds to a NULL-projected column, users querying that column will always receive null results. When interest code data is required, the correct source is the underlying ENI product hierarchy tables, not this LOV view. This distinction is critical for report authors who may otherwise expect populated values.