Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reusability of Defined Operations in ERPNext Manufacturing Module #44953

Open
alirezamohammadi opened this issue Dec 29, 2024 · 0 comments
Open

Comments

@alirezamohammadi
Copy link

In the ERPNext manufacturing module, the Operation doctype is used in BOM Operation. By design, operations appear to be intended for reuse across multiple BOMs. However, the Operation doctype includes a field for the "quality inspection template" which assumes that the same inspection template applies to all BOM Operations using the operation. This design is problematic because quality inspection requirements often vary depending on the context in which the operation is used.

Proposed Solutions

To address this issue assuming that opertions are supposed to be reusable (correct me if I am wrong):

  • Option 1:
    • Remove the "quality inspection template" field from the Operation doctype.
    • Move this field to the BOM Operation doctype, enabling BOM-specific quality inspection templates to be assigned.
  • Option 2:
    • Retain the "quality inspection template" field in the Operation doctype as a default template.
    • Allow users to override the default template by selecting a BOM-specific quality inspection template in the BOM Operation doctype.

I would be happy to submit a merge request if either solution is accepted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant