Results for “push_replenishment”

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

Overview

WMS_REPLENISHMENT_PUB is the public API package for warehouse replenishment processing within Oracle Warehouse Management (WMS) in Oracle E-Business Suite 12.1.1 and 12.2.2. The package body acts as a thin, externally callable façade over the private implementation package WMS_REPLENISHMENT_PVT. Its central purpose is to expose replenishment logic to concurrent programs, forms, and custom integrations without requiring callers to invoke internal PL/SQL directly. The most prominent entry point is the dynamic replenishment routine, which evaluates current on-hand quantities, item demand, and warehouse configuration rules to generate replenishment tasks that move material from bulk or reserve locations into picking locations. Two distinct calling conventions are provided: a standard PL/SQL procedure returning FND_API-style status, message count, and message data, and a concurrent-program wrapper that maps the same outcome onto the errbuf/retcode convention used by the Concurrent Manager. In addition to dynamic (demand-driven) replenishment, the package covers push replenishment, delivery detail updates, and move order allocation, making it a consolidated access point for the main replenishment operations in the warehouse.

Key Procedures and Functions

• DYNAMIC_REPLENISHMENT — The core entry point for dynamic, demand-driven replenishment. It delegates directly to WMS_REPLENISHMENT_PVT.DYNAMIC_REPLENISHMENT and returns standard API status outputs. It accepts an organization, a batch identifier, a plan-tasks indicator, and a release sequence rule identifier, allowing tasks to be planned only or planned and released according to a defined sequence rule.
• DYNAMIC_REPLENISHMENT_CP — Concurrent-program wrapper for DYNAMIC_REPLENISHMENT. It declares errbuf and retcode outputs, invokes the underlying replenishment logic, copies the API message into errbuf, and sets retcode to 2 on error or 0 on success.
• PUSH_REPLENISHMENT — Executes push (non-demand-driven) replenishment, moving inventory according to configured push rules rather than immediate demand signals.
• PUSH_REPLENISHMENT_CP — Concurrent-program wrapper for PUSH_REPLENISHMENT. Its parameter surface includes organization, item, ABC assignment group, ABC class, order type, and customer class, supporting replenishment targeted at specific item or classification groupings.
• UPDATE_DELIVERY_DETAIL — Updates delivery detail records in conjunction with replenishment activity, keeping outbound delivery information aligned with the replenishment outcome.
• ALLOCATE_REPL_MOVE_ORDER_CP — Concurrent-program entry point that allocates the move orders generated by replenishment, tying replenishment output into the move order transaction flow.

Tables Accessed

ETRM metadata records no directly referenced tables for this package body, because every statement is routed through WMS_REPLENISHMENT_PVT. The private package performs the physical reads and writes on WMS replenishment and move order tables via APPS synonyms. Operationally, dynamic replenishment draws on inventory on-hand and locator/configuration data, while push replenishment reads item and ABC classification attributes supplied as parameters. Replenishment task generation and move order allocation write to the WMS task and move order structures. Because the public package itself contains no SQL, any troubleshooting of table-level behavior must be directed at WMS_REPLENISHMENT_PVT.

Usage Notes

DYNAMIC_REPLENISHMENT_CP and PUSH_REPLENISHMENT_CP are registered as concurrent programs and are normally submitted from the Warehouse Management responsibility or scheduled through the Concurrent Manager, often at intervals or triggered by picking demand. DYNAMIC_REPLENISHMENT and PUSH_REPLENISHMENT are called from custom PL/SQL when programmatic replenishment is required; callers must inspect x_return_status against FND_API.G_RET_STS_SUCCESS and read x_msg_data for diagnostics. ALLOCATE_REPL_MOVE_ORDER_CP is invoked concurrently to allocate replenishment-generated move orders, and UPDATE_DELIVERY_DETAIL supports delivery-related replenishment corrections. The package body is documented as referenced by four other packages, confirming it is a recognised integration surface. The header revision (120.11, dated 2008) indicates the implementation predates 12.1.1 and remains stable across both 12.1.1 and 12.2.2. Direct DML against underlying replenishment tables should be avoided; all standard processing must go through these public procedures.