We have POCO enforced.
We have Released PO lines, that need their Receipt Date to be changed.
When we change Planned Receipt Date from the PO line, we get the error asking to change using POCO.
However, if we change the Promised Delivery Date or Planned Delivery Date on the PO line, it updates all the relevant date fields including the Planned Receipt Date, without the POCO error.
What is happening here?
We would expect to change the Planned Receipt Date without a POCO.
25.1.2
Hi,
(I am not sure how you manually changed the promised date on the line. For me, changes can only be done through “Confirm Difference via change order” when modifying the Promised Delivery Date if POCO is enforced. In my case in 25R1, I can only change the 'planned delivery date' without the system requiring me to go through POCO.)
I believe the reason for the different behaviours is that the purchase order change order functionality was built on top of IFS revision management. If you have a released purchase order that is printed or confirmed, a new revision will only be generated when the 'Wanted Delivery Date' is changed. A new revision will not be triggered if a date change does not affect this field.
I believe you would agree with me that it is logical for only the 'Wanted Delivery Date' to require reinitiating communication with the supplier, compared to other dates.
Applying the same reasoning to enforcing a POCO (which is essentially a more streamlined form of revision handling), IFS does not restrict changes to dates that do not require a new revision. Therefore, you can change the planned delivery date, but you cannot change the planned receipt date or planned arrival date, as these will also impact the Wanted Delivery Date.
Hope this helps
Asanka
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
