Kevin Fons Sr Application Consultant

It would save a lot of time if there were functionality similar to get shipment lines with filters on the get receipt lines for purchase invoicing. For example filter to a specific order / PO number or receipt date or any field that is on the purchase receipt line / header?

The way the get recipt lines page was created over half of the fields on the page cannot be filtered or sorted. Make ALL fields on the page filter able so the user can efficiently use this page to narrow down the lines they need to add to the invoice.

Over the years we have had several customers ask to be able to set a different flushing method than on the item flushing method for a particular components(s) on a production BOM. You can change it on the production order bom but you cannot set a value per the "standard BOM".

I would think in the BOM the field would be blank or user entered vs inheriting from the item when the BOM is created.

If it is left blank when a production order is refreshed it would use the value from the item as it does now. If there was a value entered when the BOM is created, it would use the value on the production bom vs from the item.

Currently the bin content is deleted when the quantity moves to zero and the bin is not fixed. Since there is a flaw in the item reclass and item journal allowing the user to move inventory out of a bin resulting in negative availability it would help to base to bin content removal on more than just quantity (pick qty, or bin availability). Of course if the item reclass / journal bug is fixed this would not be required.

Currently the item reclass / item journal doe not look at bin availability when validating the entries (only total Invneotry availability). This allows users to move material out of bins that have picks created against that inventory resulting in negative availability in the bin and if the bin content moves to zero and it's not a fixed bin the bin content is removed.

At minimum there needs to be a very strong warning when the item reclass / journal line would result on negative availability for the bin/iten/lot or serial availability in the bin.  

it would be extremely helpful to have a checkbox in Rapids Start / Configuration Packages to only update exisiting records and nto create new records. Many times we might want to update Item data but a user may have a typo or the list may have additional items but we do not want rapids start to add these items, only update the data for the items that match.

This could reduce a lot of errors.

I pretty much always recommend FIFO costing over standard these days but I keep having companies choose Standard and then at some point down the road realize I may have been right and want to move to FIFO.

It would be amazing to have a tool to move items from Standard to FIFO.

I envision a worksheet where you can add items in bulk based on filters and then run a process that would handle the conversion. It would be quite complex as there are a lot of "cleanups" to do like adjusting inventory out and back in, adjusting open transactions, etc.

I am getting this more and more and when I suggest creating a new item number it may work for a couple items but when a company has 40K+ items it's not viable.

It would be nice to have an option where a warehouse pick for a production order could operate similar to and inventory pick and consum what was picked on register of the pick. This could be a flag or enum at the location level for production pick register action (pick, Pick+consume).

This would eliminate a stepf for customers with the component flushing methods set to manual who want to consume at time of pick but cannot use the inventory pick due to how their location is configured.

From the admin center you can go to the environment and the APPS button to see what new versions of APPS are available and you can install from there.

It would be really nice if when a new version of a 3rd party APP is available for an installed app the notification users in the ADMIN center could be emailed that a new version is available. The email ideally would only be for the Production instances to avoid too many "duplicate" emails. This would save time from having to go to the app center to check periodically.

I consider this a Bug but MSFT may not so I am creating a Idea.

.

If an item is setup to have lot tracking but not serial BC allows a user to enter a serial number still in the item tracking screen creating all sorts of Chaos downstream.

Scenario - Item Tracking Code set to Lot specific with Lot warehouse tracking and NO serial number tracking set.

User can enter a serial number in the item tracking with a lot number in production output and other item journal transactions.