Cannot validate a non-balanced entry error on validate supplier invoice OpenERP 7 - odoo

I have faced the warning pop on validate the supplier invoice with OpenERP 7
1 - select supplier invoice and select supplier
2 - Add Product in invoice line
3 - select Other Info Tab and Add Payment Terms
4 - Validate the invoice
When trying to validate an invoice the application issues an error below OpenERP Warning :
"You cannot validate a non-balanced entry.
Make sure you have configured payment terms properly.
The latest payment term line should be of the "Balance" type."
Warning message raise only when there are debit and credit balance will not be matched.
I am also follwing the below article
https://bugs.launchpad.net/openobject-addons/+bug/506521
Our customer using the old base addons for accouting related module in OpenERP V7
Also apply so many other patch on my existing addons for openerp V7
but not finding any solution relavent with this issue
Any one have idea what are the stapes need to stop my warning popup . or Is there any preconfiguration needed to solve my issue

Related

Customer VAT ID / Number property

I found some resources online indicating that ORO has/had VAT ID / Number property on the Customer. Searching through the codebase I couldn't find any traces of VAT ID / Number. Is this still a case in the latest 4.* version? Also, does the Customer has properties such Company Registration Number?
As last one, what would be the best approach of extending the Customer entity and adding this fields?
The vat ID field is available in the german version of OroCommerce application:
https://github.com/oroinc/orocommerce-application-de.
For existing OroCommerce instances you can install this bundle https://github.com/oroinc/german-localization
that provides an integration with wirecard, infinitepay and dpd.
The vat Id field is available there, but it is implemented as a part of infinitepay integration
https://github.com/oroinc/OroInfinitePayBundle. You can install it separately as well.
If you are not using infinitepay, to add a vat id field, you can copy the code from there to your customization,
https://github.com/oroinc/OroInfinitePayBundle/blob/master/Form/Type/VatIdType.php
https://github.com/oroinc/OroInfinitePayBundle/blob/master/Form/Extension/CustomerVatIdExtension.php
https://github.com/oroinc/OroInfinitePayBundle/blob/master/Validator/Constraints/CustomerRequireVatId.php
https://github.com/oroinc/OroInfinitePayBundle/blob/master/Validator/Constraints/CustomerRequireVatIdValidator.php

Recalculate taxes on programatically created invoice in Odoo 12

In odoo I have created an invoice with correct invoice line items ( including tax ). I am using a node module for this which calls the /web/dataset/call_kw endpoint in odoo.
My problem is, that the tax on the invoice is not updated after adding the line items. It remains 0. Can I force the recalculation of the invoice or must I calculate the total tax and set it on the invoice programatically?
I have tried to call the method button_reset_taxes() on the account.invoice object via the web api, but failed.
Error:
account.invoice has no attribute button_reset_taxes.

Odoo 10: How to create project tasks from sale orders?

I have set my odoo system according to the "User Doc" of How to create tasks from sales orders? and want to generate project tasks automating when a sale order containing "Service" type product was created.
However, it wasn't working even after I have tried severals times.
I didn't find the the "Track Service" item when I set up a "Service" product.
screen shot
Is this the reason which odoo system can't generate task automating? Or there some thing else cause the issue?
Anyone can give me some advice?
Thanks.
this answer will help to do your task in odoo version 10.
In order to get the track the **Create Tasks From Sales Orders** you follow the following steps.
Step : 1 Install the required applications / Configuration
Install the 3 following app
1. Sales Management
2. Project management
3. Time-sheet management
Step : 2 Create and set up a product
Note :
Now in case to of the service product unit of the measurement is used in hours. to configure that go to
Go to Configuration -> Settings -> Unit of measures -> check the
Some products may be sold/purchased in different unit of measures
(advanced) radio button)
Now , create the product with following details
To create the product Go to the Sales -> Product -> Create
- Name: Service Contract
- Product Type: Service
- Unit of Measure: Hours
as this all are the general setup shown on Image below
Next configure Track Service:
You will found this under Sales -> Sales -> Product -> Invoice ->
Select Create a task and track hours.
Note :
Link your task to an existing project or create a new one on the fly if the product is specific to one project. Otherwise, you can
leave it blank, odoo will then create a project per SO.
as your product is a service invocable by hours you have to set the units of measures of the product to hours as well.
Step : 3 Create the Sales Order
Once the product is set up, you can create a quotation or a sale order
with the related product. Once the quotation is confirmed and
transformed into a sale order, the task will be created.
Step : 4 Access the task generated from the sale order
On the Project module, your new task will appear :
either on a related project if you have selected one in the product form
either on a new project with the name of related the sale order as title
(you can easily change the name of the project by clicking on More ->
Settings)
as shown in below image.
The doc screenshot of the product form seems just wrong for Odoo 10. The track service option should be found in the page "Accounting" of a product. Maybe the module sale_timesheet has to be installed before.
If the system configuration is not working, then try creating tasks as follows manually in your code by inheriting sale.order model
Iterate over your order_line one2many field of sale.order and check any products are of type service, if the condition is satisfied then invoke the create function of the model project.task and pass the field(of project.task model) values as arguments

Netsuite Customer Payment Template

I need to include the value 'PO/Check Num' from the APPLY Sublist, on the PDF template for Customer Payments. This value doesn't show up in the sublist by default, by opening up a Customer Payment in EDIT Mode, you can customize the sublist and show this column. On my other templates this value is available using the script; ${record.otherrefnum}
I have looked in the Netsuite ScriptID guide, but have not found the right tag to include the highlighted values in screenshots attached.
I have tried variations of ${record.apply.otherrefnum} but no luck so far
I just found the following in SuiteAnswers if anyone still needs this answer. Users must customize their payment page to show the PO/Check # column for this solution to work.
Print the PO# in Customer Payment using Advanced PDF/HTML Template
Published 05/28/2021 07:35 PM | Updated 05/28/2021 07:35 PM | Answer Id: 99734
Applies To
Product: NetSuite 2021.1
Scenario
Print the PO# field in the Customer Payment record.
Solution
Navigate to Customization > Forms > Advanced PDF/HTML Templates
Preferred Advanced PDF/HTML Template: Click Edit
Source Code: Click Toggle Switch
Add the code below:
${apply.Transaction_OTHERREFNUM}
Click Save

Setting BoM type to set/phantom in odoo 8

I would like to invoice BoM products and from what I've seen this is really easy in odoo 7.0 , where you can set BoM type to phantom/set. However, in the newest version (8.0 for windows) there are only two types of BoM : normal and set. Neither suits my needs. Do I need to activate something to get phantom functionality or was it deprecated in version 8.0?
I researched that bundle option is unavailable in odoo 8.0, but you can create invoices for set components after ticking "invoice based on delivery" during a quotation creation.
In order to use the BoM feature just add the manufacturing module ( Settings > Module > Local Modules, hit install - wait and and create group product by entering into the manufacturing module.