Ability to export and import counts (including quantities counted and serial/ lot numbers) to Excel
It would be nice to be able to do a monthly physical count by lot or serial number on MS Surface, Ipads or even cell phones. (Bluetooth and USB capable scanners are widely available and compatible with tablets)
Then compare what is counted to what the system thinks is on hand, count any missed items and do an inventory adjustment.
We did an application like this on industrial scanners a few years ago. It was not that hard to develop but the industrial scanners were difficult to configure and had their own operating systems and software.
A lot of users expect this to be a core capability and not a third party application...
When browsing the Item Masterfile, the 2 current fields are Item Number and Short Description. If the user wants anything different, they must click to make changes.
I think it would be more practical for the 2 fields to be the Item Number and the Item Description. The user could then do additional clicks if they want to browse by the Short Description. The 15 characters end up being quite cryptic in many cases. The Item Description is more useful. It could be truncated after about 30 characters if necessary.
The ability to filter by date range, the transactions displayed on the screen for the stock inquiry window. Right now you see the whole item history right away, and if you have 7-10 years of historical data on the item, it gets really slow.
Across the distributions modules, you can use the Unit of Measure when processing or reporting on items. When using the 'Adjust Costs' utility, you cannot. This in turn requires the end-user to get out their calculator and start calculating values (which can and most likely will be different from due to rounding, especially with 5 decimal qty & currency options) instead of just being able to rely on the setup unit of measure options for that item.
For adjust costs, please provide the ability to utilize the item's unit of measure schedule instead of requiring the user to adjust in base qty only.
The Inventory master table has created date, modified date, but lacks user who created/modified.
This is a very helpful field when investigating who created or edited a record without going to full access logging.
When posting an Inventory Batch, the Post to GL checkbox can be unmarked. This results in the HITB record having a 1900-01-01 00:00:00.000 GL Post Date value ( which would be correct, since it was never posted to the GL side ).
However, if you run HITB for a date prior to the Doc Date, the transaction will show up ( and should not ). It should show up on and after the Doc Date.
So printing by GL Posting Date needs to also consider the Document Date when the GL Posting Date is 'blank'
0.01 -> 9,999.99
-is the current range of numbers permissible in the field.
If you sell diverse product from nuts and bolts & tiny washers that are less than a <1 gram, up to big wooden reeled telecoms cable reels the size of a car that are 1,000kg =1,000,000 this gives you a problem.
There is not enough range in the numbers to cover them.
I know the example looks extreme, however this is like less than a gram to 9kg, this is not a big range. The alternative work around of being forced into extender or modified window fields for a basic attribute like this seems overkill.
Ability to restrict a count to only those in a range of bins (without using the multiple bin functionality)