Search Results is_supplier_approval




Overview
Explore in AI Chat

Overview

MSC_X_CVMI_REPLENISH is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Consigned and Vendor-Managed Inventory (CVMI/VMI) replenishment process within Oracle Advanced Supply Chain Planning (ASCP) and the Supply Chain Execution (SCE) stack. Its central responsibility is to evaluate supplier demand, determine whether replenishment should be released automatically or routed for supplier approval, and then generate the appropriate replenishment or release transactions against the planning repository. The package bridges planning-side demand data held in the MSC schema with execution-side release logic used by downstream SCE loading packages.

Key Procedures and Functions

The package exposes twelve documented program units, spanning concurrent processing, workflow integration, and UI/service layer entry points.

  • VMI_REPLENISH_CONCURRENT — Concurrent-program entry point that drives bulk VMI replenishment processing.
  • VMI_REPLENISH — Core replenishment routine that evaluates demand and produces replenishment recommendations.
  • VMI_REJECT — Handles rejection of a replenishment proposal, typically by a supplier or planner.
  • IS_AUTO_RELEASE — Determines whether a given replenishment qualifies for automatic release without manual intervention.
  • IS_SUPPLIER_APPROVAL — Determines whether supplier approval is required before release.
  • VMI_RELEASE_API — API for releasing approved VMI replenishments programmatically.
  • VMI_RELEASE_API_UI — UI-oriented wrapper around the release API for interactive invocation.
  • VMI_RELEASE_API_LOAD — Load-oriented release routine used in batch or interface processing.
  • VMI_REPLENISH_WF — Integrates replenishment processing with the Oracle Workflow engine.
  • PRINT_USER_INFO — Diagnostic utility that outputs the current user context.
  • PRINT_DEBUG_INFO — Diagnostic utility that emits debug trace information.
  • RESET_VMI_REFRESH_FLAG — Resets the internal refresh flag governing VMI data reprocessing.

Tables Accessed

The package reads and writes planning and trading-partner data through APPS synonyms. Company and site context come from MSC_COMPANIES, MSC_COMPANY_SITES, MSC_COMPANY_RELATIONSHIPS, MSC_TRADING_PARTNERS, and MSC_TRADING_PARTNER_MAPS. Item and site master references are drawn from MSC_ITEMS, MSC_SYSTEM_ITEMS, and MSC_PLANNERS, while organizational status is checked via MSC_PLAN_ORG_STATUS. Supplier demand is sourced from MSC_SUP_DEM_ENTRIES and MSC_SUP_DEM_ENTRIES_S, partner contact details from MSC_PARTNER_CONTACTS, and staging data from the MSC_VMI_TEMP table. ATP-related scheduling data is accessed through MRP_ATP_SCHEDULE_TEMP_S, and DUAL is used for single-row queries.

Usage Notes

MSC_X_CVMI_REPLENISH is invoked primarily from concurrent programs and workflow activities, with interactive paths reaching it through the UI-specific release wrapper. It is referenced by two other packages, including MSC_SCE_LOADS_PKG, which confirms its role upstream of supply chain execution loading. Because the API classification is OTHER rather than a public or private standard API, customizations should limit direct calls to the documented entry points and avoid embedding business logic that assumes internal structures. Environments upgrading between 12.1.1 and 12.2.2 should validate behavior against the target release, since dependency resolution and synonym visibility can differ.