Search Results csp_minmax_pvt




Overview
Explore in AI Chat

Overview

APPS.CSP_MINMAX_PVT is a private PL/SQL package body in the Oracle E-Business Suite Applications schema that implements the core logic for min-max planning and replenishment across inventory, purchasing, and work-in-process organizations. In the ETRM 12.2.2 classification, this object is designated as a PVT (private) API, meaning it is intended for internal consumption by the public CSP min-max planning APIs, concurrent programs, and other dependent packages rather than by external integrators. Its principal entry point, RUN_MIN_MAX_PLAN, evaluates on-hand, demand, and supply balances against item min-max parameters, determines which items require replenishment, and generates the resulting requisitions, move orders, and discrete or repetitive job suggestions. The package therefore underpins automated material replenishment in both discrete manufacturing and distribution-intensive environments. The object holds VALID status and is owned by APPS.

Key Procedures and Functions

The documented package exposes six procedures and functions, each addressing a distinct phase of the min-max planning cycle:

  • RUN_MIN_MAX_PLAN — the driving routine that executes the min-max planning process, calculating net requirements and building replenishment recommendations.
  • GET_ONHAND_QTY — derives the current on-hand quantity for an item in the relevant inventory organization and subinventory context.
  • DO_RESTOCK — performs the restocking action once a replenishment requirement has been identified and approved by the planning logic.
  • GET_SHIPPED_QTY — computes quantities shipped, used to establish historical demand or consumption patterns.
  • GET_STAGED_QTY — retrieves quantities staged in the shipping or staging subinventory for planning purposes.
  • GET_PICK_RELEASED_QTY — returns quantities already released through picking, ensuring replenishment logic does not over-order material in transit.

Together these routines provide the quantitative foundation for min-max decisions, with RUN_MIN_MAX_PLAN orchestrating the quantity functions and DO_RESTOCK applying the resulting actions.

Tables Accessed

The package reads and writes a broad set of inventory, planning, and sourcing tables through APPS synonyms. Item master data is sourced from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_REVISIONS, and MTL_CATEGORIES / MTL_CATEGORIES_KFV. On-hand, reservation, and transaction positions come from MTL_ONHAND_QUANTITIES_DETAIL, MTL_RESERVATIONS, MTL_MATERIAL_TRANSACTIONS, and MTL_MATERIAL_TRANSACTIONS_TEMP, while MTL_DEMAND and INV_MIN_MAX_TEMP supply demand and working-set data. Organization and subinventory definitions are drawn from MTL_PARAMETERS and MTL_SECONDARY_INVENTORIES, with transaction classifications resolved via MTL_TRANSACTION_TYPES and MFG_LOOKUPS. Replenishment output touches MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES (move orders), PO_REQUISITION_LINES_ALL, PO_REQ_DISTRIBUTIONS_ALL, and PO_REQUISITIONS_INTERFACE_ALL (requisitions), and the WIP family of tables (WIP_DISCRETE_JOBS, WIP_REPETITIVE_ITEMS, WIP_REPETITIVE_SCHEDULES, WIP_REQUIREMENT_OPERATIONS, WIP_JOB_SCHEDULE_INTERFACE, WIP_FLOW_SCHEDULES) for job suggestions. Calendar dates come from BOM_CALENDAR_DATES and WIP_CALENDAR, with OE_ORDER_LINES_ALL and PER_ALL_PEOPLE_F supplying order and user context.

Usage Notes

CSP_MINMAX_PVT is typically invoked indirectly rather than called directly by custom code. It is referenced by two dependent packages and by standard concurrent programs that run min-max planning for a specified organization, planner, and item range. External utilities such as INV_CREATE_MOVE_ORDER_PVT, FND_API, INV_DECIMALS_PUB, INV_LOG_UTIL, and INV_GLOBALS are leveraged for move-order creation, error handling, rounding, logging, and global constants. The package is not referenced by any other database object.