Proposal: Consider Merging is_sub_contracted_item into default_material_request_type

Hi community,

I’ve been exploring the Item doctype structure and noticed an interesting opportunity for simplification. Currently we have two related fields:

  1. default_material_request_type (Purchase/Transfer/Material Issue/Manufacture)
  2. is_sub_contracted_item (checkmark for subcontracting)

Would it make sense to consolidate these by:

  • Adding “Subcontract” as a new option in default_material_request_type
  • Deprecating the standalone checkbox

This could:
✓ Reduce field redundancy
✓ Simplify data model
✓ Align with other MR type handling patterns

I’m curious why these were initially separated. Are there specific business cases or technical constraints that require maintaining both fields? Looking forward to hearing thoughts from core maintainers and other implementors.

Best regards,