If you delete a component BOM from a Parent BOM it completely deletes the component BOM as opposed to converting back to a Parent BOM, This is incredibly dangerous, is there any way to prevent this from happening?
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Buchhaltung
- Lager
- PoS
- Projekte
- MRP
Diese Frage wurde gekennzeichnet
1
Antworten
5791
Ansichten
Unless I didn't understand your statement it sounds logical to me. If you cut the branch of a tree, all the branches attached afterwards will fall to the ground.
You should change the parent of the components that are pointing to the branch you want to delete, then delete the component you want to delete. You can easily find the components to modify beforehand with an advanced filter on "parent".
I agree that is logical, but the child branches (components) attached to the cut branch remain attached ie. it should remain a single BOM. where in this case they do not, it disappears into thin air. I understand you can change the parent of the child, but I find it dangerous that you can easily delete the entire child even though that may not have been the intent. I feel it should become a BOM without a parent.
Ah, I understand your point. Maybe you should try in the analytic account structure to see if the same occurs. If the analytic accounts behave the way you want, then I would conclude that there are relationships to BoMs that prevent of leaving the children without a parent.
Can you help me with Multi level BOM setup? Any documentation or information to setup Multi level BOM is appreciated
Diskutieren Sie gerne? Treten Sie bei, statt nur zu lesen!
Erstellen Sie heute ein Konto, um exklusive Funktionen zu nutzen und mit unserer tollen Community zu interagieren!
Registrieren