The release date field in a purchase requisition (PR) is used to calculate the date by which the PR needs to be released in order for the material to be available by the required date, taking into account goods receipt processing time, planned delivery time, and purchasing department processing time. It is not the actual date the PR was released. The questioner was confused about this and calculated the release date incorrectly by subtracting the goods receipt processing time from the required date instead of the delivery date.

1. The field 'release date' is a bit confusing. It has nothing to do with
the date you perform the release strategy (transaction ME54 or ME55).
The help on the field tells you more about it.
The release date does not mean PR release approval date.
In PR table/EBAN-FRGKZ or ME53 screen you can find the 'release date',
then press F1 -> purchase requisition release date which means for the
material to be available on the date it is needed the PR must be release
on xx.xx.xx (date) (that's requirement date less GR proessing time, GR
proessing time, planned delivery time, and purchasing department
processing time).
In ME53 screen -> item detail -> MRP data block (include release date.)
click 'statistics' icon -> administrative data (include release ind. and
rel. strategy).
In ME5A -> press F1 on 'release date' of initial screen which have same
explain for this field.
There is no actual PR release date field in EBAN, so in PR display,
we can not see "actual PR release date".
This field gets updated only at the time of creation of PR and informs that the PR should be
released by that date .
It is calculated based on purchasing processing time.Press F1 for more details.
As told earlier the actual release date will be visible only in change log.

2. The date u are seeing as a release date is in different context.That release date is a date for
processing PR to PO.It is useful in MRP.
As told earlier the actual release date will be visible only in change log.
The release date youare talkingaboutmeansthe date on whichthe release strategyhasbeeninitiated
inthe documentandnotthe dayon whichyouhave released.Sothe logicisverymuchperfectand
nothingwrong.
Hello SAP experts,
I need a small help in the calculation and understanding of the release date value in a PR.
The material needs to be delivered on 8th Feb, 2015 and the working days for the plant is from
Monday to Friday.
GR processing time = 2 days
Planned delivery time = 112 days
Pur processing time = 1 day
Now based on the standard SAP example (PR>Quantities/Dates tab>Release data (Press F1), I am getting the below
formula:
Processing time Planneddel. GR processing
Purchasing time time
|----------|---------------------|--------|
Release PO Delivery Date
date date date required

3. Date required: 01.10.2007
GR processing time: 2 days (working days)
Planned delivery time: 10 days (calendar days)
Purchasingdept processingtime: 2 days (workingdays)
For the material to beavailable onthe date it is needed, thepurchase
requisition must be released on13.09.2007 (requirement date less GR processing
time, planneddelivery time, and purchasingdepartmentprocessingtime).
If I calculate based on this formula, then the date I am getting is 15th Oct, 2014:
08th Feb 2015 - 2 (GR processing time, working days) = 05th Feb, 2015 (no
holidays set for the plant in Feb, 15)
05th Feb 2015 - 112(Planned delivery time, calendar days) = 16th Oct, 2014
16th Oct, 2014 - 1(purchasing processing time, working days) = 15th Oct,
2014 (no holidays set for the plant in Oct, 14)
But the actual release date shown in the PR is 17th Oct, 2014. Can you let me know how these
extra 2 days are getting added?
Best Regards,
I guess you are confusing delivery date and requirements date.
The GR processing time is the time between delivery date and requirements date, the date when
the material will be available to be consumed.
If your delivery date is entered in the PR with February 8, then the GR processing time is
actually February 9 and February 10, hence not included in the time back to the release date.