Define Valid Stock Move Periods
Stock moves should be entered "real time" or at least "in time sequence" to guarantee correct average price etc.
see my comment
http://
To avoid complicated (and mostly not necessary) roll back and recalculation it should be possible to post stock moves only in ONE open period.
stock moves get associated with this "open" periode independently of the actual date_done entered.
the date done should either be the last date of the period or just be ignored for calculation of the period.
Alternate solution - force periode - like for invoices.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(ferdinand) I have created a patch meanwhile
(vrs) I do not agree for one period condition.
As you wrote in the case in forum - real-life situation is often that you can not enter documents hronological. Especially in multi-user split-function companies (where ERP normally is used). This must be possible to register some moves instantly (first day of month, first minute of work), and some with delay (say inventory inspection result).
