Thx for the reply. I am aware of the average value and we want to avoid it for reasons given above in my reply. As for ATP we have the TRLT maintained and in any case we exclude the TRLT from the scope of check config. I am just surprised that rescheduling works the way it works and if it does I am also looking to some of the gurus to provide if possible a business reason as to why it would ignore the PIR from the PDT. Only thing I can think of is that the rescheduling calculation would be receipt element specific and that may complicate the MRP "behind the scenes" activities. Also if some on could show me an OSS not which specifically states that.
↧