Search Results read_comp_avail

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:

• Orchestration: COLLECT_SUPPLY_DEMAND_INFO drives the overall collection cycle; GET_SUPPLY_DEMAND_INFO retrieves the assembled results; CLEAR_SUPPLY_DEMAND_INFO purges the working data between runs; COLLECT_SUPPLY_INFO and COLLECT_DEMAND_INFO branch the collection into supply and demand paths.
• Supply collectors: COLLECT_ONHAND_SUPPLY, COLLECT_USER_SUPPLY, COLLECT_MTL_SUPPLY, COLLECT_DISCRETEJOB_SUPPLY, COLLECT_WIPNEGREQ_SUPPLY, COLLECT_REPSCHED_SUPPLY, and COLLECT_FLOWSCHED_SUPPLY each populate supply records from their respective source.
• Demand collectors and utilities: COLLECT_DISCRETEJOB_DEMAND, COLLECT_REPSCHED_DEMAND, COLLECT_USER_DEMAND, COLLECT_FLOWSCHED_DEMAND, and COLLECT_SALESORDER_DEMAND populate demand records. GET_COMPONENT_QTY and READ_COMP_AVAIL compute component quantities and read availability for component-level analysis.

Tables Accessed

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

• Supply sources: MTL_SUPPLY, MTL_USER_SUPPLY, MTL_MATERIAL_TRANSACTIONS_TEMP.
• Demand sources: MTL_DEMAND, MTL_USER_DEMAND, MTL_DEMAND_INTERFACE, OE_ORDER_LINES (sales order demand).
• Definitions and context: MTL_SYSTEM_ITEMS, MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES.
• Scheduling and BOM: BOM_EXPLOSIONS (component requirements), BOM_CALENDAR_DATES (calendar validity), MTL_ATP_RULES and MTL_ATP_RULES_S (ATP rule definitions).
• Working store: MTL_SUPPLY_DEMAND_TEMP_S, the temporary staging table into which collected supply and demand rows are consolidated for downstream scheduling.

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.