#9670 [Main] - Posting from Released production order affects Firm planned production order with same ID.
A status check was added to prevent Firm Planned production orders from incorrectly reading capacity ledger entries of same-numbered Released orders, which was causing their allocated capacity to be miscalculated.
- 2files
- 1AL files
- 1objects
Pull request · merged into main (BC30) on 2026-07-27 by DhavalMore88 (community contribution) · 2 files (+67 -0), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Added status guard in CalcActuallyPostedCapacityTime that returns 0 for non-Released/Finished statuses
- Prevents Firm Planned, Planned, and Simulated orders from reading capacity ledger entries
- Ensures allocated capacity for Firm Planned orders is calculated correctly as full needed time
- Fixes data corruption where allocated time was wrongly reduced by another order’s posted capacity
- Test coverage added for the capacity requirements scenario
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 99000774 “Calculate Routing Line”, Base Application: modified
Context
- Work items: AB#643265
- Labels: ADO: Sync, From Fork, Team: SCM
- Systems: manufacturing
- From the description: “Added a status guard at the top of CalcActuallyPostedCapacityTime that returns 0 when the routing line’s Status is not Released or Finished.”
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).