#11001 Bug 648577: [IT] Subcontracting migration does not precheck bin-mandatory locations
The IT subcontracting migration now prechecks legacy vendor and purchase-header locations for unsupported warehouse settings, such as bin mandatory. If any are found it stops with a single error listing every incompatible location and its enabled settings, and leaves migration data untouched.
- 2files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-09-18 by ChethanT · 2 files (+351 -0), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Blocks migration when legacy vendor or purchase-header locations use unsupported warehouse settings
- Reports every incompatible location and lists each enabled setting
- Migration data stays untouched when the precheck fails
- Errors collected during the precheck are handled explicitly and raised as one blocking error
- Tests cover multiple locations, all unsupported settings, and migration stopping before vendor data is copied
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 149951 “IT Subc. Migration”, SubcontractingMigrationIT (IT layer): modified
Also merged into
- #11646 into
releases/29.xon 2026-09-28
Context
- Work items: AB#648577
- Labels: Subcontracting, Team: SCM
- Systems: manufacturing
- From the description: “Block IT subcontracting migration when legacy vendor or purchase-header locations use unsupported warehouse settings.”
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).