Bug 8845 Old Prices Calculated in Req. Worksheet

[Dan Karlsson (Dan-Karlsson)]

What & why

Does not set Order Date in Requisition Line to an older date than workdate when validating other fields, to make the price calculations correct.
Only update Starting Date when it is also validated to not set a faulty starting date. Also doesn't make sense to set starting date without validation since the field Starting Date-Time will not be synchronised.

Same pull request as microsoft/BusinessCentralApps#1869 that was closed when base app moved.

Linked work

Fixes #8845

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)

• Ran Calculate Plan... in Requistion Worksheet to see the results
• Added unit test in SCMPlanReqWksht.Codeunit.al
• Fixed old tests that relied on order date in the past to pass

Risk & compatibility

Starting Date isn't set when validating Order Date on Requisition Line from code. Should be a small risk since Starting Date-Time wasn't synchronised without further field validations.

[alexei-dobriansky]

Agentic PR Review - Round 1

Recommendation: Accept

What this PR does

This fixes purchase price calculation on requisition lines when planning dates would place the order date before the work date. The code now keeps price calculation on the work date while preserving the calculated starting date unless the Order Date field is validated directly. The main changed paths use Order Date as the price document date, so the old-price case is addressed without changing posting code or public APIs. The added regression test covers two vendor price periods and checks that the current price is selected.

Suggestions

No suggestions.

Risk assessment and necessity

Risk: This touches requisition worksheet planning dates and purchase direct unit cost. A mistake here could choose the wrong vendor cost on planned supply, but the change is narrow and does not change posting code, event signatures, or public procedure signatures.

Necessity: The linked bug is valid because a rush order can otherwise use an obsolete purchase price when lead time pushes the calculated order date into the past. The scope is right for the issue, and the tests cover the price regression plus related planning date expectations.

---

[AI-PR-REVIEW] version=1 promptVersion=2 system=github pr=10213 round=1 by=alexei-dobriansky at=2026-08-14T08:47:44Z lastSha=1df8d04b084f632029abc9c4608df9d1685c3868 reviewKey=na suggestions=