Search Results print_debug_info




Overview
Explore in AI Chat

Overview

MSC_X_CVMI_PLANNING is an Oracle Advanced Supply Chain Planning (ASCP) package body owned by APPS that supports Collaborative VMI (Customer/Vendor Managed Inventory) planning integration. Its core business purpose is to bridge planning data between the APS (Advanced Planning and Scheduling) schema and the SCE (Supply Chain Execution) schema, and to compute the average daily demand used to drive VMI replenishment decisions for customer-facing inventory arrangements. The package is classified as OTHER and, based on its header revision, is a long-standing, noship-marked component that has been stable since the 11.5.x code line and carried forward into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents six members, five of which are named:

  • CALCULATE_AVERAGE_DEMAND — The principal calculation engine. It drives the average daily demand computation for VMI items by iterating over a forecast-items cursor that joins planning system items, trading partners, and the VMI temporary table. It reads the forecast horizon and VMI forecast type for each plan/item/organization/supplier-instance combination.
  • APS_TO_SCE — Transfers or maps data from the APS planning model into the SCE execution model. In VMI flows this supports pushing planning results down to execution.
  • SCE_TO_APS — The converse mapping, moving supply chain execution data back up into the APS planning model.
  • PRINT_DEBUG_INFO — A diagnostic utility that emits tracing messages controlled by the MSC_CP_DEBUG profile option. The package initializes a module-level debug variable from FND_PROFILE.VALUE('MSC_CP_DEBUG'), defaulting to '0'. This is the routine directly relevant to the user's search, since virtually every processing step in CALCULATE_AVERAGE_DEMAND is bracketed with calls to PRINT_DEBUG_INFO.
  • PRINT_USER_INFO — A companion logging routine that surfaces user-oriented informational messages, providing visibility into package behavior beyond raw debug tracing.

A sixth documented member is present in the metadata but not individually named in the excerpt.

Tables Accessed

The package works against the following APPS-synonym tables:

  • MSC_SYSTEM_ITEMS — Source of plan items, forecast horizon, VMI forecast type, UOM, and the planning code filter (inventory_planning_code = 7 for VMI).
  • MSC_TRADING_PARTNERS — Identifies the organization partner relationship (partner_type = 3), including modeled customer and customer site identifiers.
  • MSC_VMI_TEMP — Staging table holding computed average daily demand and VMI type; joined with an outer (+) in the forecast cursor to persist results per plan/item/organization/instance.
  • MSC_TRADING_PARTNER_MAPS — Supports company, organization, and site mapping levels (constants 1, 2, 3).
  • MSC_COMPANY_RELATIONSHIPS — Provides company relationship context for the OEM company (constant OEM_COMPANY_ID = 1).
  • MSC_SUP_DEM_ENTRIES — Supply/demand entries used in the APS-to-SCE and SCE-to-APS reconciliation.

Usage Notes

MSC_X_CVMI_PLANNING is typically invoked as part of the ASCP VMI planning cycle rather than directly from a form. It is referenced by one other package, indicating it serves as a called dependency within the VMI planning program stack. Diagnostic output is gated by the MSC_CP_DEBUG profile option; setting this profile to a non-zero value causes PRINT_DEBUG_INFO to emit detailed tracing, which is the standard technique for troubleshooting VMI average-daily-demand calculations in EBS 12.1.1 and 12.2.2. Custom code should not modify this package, as it is an Oracle-shipped, noship component.