Skip to content
Health
80/100
good
  • Security25/25
    No findings
  • Activity25/25
    Last human commit 1 month ago
  • Required by5/25
    0 modules depend on it
  • Maturity25/25
    In 6 Odoo series since 14.0

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.15 MB
Module directory on disk
Code analysis 0 migration notes 3 models 2 views 0 HTTP endpoints

Description

In Odoo version 13.0 and previous versions, the number of journal entries was generated from a sequence configured on the journal.

In Odoo version 14.0, the number of journal entries can be manually set by the user. Then, the number attributed for the next journal entries in the same journal is computed by a complex piece of code that guesses the format of the journal entry number from the number of the journal entry which was manually entered by the user. It has several drawbacks:

  • the available options for the sequence are limited,
  • it is not possible to configure the sequence in advance before the deployment in production,
  • as it is error-prone, they added a Resequence wizard to re-generate the journal entry numbers, which can be considered as illegal in many countries,
  • the piece of code that handles this is not easy to understand and quite difficult to debug.

Using this module, you can configure what kind of documents the gap sequence may be relaxed And even if you must use no-gap in your company or country it will reduce the concurrency issues since the module is using an extra table (ir_sequence) instead of locking the last record

For those like me who think that the implementation before Odoo v14.0 was much better, for the accountants who think it should not be possible to manually enter the sequence of a customer invoice, for the auditor who considers that resequencing journal entries is prohibited by law, this module may be a solution to get out of the nightmare.

The field names used in this module to configure the sequence on the journal are exactly the same as in Odoo version 13.0 and previous versions. That way, if you migrate to Odoo version 14.0 and you install this module immediately after the migration, you should keep the previous behavior and the same sequences will continue to be used.

The module removes access to the Resequence wizard on journal entries.

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 2

XML IDNameModelTypeStatus
view_account_journal_form account.journal form Inherits account.view_account_journal_form
view_move_form account.move form Inherits account.view_move_form

HTTP endpoints 0

No HTTP endpoints found for this module.

Models touched 3

New fields (4)
  • has_sequence_holes Boolean
    compute=False
  • refund_sequence Boolean
    default=True
  • refund_sequence_id Many2one → ir.sequence
    check_company=True copy=False domain="[('company_id', '=', company_id)]" help='This sequence will be used to generate the journal entry number for refunds.' string='Credit Note Entry Sequence' args: 'ir.sequence'
  • sequence_id Many2one → ir.sequence
    check_company=True copy=False domain="[('company_id', '=', company_id)]" help='This sequence will be used to generate the journal entry number.' string='Entry Sequence' args: 'ir.sequence'
Public methods (1)
  • create(self, vals_list)
    @api.model_create_multi

New fields (3)
  • highest_name Char
    compute=False
  • made_sequence_gap Boolean
    copy=False
  • name Char
    compute='_compute_name_by_sequence'
Public methods (0)

No public methods.

New fields (0)

No new fields.

Public methods (0)

No public methods.

Loading…

Loading…

Loading…

Loading…

Loading…

Loading…