[Event Request] Codeunit 80 "Sales-Post" - Procedure SyncSurPlusItemTracking

[cperezsx]

Why do you need this change?

We would like to be able to customize the synchronization of reservations by expanding or modifying existing functionality.

Describe the request

Add new event "OnSyncSurPlusItemTrackingOnBeforeSetSourceFromSalesLine" to the procedure "SyncSurPlusItemTracking" of codeunit 80 "Sales-Post" Also change the check mark symbol < to <= on line 10451

`local procedure SyncSurPlusItemTracking(SalesHeader: Record "Sales Header"; SalesLine: Record "Sales Line")
var
Location2: Record Location;
ReservEntry: Record "Reservation Entry";
TempTrackingSpecification2: Record "Tracking Specification" temporary;
TempWarehouseActivityLine: Record "Warehouse Activity Line" temporary;
WarehouseAvailabilityMgt: Codeunit "Warehouse Availability Mgt.";
QtyReservedForCurrLine: Decimal;
SurplusQtyToHandle: Decimal;
isHandled: Boolean; //>New var
begin
if not SalesHeader.Ship then
exit;
if not (SalesHeader."Document Type" in [SalesHeader."Document Type"::Invoice, SalesHeader."Document Type"::Order]) then
exit;

    if (SalesLine."Location Code" = '') or
       not Location2.Get(SalesLine."Location Code") or
       not Location2."Require Shipment"
    then
        exit;
    //>New code begin
    OnSyncSurPlusItemTrackingOnBeforeSetSourceFromSalesLine(SalesHeader,SalesLine,IsHandled);
    if IsHandled then
         exit;
   //<<New Code End
    TempTrackingSpecification2.SetSourceFromSalesLine(SalesLine);
    TempTrackingSpecification2.SetSourceFromSalesLine(SalesLine);
    QtyReservedForCurrLine := Abs(WarehouseAvailabilityMgt.CalcLineReservedQtyOnInvt(
        TempTrackingSpecification2."Source Type", TempTrackingSpecification2."Source Subtype", TempTrackingSpecification2."Source ID", TempTrackingSpecification2."Source Ref. No.",
        0, false, TempWarehouseActivityLine));

    if QtyReservedForCurrLine = 0 then
        exit;

    ReservEntry.SetSourceFilter(
                             TempTrackingSpecification2."Source Type", TempTrackingSpecification2."Source Subtype",
                             TempTrackingSpecification2."Source ID", TempTrackingSpecification2."Source Ref. No.", true);
    ReservEntry.SetSourceFilter('', TempTrackingSpecification2."Source Prod. Order Line");
    ReservEntry.SetRange("Reservation Status", ReservEntry."Reservation Status"::Surplus);
    if not ReservEntry.FindSet() then
        exit;

    ReservEntry.CalcSums("Qty. to Handle (Base)");
    SurplusQtyToHandle := Abs(ReservEntry."Qty. to Handle (Base)");
    //>Change code Begin
    // if (QtyReservedForCurrLine + SurplusQtyToHandle) < SalesLine."Qty. to Ship (Base)" then> old Code
    if (QtyReservedForCurrLine + SurplusQtyToHandle) <= SalesLine."Qty. to Ship (Base)" then //> New code
    //>Change code end
        exit;

    ReservEntry.ModifyAll("Qty. to Handle (Base)", 0);
    ReservEntry.ModifyAll("Qty. to Invoice (Base)", 0);
end;

//>>New Code Begin
[IntegrationEvent(false, false)]
local procedure OnSyncSurPlusItemTrackingOnBeforeSetSourceFromSalesLine(SalesHeader: Record "Sales Header"; SalesLine: Record "Sales Line"; var isHandled: Boolean)
begin
end;
//<<New Code End`

[AleksandricMarko]

Hi @cperezsx,

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:

• Meaningful Justification: Please provide a more specific explanation of the technical intent or business scenario. The current justification "customize the synchronization of reservations" is too generic. Describe the specific problem you're trying to solve and why the existing functionality cannot support it.

• Proposed Code Change: Please provide the actual AL code showing the exact changes with surrounding context (5-10 lines). The issue appears to reference code but it's not fully visible in the description.

• Alternatives Evaluated: Please describe which existing events or patterns you have tried and explain why they are insufficient for your scenario.

• Justification for IsHandled: Please explain why the IsHandled pattern is necessary instead of a standard event or alternative approach.

• Performance Considerations: Please provide information about the expected execution frequency of this event and assess the potential performance impact.

• Data Sensitivity Review: Please confirm that no sensitive data will be exposed through this event, or provide a rationale if data exposure is necessary.

• Multi-Extension Interaction: Please discuss the risks if multiple extensions subscribe to this event and describe how conflicts would be mitigated.

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