Search Results alternate_bom




Overview
Explore in AI Chat

Overview

APPS.WIPFV_MFG_ORDERS is a Business Intelligence System (BIS) view owned by the APPS schema and registered under FND Design Data WIP.WIPFV_MFG_ORDERS. It presents a consolidated, read-only picture of manufacturing order details spanning discrete jobs, repetitive schedules, and flow schedules — the three production constructs used in Oracle E-Business Suite to control production activities and maintain entity name uniqueness. Because it is a BIS view rather than a transactional table, it is intended primarily for reporting, ad-hoc querying, and integration extracts rather than for direct DML. The view carries a status of VALID in both 12.1.1 and 12.2.2 and is not referenced by any other database object, meaning it sits at the top of the dependency chain.

Underlying Base Objects

The view is defined over a set of WIP, inventory, and HR synonyms. The core manufacturing sources are WIP_ENTITIES, WIP_DISCRETE_JOBS, WIP_REPETITIVE_SCHEDULES, WIP_REPETITIVE_ITEMS, and WIP_FLOW_SCHEDULES; these supply order identity, type, status, dates, and quantities across the three order models. WIP_ENTITIES is the common parent that unifies discrete, repetitive, and flow orders under a single WIP entity key. Item context is drawn from MTL_SYSTEM_ITEMS, while organization context is resolved through HR_ALL_ORGANIZATION_UNITS and MTL_PARAMETERS, which anchor the inventory organization code and name. All base objects are accessed as APPS synonyms, so the view resolves entirely within the APPS schema.

Key Columns

Common Use Cases and Queries

A frequent requirement is identifying which manufacturing orders use a specific routing alternate. The following query filters on ALTERNATE_ROUTING and returns the identifying order context:

  • SELECT MFG_ORDER_NAME, _LA:MFG_ORDER_TYPE, _KF:ITEM_NUMBER, ALTERNATE_ROUTING, ROUTING_REVISION_DATE, _LA:MFG_ORDER_STATUS FROM APPS.WIPFV_MFG_ORDERS WHERE ALTERNATE_ROUTING = '&alt_routing';

Other typical scenarios include reporting open orders by organization (WHERE ORGANIZATION_CODE = 'M1' AND ORDER_CLOSED_DATE IS NULL), summarizing completed quantities per item, and auditing orders whose BOM and routing alternates differ. Because the view unifies discrete, repetitive, and flow orders, a single query can produce a cross-model production report without unioning the underlying WIP tables. Note that the _LA: and _KF: prefixes are BIS bind markers; in practical SQL these are surfaced as the decoded attribute and key-flex columns, and the literal query text shown in the source metadata should be edited accordingly before execution.