Search Results mrp_ap




Overview
Explore in AI Chat

Overview

MSC_CL_DEMAND_PULL is a collection package body in the Oracle Advanced Planning (MSC) schema, APPS, that extracts demand-side data from the source E-Business Suite transaction tables and stages it for consumption by the Advanced Supply Chain Planning (ASCP) and related planning engines. The package forms part of the collections framework administered through the Oracle Collections concurrent programs and is responsible specifically for "pulling" demand records — forecasts, master demand schedule entries, sales orders, reservations, user-defined demand, and related AHL/payback artifacts — into the MSC staging tables used by the planning data model.

As documented in the ETRM metadata for release 12.1.1 / 12.2.2, the package is classified as OTHER (not a formal public API) and is referenced by one other package. The body is dominated by dynamically constructed SQL statements assembled into MSC_ST_* staging tables. The $Header line (MSCPDEMB.pls 120.19 2012/06/06) identifies it as the MSC Planning Demand Extraction Body, consistent with its role in the collections pipeline. A representative fragment of the source shows LOAD_FORECASTS populating MSC_ST_DESIGNATORS from the MRP_AP_FORECAST_DSGN_V view, which reflects the typical pattern followed by every procedure in the package.

Key Procedures and Functions

The ETRM metadata documents eight procedures in the package:

  • LOAD_FORECASTS — Stages forecast designator and forecast set information into MSC staging tables. The excerpt shows it inserting into MSC_ST_DESIGNATORS from MRP_AP_FORECAST_DSGN_V, gated by the MSC_CL_PULL.FORECAST_ENABLED profile-dependent flag. It is the master entry point for forecast-driven demand.
  • LOAD_ITEM_FORECASTS — Extracts item-level forecast entries that complement the designator-level load performed by LOAD_FORECASTS.
  • LOAD_MDS_DEMAND — Extracts Master Demand Schedule entries from the MDS source tables and stages them for planning consumption.
  • LOAD_SALES_ORDER — Collects sales order demand, applying the MSC_SO_OFFSET_DAYS and MSC_X_VMI_OM_ORDER_TYPE profile values used to filter or shift order dates and to identify VMI order types.
  • LOAD_HARD_RESERVATION — Extracts hard reservations on inventory so that committed stock is reflected as demand in the plan.
  • LOAD_USER_DEMAND — Collects user-defined demand records maintained outside standard sales-order and forecast sources.
  • LOAD_AHL — Collects demand associated with Oracle Advanced Hideaway Logistics (AHL) shipment or order records.
  • LOAD_OPEN_PAYBACKS — Extracts open payback records so that contingent or refundable demand is visible to the planning engine.

All procedures follow a common design: they read profile options, build dynamic SQL strings concatenating column and table names, and execute INSERT-SELECT statements into MSC staging tables using bind variables for refresh_id and sr_instance_id.

Tables Accessed

The documented table reference via APPS synonyms is MSC_COLL_PARAMETERS, which supplies collection-run parameters (such as the refresh identifier and source instance) passed into the dynamic SQL as bind variables. In practice, and consistent with the source excerpt, the package writes primarily to MSC_ST_DESIGNATORS and other MSC_ST_* staging tables, and reads source views such as MRP_AP_FORECAST_DSGN_V. The staging tables are subsequently consumed by the planning engine's load phase.

Usage Notes

MSC_CL_DEMAND_PULL is not a user-invocable API. It is invoked by the Collections Manager and related planning concurrent programs during the demand collection phase, and indirectly by any package that orchestrates the MSC collections pipeline (the metadata notes it is referenced by one other package). Custom code should not call it directly; instead, organizations should rely on the standard collections concurrent programs. Because it is a package body in the APPS schema and an OTHER-classified object, it may change without notice between releases, and direct dependencies are unsupported. The profile options MSC_SO_OFFSET_DAYS and MSC_X_VMI_OM_ORDER_TYPE materially affect the demand data that is collected and should be reviewed when sales-order demand appears incomplete or shifted.