Results for “collect_onhand_supply”

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

Overview

WPS_SUPPLY_DEMAND is an Oracle EBS planning package owned by APPS that collects, stores, and exposes supply and demand information used by the supply chain planning and scheduling engines. It is the primary data-collection vehicle for the Planning Supply/Demand Power Tool, and is classified in ETRM as API classification OTHER. The package consolidates records from multiple execution and planning sources into a single global PL/SQL table (g_supply_demand_table), making it the entry point for extracting supply and demand information from the execution system.

The package supports a two-part model: each row is tagged with a source type (the SUPPLY DEMAND SOURCE TYPE lookup values 1 through 24, such as purchase order, sales order, WIP discrete job, onhand quantity, intransit receipt, user supply, internal order, and flow schedule) and a supply/demand indicator (1 = Demand, 2 = Supply). Records carry a source_identifier1 value that identifies the instance (‑1 for a non-distributed environment) and a plan_id that is ‑1 when the data originates from the execution system or ‑2 when populated from the scheduling manager.

Key Procedures and Functions

The documented API exposes nineteen procedures and functions:

• COLLECT_SUPPLY_DEMAND_INFO — Primary collection routine; orchestrates retrieval of all supply and demand records into the global table.
• GET_SUPPLY_DEMAND_INFO — Returns the collected supply/demand records.
• CLEAR_SUPPLY_DEMAND_INFO — Clears the global supply/demand table between collection runs.
• COLLECT_SUPPLY_INFO — Collects all supply records regardless of source.
• COLLECT_DEMAND_INFO — Collects all demand records regardless of source.
• COLLECT_ONHAND_SUPPLY — Gathers onhand quantity as a supply source (source type 8).
• COLLECT_USER_SUPPLY — Gathers user-defined supply (source type 16).
• COLLECT_MTL_SUPPLY — Gathers supply from MTL_SUPPLY.
• COLLECT_DISCRETEJOB_SUPPLY, COLLECT_WIPNEGREQ_SUPPLY, and COLLECT_REPSCHED_SUPPLY, COLLECT_FLOWSCHED_SUPPLY — Collect WIP discrete jobs, nonstandard job negative requirements, repetitive schedules, and flow schedules as supply sources.
• COLLECT_DISCRETEJOB_DEMAND, COLLECT_REPSCHED_DEMAND, COLLECT_FLOWSCHED_DEMAND — Collect component demand from the same WIP entities.
• COLLECT_USER_DEMAND — Gathers user-defined demand (source type 17).
• COLLECT_SALESORDER_DEMAND — Gathers demand from sales orders (source type 2, and reserved sales order, source type 9).

Tables Accessed

The package references the following APPS synonyms: BOM_CALENDAR_DATES (shop-calendar validation for scheduling), BOM_EXPLOSIONS (component demand), MTL_ATP_RULES (supply/demand sourcing rules), MTL_DEMAND and MTL_DEMAND_INTERFACE (demand records and their interface staging), MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_PARAMETERS and MTL_SECONDARY_INVENTORIES (organization and subinventory context), MTL_SUPPLY (supply records), MTL_SYSTEM_ITEMS (item validation and attributes), MTL_USER_DEMAND and MTL_USER_SUPPLY (user-entered supply and demand), OE_ORDER_LINES (sales order demand), WIP_DISCRETE_JOBS (discrete job supply/demand), and WIP_FLOW_SCHEDULES (flow schedule supply/demand).

Usage Notes

WPS_SUPPLY_DEMAND is invoked by planning and scheduling processes rather than by end-user forms directly. In 12.1.1 and 12.2.2 it is typically called from concurrent programs, the Planning Supply/Demand Power Tool, or from custom PL/SQL that requires a point-in-time consolidated view of supply and demand for an inventory organization. A caller first invokes CLEAR_SUPPLY_DEMAND_INFO, then COLLECT_SUPPLY_DEMAND_INFO with the group ID, system sequence number, planning status, and organization ID, and finally reads results through GET_SUPPLY_DEMAND_INFO. Because the package maintains state in a global PL/SQL table, it is session-scoped and must not be treated as a persistent staging table; records are transient. The ETRM metadata indicates the package is referenced by zero other packages, so custom code must call it explicitly.