Scheduling of Planned Receipts
A planned receipt for a raw net demand must be available at the customer location at the beginning of the demand period. However, the schedule of the planned receipt must be feasible. This means that the schedule must agree with the calendars and execution times for the delivery-relevant activities on the supplier side and customer side.
Example
The system must consider the following questions for the planned receipt:
According to the receipt calendar of the customer location, is an inbound delivery even possible at the requirement date/time at the customer location? In other words, can the customer accept the goods and execute the goods receipt?
Is a timely inbound delivery even possible in the case of immediate shipping at the ship-from location? Or is the requirement date/time so near in the future that the inbound delivery will definitely occur too late?
To determine the availability date/time for a planned receipt at the customer location (the date on which the customer has completed the goods receipt), as well as further dependent predecessor dates/times, the system performs a scheduling. In doing so, the system takes into account the calendars and execution times of the delivery-relevant processes on the supplier side and customer side (for example, goods issue, transport, and goods receipt), and the settings you have made for the base date for replenishment planning. Depending on the calendars and execution times, a planned receipt can also be available before or after the requirement period at the customer location.
Features
Processing of TS-Based Planned Receipts and Planned Replenishment Orders
The replenishment service can save planned receipts as time series (for example, relevant for SMI) or as planned replenishment orders (for example, relevant for RR). A time-series-based (TS-based) planned receipt and a planned replenishment order are two different object types (a key figure or an order document of the order document type DRPV
). Different date/time types are relevant for these object types, as follows:
Date/time of a time-series-based planned receipt
A TS-based planned receipt only contains the availability date/time at the customer location.
Dates/times of a planned replenishment order
A planned replenishment order contains, in addition to the availability date/time at the customer location, the delivery date/time and further dates/times on the supplier side. These dates/times depend on the scheduling schema used.
Scheduling Logic
The starting point of the scheduling is the requirement date. This is the beginning of the period in which the raw net demand lies. Starting at the requirement date, the system conducts a backward scheduling, to determine a feasible availability date/time at the customer location and – in the case of a planned replenishment order – to determine further dependent dates/times. In doing so, the system takes into account the relevant calendars and execution times.
A planned receipt is not allowed to have any dates/times that lie in the past. (In particular, in the case of a planned replenishment order, the order processing date is not allowed to lie in the past.) If the backward scheduling leads to a date/time that lies in the past, the system conducts a forward scheduling. The scheduling starts on the current date/time (today).
Base Date for Replenishment Planning
A key date for the scheduling logic is the base date for replenishment planning. By default, it is the availability date at the customer location. However, you can define for any combinations of supplier, customer location, and product, that the replenishment is based on the delivery date. For example, the goods receipt processing time is set in the product master, and you want the goods receipt processing time not to be considered for a supplier’s replenishment plan. When scheduling is done for products whose replenishment is based on the delivery date, the goods receipt processing time is considered 0, thus the availability date is equal to the delivery date.