[Event Request] codeunit 99000808 "PlanningRoutingManagement" OnBeforeSetRtngLineSequenceBack

[dmonteagudo-pwd]

Why do you need this change?

Description

Request to add a specific integration event at the beginning of SetRtngLineSequenceBack procedure in Planning Routing Management codeunit (ID: 99000808) to enable partners to implement a critical workaround for a data consistency bug.

Critical Business Need

There is a critical bug in SetRtngLineSequenceBack where the procedure works with record data that has been reset to zeros by previous ModifyAll operations in CalcSequenceBack. This causes incorrect sequence calculations and data corruption in manufacturing planning.

Partners need an event at the VERY BEGINNING of the procedure to:

1. Refresh the record data using PlanningRtngLine.Get()
2. Ensure the procedure works with current database state
3. Prevent manufacturing planning errors

Describe the request

    procedure SetRtngLineSequenceBack(RoutingType: Option Serial,Parallel; PlanningRtngLine: Record "Planning Routing Line"; Maxsequences: Integer; Actsequences: Integer; TotalCalculation: Boolean)
    var
        PlanningRtngLine2: Record "Planning Routing Line";
        SequenceNo: Integer;
    begin
       //-- NEW EVENT --
       OnBeforeSetRtngLineSequenceBack(RoutingType, PlanningRtngLine, MaxSeq, ActSeq, TotalCalculation, IsHandled);
       //++ NEW EVENT ++

        if RoutingType = RoutingType::Parallel then begin
            if (Actsequences - 1) > Maxsequences then
                ErrorInRouting(
                  PlanningRtngLine."Worksheet Line No.", Text001, Actsequences, Maxsequences);

[IntegrationEvent(false, false)]
local procedure OnBeforeSetRtngLineSequenceBack(RoutingType: Option; var PlanningRtngLine: Record "Planning Routing Line"; var MaxSeq: Integer; var ActSeq: Integer; TotalCalculation: Boolean; var IsHandled: Boolean)

Internal work item: AB#616459

[AleksandricMarko]

Hello @dmonteagudo-pwd
If there is a bug with existing solution, why do not you log it as a bug with repro steps so we can fix it?
That is a way better solution than just skipping part of code.

Also, I would like to mention that we have min. set of requirements for IsHandled events (link), so if you still want to go with event, you need to provide required information.

[dmonteagudo-pwd]

Hello @AleksandricMarko,

Thank you for your feedback and for pointing out the minimum requirements for IsHandled events. After reviewing the documentation, I realized that an IsHandled pattern is not strictly necessary for our scenario, so I have updated my request accordingly.

Regarding your question about logging a bug: my colleague is currently preparing the official bug report with full repro steps. The reason I initially requested an event instead of waiting for the bug fix is due to resolution time constraints. In our experience, event requests are usually processed faster than bug fixes, and we need a temporary workaround to keep manufacturing planning stable until the official fix is delivered.

Updated proposal:

• Event Name: OnBeforeSetRtngLineSequenceBack
• Location: Beginning of SetRtngLineSequenceBack in Codeunit 99000808 "PlanningRoutingManagement"
• Parameters: RoutingType, PlanningRtngLine, MaxSequences, ActSequences, TotalCalculation
• Usage Scenario: This event will allow us to refresh the Planning Routing Line record and ensure the procedure works with the current database state, preventing planning errors caused by previous ModifyAll operations

[AleksandricMarko]

✅ Analysis complete - approved for implementation

---

Implementation:

Add a new integration event at the beginning of the SetRtngLineSequenceBack procedure in Codeunit 99000808 "PlanningRoutingManagement".

Location in SetRtngLineSequenceBack procedure (around line 78):

procedure SetRtngLineSequenceBack(RoutingType: Option Serial,Parallel; PlanningRtngLine: Record "Planning Routing Line"; Maxsequences: Integer; Actsequences: Integer; TotalCalculation: Boolean)
var
    PlanningRtngLine2: Record "Planning Routing Line";
    SequenceNo: Integer;
begin
    OnBeforeSetRtngLineSequenceBack(RoutingType, PlanningRtngLine, Maxsequences, Actsequences, TotalCalculation);

    if RoutingType = RoutingType::Parallel then begin
        if (Actsequences - 1) > Maxsequences then
            ErrorInRouting(
              PlanningRtngLine."Worksheet Line No.", Text001, Actsequences, Maxsequences);

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

[IntegrationEvent(false, false)]
local procedure OnBeforeSetRtngLineSequenceBack(RoutingType: Option Serial,Parallel; var PlanningRtngLine: Record "Planning Routing Line"; Maxsequences: Integer; Actsequences: Integer; TotalCalculation: Boolean)
begin
end;

---

File: PlanningRoutingManagement.Codeunit.al

[JesperSchulz]

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.

Build ID: 43688.