[Event Request] Add OnBeforeValidateQtyPickedInShipmentBin IsHandled Event in Codeunit 7314 "Warehouse Availability Mgt."

[BergantINC]

Why do you need this change?

The procedure ValidateQtyPickedInShipmentBin in Codeunit 7314 "Warehouse Availability Mgt." assumes that the shipment quantity should always be validated against the default Shipment Bin Code defined on the Location.

This causes incorrect behavior in scenarios where a Warehouse Shipment uses a bin that is different from the Location's default Shipment Bin Code. As a result, the validation can calculate the available quantity from the wrong bin and incorrectly modify QtyPicked.

The current implementation does not expose any extensibility point that allows this logic to be overridden or redirected to the actual shipment bin.

Describe the request

Object: Codeunit 7314 "Warehouse Availability Mgt."
Procedure: ValidateQtyPickedInShipmentBin
Placement: At the beginning of the procedure, before the standard validation logic is executed.

We would need an event that has all the parameters + IsHandled at the beggining with exit if IsHandled = true.
Internal work item: AB#638833

[github-actions]

Hi @BergantINC,

Thank you for your extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Exact proposed code change with context: Please include the proposed event call and publisher signature with surrounding code context (for example 5-10 lines) showing the intended placement at the beginning of ValidateQtyPickedInShipmentBin.
• Alternatives evaluated: Please describe any existing extensibility points or patterns you considered and why they are not sufficient for this scenario.
• Performance/frequency impact: Please add a brief note on how often this code path is expected to run and any expected performance impact.
• Data sensitivity confirmation: Please confirm that the requested event would not expose sensitive or private data.
• Multi-extension interaction or conflict mitigation: Please add a brief note about how potential conflicts between multiple extensions using this IsHandled event should be handled or mitigated.

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

Note

Automatically generated by the Triage Agent — advisory only. An engineer will review before any action is taken.

Tip

Not accurate? Reply with /not-accurate (optional: add a short explanation). Your feedback improves future responses.

[BergantINC]

Additional information

Exact proposed code change with context

We would like to request an OnBefore event with an IsHandled pattern at the beginning of ValidateQtyPickedInShipmentBin in Codeunit **7314 "Warehouse Availability Mgt."`.

Proposed placement:

local procedure ValidateQtyPickedInShipmentBin(
    var QtyPicked: Decimal;
    LocationCode: Code[10];
    ItemNo: Code[20];
    VariantCode: Code[10];
    TrackingSpecification: Record "Tracking Specification";
    SourceType: Integer)
var
    Location: Record Location;
    ItemTrackingSetup: Record "Item Tracking Setup";
    QtyOnShipmentBin: Decimal;
    IsHandled: Boolean;
begin
    OnBeforeValidateQtyPickedInShipmentBin(
        QtyPicked,
        LocationCode,
        ItemNo,
        VariantCode,
        TrackingSpecification,
        SourceType,
        IsHandled);

    if IsHandled then
        exit;

    if not (Location.RequireShipment(LocationCode) and (QtyPicked <> 0)) then
        exit;

    if SourceType <> 17 then
        exit;

    // Existing implementation...
end;

Proposed event:

[IntegrationEvent(false, false)]
local procedure OnBeforeValidateQtyPickedInShipmentBin(
    var QtyPicked: Decimal;
    LocationCode: Code[10];
    ItemNo: Code[20];
    VariantCode: Code[10];
    TrackingSpecification: Record "Tracking Specification";
    SourceType: Integer;
    var IsHandled: Boolean)
begin
end;

Alternatives evaluated

We evaluated the existing extensibility points in the warehouse availability and warehouse shipment flow but could not find an event that allows overriding or replacing the logic inside ValidateQtyPickedInShipmentBin.

The issue is specifically that the implementation always uses Location."Shipment Bin Code" when calculating the available quantity. There is currently no event before this logic that allows an extension to use the actual shipment bin selected on the Warehouse Shipment instead.

Without an IsHandled event, the only alternatives are modifying the base application or duplicating functionality outside the standard flow, neither of which is desirable.

Performance / frequency impact

The proposed event would be invoked once whenever ValidateQtyPickedInShipmentBin is executed as part of the standard warehouse validation process.

The default implementation would only perform a single event invocation and a boolean check (IsHandled), resulting in negligible performance overhead. Extensions that do not subscribe to the event would experience virtually no impact.

Data sensitivity confirmation

The event would expose only the same parameters already available within the procedure (QtyPicked, LocationCode, ItemNo, VariantCode, TrackingSpecification, and SourceType).

No additional customer, personal, or sensitive data would be exposed by introducing this event.

Multi-extension interaction / conflict mitigation

This follows the standard Business Central OnBefore + IsHandled extensibility pattern already used throughout the base application.

As with other IsHandled events, it is the responsibility of subscribing extensions to coordinate behavior and avoid conflicting implementations. The event would not introduce any new multi-extension concerns beyond the existing established extensibility model.

[github-actions]

✅ Analysis complete - ready for further processing

---

Implementation:

Add a new OnBeforeValidateQtyPickedInShipmentBin integration event with IsHandled at the beginning of ValidateQtyPickedInShipmentBin so extensions can override the standard shipment-bin validation logic.

Location in ValidateQtyPickedInShipmentBin() procedure:

local procedure ValidateQtyPickedInShipmentBin(var QtyPicked: Decimal; LocationCode: Code[10]; ItemNo: Code[20]; VariantCode: Code[10]; TrackingSpecification: Record "Tracking Specification"; SourceType: Integer)
var
    Location: Record Location;
    ItemTrackingSetup: Record "Item Tracking Setup";
    QtyOnShipmentBin: Decimal;
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeValidateQtyPickedInShipmentBin(QtyPicked, LocationCode, ItemNo, VariantCode, TrackingSpecification, SourceType, IsHandled);
    if IsHandled then
        exit;

    if not (Location.RequireShipment(LocationCode) and (QtyPicked <> 0)) then
        exit;

    if SourceType <> 37 then // Database::Sales Line
        exit;

    ItemTrackingSetup.CopyTrackingFromTrackingSpec(TrackingSpecification);
    if not (Location.Get(LocationCode) and Location."Bin Mandatory" and (Location."Shipment Bin Code" <> '')) then
        exit;

    QtyOnShipmentBin := CalcQtyOnBin(LocationCode, Location."Shipment Bin Code", ItemNo, VariantCode, ItemTrackingSetup);
    if QtyOnShipmentBin = 0 then
        QtyPicked := 0
end;

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

[IntegrationEvent(false, false)]
local procedure OnBeforeValidateQtyPickedInShipmentBin(var QtyPicked: Decimal; LocationCode: Code[10]; ItemNo: Code[20]; VariantCode: Code[10]; TrackingSpecification: Record "Tracking Specification"; SourceType: Integer; var IsHandled: Boolean)
begin
end;

---

File: WarehouseAvailabilityMgt.Codeunit.al

Note

Automatically generated by the Triage Agent — advisory only. An engineer will review before any action is taken.

Tip

Not accurate? Reply with /not-accurate (optional: add a short explanation). Your feedback improves future responses.