Community mailing list archives
RE: push delivery date from PO to SOby
I’ve always recommended to separate the promise/agreement (Purchase Order) with the fulfilment of that promise/agreement (Incoming Shipment or Receipt).
I encourage users to negotiate and update the RFQ as needed, but once it is confirmed to not make changes. So, I’d recommend managing changes to the delivery date on the Incoming Shipment or Receipt, rather than the PO.
What you lose if you don’t do this is “Which suppliers actually keep their word, or tell me something accurate?”.
I would create a new date at sale order line level for handling such things, and add the logic for a correct computation of this date, because the rest is very confusing for putting in order.
2015-07-29 18:08 GMT+02:00 Leonardo Pistone <email@example.com>:
Hi,has anyone found a good way to manage a change of delivery date froman existing PO to a linked (MTO) SO in v8? The use case is a suppliercalls in to say that a product will be available in a month, and Iwant this change in the POL to affect the sale.I found the following:- the (POL) has a date_planned field, which is written to thedate_expected of the created move on the validation of the PO- this is not propagated on subsequent updates of a confirmed PO. Anew module could do that- changing the date_expected of a move propagates the date delta tochained moves. This is a new feature in v8. So far so good.Once we get to the SO, things get confusing to me. Thesale_order_dates module adds three new date fields to the SO:commitment_date, requested_date and effective date. The latter couldbe what I want, but:- it is a field on the SO, while probably that should be on the SOL- strangely enough, it checks the creation date of the picking, notthe expected dateHence, this flow doesn't work. Does anyone know how to handle it?Thanks!