#11059 Hardening subscription billing + drop shipment scenarios

Subscription Billing now creates subscriptions at sales order release from the existing quantity per serial number, using Qty. to Ship only as a fallback, so a blank Default Quantity to Ship works. It also fake-invoices sales orders released through drop shipment purchase receipts.

2files

1AL files

1objects

Pull request · merged into main (BC30) on 2026-09-08 by mynjj · 2 files (+123 -8), 1 AL · fix · tier official · reviewed (checked by Opus)

What changed

Subscription creation uses QtyPerSerialNo and falls back to Qty. to Ship only when it is zero
Handles Sales & Receivables Setup with Default Quantity to Ship set to Blank
Subscribes to sales orders closed by a drop shipment purchase order and sets the same values as the normal path
Tests added for both scenarios
Behaviour changes for users or extensions.

AL objects touched

Codeunit 8063 “Sales Documents”, Subscription Billing: modified

Also merged into

#11060 into releases/29.x on 2026-09-08

Context

Work items: AB#649031, AB#649032
Labels: AL: Apps (W1), Team: Finance
Systems: development

Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).