External purchase order release date is not calculated

Question

In our live system, when creating external purchase orders from tasks within work orders, system does not calculate the release date of purchase order as explained in the documentation (planned delivery date - planned delivery time). Strangely, when the calculated release date does not lie within the current year release date is assigned to the creation date. When calculated release date lies within the same year, correct release date is assigned to the PO.
Althogh our development and productive systems have exactly the same patch level, we do not experience this behaviour on our development system. This makes me think that the problem is due to system-dependent setting or some master data such as factory calendar.
How could we correct the problem? Thanks in advance.
Ozgen.
Edited by: Aselsan IT Department on Jun 14, 2010 2:12 PM

Answer 1

We don't have a release strategy for PReq.
On the Preq Item -> quantites/ dates tab there are 3 dates: delivery date, request date and release date. In MRP process, the release date is calculated by the sytem based on planned delivery time and GR processing time. The PReq should be changeable by MRP up to the release date. On the release date the system should transfer PReq to SRM and mark the PReqs
as u2018firmedu2019 u2013 not changeable. This is a SAP standard process. Worked well with EPRTRANS.
BADI ME_REQ_SOURCING_CUST imethod CHECK_EXTERNAL_SOURCE is already implemented. The BADI controls what requirements to send to SRM.
We tried putting a check for Release date like: if release date is = < than system date , send PReq to SRM:
   if is_req_item-FRGDT le sy-datum.
   cv_ext_sourcing = cl_mmpur_constants=>yes.
It does stop new PReqs with release date in future from coming to SRM. However, the BADI is not retriggered for the same PReq when the release date reached.
Can you please guide me through the implementation steps? If it possible to retrigger the PI message via a scheduled process?
Thank you