4/28/2023
Retail
Generated on: 2023-04-28 13:11:51 GMT+0000
SAP S/4HANA | 2022 Latest
PUBLIC
Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/9905622a5c1f49ba84e9076fc83a9c2c?locale=enUS&state=PRODUCTION&version=2022.001
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/docs/disclaimer.
This is custom documentation. For more information, please visit the SAP Help Portal
1
4/28/2023
Replenishment
Use
Replenishment is a method of supplying recipients (sites or external customers) with merchandise on a demand-driven basis. In
replenishment planning, requirements are calculated using the current stock situation. When this has been done, follow-on
documents (for example, purchase orders or sales orders) are generated for the supply of merchandise.
Replenishment for sites
Here you run replenishment planning for an internal customer (for example, a store) that has a site and customer master
record in your system. Replenishment calculates requirements by using previous goods movements, and pays particular
attention to sales that were entered at point of sale (POS) in the store and posted as goods issues in POS inbound processing.
Replenishment for external customers
Replenishment for external customers is used in vendor-managed inventory (VMI), to run requirements planning for customers
as a service. In this case, you must have access to the customer's sales and stock data. For more information, see VendorManaged Inventory (VMI).
A master record for the customer exists in your system, but there is no site master record available.
 Note
This chapter refers only to Replenishment for sites. For detailed information about Rapid Replenishment Planning see SAP
Note 2051280
Integration
Article (or material)
You can process article-related replenishment data using article maintenance.
Site
In the site master, you can maintain the different sets of data for the control of replenishment. You can, for example, determine
the type of follow-on documents that are generated.
Inventory management
You can use the inventory management of materials management (MM) as the basis for replenishment.
POS interface – inbound
During POS inbound processing, the system analyzes sales data, and updates the data as goods issues in inventory
management.
Store order
The system uses store order functions to generate follow-on documents after the replenishment requirements have been
determined.
This is custom documentation. For more information, please visit the SAP Help Portal
2
4/28/2023
Features
Determination of replenishment requirements based on stock data
Simpli ed replenishment-based inventory management enables you to also use replenishment for inventory
management on a non-article basis (value-only inventory management). The usage of MM-based inventory management
is defaulted.
Simpli cation of master data maintenance by grouping sites with similar requirements into requirement groups
Planned receipts and issues (for instance purchase requisitions, purchase orders and order con rmations) can be taken
into consideration using ATP (availability check).
Forecasted sales or consumption can be taken into consideration for the determination of expected stock and for the
calculation of a dynamic target stock.
Sales orders, purchase requisitions, purchase orders, or deliveries can be generated as follow-on documents for
replenishment planning.
Analysis of results from replenishment runs in the replenishment monitor
More Information
Background Processing: Replenishment
Replenishment Planning
Use
Replenishment planning calculates replenishment requirements and then generates follow-on documents for procurement and
delivery. Planning results will be displayed in the replenishment monitor. Here you can see which follow-on documents have been
created and which errors have occurred. You have the option of carrying out replenishment planning in the system online or as a
job.
Prerequisites
If you want to update stock information for replenishment using POS inbound processing, you must have completed processing
before beginning replenishment planning.
Process
1. You can start replenishment planning manually (online) or in the background (in batch) for selected recipients (sites)
and articles.
2. The system calculates expected stock at recipient at the end of the replenishment lead time.
3. If forecast data exists in the system, you can take the forecasted sales until the end of the replenishment lead time into
consideration (see also Replenishment: Forecasts)
If Inventory Management in Materials Management is active, planned store issues and receipts until the end of the
replenishment lead time can be taken into consideration (see also Inclusion of Expected Receipts and Issues for
Replenishment )
4. The system calculates target stock.
This is custom documentation. For more information, please visit the SAP Help Portal
3
4/28/2023
5. Target stock can be calculated using replenishment article data (static target stock) or dynamically when replenishment
planning is carried out (dynamic target stock). You can only work with dynamic target stock if forecasted sales data
exists (see also Replenishment: Example of Planning Using a Dynamic Target Stock).
6. The system calculates your required replenishment quantity.
7. The required replenishment quantity is the difference between the target stock and the expected stock. If you have
maintained a reorder point, a required replenishment quantity is only de ned if the reorder point has not been exceeded
(see also Replenishment: Using a Reorder Point ).
If, while planning replenishments, requirements are determined for components of structured articles, the system
converts the requirement to that for the header article. The follow-on documents are created for the header article. If
required, you can in uence how the system converts the component requirements to header article requirements via a
user exit (see also Replenishment: Structured Articles )
8. In online replenishment planning, the articles to be included in the replenishment run are displayed before follow-on
documents can be generated. You can, for example, lter or sort the data. Here you can also view the required
replenishment quantity for every article – you can change the quantity manually (for example, for test purposes). You
can view a detailed screen for every item which shows how required quantities are de ned.
9. Follow-on documents are generated.
After requirements have been determined, follow-on documents are generated. In case of online planning, you have to start the
follow-on document creation manually on the screen for displaying requirements. The system uses functions for store order
processing to generate follow-on documents (see also Store Orders ). You can generate the following documents:
Purchase requisition
Purchase order
Delivery
Sales order
The system generates follow-on documents and optimizes the quantities required (see also Order Optimizing: Quantity
Optimizing ) .
You can generate follow-on documents in a test mode. Follow-on documents are only generated internally in test modes without
data being written to the database. The results from replenishment runs can be evaluated both in normal mode and test mode,
using the replenishment monitor.
Result
If no errors are recorded, follow-on documents are generated for Replenishment. Each time you execute the program for
planning replenishments, the system stores the replenishment run under an internal number. This number is used to identify a
transaction when you subsequently analyze the run in the replenishment monitor. For further information, see Replenishment
Monitor
Replenishment: Inventory Management Types
When using the Replenishment application component, you can manage inventory in one of two ways:
Materials Management-based Inventory Management
In this case Replenishment is based on the Inventory Management data from Materials Management. Each goods
movement is recorded in a document. You should use this type of Inventory Management as much as possible. It can,
This is custom documentation. For more information, please visit the SAP Help Portal
4
4/28/2023
however, only be used for Replenishment if you manage stocks on an exact article basis (not on a merchandise category
basis).
Replenishment-based Inventory Management
You can activate replenishment-based Inventory Management by selecting the indicator in the replenishment article
data for the article destined for the relevant recipient.
Replenishment-based Inventory Management allows you to replenish stocks of articles managed in MM-based Inventory
Management on a merchandise category basis (value-only article).
In replenishment-based Inventory Management, inventory is managed in a much simpler way than in Materials
Management. The only gure relevant to Replenishment for a particular article at a particular recipient is the stock onhand. No goods movements documents are kept.
The following transactions/events can change replenishment stock:
Posting aggregated sales data (message category WPUUMS) or non-aggregated sales documents (message
category WPUBON) at POS inbound.
Generating follow-on documents in a replenishment run and the correction of replenishment stocks using
document quantities. You can activate corrections using document quantities in the replenishment article master
data.
You can make manual corrections to the replenishment stock using the parameter overview in Replenishment.
The following table illustrates the differences between the two types of Inventory Management:
Characteristics
MM-based Inventory Management
Replenishment-based Inventory
Management
Number of stock types managed
high
only one
Materials movements documents
created
not available
Consideration of planned issues and
possible
not possible
not supported
supported
not set
set
receipts
Article-based stock data for value-only
based Inventory Management
Replenishment-based Inventory
Management indicator
Replenishment: Example Usage Scenarios
Use
The following text lists examples for the usage of replenishment. For each example, the initial situation is rst described, and
then you are shown how you should set the parameters for replenishment in each case.
Standard Procedure
Situation:
Article-based MM inventory management has been activated for stores.
In the standard procedure, sales can be forecasted.
This is custom documentation. For more information, please visit the SAP Help Portal
5
4/28/2023
Sales data from stores is con rmed via POS inbound.
Stores can create orders themselves.
Replenishment parameters:
You use MM-based inventory management, therefore, the indicator for replenishment-based inventory management in
the article master is not set.
In the standard procedure, an MRP type can be used for dynamic target stock.
You take planned issues and receipts into consideration when planning replenishments.
You can choose to de ne a reorder point.
Simpli ed Procedure
Situation:
You carry store stock at value-only article level; that is, MM-based inventory management for the stores is not articlebased.
You do not execute sales forecasts at article/store level.
Sales data from stores is con rmed via POS inbound.
Replenishment parameters:
You use replenishment-based inventory management, therefore, the indicator for replenishment-based inventory
management in the article master is set. You can set the initial stock to zero or enter the current stock manually, which
you have determined externally by using a physical inventory count, for example.
You enter an MRP type in the article master for static target stock. You can set the static target stock using the opening
balance or a value calculated outside the system.
In the article data for replenishment, you can activate the correction of replenishment stocks using the follow-on
documents that have been generated.
You can choose to de ne a reorder point.
Replenishment: Master Data
You can maintain data for replenishment in the article and site masters.
Article master
You can de ne replenishment parameters and forecast data for Replenishment via article maintenance.
Site master
In the site master, pro les for store orders and POS inbound processing are required for replenishment. You can also maintain
requirement groups in the site master.
Replenishment: Article Master Data for Sites
This is custom documentation. For more information, please visit the SAP Help Portal
6
4/28/2023
Use
The article master data contains various data that is relevant for Replenishment. If you want to use replenishment for sites
(internal customers), use article maintenance to enter data.
Features
Maintenance levels
Recipient level
All data relevant to Replenishment is maintained on this level. This is the most detailed maintenance level for data
relevant to Replenishment. You can maintain replenishment parameters in the logistics data of an article for each site.
Requirement group level
Requirement groups make it easier to maintain data for a large number of recipients (sites). If you maintain
replenishment master data for an article at requirement group level (via Extras), the data is copied to the site level,
provided you have de ned a requirement group in the site master for the merchandise category, and the article is listed
in the site.
Data types
The following data is maintained in article maintenance:
Replenishment parameters
RP type
Replenishments can only be planned if you have entered an RP type de ned for Replenishment. The RP type must
be assigned the RP procedure W and a planning method other than 1 (planned by external system). If the RP type
is assigned the forecast indicator + (compulsory forecast), the target stock is calculated dynamically in the
replenishment planning run. If you want to plan using a dynamic target stock, you must have previously forecast
the sales.
Types RP (replenishment planning with static target stock) and RF (replenishment planning with dynamic target
stock) are de ned as standard.
Reorder point
Safety stock
Replenishment-based Inventory Management indicator (Replenish.IM)
If you set the indicator, stocks are determined using Replenishment-based Inventory Management. If you do not
set the indicator, the system calculates stocks using MM-based Inventory Management.
Indicator for correcting replenishment stock with document quantity.
This indicator only has an effect if Replenishment-based Inventory Management is used. If this indicator is set and
replenishment is run, the quantities in follow-on documents generated are added to the stock gure used for
Replenishment and are thus considered as expected goods receipts. It makes sense to set this indicator if the
only information you have as the basis for replenishment is store sales information.
Availability checks
You must enter a check group for the availability check in the logistics data for articles for which expected receipts and
issues are to be included in the planning run.
 Note
