Bug 572435 Transfer Order reservation for Inbound not possible message fully reserved appears, but no entries in the reservation table.

[v-praghav]

What & why

Issue After shipping a Transfer Order (non-direct), trying to reserve the Inbound line shows a misleading "Fully reserved." message with no reservation entries created. The Available - Transfer Lines page also displays no lines for the inbound direction.
Cause: The SetSourceTableFilters() procedure in [AvailableTransferLines.Page.al]was missing the "Qty. in Transit (Base)" > 0 filter for inbound, so no lines were returned. Additionally, AutoReserve() and Reserve from Current Line in [Reservation.Page.al] raised the generic "Fully reserved." error for inbound Transfer Lines without any meaningful explanation.
SolutionSolution
Added Rec.SetFilter("Qty. in Transit (Base)", '>0') for the inbound case so in-transit lines appear correctly. Introduced a ValidateReservationApplicable() function that shows a specific error — "Inbound quantities cannot be reserved until the items are received at the Transfer-to location." — called by both AutoReserve() and Reserve from Current Line.

Linked work

AB#572435
Fixes #

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)

Risk & compatibility