[Subcontracting] Bug 648949: Allow subcontracting direct transfers from warehouse locations - #11280
Open
alexei-dobriansky wants to merge 1 commit into
Open
Conversation
Remove the obsolete outbound warehouse guard for AB#648949 while preserving posting-mode and in-transit handling. Add straightforward Require Shipment regressions for component and WIP transfers. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: fb8e3994-dce0-4773-9daa-932d8bd11dc3
alexei-dobriansky
enabled auto-merge
September 9, 2026 15:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Remove the obsolete outbound warehouse guard in
Subc. Create Transf. Order. BaseApp supports direct Shipment and Receipt transfers from warehouse-enabled source locations, but the report rejected them before creating the transfer.Retain the valid changes from 640958: posting-mode selection, explicit in-transit-code preservation, and the existing one-step/in-transit regression tests. Keep the equivalent 28.x guard unchanged because that release does not have the same BaseApp capability.
Replace the incorrect negative test and add straightforward Require Shipment scenarios for component transfers with an explicit route and WIP-only transfers without a route. Each scenario is readable in its test procedure; setup helpers are separate and branch-free.
Linked work
Fixes AB#648949
How I validated this
What I tested and the outcome
Source-only validation: inspected the introducing commit and BaseApp validation/posting paths; checked the final diff and the test/helper structure.
git diff --checkpassed.The added AL scenarios cover automatic shipment and receipt, component quantities and locations, and WIP ledger effects without physical inventory entries. Local compilation, publishing, and AL test execution were not performed for this change, as requested. These scenarios have not been runtime-validated.
Risk & compatibility
No schema or dependency changes. Preserve BaseApp destination restrictions, one-step posting, and in-transit handling. This correction is for main/29 behavior and must not be backported to 28.x unchanged.