Search Results temp_tables

Overview

MSC_X_REPLENISH is a PL/SQL package in the APPS schema that supports Vendor Managed Inventory (VMI) and supplier collaboration workflows within Oracle Advanced Supply Chain Planning (ASCP) and its related MSC (Advanced Planning) modules. Its name, combining the MSC prefix with "X_REPLENISH," indicates an extension-oriented or custom-adjacent package focused on replenishment processing. In Oracle EBS 12.1.1 and 12.2.2, the package serves as a bridge between planning engine logic and supplier-facing replenishment actions, enabling organizations to automate and manage the flow of replenishment recommendations to suppliers through VMI arrangements.

The package is classified as OTHER within the ETRM documentation, meaning it is not exposed as a formal public API but functions as an internal utility and orchestration layer. It is referenced by other planning packages, including MSC_SCE_LOADS_PKG, MSC_X_CUST_FACING_RELEASE, and MSC_X_PLANNING, confirming its role as a shared dependency in the planning data flow rather than an isolated module.

Key Procedures and Functions

The package exposes fifteen documented procedures and functions, organized around VMI replenishment and release processing:

• VMI_REPLENISH_WRAPPER, VMI_REPLENISH_CONCURRENT, VMI_REPLENISH_WF, VMI_REPLENISH — The core replenishment family. These routines generate and process VMI replenishment recommendations across different invocation contexts: a wrapper entry point, a concurrent program, a workflow-driven path, and the primary replenishment routine.
• VMI_RELEASE and VMI_REJECT — Handle supplier response actions, allowing releases to be confirmed or rejected within the VMI collaboration cycle.
• IS_VMI_ITEM, IS_AUTO_RELEASE, IS_SELLER_APPROVE — Boolean-style validation functions that determine whether an item participates in VMI, whether auto-release is permitted, and whether seller (supplier) approval is required.
• PRINT_DEBUG_INFO and PRINT_USER_INFO — Diagnostic utilities for logging debug and user context information during processing.
• APS_TO_SCE and SCE_TO_APS — Data transformation routines converting between Advanced Planning Scheduler (APS) and Supply Chain Exchange (SCE) representations.
• CREATE_REQUISITION — Generates requisitions as an output of replenishment processing.
• TEMP_TABLES — Manages temporary tables used during processing runs.

Tables Accessed

The package reads and writes a set of MSC tables accessed via APPS synonyms. MSC_ITEMS, MSC_SYSTEM_ITEMS, and MSC_ITEM_SUPPLIERS are central to identifying replenishment-eligible items and their sourcing relationships. Partner-related tables—MSC_COMPANIES, MSC_COMPANY_RELATIONSHIPS, MSC_COMPANY_SITES, MSC_COMPANY_USERS, and MSC_PARTNER_CONTACTS—support supplier and contact resolution. MSC_SUP_DEM_ENTRIES and MSC_SUP_DEM_ENTRIES_S hold supply/demand entries that feed replenishment calculations. MSC_PO_REQUISITIONS_INTERFACE supports requisition creation, while MSC_APPS_INSTANCES, MSC_PLAN_ORG_STATUS, MSC_PLANNERS, and MSC_TP_ID_LID provide instance, planning organization, planner, and trading partner context.

Usage Notes

MSC_X_REPLENISH is typically invoked indirectly through concurrent programs and workflow activities tied to VMI replenishment cycles, rather than through direct user form interaction. Its documented dependency on MSC_SCE_LOADS_PKG and MSC_X_PLANNING indicates it participates in planning data loading and release sequences. Customizations and extensions that interact with VMI replenishment should reference this package carefully, as it is an internal planning component. Developers integrating with it should rely on the wrapper and concurrent entry points rather than calling lower-level routines directly, and should validate any signature assumptions against the specific EBS patch level in use.