Results for “assembly_description”

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

Overview

MTL_MFG_BATCHES_SECURITY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined over Process Manufacturing (GME) batch data and exposed within the INV — Inventory product family. Its documented purpose is to present GME batches together with security (access-controlled) information for use in product genealogy and batch traceability reporting. The view is registered as VALID across EBS 12.1.1 and 12.2.2 and is referenced by Oracle's ETRM (E-Business Suite Technical Reference Manual) repository.

The view is structurally a "union-shaped" projection: it exposes the standard batch and work-in-process (WIP) attributes needed by genealogy screens and concurrent programs, while padding the remaining columns with literal NULLs. The result is a flat, query-friendly record set that downstream genealogy logic can consume without branching based on batch type. Because inquiry of a batch normally leads users to the assembly description, the view exposes MSI.DESCRIPTION aliased as ASSEMBLY_DESCRIPTION, which is the attribute most commonly sought when tracing a manufactured item back to its batch.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, MTL_MFG_BATCHES_SECURITY_V is defined over the following referenced base objects:

• GME_BATCH_HEADER_VW (view) — supplies the core batch header attributes, aliased as GHDR: BATCH_ID, BATCH_STATUS, PLAN_START_DATE, PLAN_CMPLT_DATE, and ORGANIZATION_ID.
• WIP_ENTITIES (synonym) — supplies the WIP entity name and primary item identifier (WE.WIP_ENTITY_NAME, WE.PRIMARY_ITEM_ID).
• MTL_SYSTEM_ITEMS (synonym) — supplies the assembly/item description (MSI.DESCRIPTION).
• GEM_LOOKUPS (view) — supplies the decoded status meaning via LU1.MEANING, aliased as STATUS_TYPE_DISP.
• FND_DATE (package) and FND_MESSAGE (package) — Oracle Application Object Library utilities available to the view definition, typically used for date conversion and message/translation handling in related GME logic.

The batch identifier is remapped from GHDR.BATCH_ID to the column WIP_ENTITY_ID, aligning GME batch records with WIP entity semantics so that genealogy queries can treat process batches and discrete jobs uniformly. All security-relevant and lot/attribute columns not sourced from these base objects are returned as NULL placeholders, preserving a consistent column list expected by consuming reports.

Key Columns

• ROW_ID — returned as NULL; present for interface uniformity.
• WIP_ENTITY_ID — the GME batch identifier (GHDR.BATCH_ID), the primary join key for genealogy.
• WIP_ENTITY_NAME — the batch/WIP entity name.
• STATUS_TYPE — the raw batch status code; STATUS_TYPE_DISP — its decoded meaning from GEM_LOOKUPS.
• PRIMARY_ITEM_ID — the primary (assembly) item identifier.
• ASSEMBLY_DESCRIPTION — MTL_SYSTEM_ITEMS.DESCRIPTION for the assembly item; the attribute most frequently requested by users searching this view.
• SCHEDULED_START_DATE / SCHEDULED_COMPLETION_DATE — mapped from the batch plan start and plan completion dates.
• ORGANIZATION_ID — the inventory organization owning the batch.
• LOT_NUMBER, EXPIRATION_DATE, VENDOR_NAME, GRADE_CODE, and the C_/D_/N_ATTRIBUTE series — all NULL in this view; they exist to match the broader lot/genealogy column contract.

Common Use Cases and Queries

Typical uses include genealogy explosion reports, batch traceability inquiries, and inventory/quality dashboards that must display a batch alongside its assembly description and status.

• Listing batches with their assembly description and decoded status for an organization.
• Joining the view to genealogy tables on WIP_ENTITY_ID to trace where-used/where-made relationships.
• Filtering by SCHEDULED_COMPLETION_DATE to report recently completed batches.

Sample SQL:

• SELECT wip_entity_id, wip_entity_name, assembly_description, status_type_disp, scheduled_completion_date FROM mtl_mfg_batches_security_v WHERE organization_id = :org_id;
• SELECT b.wip_entity_name, b.assembly_description FROM mtl_mfg_batches_security_v b WHERE b.primary_item_id = :item_id ORDER BY b.scheduled_start_date;
• SELECT b.wip_entity_id, b.assembly_description, b.status_type_disp FROM mtl_mfg_batches_security_v b WHERE b.status_type_disp = :status;

Because assembly_description derives from MTL_SYSTEM_ITEMS, users searching on that term retrieve the actual item description for each batch, resolving the assembly behind each WIP entity in a single query.