Search Results msc_so_release_s

Overview

APPS.MSC_X_CUST_FACING_RELEASE is a customer-facing release package body within the Oracle E-Business Suite Advanced Supply Chain Planning and Vendor Managed Inventory (VMI) footprint. Its principal business function is to communicate authorized supply releases to trading partners and to coordinate the launch of downstream release programs on the source instance. The package forms part of the outbound release mechanism in which planning results, consignment data, and sales order commitments are translated into release records that suppliers and customers can act upon.

The package header comment block exposes implementation-level detail that informs its use in Oracle EBS 12.1.1 and 12.2.2. A global variable, G_VMI_OM_ORDER_TYPE, is initialized from the profile option MSC_X_VMI_OM_ORDER_TYPE. The value of this profile is loaded at package instantiation time via FND_PROFILE.VALUE, meaning any change to the profile requires a new database session before it takes effect. The package also reads the MSC_CP_DEBUG profile to gate diagnostic output written through FND_FILE.PUT_LINE to the concurrent request log, using the helper procedures log_message and LOG_DEBUG.

Key Procedures and Functions

• VMI_RELEASE — drives the primary VMI release processing path, assembling and emitting supplier-facing release information.
• SCHEDULE_DATE_CHANGED — detects or responds to changes in scheduled dates so that release output reflects revised supply timing.
• UPDATE_SO_ATP_OVERRIDE — maintains the available-to-promise override associated with sales order lines participating in the release process.
• DELETE_INTERFACE_RECORD — removes processed or superseded rows from the release interface, keeping the staging area clean for subsequent runs.
• IS_CONSIGNED_VMI — evaluates whether an item or trading relationship qualifies for consigned VMI handling, returning a Boolean-style determination used to branch processing logic.
• CREATE_VMI_RELEASE — constructs the release record itself and initiates the release program on the source instance, supporting both a primary database link (p_dblink) and an A2M link (p_a2m_dblink), a pattern consistent with multi-instance deployments.

Tables Accessed

All documented table references are resolved through APPS synonyms. MSC_SO_RELEASE_INTERFACE and MSC_SO_RELEASE_S hold staged and stored release records. MSC_SUP_DEM_ENTRIES supplies supply and demand planning detail. MSC_TRADING_PARTNERS and MSC_TRADING_PARTNER_SITES provide partner and site identities. MSC_TP_ID_LID and MSC_TP_SITE_ID_LID resolve trading partner identifiers for cross-instance transfers. MSC_APPS_INSTANCES, MRP_AP_APPS_INSTANCES_ALL, and DUAL support instance discovery and control-flow queries.

Usage Notes

The package is compiled under APPS and is classified as OTHER rather than as a public API. It is referenced by zero other packages, indicating it is invoked directly rather than as a shared library. Typical invocation is from the concurrent manager during VMI release processing, or from custom code performing cross-instance release dispatch. Because G_VMI_OM_ORDER_TYPE derives from the MSC_X_VMI_OM_ORDER_TYPE profile option, the effective order type must be set before the processing session begins.