Currently, when a Warehouse Employee is assigned to all locations using a blank Location Code, creating a new Internal Movement fails if any location in the system does not meet required warehouse settings, such as Bin Mandatory = Yes. In this scenario, the system validates the blank location or an invalid location first and prevents Internal Movement creation, even when other valid warehouse locations are available.

This behavior results in confusing location‑related validation errors and blocks users from proceeding, despite having correctly configured warehouse locations in the environment. The system does not fall back to a valid location nor prompt the user to select one.

The idea is to improve the Internal Movement creation logic so that the system:

• Ignores locations that are not eligible for warehouse processing
• Automatically selects a valid warehouse location where requirements are met, or
• Prompts the user to choose from eligible locations only

This enhancement would improve usability and make warehouse operations more intuitive in environments with multiple or mixed‑configuration locations, while maintaining existing warehouse validation rules.