Results for “vmi_release_api_load”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MSC_X_CVMI_REPLENISH is a customer-facing Vendor Managed Inventory (VMI) replenishment engine within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. The package body implements the business logic required to evaluate, approve, and release VMI replenishment orders between a supplier and a customer organization. It forms part of the MSC (Materials and Supply Chain) schema family owned by APPS and is classified as an OTHER-type API in the ETRM repository.
The header comment references the file MSCXCFVB.pls at version 120.3, last modified in December 2005, indicating the package traces its origin to earlier ASCP releases and remains compatible through EBS 12.1.1 and 12.2.2. The "X" in the package name signals an extensible or customer-facing routine, and the "CVMI" prefix denotes Customer VMI processing. The engine is driven by refresh numbers that track netting runs against the sup_dem_entries tables.
Key Procedures and Functions
- VMI_REPLENISH_CONCURRENT — The primary concurrent entry point. It calculates average daily demand via MSC_X_CVMI_PLANNING, determines the current and last refresh numbers from MSC_SUP_DEM_ENTRIES and MSC_PLAN_ORG_STATUS, and seeds replenishment status records before processing.
- VMI_REPLENISH — Executes the core replenishment calculation for qualifying supplier-customer relationships.
- VMI_REJECT — Rejects a proposed replenishment, presumably when validation or supplier approval fails.
- IS_AUTO_RELEASE — Determines whether a replenishment order qualifies for automatic release without manual intervention.
- IS_SUPPLIER_APPROVAL — Checks whether supplier approval is required prior to release.
- VMI_RELEASE_API, VMI_RELEASE_API_UI, VMI_RELEASE_API_LOAD — Public interfaces for releasing VMI orders, invoked from user interfaces and bulk load routines.
- VMI_REPLENISH_WF — Workflow-integrated replenishment processing.
- PRINT_USER_INFO and PRINT_DEBUG_INFO — Logging utilities honoring the MSC_CP_DEBUG profile option.
- RESET_VMI_REFRESH_FLAG — Resets the refresh flag controlling incremental processing.
Tables Accessed
The package reads and writes several MSC tables through APPS synonyms. MSC_COMPANIES, MSC_COMPANY_SITES, MSC_COMPANY_RELATIONSHIPS, MSC_TRADING_PARTNERS, and MSC_TRADING_PARTNER_MAPS define supplier-customer sourcing relationships and site-level associations. MSC_ITEMS and MSC_SYSTEM_ITEMS identify the planned inventory items. MSC_SUP_DEM_ENTRIES and MSC_SUP_DEM_ENTRIES_S hold supplier demand and replenishment records keyed by refresh number; MSC_PLAN_ORG_STATUS stores netting run status per plan, organization, and source instance. MSC_PLANNERS, MSC_PARTNER_CONTACTS, and MSC_VMI_TEMP support planner lookup, contact resolution, and intermediate processing. MRP_ATP_SCHEDULE_TEMP_S is used for ATP-based scheduling checks, and DUAL supports singleton queries.
Usage Notes
MSC_X_CVMI_REPLENISH is typically invoked through the VMI replenishment concurrent program, which calls VMI_REPLENISH_CONCURRENT to orchestrate refresh-number validation, demand averaging, and replenishment generation. Release operations may be triggered from VMI workbenches or the release APIs exposed for UI and bulk load scenarios; workflow-enabled replenishment routes through VMI_REPLENISH_WF. The package is referenced by two other packages in the ETRM metadata, indicating reuse by dependent ASCP components. The global g_msc_cp_debug variable, initialized from the MSC_CP_DEBUG profile, governs debug output for diagnostics. Debug logging should be disabled in production to avoid performance overhead during large netting runs.