Search Results delete_price_lists

Overview

MSD_DEM_COLLECT_PRICE_LISTS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It is a component of Oracle's Demand Planning / Demand Signal Repository (DSR) data collection infrastructure, delivered under the MSD (Demand Planning) application family and documented as an API classification of "OTHER" in the ETRM repository. Its principal business role is to orchestrate the harvesting, staging, and lifecycle management of price list data from external or EBS source systems into the demand planning data model. Price lists represent the commercial pricing agreements that govern how products are sold to customers and channels; collecting them accurately is a prerequisite for price-sensitive demand analysis, promotional lift calculations, and revenue impact simulations.

The package version header indicates a long-standing, stabilized code line (last modified in 2007, version 120.1.12000000.2), which is consistent with its presence in both EBS 12.1.1 and 12.2.2. It exposes two public procedures and no functions, and is referenced by zero other packages in the documented metadata, indicating it is invoked directly by concurrent program drivers or integration code rather than being called programmatically by other PL/SQL units.

Key Procedures and Functions

The package publishes two documented procedures:

• COLLECT_PRICE_LISTS — The primary extraction and load routine. It accepts an error buffer and return code, an instance identifier, a start date and end date defining the collection window, an "include all" flag, and include/exclude price list filter parameters. The procedure selects qualifying price lists from the source, applies the caller's inclusion and exclusion criteria, and stages the results into the demand planning tables for subsequent processing. The date window supports incremental collection so that only changed or newly effective price lists are re-collected on each run.
• DELETE_PRICE_LISTS — The purge and reconciliation routine, and the object of the "delete_price_lists" search. It accepts an error buffer, a return code, and a single list parameter that identifies the price list or set of price lists to be removed. This procedure is used to clear stale, superseded, or out-of-scope price list records from the planning staging tables, either as part of a full refresh cycle or as targeted cleanup after a source-side change.

Tables Accessed

Documented table references resolve through APPS synonyms:

• MSD_DEM_PRICE_LISTS — The core staging table where collected price list records are written by COLLECT_PRICE_LISTS and from which records are purged by DELETE_PRICE_LISTS.
• MSD_DEM_ENTITIES_INUSE — Tracks which demand planning entities are currently active/in use, gating whether a given price list belongs to an in-scope entity.
• MSC_APPS_INSTANCES — Provides source instance context, resolving the instance identifier passed into COLLECT_PRICE_LISTS when multiple source EBS instances feed the planning repository.
• FND_LOOKUP_VALUES — Supplies lookup-driven configuration values used during collection (for example, control flags or status codes applied to staged rows).
• DUAL — Used for single-row selection and standard PL/SQL plumbing.

Usage Notes

This package is not typically invoked from an EBS form. It is designed to be called from a concurrent program wrapper or from custom integration code that supplies the required IN/OUT parameters, including the error buffer and return code that the concurrent manager uses to determine completion status. In practice, COLLECT_PRICE_LISTS is scheduled as part of the recurring demand planning data collection cycle, while DELETE_PRICE_LISTS is invoked when a targeted purge is required — frequently in response to the same search term that surfaced this package. Because the package is referenced by no other documented package, implementers integrating with it should treat it as a standalone API boundary and must supply all parameters explicitly; there are no documented defaults in the metadata. Organizations upgrading between 12.1.1 and 12.2.2 should note the package signature is stable across both releases per the documented source header.