Results for “purchasing_item_flag”

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

Overview

APPS.AHL_MTL_ITEMS_NON_OU_V is a valid database view owned by the APPS schema and shipped as part of the AHL (Complex Maintenance Repair and Overhaul) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose inventory item definitions drawn from all inventory organizations without regard to Operating Unit (OU) boundaries. The view's description states explicitly that it retrieves items from all inventory organizations and that the item's organization need not reside in the same Operating Unit as the querying responsibility. This makes it a cross-OU read model rather than a transactional or secured data source.

Within EBS, this view is used for reporting, integration, and internal AHL processing where a maintenance or MRO workflow must resolve item attributes across the enterprise. Because item master and item organization data are normally subject to Operating Unit and organization security, the view provides a denormalized, read-only projection that bypasses OU scoping while still restricting results to EAM-enabled organizations.

Underlying Base Objects

The documented base objects for the 12.2.2 metadata are:

• MTL_SYSTEM_ITEMS_KFV (SYNONYM) — the key flexfield-enabled view over MTL_SYSTEM_ITEMS, aliased KFV, supplying the item core attributes.
• MTL_PARAMETERS (SYNONYM) — aliased MP, supplying inventory organization parameters and the MASTER_ORGANIZATION_ID linkage.
• HR_ORGANIZATION_UNITS (VIEW) — aliased HOU, supplying the organization name.
• HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE) — referenced for organization/security resolution as used by the AHL layer.

The join logic is driven from MTL_PARAMETERS: MP.MASTER_ORGANIZATION_ID = HOU.ORGANIZATION_ID and KFV.ORGANIZATION_ID = MP.ORGANIZATION_ID, with a filter of MP.EAM_ENABLED_FLAG = 'Y'. SELECT DISTINCT is applied, and the organization code is obtained through a subquery on MTL_PARAMETERS, while the description is obtained through a subquery on MTL_SYSTEM_ITEMS_KFV for the master organization. As synonyms are used in 12.2.2, the physical tables are typically MTL_SYSTEM_ITEMS_B/TL (via the KFV view), MTL_PARAMETERS, and HR_ORGANIZATION_UNITS.

Key Columns

• INVENTORY_ITEM_ID — surrogate key identifying the item.
• INVENTORY_ORG_ID — populated from MP.MASTER_ORGANIZATION_ID, i.e. the item master organization rather than the transaction organization.
• ORGANIZATION_NAME / ORGANIZATION_CODE — the organization's display name and its MTL_PARAMETERS organization code.
• ITEM_TYPE — item type classification (for example standard, kit, or AHL-specific types).
• CONCATENATED_SEGMENTS — the concatenated item key flexfield segments.
• DESCRIPTION — the item description resolved for the master organization.
• REVISION_QTY_CNTRL_CODE — the revision quantity control code, exposed under this alias though the underlying column is KFV.REVISION_QTY_CONTROL_CODE; it determines whether revision and lot/serial quantity control applies to the item. This is the column most directly referenced by the search term "revision_qty_cntrl_code".
• LOT_CONTROL_CODE / SERIAL_NBR_CNTRL_CODE — lot and serial number control codes.
• COMMS_NL_TRACKABLE_FLAG, SERVICE_ITEM_FLAG, MTL_TRANSACTIONS_ENABLED_FLAG — flags governing communications/non-ledger tracking, service items, and transaction enablement.
• EAM_ITEM_TYPE, BUILD_IN_WIP_FLAG, WIP_SUPPLY_TYPE, ENG_ITEM_FLAG — EAM and manufacturing-relevant attributes.
• ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE — item enablement and effective dating.

Common Use Cases and Queries

Typical scenarios include enterprise-wide item reporting, cross-OU maintenance lookups, and validation of revision and quantity control settings for EAM-enabled organizations. Because results are not OU-restricted, the view suits centralized reporting but should not be used for transactional posting.

Listing EAM-enabled items with their revision control setting:

• SELECT INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, ORGANIZATION_CODE, REVISION_QTY_CNTRL_CODE FROM APPS.AHL_MTL_ITEMS_NON_OU_V WHERE REVISION_QTY_CNTRL_CODE IS NOT NULL;
• SELECT ORGANIZATION_CODE, COUNT(*) FROM APPS.AHL_MTL_ITEMS_NON_OU_V GROUP BY ORGANIZATION_CODE;
• SELECT INVENTORY_ITEM_ID, DESCRIPTION, LOT_CONTROL_CODE, SERIAL_NBR_CNTRL_CODE FROM APPS.AHL_MTL_ITEMS_NON_OU_V WHERE ENABLED_FLAG = 'Y' AND MTL_TRANSACTIONS_ENABLED_FLAG = 'Y';

Note the DISTINCT and correlated subqueries can affect performance on large item masters; restrict by ORGANIZATION_CODE or ENABLED_FLAG where possible.