summaryrefslogtreecommitdiff
path: root/addons/stock_picking_batch/data
AgeCommit message (Collapse)Author
2020-09-30[IMP] stock_picking_batch: demo data fluxsvs-odoo
Decreases the move lines qty to process for the picking batch #1 in order to make the demo flux quicker. closes odoo/odoo#58895 Signed-off-by: Arnold Moyaux <amoyaux@users.noreply.github.com>
2020-08-27[IMP] stock_picking_batch: internal -> deliverysvs-odoo
Change the demo data to create pickings/picking batchs about deliveries instead of internal transfers. Made this change because multi-location is disabled by default so it doesn't make sense to work with internal transfer with this config. Also, renames these data records reference to avoid migration issue as the pickings/picking batches picking type was changed. Adds a second picking in the batch picking BATCH/00001 because it doesn't make sense to have a batch picking for only one picking.
2020-08-18[IMP] stock,mrp,purchase: refactor priorityRémy Voet (ryv)
- MO/picking/PO/stock.move have now the "same" `priority` fields (Boolean logic: Normal or Urgent). These models are now sort by priority first. Note that the priority field of stock move is a technical one. - For MO and picking, the set of `priority` field change priority of the related stock move. The prioriry field on stock move is used by the scheduler for reservation ('Urgent' before 'Normal') - The Stock Replenishment Report also take in account the priority to be consistent with the reservation. task-2246665
2020-07-31[FIX] stock_picking_batch: wrong sanity check on picking creation.Victor Feyens
1) Wrong use of self.batch_id in an api.model method. 2) Fix demo datas which didn't pass the sanity check (after the fix) Avoid to put draft picking into non-draft batch picking and use batch's actions instead of picking's actions for confirmation and reservation. closes odoo/odoo#55254 X-original-commit: 9e9f50169ba4d4698ce64b0865db4cc6b4833b0e Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> Co-authored-by: Steve Van Essche <svs@odoo.com>
2020-05-27[IMP] various : Update the demo data of SO/PO/invoice with activitiesHardik Prajapati
Purpose of the task is, we have added the activities on various listviews, the goal of this task is to update SO/PO/invoice demo data with activities and also set tags on sales orders. So in this commit, We added the activity on several SO/PO/Invoices and also added the some tags one sales order and set the user as False where the user is set as 'Odoobot'. closes odoo/odoo#51799 Taskid: 2254708 Closes: #51799 Related: odoo/enterprise#10743 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
2020-01-31[IMP] stock_picking_batch: display moves and move linesSimon Lejeune
* allow to directly edit the move lines of the batched transfers * add a check availability button if any move is not assigned yet task-2069646
2019-09-03[REF] stock_picking_batch: multi companySimon Lejeune
Ensure proper domains are applied and enforced on relation fields thanks to the `check_company` attributes. task-1985992
2019-08-14[IMP] stock_picking_batch: Views cleanupArnaud Baes
2019-07-31[IMP] stock_picking_batch: usability changes in the batch picking reportPrakash Prajapati
Improve batch picking demo data. The first page shows the summary of all the pickings. next page onwards we can see the picking information in the report. task-1889404 Closes #29209
2019-03-28[FIX] *: put all mail.message.subtype as noupdateNans Lefebvre
The mail.message.subtype model contains a field internal, which decides if the messages are visible to external users or not. Such a value should not be overriden at module update, so all subtypes should be in noupdate. opw 1946043 closes odoo/odoo#32214 Signed-off-by: Nans Lefebvre (len) <len@odoo.com>
2018-08-22[Add] stock_picking_batch: Create batch picking report by location.Ankit Joshi
We have added a report for batchpicking that show picking operations sorted by locations. TASK-ID: 35645
2018-08-01[IMP] stock_picking_batch: add picking type to pickings demoRomainLibert
2018-07-05[IMP] product: Unify/Clean product demo dataFabien Pinckaers
PURPOSE ======= 1. Unified product demo data 2. Less demo: one per use case 3. Demo data for all models Specification ============= 1. Refactor all the brol in the demo data 2. Adapt the tests to make them green, as some products are renamed, removed, created in python instead of as demo data ...
2018-02-26[IMP] product: move uom in a new addonXavierDo
Moves UoM models, test and data to a new addon in order to be able to use uom without product. A simple example is be to be able to use UoM for timesheets. This commit only move code, and adapt xml ids without chaging any feature or functionnal behavior. Note: 'product' module now depends on new 'uom' module.
2017-09-26[REF] stock_picking_batch: improve demo dataamoyaux
With the old demo data there were 3 picking without initial demand. This commit modifies the picking to reflect 3 differents cases. -One picking without quantity done -A picking that need a back order -A picking without qty done and initial demand that should raise an error
2017-09-13[REF] stock_picking_batch: wording on namePrakash Prajapati
2017-08-25[IMP] stock_picking_batch: few improvements,Kirti Choudhary
- model renamed: stock.picking.wave -> stock.picking.batch - Class renamed: StockPickingWave -> StockPickingBatch - .xml files: changed XML IDs according to module guidelines, reindented code and removed commented code
2017-08-25[IMP] stock_picking_wave: rename to stock_picking_batchKirti Choudhary
Also rename it's files and replace old references with new one