web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Cannot close migrated Direct Transfer Order – put-away blocked, undo shipment blocked

(3) ShareShare
ReportReport
Posted on by 49
Hello experts,
 
We have migrated historical data from NAV 2017 to Business Central (SaaS), including open transfer orders. Several of the migrated transfer orders is a Direct Transfer that was shipped but never received/finished in NAV before migration. I now need to close it in BC so it no longer appears in the Transfer Orders list, but I'm stuck.
Setup:
  • Location card has: Require Put-away = Yes, Require Pick = Yes, Bin Mandatory = Yes
  • Transfer order is flagged as Direct Transfer
  • Quantity Shipped is posted; Qty. to Receive is still outstanding

What I have tried:
  1. Create Inventory Put-away to post the receipt → fails with error: "All items have been shipped." As I understand, for a direct transfer the receipt is posted automatically together with the inventory pick, so a separate put-away is not allowed.
  2. Undo the posted transfer shipment line (from Posted Transfer Shipment) so I could re-ship and close it correctly → fails with error: "You cannot undo line 10000 because inventory pick lines have already been posted."
  3. Delete the transfer order → not possible because quantity has been shipped.
So I'm blocked in every direction: cannot post the receive, cannot undo the shipment, cannot delete the order.
 
Question:
What is the recommended way to close/clean up a migrated Direct Transfer order that is stuck in this half-shipped state?
  • Is it acceptable/supported to clear the Direct Transfer flag on the transfer header (e.g., via configuration package or code) and then receive it as a normal transfer?
  • Or is deleting the header/lines directly (via code/config package) the better approach if the item ledger entries are already correct from the opening balance migration?
  • Has anyone handled this scenario after a NAV → BC migration and found a clean standard solution?
Any guidance or experience would be much appreciated. Thanks in advance!
 
NB! I have tried several AI solution without any luck. 
 
I have the same question (0)
  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    3,066 Super User 2026 Season 2 on at
    Hi, thanks for the extra detail. Makes sense now, direct transfer doesn't let you split shipment and receipt apart in current BC, that's exactly why both things you tried failed — put-away wants to do ship and receive together and there's nothing left to ship, and undo just isn't offered for direct transfer at all.
    Honestly this looks like a state that shouldn't exist in a normal BC flow, only migration got you here, shipped posted with no receipt route through any standard posting. I don't see a clean UI path out of it. I'd get this corrected at the data level with your partner, forcing Qty. to Receive down to match rather than trying to post it through — not something I'd trust to a UI workaround for this case. Did you check if the pick is still sitting open somewhere, or fully consumed already? And is this just a document cleanup, or is it also throwing off inventory quantity/value?
     
    Glad to help - follow up if anything is unclear.  
    ►  If this solved it, marking it verified helps others too.      
    Regards,
    Grigorios Mavrogeorgis
    Business Central Consultant & AL Developer

    Work: Gmsoft Limited
    Blog:  insidebusinesscentral
    LinkedIn: linkedin.com/in/gregorymavrogeorgis

     
  • Blackdiamond Profile Picture
    49 on at
    Hi Grigorios,

    Thank you for the quick reply.

    I'm fully aware of how direct transfer functionality works in BC — what puzzles me is how the client was able to post the inventory picks in NAV 2017 in the first place without the process completing with the corresponding put-aways/receipt. That half-finished state is what got carried over in the migration.

    To answer your questions: there are no open inventory-pick documents remaining, and all inventory has been posted correctly — in some cases the stock has since been consumed as well. So inventory quantity and value are not affected; this is purely a document cleanup exercise so the client no longer sees these old transfer orders in the list.

    I work at a partner house myself, but most of our developers are currently on vacation, so I'm trying to do the groundwork now and have a solution ready for when they return.

    With that in mind: apart from a data-level correction through a developer, do you know of any other solution or workaround to complete this cleanup — for example via configuration package, or any supported way to force the order closed from the UI? If a code-based fix is truly the only option, that's fine too, but I'd like to rule out any simpler alternatives first.

    Thanks again for your help.


     
  • Suggested answer
    YUN ZHU Profile Picture
    102,765 Super User 2026 Season 2 on at
    How many records are there? If there's no other way, you could have the developers manually delete them from the code... though that isn't recommended.
     
    Thanks.
    ZHU
  • Suggested answer
    OussamaSabbouh Profile Picture
    18,722 Super User 2026 Season 2 on at
    Hello,
    This transfer order is in an inconsistent migrated state that cannot be completed through the standard process: for a Direct Transfer, shipment and receipt belong to the same posting process, a separate receipt is not allowed, and Microsoft also states that a direct-transfer shipment cannot be undone. Do not clear the Direct Transfer flag or delete the records through a configuration package, because this can disconnect the document from warehouse and item ledger entries. First reconcile the posted transfer shipment, item ledger entries, warehouse entries, and destination inventory; if the inventory was already correctly migrated through opening balances and this order is only an orphan document, the clean approach is a controlled one-time data-repair extension or a Microsoft support request to remove/close the orphan header and lines after testing in a sandbox. There is no standard UI function that safely fixes this specific half-posted migrated direct transfer.
     
    Regards,
    Oussama Sabbouh
  • Blackdiamond Profile Picture
    49 on at

    @Yun Zhu – Thanks for the reply. We have 100+ transfer orders where the item was never received after the pick was posted, so deleting them isn't something we can do lightly, since we still need to account for that inventory landing on the correct location. Given that scale, what would you recommend as the solution here?

     

    @OussamaSabbouh – Could you clarify the reconciliation step you mentioned? Specifically:


    • When you say "reconcile the posted transfer shipment, item ledger entries, warehouse entries, and destination inventory" — are you suggesting we manually trace each transfer order's item ledger/warehouse entries against the current on-hand quantity at the destination location to confirm the migration already landed the stock correctly, before we touch the header/lines?

    • By "orphan document," do you mean a transfer order header/lines that no longer have any open warehouse activity (pick/put-away) tied to them, i.e. purely a dangling document with no functional link to inventory anymore?

    • On the "controlled one-time data-repair extension" — would this be a custom AL codeunit that deletes/closes the header and lines directly in the tables (bypassing the standard posting routines), run once against the affected 100+ transfer orders, as opposed to going through Microsoft support?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 575 Super User 2026 Season 2

#2
YUN ZHU Profile Picture

YUN ZHU 430 Super User 2026 Season 2

#3
Grigorios Mavrogeorgis Profile Picture

Grigorios Mavrogeorgis 334 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans