The Location does not exist. Identification fields and values: Code='' in Req. worksheet

(1) Share

Report

Posted on by Community member

It seems all the item SKU set correctly. Not sure why get stop after running middle of the item list and get this pop up message in particular Location. Other location seems fine. What potential setting is wrong?

The Location does not exist. Identification fields and values: Code=''

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (1)

Gerardo Rentería Ga... 25,157 Most Valuable Professional on at

Like (0)

Report

Hello good day, what do you do specifically?
You could copy the detail indicated in the message, it will surely give us more clues.
Greetings

Was this reply helpful? Yes No
Community member 2 on at

Like (0)

Report

I am doing Requisition worksheets for specific location. Other Location is running smoothly except this location only able to go through 10% of the SKU then stop and get this message out "The Location does not exist. Identification fields and values: Code='' . Not sure is because this location setting miss anything or particular SKU card setting wrong or why?

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,329 Super User 2025 Season 2 on at

Like (0)

Report

This looks like a data issue, could you please ask a developer to debug this?

Hopefully other experts can give you better advice.

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

Judy Microsoft Employee on at

Like (0)

Report

Hi Sir,

For the error messages, it indicates that a location with the specified code is not found in the Req. worksheet.

It is highly recommended that you can do troubleshooting following the Microsoft Documents to see if you can find any other valuable messages for that issue:

Troubleshooting overview - Business Central | Microsoft Learn

Best Regards,

Judy

Was this reply helpful? Yes No
Verified answer

_Hampus_ 67 on at

Like (1)

Report

Hi,

I just stumbled across this post while I was struggling with the same error message. After debugging the problem, my conclusion is that the error message is due to a certain item that was processed and was missing a transfer-from code in its SKU.

(the picture is from one of my Cronus databases and not from the environment where the problem actually occurred)

Was this reply helpful? Yes No