Results for “mtl_effectivity_control”

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

Overview

APPS.WIP_FLOW_ASSEMBLIES_V is a reporting and integration view in Oracle E-Business Suite that exposes assembly headers eligible for flow (line-based) manufacturing in Oracle Work in Process. It consolidates item, routing, revision, and control-attribute information into a single denormalized result set that downstream WIP flow scheduling and shop-floor applications consume. Rather than presenting every inventory assembly, the view returns only those assemblies associated with a common flow routing (where cfm_routing_flag = 1) and whose line operations remain in a pending state, as determined by the WIP_SFCB_UTILITIES package. This selective behavior makes the view a functional access point for identifying work that can still be sequenced or started in a flow line.

The view is significant in the context of effectivity control because it derives its EFFECTIVITY_CONTROL description through a join to MFG_LOOKUPS on the MTL_EFFECTIVITY_CONTROL lookup type. In Oracle EBS, assemblies that carry effectivity control are governed by revision effectivity dates; the view surfaces a truncated EFFECTIVITY_DATE from the routing revision high-date view so that consumers can evaluate the effective revision of a flow assembly.

Underlying Base Objects

The view is defined over six documented objects. BOM_OPERATIONAL_ROUTINGS and BOM_OPERATION_SEQUENCES (both referenced through synonyms) supply the routing header and operation sequence data. MTL_SYSTEM_ITEMS_KFV, also a synonym, supplies the concatenated item segment and descriptive attributes. MTL_ROUTING_REV_HIGHDATE_V is a view that resolves the process revision and its effectivity date. MFG_LOOKUPS is a view providing the decoded meanings for lot, serial, and effectivity control. WIP_SFCB_UTILITIES is the package whose line_op_is_pending function filters out completed or non-pending operations.

Two important filtering conditions define the join logic. The routing must be a common flow routing (cfm_routing_flag = 1), and only line operations (operation_type = 3) are considered. The final predicate invokes WIP_SFCB_Utilities.line_op_is_pending across the operation sequence, routing sequence, item, organization, and alternate routing designator, retaining only rows where the function returns 1.

Key Columns

• NODE_LABEL — A composite key formed from the concatenated item segment, alternate routing designator, process revision, and operation sequence number.
• ORGANIZATION_ID and INVENTORY_ITEM_ID — The organization and item primary keys.
• ASSEMBLY_NAME and DESCRIPTION — The concatenated item segment and item description.
• ALTERNATE_ROUTING_DESIGNATOR, LINE_ID, STANDARD_OPERATION_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID — Routing and operation identifiers, several of which form the composite primary key.
• PROCESS_REVISION and EFFECTIVITY_DATE — The effective revision and its truncated effectivity date.
• LOT_CONTROL, SERIAL_CONTROL, EFFECTIVITY_CONTROL — Decoded lookup meanings for the assembly's control attributes.
• PRIMARY_UOM_CODE and NODE_TYPE — The primary unit of measure and the node type constant (1).

Common Use Cases and Queries

A primary use case is locating flow assemblies whose effectivity control is enabled, which is directly relevant to the mtl_effectivity_control lookup. The following query lists assembly names, process revisions, and effectivity dates for effectivity-controlled flow assemblies:

• SELECT assembly_name, process_revision, effectivity_date, effectivity_control FROM apps.wip_flow_assemblies_v WHERE effectivity_control IS NOT NULL ORDER BY assembly_name;
• SELECT node_label, organization_id, inventory_item_id, process_revision FROM apps.wip_flow_assemblies_v WHERE organization_id = :org_id AND assembly_name = :item;

Because the view already filters to pending line operations, it is commonly joined to WIP scheduling and dispatch queries to identify assemblies still open on the floor. Effectivity-controlled rows merit particular attention: the truncation of EFFECTIVITY_DATE means date-based revision selection should use the date component only when comparing to revision effectivity ranges maintained on the routing revision.