openerp-expert-accounting team mailing list archive

[Raphaël Valyi - http://www.akretion.com <rvalyi@xxxxxxxxx>]

+1 also for this behavior, I think it's what is expected.

Also notice that, at least in v6 that has cleanest dependencies, the sale
module depends on stock which depends on account.
But of course account doesn't depend on sale.
That mean that sale pricelist code should somewhat move to the account
module instead and both account and sale should use the same factored
pricelist functions.

As a general consideration, I think that OpenERP lacks of such abstractions
that would allow business objects to share methods implementations or
ainterfaces even if they don't inherit one form an other. Yes there are
workarounds to reuse the code, but something cleaner here would have been
welcome (such as Java interface + the required design pattern plumbing, or
say Ruby mixins and I'm pretty sure there would be Python abstractions too,
specially since Python supports multiple inheritance).

Raphaël Valyi
*http://www.akretion.com* <http://www.akretion.com>
[image: logo_only_17 (another copy).png]


On Thu, Jun 17, 2010 at 9:49 PM, Nhomar Hernández -
http://openerp.netquatro.com <nhomar@xxxxxxxxx> wrote:

> +1
>
> It should be a module as Albert offer make it, and It must be part of
> the core for version 6.0
>
> IOH, I think the module purchase_discount _must_ be part of the core
> too, the manipulation of prices on invoice must be so flexible in
> Invoices directly from sales.
>
> We are improving the module purchase_discount with some functions extra,
> I will report the bugs generated in the correct place. but is closly
> related with this one.
>
> --
> Pricelists should be used in invoices even without sale orders
> https://bugs.launchpad.net/bugs/387374
> You received this bug notification because you are subscribed to
> OpenObject Addons.
>
> Status in OpenObject Addons Modules: Confirmed
> Status in OpenObject Addons trunk series: Confirmed
>
> Bug description:
> OpenERP 5.0 (all releases)
>
> When manually defining a stock move "to be invoiced" we can specify the
> partner but not the price list so that
> the invoice takes in account the product price and not the  price defined
> in a price list
>
> There is no problem when the stock move is generated from a sale.
>
> Maurice
>
> There is also a generic need for beeing able to record invoices using
> pricelists when no sale order is involved (please see duplicate bugs).
> Identified workflows include:
> - standalone invoice
> - invoice from packings
> - invoice from membership
> Lionel
>
>
>
>
>


** Attachment added: "unnamed"
   http://launchpadlibrarian.net/50517957/unnamed

-- 
Pricelists should be used in invoices even without sale orders
https://bugs.launchpad.net/bugs/387374
You received this bug notification because you are a member of OpenERP
Accounting Experts, which is a direct subscriber.

Status in OpenObject Addons Modules: Confirmed
Status in OpenObject Addons trunk series: Confirmed

Bug description:
OpenERP 5.0 (all releases)

When manually defining a stock move "to be invoiced" we can specify the partner but not the price list so that
the invoice takes in account the product price and not the  price defined in a price list

There is no problem when the stock move is generated from a sale.

Maurice

There is also a generic need for beeing able to record invoices using pricelists when no sale order is involved (please see duplicate bugs).
Identified workflows include:
- standalone invoice
- invoice from packings
- invoice from membership
Lionel