Search Results eng_item_flag




Overview
Explore in AI Chat

Overview

APPS.AHL_MTL_ITEMS_NON_OU_V is a validity-verified view in the Application Object Library (APPS) schema, registered in FND Design Data under AHL.AHL_MTL_ITEMS_NON_OU_V with View Type Internal. Its purpose is to present a flattened, reporting-friendly projection of item master attributes across inventory organizations that are not bound to the current operating unit (OU) context. In Oracle EBS 12.1.1 and 12.2.2 the view supplies item definition data to Oracle Complex Maintenance, Repair, and Overhaul (AHL/ETRM) functionality and to adjacent modules that require cross-organization visibility of item characteristics without enforcing operating unit security filtering. The NON_OU suffix distinguishes it from OU-restricted item views: rows are not narrowed by MO: Operating Unit, which makes it appropriate for maintenance programs that operate on assets and rotables shared by multiple organizations.

Because this is an Oracle internal-use object, Oracle Corporation does not support direct access to applications data through it except from standard Oracle Applications programs. Customers may query it for diagnostics and read-only reporting, but should not build interfaces or modifications that depend upon its contract remaining stable.

Underlying Base Objects

The documented dependency set for 12.2.2 comprises the following referenced base objects:

  • MTL_SYSTEM_ITEMS_KFV (synonym to the key-flexfield item view) — supplies item identity, concatenated segments, description, and item type.
  • MTL_PARAMETERS (synonym) — supplies inventory organization context, joining organization identifiers to the organization definitions.
  • HR_ORGANIZATION_UNITS (view) — supplies organization name and organization code values.
  • HR_GENERAL (package) and HR_SECURITY (package) — provide organization hierarchy and security plumbing used in resolving which organizations are visible, without applying the operating unit predicate.

The view therefore reads primarily from the item master key flexfield view and the inventory organization parameters, enriched with organization attributes from the HR organization model. Because MTL_SYSTEM_ITEMS is a multi-organization table keyed on INVENTORY_ITEM_ID and ORGANIZATION_ID, the view exposes one row per item–organization combination (subject to any internal filtering), which is precisely the granularity ETRM requires when evaluating whether an item is usable in a given maintenance organization.

Key Columns

Common Use Cases and Queries

Typical scenarios include locating engineering items across all organizations for maintenance planning, validating whether an item is enabled and stockable before defining a maintenance work requirement, and auditing serial and lot control settings for rotable parts. A representative query returning engineering items in a given organization follows:

  • SELECT inventory_item_id, inventory_org_id, organization_code, concatenated_segments, description, eng_item_flag, service_item_flag, eam_item_type FROM apps.ahl_mtl_items_non_ou_v WHERE organization_code = 'M1' AND eng_item_flag = 'Y' AND inventory_item_status_code = 'Active';
  • SELECT organization_code, primary_uom_code, serial_nbr_cntrl_code, lot_control_code FROM apps.ahl_mtl_items_non_ou_v WHERE concatenated_segments = 'ROTABLE-1001';

Because the view applies no operating unit predicate, it is well suited to cross-OU fleet and EAM reporting, but queries against it should be constrained by organization and status to avoid full scans of the item master.