Vendors Can’t be Put on Hold and Other Inconsistencies

As I pointed out in a previous article , various areas of M2M function differently. When you spend enough time administering a M2M database you realize that at one time there were several different individuals or teams working on various modules (sales, invoices, purchasing, production, etc) and they did not communicate enough.

For example, M2M does not allow you to put Vendors on hold. There is no way to prevent a purchasing agent from purchasing from a specific Vendor. This is inconsistent with the customer screen (CUST) which allows you to prevent users from selling to certain customers. M2M’s workaround is to change the vendor name to “DO NOT USE” but that is not a very elegant solution.

Similarly, M2M handles releases differently in the Sales and Purchasing modules. The Sales module has a dedicated table for releases while Purchasing integrates them into the items table. For beginners, it can be confusing to report against.

What other inconsistencies have you noticed?

2 comments to Vendors Can’t be Put on Hold and Other Inconsistencies

  • Fred Crawford

    How about not being able to correct/change the primary vendor for “subcontract” vendor purchase orders. The only way that you are able to correct/change these, are to go directly in the SQL database and change the priority numbers. You can correct/change the primary vendor for “regular purchased items” directly in the item master program. I created a CR for this a year or two ago, but to my knowledge, nothing has ever been done for this.

    In all fairness to M2M, they are no different from any other software developer. When you have multiple programmers working on multiple projects over a long period of time (years), there will always be some inconsistencies. From my own experience developing software for IBM AS/400 (iseries), as hard as my group worked to keep everything consistent, much to my dismay, there are still some differences here and there.

  • Interesting point Fred. However, I would like to caution everyone to think twice before modifying their SQL tables directly. Only do so if you’re confident that you know what you’re doing.

Leave a Reply




You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>