3610010 - How the requirement date of the stock transfer purchase requisition is calculated?

Special procurement type key for stock transfer is activated for the material and plant A is the ordering plant and plant B is the delivering plant.
After the MRP run, stock transfer requisition is generated to transfer the material from B to A.
In the delivering plant B, the requirement date of the stock transfer purchase requisition is calculated and displayed in the Monitor Stock / Requirements List (MD04). However, the calculation logic is unclear and the result is not understandable.

This article will provide a general explanation on how this requirement date is calculated.

SAP S/4HANA Cloud Public Edition

Before introducing the calculation logic, some terms and their dependencies should be clarified:

• Requirement date of the stock transfer purchase requisition in the delivering plant: This is the date when the material should be available in stock for the transfer. It is the date that is displayed in MD04.
  
  
• Delivery date: The delivery date is the date at which the ordering plant receives the goods. The delivery date plus GR processing time (working days) determines the MRP availability date of the input in the ordering plant.
  
  
• Planned delivery time (factory calendar days): The planned delivery time from the material master of the ordering plant represents the move time between the plants in this processing. This can be check in the master data.
• Processing time of purchasing: The processing time of purchasing is the time which is needed by the purchasing department of the ordering plant to convert a purchase requisition into a purchase order. This can be check in SSCUI 102156 - Define Plant Parameters Overview.
  
  
• PO date: The date at which the purchase order is created.
  
  
• Release date: The date at which the purchase requisition is created.

The basic relationship between them are:
PO date = release date + processing time of purchasing
Delivery date = PO date + planned delivery time
MRP availability date in the ordering plant. = delivery date + GR processing time

Then regarding the calculation of the requirement date of the stock transfer purchase requisition (PRqRel) in the delivering plant, there are 2 scenarios:
1. If the planned delivery time is greater than 0:
Requirement date of the stock transfer purchase requisition in the delivering plant
= Delivery date of stock transport purchase requisition in the ordering plant - Planned delivery time 
2. If the planned delivery time equals to 0:
Requirement date of the stock transfer purchase requisition in the delivering plant
= Release date in ordering plant + Processing time of purchasing

Let's now explain this with an example.
The sample data is:
Planned delivery time = 12 days
Processing time of purchasing = 3 working days
GR processing time = 3 working days
The MRP is run on 2025.5.21 and the original requirement, for example an sales order, falls on 2025.2.20.
Since the requirement falls in the past, so forward scheduling is used. (For backward scheduling, the calculation is even more straight forward and easy to understand.) The calculation procedures are as follows:
The release date is Today (2025.5.21).
PO date = release date + processing time of purchasing = 2025.5.21 + 3 working days = 2025.5.26 (24 and 25 are non-working days so the result is set to the next working day)
Delivery date = purchase order date + planned delivery time = 2025.5.26 + 12 days = 2025.6.9 (6.7 is a non-working day so the result is set to the next working day)
MRP available date in the ordering plant = delivery date + GR processing time = 2025.6.9 + 3 days = 2025.6.12
Requirement date in the delivering plant = delivery date - planned delivery time = 2025.6.9 - 12 days = 2025.5.28

Material Requirements Planning, Requirement Date, stock transfer purchase requisition, PRqRel, Delivery Date, Planned Delivery Time, GR processing time, MD04, release date, Processing time of purchasing, ordering plant, delivering plant , KBA , PP-MRP-2CL , Material Requirements Planning (Public Cloud) , Problem