You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When someone transitions from the old system to ERPNext, the work order does not exist at that time.
Repack keeps the output as an FG item and the input as raw materials by default, making it very difficult to reverse when there are 150 material input items.
On the other hand, Disassembly performs the expected operation in one go.
It would be beneficial to consider ignoring the Work Order (WO) validation, as it is a simple change that could help in several manufacturing scenarios.
For example, in cases where different operations are carried out via subcontracting, users may not want SFG (Semi-Finished Goods) items to be created at each stage.
Is your feature request related to a problem? Please describe.
When someone transitions from the old system to ERPNext, the work order does not exist at that time.
Repack keeps the output as an FG item and the input as raw materials by default, making it very difficult to reverse when there are 150 material input items.
On the other hand, Disassembly performs the expected operation in one go.
It would be beneficial to consider ignoring the Work Order (WO) validation, as it is a simple change that could help in several manufacturing scenarios.
For example, in cases where different operations are carried out via subcontracting, users may not want SFG (Semi-Finished Goods) items to be created at each stage.
https://support.frappe.io/helpdesk/my-tickets/33477
Describe the solution you'd like
Please remove the mandatory Work Order requirement for Disassembly in Stock entry.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: