Results for “build_in_wip_flag”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AHL_MTL_ITEMS_OU_V view is a seeded, VALID database object owned by the APPS schema within the AHL – Complex Maintenance Repair and Overhaul product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to retrieve items from all inventory organizations that fall under a given operating unit. In this sense the view acts as an operating-unit-scoped, flattened access layer over Oracle Inventory master item data, removing the need for callers to join MTL_SYSTEM_ITEMS_KFV, HR_ORGANIZATION_UNITS, and MTL_PARAMETERS explicitly. From a reporting and integration standpoint, it is typically consumed by AHL-dependent concurrent programs, Oracle Reports, OBIEE/BI Publisher datasets, and custom PL/SQL that must present item definitions limited to the organizations the caller is authorized to see.

Underlying Base Objects

The view text is defined over three primary objects, joined on ORGANIZATION_ID:

  • MTL_SYSTEM_ITEMS_KFV (synonym over the key-flexfield item view) — supplies the item attributes (item number, description, control codes, flags, UOM, status).
  • HR_ORGANIZATION_UNITS (view) — supplies the organization name.
  • MTL_PARAMETERS (synonym) — supplies the organization code and the EAM_ENABLED_FLAG.

Operating-unit filtering is achieved through a correlated subquery on ORG_ORGANIZATION_DEFINITIONS, which restricts ORGANIZATION_ID values to organizations whose OPERATING_UNIT matches the operating unit derived from the session USERENV('CLIENT_INFO') — the standard EBS mechanism for reading the current organization context set by the multi-org / MO security layer. The documented referenced objects also include HR_GENERAL, HR_SECURITY, and MO_GLOBAL packages, which support this multi-org security resolution. Because the view depends on session security context, its result set varies by user and by the operating unit currently selected in the Navigator.

Key Columns

Common Use Cases and Queries

Typical uses include validating that an item number exists within an operating unit, listing service or traceable items for MRO scheduling, and populating LOVs in AHL customization.

  • Locate an item by concatenated segments:
    SELECT inventory_item_id, inventory_org_id, organization_code, description FROM ahl_mtl_items_ou_v WHERE concatenated_segments = :item_number;
  • List service-enabled items:
    SELECT organization_code, concatenated_segments, primary_uom_code FROM ahl_mtl_items_ou_v WHERE service_item_flag = 'Y' AND enabled_flag = 'Y';
  • Join to inventory organizations for reporting:
    SELECT a.concatenated_segments, a.organization_name, a.eam_item_type FROM ahl_mtl_items_ou_v a WHERE a.inventory_item_flag = 'Y';

Because results are filtered by the session operating unit, ad hoc queries outside the EBS forms environment should be run using a valid CLIENT_INFO context, or through the MO_GLOBAL initialization API, to ensure the expected organizations are returned.