Search Results wipfv_mfg_orders




Overview
Explore in AI Chat

Overview

WIPFV_MFG_ORDERS is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined in the Work in Process (WIP) module. It provides a consolidated, de-normalized presentation of manufacturing orders—both discrete jobs and repetitive schedules—enriched with descriptive lookup values, organization identifiers, and item key flexfield references. The view is part of the Oracle Enterprise Technical Reference Model (ETRM) catalog and is marked VALID in 12.2.2. Its primary role is to serve as a single data source for forms, reports, and integration extracts requiring a unified list of WIP manufacturing orders regardless of whether the underlying order is a discrete job or a repetitive schedule.

Rather than querying WIP_ENTITIES, WIP_DISCRETE_JOBS, and WIP_REPETITIVE_SCHEDULES separately, consumers can query this view to obtain a homogenous result set. The view also embeds Oracle Applications "flexfield" and message tokens such as '_LA:...:MFG_LOOKUPS...', '_KF:INV:MSTK:SY', and '_SEC:DI.ORGANIZATION_ID', which are resolved at runtime by the OA Framework / Oracle Forms layer to display translated lookup meanings, key flexfield concatenations, and security predicates.

Underlying Base Objects

Per the documented ETRM metadata, WIPFV_MFG_ORDERS is defined over the following base objects (all exposed to APPS as synonyms):

Internally the view is defined as a UNION of two SELECT statements joined by WIP_ENTITY_ID. The first branch joins WIP_ENTITIES to WIP_DISCRETE_JOBS; the second branch joins WIP_ENTITIES to WIP_REPETITIVE_SCHEDULES and WIP_REPETITIVE_ITEMS. Both branches join to MTL_SYSTEM_ITEMS, MTL_PARAMETERS, and HR_ALL_ORGANIZATION_UNITS on ORGANIZATION_ID, and both apply the security predicate '_SEC:DI.ORGANIZATION_ID' IS NOT NULL (or its repetitive equivalent).

Key Columns

Note that the repetitive branch maps FIRST_UNIT_START_DATE and LAST_UNIT_COMPLETION_DATE into the same start/completion columns as the discrete branch, preserving a consistent column layout.

Common Use Cases and Queries

Typical uses include WIP order dashboards, open order reports, organization-level workload analysis, and integration extracts. The view also supports cross-checking against INV_ONHAND or MTL_MATERIAL_TRANSACTIONS via WIP_ENTITY_ID.

Representative query returning discrete and repetitive orders with organization context:

  • SELECT wip_entity_name, entity_type, status_type, quantity_completed,
           scheduled_start_date, scheduled_completion_date,
           organization_code, name
      FROM apps.wipfv_mfg_orders
     WHERE organization_id = :p_org_id
       AND scheduled_completion_date BETWEEN :p_from AND :p_to;

Filtering to a single order for drill-down:

  • SELECT * FROM apps.wipfv_mfg_orders WHERE wip_entity_name = :order_number;

Aggregating workload by demand class or organization:

  • SELECT organization_code, demand_class, COUNT(*) order_count, SUM(quantity_completed) total_completed
      FROM apps.wipfv_mfg_orders
     GROUP BY organization_code, demand_class;

Because the view embeds _SEC and _KF tokens, direct SQL access outside Forms returns the raw token strings in place of resolutions; reports and integrations that consume the view directly should resolve these via MFG_LOOKUPS and the INV item key flexfield (MSTK) rather than relying on the tokens.