Hello Dr. Ferdinand,
This issue is already improved in current trunk code.
You can change and assign past date from stock picking object form and that
date will write in stock move.
Hope this will help you.
Thanks.
** Changed in: openobject-addons
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/371262
Title:
stock moves must allow past dates
Status in OpenObject Addons Modules:
Fix Released
Bug description:
the purchase/packing/picking flow always assigns now() as date and uses this
date to assign the period, which is fine as long as every stock move can be
entered "real time". this is technically correct, but not suitable for many
business.
entering "real time" is not the case if
* the computer/network is down
* the person with grants/roles to validate picking is absent
* monthly inventory might be entered on the first day of the month
* incoming/outgoing goods are handled at remote sites without technical or
organizational possibilities to enter data there
(this is typically in farming business, goods sold are weighted at customer
site and the documents arrive some days after the actual move)
I have already created a patch ( together with price_unit) which allows to
enter document date and derives the period from this date (so far for purchase)
- not fully tested yet.
see also https://bugs.launchpad.net/openobject-addons/+bug/358584
Obviously allowing to enter a previous date might create other problems,
especially the correct calculation of average price may get inaccurate if the
sequence of entering documents is disrupted. This must be prevented by
organizational measures.
So I suggest
* allow only working in one "open" period - this can be appropriate if the old
period can be closed in between a few hours of the first working day and no
stock moves must be generated during this time
* recalculate average price in the order of posting dates (+ id numbers)
** without touching any evaluation of stock moves, but creating account_moves
with the value differences found.
** reevaluate everything - account_moves will need an additional state
"preliminary evaluation" or remain as draft until final evaluation (closing of
the period) - for this it must be possible to "close" the stock journal of a
period.
It could also be helpful to restrict entering a past date to a certain user
group, for certain product group, for certain periods.
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
