| Age | Commit message (Collapse) | Author |
|
|
|
ir.sequence.date_range, refactored ir.sequence and ir.sequence.date_range implementation
|
|
bzr revid: jco@openerp.com-20140120090628-6uqd51mweoelxu9g
|
|
bzr revid: jco@openerp.com-20140117173851-60246vguu1y3hiq2
|
|
bzr revid: fp@openerp.com-20130803175004-ivqkxtsd7vh4npwe
|
|
bzr revid: fp@tinyerp.com-20130630222646-wrpyd1o89md8gknx
|
|
procurement module (where stock.move.group was defined) does not depend on the stock module
the same grouping system could be used for services too
procurement.group
removed sequence_id field
put a default values on the name field, using a defined sequence
renamed "Move Group" into "Procurement Requisition"
procurement object:
location_id should not come from the customer property but should be stored on the procurement (set by the sale order, using the customer property)
bzr revid: fp@tinyerp.com-20130629091328-5gc39647aa2pymlf
|
|
batch mode, with one transaction per order
A programming error during an older refactoring lead to
the scheduler working with a single monolithic transaction.
This could cause unnecessary resource contention, plus
undesired rollback of all previous operations in the event
of an exception during scheduling.
bzr revid: odo@openerp.com-20130701163532-8bekn7sbb99ua08c
|
|
to procurement module.
bzr revid: uco@tinyerp.com-20100528104430-opnf85w0osxhb3te
|
|
procurement : renamed 'mrp.procurment' object to 'procurement.order'.
bzr revid: uco@tinyerp.com-20100527124706-uptnmyrdopc9yht9
|
|
procurement : renamed files
bzr revid: uco@tinyerp.com-20100527054542-0jq7fam3f6ga071f
|