Search Results atp_components_flag

Overview

ASO_I_ITEMS_V is a valid, reportable view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the ASO – Order Capture product family and serves as a simplified, single-source projection of system item master data for use by order capture, order management, and related integration flows. The view is defined directly over MTL_SYSTEM_ITEMS_VL, the multilingual system items view, and inherits its core identification, planning, pricing, and descriptive attributes, plus the concatenated segment column that presents the item's flexfield key in a single readable string.

Because it is a view rather than a table, ASO_I_ITEMS_V stores no data of its own. Its role is to present the item definition in a form tailored to order capture logic, exposing flags and attributes that determine whether an item can be ordered, priced, shipped, or serviced. For the user search term "customer_order_flag," this view is the relevant access point: CUSTOMER_ORDER_FLAG is one of the columns selected from MTL_SYSTEM_ITEMS_VL and exposed by ASO_I_ITEMS_V.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: MTL_SYSTEM_ITEMS_VL (VIEW). ASO_I_ITEMS_V is therefore a thin wrapper — its SELECT list is drawn entirely from that multilingual item view, with no joins, unions, or supplementary tables appended. MTL_SYSTEM_ITEMS_VL is the language-aware layer over the MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_TL pair, so items returned by ASO_I_ITEMS_V reflect the item's base definition (B) joined with the translated description (TL) for the session's language. The view additionally surfaces the concatenated flexfield segments (CONCATENATED_SEGMENTS and PADDED_CONCATENATED_SEGMENTS) generated by the key flexfield structure defined on the item master.

Key Columns

The view exposes a broad set of item attributes. The most significant include:

• INVENTORY_ITEM_ID and ORGANIZATION_ID — the composite key identifying an item within a specific inventory organization.
• CUSTOMER_ORDER_FLAG and CUSTOMER_ORDER_ENABLED_FLAG — indicate whether the item is orderable by customers and whether that capability is currently enabled; these are the columns most relevant to the user's search.
• SHIPPABLE_ITEM_FLAG, ATP_FLAG, and ATP_COMPONENTS_FLAG — control shipping eligibility and available-to-promise participation.
• PRIMARY_UOM_CODE and PRIMARY_UNIT_OF_MEASURE — the item's primary stocking and transaction unit.
• ITEM_TYPE, INVENTORY_ITEM_STATUS_CODE, INVENTORY_ITEM_FLAG, ENABLED_FLAG, START_DATE_ACTIVE, and END_DATE_ACTIVE — define item classification and lifecycle validity.
• LIST_PRICE_PER_UNIT — the base list price carried into pricing calculations.
• SERVICE_ITEM_FLAG and related SERVICE_* columns — support service-enabled ordering scenarios.
• CONCATENATED_SEGMENTS and PADDED_CONCATENATED_SEGMENTS — the human-readable flexfield key, and DESCRIPTION for the translated item name.
• ATTRIBUTE1 through ATTRIBUTE15 and the GLOBAL_ATTRIBUTE columns — the descriptive flexfield segments available for customer-specific extension.

Common Use Cases and Queries

ASO_I_ITEMS_V is typically queried to validate that an item is orderable before it is added to an order line, to populate item LOVs in ASO-based order capture screens, or to feed downstream integrations that require the concatenated segment rather than the numeric item ID. A common pattern filters specifically on the customer order flags:

SELECT inventory_item_id, organization_id, concatenated_segments, description, customer_order_flag, customer_order_enabled_flag FROM apps.aso_i_items_v WHERE organization_id = :org_id AND customer_order_flag = 'Y' AND customer_order_enabled_flag = 'Y' AND NVL(enabled_flag,'Y') = 'Y' AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);

Because the view carries no organization filter of its own, callers must always constrain ORGANIZATION_ID to avoid returning the same item across multiple inventory organizations. Joins to pricing, ATP, or order line tables are performed on INVENTORY_ITEM_ID plus ORGANIZATION_ID, matching the base item master key.