Search Results compute_late_order

Overview

APPS.MSC_X_NETTING1_PKG is a VALID PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Advanced Supply Chain Planning (ASCP) module, where the MSC_X_ prefix identifies objects dedicated to exception processing and plan output analysis. The package supports netting-related exception computation, providing the logic that detects undesirable planning conditions — late orders, early orders, and demand/forecast mismatches — and surfaces them as actionable exceptions for planners.

The ETRM metadata classifies this package as an "OTHER" API, meaning it is an internal implementation package rather than a documented public API. It is not intended for direct customer invocation. Its purpose is to encapsulate the computation routines that transform raw netting and supply/demand data into exception records stored in the ASCP exception tables.

Key Procedures and Functions

Three documented procedures are exposed by this package. Parameter lists are not published in the ETRM metadata and are therefore not reproduced here.

• COMPUTE_LATE_ORDER — Evaluates orders that are scheduled to arrive after their required need date and generates the corresponding late-order exception. This drives the Late Order exception category used by planners to prioritize expediting actions.
• COMPUTE_EARLY_ORDER — Identifies orders arriving before their required date, producing early-order exceptions. These flag excess or premature supply that may warrant rescheduling or cancellation.
• COMPUTE_FORECAST_MISMATCH — Compares forecast consumption against actual demand to detect mismatches, generating exceptions where forecast and demand diverge beyond tolerance. This supports forecast accuracy analysis within the plan.

Tables Accessed

{{UNRESOLVED_TABLE_LIST}}

Usage Notes

MSC_X_NETTING1_PKG is invoked internally by MSC_X_NETTING_PKG, which the ETRM dependency report identifies as a referencing package, and the package also references itself. It should never be called directly from custom code because its interface is not a supported API and may change between patch levels.

In practice, the package is executed during plan netting and exception-generation runs, typically triggered by the ASCP plan launch concurrent programs. The exception rows produced by its procedures become visible through planner workbench and exception inquiry forms. Customers requiring custom exception logic should extend the underlying exception views or use supported ASCP APIs rather than modifying or wrapping this package.