Results for “msc_item_suppliers_temp”

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

Overview

MSC_X_REPLENISH is a PL/SQL package body in the APPS schema that implements vendor-managed inventory (VMI) replenishment logic within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) and Collaborative Planning modules. It is classified as a utility/engine package (API classification OTHER) rather than a public business API. Its principal business function is to calculate and execute VMI replenishment recommendations for both the supplier side (VMI) and the customer side (CVMI, customer vendor-managed inventory), and to drive the resulting replenishment actions into requisitions and workflow notifications. The header comment ($Header: MSCXSFVB.pls 120.7 2008/02/25) confirms that the package has been stable across the 12.1.1 and 12.2.2 code lines, with the last shipped revision predating both releases.

Key Procedures and Functions

The package exposes fifteen documented procedures and functions:

• VMI_REPLENISH_WRAPPER — Entry point for the concurrent program. It evaluates supplier and customer replenishment flags and invokes the appropriate VMI engine with the supplied time fences.
• VMI_REPLENISH_CONCURRENT — Concurrent-program driver for supplier-side replenishment.
• VMI_REPLENISH_WF — Workflow-invoked variant of the replenishment routine.
• VMI_REPLENISH — Core supplier VMI replenishment engine.
• VMI_RELEASE — Releases approved replenishment recommendations to downstream execution.
• VMI_REJECT — Rejects replenishment recommendations that fail validation or approval.
• IS_VMI_ITEM — Predicate that determines whether an item participates in VMI.
• IS_AUTO_RELEASE — Predicate that determines whether a recommendation may be released automatically.
• IS_SELLER_APPROVE — Predicate controlling whether the seller (supplier) approval step is required.
• PRINT_DEBUG_INFO — Diagnostic logging gated by the MSC_CP_DEBUG profile option.
• PRINT_USER_INFO — Writes user-facing informational output.
• APS_TO_SCE / SCE_TO_APS — Conversion utilities between the planning (APS) and execution (SCE) representations of replenishment data.
• CREATE_REQUISITION — Creates purchase requisitions from approved VMI replenishment demand.
• TEMP_TABLES — Manages temporary staging tables used during processing.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• MSC_ITEM_SUPPLIERS — Stores supplier-item sourcing rules and the VMI flags (including vmi_flag and vmi_refresh_flag) that drive eligibility and refresh behavior.
• MSC_SYSTEM_ITEMS, MSC_ITEMS — Item master / planning item attributes.
• MSC_COMPANIES, MSC_COMPANY_SITES, MSC_COMPANY_RELATIONSHIPS, MSC_COMPANY_USERS, MSC_PARTNER_CONTACTS — Trading-partner and contact data for supplier/customer relationships.
• MSC_APPS_INSTANCES, MSC_PLAN_ORG_STATUS, MSC_PLANNERS — Instance, plan organization, and planner context.
• MSC_SUP_DEM_ENTRIES, MSC_SUP_DEM_ENTRIES_S — Supplier demand entries generated or consumed by the replenishment engine.
• MSC_PO_REQUISITIONS_INTERFACE — Interface table populated by CREATE_REQUISITION for downstream purchasing.
• MSC_TP_ID_LID — Trading-partner identifier mapping.

Notably, the reset_vmi_refresh_flag routine updates MSC_ITEM_SUPPLIERS for records where plan_id = -1 and vmi_flag = 1, clearing the refresh indicator after processing.

Usage Notes

MSC_X_REPLENISH is invoked primarily from concurrent programs in the Advanced Supply Chain Planning responsibility; the wrapper procedure accepts replenish flags and time-fence parameters and dispatches to the supplier and customer engines. Because the package body is owned by APPS and referenced by three other packages, the documented procedures (notably IS_VMI_ITEM, IS_AUTO_RELEASE, IS_SELLER_APPROVE, APS_TO_SCE, and SCE_TO_APS) may also be called from custom concurrent programs, workflow processes, or extension code. The MSC_CP_DEBUG profile option controls debug logging. The wrapper is wrapped in an exception handler that logs the error and re-raises it, so failures surface to the concurrent manager. Direct updates to MSC_ITEM_SUPPLIERS should be avoided outside this package to preserve refresh-flag integrity. Because the shipped source revision predates 12.1.1 (120.7, dated 2008), behavior is consistent across 12.1.1 and 12.2.2, but any customization should be validated against the corresponding file version in each environment.