Skip to content
Health
55/100
fair
  • Security25/25
    No findings
  • Activity0/25
    Last human commit 101 months ago
  • Required by5/25
    0 modules depend on it
  • Maturity25/25
    In 5 Odoo series since 6.1

Heuristic over the facts below, not an audit · How it's computed

Security findings
Grave / minor (static analysis)
Required by
0
Modules depending on it
External deps
0 pip · 0 bin
Python packages / system binaries
License
AGPL-3
No conflicts with its dependencies
Folder size
0.07 MB
Module directory on disk
Code analysis 15 migration notes 6 models 9 views 0 HTTP endpoints

Description

Enhance the management of Production Lots (Serial Numbers) in OpenERP.

Here are the additional features proposed by this module:

  1. Add a new selection field 'Lot split type' on the product form under the 'Inventory' tab to specify how the Production Lots should be split on the Pickings (you should also enable 'Track Incoming/Outgoing Lots', and the new 'Track internal lots' field).

  2. If the option 'Active auto split' is active for the Company, OpenERP will automagically split up picking list movements into one movement per product instance or logistical unit packing quantity (in that case, only the first logistical unit is taken into account at the present time. Improvement to take them all to be done!).

  3. Turn Incoming Pickings into an editable grid where you can directly type the codes of a new production lot and/or tracking number to create and associate to the move (it also checks it doesn't exist yet).

  4. If the option 'Group invoice lines' is active for the Company, OpenERP will group the invoice lines to make it look like the Sale/Purchase Order when generating an Invoice from a Picking.

Dependencies

Odoo dependencies
Python dependencies
None
System dependencies
None
Required by
None

Code analysis

Extracted from the source by best-effort static analysis (no code is executed); details may be incomplete.

Views touched 9

XML IDNameModelTypeStatus
autosplit_company res.company.autosplit.config res.company form Inherits base.view_company_form
view_move_form_manual_split view.stock.move.form.manual_split stock.move form Inherits stock.view_move_form
view_normal_unique_production_number_form product.normal.stock.form.unique_production_number.inherit product.product form Inherits stock.view_normal_procurement_locations_form
view_picking_form stock.picking.form.prodlot.selection stock.picking form Inherits stock.view_picking_form
view_picking_in_form stock.picking.in.form.prodlot.selection stock.picking.in form Inherits stock.view_picking_in_form
view_picking_out_form stock.picking.out.form stock.picking.out form Inherits stock.view_picking_out_form
view_production_lot_form_unique_production_number view_production_lot_form_unique_production_number stock.production.lot form Inherits stock.view_production_lot_form
view_stock_move_tree_editable view_stock_move_tree_editable stock.move tree Inherits stock.view_move_picking_tree
view_stock_picking_prodlot_selection stock.picking.prodlot.selection stock.picking.prodlot.selection form New

HTTP endpoints 0

No HTTP endpoints found for this module.

Models touched 6

New fields (0)

No new fields.

Public methods (0)

No public methods.

New fields (0)

No new fields.

Public methods (0)

No public methods.

New fields (0)

No new fields.

Public methods (3)
  • action_done(self, cr, uid, ids, context=None)
    If we autosplit moves without reconnecting them 1 by 1, at least when some move which has descendants is split. The following situation would happen (alphabetical order is order of creation, initially b and a pre-exists, then a is split, so a might get assigned and then split too): Incoming moves b, c, d Outgoing moves a, e, f Then we have those links: b->a, c->a, d->a and: b->, b->e, b->f The following code will detect this situation and reconnect properly the moves into only: b->a, c->e and d->f.
  • copy(self, cr, uid, id, default=None, context=None)
  • split_move(self, cr, uid, ids, context=None)

New fields (0)

No new fields.

Public methods (2)
  • action_assign_wkf(self, cr, uid, ids, context=None)
  • action_invoice_create(self, cursor, user, ids, journal_id=False, group=False, type='out_invoice', context=None)

New fields (0)

No new fields.

Public methods (1)
  • select_or_create_prodlots(self, cr, uid, ids, context=None)

New fields (0)

No new fields.

Public methods (0)

No public methods.

Loading…

Loading…

Loading…

Loading…