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?

BOO! Happy Halloween!
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?

BOO! Happy Halloween!
KIN-I-6579: Data Collection (MES) should allow all non-AMM shop transactions
The data collection module has many options that can be run directly from these traditional MES Screen, but some of the transactions appear to have a restriction that requires the AMM license before they can be done with the Data Collection Module. This idea is to correct the data collection screens so that all shop floor type tranactions can be done without the AMM license, unless they are truly part of the Advanced Material Module (AMM).
I mean Receipt Entry is basic functionality - this is just a money grab. so dum.
I’m sure this one isn’t available yet because I just created it. But on the off chance that Tim sees it this morning I’m gonna go ahead and drop it here.
There should be an easy way for users to show data from a baq in a gantt component. I’m proposing a simplified read only gantt component for visualizing a task timeline without the added complexity of tying to the scheduling service. I think we should be able to create a baq with the appropriate columns for input and show it in a Gantt.
I have a few ideas I’d like to push… again… this week:
Allow Delivery Plans to be Cross Order
In theory this would allow users to link different orders to have the same shipping data.
Remove top GL line when using Allocations
When using GL Allocation, it adds lines based on the allocation but the initial line with the entire amount does not self-delete causing essentially a duplication of the line amount.
Include a ‘Stub Stub Check’ Option for Check Printing
I think ‘stub stub check’ is the default/standard check and should be supported natively out of the box. This is further emphasized by the fact that the checks that Epicor supplies are ‘stub stub check’.
Wishing you all a happy Halloween Friday.
Is this something that happened recently? I swear that it used to work without an AMM license.
Been like that since we started to our onboarding 2 years ago ![]()
I see posts on here about it in EKW so I think it been a thing forever.
My favorite idea (just created) is this one Log In - Epicor Identity for enhancing Cycle Counting (& Physical Inventory) to allow for “Entry by sheet”..
The Cycle Counting/Physical Inventory module was a feature brought over from our legacy Avante system, but when it was brought over, they included “Print by sheet” (instead of print by tag) but never included the “Enter counts by sheet” which is an amazing time saver for entering cycle counts.
The way it works is:
Frightdeas was right there…
Right, skipping to tag #____ is murder in Count Tag Entry.
Conceptually that’s similar to what I’ve had to engineer here.
We hand out a bundle of 25 “toe tags” - the carbon-copy, pre-wired classic inventory tag - to a group, say tag numbers 0076-0100, and then they turn in the tags (in order, mister!) and someone keys that in.
Problem of course is that Uline tag 0076 does not naturally correspond to Kinetic tag 00000118657.1.
What I’ve done in the past was to void enough blank tags so that there would be a blank tag with tag number 00000120076.1. Then I made an uBAQ dashboard to easily jump to that section. (Drop the decimal; convert to integer, and give them a couple filter boxes.)
But that was still a nightmare, so I just gave them a UD table to enter into (with lots of validation events), and an EFx writes the data to the relevant CCTag.
But unless your warehouse is ordered like the library, it is hard to physically count in tag order, no matter what sort method you choose.
But yes, any navigation/entry improvement to Count Tag Entry is welcome.
I believe that when you generate the tag numbers, you can specify to sort them in bin order, so that they are in a good sequence.
Right, but I’m saying,
So I’ll flesh out my inner monologue that was in my head before I posted that:
Me 1: Just print tags in bin order!
Me 2: We’ve tried that. But our warehouse is not arranged alphabetically - people just create whatever bin names they want
Me 1: Well that’s a management problem, and other condescending statements.
Me 2: True, but we are too entrenched now, and the count is next week (hypothetically).
Also, parts are not located where they are supposed to be, so it results in most shelves being a mix of
Again, I know, I know, if we were more perfect, this would be so easy!
But if your company is not perfect, then tag entry is a cruel mistress.
Hmmm.. Thinking another enhancement Epicor Idea is in order… maybe an option to generate tags in the BIN SEQUENCE order as defined in the warehouse bin table.
or even first by ZONE and then by BinSeq
Agreed. You are definitely on to things we have discussed at my company there. There may even be an idea for this already…
But yes, it would always drive our people crazy that they couldn’t really zone the warehouse for cycle counting.
Honestly, though, with cycle counting, what our previous GM implemented a few months ago was the best idea I’ve seen or thought of.
We lump the critical parts into various types (grating, bumpers – groups that makes sense to us here) and then count everything in the type, regardless of A/B/C or high or low volume. Since that stuff all looks the same to most people, we’d get miscounts of one part vs another similar part. Doing the like parts at the same time reduces that.
And there is definitely no print order for that!
This is it:
Cycle Count Sequence on Bins
Also:
Add Timestamps to CMP Refresh DB Backup
On the Cloud Management Portal, there is a lack of timestamp visibility onthe backups, making it difficult to confidently choose the most accurate restore point.
For example on the 31st, I selected the 30th do a DB restore.
Only afterwards to find all the customisations loaded into the DB on the 30th were missing..spooky ![]()
It was later found when I reviewed the logs that despite the 30th being selected, the 29th differential backup was taken.
If the DB backups had timestamps, I could have seen there was no backup taken on the 30th!
There is a NEW idea that I created, and i merged in one of the two you found. The other is a separate idea that will need to be kept separate. Here is the new idea: KIN-I-7058 - Generate Inventory Count Tags by Zone & Bin Sequence
Thank you, Tim. We really do appreciate you listening to our whining.
Speaking of listening to our whine, how’s the process for getting all ideas reviewed quicker going? There is still a ECM idea from the Oct 24th thread that still can’t be viewed.
It looks like there’s already a sheet number reference in the count entry table’s dataset? This should plausibly be possible now by filtering by page number…