Comment 10 for bug 670451

On 31/03/11 18:11, Michael Schwessinger wrote:
> OK. In this case we do NOT need any OPW and will cancel our latest
> one.... Also we will stop any introduction of OpenERP in our
> companies because it is not usable. Why OPW, if all promised features
> are not working and bug reports are declared as "wishlist" and "no
> bug"....

Sorry Michael, I'm just trying to be honest and give everyone realistic
expectations about what OpenERP does and what it does not do.

I think it's much better than confirming more and more bugs about
"apparent issues" with production lots/batch numbers, ignoring the
possibly big consequences this has behind the scene.

On 31/03/11 18:49, Steffi Frank (Bremskerl, DE) wrote:
> after reading your comment I hope there is a chance to agree on a
> solution.

We had a very long meeting in R&D yesterday about these issues, and we
are going to see what can be done about it. I realize this looks like a
major shortcoming in OpenERP when you are in automotive industry, but I
hope I showed what was the philosophy in the OpenERP implementation, so
you can actually make the correct assumptions based on that.

> But we've got one big issue: for one of our companies we set 1st of
> April as date for going live. Cause of all the trouble with production
> lots we moved that already to 1st of May.....

I understand and I'm sorry you were not warned before about this. The
number of apparent bugs you encountered with production lots should have
acted as a warning sign that something bigger was behind it :-(

> We definitely can't go live without a solution for our reported bugs
> concerning production lots (automobil industry is bounded for full
> traceability too). So 'whishlist' and 'next version' won't help at
> all... But the idea of a new module 'track internal moves' sounds good
> (as far as I know c2c started working on it already?) - subject to one
> condition: for testing we need it at least in 2 weeks.

We'll let you know what we'll do asap.