l10n_be_invoice_bba : structured communication checked on all invoiced
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Odoo Addons (MOVED TO GITHUB) |
Fix Committed
|
Low
|
OpenERP Publisher's Warranty Team | |||
| OpenERP Community Backports (Addons) | Status tracked in 7.0 | |||||
| 7.0 |
Fix Committed
|
Low
|
Unassigned | |||
Bug Description
Hi,
I'm facing a bug with the l10n_be_invoice_bba module.
The problem is that the uniq constaint on structered communication is checked on the whole set of invoices without distinction on the type of invoice : Customer or Supplier invoice... In fact, the structured communication uniq constraint of an invoice should only be check on the same type of invoice. For example, the structured communication should only be checked on customer invoices if I'm filling in a Customer invoice and on supplier invoices if i'm filling in a supplier invoice.
In addition of that, for a supplier invoice, the structured communication uniq constraint should only be check on the supplier invoice of the same supplier as two different suppliers could possibly give an invoice with the same structured communication. This probability should not happen anyway this is the good way to check this constraint.
You can go from a empty database and install this module create a customer invoice with struct comm and create a supplier invoice with the same struct comm.
Thanks for your help,
Houssine
Related branches
- Naresh(OpenERP): Pending requested
-
Diff: 37 lines (+14/-6)1 file modifiedl10n_be_invoice_bba/invoice.py (+14/-6)
| Changed in openobject-addons: | |
| assignee: | nobody → OpenERP Publisher's Warranty Team (openerp-opw) |
| tags: | added: maintenance |
| Peter Langenberg (peter-langenberg) wrote Re: [Bug 1206852] Re: l10n_be_invoice_bba : structured communication checked on all invoiced | #1 |
| Houssine (houssine-bakkali) wrote | #2 |
| Changed in ocb-addons: | |
| status: | New → Fix Committed |
| importance: | Undecided → Low |
| Changed in openobject-addons: | |
| assignee: | OpenERP Publisher's Warranty Team (openerp-opw) → nobody |
| assignee: | nobody → OpenERP Publisher's Warranty Team (openerp-opw) |
| status: | New → Fix Committed |
| importance: | Undecided → Low |
| Houssine (houssine-bakkali) wrote | #3 |
Keep also in mind the multicompany aspect !
2013/7/31 Vinay Rana (OpenERP) <email address hidden>
> ** Changed in: openobject-addons
> Assignee: (unassigned) => OpenERP Publisher's Warranty Team
> (openerp-opw)
>
> ** Tags added: maintenance
>
> --
> You received this bug notification because you are subscribed to OpenERP
> Addons.
> https:/
>
> Title:
> l10n_be_invoice_bba : structured communication checked on all
> invoiced
>
> Status in OpenERP Addons (modules):
> New
>
> Bug description:
> Hi,
>
> I'm facing a bug with the l10n_be_invoice_bba module.
>
> The problem is that the uniq constaint on structered communication is
> checked on the whole set of invoices without distinction on the type
> of invoice : Customer or Supplier invoice... In fact, the structured
> communication uniq constraint of an invoice should only be check on
> the same type of invoice. For example, the structured communication
> should only be checked on customer invoices if I'm filling in a
> Customer invoice and on supplier invoices if i'm filling in a supplier
> invoice.
>
> In addition of that, for a supplier invoice, the structured
> communication uniq constraint should only be check on the supplier
> invoice of the same supplier as two different suppliers could possibly
> give an invoice with the same structured communication. This
> probability should not happen anyway this is the good way to check
> this constraint.
>
> You can go from a empty database and install this module create a
> customer invoice with struct comm and create a supplier invoice with
> the same struct comm.
>
> Thanks for your help,
> Houssine
>
> To manage notifications about this bug go to:
> https:/
>