This is custom documentation. For more information, please visit the SAP Help Portal
7
4/28/2023
For the determination of receipts issues ATP con guration is used, even thought for the process of the determination
no ATP functions are used.
Forecasts
You can enter forecast data (for example, forecast models) in article maintenance for articles with Inventory
Management on an exact article basis. The forecast is based on Materials Management functions.
Replenishment block
An article can be blocked for replenishment by using the following status in the article master:
General article status
You can choose to set this status either on the client level or the site level. If a block is set, an error message is
generated in Replenishment planning. You can determine the in uence (for example, on Requirements Planning,
Purchasing or Inventory Management) that a particular status may have in article Customizing via control data. In order
to affect Replenishment, you must set a block for requirements planning at the relevant status in Customizing.
Sales status
You can set this status at client level, for the distribution channel or the distribution channel/site level. If a block is set, an
error message appears when generating follow-on documents. You can determine the in uence (for example, on sales
orders or deliveries) that a particular status may have in article customizing via sales relevant data. In order to in uence
replenishment, you must set a replenishment block in article settings for the article status for Retail functions.
Related Information
Vendor Managed Inventory (VMI)
Replenishment: Structured Articles
Use
Replenishment allows you to calculate the requirements for a header article of a structured article based on the requirements
for the relevant components. If you run replenishment for the components and the components are not listed individually, the
component requirements are converted into a header article requirement.
Integration
The following general function is used to calculate the header article requirements based on the component
requirements:Requirements Planning: Calculating the Header Article Quantities Based on the Component Quantities.
Prerequisites
You cannot list components individually for particular sites. Components should only be listed as components of
structured articles. If components are listed individually, they are also procured individually.
You must maintain replenishment data for each component in the article master.
You must enter a unique RP indicator in the logistics data for header articles and related components.
Example
This is custom documentation. For more information, please visit the SAP Help Portal
8
4/28/2023
If you want to maintain the master data for a prepack and run replenishment for components, you must follow the sequence
listed below:
1. Create a generic article (with variants)
Maintain the suitable replenishment data to be copied later into the logistics data at reference site level.
Enter the availability indicator ND in the logistics data at reference site level so that replenishment is not carried out for
that article.
2. Create a bill of materials for a prepack, based on the generic article.
3. List the prepack.
Here, the prepack components, in this case the generic article variants, are also listed. In accordance with the default
logic of the article master, the replenishment master data is generated for the components in the listed sites.
Requirements Planning: Calculation of the Quantity Required of
Header Article from the Component Quantities
Use
This function calculates the quantity required for a header article of a structured article from the quantities required of the
constituent components.
You can incorporate your own method of calculation using User Exit WSOS0001 and component EXIT_SAPLWSOS_001. If you do
not use your own method of calculation , the system calculates the quantity required for a header article using the mean value
method, as explained in the following example:
 Example
