Results for “clean_up_process”

16 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_X_EX5_PKG is a PL/SQL package owned by the APPS schema within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. Its identifier, the "X_EX" prefix, indicates that it is a planning-engine extension package; the source header (MSCXEX5S.pls, version 115.2, last modified in 2003) confirms that it is an internal component shipped with the MSC (Material Supply Chain) product family and used to extend the standard planning exception engine. The package is declared with AUTHID CURRENT_USER, meaning that its unqualified references to database objects are resolved against the privileges of the calling user rather than the package owner, a common pattern for engine-side code that must execute under the security context of the planning run.

Functionally, MSC_X_EX5_PKG addresses Vendor Managed Inventory (VMI) exception processing. VMI arrangements require the planning engine to compare supplier-managed replenishment against demand signals and to surface deviations as actionable exceptions. The package encapsulates the logic that identifies those deviations, persists the results, and cleans up the transient working structures used during the computation.

Key Procedures and Functions

  • COMPUTE_VMI_EXCEPTIONS — The principal driver procedure. It is invoked with a refresh number and a replenish time fence. Together these parameters scope the run: the refresh number ties the work to a specific planning refresh cycle, while the replenish time fence defines the planning horizon within which replenishment exceptions are evaluated. The procedure computes VMI exceptions and writes them to the exception detail structures.
  • CLEAN_UP_PROCESS — Performs post-processing housekeeping. Given the package's reliance on global temporary tables and a temporary VMI workspace, this procedure releases or truncates transient data so that subsequent runs start from a clean state.
  • PRINT_DEBUG_INFO — Emits diagnostic output during execution, intended for development and troubleshooting of the planning engine rather than for end users.
  • PRINT_USER_INFO — Emits user-facing informational messages, typically log entries that describe progress or summary counts from the exception computation.

No public functions are declared; all four documented program units are procedures. No parameter lists are reproduced here beyond those visible in the source excerpt.

Tables Accessed

The package reads and writes a set of planning tables through APPS synonyms. The global temporary tables — MSC_X_ITEM_ORGS_GTT, MSC_X_ITEM_SITES_GTT, and MSC_X_ITEM_SUPPLIERS_GTT — serve as session-scoped staging areas for item, site, and supplier combinations under evaluation, consistent with the cleanup procedure. MSC_VMI_TEMP holds the transient VMI working set. MSC_ITEM_EXCEPTIONS and MSC_X_EXCEPTION_DETAILS store the computed exception results, while MSC_ITEM_SUPPLIERS and MSC_TRADING_PARTNERS / MSC_TRADING_PARTNER_SITES supply the sourcing and supplier master data used to determine which items are VMI-managed. MSC_SYSTEM_ITEMS and MSC_SUP_DEM_ENTRIES provide the item and supply/demand inputs to the exception logic, and FND_LOOKUP_VALUES is consulted for reference codes and lookup meanings. The exact read/write direction of each table is not enumerated in the metadata but follows from the exception-computation pattern above.

Usage Notes

MSC_X_EX5_PKG is not intended for direct invocation by end users. It is called by the ASCP planning engine during plan generation and by at least one other package, as the ETRM metadata records a single reverse dependency. In Oracle EBS 12.1.1 and 12.2.2 deployments, the package executes as part of the planning concurrent program flow, typically in the context of the user running the plan rather than as a standalone concurrent request. Customizations should not modify the shipped package; extension should instead be implemented through the supported MSC extension mechanism.

The "x64 Installer (.exe)" search phrase that surfaced this object is unrelated to the package itself, as the package is delivered through the standard EBS patch and RapidInstall media rather than through a standalone binary installer.