Search Results load_open_paybacks

Overview

MSC_CL_DEMAND_PULL is an Oracle Advanced Supply Chain Planning (ASCP) collection package owned by the APPS schema and declared with AUTHID CURRENT_USER. Its header, MSCPDEMS.pls version 120.1, dates to October 2007, indicating a long-lived component of the MSC (Supply Chain Planning) collection layer. The package belongs to the demand-pull stage of the planning data collection process: the phase in which the planning engine retrieves independent and dependent demand from source Oracle EBS applications and stages it in the MSC interface tables so that the memory-based planner can consume it. It is classified as OTHER in the ETRM metadata, meaning it is not a formal public API but an internal collection utility invoked by the collection manager and related concurrent programs. The documented procedure list defines the package's scope: forecasts, master demand schedule (MDS) demand, sales order demand, hard reservations, user-defined demand, AHL (aftermarket/field service) demand, and open paybacks. Notably absent is any procedure that processes the plan output; MSC_CL_DEMAND_PULL is strictly an inbound demand loader.

Key Procedures and Functions

The package exposes eight documented procedures, all first-level entries in the specification:

• LOAD_FORECASTS — Extracts forecast demand from the source forecasting tables and loads it into the planning collection interface.
• LOAD_ITEM_FORECASTS — Handles item-level forecast demand, typically the finer granularity used by item-level forecast sets.
• LOAD_MDS_DEMAND — Pulls demand entered through the Master Demand Schedule, serving as the authoritative independent demand stream for plans that consume MDS rather than sales orders.
• LOAD_SALES_ORDER — Loads sales order demand. Unlike the others, it takes a worker number parameter, reflecting the parallel worker architecture of ASCP collection, where numbered workers process disjoint slices of the source data.
• LOAD_HARD_RESERVATION — Collects hard reservations against on-hand inventory so that planning nets reserved supply correctly against demand.
• LOAD_USER_DEMAND — Loads user-defined, manually entered demand — the "demand at a specified location and date" records created outside the standard forecast, MDS, or sales order flows. This is the procedure associated with the search term load_user_demand.
• LOAD_AHL — Collects demand originating from Oracle AHL (Advanced Heavy/Light industry and field service) applications.
• LOAD_OPEN_PAYBACKS — Loads open payback records, which represent demand created by returns and related supply chain events.

Tables Accessed

The documented table reference is MSC_COLL_PARAMETERS, accessed through an APPS synonym. This is the collection parameter table that governs how each collection run behaves — for example, which organizations are included, the planning mode, and cutover or snapshot settings. MSC_CL_DEMAND_PULL reads these parameters to decide which source demands to select and how to filter them. Although the ETRM extract names only this table directly, the procedures in practice insert into the MSC staging and interface tables for demand before the planner's snapshot step materializes them for the engine.

Usage Notes

MSC_CL_DEMAND_PULL is not intended for direct invocation by end users or customer code. It is called internally by the ASCP collection manager during the demand collection phase of a planning run, typically from the "Planning Data Collection" concurrent program, and can be launched manually from the Collections workbench for diagnostic or refresh purposes. The numbered worker parameter on LOAD_SALES_ORDER indicates that the collection framework may spawn multiple concurrent workers, each calling the package to pull a subset of demand. Because the package is AUTHID CURRENT_USER and classified as OTHER, custom extensions should not wrap or override it; instead, custom demand should be surfaced through supported sources so that LOAD_USER_DEMAND or the standard loaders pick it up. Referenced by one other package, it sits within the dependency chain of MSC collection logic, and any modification carries risk to downstream planner data integrity.