A display consists of the following:
Component
BOM quantity
Component 1
10
Component 2
20
Component 3
30
The consumption gures for the components are as follows:
Component
Consumption
Component 1
90
Component 2
160
Component 3
210
For every component, a certain number of displays are required to replace the quantity consumed. This number is the
consumption gures for each component divided by the quantity of each individual component in the bill of material of the
structured article.
This is custom documentation. For more information, please visit the SAP Help Portal
9
4/28/2023
Component
Consumption
BOM quantity
Required Displays
Component 1
90
10
90 / 10 = 9
Component 2
160
20
160 / 20 = 8
Component 3
210
30
210 / 30 = 7
The mean value of all the components is taken as the number of displays required:
Mean value for the number of displays required = (9 + 8 + 7) / 3 = 24 / 3 = 8
If decimal places appear in the calculation, the system rounds down under 0.5, otherwise it rounds up.
Integration
This function is used in the following areas:
Requirements planning
in time-phased planning of components of a structured article
Replenishment
in the planning of replenishments for components of a structured article
Allocation
in allocations using replenishment allocation strategies where structured articles are involved.
Replenishment: Logistical Products
You carry out replenishment planning for logistical products in the same way as for other product categories. The system
processes logistical products based on a slightly different logic.
For general information about logistical products, see Logistical Product.
Replenishment for Stores
Replenishment allows you to calculate the requirements for a logistical product based on the requirements for the sales
product on which the logistical product is based.
 Note
