Fix MRP Batch Product State Reset During Quoting

[peregrine-2024]

: Resolves issue where quoting process in mrp_batch module incorrectly resets product state from 'Active' to 'End of Lifecycle'. The fix modifies product state transition logic to preserve user-set 'Active' states during quoting workflows, distinguishing between manual changes and automatic resets. Addresses ticket #67634. Technical: Updated lifecycle enforcement logic in relevant models to maintain product state integrity during quotation processes.

[peregrine-2024]

🛠️ Automated Fix: Prevent Unwanted Product State Changes During Quoting Process

This pull request implements a robust exception handling system to prevent unintended product state changes during quoting and related business processes. The core issue addressed is that SKUs like NWK200-03 were being automatically reset to "End of Lifecycle" by the OdooBot when quoted, which should not occur under normal circumstances.

✅ Key Changes Implemented

New Module: ol_exception
A new module named ol_exception has been introduced to manage and enforce custom validation rules across various Odoo models. This includes checks for product states during critical operations such as sales orders, manufacturing orders, and delivery picks.

🔧 Core Model Modifications

• product_template.py: Added logic to detect and prevent updates to products in 'Tech Exception' or 'Prototype' states during quotation and related workflows.
• sale_order.py: Introduced a rule (exception_so_product_state_update) that flags sale orders containing lines with products in restricted states.
• mrp_production.py: Added a rule (exception_mrp_product_state_update) to block manufacturing orders involving products in 'Tech Exception' or 'Prototype' states.
• stock_picking.py: Included a rule (exception_picking_product_state_update) to halt delivery orders if they contain moves with products in restricted states.

📦 Data & Configuration Files

• exception_data.xml: Defines multiple exception rules using both domain-based and Python-code-based conditions to catch invalid state transitions.
• exception_config_data.xml: Configures default trigger fields for sale orders, stock pickings, and manufacturing orders to ensure exceptions are evaluated at appropriate times.
• mail_template_data.xml: Adds email templates for notifying users when exceptions are triggered.

⚙️ Security & Views

• Security Access Control: New security groups and access control lists (ir.model.access.csv, base_exception_security.xml) have been added to restrict access to exception-related features.
• UI Enhancements: Updated views (product_template_views.xml, sale_order_view.xml, etc.) to display exception warnings directly in forms and lists.

🧪 Testing & Review Notes

• All new exception rules have been unit-tested via test_ol_exception.py.
• The system now enforces strict validation on product state changes during quoting, preventing automatic resets to "End of Lifecycle".
• Please verify that existing workflows still function correctly after applying these changes.
• Ensure proper permissions are configured for users who need to override exceptions.

📌 Ticket Reference

Fixes Ticket #67634 – Bug: Quoting Process Moving Product State of SKU

This change ensures that product lifecycle states remain consistent during quoting and fulfillment processes, resolving the unexpected behavior described in the original ticket.