Search Results msc_x_vmi_util_new




Overview
Explore in AI Chat

Overview

MSC_X_VMI_UTIL_NEW is a PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM taxonomy as an "OTHER" API. Its name and constituent procedures indicate that it serves the Vendor Managed Inventory (VMI) and supplier/customer collaboration functionality delivered through Oracle Advanced Supply Chain Planning (ASCP) and the MSC (Manufacturing Supply Chain) schema family. The package consolidates calculation and graph-generation logic used to present VMI demand, on-hand, and usage metrics to trading partners within the collaborative planning framework. It is documented as VALID in both 12.1.1 and 12.2.2, and ETRM records it as referencing only SYS.STANDARD at the direct dependency level, while being referenced by the view MSC_SUP_DEM_ENTRIES_VMI_V and by one additional package. Table access occurs through APPS synonyms rather than direct MSC schema references, consistent with the standard EBS synonym-layer convention.

Key Procedures and Functions

ETRM documents nine callable units within the package:

  • VMI_DETAILS_SUPPLIER — returns VMI detail information from the supplier perspective, drawing on supplier demand and item-supplier relationships.
  • VMI_DETAILS_CUSTOMER — the customer-facing counterpart, returning VMI detail data relevant to the buying organization.
  • VMICUSTOMERGRAPHCREATE and VMICUSTOMERGRAPHTEST — construct and validate customer-side VMI graph data, typically for display in collaborative planning or supplier portal screens.
  • VMISUPPLIERGRAPHONHAND — generates supplier-side on-hand graph data used in VMI dashboards.
  • AVG_DAILY_DEMAND, SUPPLIER_AVG_DAILY_USAGE, and CUSTOMER_AVG_DAILY_USAGE — compute average daily demand and average daily usage metrics from the supplier and customer vantage points, serving as planning inputs and graph series values.
  • INTRANSIT_LEAD_TIME — derives in-transit lead time, supporting replenishment and visibility calculations for goods moving between source and receipt organizations.

No parameter signatures are documented in the ETRM extract; consumers should validate interfaces against the deployed package specification rather than assuming argument lists.

Tables Accessed

Via APPS synonyms, the package reads and writes the following documented tables:

Usage Notes

The package is not designed for direct end-user invocation; it is called programmatically by the VMI view MSC_SUP_DEM_ENTRIES_VMI_V and by at least one other package, meaning it surfaces indirectly through OBI/HTML-based collaborative planning and supplier portal pages that render VMI graphs and metrics. Because it is classified as OTHER rather than a public API, Oracle does not guarantee interface stability. Customizations should treat it as internal, avoid direct calls where a supported alternative exists, and re-validate behavior after applying 12.1.1 or 12.2.2 patches, since graph and demand-calculation logic in the MSC schema family is frequently revised.