Results for “mtl_mfg_components_v”
38 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MTL_MFG_COMPONENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Inventory (INV) product family. It consolidates work in process (WIP) component demand and material transaction activity into a single denormalized row set, exposing both the manufacturing job context and the component-level transaction detail. The view is primarily used by inventory and manufacturing reporting, by Oracle Manufacturing Execution System (MES) style dashboards, and by integrations that require a flattened read of component issue activity against discrete jobs.
Because the object is a view rather than a table, it carries no independent storage or indexes. Its performance characteristics are inherited entirely from the base tables it joins. The view is classified as VALID in the ETRM registry for both 12.1.1 and 12.2.2, and its referenced base objects are consistent across those releases. In 12.2.2 the documented base objects include the GME_MATERIAL_DETAILS synonym, reflecting the shared use of process manufacturing material detail data alongside discrete WIP structures.
Underlying Base Objects
The view is defined over a join of WIP and inventory tables. The documented referenced base objects are: GME_MATERIAL_DETAILS, HR_GENERAL (package), HR_ORGANIZATION_UNITS (view), HR_SECURITY (package), MTL_MATERIAL_TRANSACTIONS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS_KFV, MTL_TRANSACTION_LOT_NUMBERS, MTL_UNIT_TRANSACTIONS, WIP_ENTITIES, and WIP_REQUIREMENT_OPERATIONS.
- WIP_ENTITIES and WIP_REQUIREMENT_OPERATIONS supply the job header and component requirement lines, joined on WIP_ENTITY_ID.
- MTL_SYSTEM_ITEMS_KFV provides the concatenated item number and description for both product and component, keyed by INVENTORY_ITEM_ID and ORGANIZATION_ID.
- MTL_MATERIAL_TRANSACTIONS supplies transaction date, type, subinventory, and locator; it is joined to the requirement operation and restricted to TRANSACTION_SOURCE_TYPE_ID = 5 (WIP).
- MTL_TRANSACTION_LOT_NUMBERS and MTL_UNIT_TRANSACTIONS supply lot, grade, and serial number detail.
- MTL_PARAMETERS, HR_ORGANIZATION_UNITS, HR_GENERAL, and HR_SECURITY provide organization context and organization-level security filtering.
- GME_MATERIAL_DETAILS supports process manufacturing component detail.
Key Columns
The column list is dominated by identifiers, quantities, and descriptive attributes. Notable columns include:
- GEN_OBJECT_ID, WIP_ENTITY_ID, WIP_ENTITY_NAME — job identity for the manufacturing order.
- ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — the inventory organization context.
- PRODUCT_ITEM_ID (aliased from PRIMARY_ITEM_ID) and ITEM_NUMBER — the assembled product.
- INVENTORY_ITEM_ID, ITEM_DESCRIPTION, PRIMARY_UOM_CODE, SECONDARY_UOM_CODE — the component item attributes.
- ITEM_TYPE — a literal constant returned as 'COMPONENT', which is significant for the "item_type" search context; it allows the view to be unioned with product-level queries while retaining a discriminator.
- JOB_QUANTITY (from REQUIRED_QUANTITY) — required component quantity on the job.
- TRANSACTION_QUANTITY, PRIMARY_QUANTITY, SECONDARY_QUANTITY — issued quantities, resolved via DECODE so that serialized items return 1 and lot-controlled items fall back to transaction or lot quantities.
- LOT_NUMBER, GRADE_CODE, SERIAL_NUMBER and the PRODUCT_LOT_NUMBER / PRODUCT_SERIAL_NUMBER — traceability detail.
- TRANSACTION_DATE, TRANSACTION_TYPE_ID, SUBINVENTORY_CODE, LOCATOR_ID — transaction location and timing.
Common Use Cases and Queries
Typical scenarios include component issue reconciliation, WIP material variance reporting, and traceability lookups for lot and serial controlled assemblies. Organizations also use the view to feed MES dashboards showing components consumed per job. A basic query listing components for a specific job:
SELECT wip_entity_name, item_number, item_description, item_type, job_quantity, transaction_quantity, transaction_date, subinventory_code
FROM apps.mtl_mfg_components_v
WHERE wip_entity_name = :job_name
ORDER BY item_number;
Filtering by the discriminator is useful when the view is combined with other sources:
SELECT inventory_item_id, lot_number, transaction_quantity
FROM apps.mtl_mfg_components_v
WHERE item_type = 'COMPONENT'
AND organization_id = :org_id
AND transaction_date >= :from_date;
Because no indexes are owned by the view, queries should be filtered on WIP_ENTITY_ID, ORGANIZATION_ID, or transaction date to allow the optimizer to drive from the selective base tables. Runtime cost is dominated by the joins to MTL_MATERIAL_TRANSACTIONS and the unit transaction tables, so restricting the date range is strongly recommended in production reporting.
-
View: MTL_MFG_COMPONENTS_V 12.2.2
APPS.MTL_MFG_COMPONENTS_V·↳ GME_MATERIAL_DETAILS·↳ HR_GENERAL·↳ HR_ORGANIZATION_UNITS·Explore INV module →
-
View: MTL_MFG_COMPONENTS_V 12.1.1
APPS.MTL_MFG_COMPONENTS_V·↳ GME_MATERIAL_DETAILS·↳ HR_GENERAL·↳ HR_ORGANIZATION_UNITS·Explore INV module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
SYNONYM: APPS.WIP_ENTITIES 12.2.2
-
SYNONYM: APPS.WIP_ENTITIES 12.1.1
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person