Search Results flm_supply_demand




Overview
Explore in AI Chat

Overview

FLM_SUPPLY_DEMAND is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Flow Manufacturing supply and demand engine. It is the central collection and retrieval layer used by flow scheduling to assemble a consolidated picture of material availability for a given item, organization, and scheduling horizon. The package gathers supplies from multiple sources (on-hand inventory, discrete jobs, repetitive schedules, flow schedules, and user-defined supply) and demands from multiple sources (discrete job component requirements, repetitive schedules, flow schedules, sales orders, and user-defined demand), normalizing them into a common temporary structure so the flow scheduler can evaluate feasibility and net availability.

The package is classified as OTHER (not a public open interface), which indicates it is an internal engine component rather than a supported customer-facing API. It is callable by other flow manufacturing programs and is referenced by FLM_SEQ_READER_WRITER, confirming its role in the flow sequencing and scheduling pipeline. The current object status is VALID.

Key Procedures and Functions

The 21 documented procedures/functions fall into three functional clusters:

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

Usage Notes

FLM_SUPPLY_DEMAND is invoked internally by the Flow Manufacturing scheduling programs, typically as part of a flow schedule generation or sequencing run and by FLM_SEQ_READER_WRITER. In Oracle EBS 12.1.1 and 12.2.2, direct custom invocation is not recommended, as the package is not a supported public API and its interfaces may change. Custom code should call higher-level flow manufacturing APIs or concurrent programs instead. When troubleshooting, DBAs may trace the package to verify collection of supply and demand into MTL_SUPPLY_DEMAND_TEMP_S. The package's tight coupling to MTL_ATP_RULES_S and BOM_EXPLOSIONS means its behavior is sensitive to ATP rule configuration and BOM structure, so those setups should be validated when supply/demand anomalies occur.