[Extensibility] Add integration event in Codeunit 99000819 before GetPlanningParameters.AtSKU in CreatePlanningComponentFromProdBOM

[andbyPrague]

Why do you need this change?

In multi-warehouse manufacturing scenarios, the component location (PlanningComponent."Location Code") must sometimes be overridden based on custom business rules before the system resolves the component's SKU. A common real-world case: a company manufactures goods at one location but sources components from a different location depending on the component item. The standard logic assigns PlanningComponent."Location Code" from SKU."Components at Location", but partners need to override this per-item before SKU parameters are resolved.

The SKU resolution happens in GetPlanningParameters.AtSKU(...) and determines critical planning fields such as "Flushing Method" and "Planning Level Code". Without an event before this call, any location override made in a subscriber has no effect ΓÇö the wrong SKU is used, leading to incorrect flushing method and planning level on the component.

The nearest existing event OnTransferBOMOnBeforeGetDefaultBin fires after GetPlanningParameters.AtSKU has already executed, making it unsuitable as a workaround.

Describe the request

Add an [IntegrationEvent] in Codeunit 99000819 "Mfg. Planning Line Management", procedure CreatePlanningComponentFromProdBOM, immediately before the call to GetPlanningParameters.AtSKU(...). The event should expose PlanningComponent, ProductionBOMLine, RequisitionLine, and SKU so subscribers can modify the component location before SKU parameters are resolved.

Suggested name: OnCreatePlanningComponentFromProdBOMOnBeforeGetPlanningParameters
The event should be inserted after:

PlanningComponent.Validate("Calculation Formula", ProdBOMLine."Calculation Formula");
and before:

GetPlanningParameters.AtSKU(CompSKU, PlanningComponent."Item No.", PlanningComponent."Variant Code", PlanningComponent."Location Code");

Internal work item: AB#635594

[AleksandricMarko]

Hi @andbyPrague,

Thanks for submitting this extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Proposed code change: Please provide the exact AL code addition or modification with surrounding context (about 5-10 lines), showing the target procedure area and the new event publisher call and declaration in text form.

Please update the issue with the missing details. We'll automatically re-analyze once updated.

[andbyPrague]

Hi @AleksandricMarko
event publisher call in CreateEventPlanningComponentFromProdBOM (surrounding context)
PlanningComponent.Validate("Scrap %", ProdBOMLine."Scrap %");
PlanningComponent.Validate("Calculation Formula", ProdBOMLine."Calculation Formula");

OnCreatePlanningComponentFromProdBOMOnBeforeGetPlanningParameters(PlanningComponent, ProdBOMLine, ReqLine, SKU); // NEW

GetPlanningParameters.AtSKU(CompSKU, PlanningComponent."Item No.", PlanningComponent."Variant Code", PlanningComponent."Location Code");
if Item2.Get(PlanningComponent."Item No.") then
PlanningComponent.Critical := Item2.Critical;

PlanningComponent."Flushing Method" := CompSKU."Flushing Method";
OnTransferBOMOnBeforeGetDefaultBin(PlanningComponent, ProdBOMLine, ReqLine, SKU);

event declaration to be added at the bottom of the codeunit
[IntegrationEvent(false, false)]
local procedure OnCreatePlanningComponentFromProdBOMOnBeforeGetPlanningParameters(
var PlanningComponent: Record "Planning Component";
var ProductionBOMLine: Record "Production BOM Line";
RequisitionLine: Record "Requisition Line";
var SKU: Record "Stockkeeping Unit")
begin
end;

[AleksandricMarko]

✅ Analysis complete - approved for implementation

---

Implementation:

Add a new integration event in CreatePlanningComponentFromProdBOM() immediately before GetPlanningParameters.AtSKU(...) so subscribers can update PlanningComponent."Location Code" before SKU parameters are resolved.

Location in CreatePlanningComponentFromProdBOM() procedure (around line 316):

PlanningComponent.Validate("Scrap %", ProdBOMLine."Scrap %");
PlanningComponent.Validate("Calculation Formula", ProdBOMLine."Calculation Formula");

OnCreatePlanningComponentFromProdBOMOnBeforeGetPlanningParameters(PlanningComponent, ProdBOMLine, ReqLine, SKU);

GetPlanningParameters.AtSKU(CompSKU, PlanningComponent."Item No.", PlanningComponent."Variant Code", PlanningComponent."Location Code");
if Item2.Get(PlanningComponent."Item No.") then
    PlanningComponent.Critical := Item2.Critical;

PlanningComponent."Flushing Method" := CompSKU."Flushing Method";
OnTransferBOMOnBeforeGetDefaultBin(PlanningComponent, ProdBOMLine, ReqLine, SKU);

Event Publisher (add at the end of the codeunit with other events):

[IntegrationEvent(false, false)]
local procedure OnCreatePlanningComponentFromProdBOMOnBeforeGetPlanningParameters(
    var PlanningComponent: Record "Planning Component";
    var ProductionBOMLine: Record "Production BOM Line";
    RequisitionLine: Record "Requisition Line";
    var StockkeepingUnit: Record "Stockkeeping Unit")
begin
end;

---

File: MfgPlanningLineManagement.Codeunit.al

[AleksandricMarko]

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.