x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 2374 views
  • Users 0 members are here
Browse Forums
Announcements
68
topics
93
replies
Customization and Integration
262
topics
822
replies
Financials, Projects, and Administration
382
topics
843
replies
General Discussion
327
topics
836
replies
Installation and Technical Issues
335
topics
1k
replies
Manufacturing, Distribution, and Applications
341
topics
696
replies
Reporting and Analytics
123
topics
480
replies
JamesD

Setting MOQ, Order Multiple Qt on Purchasing Side When Registering Item

Posted By

When Registering an Item in 500, we can register an Item's MOQ & Multiple Order Qty so when we an Item under Sales Order (SO) and if the Qty entered in SO isn't correct, a warning will pop up telling us that the Qty doesn't match the MOQ &/or Multiple Order Qty.  This is good.

How can the same thing be done for the Purchase Order (PO) side so that when we order a part to a supplier, we will be ordering with the correct MOQ & Multiple Order Qty that the supplier sells at?  That is when registering an item to set the MOQ & Multiple Order Qty on both the Sales & Purchasing side.

This is something I have been trying to get 500 do for a long time but have found no way.

  • 0

    Hi James,

    Since it looks like your question relates directly to Sage 500 ERP, I am going to move your post to that Support Group so that other users of this software will see it and be able to offer their thoughts and insight.

    Thanks,

    Derek

  • 0 in reply to Derek Vink

    Unfortunately, that sounds like it would have to be an enhancement starting at the Vendor Item level.

  • 0 in reply to Ramon M.

    You could use Alerts/KnowledgeSync to catch these after the fact and alert you.  Another way would be to write a trigger which could send an email or deny the writing of the PO.  Another option would be to have a master developer write a mod.  Personally (not knowing your real requirements) I'd write a SQL job which scans the POs and sends an email when it finds something it doesn't like.  We use this extensively in our Sales Order system and it's quite successful.  One more idea is to add a button to the batch process.  It could then run a stored procedure which reports on issues.  We use this also though I think I like the SQL job better.

*Community Hub is the new name for Sage City