Search Results compute_changed_order

Overview

MSC_X_NETTING4_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Advanced Supply Chain Planning (ASCP) module of the Oracle Value Chain Planning suite, where the MSC schema prefix identifies objects used by the planar and unconstrained netting engine. Within that framework, MSC_X_NETTING4_PKG serves as a specialized netting and diagnostic utility package, providing the routines that evaluate planning output, detect exception conditions, and measure the accuracy of forecast and performance calculations.

The package is classified in the ETRM repository as "OTHER," indicating that it is an internal implementation object rather than a published, supported API. It is tightly coupled to the core netting driver, MSC_X_NETTING_PKG, which both references and is referenced by this package. This mutual dependency confirms that MSC_X_NETTING4_PKG operates as a subordinate module invoked by the main netting program rather than as an entry point called directly by end users.

Key Procedures and Functions

The ETRM metadata documents four procedures or functions within this package:

• COMPUTE_CHANGED_ORDER — Identifies and processes planning orders whose attributes, quantities, or dates have changed since the prior planning run, supporting incremental netting and change detection logic.
• COMPUTE_FORECAST_ACCURACY — Calculates forecast accuracy metrics by comparing forecasted demand against actual or historical consumption, expressed through the MSC_SUP_DEM_HISTORY and MSC_SUP_DEM_ENTRIES structures.
• COMPUTE_PERFORMANCE — Derives performance measurements for the planning results set, used for plan quality reporting and benchmarking.
• COMPUTE_CUSTOM_EXCEPTION — Evaluates user-defined exception criteria against planned data and records the resulting exception rows for planner review.

No parameter lists are documented in the ETRM extract; accordingly, only the logical purpose of each routine is stated here. All four are presumably called in sequence or selectively by the parent netting package.

Tables Accessed

The package operates against a defined set of ASCP tables and views accessed through APPS synonyms:

• MSC_ITEM_EXCEPTIONS — stores item-level exception records generated by the exception evaluation logic.
• MSC_X_EXCEPTION_DETAILS — holds the detailed rows of custom exceptions produced by COMPUTE_CUSTOM_EXCEPTION.
• MSC_SUP_DEM_ENTRIES and MSC_SUP_DEM_HISTORY — supply and demand entry and historical data used for forecast accuracy computation.
• MSC_ITEM_SUPPLIERS, MSC_TRADING_PARTNERS, and MSC_TRADING_PARTNER_MAPS — sourcing and trading partner relationships required to resolve supply paths and partner mappings.
• FND_LOOKUP_VALUES — standard Oracle Application Object Library lookup values used for code validation and meaning resolution.
• DUAL — used for scalar computation and validation queries.
• PLITBLM — the Oracle-supplied PL/SQL table type used for in-memory collections within the package.

Usage Notes

MSC_X_NETTING4_PKG is not a user-invocable API. It is invoked internally by MSC_X_NETTING_PKG during plan execution and netting runs, typically triggered from ASCP concurrent programs such as the plan launch and netting programs. The ETRM dependency record shows the package is referenced by one other package (MSC_X_NETTING_PKG) and references that same parent, confirming its role as an internal subroutine library. Customizations should avoid direct calls to this package because its interface may change between patch levels. When troubleshooting ASCP exception generation or forecast accuracy discrepancies, DBAs may query dependency and status information for this package, but its status must remain VALID for the parent netting plan to complete successfully.