Search Results vmi_release

Overview

MSC_X_CUST_FACING_RELEASE is an Oracle EBS Applications (APPS) schema package that supports customer-facing release processing within Oracle Supply Chain Planning and the VMI (Vendor Managed Inventory) / supplier collaboration flows. The package is compiled with AUTHID CURRENT_USER, meaning its unqualified object references resolve against the invoking user's schema, and it exposes a set of PL/SQL procedures designed primarily as Workflow-callable APIs (each documented entry point follows the standard Workflow procedure signature: itemtype, itemkey, actid, funcmode, and resultout).

The package encapsulates the business rules governing release of planned replenishment orders and consumption advice to trading partners. Its constant declarations reveal the domain model: release types (replenishment, planner override ATP, consumption advice), VMI types (consigned versus unconsigned), release statuses (unreleased, released), operation modes (create, update), and outcome codes (success, warning, error, successful). These constants are referenced by the Workflow processes that drive customer-facing release generation. In the context of the search term create_vmi_release, the package is the primary repository object that exposes this named procedure.

Key Procedures and Functions

The ETRM metadata documents six procedures, all declared in the package specification:

• CREATE_VMI_RELEASE — the primary VMI release creation routine. It accepts item, customer, customer site, release ID, destination, and instance context information along with the standard Workflow parameters, and returns ERRBUF and RETCODE outputs. It is the procedure most directly associated with the user's search and is intended to generate a VMI release for the specified customer and item.
• VMI_RELEASE — the Workflow entry point that orchestrates VMI release processing, dispatching based on release type and VMI type constants.
• SCHEDULE_DATE_CHANGED — handles the business event where a scheduled date on a release changes, triggering downstream recalculation or notification.
• UPDATE_SO_ATP_OVERRIDE — applies or updates a planner ATP override associated with a sales order release.
• DELETE_INTERFACE_RECORD — removes staging/interface rows, typically after successful processing or when a release is cancelled.
• IS_CONSIGNED_VMI — a predicate-style procedure returning whether the VMI arrangement in context is consigned, using the G_CONSIGNED_VMI / G_UNCONSIGNED_VMI constants.

The metadata does not expose parameter lists for the remaining procedures; these are not reproduced here to avoid speculation.

Tables Accessed

According to the documented table references (via APPS synonyms), the package reads and writes:

• MSC_SO_RELEASE_INTERFACE and MSC_SO_RELEASE_S — the release interface and base release tables that hold the release records being created, queried, or deleted.
• MSC_TRADING_PARTNERS and MSC_TRADING_PARTNER_SITES — provide customer and customer site context for release generation.
• MSC_TP_ID_LID and MSC_TP_SITE_ID_LID — the trading partner ID and site ID lookup/denormalization tables used to resolve internal identifiers.
• MSC_SUP_DEM_ENTRIES — supply/demand entries underpinning replenishment quantity and date logic.
• MSC_APPS_INSTANCES, MRP_AP_APPS_INSTANCES_ALL — instance and application instance context, used where multi-instance or multi-org resolution is required (the p_instance_id parameter in CREATE_VMI_RELEASE aligns with this).
• DUAL — used for constant evaluation and single-row expression evaluation.

Usage Notes

MSC_X_CUST_FACING_RELEASE is not referenced by any other documented package, indicating it sits at the top of the call stack rather than acting as a shared utility. It is invoked in three principal ways: (1) as Workflow activity functions, where the standard itemtype/itemkey/actid/funcmode/resultout signature is required by the Oracle Workflow engine; (2) as underlying logic for scheduled concurrent processes and planning-engine output processing that generate customer-facing releases; and (3) from custom extensions or concurrent program wrappers, particularly for CREATE_VMI_RELEASE, which exposes ERRBUF/RETCODE outputs suitable for direct invocation. Because the package is AUTHID CURRENT_USER, callers must ensure the invoking schema has privileges on the underlying base objects. Administrators customizing VMI or supplier collaboration flows should treat CREATE_VMI_RELEASE and VMI_RELEASE as the supported entry points and avoid direct DML against MSC_SO_RELEASE_INTERFACE.