[Feature] External build order

[SchrodingersGat]

References

• Closes [FR] External Processing for Build Routing #2860
• Closes Add "External Build Order" #1071

This PR implements the concept of an "external" build order

• Build Order and Purchase Order are linked
• Stock is consumed against build order
• Purchase order line items are received into the build order (as outputs)

TODO

• Only allow builds to be marked as external if the linked part is purchaseable
• Only allow line items to link to a build order if the part is “assembly”
• Only allow line items to link to an “external” build order
• Display “external” status on build detail page
• Add “external” flag to build order
• Assign stock against build order when receiving
• Display linked “purchase orders” on build detail page
• Prevent build outputs being manually created against external order
• Display “build order” column in line item table
• Add link to build order in line item row
• API testing
• Playwright testing
• “External” badge on build order page
• Documentation for external builds
• Screenshots too
• Update demo dataset with an “external” build - Add external build order example demo-dataset#89
• Update demo dataset to enable feature - Add external build order example demo-dataset#89
• Implement functionality on receipt
• Display “external” status in build table / API
• Filter build list by “external” status
• Allow multiple line items to point to a build order ??
• Ensure that the “in production” and “on order” quantities do not “double up”

[netlify]

✅ Deploy Preview for inventree-web-pui-preview ready!

Name	Link
🔨 Latest commit	3bae51c
🔍 Latest deploy log	https://app.netlify.com/sites/inventree-web-pui-preview/deploys/680c3a5c67a5250008d7f448
😎 Deploy Preview	https://deploy-preview-9312--inventree-web-pui-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 91 (🔴 down 3 from production) Accessibility: 89 (no change from production) Best Practices: 100 (no change from production) SEO: 78 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

Attention: Patch coverage is 87.27273% with 14 lines in your changes missing coverage. Please review.

Project coverage is 86.35%. Comparing base (9729c41) to head (3bae51c).

Files with missing lines	Patch %	Lines
src/backend/InvenTree/order/models.py	56.66%	13 Missing ⚠️
src/backend/InvenTree/order/api.py	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #9312      +/-   ##
==========================================
- Coverage   86.35%   86.35%   -0.01%     
==========================================
  Files        1229     1231       +2     
  Lines       53954    54060     +106     
  Branches     2261     2257       -4     
==========================================
+ Hits        46594    46685      +91     
- Misses       6788     6803      +15     
  Partials      572      572              

Flag	Coverage Δ
backend	88.32% <87.27%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[SergeoLacruz]

-Build Order and Purchase Order are linked
I think this is the most important feature. It reflects our way of working. Actually we just leave comments in PO and BO :-(

-Stock is consumed against build order
Is there a difference from the way it works now? Stock is already consumed.

-Purchase order line items are received into the build order (as outputs)
Means when I receive the line items, BO output is automatically created and I cannot do this in BO? This is not so important, but will ease work and reduce errors :-)

• Add “external” flag to build order
  Nice because we also have internal ones :-)

• Add link to build order in line item row
  Does that mean each PO line item can be linked to a different BO? I understand from the other features that on PO is linked against on BO which is quite OK. The other way might make sense. I can imagine multiple POs for one BO in case the volume gets high or we distribute the BO over a longer time frame. 100pcs now, 500pcs a month later. But another BO would also be fine.