c2c-oerpscenario team mailing list archive

["qdp \(OpenERP\)" <qdp-launchpad@xxxxxxxxxxx>]

the patch released in revision 5386 should have fixed most of the
problems.

Do not hesitate to create new bugs if you still found some.

Thanks,
Quentin

** Changed in: openobject-addons
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP Project Group.
https://bugs.launchpad.net/bugs/802322

Title:
  orderpoint

Status in OpenERP Addons (modules):
  Fix Released

Bug description:
  There are a couple of problems with orderpoints and the scheduler.  
  The first - there seems to be an issue that automatic orderpoints are not processed when run by non admin user, however this may be just my configuration - feel free to test and confirm if this is the case.  I notice a client error around access rights, so I think it may be that the scheduler trys to compute all procurements, but because the user does not have rights to all companies it fails.

  This next one is really the one I need looked at.  When computing
  scheduler / orderpoints as admin user,  all of the automatic
  orderpoints are assigned to company 1, instead of the company who the
  order point belongs to.  So basically we end up with draft PO's going
  to the wrong warehouse and company.

  To test.  Create 2 companies, a parent and a child.  Create warehouses
  and stock locations for each and a user for both.  Define a product
  without an associated company (so it appears in both companies) with a
  supplier with no associated company, create 2 minimum orderpoints such
  that it will be triggered on the child company and parent company, and
  then to test case 1 - Compute Schedulers as child user and in my case
  nothing happens (although logs show an error relating to stock move
  access rights).  Then to test my more important case 2, compute
  schedulers as admin user, and check the resulting Draft PO's.  They
  are all to the parent.

  Now I did some further tests, adding company_id to the procurement
  object creation and this partially fixed the issue.  Line 265 of
  schedulers.py in procurement.  Now the resulting purchase orders are
  created against the correct company, however it still references the
  wrong warehouse, but the right location.  There is no warehouse_id
  column in procurement_order so there may be an issue in the creation
  of PO's from procurement orders that it picks up the wrong warehouse,
  based on the uid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/802322/+subscriptions