Results for “grade_control_flag”

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

Overview

MTL_SYSTEM_ITEMS_ER1_V is an APPS-owned view in the Oracle E-Business Suite Inventory (INV) module, defined with VALID status. Its documented purpose is to support the ERES (Electronic Records and Electronic Signatures) framework for items. In regulated environments subject to 21 CFR Part 11, ERES requires that item master attributes be presented in a structured, human-readable form suitable for electronic review, approval, and signature capture. This view supplies the descriptive and decoded item attributes that the ERES framework renders on item definition and change screens, rather than serving as a general-purpose transactional reporting object.

The view is a denormalized read-only projection that joins the core item master tables with organization, category, subinventory default, and item translation data, and applies lookup decoding through the INV_MEANING_SEL package. Because these decodings convert coded values into their meanings, the view is well suited for audit trail display and for integration interfaces that must emit item attribute changes in a reviewable format for signature workflows.

Underlying Base Objects

The documented base objects for this view include both tables and supporting views and packages. The central item data originates from MTL_SYSTEM_ITEMS_B_KFV, the key flexfield view over the item master, and MTL_SYSTEM_ITEMS_TL, which holds translated item descriptions and long descriptions. Organization context is supplied by HR_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL. Category information is drawn through MTL_ITEM_CATALOG_GROUPS_KFV and FA_CATEGORIES_B_KFV.

Additional supporting objects include MTL_PARAMETERS, MTL_ITEM_SUB_DEFAULTS, MTL_ITEM_LOCATIONS_KFV, RCV_ROUTING_HEADERS, and OKS_COVERAGE_TEMPLTS_V. Security and decoding logic rely on the HR_SECURITY and HR_GENERAL packages plus the INV_MEANING_SEL package, which performs the lookup translation in the SELECT list. The view therefore spans item definition, organization, category, receiving, service coverage, and security data to assemble a complete ERES-facing record.

Key Columns

• INVENTORY_ITEM_ID, ORGANIZATION_ID — the composite key identifying the item within an organization.
• ORGANIZATION_CODE, NAME — the operating unit or inventory organization code and name from the organization tables.
• CONCATENATED_SEGMENTS — the item flexfield concatenated key, and the category concatenated segments from the category flexfield.
• DESCRIPTION, LONG_DESCRIPTION — item description fields sourced from MTL_SYSTEM_ITEMS_TL.
• INVENTORY_ITEM_STATUS_CODE, INVENTORY_ITEM_FLAG, STOCK_ENABLED_FLAG, MTL_TRANSACTIONS_ENABLED_FLAG — item status and material control indicators.
• RESTRICT_SUBINVENTORIES_CODE — decoded via INV_MEANING_SEL.C_MFG_LOOKUP against the MTL_SUBINVENTORY_RESTRICTIONS lookup, controlling which subinventories an item may be assigned to.
• RESTRICT_LOCATORS_CODE — decoded against MTL_LOCATOR_RESTRICTIONS, controlling locator assignment.
• LOCATION_CONTROL_CODE, RESERVABLE_TYPE — location and reservation control settings.
• LOT_CONTROL_CODE, SERIAL_NUMBER_CONTROL_CODE, SHELF_LIFE_CODE — lot, serial, and shelf-life control attributes.
• PRIMARY_UOM_CODE, SECONDARY_UOM_CODE, DUAL_UOM_DEVIATION_HIGH/LOW — unit of measure and dual UOM tolerance attributes.
• SUBINVENTORY_CODE — default subinventory information.

Common Use Cases and Queries

The most frequent use of this view is within the ERES framework for item master review and approval, and in custom compliance reports that require decoded item attributes. The query below retrieves item subinventory restriction data for a given organization, which is the typical pattern when the term restrict_subinventories is the search target.

SELECT inventory_item_id, organization_code, concatenated_segments, description, restrict_subinventories_code FROM apps.mtl_system_items_er1_v WHERE organization_id = :org_id AND restrict_subinventories_code IS NOT NULL;

Analysts also use it to produce an audit-ready listing of item controls across organizations, filtering on lot, serial, or locator restrictions, and to feed interface tables where lookup meanings are required in place of codes. Because decoding is performed inline by INV_MEANING_SEL, callers should expect the values in restriction columns to appear as lookup meanings rather than raw codes, and should validate this behavior in their target instance before relying on the output for transactional integration.