Search Results mtl_item_flexfields




Overview

The APPS.MRP_COMPONENTS_SC_V view is a supply chain components view delivered within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. Its primary role is to expose detailed bill-of-material component information for a given assembly within a specific organization, resolving the surrogate item identifiers stored in the base MRP tables into human-readable item numbers. The view is a union of multiple component scenarios, allowing reports, concurrent programs, and integration interfaces to query a single flattened source for component-level detail such as supply type, effectivity, optionality, and operation sequencing. Because it joins two instances of MTL_ITEM_FLEXFIELDS, the view is often surfaced when users search for "mtl_item_flexfields," as that object is central to translating inventory item IDs into concatenated item numbers.

Underlying Base Objects

The view is defined over a set of documented base objects owned by APPS. The central fact source is MRP_BOM_COMPONENTS (accessed via synonym), which holds the component-to-assembly relationships. MRP_SYSTEM_ITEMS provides the driving item information used in the effectivity logic. Two references to MTL_ITEM_FLEXFIELDS, aliased as ASSY_NAME and COMP_NAME, supply the assembly and component item numbers respectively. MFG_LOOKUPS (a view) resolves the WIP_SUPPLY_TYPE lookup meaning, restricted to the 'WIP_SUPPLY' lookup type. MTL_PARAMETERS supplies the organization code, and MRP_FORM_QUERY (MFQ) restricts rows to the current query context using NUMBER1, NUMBER2, and CHAR1 parameters. The joins link assembly and component flexfield views on both INVENTORY_ITEM_ID and ORGANIZATION_ID, ensuring item numbers resolve correctly within each inventory organization.

Key Columns

Common Use Cases and Queries

Typical usage includes MRP/MPS component reports, supply-chain exception analysis, and custom interfaces that require resolved item numbers rather than internal IDs. A representative query filters by organization and assembly:

  • SELECT QUERY_ID, ASSY_NAME, COMP_NAME, OPERATION_SEQ_NUM, MEANING FROM APPS.MRP_COMPONENTS_SC_V WHERE ORGANIZATION_CODE = :org AND ASSY_NAME = :assembly;
  • SELECT COMP_NAME, INVENTORY_ITEM_ID, OPERATION_SEQ_NUM FROM APPS.MRP_COMPONENTS_SC_V WHERE OPTIONAL_COMPONENT = 1 AND ORGANIZATION_ID = :org_id;
  • SELECT ASSY_NAME, COMP_NAME, DISABLE_DATE, USE_UP_CODE FROM APPS.MRP_COMPONENTS_SC_V WHERE ORGANIZATION_CODE = :org ORDER BY ASSY_NAME, OPERATION_SEQ_NUM;

Because many columns derive from MTL_ITEM_FLEXFIELDS, queries against this view require the item flexfield to be correctly compiled in the target organization; otherwise item number lookups return unexpected values.