El 29/09/14 a les 13:49, Cédric Krier ha escrit:
On 29 Sep 13:05, Sergi Almacellas Abellana wrote:
>Hi,
>
>I have some doubts about the usage of planned date in supplier shipments.
>
>With some testing (and reading the code) I got the following conclusions
>about planned date (which is expect somebody to correct me if anything is
>wrong):
>
>- The planned date field is used mainly to compute*forecast* quantity of
>products.
>- When the move is done, the planned date it's only used for statistical
>reasons, as effective date is always used to compute the quantities.
Wrong there is nothing for statistical.
So why it's needed? Forecast quantity can be computed with the state of
the move, can't it? It's used for something else or we can remove it (or
move it to a separate module for those who want to use it for
statistics) ?
>- If a move is related to a shipment, the planned date of the move is
>managed on the shipment, so if you want to change the planned date of a move
>you must modify the date of the shipment, and it updates the planned date of
>the draft moves.
>
>The second point, works on customer shipments, customer return shipments and
>for supplier return shipments but not in all cases in the supplier
>shipments. I have found the following cases:
>
>1. If create a supplier shipment with planned date all the unplanned moves
>(planned date field is blank), doesn't get planned (planned date is still
>blank on moves, but not on shipment). Why a unplanned move can not be re
>planned?
>2. If you update the planned date of a supplier shipment the planned date is
>not updated for those moves that the current planned date is*after* the
>planned date of the shipment. The move's planned date is the same as before
>planning the shipment. So how can I reflect that the supplier told me that
>the move will be received before the original expected date?
>3. If you create a unplanned shipment (planned date of shipment is blank),
>all the currently planned dates get blank so you got to point 1 and you can
>not replan all the moves. Also all the statistical data is lost, as planned
>date is updated to blank.
>
>So currently, the planned date on the supplier shipment can only be modified
>to a worse date (a date in the future or an unknown date). Why are the
>supplier shipments working in a different way and with all this
>restrictions?
All is explained in the code:
http://hg.tryton.org/modules/stock/file/0e50182a4fa8/shipment.py#l344
Planning a unplanned move is being optimistic?
What happens when we know that supplier will send us the goods before
the planned date?
Don't you think that both points can improve the forecast?
And it is prefectly normal that supplier shipments behave differently
than other shipments because they are not under the control of the
company but of external entities.
I can understand that they behave different, but not why there are so
restrictions. Also customer returns must behave in a non optimistic way,
as they aren't under the control of company.
>Extra point:
>
>On the supplier shipments you usually select existing moves (which may have
>planned dates) so why not computing the shipment planned date (if the user
>doesn't enter one) based on the worst date of the shipment and then
>replaning all the moves which have planned date?
Because we want the user to enter a date.
So why not having it required? Otherwise most of the users won't enter it.
Maybe someone can give a user prespective point, but if the system has
all the information, it's doable that it can compute it if left blank.
But I think having it by
default to today will be a good improvement.
Agree, but i think there is room for more improvement, for example also
planning unplanned moves because if the user adds them to a planned
shipment it's because he wants to plan the moves.
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
