Skip to Content
Menu
This question has been flagged
2 Replies
1069 Views

Hello! Can someone help me?
In Odoo14, I am trying to 'mark as done' a manufacturing order (MO) that is in 'to close' status with all component quantities fully available and reserved. When I click the 'Mark as done' button, it informs me of the following error:
TypeError: _action_done() got an unexpected keyword argument 'cancel_backorder'


Avatar
Discard
Author

Thank you very much for your reply, Niyas Raphy.
I don't know how to use the odoo runbot. I don't have a preliminary fabrication module. I am going to follow your instructions regarding duplicating the database and removing some third-party applications that I installed later. I will communicate the results later. Have a good day.

Author Best Answer

Hello Niyas Raphy.

I have followed your instructions. I have duplicated the database and in it I have been uninstalling various modules and third party applications but the problem persists: TypeError: _action_done() got an unexpected keyword argument 'cancel_backorder'.

Then it occurred to me to update the Manufacturing (mrp_production) and Inventory (stock) modules themselves. I have not been able to update this last one because an error appears that may have to do with my problem since it talks about the same, the backorders.

This new error is as follows:

An error occurred while validating the view:

process_cancel_backorder is not a valid action on stock backorder confirmation

View name: stock_backorder_confirmation
Error context:
view:  ir ui  view
xmlid: view_backorder_confirmation


Can you give me any suggestion to tackle this new inconvenience?

Avatar
Discard
Best Answer

Hi,

Didn't hear such an issue inside odoo core. may be the error is raised due to any third party apps ? You can verify it by checking in the odoo runbot, if the error is not reproducible in the odoo runbot, the bug is due to either not updated source code or any third party apps.

So update the odoo source code and remove third party apps in a duplicated db and see if the issue still exists or not.


NOTE: do you have draft manufacturing module in your instance ? if yes, duplicate the db, and in duplicated db, uninstall that module and see, if the error comes or not.


Thanks

Avatar
Discard
Related Posts Replies Views Activity
1
May 24
365
0
May 24
249
1
Nov 22
2815
0
Apr 21
920
1
Dec 20
2002