Search Results shippable_item_flag

Overview

OKX_SYSTEM_ITEMS_V is an APPS-owned database view that exposes inventory item definitions to the Oracle E-Business Suite contracts integration layer (OKX). It provides a denormalized, reporting-friendly projection of item master attributes that Oracle Order Management, Oracle Service Contracts, and related OKX processes require when validating, pricing, and processing contract lines that reference inventory items. Because the view returns a single row per organization/item combination and carries flattened key flexfield segments alongside operational flags, it serves as a stable integration surface that shields downstream logic from the underlying multi-table structure of the item master. The view is documented as VALID and is intended primarily for read access — typically through custom reports, extracts, and contract integration lookups.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, OKX_SYSTEM_ITEMS_V is defined over two referenced base objects:

• MTL_SYSTEM_ITEMS_B_KFV (VIEW) — the key flexfield–flattened variant of MTL_SYSTEM_ITEMS_B, supplying item identifiers, the concatenated flexfield segments, and the descriptive and control flags (for example SHIPPABLE_ITEM_FLAG, SERVICE_ITEM_FLAG, INVOICEABLE_ITEM_FLAG).
• MTL_SYSTEM_ITEMS_TL (SYNONYM) — the translation-level table that supplies the item DESCRIPTION (aliased as NAME in the view text) for the applicable language.

The view joins these objects on inventory item and organization, producing the aliased ID1 and ID2 columns used for internal joins. No DML is expected through this view; it is read-only.

Key Columns

The view exposes identifiers, descriptions, key flexfield segments, and a broad set of item control flags. Notable columns include:

• ID1 / INVENTORY_ITEM_ID and ID2 / ORGANIZATION_ID — primary join keys for the item within an inventory organization.
• NAME — the translated item description; DESCRIPTION — the concatenated flexfield segments.
• SHIPPABLE_ITEM_FLAG — the column cited in the user's search; indicates whether the item may be shipped. It is critical in contract and order validation.
• SERVICE_ITEM_FLAG, SERVICEABLE_PRODUCT_FLAG, VENDOR_WARRANTY_FLAG, COVERAGE_TEMPLATE_ID — service-contract-relevant attributes.
• CUSTOMER_ORDER_ENABLED_FLAG, CUSTOMER_ORDER_FLAG, INTERNAL_ORDER_FLAG, ATP_FLAG — ordering and availability controls.
• INVOICEABLE_ITEM_FLAG, INVOICE_ENABLED_FLAG, PURCHASING_ENABLED_FLAG, LIST_PRICE_PER_UNIT — billing and pricing attributes.
• B_STATUS / STATUS — status derived via DECODE(ENABLED_FLAG,'Y','A','I'), and INVENTORY_ITEM_STATUS_CODE.
• SEGMENT1–SEGMENT20 — flattened key flexfield segments for reporting and filtering.
• GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1–7 — descriptive flexfield placeholders.

Common Use Cases and Queries

Typical scenarios include validating shippable items for a contract, extracting serviceable products, and reporting item attributes by organization. A representative query filtered on the searched column follows:

• Shippable item lookup: SELECT inventory_item_id, organization_id, name, shippable_item_flag FROM okx_system_items_v WHERE shippable_item_flag = 'Y';
• Serviceable products: filter on serviceable_product_flag = 'Y' for contract entitlement configuration.
• Billing extract: select invoiceable_item_flag, list_price_per_unit, and segment columns for pricing reports.
• Status reconciliation: compare STATUS with INVENTORY_ITEM_STATUS_CODE to detect disabled items.

Because the view is owned by APPS, all statements should be qualified with the APPS schema or executed under an EBS application responsibility with appropriate read privileges.