| Age | Commit message (Collapse) | Author |
|---|
|
As a user accessing only the purchase module, create a request for
quotation, add a line with a tax and a cost > 0.
Confirm the RfQ to create the purchase order.
Before this commit, the user get a access error on account.account.tag
This patch add read access on this model for purchase users
opw : 2466688
closes odoo/odoo#67072
Signed-off-by: William Henrotin <Whenrow@users.noreply.github.com>
|
|
Before this patch, the purchase users get an access violation error
at the invoice creation from a purchase order. This was due to
some missing ACL between v12 and v13.
Task : 2206969
X-original-commit: 4c4fb33e4bbc78a85ad309baf5df906cf16566ea
|
|
For stock, purchase, repair and mrp modules, do a small clean of ACL:
Remove duplication and useless line.
Also improve the readability of the stock traceability report.
task-2172399
closes odoo/odoo#45055
Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>
|
|
Task 2092079
Accounting firms that want to give access to their customers avoiding
mistakes and risks will love this profile that can't do anything
wrong... Maybe as well as companies auditors..?
closes odoo/odoo#39860
Related: odoo/enterprise#6576
Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>
|
|
(beaa30a3d1843de43a45f419bfbc1bfa7613a920)
This commit merges the following models
* account.invoice and account.move
* account.invoice.line and account.move.line
* account.voucher and account.move
* account.voucher.line and account.move.line
It was the opportunity for a big cleanup of the code, so it also restructures the whole account module, its different models/fields, the tests etc. for a better world and a better code readability.
==== Rationale ====
The rationale of this huge change is that we want journal entries / invoices to be easily edited, and changes reflected in the other model. It's a HUGE feature and very strategic for the fiduciary companies. For example, changing the account of a journal entry needs to be automatically reflected on the related invoice.
The same reasoning applies to sale/purchase vouchers.
==== Changes made in features =====
When creating an invoice, you are now creating a journal entry directly.
--> The object account.invoice no longer exists.
In the same fashion when creating an invoice line, you're now adding journal items directly in the journal entry representing the invoice. If this invoice line has some tax, it may create additional journal items as well.
--> The models account.invoice.line & account.invoice.tax no longer exist
Identically, when creating a sale/purchase receipt with its lines, you are now creating a journal entry directly and there's no more usability difference between encoding a receipt or an invoice.
--> The object account.voucher no longer exists.
--> The object account.voucher.line no longer exists.
--> The whole account_voucher module no longer exists.
Positive side-effects coming from these changes are
* draft invoices/bills/sale or purchase receipts now create a draft accounting entry. Validate these objects now simply post its journal entry. That means that draft invoices/bills/sale or purchase receipt can straightforwardly be included in reporting or budgets.
* opening a journal entry in form view will now always open the correct view: if it's a sale/purchase journal entry we will have a customer invoice/vendor bill view or a sale/purchase receipt view, whatever the menu we're coming from.
* code & business logic simplification. It is also condensed in a single place instead of being partially duplicated on invoices, vouchers and journal entries.
There should be no feature loss, except the one allowing to group multiple journal items together based on the same product during the invoice validation.
==== Changes made in models =====
* account.invoice: model removed. Instead, now use account.move with following mapping
field (account.invoice) field (account.move)
----------------------- --------------------
name invoice_payment_ref
number name
reference ref
comment narration
user_id invoice_user_id
amount_ total_company_signed amount_total_signed
residual amount_residual
state state + invoice_payment_state /!\ selection changed
date_invoice invoice_date
date_due invoice_date_due
sent invoice_sent
origin invoice_origin
payment_term_id invoice_payment_term_id
partner_bank_id invoice_partner_bank_id
incoterm_id invoice_incoterm_id
vendor_bill_id invoice_vendor_bill_id
source_email invoice_source_email
vendor_display_name invoice_vendor_display_name
invoice_icon invoice_vendor_icon
cash_rounding_id invoice_cash_rounding_id
sequence_number_next invoice_sequence_number_next
sequence_number_next_prefix invoice_sequence_number_next_prefix
'invoices' subset of account.move can be accessed by using the selection field 'type' or one of the many helpers like is_invoice()
* account.move: now has a valid state 'cancel' that has to be excluded from all business logic
* account.move: field 'amount' renamed into 'amount_total'
* account.move: field 'reverse_entry_id' renamed into 'reversed_entry_id'
* account.move.line: now has a field 'display_type' that has to be excluded from all business logic, in order to support invoice layouting
* account.invoice.line: model removed. Instead, now use account.move.line with following mapping
field (account.invoice.line) field (account.move.line)
---------------------------- -------------------------
invoice_id move_id
uom_id product_uom_id
invoice_line_tax_ids tax_ids
account_analytic_id analytic_account_id
'invoice lines' subset of all account.move.line from a journal entry can be accessed by using the boolean field 'exclude_from_invoice_tab'
* account.invoice.tax: model removed. Instead, now use account.move.line with following mapping
field (account.invoice.tax) field (account.move.line)
--------------------------- -------------------------
invoice_id move_id
account_analytic_id analytic_account_id
amount price_unit
base tax_base_amount
'tax lines' subset of all account.move.line from a journal entry can be accessed by using the relational field 'tax_line_id'
* account.invoice.confirm: model removed. Instead, now use the 'post()' function of account.move
* account.invoice.refund: model removed. Instead, now use account.move.reversal to reverse the entries with the same options as we had for invoices
* account.voucher: model removed. Instead, now use account.move of type in ['out_receipt', 'in_receipt]
* account.voucher.line: model removed. Instead, now use account.move.line
==== Changes made in functions ====
* on account.move, method _run_post_draft_to_post() renamed into _autopost_draft_entries()
* on account.move, method action_account_invoice_payment() renamed into action_invoice_register_payment()
* on account.move, method action_invoice_reconcile_to_check() renamed into action_open_matching_suspense_moves()
* on account.move, method _get_domain_edition_mode_available() renamed into _get_domain_matching_supsense_moves()
* on account.move, method _get_intrastat_country_id() renamed into _get_invoice_intrastat_country_id()
* on account.move.line, method _get_domain_for_edition_mode() renamed into _get_suspense_moves_domain()
* in account.bank.statement, contextual key 'edition_mode' renamed into 'suspense_moves_mode'
Was task 1917430
|
|
This table tracked standard price changes.
It was used to compute the valuation at date in AVCO and standard
through `get_history_price`.
The next commits will introduce the stock valuation layers, separating
the valuation from the stock move. As a valuation layer will be created
when a standard price is updated on the product or when a stock move
impacts the valuation, the information from this table will be
duplicated.
We don't plan to adapt `get_history_price` to work with the valuation
layer since the valuation report at date and today will be the same: a
grouped list on the valuation layers with eventually a domain on the
date.
task-1875873
|
|
When splitting purchase and stock, the access
rules of the report was wrongly moved to
purchase_stock. This commit restores balance
in the universe.
|
|
We want to break the dependency between stock and purchase
for our furtur developpement. For more modularity, a new
bridge module 'purchase_stock' is created.
This commti move part of business code, views, data, ...
related to stock management from purchase into purchase_stock
without changing any feature.
Task #47927
|
|
This adds the possibilty to select another account.invoice object in a vendor bill or credit note, to automatically copy its lines.
When the purchase app is installed, the same field can be used for auto-completion and users can choose between vendor bills or purchase orders (preferably PO)
Co-authored-by: dat@openerp.com
|
|
Also rename product.uom.categ into uom.category to
give it a decent name.
|
|
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.
|
|
Was part of PR #19820. Courtesy of Vauxoo
|
|
|
|
So much badass.
|
|
Access on purchase order lines for managers is present twice in the
security file. Once with only read access and once with full access.
I suppose the latter one is the correct one.
|
|
|
|
|
|
|
|
allows to have several sequences running for the same one depending on date ranges (similar to what was existing previously on accounting with FY, which is now deprecated) + port to new API
|
|
(closes #500)
(cherry picked from commit 84c0595aef3a417702c81b5226ae1f61817a2bf8)
|
|
product.price.history + passed 'date' as real parameter instead of contextual one in get_history_price() because it makes more sense.
bzr revid: qdp-launchpad@openerp.com-20140428153355-vbuam1hfnah7m4wp
|
|
bzr revid: csn@openerp.com-20140117135034-8m7798nqu1spz370
|
|
mrp, sale_stock
bzr revid: csn@openerp.com-20130709150027-wy8avglaosiktm5m
|
|
bzr revid: stw@openerp.com-20120822133729-8her237u00inknsl
|
|
purchase order
bzr revid: bde@tinyerp.com-20120817071950-3h1c0x2yxun8kd68
|
|
bzr revid: dhr@tinyerp.com-20120621051616-bk606ej84oauqbzn
|
|
the merge of the objects res.partner and res.partner.address
bzr revid: qdp-launchpad@openerp.com-20120330090837-s87z2qzsvynhlbwr
|
|
to solve 'test/process/edi_purchase_order.yml' yml and its references
bzr revid: bde@tinyerp.com-20120305132539-1u8zok2ccy6csemu
|
|
lp bug: https://launchpad.net/bugs/917333 fixed
bzr revid: mma@tinyerp.com-20120118084854-rpq7u420uxdvcepy
|
|
bzr revid: fp@tinyerp.com-20111212181113-mhnnbps3ip8ls6pp
|
|
bzr revid: rmu@tinyerp.com-20110711050722-mdw6i1qsyhn6vw45
|
|
bzr revid: fp@tinyerp.com-20101228151738-mmm1gug4t2hesron
|
|
bzr revid: fp@tinyerp.com-20101228145442-9ktaid5cxqs43yej
|
|
bzr revid: fde@openerp.com-20101228083043-6sfsuh4uvqvhu3ap
|
|
bzr revid: fde@openerp.com-20101220145607-vx2r937j9sj7e1zw
|
|
bzr revid: qdp-launchpad@tinyerp.com-20101217164143-glfqx79n719079i3
|
|
bzr revid: qdp-launchpad@tinyerp.com-20101214160729-lc1q0oy76dygh5s2
|
|
bzr revid: ksa@tinyerp.co.in-20101102055419-dxikwcij3n7xa9ko
|
|
bzr revid: ksa@tinyerp.co.in-20101101124537-7h3acibsx82thvej
|
|
bzr revid: fp@tinyerp.com-20101017213029-79yh7xvz06ii8dgo
|
|
bzr revid: fp@tinyerp.com-20101012093745-kpfyjls7h8ftczjm
|
|
bzr revid: vir@tinyerp.com-20100807063414-u5uhbdfwuijgxcv7
|
|
bzr revid: amp@tinyerp.com-20100723072243-kpex4cdgckhga46d
|
|
bzr revid: fp@tinyerp.com-20100708144347-b9x0lx1ulfbjtli4
|
|
bzr revid: fp@tinyerp.com-20100629120926-9c7qdw0mug279ehh
|
|
bzr revid: rpa@tinyerp.com-20100628134938-23kiccr4355jfhmg
|
|
bzr revid: nel@tinyerp.com-20100616132609-abqesd6tm8axcokx
|
|
bzr revid: fp@tinyerp.com-20100612162154-f9dgju8wsmn79gq0
|
|
bzr revid: fp@tinyerp.com-20100611142631-8njuqup1ugudbb3w
|
|
and osv_memory. to be continued
bzr revid: odo@openerp.com-20100519164111-9n8vrpz4lfmml8an
|
