Skip to main content

DynamicsNAV & Business Central - Internal Movement Error - You Cannot use Location Code.

Hi Readers,

I was handling a support ticket for a customer who is recently upgraded from NAV 2013R2 to Business Central 14.

Customer users use Internal Movement as a part of this process.

When a user is trying to create a New Internal Movement system is generating this error message.

This article/solution is for #NAV2018 & #MSDYN365BC.


What is Internal Movement -

Specifies the take and place lines for items that you want to move between bins when they are not demanded by a particular source document. To process this manual movement, you then transfer the internal movement details to the Inventory Movement window where you can register it.

Read More about Internal Movement.

What setup is required for Internal Movement?

  • Internal Movement Required user to be setup as Warehouse Employee.
  • Location that is selected in Warehouse Employee should have - 
    • Bin Mandatory = TRUE and Directed Put-away and Pick = FALSE.

So first I thought that the user might be missing the Warehouse Employee setup and I checked Warehouse Employee and Location Card.


After Debugging we found out -

  • Base Microsoft Code is changed after NAV 2013 R2 related to New Internal Movement.

How to Fix Issue?

Check Warehouse Employee, Filter for records with Location Code Blank and Delete Records where Location Code is Blank.


Try Create Internal Movement?

After Deleting Junk Data Create a new Internal Movement. It will work as expected.


I hope it helps if you get stuck with this issue.

Stay Tuned for more.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.