Basma Ehab (Convergys International Europe B V) technical support engineering

If the WHSCloseContainerProfile.PrintPackingSlip function is specifically designed for sales orders and does not directly support printing packing slips for transfer orders, it is problematic. At the very least, the posting dialog for sales orders should not appear when closing a container for a transfer order, as it currently disrupts the process.

Additionally, it is crucial to ensure that the packaging procedures for both sales orders and transfer orders are consistent within the warehouse management module. Warehouse employees only interact with WHS shipments or WHS containers and cannot distinguish between containers for transfer orders—which require manual packing slip posting—and those for sales orders.

Imagine managing several thousand containers of sales and transfer orders mixed together at a packing station each day.

The system generates an error when choosing 'Report as Finished' and 'Put Away' simultaneously, preventing the process from being completed. Ideally, if 'Report as Finished' and 'Put Away' are chosen together, the system should work without errors.

the pop message of counting reason code didn’t appear when you use “adjust in ”  warehouse mobile

application menu and to choose the reason code you should click on the counting

reason code and edit it and then you can choose it from the 2^nd screen.

The pop message of counting reason code should appear 

when you use “adjust in ” warehouse mobile application menu in the same screen as “adjust out “

menu because they have the same setup

A purchase order linked to a sales order gets a license plate upon receipt. After put-away, the reservation is lost on the inventory screen but remains on the sales order screen. When sales order picking starts, the system incorrectly selects the first available stock alphabetically rather than the specific license plate stock.

Users are asking for a sort of a design enhancement to support this scenario without the need to use cross docking.

The system doesn't automatically execute work if a sales order has multiple lines and at least one line has a manual batch reservation. This causes delays and errors in order processing. The system should handle batch reservations and execute work automatically, even with manual batch reservations. And Batch Reservation and automatic work execution should function properly, even if the sales order line/load has multiple lines and at least one sales order line has a manual batch reservation.

We need to move 3 damaged items from Location A (Floor) to Location B (Damaged Items) and update the inventory status from 'Available' to 'Damaged'. However, this task cannot be accomplished through the browser.

in addition, the "On-hand by location" form allows changing the inventory status, but it does not permit specifying the quantity or location.

Update the quantity when using India localization and import order toggle without being blank

create a sales line very quickly by inputting Item and Qty with minimal number of actions and without triggering a validation error.

Sales order processing and inquiry tiles are not updating correctly, leading to confusion in order visibility.

The issue arises from mixing up delayed orders, based on customer-requested shipping dates, with backorders, based on the confirmed delivery dates.

The only fix for this is to create a separate tile for backorder lines, though this solution is time-consuming

.

The "Safety Level of Invoiced Order" parameter, when locked in Company X, is inadvertently affecting the creation of intercompany (IC) orders and sales orders in Company Y. This results in orders in Company Y being locked as well, preventing necessary changes and updates.