Search Results calculate_average_demand

Overview

MSC_X_CVMI_PLANNING is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the Supply Chain Management family of objects and is associated with Oracle Advanced Supply Chain Planning (ASCP) and the Collaborative VMI (Vendor Managed Inventory) planning process. The package supports the exchange and transformation of planning data between the APS (Advanced Planning and Scheduling) planning engine and the SCE (Supply Chain Execution) transactional environment. Its name, MSC_X_CVMI_PLANNING, follows the MSC_ prefix convention used across Oracle's planning application modules, with the "X" and "CVMI" segments indicating an extension utility for collaborative VMI processing.

In functional terms, the package provides logic used to calculate demand averages derived from planning activity and to bridge planning-engine data with execution-layer records. Although the documented metadata classifies the object as OTHER rather than a formal public API, its procedures are invoked internally by planning-related packages and utilities.

Key Procedures and Functions

ETRM documentation records six procedures and functions for this package. Their names and purposes are as follows:

• CALCULATE_AVERAGE_DEMAND — Computes an average demand value used in VMI planning calculations, typically based on historical or planned demand stored in planning tables.
• APS_TO_SCE — Transforms or maps data from the APS (Advanced Planning and Scheduling) representation into the SCE (Supply Chain Execution) representation, enabling planned results to be consumed by execution-side processes.
• SCE_TO_APS — Performs the reverse mapping, moving transactional or execution data back into APS structures for planning consumption.
• PRINT_DEBUG_INFO — Emits diagnostic or debug-level output, used for troubleshooting during planning runs or development.
• PRINT_USER_INFO — Outputs user-facing informational messages, typically logged during processing for visibility into package behavior.

Because the documented metadata does not expose parameter signatures, no parameter lists are described here. The list above reflects the six documented procedures and functions associated with the object; the metadata excerpt lists five named entries, and the balance of the six comprises additional internal routines. The APS_TO_SCE and SCE_TO_APS procedures are the most significant from a data-integration perspective.

Tables Accessed

The package references the following tables through APPS synonyms:

• MSC_COMPANY_RELATIONSHIPS — Stores relationships between companies involved in trading partner arrangements; used to resolve organizational context for VMI planning.
• MSC_SUP_DEM_ENTRIES — Holds supply and demand entries from the planning engine, essential for averaging demand and reconciliation logic.
• MSC_SYSTEM_ITEMS — The planning system item master, providing item attributes required during demand calculations and data transformation.
• MSC_TRADING_PARTNERS — Defines trading partner identities used in collaborative planning.
• MSC_TRADING_PARTNER_MAPS — Maps partners to their associated identifiers, supporting the APS-to-SCE and SCE-to-APS conversions.
• MSC_VMI_TEMP — A temporary staging table for VMI planning data, used during intermediate processing steps.

These tables confirm that the package operates within the ASCP/VMI planning schema and performs both read and staging write activity.

Usage Notes

MSC_X_CVMI_PLANNING is referenced by one other package, MSC_X_CVMI_REPLENISH, and is itself listed as referencing its own body and internal SQL statements. It is not typically invoked directly by end users. Instead, it is called from within the VMI replenishment flow and planning-engine integration paths, generally during planning runs or when replenishment data is exchanged between APS and execution systems. Because it is an internal (non-API) object, custom code should avoid a hard dependency on it; the documented procedure names are useful for tracing unlogged errors or debug output generated during VMI planning. When diagnosing VMI planning issues in EBS 12.1.1 or 12.2.2, the PRINT_DEBUG_INFO and PRINT_USER_INFO procedures provide the primary visibility into package execution.