Public Profile
  • Inventory Valuation Report - Direct Postings

    While I always highly recommend to our customer to NEVER Direct post to their inventory accounts, unfortunately some do (even the stock Cronus db has a opening balance posting in the test data). I would proposed that on the inventory valuation report the direct postings are included (total and details depending on how the report is run). This could be another section at the end of the report and have a grand total. this would help tie out the report to the GL accounts.
  • Remit to on Company Information Page

    It would be helpful to have another address on the Company Information Page we could use for a Remit to address. it is pretty common in the US
  • Allow PO changes if only a Put-away remains

    The current logic will not allow a user to change the PO quantity if there is an open Put-Away for the item against the PO. Not allowing with an open warehosue receipt makes sense but if there is no unposted whse receipt and only a put away the user should be able to change the PO. As long as you are changing the quantity to an amount greater than or equal to the tot al quantity received and there in not an unposted warehosue receipt for the item allow the user to change. This is a simple change to just change the document types you are checking for when you validate a quantity change.
  • View Put-aways from the Purchase Order

    On the Purchase order the user is not able to see open or registered warehosue put-aways (only inventory put-aways). This would be a simple menu item to add and useful to users as the only way they can find them now by PO or item is to go to the whse put-away page or from the bin contents.
  • Posting by cost share (Materials, Labor and Overhead)

    We have had a few Large Customers wanting their COGS, Inventory and WIP to be posted into sub accounts for Materials, Labor and Overhead. This appears to becoming more common recently and several other ERP solutions in the marketplace allow for this type of posting. Inventory Total Inventory Materials Inventory Labor Inventory Overhead
  • Show USerID on the Database Locks page

    On the Database Locks page it would be extremely helpful to show the User ID so you know who is actually causing the locks. Without it is is pretty difficult to determine who is locking, especially in large companies.
  • Headline Page for Customers to add headlines without development

    We just had a customer ask to add a Headline Message. Right now this cannot be done without development. it would be valuable to have a Headline Page where a customer can add a message with a start and end date that would show in the role center headline. This would allow customers to add messages to their users without development.
  • Make the Printer Selections Company Specific

    Table 78 Printer Selections is set to share across companies which is a major limitation when it comes to setting up reports in a multi-company environment. The functionality is not useable for some of our customers as when we set a report up to a printer and even to a specific user based on the company the report needs to go to different printers. This functionality has caused major confusion with reports printing to the wrong printers in a multi-company environment. Please make the table company specific or add a field to specify the company in the record.
  • Rapid Start Modify Only Setting

    When importing data to master record tables like item, customer, vendor, etc. it would be really helpful to have a setting (boolean) on the table section of the config package where you could check that you only want to modify and NOT create records. I have had many instances where the imported data records contains new records that you may not want to create and the Modify Only setting would resolve this. For records not existing they would be sent to the errors just like when loading sub tables where the master record does not exist (i.e. bom line where the item doesn't exist). An alternative might be to place the boolean at the field level (i.e. for items on the No. field where the code would then check to see if the No. exists before creating a new record). This would be a really simple addition as it would just be an additional Boolean which would drive a validation event to make sure the record exists before creating a new record.
  • Block Reclass from Receive bin if Require Put-Away Enabled

    if a location has Require Put-Away enabled, block item reclassification / non- putaway moves from the bin identified as the receipt Bin on the location card.


    If the user does an item reclassification to move the items the availability for picks will be messed up as the quantity to put away on the purchase receipt will never be adjusted properly and cannot be fixed by moving the material back and attempting to re-put the material away on a put-away. The only way to fix is to create a processing report to update the warehosue receipt line via code.