Results for “date_released”

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

Overview

MTL_WORK_ORDER_HEADER_V is an APPS-owned database view in the Oracle E-Business Suite Inventory (INV) module that provides a consolidated, unified header-level representation of work orders and batch production records. It serves as a reporting and integration interface for work order information, drawing together discrete job data from Oracle Work in Process (WIP), lot and lot attribute data from inventory, and organization information. The view presents a single row per work order entity, exposing job identity, status, item details, scheduling and completion dates, and quantity metrics alongside lot-level attribute columns.

The view is significant because it abstracts the underlying complexity of the WIP schema. Users who search for "wip_discrete_jobs_v" are typically attempting to retrieve discrete job header information; MTL_WORK_ORDER_HEADER_V extends this concept by wrapping WIP_DISCRETE_JOBS_V and layering additional descriptive and lot-attribute fields, making it suitable for unified work order reporting where both discrete jobs and batch processes are relevant. It is commonly consumed by reports, concurrent programs, and external integrations that require a stable, denormalized view of work order headers without navigating the base WIP and inventory tables directly.

Underlying Base Objects

The documented referenced base objects for this view are:

• WIP_DISCRETE_JOBS_V (VIEW) — the principal source of discrete job header data, supplying job identity, status, dates, and quantities.
• MTL_SYSTEM_ITEMS_KFV (SYNONYM) — provides the concatenated item segments, description, and inventory item identifier.
• MTL_LOT_NUMBERS (SYNONYM) — supplies lot number, disposition, and lot attribute columns.
• MTL_PARAMETERS (SYNONYM) — organization-level inventory parameters.
• HR_ORGANIZATION_UNITS (VIEW) and HR_GENERAL / HR_SECURITY (PACKAGES) — resolve organization name and enforce organization-level security.
• GEM_LOOKUPS (VIEW) — supplies lookup-based decode values.
• GME_BATCH_HEADER and GME_MATERIAL_DETAILS (SYNONYMS) — process manufacturing batch and material detail sources.
• WIP_ENTITIES (SYNONYM) — the underlying WIP entity record.
• PJM_PROJECT (PACKAGE) — project-related resolution.

The view therefore joins work order header data with item master information and lot attributes through these objects, presenting a composite record. Notably, the view text also aliases records with constants such as 'JOBS' for WORK_ORDER_TYPE and 'PRODUCT' for LINE_TYPE.

Key Columns

• WIP_ENTITY_ID / WIP_ENTITY_NAME — unique identifier and user-facing name of the work order.
• ORGANIZATION_ID / ORGANIZATION_CODE / ORGANIZATION_NAME — the owning inventory organization.
• STATUS_TYPE — decoded job status (e.g., Released, Complete).
• ITEM_NUMBER / ITEM_DESCRIPTION / INVENTORY_ITEM_ID — the assembled item and its description.
• FIRM_PLANNED_FLAG, CLASS_CODE, JOB_TYPE — job classification attributes.
• SCHEDULED_START_DATE, DATE_RELEASED, SCHEDULED_COMPLETION_DATE, DATE_COMPLETED, DATE_CLOSED — key scheduling and lifecycle dates.
• START_QUANTITY, QUANTITY_REMAINING, QUANTITY_COMPLETED, QUANTITY_SCRAPPED, NET_QUANTITY — quantity metrics for the order.
• COMPLETION_SUBINVENTORY — target subinventory for completions.
• Lot attributes from MTL_LOT_NUMBERS: LOT_NUMBER, EXPIRATION_DATE, VENDOR_NAME, GRADE_CODE, STATUS_ID, plus descriptive flexfield columns C_ATTRIBUTE1 through C_ATTRIBUTE20, D_ATTRIBUTE1 through D_ATTRIBUTE10, and N_ATTRIBUTE columns.

Common Use Cases and Queries

Typical uses include work order status dashboards, open job reports, quantity reconciliation, and integration feeds that require a single row per order with item and lot context.

Example — list released jobs for an organization:

• SELECT WIP_ENTITY_NAME, ITEM_NUMBER, STATUS_TYPE, START_QUANTITY, QUANTITY_COMPLETED FROM APPS.MTL_WORK_ORDER_HEADER_V WHERE ORGANIZATION_CODE = :org AND STATUS_TYPE = 'Released';

Example — pending and incomplete work orders:

• SELECT WIP_ENTITY_NAME, ITEM_NUMBER, SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE, QUANTITY_REMAINING FROM APPS.MTL_WORK_ORDER_HEADER_V WHERE DATE_COMPLETED IS NULL ORDER BY SCHEDULED_START_DATE;

Example — lot-attributed job extract:

• SELECT WIP_ENTITY_NAME, ITEM_NUMBER, LOT_NUMBER, EXPIRATION_DATE, GRADE_CODE FROM APPS.MTL_WORK_ORDER_HEADER_V WHERE LOT_NUMBER IS NOT NULL;

Because the view incorporates HR_SECURITY logic, query results are constrained by the organization access of the requesting user, which should be accounted for in integrations and reports.