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?
Todayās Valentineās Day Special:
Share some ideasā¦
ā¦ get some Love.
Even if theyāre not your own, post up the favorites youāve been secretly admiring and letās show some love to the Ideas that give us the warm and fuzzies.
Here are a few of my ācrushesā:
Bring back detailed error messages in the user interface - @aosemwengie1
Replace Tired SSRS Reports with a more modern tool - @josecgomez
Can we change the name of Non-Stock? - @JasonMcD
Comprehensive request to re-engineer all of the Email actions and components in Kinetic - @MikeGross
And of course the Idea thatās so beautiful, everybody is afraid to ask it out:
Make the software more friendly for DevOps Practices for Customers, the Cloud Team, and Professional Services - @Mark_Wonsil
Sorry, I am so against this one, I just left a comment on the idea to not do this.
I also donāt agree with changing the word non-stock, at least not as suggested, and didnāt vote but commented on this one. I believe the problem is that it isnāt clear all the different behaviors that are driven from that checkbox and there is huge room for improvement. For example, what if you could explicitly set the default types of suggestions to receive for that part (make direct, purchase direct, make to stock, etc.). Wouldnāt that remove so much confusion?
Well I am not in any way offended by the feedback. Just kind of wish it came soonerā¦
I do know that ānon-stockā is confusing as all get-out, and any attempts by Epicorās help system to explain it are wholly insufficient.
To really understand it, you need to read the MRP Technical Reference Guide. That contains all of the logic as to how it is applied (Maybe the Scheduling Technical Reference Guide too). I completely agree it is a complicated and confusing field and functionality, but would be concerned that if Epicor changed it, they would be cutting off their nose to spite their face.
Donāt worry, the odds they do anything with this idea are 0.0%
I mean, I know, but you didnāt have to actually say it. 
This isnāt my idea but Iām a big fan of it.
# Kinetic 2025.2 - The Boring Edition
Even if it also has a 0.0% chance of ever happening.
I wish we would get updates on this, and many other Kinetic ideas that have a status of āIn Developmentā sinceā¦2020. Oh well, me finding love has been āIn Developmentā forever.
I would agree with this!
The problem I encounter is a part flagged āNon-Stockā and āQuantity Bearingā could still be held in inventory. Which is fine. By definition, this makes sense.
The problem is that the system defaults to āmake directā even though we have parts on the shelf. So (if weāre not paying attention) the system may put suggestions for parts we actually have in inventory at that moment.
Iād be okay with a simple pop-up warning of āHey, this is non-stock, but you have some in inventory, you want to ship those?ā or āā¦ you want to issue those to this job instead of making/buying them direct?ā
Iām sure this could be done via BPMā¦ just feel like the system should be smart enough that if there are unallocated and/or unreserved parts in inventory, that quantity should be considered in its calculations/suggestions, etc.
I need a warning when someone is going to be this funny. I almost spit my drink out all over my keyboard.
Like calling them ājobsā instead of āwork ordersā?
Edit: This is defined as being for Pull As Assembly parts, not sure if it would work with purchased parts. But we all know how Epicor likes to explain a field as one thing, but it actually does much more.
Part Site.
Right, I almost suggested that, but I feel like sales orders do not honor thatā¦
If Iām reading that correctly, it would help with jobsā¦ but what about SO releases?
Also, hereās a note on that checkbox (KB0130414):
The Auto Consume flag in Part Maintenance should only be used with stocked manufactured parts. If this flag is set to true for non-stock manufactured parts, it can cause issues such as marking operations/materials as complete prematurely.
For a manufactured part or a purchased part? Yes, per the documentation, this only affects subassemblies and not the top level.
I hear ya. I canāt even get to a āGauging Interestā status.
