#8902 Bug 639568: Scope Subc. PO component location check to current prod order line
Fixed a false warning when creating subcontracting purchase orders from routing lines on production orders with multiple lines sharing the same routing link code by scoping the component location check to the current line.
- 2files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-07-28 by ChethanT · 2 files (+79 -0), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- A false warning about component location appeared when a production order had several lines sharing the same routing link code
- Root cause: the component check filtered by production order and routing link code but not by production order line number
- Adds a Prod. Order Line No. filter so only the current line’s components are checked
- Adds a test where another line’s component is already at the subcontracting location
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 20557 “Subc. Purchase Order Creator”, Subcontracting: modified
Context
- Work items: AB#639568
- Labels: AL: Apps (W1), Subcontracting, Team: SCM
- Systems: manufacturing
- From the description: “added
SetRange("Prod. Order Line No.", ProdOrderRoutingLine."Routing Reference No.")to scope the check to the line being processed”
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).