Mohamed Shoman SUPPORT ENG

Idea:

• It would be great to allow search in list values (Dropdown) in WMA like Unit, Disposition code, full cluster position and so.

User experience challenges:

• It's not possible to change the Input type from the Warehouse app field names.
• Considering the high number of values it's difficult to select between them and during the selection on the touch screen potential incorrect data entry will be high as well.

Business requirements:

• How to perform a partial count for an item at all the locations that have on-hand for that item at once.

Challenges:

• The partial cycle count could be performed right now using the Cycle count plans, by applying a filter on specific items, so only these items will be included in the cycle count work at the locations that have on-hand for these items.
• The way that how the cycle count work is generated is not the optimum way for the cycle count business scenario as in a standard cycle, the count plans is driven by the location, not the items so in that case, first, a location will be selected then secondly the items in the product query will be included in the cycle count work considering other options like the Maximum number of cycle counts or filtered locations could cause the fact that some items could not be counted in all locations.

Idea:

• It would be great if an option to be called partial cycle count be added to form Cycle count work by item so when this option is enabled then it creates partial cycle count works for the filtered items across the locations that have on-hand.

Idea: Support over pick in the (User and system directed) cluster picking flow

Issue and business impact:

The Quality item sampling label that is generated from a purchase order doesn’t show the information of Account number, Account name, and ordered quantity however the required information is important for the warehousing team to know which supplier the goods came from.

Idea and expectations:

The Quality item sampling label that is generated from purchase order flow should disapply of the required values of the Account number, Account name, and ordered quantity

As per the current design, it's only possible to calculate the price for a sales order or quotation line by line. The idea is to allow the users to run a job to calculate multiple orders and multiple items in the background like how it currently works with normal costing version calculation.

While running inventory closing and creating the (Weighted average inventory closing) transactions system is thrown the following error message "Inventory closing cannot proceed because available physical on-hand inventory on item XX is currently negative, which is not allowed according to its item model group." in case of the items have negative on-hand and the item model group doesn't allow physical negative inventory.

The request is to add an option to validate the negative balance before running the inventory closing.

Business scenario:

• In such a scenario where a specific operation has a planned route scrap if no scrap is actually reported (Full quniaity reported as a good quantity) while starting the next operation, it defaults to the planned requested quantity, not the good quantity of the last operation.

Example:

• User starts operation 10 with Qty = 100 where operation 10 has a planned scrap of 1% specified in the route.
• In fact, no scrap occurred on the floor, so users reported 100 as a good quantity.

Results:

• Actual results: The requested and remaining quantity of operation 20 is 99
• Expected results: The remaining quantity of operation 20 is 100.

Idea:

• Add an option “Default started quantity from the good quantity of the last operation” in Production floor execution so that when the user starts operation 20 it starts with 100 hence remaining quantity is updated accordingly to 100.

Idea:

• To support standard cost calculation of finished goods (BOM calculation) whereas raw materials are evaluated by actual cost like weighted average.

Challenges:

• As per the current design, Raw materials must have an active standard cost record to be considered during the BOM calculation.

Expectations:

• Facilitate the Raw materials cost price calculation based on the calculation group (Inventory price) or use the latest cost price record as a fallback for the costing calculation.

Issue:

• The items have been configured to use the Same batch selection functionality hence as a prerequisite configuration the Batch level is marked as Coverage plan by dimension however while updating the Minimum coverage of an item the following error is thrown: “You must set all coverage planned dimensions before you can define minimum and maximum inventory”

Challenges:

• Regardless of the fact that it's not even possible to set Minimum coverage on batch level (From an application point of view), however, assuming that even this is possible, it's not feasible from a business perspective to maintain minimum coverage on batch.
• This is a blocking situation where we should trade off two options either use (Same batch selection functionality) or leave it.

Issue:

• The start job Button is active on the Production floor execution after starting a setup job.

Idea:

• As per the intended design, the setup jobs cannot be started more than once so from a user experience the start job button should be desirable once the setup job already started.