credativ team mailing list archive
-
credativ team
-
Mailing list archive
-
Message #00986
Re: [Bug 742534] Re: Bug fixes in OpenERP POS
On Thursday 08 December 2011, you wrote:
> Didn't notice your POS replacement until now, my friend... Shame on me
> !!
Haven't seen your mail until now. Shame on me, too!
> What is needed to use the pg84-next branch?
> Is that a replacement for the 6.0.x series? Does it include the 6.0.3
> modifications? I tried to find out more, but could only find your blog...
pg84-next always aimed to be a drop-in replacement for the official 6.0 openerp-
server. It contained all the fix /proposed/ for the official series, that ought
to be discussed with the community etc. Now, it is stable[1] and is no longer
planned to receive any more features[2]. It does still follow the 6.0
maintenance and receives all patches that make any sense, from 6.0 .
*addons* have needed the same treatment, too. The corresponding branch is
"trunk-xrg" and had all these improvements, community contributions and
patches you would be missing in official 6.0 series. However, since some[3]
improvements /need/ addons to be patched[4], and some addons /need/ the server
to be improved, you _should_ only run 'pg84-next' server against 'trunk-xrg'
Practically, I would advise just to take a backup of your database (as you
should always do), revise the wording changes in openerp-server.conf[5] and
give them a try.
>
> Regards,
> -Mario
[1] as much as any piece of computer software can be.
[2] now, development has shifted to the 'f3' series.
[3] namely, the enhanced domain expressions, ir.sequence, the daemon support
in the framework etc.
[4] in these branches, server advertises its "release options" and addons
define their dependencies on them. So, you can tell what is compatible by only
looking at the __openerp__.py file. This makes addons forward-compatible for
the future, too.
[5] for historical reasons (even before 6.0), the pg84 server has more
options, and calls the HTTP layer "http" not "xmlrpc". I think this will also
be fixed in official 6.1 .
--
Say NO to spam and viruses. Stop using Microsoft Windows!
--
You received this bug notification because you are a member of OpenERP
Framework Experts, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/742534
Title:
Bug fixes in OpenERP POS
Status in OpenERP Addons (modules):
Confirmed
Bug description:
In Openerp 6.0.1 Point of Sale Module the following problems occur:
1.) If a product was configured to have a different UoM (PCE for
default and Box100 for Purchase UoM), the POS makes use of the
Purchase UoM. So a product sold for $7.00 will have a unit cost of
$700 in the order line due to the Box100 (Purchase UoM). Follow the
code below for reference:
point_of_sale.py (Line: 1074)
1066 def price_by_product(self, cr, uid, ids, pricelist, product_id, qty=0, partner_id=False):
1067 if not product_id:
1068 return 0.0
1069 if not pricelist:
1070 raise osv.except_osv(_('No Pricelist !'),
1071 _('You have to select a pricelist in the sale form !\n' \
1072 'Please set one before choosing a product.'))
1073 p_obj = self.pool.get('product.product').browse(cr, uid, [product_id])[0]
1074 uom_id = p_obj.uom_po_id.id
The line (1074) "uom_id = p_obj.uom_po_id.id" should be "uom_id =
p_obj.uom_id.id"
2.) POS transactions paid in cash does not create Sales and Tax
entries. Only Cash and Accounts Receivable entries are created, which
is not appropriate in a cash sale transaction. A minor modification of
the file point_of_sale_view.xml is required to add a "Confirm Order"
button that will trigger the posting of the POS transaction to
accounting entries: Sales and Tax. Refer to these lines:
<group colspan="4" col="8">
<field name="state" />
<button name="%(action_add_product)d" string="Add product" type="action" icon="gtk-ok" states="advance" groups="base.group_extended"/>
<button name="%(action_pos_payment)d" string="Make Payment" icon="terp-dolar" type="action" states="draft,advance" />
<button name="%(action_pos_confirm)d" string="Confirm Order" icon="gtk-execute" type="action" states="paid" />
<button name="%(action_report_pos_receipt)d" string="Reprint" icon="gtk-print" type="action" states="paid,done,invoiced"/>
<button name="set_to_draft" string="Set to draft" states="paid" icon="gtk-execute" type="object" />
<button name="%(action_view_pos_return)d" string="Return Picking" type="action" icon="gtk-ok" states="paid" attrs="{'invisible':[('state','!=','done'),('state','!=','invoiced')]}" context="{'return':'return'}" />
</group>
Notice the added line "<button name="%(action_pos_confirm)d"
string="Confirm Order" icon="gtk-execute" type="action" states="paid"
/>".
I hope this will be of great help to others seeking for the solutions
presented.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/742534/+subscriptions
References