Replenishment Service
The replenishment service (technical name REPL_SERVICE
) is a planning service that executes replenishment planning for the selected customer location products. A result of replenishment planning are the planned receipts in the customer location and corresponding
updated key figures. You can use the Planning Service Manager (see Planning Service Manager) to execute the replenishment service in the background. In the replenishment monitors, you can call the replenishment service
using the Propose Planned Receipts
function.
The replenishment service plans on the level of the following characteristics:
Product
Customer location
Supplier
Promotion ID (only relevant for Responsive Replenishment
)
The replenishment service only executes a replenishment planning for a customer location product if the location product status of the customer location product allows it. For customer location products with the status Inactive
or Discontinued
,
the replenishment service does not execute a replenishment planning. For more information, see Location Product Status.
SAP SNC can use the supplier back-end product when communicating with the supplier back-end system. Data in the XML messages is therefore based on the supplier back-end product. Upon receipt of an XML message, SAP SNC executes product determination and thereby determines the planning product, in other words, the product for which you are executing the replenishment planning in SAP SNC. When the supplier sends a replenishment order to the supplier back-end system, the system again executes a product determination for the outbound XML message, to determine the supplier back-end product. For more information, see Use of Supplier Back-End Products and Products.
The replenishment service executes the replenishment planning for the planning horizon. You can define the start and the duration of the planning horizon as follows:
You can configure the duration of the planning horizon in Customizing for Supply Network Collaboration
, under .
You can determine the start of the planning horizon in the replenishment service profile. To do this, you specify a number of hours by which you want to shift the start of the planning horizon in the future or in the past.
In the replenishment monitors, the replenishment service uses the following planning horizon:
If you have not determined a planning horizon in Customizing, the replenishment service uses the display horizon of the replenishment monitor that you determine in the time buckets profile (see Defining Time Bucket Profiles).
If you have determined a planning horizon in Customizing, the replenishment service uses the intersection of this planning horizon and the display horizon.
You can make settings so that the replenishment service first deletes the existing planned receipts before it creates a new planning. To do this, you select the Clear Planned Receipts
checkbox. If you do not select this checkbox, the replenishment
service function does not delete the existing planned receipts. This has the following consequences: When the projected stock in a period falls below the reorder point, the replenishment service increases the existing planned receipt in this period accordingly, to reach the target
stock. If, as a result, the projected stock exceeds the maximum stock level in the subsequent period, the function does not reduce the planned receipt in this subsequent period. If you do set the indicator, you can avoid such surplus.
You select the checkbox in Customizing for Supply Network Collaboration
under . For the SMI Monitor and the Min/Max Replenishment Monitor, you can also select the checkbox on the Web user interface (Web UI) in the monitor settings. For more information, see Example:
Clearing Planned Receipts.
In the standard system, the replenishment service deletes unpublished TLB shipments and the assigned replenishment orders at the beginning of the planning run. You can configure the replenishment service profile so that the replenishment service does not delete these objects.
The replenishment services uses sourcing to determine the following data:
The ship-from location that is to prepare a planned receipt
The means of transport with which the planned receipt is to be shipped
The following sourcing methods are available:
Static sourcing (creates planned receipts)
Dynamic sourcing (creates TLB shipments)
For more information, see Sourcing.
For the replenishment service to be able to calculate the raw net demand of a period, it must first calculate the projected stock. You configure how the replenishment service calculates the projected stock in Customizing for Supply Network Collaboration
. For more
information, see Calculation of Projected Stock.
The raw net demand represents the unrounded net demand of the customer location product in a period. The raw net demand is the demand that the supplier must actually cover with planned receipts. In the raw net demand, the system - contrary to the gross demand - considers the existing stocks and receipts. The raw net demand is the basis for calculating the planned receipts: The replenishment service determines the quantity of the planned receipt by rounding the demand quantity up or down. For more information, see Calculation of Raw Net Demand.
A planned receipt for a raw net demand must occur as punctually as possible. The dates/times for the outbound and inbound delivery must agree with the calendars and execution times for all delivery-relevant activities on the supplier side and customer side. To determine these dates/times, the replenishment services conducts a scheduling. Depending on the calendars and the execution times, a planned receipt can occur before or after the actual demand period. For more information, see Scheduling of Planned Receipts.
To cover the raw net demand as punctually as possible, the scheduling (see above) creates a planned receipt for a particular raw net demand on a date/time that lies in or as close as possible to the demand period. In doing so, the system takes into account the relevant calendars and execution times. In this way, the planned receipts for different raw net demands can come together in a period. The replenishment service groups these quantities together into one planned receipt. In addition, the replenishment service now applies different restrictions for the receipt quantity: It rounds the receipt quantity according to the rounding settings in the master data. In an SCM server installation, the replenishment service can also consider product allocations. For more information, see Rounding Using One Rounding Value, Two-Level Rounding, and Consideration of Product Allocations.
You can configure whether the replenishment planning saves planned receipts as time series in Time Series Data Management (TSDM) or as planned replenishment orders (order document type DRPV
) in Order Document Management (ODM). In the Supplier Managed
Inventory
business scenario, for example, you use time series; in the Responsive Replenishment
business scenario, you use planned replenishment orders. Thus, depending on your settings, the key figure Planned Receipts
represents
time series data or planned replenishment orders.
When advanced shipping notifications (ASNs) and replenishment orders are published, the system also updates the key figure Planned Receipts
based on the formula used for the projected stock. For more information, see Update
of the "Planned Receipts" Key Figure.
The replenishment service creates the following objects and updates the corresponding key figures:
Planned Receipts
TLB shipments (only in the case of dynamic sourcing)
Substitution orders (only in the case of product interchangeability)
Baseline Stock Used for Promotion
indicator
In the following cases, the system automatically saves the results of a replenishment service run:
If you execute the replenishment service in the Planning Service Manager
If the supplier executes the replenishment service in the overview screen of a replenishment monitor
On the details screen of a replenishment monitor, the supplier must save the results manually by choosing the Save
function.
Note
Customers can only perform simulative planning in the replenishment monitor and therefore they cannot save their planning.