El 29/09/14 a les 17:11, Cédric Krier ha escrit:
On 29 Sep 16:52, Sergi Almacellas Abellana wrote:
El 29/09/14 a les 15:09, Cédric Krier ha escrit:
On 29 Sep 14:45, Sergi Almacellas Abellana wrote:
El 29/09/14 a les 13:49, Cédric Krier ha escrit:
On 29 Sep 13:05, Sergi Almacellas Abellana wrote:
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?
Please defines precisily what you mean?
Planning a move is just setting the planned date.
But it can not be set from the shipment because of the code you pointed.
What I mean:
1. Create a purchase of a product (without supplier info) and process it.
2. The move created by the purchase has no planned date.
3. Create a supplier shipment, set a planned date and add the move.
4. Save the shipment and the planned date for the move is still blank.
So that's the restriction i was talking about.
Can you try this scenario?
What happens when we know that supplier will send us the goods before the
planned date?
This sentence means nothing. The planned date of something is the date
you think/known/expect it to happen.
So if a planned date change because you have more information, you just
change it.
So if the date is before the current planned date and I have created a
shipment for the move, the planned date doesn't gets updated from the
shipment. You have to manually go to the moves and modify it.
But what the point of creating this shipment? It is useless if you don't
have the shipment in front of you.
So it's useless to have the planned date on supplier shipments.
It's confusing that sometimes it gets modified and sometimes not.
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.
Which restrictions?
Not being able to change planned_date from supplier shipments in certain
conditions.
It is possible to change the planned_date of a shipment.
But the planned date of the moves is not updated (in the conditions i
explained before), so it's useless to change it.
Also customer returns must behave in a non optimistic way, as
they aren't under the control of company.
This has no sense. You never plan customer returns.
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.
Because it is bad to make required something that doesn't need.
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.
Compute what? It doesn't make sense to compute a new information.
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.
Wrong!!! You don't plan a move by putting it in a shipment. You plan a
move by putting a planned date that's all.
So then, why we have a planned date on shipments? We can not plan a supplier
shipments?
I think all your troubles are because you don't use correctly the tools.
This is more and more truth.
So will be great if you can explain which is the correct usage of the
tools, as it's not clear on my side.
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
