Direct Debit
account_direct_debit · OCA/bank-payment
Health
63/100
fair
-
Security25/25No findings
-
Activity0/25Last human commit 101 months ago
-
Required by20/254 modules depend on it
-
Maturity18/25In 3 Odoo series since 6.1
Heuristic over the facts below, not an audit · How it's computed
Required by
4
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.06 MB
Module directory on disk
Code analysis
6 migration notes
3 models
4 views
0 HTTP endpoints
Migration considerations
- Migrating to 19.0: only `__manifest__.py` is recognized: a module with `__openerp__.py` is not detected at all. migration-openerp-manifest · source
PaymentOrderCreate— Migrating to 13.0: `@api.multi`/`@api.one` were removed (multi is the default): drop them, looping over `self` where `@api.one` was used. (1 methods) migration-api-multi-one · sourceview_payment_order_form— Migrating to 17.0: `attrs=`/`states=` are rejected in views: convert them to Python expressions in `invisible`/`readonly`/`required`, keeping the original AND/OR logic. migration-view-attrs-states · source- Migrating to 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp`) migration-openerp-import · source
- Migrating to 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp`) migration-openerp-import · source
- Migrating to 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp`) migration-openerp-import · source
Migration review checklist, not a compatibility verdict. "Migrating to X.0" applies once you upgrade to that version; "Since X.0" means this version already ignores or rejects that code. Methodology
Description
Dependencies
- Odoo dependencies
- Python dependencies
- None
- System dependencies
- None
- Required by
- account_banking_fr_lcr, account_banking_sepa_direct_debit, l10n_ch_lsv_dd, l10n_es_payment_order
Code analysis
Extracted from the source by best-effort static analysis (no code is executed); details may be incomplete.
Views touched 4
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
view_payment_mode_form_inherit |
payment.mode.form.inherit | payment.mode | form | Inherits account_banking_payment_export.view_payment_mode_form_inherit |
view_payment_mode_type_form_inherit |
view.payment.mode.type.form | payment.mode.type | form | Inherits account_banking_payment_export.view_payment_mode_type_form |
view_payment_mode_type_tree |
view.payment.mode.type.tree | payment.mode.type | tree | Inherits account_banking_payment_export.view_payment_mode_type_tree |
view_payment_order_form |
direct.debit.payment.order.form | payment.order | form | Inherits account_banking_payment_export.view_payment_order_form |
HTTP endpoints 0
No HTTP endpoints found for this module.
Models touched 3
New fields (0)
No new fields.
Public methods (1)-
line2bank(self, cr, uid, ids, payment_type=None, context=None)I have to inherit this function for direct debits to fix the following issue : if the customer invoice has a value for 'partner_bank_id', then it will take this partner_bank_id in the payment line... but, on a customer invoice, the partner_bank_id is the bank account of the company, not the bank account of the customer !
New fields (1)
-
bank_idMany2onestring='Partner Bank Account'
No public methods.
New fields (0)
No new fields.
Public methods (1)-
extend_payment_order_domain(self, payment_order, domain)@api.multi
Loading…
Loading…