[W1][Codeunit][22][Item Jnl.-Post Line] Add integration event OnApplyItemLedgEntryOnBeforeCheckApplicationComplete in procedure ApplyItemLedgEntry

[mavohra]

Why do you need this change?

We need to suppress the standard application-loop exit inside ApplyItemLedgEntry when "Remaining Quantity" + "Reserved Quantity" = 0 is satisfied, but an additional quantity dimension on the item ledger entry is still non-zero. The standard code exits unconditionally when that single sum reaches zero, with no way to evaluate further conditions before the exit is taken.

The standard exit check is if ItemLedgEntry."Remaining Quantity" + ItemLedgEntry."Reserved Quantity" = 0 then exit. For items that carry an additional quantity field alongside the base quantity, the base remaining quantity can reach zero while the alternate remaining quantity is still outstanding, meaning the application is not yet complete. The standard check cannot account for this because it reads only the two base fields.

OnAfterUpdateItemLedgerEntryRemainingQuantity fires inside UpdateItemLedgerEntryRemainingQuantity before CalcReservedQuantity is called on the outer entry, so reserved quantity is not yet refreshed and the full exit condition cannot be evaluated there. OnApplyItemLedgEntryOnApplicationLoop fires at the very end of each loop iteration, after the exit check has already been executed and the procedure has already returned, making it too late to prevent the exit. No event currently exists between ItemLedgEntry.CalcReservedQuantity() and the if ... = 0 then exit line inside the if AppliedQty <> 0 then block of ApplyItemLedgEntry.

Describe the request

Add an integration event OnApplyItemLedgEntryOnBeforeCheckApplicationComplete in ApplyItemLedgEntry in Codeunit 22 "Item Jnl.-Post Line" after ItemLedgEntry.CalcReservedQuantity() and before the exit condition that checks whether remaining and reserved quantities sum to zero.

                UpdateItemLedgerEntryRemainingQuantity(ItemLedgEntry, AppliedQty, OldItemLedgEntry, CausedByTransfer);

                ItemLedgEntry.CalcReservedQuantity();
                IsHandled := false;
                OnApplyItemLedgEntryOnBeforeCheckApplicationComplete(ItemLedgEntry, IsHandled); // <---- New Event
                if not IsHandled then
                    if ItemLedgEntry."Remaining Quantity" + ItemLedgEntry."Reserved Quantity" = 0 then
                        exit;
            end;

Event Signature:

[IntegrationEvent(false, false)]
local procedure OnApplyItemLedgEntryOnBeforeCheckApplicationComplete(var ItemLedgEntry: Record "Item Ledger Entry"; var IsHandled: Boolean)
begin
end;

Alternatives evaluated: OnAfterUpdateItemLedgerEntryRemainingQuantity fires inside UpdateItemLedgerEntryRemainingQuantity before CalcReservedQuantity is called on the outer item ledger entry, so the reserved quantity used in the exit condition is not yet current and the full exit decision cannot be made at that point. OnApplyItemLedgEntryOnApplicationLoop fires at the very end of each loop iteration, after the exit check has already executed and the procedure has already returned when the condition was true, making it impossible to prevent the exit. No event currently exists between ItemLedgEntry.CalcReservedQuantity() and the if ItemLedgEntry."Remaining Quantity" + ItemLedgEntry."Reserved Quantity" = 0 then exit line inside the if AppliedQty <> 0 then block of ApplyItemLedgEntry.
Internal work item: AB#638497

[github-actions]

Hi @mavohra,

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:

• Performance considerations: Please describe the expected execution frequency of this IsHandled event and any anticipated performance impact.
• Data sensitivity review: Please confirm that the event does not expose sensitive data, or provide the rationale if sensitive data must be exposed.
• Multi-extension interaction: Please describe any conflict risk if multiple extensions subscribe to this IsHandled event and how that risk should be handled.

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.

[mavohra]

Performance note: ApplyItemLedgEntry drives the item ledger application loop and is called for every item journal posting that requires cost application, purchases, sales, transfers, output, and consumption. Within each call, the loop iterates once per entry pair applied. The event fires once per iteration, inside the if AppliedQty <> 0 then block, after CalcReservedQuantity is called on ItemLedgEntry. For items with many open applications this fires multiple times per posting. When IsHandled is not set, execution falls through to the standard exit check unchanged with no overhead. When a subscriber sets IsHandled, it takes over the exit decision: the subscriber evaluates whether any additional quantity dimension still outstanding on ItemLedgEntry should prevent the exit, and either allows the exit or continues the loop.

Data sensitivity review: The event exposes ItemLedgEntry (var Item Ledger Entry) and IsHandled. The item ledger entry contains standard posting data: item number, location, quantities, item tracking, and posting date. No sensitive data is exposed beyond what ApplyItemLedgEntry already processes internally.

Multi-extension interaction assessment: Unlikely

[github-actions]

Hi @mavohra,

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:

• Multi-extension interaction: Please explain how conflicts would be handled if multiple extensions subscribe to this IsHandled event and influence the same control-flow decision.

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.

[mavohra]

Any subsequent subscriber can check IsHandled before acting to avoid conflicts. This is the same pattern used by existing IsHandled events throughout Purch.-Post. No additional mitigation is needed.

[github-actions]

✅ Analysis complete - ready for further processing

---

Implementation:

Add a new integration event in ApplyItemLedgEntry of Codeunit 22 "Item Jnl.-Post Line" after ItemLedgEntry.CalcReservedQuantity() and before the application-complete exit check.

Location in ApplyItemLedgEntry procedure:

                UpdateItemLedgerEntryRemainingQuantity(ItemLedgEntry, AppliedQty, OldItemLedgEntry, CausedByTransfer);

                ItemLedgEntry.CalcReservedQuantity();
                IsHandled := false;
                OnApplyItemLedgEntryOnBeforeCheckApplicationComplete(ItemLedgEntry, IsHandled);
                if not IsHandled then
                    if ItemLedgEntry."Remaining Quantity" + ItemLedgEntry."Reserved Quantity" = 0 then
                        exit;
            end;
            OnApplyItemLedgEntryOnApplicationLoop(ItemLedgEntry);
        until false;
    end;

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

[IntegrationEvent(false, false)]
local procedure OnApplyItemLedgEntryOnBeforeCheckApplicationComplete(var ItemLedgEntry: Record "Item Ledger Entry"; var IsHandled: Boolean)
begin
end;

---

File: ItemJnlPostLine.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.