Procurement products are not replenished. If you select any procurement products on the selection screen, the system
lters them out.
As the name implies, procurement products are procured by sites. Therefore, if open quantities exist for any of the
procurement products, they all need be considered in the replenishment calculation.
Sales products are processed very much like single articles and are replenished in the following way:
1. You run replenishment planning for stores by using the Execute Rapid Replenishment app (transaction WRP1R).
This is custom documentation. For more information, please visit the SAP Help Portal
10
4/28/2023
2. You select multiple products including sales products.
3. Replenishment requirements are determined based on stock gures and sales forecast data and are calculated for
single articles and sales products in the same way.
4. Open quantities from planned receipts and issues (for which documents exist) are not only determined for the selected
sales products, but also for all procurement products associated with the sales products.
The system checks availability and generates replenishment requirements. An availability checking group is assigned to
the sales product in article maintenance and can be displayed by using the Change Article, Maintain Article app
(transaction MM42) under
Logistics: store
General control parameters
Checking Group for Availability Check .
The availability check takes into account the documents related to receipts and issues that are speci ed by its checking
group and the checking rule in Customizing for Sales and Distribution under
Transfer of Requirements
Availability Check
Basic Functions
Availability Check and
Con gure Scope of Availability Check . These settings are used for
the sales product and all its associated procurement products.
5. Any open quantities for the procurement products are added to those of the sales product so that the replenishment
process takes into account the sum of all products belonging to a logistical product.
6. You can proceed with replenishment planning without taking into account the planned receipts and issues for
procurement products or you can change the overall replenishment requirement quantity manually to allow for any open
orders for procurement products in the replenishment calculation.
 Note
In the Monitor Replenishment app (transaction WRMO), the overview displays the sum of all quantities for the sales
product and all its associated procurement products.
When you then navigate to the availability details in the Monitor Product Availability app (transaction CO09), only the
documents related to planned receipts and issues of the sales product are displayed. Therefore, the sum of all
quantities for the sales product and all its associated procurement products displayed in the overview and the sum of
the quantities in the availability details might differ.
7. On completion of replenishment planning, follow-on documents are generated in which the sales product is procured.
A follow-on document can be an internal or external purchase order, a stock transport order, or a purchase requisition.
8. When a purchase order is created as a follow-on document or based on a follow-on document (for example, a purchase
requisition) either immediately after replenishment planning or later, if requirements for procurement products were
identi ed, the sales product is automatically replaced with the corresponding procurement product.
 Note
