Production Scenarios

Release: Production Scenarios – 26.0.9684.35708

Description

This release of Production Scenarios delivers a critical bug fix for the MPO (Manufacturing Planning & Optimization) integration module and introduces a technical alignment for Business Central v29 compatibility.

The main fix resolves a runtime error that occurred when users attempted to change the Process Type on a production order line where the current Process Type was empty. Additionally, a codeunit reference used in the Family Production Journal page has been updated to align with the renamed manufacturing-specific codeunit introduced in Business Central v29, ensuring forward compatibility.

User Stories

Title Description Setup Instructions Impact on previous version
[24182] – v29 requirement Technical alignment of the Production Scenarios application with Business Central v29 platform requirements. The variable CostCalcMgt in the Family Production Journal page (Page 71926175 – briPSC_FamilyProductionJournal) was retyped from Codeunit “Cost Calculation Management” to Codeunit “Mfg. Cost Calculation Mgt.” to match the renamed codeunit in the v29 manufacturing module. No setup required. The change is internal and transparent to the user. No breaking change. The variable is private and has no external surface impact. Applications dependent on v29 must adopt this version.

Bugs

Title Description Impact on previous version
[23857] – Integration MPO – Error when “Change Process Type” and Process Type is empty When a Factory Planning line had an empty Process Type but valid production scenarios existed for the item/location, opening the “Change Process Type” dialog raised the error: “The Production Scenario does not exist. Identification fields and values: Item No.=’…', Variant Code=’…', Location Code=’…', Process Type=’'". The fix applies a guarded if ProductionScenario.Get(...) then; pattern in the OnOpenPage trigger of page 71926186 (briPSC_ChangeProcessType), allowing the dialog to open gracefully even when no Process Type is currently assigned. The user can then select among available process types. Low risk. The fix only changes error-handling behavior from a hard error to a graceful fallback. No regression expected on existing scenarios where a Process Type is already assigned.

Events

No event added or updated in this release.

Previous