Search Results msc_x_hz_ui_query_id_s

Overview

MSC_X_VMI_UTIL_NEW is a PL/SQL package body owned by the APPS schema and validated as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Advanced Supply Chain Planning (ASCP) / MSC product family and provides utility logic for Vendor Managed Inventory (VMI) processing. The package consolidates the calculation and presentation logic used to expose VMI information to both suppliers and customers, including average daily demand, usage, in-transit lead time, and graph-generation routines that drive VMI dashboards and inquiry screens. The ETRM metadata classifies the package as an "OTHER" API, indicating it is a supporting utility rather than a public integration interface. It is a standalone package body: it references numerous MSC, MRP, and FND objects, and is not referenced by any dependent database object according to the dependency listing, although the application metadata notes it is referenced by one other package. Because it is part of the MSC schema construct, changes to it should be treated as an Oracle-supplied customization boundary and avoided in favor of supported extensions.

Key Procedures and Functions

The documented body exposes nine procedures and functions:

• VMI_DETAILS_SUPPLIER — Returns the VMI detail dataset from the supplier perspective, drawing on item-supplier, trading partner, and sourcing data.
• VMI_DETAILS_CUSTOMER — Returns the VMI detail dataset from the customer perspective, complementing the supplier-side routine.
• VMICUSTOMERGRAPHCREATE — Builds the customer-side VMI graph output, writing to or consuming the VMI graph structures.
• VMISUPPLIERGRAPHONHAND — Builds the supplier-side graph reflecting on-hand inventory position.
• AVG_DAILY_DEMAND — Computes average daily demand, a core VMI metric used to size replenishment recommendations.
• INTRANSIT_LEAD_TIME — Derives in-transit lead time for shipments between source and receipt organizations.
• VMICUSTOMERGRAPHTEST — A test/validation routine for the customer graph generation path.
• SUPPLIER_AVG_DAILY_USAGE — Calculates average daily usage from the supplier's view of consumption.
• CUSTOMER_AVG_DAILY_USAGE — Calculates average daily usage from the customer's view of consumption.

No parameter lists are documented in the ETRM metadata, so signatures should be confirmed directly from the package specification in the database before invocation.

Tables Accessed

The package operates primarily against MSC synonym-based tables: MSC_ITEMS, MSC_SYSTEM_ITEMS, MSC_ITEM_SUPPLIERS, MSC_UNITS_OF_MEASURE, MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_MAPS, MSC_COMPANIES, MSC_COMPANY_RELATIONSHIPS, MSC_COMPANY_SITES, MSC_COMPANY_USERS, MSC_SR_ASSIGNMENTS, MSC_SR_SOURCE_ORG, MSC_SR_RECEIPT_ORG, MSC_ASSIGNMENT_SETS, MSC_PLAN_ORG_STATUS, MSC_SUP_DEM_ENTRIES, and MRP_ATP_SCHEDULE_TEMP_S. It also references the VMI-specific structures MSC_VMI_GRAPH, MSC_VMI_TEMP, and MSC_X_HZ_UI_QUERY_ID_S. These tables supply planning item definitions, trading partner and company hierarchies, sourcing assignments, source and receipt organization mappings, supply/demand entries, and temporary graph scaffolding used to produce VMI output.

Usage Notes

MSC_X_VMI_UTIL_NEW is invoked from VMI inquiry and dashboard flows, typically behind Oracle Forms or OAF pages and their supporting concurrent programs, rather than being called directly by end users. The VMI_DETAILS_* and *GRAPH* routines populate the data and graph datasets displayed to suppliers and customers, while AVG_DAILY_DEMAND and the usage/lead-time routines feed the underlying replenishment metrics. Standard behavior should be treated as Oracle-owned; customizations should be implemented in extension packages or views instead of modifying this body, and any direct call should first confirm the current signatures from the package specification, since ETRM documents procedure names but not their parameter lists.