New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[8.0] stock_valuation_account_manual_adjustment #228
[8.0] stock_valuation_account_manual_adjustment #228
Conversation
cc @eficent |
…ove and account move line - to avoid forcing the computation
</group> | ||
<newline/> | ||
<group colspan="2"> | ||
<button name="process" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's better to put the buttons on
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andhit-r Regarding your long comment, if a company runs perpetual inventory the inventory account should be detailed at a product level. I recently performed an initial balance for a company, and I asked the quantity on stock and the valuation of each product, in order to create the opening entry, detailed at product level.
In order to load what I did was:
1-. Enter the correct standard cost in the product
2.- Set the product valuation to real_time
3.- Change the virtual inventory location to use as debit and credit account "Opening Balance Equity"
4.- Perform an inventory adjustment, to add the on hand quantities as they reported
As a result journal entries were created for each product as:
Dr. Finished Goods
Cr. Opening Balance Equity
That's the correct way to do IMHO. No need to use the manual adjustments tool at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True, but not all implementation project start that way. What is a company use accounting only module first?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a company starts using accounting only, when they switch to stock accounting they should open a new GL account to manage inventory valuation, of course! Then they will need to credit the balance from the old and debit into the new. Same procedure as above, but replace "opening balance equity" with "old inventory account". :)
Thanks for the feedback!
===== | ||
|
||
* Go to the list of products or product variants. You can see in the tree | ||
view the inventory value and the accounting value. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inventory Value, Accounting Value, and Discrepancy can only be seen on Real Time Inventory Valuation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Done!
|
||
@api.multi | ||
def post(self): | ||
timenow = time.strftime('%Y-%m-%d') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not use fields.Datetime.now()? You use it on https://github.com/OCA/stock-logistics-warehouse/pull/228/files#diff-ecb3b276206e9b56ac80d5cccbfe6518R167.
@jbeficent i'm still sure that you only need to assign product_in on one move line. Strange things always happen on implementation hahaha. But for now it's fine. I will create PR if my use case happen in the future. Waiting to pass all test before tumbs. Thank you for this PR. Can't wait to use it on production. |
@eficent can you please review? |
cr.execute( | ||
""" | ||
ALTER TABLE account_move_line | ||
ADD COLUMN stock_valuation_account_manual_adjustment_id |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pedrobaeza Can you help me with this? I am adding field 'stock_valuation_account_manual_adjustment_id' in account.move.line as a related with move_id, and in order to speed-up the install I am pre-creating the field. However at the time of install the field is being still computed. Why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that computed with store=True are always computed when the module is installed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In fact the pre-init code is running correctly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
@andhit-r Runbot is green. However there's still one issue related to the pre-init hook. I'm not sure if it's being effective. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
I think also that it would be a good idea to have the filter 'Valuation Discrepancy != 0.0' in the "Real-Time Inventory valuation" tree view.
👍 . It's better if all status checks pass though. |
Thanks @andhit-r. Now merged |
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
stock_split_picking : open action instead of create wizard
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
[ADD] stock_valuation_account_manual_adjustment
Stock Inventory Account Manual Adjustment
This module shows in the product inventory stock value and the accounting
value, and allows to create accounting adjustment entries to align the
accounting value to match with the inventory stock value.
Configuration
Assign the group 'Stock Valuation Account Manual Adjustments' to the users
that should be allowed to list the valuation discrepancies and to reconcile
them.
Usage
Go to 'Warehouse / Inventory Control / Real Time Inventory Valuation'
Filter on 'Valuation Discrepancy != 0.0' using the advanced filter.
Select the products that you wish to reconcile and press 'More /
Adjust Stock Valuation Account Discrepancies'.
Known issues / Roadmap
In order to properly manage the inventory valuation from an accounting
perspective all journal items created for inventory accounts should
include the product.
The price change function of Odoo creates journal entries to the inventory
account without specifying the product. This is bad because you loose the
ability to control the inventory valuation from accounting at the level of
the product. In order to fix this, use the module
'stock_inventory_revaluation', to be found in the same OCA repository.