Rapid Replenishment Planning
With this feature, you can use a performance-optimized method for replenishment planning, which is called rapid replenishment planning.
Rapid replenishment planning allows you to save substantial runtime in the replenishment planning process, depending on the planning scenario used. The response time in dialog planning for larger numbers of items is noticeably better. Batch planning takes significantly less time, so the planning process can be scheduled for a later point in time and/or will be finished earlier, and system resources can be used for other tasks.
Rapid replenishment planning uses the same master data and control data (from Customizing) as classic replenishment planning, provides the same calculation logic, and is fully integrated into the overall replenishment process (for example, usage of the replenishment monitor or parameter overview, lock concept). Business Add-Ins and user exits of classic replenishment can still be used with rapid replenishment planning. The main differences between rapid replenishment planning and classic replenishment planning are:
Rapid replenishment planning can be used only for sites, not for external customers. Only forecasts from materials management can be used, not from flexible planning.
The determination of receipts/issues is not performed via functions of ATP (Available-to-Promise), although the existing ATP control is used for rapid replenishment planning. With the current version of rapid replenishment planning, purchase orders, order confirmations, and purchase requisitions can be considered as receipts/issues (both for external and internal procurement). There are some minor differences in the consideration logic for open receipts/issues, compared to ATP.
Rapid replenishment planning is executed via transaction WRP1R
(report RWRPLRRP
), which is available after activation of business function ISR_APPL_RRPL
. Rapid replenishment planning and classic replenishment planning can be used at the same time.
Rapid replenishment planning, with its optimized runtime and alternative data access implemented as core data services (CDS), is an alternative to classic replenishment planning (transaction WRP1
).
The database access contains joins to multiple tables with conditions, aggregations, and calculations. Database access like this can be very efficiently executed in a column-based in-memory database such as SAP HANA, especially when processing large data sets. The execution performance may also improve significantly on other database platforms.
The actual performance impact also depends largely on the replenishment scenario as well as on data volumes and the execution mode for replenishment planning. See SAP Note 2051280
for more details, also about database specific information. You should evaluate the performance and functional fit of rapid replenishment planning for your actual use case and potentially adjust the execution mode (for example, packet size) before using it productively.
Classic replenishment planning is, as before, available on all database platforms supported by ECC Retail.
Technical Details
Technical Name of Product Feature | ISR_ERP6_EHP7_SP07_RRPL |
|---|---|
Product Feature Is | New |
Country Dependency | Valid for all countries |
Software Component Version | SAP APPL 6.17 |
Application Component | IS-R-PUR-RP |
Available as of | SAP Enhancement Package 7 (SP08) for SAP ERP 6.0 |
Required Business Functions |