Logistical products are not supported in the replenishment process for external customers.
Replenishment Planning for Distribution Centers (MRP)
You execute replenishment planning for procurement products in distribution centers by using the following applications:
Change Article, Maintain Article app (transaction MM42)
You enter forecast data such as forecast models for procurement products in article maintenance.
Execute Material Forecast app (transaction MP30)
You can carry out an individual forecast for a speci c combination of procurement product and distribution center.
You execute planning runs also for procurement products by using the following applications:
Requirements planning per vendor app (transaction MDW1)
This is custom documentation. For more information, please visit the SAP Help Portal
11
4/28/2023
MRP Live optimized for SAP HANA: Schedule MRP Runs app (transaction MD01N or app ID F1339)
For more information about requirements planning using MRP live, see Related Information.
Classic MRP:
Schedule MRP Runs app (transaction MD01)
MRP - Single-Item, Multi-Level app (transaction MD02)
MRP-Individual Planning-Single Level app (transaction MD03)
Related Information
Replenishment
Carrying Out the Planning Run Using MRP Live
Replenishment: Maintenance of Requirement Groups
Use
When you have to manage a large number of sites or a large number of articles, you can reduce the effort required to maintain
the large amount of data by de ning requirement groups. This prevents you from having to maintain all the data for every
combination of site and article.
Process
You create requirement groups for every merchandise category. A group comprises all the sites who have the same
requirements in a particular merchandise category and who therefore place the same demands on Replenishment.
You maintain requirement groups as follows:
1. You de ne requirements groups in customizing.
2. You list the articles for which you want to de ne requirement group values in all the relevant sites.
3. You maintain replenishment parameters in the article master at requirement group level (and not at site level).
If you have to change a parameter for an article for the whole requirement group, you only have to make one change. If a
particular article is listed in a site, the data at requirement group level is copied to site level.
You can maintain values for speci c articles at site level that differ from the requirement group values. These values are treated
as exceptions and are protected from being overwritten. Some data, such as the RP type, cannot be maintained at requirement
group level. This data must be maintained at site level.
Replenishment: Example of Requirement Groups Usage
Use
The following example illustrates how the use of requirement groups affects replenishment.
Requirement Group Assignment in the Site Master
This is custom documentation. For more information, please visit the SAP Help Portal
12
4/28/2023
The following table illustrates several site master records. A requirement group has been assigned to the confectionery
merchandise category.
Sites
Merchandise category
Description
Requirement group
R151
R1115
Confectionery
01 (large)
R152
R1115
Confectionery
01 (large)
R153
R1115
Confectionery
02 (medium)
Replenishment Article Data at Requirement Group Level
Replenishment data has been de ned at requirement group level for article R100002 (chocolate) in merchandise category
R1115 (confectionery):
Requirement group
Reorder point
Target stock
01 (large)
90
300
02 (medium)
30
120
Replenishment Article Data at Site Level
The system copies the replenishment article data from requirement group level to site level. It does so based on the site group
assignments made in the site master.
Article
Description
Sites
Reorder point
Target stock
R100002
Chocolate
R151
90
300
R100002
Chocolate
R152
90
300
R100002
Chocolate
R153
30
120
Every change made to the replenishment data at requirement group level is automatically copied to the sites. This makes it
more convenient to maintain data when a requirement group contains a very large number of sites.
Replenishment Data at Site Level with Exceptions
Even though site R152 is assigned to a requirement group, you change its reorder point to 80.
Article
Description
Site
Reorder point
Target stock
R100002
Chocolate
R152
80
300
You then change the reorder point for requirement group 01 to 100.
Requirement group
Reorder point
Target stock
01 (large)
100
300
This change is then made for all the sites assigned to the requirement group. The reorder point for site R152 differs from that
for the requirement group. It is therefore treated as an exception and not changed.
This is custom documentation. For more information, please visit the SAP Help Portal
13
4/28/2023
Article
Description
Site
Reorder point
Target stock
R100002
Chocolate
R151
100
300
R100002
Chocolate
R152
80
300
R100002
Chocolate
R153
30
120
Replenishment: Site Master Data
Use
The following data for controlling Replenishment can be maintained in the site master. You can, for example, de ne suggested
values for the type of generated follow-on documents or assign requirement groups to merchandise categories.
Features
In the site master you maintain the following data for controlling Replenishment:
Store order control parameters
Replenishment uses the store order functions to create follow-on documents. You can maintain store order control parameters
in a POS inbound pro le in the Customizing section for POS inbound. Pro les are assigned to sites.
You can also enter special pro les for Replenishment and the Store Order which you can then assign in the site master at
merchandise category level.
The parameters relevant for Replenishment include:
Default setting for the document category
This controls the follow-on document created, for example, purchase orders or deliveries. You can enter different default values
for every type of source of supply (internal or external vendor). If no details exist, the system uses the general default value.
Default delivery type
If the follow-on document created is a delivery, you can enter a default document type for the delivery.
Error message control
POS inbound processing control
To control POS inbound processing, you assign a POS inbound pro le to the site. Depending on the type of Inventory
Management used (MM-based or Replenishment-based), in the Customizing section for POS inbound you must adjust the
process control in the POS inbound pro le for:
Aggregated sales
Sales as per receipts
If you use inventory management in Materials Management, you must set the Inventory Management indicator. The Update
Replenishment Stock indicator should not be set in this case.
This is custom documentation. For more information, please visit the SAP Help Portal
14
4/28/2023
If you use replenishment-based Inventory Management, you must set the Update Replenishment Stock indicator. The Inventory
Management indicator should not be set in this case.
Requirement group control parameters per merchandise category
You can assign a requirement group to each merchandise category in every site for Replenishment. The requirement group
values for the site are thus copied to all articles in the merchandise category listed in the site.
Requirements planning indicator
If you want to run replenishments using the net-change method, you must set the Requirements planning indicator in the
listing/requirements planning data.
Check Consistency of Replenishment Data
Use
You can use this function to manage the replenishment master data consistently and efficiently. You can execute the
replenishment data consistency check function online and in the background
Features
Using this function, you can perform the following activities:
Consistency check
You use this activity to check for and eliminate inconsistencies in table WRPL. The system overwrites any
inconsistent entries in table WRPL with entries from the table MARC.
Deletion of replenishment data
You can delete any entries in tables WRPL and WRPT that are no longer required. The system only deletes entries
that have an MRP type that is not relevant for replenishment.
Deletion of requirement groups
If you maintain replenishment master data using requirement groups, you cannot delete the entries in table
WRPP for all materials in a store. Set this indicator if there are entries in table WRPP for materials that no longer
exist in table WRPL and which therefore need to be deleted.
You can execute the replenishment data consistency check function online and in the background.
Replenishment: Forecasts
Use
In replenishment planning, forecast data is used at two points:
You can consider forecasted sales as expected issues. In doing so, sales are considered from the time of planning until
the end of the replenishment lead time.
If you work with dynamic target stock, the target stock is calculated again, based on forecasted sales data. In this case,
forecasted sales are considered from the end of the replenishment lead time for the duration of the target range of
This is custom documentation. For more information, please visit the SAP Help Portal
15
4/28/2023
coverage.
A number of models are available for running a forecast (for example, trend models or constant models).
Features
If you use article-based inventory management in materials management, you can carry out the forecast by using the
functions of requirements planning.
You can maintain the forecast parameters for each site in the article master.
You can also select the periods in which the forecast values should be determined, for example, each day, each week, or
each month.
Replenishment: Inclusion of Expected Receipts and Issues
Use
In the time between replenishment planning and the sale of goods in the stores, the stock situation in the store can change, due
to goods receipt for example. In replenishment planning, expected receipts and issues can be determined by the system and
used when calculating requirements. When doing so, planned receipts and issues and forecasted sales can be taken into
consideration.
The relevant time period for taking expected receipts and issues into consideration begins on the planning date and ends when
the replenishment lead time ends. For articles with article-based inventory management in materials management (MM), the
replenishment lead time is de ned using article master data (replenishment lead time = purchasing department processing
time + planned delivery time + goods receipt processing time). You can also de ne the corresponding time period for other
articles in replenishment planning.
Features
Receipts/issues
To take planned receipts and issues into consideration, you must set the corresponding indicator in replenishment planning
(Determine Receipts/Issues). If the indicator has been set open receipts / issues are determined for the article until the end of
the replenishment lead time. The expected stock at the end of replenishment lead time is the current stock plus open receipts
minus open issues.
You can consider purchase orders, order con rmations and purchase requisitions as receipts for both, external and internal,
procurement. Stock transport orders and stock transport requisitions are considered as issues. Returns are considered as
“negative” receipts or issues.
Planned issues and receipts can be determined only for articles with MM-based inventory management. For using this feature,
you must enter a check group for availability checks, in the logistics data of the article master for the relevant article. Check
groups for the availability check can be maintained in Customizing for sales and distribution. The check rule for replenishment is
de ned internally as RP.
For a combination of check rule and check group, you de ne the scope of check and use it to determine, for example, which
documents are to be taken into consideration as planned receipts. The setting for the consideration of the replenishment lead
time (RLT) has no in uence on the determination of the receipts/issues. The receipts and issues are always considered up to
end of replenishment lead time
Issues based on forecasted sales
This is custom documentation. For more information, please visit the SAP Help Portal
16
4/28/2023
If you have calculated future sales by using a forecast, you can include these values in the calculation, as issues. To do this, you
must set the indicator Include Forecasted Issues in replenishment planning.
Forecasted sales are considered from the planning date until the end of the replenishment lead time. In comparison, dynamic
target stock includes the sales from the end of the replenishment lead time in the calculation, for the duration of the target
range of coverage.
In replenishment planning, the system considers the forecasted sales for each day. If you use a different period for forecasting
(such as a week or month), the system calculates the average daily sales as follows:
Daily sales = sales per period / number of working days per period
Example
The following examples refer to activities that include expected receipts and issues for replenishment.
Starting Point
The following table shows a replenishment planning run that includes expected receipts and issues. The run results in
replenishment requirements for this week (week 0).
Week
-2
-1
0 (today)
1
2
Target stock
200
200
200
200
200
Actual stock on-
160
145
160
Expected stock
145
135
170
140
150
Expected receipts
55
65
30
60
50
Expected issues
60
50
50
50
50
Replenishment
30
60
50
hand
requirement
How are replenishment requirements determined?
The replenishment requirement for the week is based on the target stock for the week and the expected stock at the time of
the goods receipt. In the example, a replenishment lead time of two weeks is assumed. The replenishment requirement for the
current week is calculated as follows:
Replenishment requirement (week 0)
=
Target stock (week 0)
– expected stock (week 2)
=
200 – 150
=
50
How is expected stock calculated?
The expected stock for any future week is based on the actual stock on-hand for the current week and the expected receipts
and issues from now until the future week. In the example, a replenishment lead time of two weeks is assumed. The expected
stock for week 2 is calculated as follows:
This is custom documentation. For more information, please visit the SAP Help Portal
17
4/28/2023
Expected stock (week 2)
=
Actual stock on-hand (week 0)
+ expected receipts (week 0)
+ expected receipts (week 1)
- expected issues (week 0)
- expected issues (week 1)
=
160 + 30 + 60 – 50 – 50
=
150
Replenishment: Planning Using Dynamic Target Stock
Use
You are planning replenishments of article R100499 (chocolate) in store R151.
Article master
The following data exists for the article:
Parameter
Value
This means:
RP type
RF
Calculate target stock during planning
phase
Replenishment lead time
3 days
Time required between DC R300 placing
PO and store R151 receiving goods
Target range of coverage
7 days
Matches the delivery cycle: weekly
deliveries, on Thursday mornings
Safety stock
10 piece
Stock should not fall below this level.
Maximum target stock
500 piece
Stock should not exceed this level.
Minimum target stock
Not de ned
Stock should not fall below this level.
Current stock
100 piece
Stock level in store R151 on planning date
Forecasts
A forecast is run for the next four weeks for the article and site. The following values are produced:
Calendar week
20
21
22
23
Forecasted sales (in
240
300
240
240
pieces)
Replenishment Planning
You plan replenishments on the Monday evening of week 20, taking expected receipts and issues into account. Since there is a
replenishment lead time of 3 days, a stock transport order is generated as a follow-on document for the replenishment run. The
This is custom documentation. For more information, please visit the SAP Help Portal
18
4/28/2023
stock can be delivered from distribution center R300 by Thursday morning of week 20.
The planning run operates as follows (all quantities in pieces) :
Calculation of the expected stock
1. The stock currently available (100) is determined.
2. Planned receipts and issues are added (period: planning date until the end of the replenishment lead time).
3. No such transactions (receipts / issues) are planned between Monday evening and Thursday morning. The value is
therefore zero.
4. Subtraction of the forecasted sales (period: planning date until the end of the replenishment lead time).
The period taken into account is from Tuesday of week 20 to Wednesday of week 20. Based on 6 working days a week, 40 pieces
would be sold per day in week 20. Over the total period of 2 days (Tuesday and Wednesday):
Forecasted sales = 240 / 6 * 2 = 80
Expected stock:
Expected stock = 100 + 0 - 80 = 20
Calculation of the dynamic target stock
1. Addition of the forecasted sales (period: End of the replenishment lead time until end of the target range of coverage)
2. The period taken into account is from Thursday of week 20 to Wednesday of week 21. 40 pieces would be sold a day in
week 20, 50 in week 21. Over the total period of 6 days (Thursday, Friday, Saturday, Monday, Tuesday and Wednesday):
Forecast sales = 240 / 6 * 3 + 300 / 6 * 3 = 270
3. The safety stock of 10 is added.
4. Target stock:
Target stock = 270 + 10 = 280
5. Limitation using minimum and maximum stock levels
A minimum stock level was not speci ed. The maximum stock level of 500 is not exceeded. The result is therefore not changed.
Calculation of replenishment requirements
Replenishment requirement = target stock - expected stock
= 280 – 20
= 260
Replenishment: Using a Reorder Point
Use
In replenishment article data, you can de ne a reorder point. As a result, replenishment only creates follow-on documents when
the stock on-hand or – if you are including receipts and issues in the calculation – the expected stock has fallen below the
This is custom documentation. For more information, please visit the SAP Help Portal
19
4/28/2023
reorder point. The reorder point is used as it is in reorder point planning.
Example
The following example illustrates the effects of using a reorder point in Replenishment. You have de ned a reorder point of 10
pieces. The Replenishment run generates purchase orders as follow-on documents. Store stock refers to the physical stock
gure in a store.
Transaction
Stocks
Target stock
Requirement
Starting point
100
100
100
Goods issue 80
20
100
20
Replenishment run
20
100
Goods issue 15
5
100
Replenishment run
5
100
Purchase order created
5
100
5
Goods receipt 95
100
100
100
0
Physical stock
20
5
95
5
Executing Replenishment Planning
Use
You can start replenishment planning manually or in the background.
Procedure
From the general initial menu choose
Purchasing
Replenishment
Replenishment Planning .
Manual Start
To manually start replenishment planning for sites, proceed as follows:
1. On the screen Replenishment: Planning, specify the sites or site groups. Make further selections based on article and
merchandise category.
If you want to determine the expected stock at the time of goods receipt, set the indicator Determine Receipts/Issues .
Enter a planning date (in case the default is not suitable), and a period after which the goods receipt should take place.
Planned receipts and issues of the site are then taken into account for this period. However, this is only the case if the
replenishment lead time cannot be determined from the master data (see Inclusion of Expected Receipts and Issues for
Replenishment). If a sales forecast was previously carried out, these values can also be taken into account by setting the
indicator Include forecasted issues.
2. By choosing
Program
Execute , you can calculate and see an overview of the replenishment requirements for the
selected sites.
If you want to change the quantities, proceed as follows:
1. Double-click the quantity. A window appears, in which you see an overview of the stock levels, the expected receipts and
issues, and the resulting replenishment requirements. Change the replenishment requirement.
This is custom documentation. For more information, please visit the SAP Help Portal
20
4/28/2023
2. When you choose
Replenishment Requirements
Generate Follow-On Documents , the quantities are saved and the
follow-on documents (purchase requisition, purchase order, delivery, or sales order) are created.
3. You can then go to the replenishment monitor or the parameter overview. There you can see an overview of any errors
that occurred, the generated work items, and the generated documents.
Start in the Background
To start replenishment planning in the background, you need to schedule the process as a job in the system. If POS inbound
processing takes place, it should be completed before you start replenishment planning.
With background processing, you have the option to set technical parameters that divide the items to be processed into smaller
logical packets.
Replenishment Monitor
Use
You can use the replenishment monitor to analyze the results of replenishment planning. It displays information such as which
items were successfully processed, and in which items errors occurred. For the items with errors, you can analyze the cause. You
identify the replenishment run that you want to analyze via the number that was issued internally by the system.
Prerequisites
When you run replenishment in dialog, you can always go to the monitor. If you want to analyze the results of replenishment
runs that took place in the background or were scheduled as jobs, you must activate the update of replenishment results in
Customizing. In the standard con guration, the update is activated.
Features
In the replenishment monitor, the results are divided into the following categories:
Successfully processed
Work item generated
Errors occurred
Each category contains information about how the items (a combination of recipient and article) were processed.
You can view the potential results of the replenishment run when follow-on documents are generated in test mode when
planning is executed online. Errors that occurred during the generation of follow-on documents are also displayed. You cannot
go to the follow-on documents themselves, since the documents have not yet been stored on the database at this time. From
test mode, you can trigger the posting of documents in the database after you have checked the potential results.
 Note
A number is assigned to every potential follow-on document even when follow-on documents are generated in test mode.
The number is taken from the relevant number range. If you exit test mode without posting documents in the database, their
current number levels are increased nonetheless. The document numbers assigned in test mode are therefore “used”, and
they can no longer be assigned to other documents.
This is custom documentation. For more information, please visit the SAP Help Portal
21
4/28/2023
Activities
The logs of replenishment results that are no longer required can be deleted from the system by using report RWRPLDEL
(transaction WRDL). How often you delete this data should depend on the volume of data in the system.
This is custom documentation. For more information, please visit the SAP Help Portal
22