Users are receiving more than was ordered, delivering more than was ordered, etc.
What is the best way to do this?
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Boekhouding
- Voorraad
- PoS
- Project
- MRP
Deze vraag is gerapporteerd
2
Antwoorden
10291
Weergaven
If you do this, you must educate users that IMMEDIATE Internal Transfers are no longer possible (they don't have any initial demand) unless they UNLOCK them after creation to add the initial demand.
They can still do PLANNED Internal Transfers without any issues.
One method is to create an Automated Action to block over picking:
Code:
if record.product_uom_qty < record.quantity_done:
raise Warning("You can't transfer more than the Initial Demand!")
Note that this is a code snippet only, and you may need to modify it to be more robust and to fit any specific edge cases you encounter.
For example, if you use scanning or show detailed operations on the transfer type you may need to create another automated action to handle security on Packing Operations (stock.move.line)
This works for PICKS, but not Delivery Orders (OUT).
You can change the code like:
if record.picking_code and record.picking_code != "internal" and record.product_uom_qty < record.quantity_done:
raise UserError("You can't transfer more than the Initial Demand!")
Geniet je van het gesprek? Blijf niet alleen lezen, doe ook mee!
Maak vandaag nog een account aan om te profiteren van exclusieve functies en deel uit te maken van onze geweldige community!
Aanmelden| Gerelateerde posts | Antwoorden | Weergaven | Activiteit | |
|---|---|---|---|---|
|
2
nov. 24
|
1733 | ||
|
0
jun. 25
|
376 | ||
|
0
jan. 25
|
1466 | ||
|
0
jan. 25
|
1509 | ||
|
1
dec. 24
|
2004 |
**raise UserError**
instead of "raise Warning" for V14 and above.