On Friday, itās EpiUsers Frideas Day! Have you been to the Epicor Ideas Portal recently? If so, are there some ideas you want to encourage other users to vote for? Maybe want to add comments to an existing idea?
Figured weād kick this off early this week since most of our US contingent will be off work tomorrow and/or Friday for the Thanksgiving Holiday.
BLACK FRIDAY SPECIAL!
All Epicor Ideas are FREE to enter and FREE to vote for!
Donāt panic! There are plenty for everyone!
A couple that would really help productivity/user experience (IMO):
Ability to Renumber Quote Lines - KIN-I-4810
Add Assembly Navigation to Job Entry/Tracker Activity Tab - KIN-I-4861
KNTC-I-1954 - Planning Contracts not tied to Bin
Planning contracts are incredibly useful, yet the implementation where it ties them ta specific bin is dopey. It would make much more sense to tie it to a PCID, or just track it at the PartBin level (like we do Lots, PIDS) where the Items are shouldnāt matter what should matter is that they satisfy the contract. The current implementation makes it mostly useless for any real world warehouses. Nobody can be tied to keeping a specific thing in a specific bin to make the āsystemā happy.
An oldie but goodie, there. Havenāt seen that one before. Thanks for posting it!
Honestly this one should be more like Epicor hire a good DBA and have them revamp your entire Index infrastructure and put proper maintenance plans in place across the product. When we look at Index usability thereās a tiny fraction of indexes that get pounded and 90% of the rest never get used.
Indexes bloat your Db and make inserts slow!
Going to bump my shipping ideas:
Add RFQ Reference Rows in Time Phase - KIN-I-5805
If a PO Suggestion is processed to a PO, the PO information is visible in Time Phase, so you can have a full accounting of the demand/supply.
However, if a PO Suggestion is processed to an RFQ, there is no reference to this in Time Phase. The suggestion was processed, so it no longer appears, and there is no PO (yet) so there is no way for someone to know a given part is being taken care of, if there was a glitch and no suggestion was ever created, etc. This creates a lot of confusion and requires additional digging to truly learn the status of a particular part.
cries in DBA
Iām less worried about the indexes, what we get is common enough. Iād bet someone thought about it enough to inquire about SQL Serverās opinions on missing indexes and apply it as gospel, bless their hearts. Happens all the time. The unbounded defiance of normalization, however, thatāll boost our data size by a solid decimal point.
Although, whoeverās setting up SaaS database maintenance has definitely heard of Ola Hallengren and hasnāt decided they can do better, which is very good news.
Great one! Voted.
Doesnāt MRP also ignore RFQs and spit out a new suggestion? I seem to recall having seen that behavior in the past, but could be mistaken and/or my info is outdated.
